Olivier, You are correct. RDF/XML does allow relative URIs in certain places, including rdf:about. The URI is resolved into an absolute URI using the XML Base rules. [1] You can include an xml:base attribute. If that's missing, the base is the document URI.
Your link points to the application/xml section of the spec which gives guidelines for producing an XML representation that would be valid RDF/XML, but that would not use all the features of RDF/XML and therefore be suitable for processing as XML. The intention was to eliminate flexibility so it would be easier to parse. When you produce application/rdf+xml, use RDF/XML, there are no constraints, i.e. just follow the W3C spec. Are you asking to clarify the use of relative URIs in the application/xml case? [1] http://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-ID-xml-base Regards, ___________________________________________________________________________ Arthur Ryman, PhD, DE Chief Architect, Project and Portfolio Management IBM Software, Rational Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063 From: Olivier Berger <[email protected]> To: "[email protected]" <[email protected]> Date: 01/18/2011 09:28 AM Subject: [oslc-core] Repost: Relative URIs in rdf:about of OSCL resources Sent by: [email protected] Hi. May I kindly ask again if some have any insights on this (thy shall not post on days before Christmas ? ;) ? Le jeudi 23 décembre 2010 à 16:14 +0100, Olivier Berger a écrit : > Hi. > > I may be mistaken, but RDF+XML allows to set relative URIs for rdf:about > properties. > > For instance the document retrieved from > http://example.com/blogs/entries may contain : > > <rdf:RDF > xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; > xmlns:dcterms="http://purl.org/dc/terms/"; > xmlns:foaf="http://xmlns.com/foaf/0.1/"; > xmlns:oslc_blog="http://open-services.net/ns/bogus/blogs#";> > > <oslc_blog:Entry > rdf:about="#1"> > > <dcterms:title>I love trash</dcterms:title> > SNIP > > Which would describe an oslc_blog:Entry resource whose URI would be > http://example.com/blogs/entries#1 > > Then, similarly, rdf:about="" would be valid and refer to the document > itself (http://example.com/blogs/entries) in such case. > > Still, the OSLC specs in [0] mention : > "# 1.0 Open the XML root element <rdf:RDF> and include all required namespace declarations > # 2.0 Open the XML element as a first child of the XML root element using the Resource's Prefixed Name > > * 2.1 Add to the XML element the rdf:about attribute set to the URI of the resource" > > So, would rdf:about="" be a valid content for a document produced by an > OSLC compliant provider (of course, it'd be better accessed from a > "stable" URL) ? > > Thanks in advance. > > Best regards, > > [0] http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixRepresentations#Steps_to_generate_an_XML_represe -- Olivier BERGER <[email protected]> http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingénieur Recherche - Dept INF Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France) _______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net
