- From: Richard Light <richard@light.demon.co.uk>
- Date: Fri, 21 Feb 2020 09:12:36 +0000
- To: "semantic-web@w3.org" <semantic-web@w3.org>
- Message-ID: <168d21d3-f53f-ea8f-e5f4-3221f7f7d47c@light.demon.co.uk>
On 21/02/2020 08:29, Martynas Jusevičius wrote: Hi, On Fri, Feb 21, 2020 at 9:26 AM Thomas Francart <thomas.francart@sparna.fr><mailto:thomas.francart@sparna.fr> wrote: I read at https://us2ts.org/program-easier-rdf a proposal to deprecate RDF/XML. This syntax has a major advantage : it can be generated using XSLT from source XML files. This ability to bridge XML and RDF is also key in some projects. I was about to write exactly the same thing. RDF/XML is a crucial bridge to/from the XML stack. To put it more generally, an XML serialization of RDF graphs is a crucial bridge to/from the XML stack. You could make an argument (under the 'simplify RDF' heading) for a less clever XML serialization which simply represents nodes and arcs for what they are. I did this when faced with the job of generating multiple RDF serializations from an XML source. Once I had my 'simple RDF XML', I could write a single generic XSLT transform for each serialization required. I couldn't begin to do that, starting from RDF/XML. Also, as you imply, it's not just about generation of Linked Data: it's also about consumption. What I'm working on right now is an XSLT transform which uses the XSLT document() function to query a Linked Data resource and add lat/long coordinates to my source (XML) data. Richard . -- Richard Light
Received on Friday, 21 February 2020 09:12:53 UTC