RE: Please publish Turtle or JSON-LD instead of RDF/XML [was Re: Recommendation for transformation of RDF/XML to JSON-LD in a web browser?]

Yes – double nesting – this is what GML* does. It makes instance documents trivial to transform to valid RDF, but confuses the hell out of most XSD-RDF converters.

Simon Cox

*Geography Markup Language.

From: Timothy W. Cook [mailto:tim@mlhim.org]
Sent: Friday, 4 September 2015 9:34 PM
To: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
Cc: Kingsley Idehen <kidehen@openlinksw.com>; public-lod@w3.org
Subject: Re: Please publish Turtle or JSON-LD instead of RDF/XML [was Re: Recommendation for transformation of RDF/XML to JSON-LD in a web browser?]



On Fri, Sep 4, 2015 at 7:02 AM, Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk<mailto:soiland-reyes@cs.manchester.ac.uk>> wrote:



I must admit I have even done XML Schemas for documents that just
happens to be valid RDF/XML documents - (this was before JSON-LD and
Turtle were standards) - this was pushing the envelope in both
directions (e.g. needing double-nested XML elements, one for the
property, and one for the class) and I wouldn't do this again -

​This is what appinfo elements are for. Sounds you used a very complex approach.  Just embed the EDF/XML inside appinfo tags and it is very clean.

  ​



--

============================================
Timothy Cook
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook

MLHIM http://www.mlhim.org<http://www.mlhim.org/>