OSLC Core Meeting March 4, 2010

Meeting logistics

See the OslcCoreMeetings for telecon number, passcode and online meeting info.

Agenda

• Status
• Comments on spec so far
• The collections issue
• How you can help
• Other issues?
• Quick review of spec concepts (if there is time)

Meeting Minutes

• DaveJohnson
• NickCrossley
• TackTong
• SteveSpeicher
• ScottBosworth
• ArthurRyman
• PaulMcMahan
• Robert Elves

Meeting Minutes

DaveJohnson: Spec lead status

• With Scott's help I now have spec on the wiki
• Guidance on Modeling Links & Partial Update are separate pages
• I've been working to refine the spec language, in particular:
  • Way we describe resources, properties, nesting
  • Way we describe queries
  • Made stab at JSON representation (and got it wrong)
• Met with Tack Tong Aligned Resource Shapes section with Tack's work, need to add examples
• Got excellent comments from Ian Green and Arthur Ryman

DaveJohnson: Comments on spec so far

• Add comments here: http://open-services.net/bin/view/Main/OslcCoreV1Issues
• Ian Green sent useful comments via email
  • better terminology, use some RDF ideas
  • need to spec XML namespaces
  • need to explain idempotence, transactions/changes?
  • should relative URLs be allowed in representations
  • should XML allow xml:base?
  • need guidance of how existing 1.0 specs can migrate
  • worried that Resource Shape == brittle/inflexible, do we want it in core?
  • queries should support POST - need to define String, URI and may need XML Literal
  • not all POSTs need return a Location
  • need to state that ordering is insignificant in representations
  • do we need one required authentication mechanism
  • partial update by command: what are the motivations?
• Arthur Ryman made these comments on the mailing list
  • Need for oslc.properties on resources
  • Need to spec type URI / namespaces
  • Need to spec notion of a Resource Type more clearly
  • rdf:about not a property

DaveJohnson: The Collections Issue - settled?

• • We've decided to use Creation and Query resources instead of AtomPub? -style Collection Resources
  • And to use multi-valued properties instead of Link Collection Resources
  • That's why we are trying to avoid use of the word "collection" because it means AtomPub? collection to some
  • We allow a service to have multiple query resources, each can return subset
  • And multiple creation resources, each can be for a different type of resource
  • The only place we really have anything like a "collection resource" like thing is in query results

• • How folks can help - Review spec carefully and critically
  • Pick a section that needs love, volunteer - Steve S volunteered for Service Resource - Edit the Core spec directly, I'll pick up the pieces

DaveJohnson then reviewed these parts of the spec

• How an OSLC Defined Resource is defined
• In-Line Resource
• Link Resource
• Blog Management example

ArthurRyman: The RDF/XML is wrong, e.g. in , there should be a element wrapping the property values.

ArthurRyman: The query resource representation should be when query is against and entire service, and when query is against some subset of all resources determined by a membership property.

ArthurRyman: The principles of REST design say that resources should not be verbs like get or query or create, but nouns. The notion of an AtomPub? -style collection is useful, a place where you post items and then you can get back items of that same type.