OSLC Core Meeting June 30, 2010

Meeting logistics

See the OslcCoreMeetings for more information, more dial-in numbers and on-line meeting information.

• Conference Access
  • Toll free: 1-866-423-8350
  • Toll: 1-719-387-8273
• Participant passcode: 558663

Agenda

• Resolved during past week
  • Resource Shapes #24 - drop oslc:describes
    • Resolution: keep it in the spec
  • Query Capability #24 - need a query resource definition
    • Resolution: don't need it because query syntax implies shape of query response
  • Resource Shapes #25 - how to offer / extend resource shapes?
    • Resolution: added following text to Common Properties section on resource shapes:
      • OSLC implementations that provide Resource Shapes representing resources defined by OSLC specifications are expected to provide the very same information provided in the specifications without changing or removing any of the Properties specified. Resource Shapes MAY include new implementation specific properties as long as such "custom" properties are defined in non-OSLC namespaces (i.e. not rooted at http://open-services.net).

• Status of open issues
  • Creation Resources #5 - programmatic id of create, query
    • Steve's proposal and thread
      • http://open-services.net/pipermail/oslc-core_open-services.net/2010-June/000313.html

• Status of Link Guidance - http://open-services.net/bin/view/Main/OSLCCoreLinksDRAFT
  • Link is just a URI reference: unidirectional and may be untyped
  • Simplified down to three ways to express relationships: Link, Anchor and External Anchor
  • Still a rough draft: will have new revision ready by the end of this week with Jim Conallen's form of Anchor
  • ISSUE: switch core to using only rdf:RDF root?

• Status of Partial Update Guidance http://open-services.net/bin/edit/Main/OSLCCorePartialUpdateDRAFT
  • Have replaced my proposed PATCH format with subset of SPARQL update
  • Still a rough draft: will have new revision ready by the end of this week

Minutes

Attendees:

• DaveJohnson
• NickCrossley
• JimConallen
• PaulMcMahan
• SteveSpeicher
• ArthurRyman
• TackTong
• RobertElves
• MikeLoeffler

We reviewed the issues that have been closed.

NickCrossley commented on "Resource Shapes #25 - how to offer / extend resource shapes?" and pointed out that allowing NO CHANGE was perhaps too restrictive and that better language might be NO INCOMPATIBLE CHANGE.

DaveJohnson AI: rewrite to use word compatible

Discussion of Creation Resources #5: no objections or other negative feedback has been received.

SteveSpeicher AI: make proposed Create/Query identification changes.

Discussed Partial Update Guidance, briefly.

Discussed Link Guidance and need to use rdf:RDF as root element to enable "annotated links" AKA anchors. DaveJohnson proposed that we move to using rdf:RDF as the root element for all OSLC RDF/XML representations because we don't want one form for resources with anchors and other for resources without. ArthurRyman did not object to moving to rdf:RDF, but recommended deleting the RDF/XML representation rules and instead ask folks to use an RDF parser. In the discussion that followed consensus seemed to be that the rules ensure consistency and make like easier for those using XML tools -- and ought to stay.

DaveJohnson AI: get rdf:RDF in to Core spec as option now and as only option as soon as possible.