The current OSLC Core 3.0 specification requires specific RDF serialization formats based on similar requirements in LDP 1.0. This creates a compatibility conflict with OSLC 2.0 which requires RDF/XML and is overly restrictive. This proposal modifies Core to simply say servers must support some RDF serialization format, and which ones they should support and why (in order to provide interoperability with LDP and/or OSLC 2.0).
In OSLC Core Overview (http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/oslc-core-v3.0-part1-overview.html)
Change:
4.4.1 OSLC Services must provide and accept text/turtle and application/ld+json representations for each OSLC resource.
4.4.2 OSLC Services should provide and accept RDF/XML representations for each OSLC resource.
4.4.3 OSLC Services may provide and accept existing standard or emerging standard formats such as XML, HTML, and the Atom Syndication Format.
to:
4.4.1 OSLC Services MUST support some RDF resource serialization format, and SHOULD support many serialization formats through content negotiation.
4.4.2 OSLC Services SHOULD provide and accept text/turtle and application/ld+json representations for each OSLC resource for compatibility with LDP 1.0.
4.4.3 OSLC Services SHOULD provide and accept RDF/XML representations for each OSLC resource for compatibility with OSLC 2.0
4.4.4 OSLC Services MAY provide and accept existing standard or emerging standard formats such as RDF/XML-ABBREV, XML, HTML, and the Atom Syndication Format. |
