Developing Extensions: Difference Between Using schema: Prefix and skos:exactMatch? #3498
Unanswered
MaxwellDAnderson
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello!
I am trying to develop a modest extension that would be useful for users, consumers, and publishers, of information related to the field of law. In doing this, Protégé has been my editor of choice.
I have added
schema:
as a prefix and have been using said prefix in creating subclasses ofschema:CreativeWork
and others. But as I was reviewing the GS1 external extension ontology file, I noticed that, for some of their classes, they useskos:exactMatch
to make an association. For instance, GS1'sBrand
class is annotated as askos:exactMatch
for http://schema.org/Brand. However, GS1 uses theschema:
prefix for other classes, such asschema:Product
.As far as I can tell, the only difference between these two usages is whether the class is used at the same hierarchy level.
Specifically, Schema.org's
Brand
class is nested as a subclass ofIntangible
, which is itself a subclass ofThing
. GS1, however, only nestsBrand
as a subclass ofThing
and does not have anIntangible
subclass ofThing
.Conversely, GS1's
schema:Product
class is nested the same as Schema.org'sProduct
class, i.e., as a subclass ofThing
.If my proposal turns into a proposed external extension, am I correct that:
skos:exactMatch
is appropriate when a vocabulary utilizes a Schema.org class or property, but utilizes it at a different level of hierarchy than Schema.org; andThe
schema:
prefix is appropriate when a vocabulary utilizes a Schema.org class or property at the same level of hierarchy as Schema.org?If I am not correct, then what is the difference between using the
schema:
prefix and theskos:exactMatch
annotation?Beta Was this translation helpful? Give feedback.
All reactions