Open kelvinqian00 opened 2 years ago
Per our July 19th, 2022 meeting, we also aren't seeing a ton of value in the SKOSs predicate relationships. I would be curious if anyone has a use case where there is value in classifying these within xAPI Profiles, especially to the point of requiring SKOs relationships.
The section Part Three: Communication and Processing describes requirements for inference logic to be implemented by Profile Servers:
However, these requirements are currently vague and/or impractical.
profile:concepts
,profile:templates
, andprofile:patterns
should be subproperties of the inverse ofskos:inScheme
)"profile:concepts
ANDprofile:templates
ANDprofile:patterns
should be subproperties of the inverse ofskos:inScheme
."profile:concepts
,profile:templates
, andprofile:patterns
being subproperties of the inverse of skos:inScheme" would entail that the inferencer should add (for example) the triple<conceptId> skos:inScheme <profileId>
. Is this the intent of that phrase? If so, it would be clearer to state that explicitly; if not, it would be useful to give a concrete example of the intended inference.A skos:related B -> B skos:related A
* (as well as similar ones forskos:broader
andskos:narrower
) would add inferred triples that are indistinguishable from triples added by the author.A skos:relatedMatch B -> B skos:relatedMatch A
** will affect Concepts in multiple graphs.A skos:definition B -> A skos:note B
*** be implemented?As such, I believe this sentence should be expanded into its own section on inference requirements, with an explicit list of inference rules that MUST be implemented and preferably with some examples.
Entailments from the SKOS specification: * S23:
skos:related
is an instance ofowl:SymmetricProperty
** S44:skos:relatedMatch
is an instance ofowl:SymmetricProperty
*** S17:skos:definition
is a subproperty ofskos:note