- From: Rob Sanderson via GitHub <sysbot+gh@w3.org>
- Date: Mon, 25 Jun 2018 16:39:00 +0000
- To: public-dxwg-wg@w3.org
azaroth42 has just created a new issue for https://github.com/w3c/dxwg: == [profiledesc] role assumes closed world of the document == The profiledesc ontology has a role associated directly with a resource which it does not control. For example: ``` <https://.../dcat-ap-v11> prof:resource <http://data.europa.eu/...c096> . <http://data.europa.eu/...c096> prof:resourceRole roles:Guidance . ``` This role is only true for dcap-ap-v11, and the same resource might have other roles in other contexts. For example a Guidance document for one profile might also include a constraints description for a different profile. Or more likely, a PartConstraints for one profile might be a FullConstraints for another simpler profile. There are various solutions: * Named Graphs. Not supported by many systems, and you only get to use the ace once (a triple can be part of only one named graph). * Reification. Instead of `resource`, have a node between the Profile and the document that has the role associated with it. Compare the Web Annotation model for [SpecificResource](https://www.w3.org/TR/annotation-model/#specific-resources). Much more verbose, but good when the vocabulary of roles is open ended. * Many Relationships. A simpler pattern but harder to extend -- each role is encoded in the predicate between the Profile and the document, eg hasPartConstraints vs hasFullConstraints. Good for implementations when the vocabulary is closed and relatively small. Reification: ``` <profile1> prof:hasResourceWithRole <rr1> . <rr1> prof:hasRole roles:PartConstraint ; prof:forDocument <constraint1>. ``` Relationships: ``` <profile1> prof:hasPartConstraintResource <constraint1> . ``` Please view or discuss this issue at https://github.com/w3c/dxwg/issues/262 using your GitHub account
Received on Monday, 25 June 2018 16:39:04 UTC