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 4 September 2015 at 12:02, Stian Soiland-Reyes <
soiland-reyes@cs.manchester.ac.uk> wrote:

> +1 to minimize RDF/XML use!
>
> I do also think there is the same danger now of JSON-LD being seen as
> a dialect of JSON, rather than a way to serialize RDF.
>
> I have seen people trying to do "JSON-LD" with arbitrary JSON added
> here and there. Some even interpreted "Linked Data" as meaning "Just
> make some JSON with arbitrary keys and put it on the web". For many
> developers who come fresh to RDF/Linked Data - the first thing they
> see is the serialization and they want to stop there - they have
> enough other things to worry about.
>

This is definitely one of the weaknesses of JSON, and people are doing
this, or trying to do this already.

As far as I know, linked data doesnt have a systematic way of translating
the property "attribute" into a URI.

So the downside of increased JSON usage, could be lower quality data.


>
> I think that is fine, as long as they don't try to push the
> serialization further or add additional hidden meanings - RDF as a
> graph still should be in the back of your mind - e.g. a nested
> JSON-object in JSON-LD is not magically "owned" by the super-parent.
> You can have nice-to-have structures, e.g. like you say to do
> transformations, and also Linked Data By Stealth.
>
>
> 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 - but
> doing similar in the JSON world can still be useful as long as we
> don't push it too far or hide the RDF semantics too well.
>
>
>
> On 3 September 2015 at 19:41, Kingsley Idehen <kidehen@openlinksw.com>
> wrote:
> > On 9/3/15 1:53 PM, Martynas Jusevičius wrote:
> >> With due respect, I think it would be foolish to burn the bridges to
> >> XML. The XML standards and infrastructure are very well developed,
> >> much more so than JSON-LD's. We use XSLT extensively on RDF/XML.
> >
> > We don't have to dump RDF/XML per se., we simply need minimize use and
> > emphasis. For instance, we use RDF/XML extensively in our transformation
> > middleware, but that's all inside and doesn't affect things on the
> outside.
> >
> > The problem with RDF/XML is that it had an exalted position in the
> > Semantic Web realm for way too long. To this very day, many of us are
> > still trying to get folks to understand that RDF is neither a format nor
> > a dialect of XML.
> >
> > Kingsley
> >>
> >> Martynas
> >> graphityhq.com
> >>
> >> On Thu, Sep 3, 2015 at 8:03 PM, David Booth <david@dbooth.org> wrote:
> >>> Side note: RDF/XML was the first RDF serialization standardized, over
> 15
> >>> years ago, at a time when XML was all the buzz. Since then other
> >>> serializations have been standardized that are far more human friendly
> to
> >>> read and write, and easier for programmers to use, such as Turtle and
> >>> JSON-LD.
> >>>
> >>> However, even beyond ease of use, one of the biggest problems with
> RDF/XML
> >>> that I and others have seen over the years is that it misleads people
> into
> >>> thinking that RDF is a dialect of XML, and it is not.  I'm sure this
> >>> misconception was reinforced by the unfortunate depiction of XML in the
> >>> foundation of the (now infamous) semantic web layer cake of 2001,
> which in
> >>> hindsight is just plain wrong:
> >>> http://www.w3.org/2001/09/06-ecdl/slide17-0.html
> >>> (Admittedly JSON-LD may run a similar risk, but I think that risk is
> >>> mitigated now by the fact that RDF is already more established in its
> own
> >>> right.)
> >>>
> >>> I encourage all RDF publishers to use one of the other standard RDF
> formats
> >>> such as Turtle or JSON-LD.  All commonly used RDF tools now support
> Turtle,
> >>> and many or most already support JSON-LD.
> >>>
> >>> RDF/XML is not officially deprecated, but I personally hope that in
> the next
> >>> round of RDF updates, we will quietly thank RDF/XML for its faithful
> service
> >>> and mark it as deprecated.
> >>>
> >>> David Booth
> >>>
> >>
> >
> >
> > --
> > Regards,
> >
> > Kingsley Idehen
> > Founder & CEO
> > OpenLink Software
> > Company Web: http://www.openlinksw.com
> > Personal Weblog 1: http://kidehen.blogspot.com
> > Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen
> > Twitter Profile: https://twitter.com/kidehen
> > Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
> > LinkedIn Profile: http://www.linkedin.com/in/kidehen
> > Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this
> >
> >
>
>
>
> --
> Stian Soiland-Reyes, eScience Lab
> School of Computer Science
> The University of Manchester
> http://soiland-reyes.com/stian/work/
> http://orcid.org/0000-0001-9842-9718
>
>