OSLC Core Meeting September 15, 2010

Last week's meeting

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 changes to Link Guidance OSLCCoreLinksDRAFT
• Review changes to Representation Guidance OSLCCoreSpecAppendixRepresentations

Things we did not get to last week:

• Discuss how to finalize Link Guidance
  • Assign it a date or a version number?
  • Mark it as FINAL or as "in finalization"?
  • Lock it down so only 2-3 people can edit?

• Discuss possible next topics for workgroup
  • Partial Update and possible collaboration with W3C? SPARQL Protocol Working Group
  • Standardization of JSON format, e.g. for application/rdf+json and possible collaboration with existing Talis effort
  • Spec "backlog"
    • Attachments
    • Eventing
    • Baselining
    • Hierarchical URLs and "staging" URLs

• Implementation feedback?

Minutes

Attendees and notes from the meeting

Attendees

• ScottBosworth
• NickCrossley
• PaulMacMahan?
• MikeLoeffler
• JimConallen
• SteveSpeicher

Topics discussed

Reviewed changes to link and JSON representation guidance

Action items:

- Dave to fix missing commas in subscribesTo - DONE

- Dave to make examples 2, 3 and 4 semantically the same - DONE

- Dave to add outer RDF context to example 1 - DONE

- Dave to change JSON guidance to state that properties that can be multi-valued are always represented as JSON arrays - DONE

Agreed that Link Guidance should be finalized

Discussed how to finalize Link Guidance

Action items:

- Dave to declare guidance as final, pending changes above

- Dave to move Link Guidance to new URL, remove word DRAFT from title and assign it a release date

- Scott to lock down link guidance document so that only Dave, Steve and Scott can change

Discussed possible next topics for workgroup

Additional items not on above list:

- Adoption activities: test suites, reference implementation

- Content for namespace URIs

- Seed list approach to enable distributed search

- Guidance for multi-typed resources

Action items:

- Dave to write list of next topics, each with explanation, and circulate it amongst workgroups and inside IBM

Discussed criterial for making OSLC Core spec FINAL

Agreed that having three final domain specs is a good criteria