uncefact / spec-jsonld

Exposing the UN/CEFACT vocabulary as web semantics
https://service.unece.org/trade/uncefact/vocabulary/uncefact/
13 stars 5 forks source link

website and ontology are not in sync! #193

Closed VladimirAlexiev closed 1 year ago

VladimirAlexiev commented 1 year ago

Related to #45 and #185.

https://vocabulary.uncefact.org/physicalIndicator shows xsd:boolean.

But the ontology (converted to turtle) shows a different range:

uncefact:physicalIndicator
        rdf:type                        rdf:Property ;
        rdfs:comment                    "The indication of whether or not this geographical object can be characterized as physical." ;
        rdfs:label                      "physicalIndicator" ;
        schema:domainIncludes           uncefact:GeographicalObjectCharacteristic ;
        schema:rangeIncludes            xsd:string ;
        uncefact:cefactElementMetadata  cefact:Specified_GeographicalObjectCharacteristic.Physical.Indicator .

Also, the two show different prefix: unece vs uncefact.

This means that the website and ontology are not in sync!!

Needless to say, this is detrimental to the main purpose of UNCEFACT JSONLD: better interoperability.

@nissimsan can you give this issue top priority?

VladimirAlexiev commented 1 year ago

Ok, I've read at https://github.com/uncefact/spec-jsonld/blob/main/docs/CI_CD.md that the right repo for this issue is https://github.com/uncefact/vocabulary-outputs/ And the people are @nissimsan @kshychko @webilhan.

Can you guys diagnose how the discrepancy described above has happened?

VladimirAlexiev commented 1 year ago

Now the ontology is updated:

"@id": "unece:physicalIndicator",
"schema:rangeIncludes": {
        "@id": "xsd:boolean"
      },