OSLC Core Meeting July 14, 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
Recent changes to OSLC Core spec
- Change to RDF/XML representation guidelines:
An OSLC service MUST provide RDF/XML representations of all OSLC Defined Resources. For each resource, an OSLC service may offer either an abbreviated RDF/XML subset that is XML-tool friendly, a full RDF/XML or both forms according to these rules:
- When an OSLC client asks for RDF/XML by using content-negotiation to request content-type application/rdf+xml, then the client MUST accept any valid RDF/XML and the server MAY return either full RDF-XML or Abbreviated RDF/XML as defined below.
- When an OSLC client asks for XML by using content-negotiation to request content-type application/xml, then the server MUST return XML and MAY return abbreviated RDF/XML as defined below.
- When an OSLC client requests application/xml and the server only provides full RDF/XML then the server SHOULD return an HTTP status of 406 (Not Acceptable).
(also added text about configuring Jena for abbreviated RDF/XML and a how to generate full RDF/XML, i.e. see the spec)
Finalization plans
- Next week on July 21 we:
- Declare the OSLC Core spec to be in finalization
- Remove the word DRAFT from the spec and URLs
- We allow only corrections and clarifications to the spec
- We encourage our currently converging specs to finalize
- We wait to declare the spec "final" when implementations are compete
Topic revision: r1 - 13 Jul 2010 - 21:15:35 -
DaveJohnson