OSLC Core Meeting June 16, 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

• Review of open issues and some proposed resolutions
• If we have time: brief overview of Link Guidance, which is still being rewritten

Open issues

• Possibly resolved issues
  • Common Properties #15 - dcterms
    • Specification versioning story should prevent any breakage
  • OSLC Defined Resources # 26 - Value-types, node ID issue
    • Made rdf:nodeID correction in RDF/XML and JSON reps
    • re: change to RDF terminology. Do we have a proposal for new terms?
    • re: requiring RDF parser. Not sure I understand, XML parser is not good enough?

• Contentious new issues
  • Common Properties #17 - drop oslc:instanceShape
    • This enables update via resource shape information
    • We're OK with shapes for create and query, but worried about update
  • Resource Shapes #25 - drop oslc:describes
    • This types a shape to a type
    • Worried that this takes us down a path to rigid schemas for types
  • OSLC Defined Resources # 28 - drop notion of extended properties
    • We have resource paging, do we really need this any more?

• New 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
  • Resource Shapes #25 - how to offer / extend resource shapes?
    • Proposal: we host "base shapes" at open-services.net/shapes
    • Proposal: implementation can override these to add custom properties

• Old issues
  • Query Capability #24 - need a query resource definition
    • Couldn't reach consensus on this without Arthur

Minutes

Attendees:

• NickCrossley
• JimConallen
• PaulMcMahan
• ScottBosworth
• ArthurRyman
• SteveSpeicher

Decided to use dcterms instead of dc, urged spec leads to talk to implementors to make them aware of this late-breaking change

• AI: Spec leads to make implementation folks aware of dcterms change

Had a long discussion about RDF terminology and replacing value types Resource and Local Resource with URI reference and Blank Node reference. Also, move Inline Resource and Local Inline Resource from the value-type column and putting them into a representation column. Also discussed need for tabular form of property definitions defined in and used by the Core spec.

• AI: Dave to propose change to value-types
• AI: Dave to propose table format for defining properties
• AI: Dave to use table format in Core spec

Discussed simplifications of resource shape related things and extended properties. Consensus seems to be that:

1. re: oslc:instanceShape - useful in update but update is challenging and perhaps we need guidance that says conforming to shape does not guarantee successful update.
2. re: oslc:describes - raised the issue and nobody object to removing this property, but Arthur was not present at that time
3. re: extended properties - we still need extended properties, but there are still concerns that it makes things more complicated for clients. Also, that inlining large binary resources as property values make not be the preferred approach.

• AI: Steve to follow up with Rational folks on update concerns

The extended properties discussion extended until the very end of the meeting and we did not get to our other items.

• AI: Dave to raise remaining items on mailing list