Warning:
This wiki has been archived and is now read-only.
ORG comments
Contents
Comments Disposition: ORG
This page consolidates comments from Last Call and CR stages.
CR Comments
Only one comment requiring disposition was raised at CR stage.
Commenter | Message | Summary | Status | GLD response | Acknowledgement |
---|---|---|---|---|---|
Dominique Hazael-Massieux | [1] | Textual description of org:hasMember and org:memberOf in the reference was unclear in talking of members as people, whereas they can be agents (and thus other organizations). | This is clear in the main text and the declared domains and ranges, clarified the text as a small editorial change. | [2] | [3] |
All other comments were implementation reports including information on planned future usage and are summarized on ORG_Implementations none of these raised issues with the ontology.
The use of OWL Time as a normative reference (for representation of time intervals) was marked At Risk and we sought feedback. One non-WG implementation report was received responding to this request [4] who asked that OWL Time be retained. We are thus seeking to proceed with this reference retained.
Last Call comments
Comments and draft responses for ORG Last Call ending 2012-11-25 then later extended to 2013-04-08 due to administrative omission in notifying w3c-chairs.
Commenter | Message/Issue | Summary | Status | GLD response | Acknowledgement/Resolution |
---|---|---|---|---|---|
Leigh Dodds | [5] | Endorsement and example of usage. | Acknowledged. | [6] | N/A |
Bill Roberts | [7] | Endorsement. Side comment on complexities of vCard. | Responded that the WG has relaxed vCard use to recommendation rather than requirement. | [8] | [9] |
PROV working group | [10] tracked as ISSUE-55 | Suggestion that prov:wasDerivedFrom should be explicitly or implicitly asserted to link a org:resultedFrom organization to the org:originalOrganization | This has been addressed by including a property chain axiom and providing an example and explanation of this relationship in the informative section "Organization History". This would not invalidate previous implementations is not seen as requiring a new Last Call. | [11] | [12] |
PROV working group | [13] tracked as ISSUE-56 | There are additional semantic constraints on use of PROV that should be checked before proceeding with its use in ORG. | We have examined these constraints and see no implication for the use of ORG terms themselves. An application which combines ORG with use of PROV-O terms (e.g. for the time of occurrence of event) should take the PROV-CONSTRAINTS into account. We have added a comment to this effect in the informative section on "Organizational History". | [14] | [15] |
PROV working group | [16] tracked as ISSUE-57 | Suggestion to use PROV invalidation vocabulary to state when a changed organization ceases to exist. | An application of ORG is indeed free to use further terms from the PROV vocabulary such as those on invalidation. This is already possible with no change to ORG being required. | [17] | [18] |
Dan Brickley | Off list tracked as ISSUE-42 | The ORG vocabulary itself states that org:Organization is owl:equivalentClass foaf:Organization but this isn't reflected in the HTML description. | Corrected missing lines in the HTML description | Acknowledged | Acknowledged |
Richard Cyganiak (GLD member) | Raised and track as ISSUE-45 | Align treatment of registered addresses between Org and RegOrg | Removed range constraint on org:siteAddress leaving it open but recommending vCard. Does not invalidate existing usage. | [19] | [20] and confirmed at Telecon 2013-02028 |
João Paulo (GLD member) | Raised and tracked as ISSUE-48 | State the domain and range of org:reportsTo as being foaf:Agent as opposed to unionOf(foaf:Agent, org:Post) | Invalidated by resolution of ISSUE-51 | N/A | |
João Paulo (GLD member) | Raised and tracked as ISSUE-49 | Informative text incorrectly states that reportsTo is Acyclic | Editorial change made. | [21] | Closed at Telecon 2013-02021 |
João Paulo (GLD member) | [22] tracked as ISSUE-50 | Is it valid that org:Organization is sub-class of foaf:Agent. | WG agreed to retain current relationship with foaf, no change. | [23] | Closed at Telecon 2013-02021 |
João Paulo (GLD member) | Raised and tracked as ISSUE-51 | Is it correct for org:Post to be a sub class of org:Organization | Removed constraint requiring this and added editorial comment explaining that entities can still be both org:Post and org:Organization. This change does not invalidate previous implementations. | [24] | Closed at Telecon 2013-02021 |
Renato Iannella (post Last Call) | [25] [26] | 1. Move vcard to informative instead of normative.
2. Remove vcard:VCard grey box from diagram. 3. Include mapping ORG terms to new vcard terms. |
Editorial corrections for (1) & (2). Recommended that (3) be done from vcard and then once new vcard is stable add the mapping into ORG. | [27] | [28] |
LC Summary
We have had three external comments. Two simply endorsing it, one pointing out an editorial omission now fixed.
We had valuable feedback from the PROV working group which has been addressed and acknowledged as acceptable.
In addition WG members raised some issues post-Last Call but not on the comments list. The resulting issues have all been closed as tracked above.
Some small changes were made to the ontology in response to these issues. However, they just involved the relaxation of two constraints (range of org:siteAddress, sub class restriction on org:Post) and the addition of one property call axiom (to enable deduction of prov:wasDerivedFrom). These are not seen as invalidating implementations of Last Call and so do not require a further Last Call.
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. [29] [30]
João Paulo's improved digram has been incorporated into the document as a CR stage editorial change.