[OASIS Issue Tracker] (OSLCCORE-142) OSLC Core 3.0 should not mandate any particular RDF serialization format

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OSLCCORE-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=68506#comment-68506 ] 

Andrii Berezovskyi commented on OSLCCORE-142:
---------------------------------------------

Suggestion for the normative reference https://www.w3.org/TR/rdf11-concepts/#rdf-documents

> OSLC Core 3.0 should not mandate any particular RDF serialization format
> ------------------------------------------------------------------------
>
>                 Key: OSLCCORE-142
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-142
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>          Components: Core
>            Reporter: James Amsden
>            Assignee: James Amsden
>
> The actual RDF serialization format is not something that OSLC should even need to address. OSLC should only specify that the resources are represented as any standard RDF format. The reason is that no OSLC client should ever depend on a specific resource serialization representation, and they should utilize RDF parsers that support any standard representation. Otherwise interoperability suffers. 
> Now unfortunately this is not the case. Some tools rely on RDF/XML with inlined resources, even going so far as to expect the results to be in RDF/XML-ABBREV, something that isn't even a standard. These clients may use XPath or other lexical mechanisms to "parse" these RDF/XML files for their convenience, and to avoid using RDF parsers. So we have to deal with this.
> For OSLC, interoperability with 2.0 clients and servers is more important than whether RDF/XML, Turtle or JSON-LD is the serialization format. Since we know there are implementations that are limited to RDF/XML, then we should continue to support that in OSLC 3.0 and the domain specifications. 
> OSLC Core 3.0, and the OSLC domain specifications change all references to specific RDF serialization formats to SHOULD, and document in the clause why. Clients and servers SHOULD support Turtle and JSON-LD because they are simpler, more readable representations mandated by LDP. Clients and Servers SHOULD support RDF/XML because it is required by OSLC 2.0 and there are many existing clients and servers you might want to integrate with.
> Now what the servers provide is not over-specified and is left to what they need to provide in their broader execution environment.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)