Contents

• Core 2.0 Finalization issues
• TrackedResourceSet 2.0 Issues
• Partial Update 2.0 Issues

Core 2.0 Finalization issues

This section tracks issues during and after finalization, some of which have been or will be reflected in changes above.

This section captures the issues raised against OslcCoreSpecification

These are the issues raised during the development of the OSLC Core spec up to and after finalization time.

If there is a #num next to the status, this represents the issue # from the previous wiki page. To see the list of issues that occurred during the convergence phase see OslcCoreV2ConvergenceIssues

Note: dates below use US format (mm/dd/yyyy)

Here’s what the states mean:

• OPEN - indicates that we have no response for the issue yet
• RESOLVED - indicates that we have a response that we believe resolves the issue
• CLOSED - issue has been resolved and the resolution has been reviewed by the WG
• DEFERRED - indicates that issue will be addressed in Core Guidance v1.0 during the month after the Core Specification is final.
• TABLED - indicates that issue will be reconsidered at some later but unspecified date

See CLOSED items above with FIXED subheadings.

Issues:

(only OPEN or RESOLVED issues migrated here 08/23/2012. For CLOSED or DEFERRED issues, see OslcCoreV2Issues )

1. CLOSED #30 anchor duplication (JohnArwe 11/09/2011)
   • Response Fix by using Wiki override option to add unique anchors (SteveSpeicher 11/16/2011)
   • Updates made. Since the syntax was hard to find, it’s in the TOC macro documentation page (JohnArwe 2013-05-07)
2. OPEN #31 Format encoding/charset defaults (FrankBudinsky 11/22/2011)
   • Response TBD
3. OPEN #33 XHTML vs simple text in OSLC Core’s common properties (JohnArwe 11/15/2011)
   • Response TBD
4. OPEN #34 Representing the order of triples in a query response that uses oslc.orderBy (ArthurRyman 12/08/2011)
   • Response Arthur included a proposal in the same note
5. CLOSED #35 Buglet in Core 2.0 - non-exemplary(?) use of Change Request (JohnArwe 12/30/2011)
   • Response No objections noted to the proposal, changes live (JohnArwe 2013-05-13)
6. CLOSED #36 Ambiguity in Resource Shape definition + consequent questions (JohnArwe 12/30/2011)
   • Response Discussed at Jan 11 meeting. Proposal sent to list and response led to unclear statement if resolved.
   • No objections noted to the proposal referring back to the original response, changes live (JohnArwe 2013-05-13)
7. OPEN #38 Suggested improvements to representations samples - (John Arwe 2/15/2012)
   • Response Proposal to defer to 3.0 (JohnArwe 2013-05-13)
8. RESOLVED #40 oslc:modifiedBy proposal - (ArthurRyman 3/14/2012)
   • Response Agree with adding - need to propose text, ask DCMI and clarify dcterms:contributor guidance
9. RESOLVED #41 Multi-typed resource scenarios and rdf:type/dcterms:type - (MichaelFiedler 3/14/2012)
   • Response Discussed at April 04 meeting. The workgroup concluded that this issue should be handled by adding additional features to an abbreviated RDF/XML writer, not by changing the specification. Artificially introducing additional type predicates beyond rdf:type is not desirable.
10. OPEN #42 unknown or unsupported property handling - (SamPadgett 3/21/2012)
    • Response TBD

11. CLOSED #43 Read-only and friends - (JohnArwe 4/13/2012)

    • Response TBD
    • Drafts discussed at May 30 meeting
      • wording for items 1, 3, 4, approved as-is; item 7 approved, either as-is or substituting “one or more” for “at least one”; changes requested for items 5, 8, 9.
      • New item added to define Name as the fragment portion of the property’s URI instead of calling it a Qname (qualified name), which is a tuple; also search for other occurrences in Core.
      • Separate issue (44) added to correct all occurrences of open-service.net/ns (missing final s on serviceS) on the website.
    • Drafts for Range: 8+9, Read-only: 2, Occurs: 5 discussed at June 13 meeting
    • Drafts for Range: 8+9, Read-only: 2, Occurs: 5 discussed at June 27 meeting
    • Occurs: 5 fixed, Read-only: 2 fixed
    • Drafts for July 11 meeting: 43-8+9: Range, 43-6: Specs get 1:* value types, shapes get 0:1, 43-11: Range allows 1:* types, valueShape 0:1
    • Range: 8+9 Core fixed, Core App A fixed, Core App C fixed
    • Value-type: 6 Core App A fixed per July 11 meeting, and Issue 46 created for plain literals in resource shapes per discussion in the same meeting.
    • Confirmed in live specs that all approved changes have been made, and all issues raised either had changes approved or were spun off to new issues (JohnArwe 2013-05-07)

12. OPEN #44 correct all occurrences of open-service.net/ns (missing final s on serviceS) on the website - (JohnArwe 2012-05-30)

    • Response SteveSpeicher has done a search/replace through wiki pages, need to do attached examples
13. OPEN #45 the usage of QName in this context is not valid. It should really state that we use hash URIs and this is the fragment segment of the URI. Need to promote/clarify OSLCCoreURINamingGuidance - (ArthurRyman 2012-06-13)
    • Response TBD
14. OPEN #46 Resource shapes provide no way to represent an RDF Plain Literal, only typed literals - (JohnArwe for ArthurRyman, 2012-07-11)
    • Response Proposal to defer to 3.0 (JohnArwe 2013-05-13)
15. CLOSED #47 Add oslc:usage to oslc:Service - (JohnArwe for Automation WG), 2012-07-25)
    • Response Accepted per July 25 meeting
    • Updates made, and fixed 20120725 meeting link in the response (JohnArwe 2013-05-07)
16. CLOSED Handling of unrecognized content (JimConnalen, 2012-09-27)
    • Response Proposed changes accepted per Meeting20120919
    • Changed made in revision 72 http://open-services.net/bin/view/Main/OslcCoreSpecification?rev=72
17. RESOLVED Handling of long URIs JohnArwe 2012-09-06)
    • Response ToDo on JohnArwe to provide writeup on handling of form-encoded POST to mean query instead of GET. Meeting20121017
18. OPEN Proposal for new property oslc:shortId - (ArthurRyman 2013-02-14)
    • Response TBD

TrackedResourceSet 2.0 Issues

These are the issues against Tracked Resource Set 2.0

1. CLOSED trs:changes shouldn’t be plural - Vivek Garg 2013-03-26
   • Response Propose to change to trs:change (drop the ‘s’) – SteveSpeicher
   • Change made revision 2461 – SteveSpeicher 2013-04-03
2. OPEN TRS truncation of change log - Joe Ross 2013-05-02
   • Response Proposal: Defer issue stating we’d like more experience with Joe’s proposed approach - Steve Speicher 2013-05-22
3. OPEN TRS spec cutoffEvent property - Joe Ross 2013-05-02
   • Response Proposal: Add Jim’s description - Jim des Rivieres 2013-05-15
4. OPEN Misc comments - John Arwe 2013-05-14
   • Response A) Proposed: Resource definitions - Steve Speicher 2013-05-20
   • Response B) Proposed: Other misc comments - Steve Speicher 2013-05-20

Partial Update 2.0 Issues

These are the issues against http:open services.netwikicoreOSLC Core Partial Update

1. OPEN Concern over matching blank nodes - don’t use ids and use variables, possibly SPARQL update subset - ArthurRyman 2013-03-13
   • Response Clarify that bnode labels/ids are not part of the mapping, just in the example – SteveSpeicher
2. OPEN Usage of predicate names for insert/delete instead of graph names, streaming/order and more - AndySeaborne 2013-03-13
   • Response working on response - SteveSpeicher

Category:Supporting Documents