RDF Support for JAX-RS

[glassfishrobot]

The Semantic Web is gaining momentum, as the possiblity to access all kinds of information using a single technology opens new types of use cases.

One of the accepted standards of The Semantic Web clearly is the RDF data format.

So a future release of the JAX-RS specification should come with mandatory support for automatic RDF marshalling / unnmarshalling.

The most easy way for the application author would be to just set the RDF format using the existing MIME annotations, like @Produces / @Consumes.

Environment

Operating System: All Platform: All

Affected Versions

[2.0]

[glassfishrobot]

• Issue Imported From: https://github.com/jax-rs/api/issues/30
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @glassfishrobot

[glassfishrobot]

@glassfishrobot Commented Reported by mkarg

[glassfishrobot]

@glassfishrobot Commented sandoz said: I am not sure JAX-RS should get into the business of defining data format mappings to/from Java. My concern is specifications of such mappings can be complex and take a lot of time to define, thus separate JSRs may be appropriate.

While RDF is by definition URI centric i do not see RDF representations being fundamentally different to other hypermedia representations, such as XML or JSON when used appropriately. Do you agree?

How about the following instead. JAX-RS should define good hypermedia support what ever the representation and associated Java library. RDF and associated Java libraries can be input as use-cases.

Do you have any suggestions for Java libraries that can produce/consume RDF?

[glassfishrobot]

@glassfishrobot Commented mkarg said: I need to disagree in part. The web would never have become popular if there wouldn't have been HTML as the default human-readable data format. Without hat, people would send Microsoft docx file and others could not read it. Same is with RDF: It is THE definitive machine-readable data format for the SEMANTIC web, just like XML and JSON are standard machine-readable data formats for the NON-SEMANTIC web. JAX-RS is the standard for RESTful APIs, and what JAX-RS is missing is good support for Hypermedia. But what actually is it missing? It is missing machine-readable SEMANTICs - and this is what RDF actually is good for! So the big difference I see is that RDF is an intrinsic part of the semantic web, providing exactly what currently is missing in JAX-RS, while every other data format does not. So I really vote PRO adding this single data format exactly to JAX-RS and to no other project, as it is highly related with the RS postfix of this JSR. Without it, JAX-RS would be just JAX-HS (HTTP-Based-Web- Services). So RDF has a completely different relation to JAX-RS than other data formats.

No, I do not know any library that could get attached. But I heard about someone already done a JAX-RS implementation of RDF some months back.

[glassfishrobot]

@glassfishrobot Commented sandoz said: Manuel sent the following to the issues email list:

https://jsr311.dev.java.net/servlets/ReadMsg?list=issues&msgNo=227

Hi,

We [1] wrote some RDF providers [2] using the jena [3] for serializing [4] and parsing [5] different RDF formats.

Cheers, Manuel

[1] http://incubator.apache.org/clerezza/ [2] http://svn.apache.org/repos/asf/incubator/clerezza/trunk/org.apache.clerezza.parent/org.apache.clerezza.jaxrs.rdf.providers/ [3] http://jena.sourceforge.net/ [4] http://svn.apache.org/repos/asf/incubator/clerezza/trunk/org.apache.clerezza.parent/org.apache.clerezza.rdf.jena.serializer/ [5] http://svn.apache.org/repos/asf/incubator/clerezza/trunk/org.apache.clerezza.parent/org.apache.clerezza.rdf.jena.parser/

[glassfishrobot]

@glassfishrobot Commented @mpotociar said: Out of scope for 2.0 and very limited time left - deferring to a future release.

[glassfishrobot]

@glassfishrobot Commented rebach said: The Apache clerezza project has a module calles jaxrs.rdf.providers which provided MBW and MBR for graphs as well as MBW for Sparql result sets.

[glassfishrobot]

@glassfishrobot Commented This issue was imported from java.net JIRA JAX_RS_SPEC-25