[FIG(quote)[ [FIGCAPTION[ [1] [CITE[PubChemRDF Release Notes]] ([TIME[2016-09-14 23:56:18 +09:00]]) ]FIGCAPTION] > Abbreviated RDF/XML > application/rdf+xml+abbrev > rdfxml-abbrev ]FIG] [2] [CITE@en[Bug 392325 – StackOverflowException in abbreviated RDF XML writer when associating project area from RTC]] ([TIME[2016-10-19 20:44:37 +09:00]]) [FIG(quote)[ [FIGCAPTION[ [3] [CITE@en_US[OSLCCoreSpecAppendixRepresentations < Main < TWiki]] ([TIME[2016-10-19 20:45:39 +09:00]]) ]FIGCAPTION] > In this section we offer instructions for creating an XML representation for OSLC Defined Resources. The resultant XML representations are designed to validate as RDF/XML and therefore are often referred to as "constrained RDF/XML" or "abbreviated RDF/XML" representations, however the main intent of these instructions is to document a specific XML representation format for use in scenarios where a more unfettered RDF/XML representation or use of RDF/XML toolkits is not appropriate or preferred. OSLC domain specifications SHOULD refer to these instructions when requiring application/xml representations. > XML representations returned by OSLC Defined Resources SHOULD be: > Returned when these content types requested: application/xml > Returned as content-type: application/xml ]FIG] [FIG(quote)[ [FIGCAPTION[ [4] [CITE[Raptor RDF Syntax Library]] ([TIME[2014-12-16 11:41:45 +09:00]]) ]FIGCAPTION] > A second serializer is provided using several of the RDF/XML abbreviations to provide a more compact readable format, at the cost of some pre-processing. This is suitable for small documents. ]FIG] [FIG(quote)[ [FIGCAPTION[ [5] [CITE@en[ConverterFromRdf - W3C Wiki]] ([TIME[2016-10-19 15:36:45 +09:00]]) ]FIGCAPTION] > Raptor (part of Redland framework) can serialise to the following: > N-Triples, RDF/XML, RDF/XML (Abbreviated), RDF/XML (XMP Profile), Turtle ]FIG] [FIG(quote)[ [FIGCAPTION[ [6] [CITE[Frequently Asked Questions about using RDFLib — rdflib 4.2.2-dev documentation]] ([TIME[2016-10-15 21:42:37 +09:00]]) ]FIGCAPTION] > How can I use some of the abbreviated RDF/XML syntax? > Use the “pretty-xml” format argument to the serialize method: > myGraph.serialize(target_pretty, format="pretty-xml") ]FIG] [FIG(quote)[ [FIGCAPTION[ [7] [CITE[RDF::Helper - search.cpan.org]] ([TIME[2016-10-19 20:52:01 +09:00]]) ]FIGCAPTION] > Serializes the back-end RDF model to a string, using the specified format type, or defaulting to abbreviated RDF/XML. ]FIG] [FIG(quote)[ [FIGCAPTION[ [8] [CITE@en-US[PublishingRdfVocabularies < LinkedData < TWiki]] ([TIME[2016-10-19 20:54:36 +09:00]]) ]FIGCAPTION] > Transform the RDF to HTML, e.g. for the Reporting Data Dictionary, this is done in two steps. First, the Turtle file is converted using Jena to dd-vocabulary.rdf which contains non-abbreviated RDF/XML. Second, the RDF/XML is converted using XSLT to the HTML file dd-vocabulary.html. See below for an Ant script and XSLT file to automate this process. ]FIG] [FIG(quote)[ [FIGCAPTION[ [9] [CITE@en[IBM Knowledge Center - Updating Service Provider records URLs in batch]] ([TIME[2016-10-19 20:55:23 +09:00]]) ]FIGCAPTION] > Set the Accept HTTP header to define the media type in which you want to get the resource representation. Possible values for the media types are as follows: > application/xml to get an abbreviated RDF/XML representation of the resource. > application/rdf+xml to get an expanded RDF/XML representation of the resource. > If you do not specify this header, you get a resource represented in abbreviated RDF/XML format by default. ]FIG]