precise correspondence YAML-JSONLD-TTL

VladimirAlexiev commented 7 months ago

Hi @beachtom (cc @Gonsco and @EdliraK and @maximelefrancois86 )! (As continuation to #6)

For every regulation, in addition to a YAML file, we also need a JSONLD and TTL, made automatically and with standard tools. I know Thamer made some tools, but we need to use standard RDF conversion tools to have any success.

How did you make FI2.ttl?

https://ci.mines-stetienne.fr/aec3po/aec3po.jsonld defines hasTarget as @id, but you have

<https://data.accordproject.eu/2.1.2.4_method.1.1.1.2> <https://w3id.org/lbd/aec3po/hasTarget> "pi" .

similarly hasComparator is defined as @id, but you have:

<https://data.accordproject.eu/Government_Decree_on_Accessibility_of_building/2.1.2.4_method.1> <https://w3id.org/lbd/aec3po/hasComparator> "CheckMethodComparator-multiplication" .

"functions" and "tan" are missing from it

riot

I tried to convert it with this tool, part of Jena:

riot --formatted ttl FI2.jsonld >FI2-riot.ttl

I got a bunch of errors:

The context does not define the expansion of hasComparator values. @maximelefrancois86 this can be done by declaring it `@type:@vocab and then declaring the @vocab namespace for it. Or you can enumerate all values:

Apr 03, 2024 10:12:45 AM com.apicatalog.jsonld.deseralization.JsonLdToRdf build
WARNING: Non well-formed subject [%] has been skipped.
Apr 03, 2024 10:12:45 AM com.apicatalog.jsonld.deseralization.JsonLdToRdf build
WARNING: Non well-formed subject [CheckMethodComparator-eq] has been skipped.
Apr 03, 2024 10:12:45 AM com.apicatalog.jsonld.deseralization.JsonLdToRdf build
WARNING: Non well-formed subject [CheckMethodComparator-ge] has been skipped.
Apr 03, 2024 10:12:45 AM com.apicatalog.jsonld.deseralization.JsonLdToRdf build
WARNING: Non well-formed subject [CheckMethodComparator-gt] has been skipped.
Apr 03, 2024 10:12:45 AM com.apicatalog.jsonld.deseralization.JsonLdToRdf build
WARNING: Non well-formed subject [CheckMethodComparator-le] has been skipped.
Apr 03, 2024 10:12:45 AM com.apicatalog.jsonld.deseralization.JsonLdToRdf build
WARNING: Non well-formed subject [CheckMethodComparator-logicalAND] has been skipped.
Apr 03, 2024 10:12:45 AM com.apicatalog.jsonld.deseralization.JsonLdToRdf build
WARNING: Non well-formed subject [CheckMethodComparator-lt] has been skipped.
Apr 03, 2024 10:12:45 AM com.apicatalog.jsonld.deseralization.JsonLdToRdf build
WARNING: Non well-formed subject [CheckMethodOperator-division] has been skipped.
Apr 03, 2024 10:12:45 AM com.apicatalog.jsonld.deseralization.JsonLdToRdf build
WARNING: Non well-formed subject [CheckMethodOperator-exists] has been skipped.
Apr 03, 2024 10:12:45 AM com.apicatalog.jsonld.deseralization.JsonLdToRdf build
WARNING: Non well-formed subject [CheckMethodOperator-multiplication] has been skipped.
Apr 03, 2024 10:12:45 AM com.apicatalog.jsonld.deseralization.JsonLdToRdf build
WARNING: Non well-formed subject [CheckMethodOperator-notExists] has been skipped.

hasTarget: "pi" cannot be resolved to a reasonable URL because there's no prefix
```
WARNING: Non well-formed subject [pi] has been skipped.
```

@beachtom None of the subject URLs work. The file defines @base, so I wonder why. I'll try with another tool.

Apr 03, 2024 10:12:45 AM com.apicatalog.jsonld.deseralization.JsonLdToRdf build
WARNING: Non well-formed subject [Government_Decree_on_Accessibility_of_building] has been skipped.
Apr 03, 2024 10:12:45 AM com.apicatalog.jsonld.deseralization.JsonLdToRdf build
WARNING: Non well-formed subject [Government_Decree_on_Accessibility_of_building/1] has been skipped.
(and many more)

jsonld

npm install -g jsonld-cli

This is the same source that runs the JSONLD Playground.

I used it to lint the file and got 79 warnings due to relative URLs in @type, see https://github.com/digitalbazaar/jsonld-cli/issues/29

I had better success converting. After jsonld I run riot in order to format the file for easier reading. I get 4 errors because hasUnit is declared $id but % cannot be converted to a reasonable URL. (I bet QUDT defines a unit for percent with appropriate URL)

jsonld toRdf -q FI2.jsonld | cat prefixes.ttl - | riot -formatted ttl -syntax ttl > FI2-jsonld.ttl
10:38:00 WARN  riot            :: [line: 391, col: 133] Bad IRI: <https://data.accordproject.eu/%> Code: 30/ILLEGAL_PERCENT_ENCODING in PATH: The host component a percent occurred without two following hexadecimal digits.
10:38:01 WARN  riot            :: [line: 738, col: 133] Bad IRI: <https://data.accordproject.eu/%> Code: 30/ILLEGAL_PERCENT_ENCODING in PATH: The host component a percent occurred without two following hexadecimal digits.
10:38:01 WARN  riot            :: [line: 776, col: 133] Bad IRI: <https://data.accordproject.eu/%> Code: 30/ILLEGAL_PERCENT_ENCODING in PATH: The host component a percent occurred without two following hexadecimal digits.
10:38:01 WARN  riot            :: [line: 872, col: 133] Bad IRI: <https://data.accordproject.eu/%> Code: 30/ILLEGAL_PERCENT_ENCODING in PATH: The host component a percent occurred without two following hexadecimal digits.

These URLs are obviously not what is intended:

    aec3po:hasComparator  <https://data.accordproject.eu/CheckMethodComparator-le> ;
    aec3po:hasUnit        <https://data.accordproject.eu/%> ;
    aec3po:hasTarget      <https://data.accordproject.eu/pi> ;

Even the instance URLs are missing the /FI part. The same occurs on https://json-ld.org/playground/:
```
<https://data.accordproject.eu/Government_Decree_on_Accessibility_of_building/2.1.2.4_method>
```
<functions:tan> is treated as an absolute URL with an invalid (unregistered) scheme functions:

I have also sorted FI2-jsonld.ttl by "paragraph" to make it easier to track. Tom, can you check it out and see if it includes all info from JSONLD (especially look for the complex nested structure from #6), and that it doesn't have other problems?

beachtom commented 7 months ago

Hi Vladmir, the TTL is generated by my pipeline - which is in fact just json-ld titanium

https://github.com/filip26/titanium-json-ld

It seems the actual ttl on the github was not up to date with the latest version - can you try again with this version and see if it improved. I will try and improve it also - I did at one point have it working upload to a local graphDB - but something recently seems to have broken it.

VladimirAlexiev commented 7 months ago

@beachtom GraphDB 10.5 (Dec 2023) switched to titanium (actually a fork with improved performance) in order to support JSON-LD 1.1. See https://graphdb.ontotext.com/documentation/10.5/release-notes.html#graphdb-10-5-0.

Proposed solution for the Bad IRI error:

instead of units like %, use PERCENT and resolve them against the https://qudt.org/vocab/unit/ namespace (check out https://qudt.org/vocab/unit/PERCENT).
But this means we need some strict checking that only valid units are used
@EdliraK, @maximelefrancois86: do you agree to use QUDT unit URLs directly? vocabularies/quantity_kinds.ttl proposes some quantity kinds and relates them to QUDT...

@beachtom Can you add a Makefile in each folder to systematically derive various RDF serializations? To be sure what is derived from what, and using which tool.

maximelefrancois86 commented 7 months ago

@VladimirAlexiev you wrote:

The context does not define the expansion of hasComparator values. @maximelefrancois86 this can be done by declaring it @type:@vocab and then declaring the @vocab namespace for it. Or you can enumerate all values:

Is there any action on me pending to update the file https://github.com/Accord-Project/aec3po/blob/main/src/aec3po.yaml ?

beachtom commented 6 months ago

This is now sorted I think

Accord-Project / API-Development

precise correspondence YAML-JSONLD-TTL #7

riot

jsonld