Thanks for this great tool!

In the context of solid we often have RDF serialized .acl files. Specifically they usually serialised in turtle. Could this extension add support to apply syntax highlighting to those files by default if there is no other syntax highlighting already applied to .acl by other extensions.

{
     "@context": {"@vocab": "http://schema.org/"},
     "@graph": [
         {
             "@type":"schema:Thing",
             "@id":"https://data.example.com/thing/1",
             "isLogic-as-Boolean": true,
             "isLogic-as-String" : "YES"        
         }
     ]
 }

when transformed to Turtle gives

@prefix schema: <http://schema.org/>.
@prefix thing: <https://data.example.com/thing/>.

thing:1
    a <schema:Thing>;
    schema:isLogic-as-Boolean false;
    schema:isLogic-as-String "YES".

Note that true is now false which is not logical.

Conversion to N-quads gives

<https://data.example.com/thing/1> <http://schema.org/isLogic-as-Boolean> "true"^^<http://www.w3.org/2001/XMLSchema#boolean>  .
<https://data.example.com/thing/1> <http://schema.org/isLogic-as-String> "YES"  .
<https://data.example.com/thing/1> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <schema:Thing>  .

Here the true is recognized as a true Boolelan, which is logical.

Other serialisations (compact, flatten, expanded) behave logical, from the true perspective at least.

It will be great to add the possibility of converting to Mermaid.

Maybe CRITERIA can be reused.

Hi!

Just discovered your extension and really like its capabilities.
Could you please provide an update to detect whether or not dark-mode is set and invert the colors of the labels in the visualization so we can read them?

Thanks!

tduval-unifylogic

In order to support this extension vscodium editors (that have the telemetry from vscode stripped) it needs to be published to the openvsx marketplace.

I would be very grateful if this could be supported (and this has also been requested in https://forum.solidproject.org/t/solid-app-development-tech-tools-stack-recommentation/5838/7).

Hello

I have noticed that when using a TTL to query with optional where clauses, the output doesn't allow for blank values and therefore shifts the populated values of one column into the unpopulated value.

For example, if I run the below query:

# file: example_file.ttl

prefix ex: <http://www.example.com>

select ?Name ?City ?PhoneNumber ?DateOfBirth
where {
?Name ex:LivesIn ?City.
?Name ex:BornOn ?DateOfBirth.
optional {?Name ex:HasPhoneNumber ?PhoneNumber.}
}

And my data has incomplete phone numbers and hence is being queried as an optional data point, I am seeing something like the below returned:

The lack of phone number for Fred and Sarah sees their dates of birth slip into the phone number column.

I would expect it to look like the below:

This appears on both the CSV output and the HTML view.

Remote "@context" is not properly supported, i.e. https not recognized.

How to reproduce

Create a file with content:

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "actor": "https://other_domain/users/phoenix",
  "id": "https://other_domain/users/phoenix#likes/557",
  "object": "https://my_domain/activitypub/helge/id567",
  "type": "Like"
}

run Linked-Data: Compact

Error messages:

file:///home/helge/code/bovine/tests/data/https%3A/www.w3.org/ns/activitystreams. Detail: Unable to read file '/home/helge/code/bovine/tests/data/https:/www.w3.org/ns/activitystreams' (Error: Unable to resolve nonexistent file '/home/helge/code/bovine/tests/data/https:/www.w3.org/ns/activitystreams')

and

Dereferencing a URL did not result in a valid JSON-LD object. Possible causes are an inaccessible URL perhaps due to a same-origin policy (ensure the server uses CORS if you are using client-side JavaScript), too many redirects, a non-JSON response, or more than one HTTP Link Header was provided for a remote context.

The SHACL graph get loaded fine, but I get:

this.dataset.match is not a function

Any ideas?

Given

@prefix ex: <http://example.org/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

ex:alice
  ex:name "Alice" ;
  ex:age "25"^^xsd:integer .

ex:bob 
  ex:name "Bob" ;
  ex:age "25"^^xsd:integer .

ex:charlie
  ex:name "Charlie" ;
  ex:age "25"^^xsd:integer .

ex:dave
  ex:name "Dave" ;
  ex:age "25"^^xsd:integer .

running the following query

PREFIX ex: <http://example.org/>

select ?name ?age
where {
  ?person ex:name ?name .
  OPTIONAL{?person ex:age ?age.}
}

gives the following expected result

But executing the same query on this input:

@prefix ex: <http://example.org/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

ex:alice
  ex:name "Alice" .
  # ex:age "25"^^xsd:integer .

ex:bob 
  ex:name "Bob" ;
  ex:age "25"^^xsd:integer .

ex:charlie
  ex:name "Charlie" ;
  ex:age "25"^^xsd:integer .

ex:dave
  ex:name "Dave" ;
  ex:age "25"^^xsd:integer .

give this result:

with this data result:

"Alice"
"Bob";"25"
"Charlie";"25"
"Dave";"25"

As I raised in william-vw/vscode-extension-n3#1; it would be great of this extension could support Notation3 syntax by using the https://github.com/william-vw/vscode-extension-n3 extension.

Linked Data Extension v1.0.6
VSCode/Windows Version:

I am using your example for SHACL validation by placing the shapes attribute as a comment with the relative path to the shapes file:

# shapes: shacl_example_shapes.ttl
@prefix ex: <https://example.com/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

ex:Alice
	a ex:Person ;
	ex:ssn "987-65-432A" .

However, still a dialog opens asking me to select the shapes file.