ORG LC comments
From Government Linked Data (GLD) Working Group Wiki
m |
(→prov:wasDerivedFrom) |
||
| Line 3: | Line 3: | ||
Comments and draft responses for ORG Last Call ending 2012-11-25 | Comments and draft responses for ORG Last Call ending 2012-11-25 | ||
| - | === prov:wasDerivedFrom === | + | === prov:wasDerivedFrom [Done - pending confirmation] === |
From PROV feedback [http://lists.w3.org/Archives/Public/public-gld-comments/2012Nov/0003.html] | From PROV feedback [http://lists.w3.org/Archives/Public/public-gld-comments/2012Nov/0003.html] | ||
Suggestion that prov:wasDerivedFrom should be explicitly or implicitly asserted to link a the org:resultedFrom organization to the org:originalOrganization | Suggestion that prov:wasDerivedFrom should be explicitly or implicitly asserted to link a the org:resultedFrom organization to the org:originalOrganization | ||
| + | |||
| + | This has been addressed by including a property chain axiom, as suggested in the feedback and providing an example and explanation of this relationship in the informative section "Organization History". | ||
=== Check PROV semantic constraints === | === Check PROV semantic constraints === | ||
Revision as of 15:21, 16 February 2013
Last Call Comments Disposition: ORG
Comments and draft responses for ORG Last Call ending 2012-11-25
prov:wasDerivedFrom [Done - pending confirmation]
From PROV feedback [1]
Suggestion that prov:wasDerivedFrom should be explicitly or implicitly asserted to link a the org:resultedFrom organization to the org:originalOrganization
This has been addressed by including a property chain axiom, as suggested in the feedback and providing an example and explanation of this relationship in the informative section "Organization History".
Check PROV semantic constraints
From PROV feedback [2]
There are additional semantic constraints on use of PROV that should be checked before proceeding with its use in ORG.
Consider use of "invalidation"
From PROV feedback [3]
Suggestion to use PROV invalidation vocabulary to state when a changed organization ceases to exist.
Request for more complete illustrative diagram
The non-normative pictorial representation of the vocabulary is not complete, and clearly stated as such in the LC document.
Comment from João Paulo requesting that the relation between org:Organization and foaf:Agent and between org:Post and org:Organization should be made explicit. [4]
Relationship to foaf:Organization [Done]
Off list comment from Dan Brickley.
The ORG vocabulary itself states that org:Organization is owl:equivalentClass foaf:Organization but this isn't reflected in the HTML description.
Recorded as Issue-42
This edit has been made to the current editor's draft and the issue can be marked as closed.
Align treatment of registered addresses with RegOrg [Proposed]
Comment from Richard Cyganiak recorded as Issue-45
Proposed that the range constraint on org:siteAddress be removed and vCard simply referenced as an example.
This change has been made to the current editor's draft.
Domain/range of org:reportsTo [Done - pending confirmation]
Comment from João Paulo.
State the domain and range of org:reportsTo as being foaf:Agent as opposed to unionOf(foaf:Agent, org:Post) and add clarifying text pointing out that someone can reportTo an org:Post. This is not a change in semantics, just a clarification.
Recorded as Issue-48
Edit has been made, João Paulo to confirm acceptance or otherwise.
org:reportsTo is not acyclic [Done]
Comment from João Paulo.
There is currently a comment in informative text mentioning reportsTo as acyclic that should be removed or clarified. This would be a minor change, not affecting semantics.
Recorded as Issue-49
The offending informative comment has been removed and this issue can now be closed.
Should org:Organization be sub-class of foaf:Agent
Comment from João Paulo.
Recorded as Issue-50
(consider birthday property as a test case)
Should org:Post be a sub class of org:Organzation
Comment from João Paulo.
Recorded as Issue-51
