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

• Action items from time taken and corresponding issues resolved
  • RESOLVED - Common Properties #15 - dcterms
    • Moved to dcterms
  • RESOLVED - OSLC Defined Resources # 26 - Value-types, node ID issue
    • Now have value-types: Resource and Local Resource
    • Now have representations: Reference and Inline
    • Now have range column
    • Now have standard table format in Core spec
  • RESOLVED - Common Properties #17 - drop oslc:instanceShape
    • We will keep oslc:instanceShape
  • RESOLVED - OSLC Defined Resources # 28 - drop notion of extended properties
    • We will keep extended properties

• 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
  • Resource Shapes #24 - drop oslc:describes
    • Only use case comes from reporting, what is it?
  • Resource Shapes #25 - how to offer / extend resource shapes?
    • Proposal: expect implementations to provide shapes as required by domain specs
  • Query Capability #24 - need a query resource definition
    • Couldn't reach consensus on this without Arthur

• 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
  • Removed Common Link Properties because it appears that we may not need them
    • None are really common
    • Having them encourages back-links

Minutes

Possible Attendees:

• NickCrossley
• JimConallen
• PaulMcMahan
• SteveSpeicher

Reviewed resolved items

Discussed how resource shapes can override OSLC definitions

• AI (Dave): draft proposal for how implementation can offer shapes, rules for changing/adding custom properties

Discussed fact that extended properties not in OSLC Core spec table

• Dave: we expect that very few properties will be extended, so we did not want to devote a column to them. They can be specified elsewhere.

Discussed programmatic ID of creation factory

• Dave: three ways to specify how creation factory is used: type, usage and shape, do we need guidelines for how they should be used
• Jim: have we specified anything that uses these attributes, in the CM2 spec for example?
• Steve: not yet

AI (Dave): to follow-up with Tack on oslc:describes

AI (Dave): follow-up with Arthur on query resource definition

Discussed status of Link Guidance. It has been trimmed down a bit, now covers three ways to express relationships: link, anchor and external anchor. There is some contention over how to express link attributes and Jim Conallen is offering a more complex form which he claims has better query characteristics.