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

providerParty property type #139

Closed kshychko closed 1 year ago

kshychko commented 2 years ago

One more issue I discovered running the check for broken links is providerParty property:


            "@id": "unece:providerParty",
            "schema:rangeIncludes": {
                "@id": "unece:TradeParty"
            },
            "@type": [
                "rdf:Property",
                "owl:ObjectProperty"
            ],
            "schema:domainIncludes": [
                {
                    "@id": "unece:Authentication"
                },
                {
                    "@id": "unece:IOTDevice"
                }
            ],
            "rdfs:comment": [
                "The provider party for this monitoring IOT device.",
                "The referenced party providing this document authentication.",
                "The trade party providing this document authentication."
            ],
            "rdfs:label": "providerParty",
            "unece:cefactElementMetadata": [
                {
                    "@id": "cefact:Monitoring_IOTDevice.Provider.Trade_Party",
                    "@type": "unece:AssociationBIE",
                    "unece:cefactUNId": "UN01013489",
                    "unece:cefactBieDomainClass": "cefact:Monitoring_IOTDevice.Details",
                    "unece:cefactBusinessProcess": "Buy-Ship-Pay",
                    "rdfs:comment": "The provider party for this monitoring IOT device.",
                    "unece:domainName": "IOTDevice"
                },
                {
                    "@id": "cefact:Document_Authentication.Provider.Trade_Party",
                    "@type": "unece:AssociationBIE",
                    "unece:cefactUNId": "UN01003526",
                    "unece:cefactBieDomainClass": "cefact:Document_Authentication.Details",
                    "unece:cefactBusinessProcess": "In All Contexts",
                    "rdfs:comment": "The trade party providing this document authentication.",
                    "unece:domainName": "Authentication"
                },
                {
                    "@id": "cefact:Document_Authentication.Provider.Referenced_Party",
                    "@type": "unece:AssociationBIE",
                    "unece:cefactUNId": "UN01002642",
                    "unece:cefactBieDomainClass": "cefact:Document_Authentication.Details",
                    "unece:cefactBusinessProcess": "In All Contexts",
                    "rdfs:comment": "The referenced party providing this document authentication.",
                    "unece:domainName": "Authentication"
                }
            ]
        }

We have ASBIE cefact:Document_Authentication.Provider.Referenced_Party but we don't have Referenced Party BBIE defined And because there is no additional attributes to distinguish it from cefact:Document_Authentication.Provider.Trade_Party we get one RDF property for two different ASBIEs There are could be more cases like this, need to run additional checks

nissimsan commented 2 years ago

Approach: