Re: A question on RWPM: why the 'metadata' tag?

> On 9 Jan 2018, at 17:01, Benjamin Young <byoung@bigbluehat.com <mailto:byoung@bigbluehat.com>> wrote:
> 
> What's the address (as defined in WP) for this book? All I see is the alternate identifier.

This is not a WP manifest. It is a Readium Manifest, which is happy with the urn as an identifier. But that is a secondary issue now, I was really looking at the JSON-LD aspect of things only

Ivan



> 
> --
> http://bigbluehat.com/ <http://bigbluehat.com/>
> http://linkedin.com/in/benjaminyoung <http://linkedin.com/in/benjaminyoung>
> From: Ivan Herman <ivan@w3.org <mailto:ivan@w3.org>>
> Sent: Tuesday, January 9, 2018 10:58:44 AM
> To: Hadrien Gardeur
> Cc: Leonard Rosenthol; W3C Publishing Working Group
> Subject: Re: A question on RWPM: why the 'metadata' tag?
> 
> 
> 
> > On 9 Jan 2018, at 16:44, Hadrien Gardeur <hadrien.gardeur@feedbooks.com <mailto:hadrien.gardeur@feedbooks.com>> wrote:
> >
> > My main problem is not the blank node. I know that many in the LD community are up in arms against it, but I may be less sensitive.
> >
> > My problem is making owl:sameAs a central aspect of the data; what I expect that, in practice, all the linked data that is hanging on that blank node will be, essentially, useless in (Linked Data) practice, because tools will not reach that data (apart from OWL reasoners and triple stores that know how to reason with OWL terms, which is a small minority of the usage).  My claim is that the current structure produces possibly lots of Linked Data that will become totally useless… then why do it?
> >
> > A possibility is that _only_ the JSON object in metadata should be considered as RDF metadata, and all the rest is ignored. I am not yet sure how to achieve that with @context  (maybe by using @context only in that object, I have to check with the JSON-LD spec).
> >
> > If we don't care about the default reading order in RDF, then we could simply remove spine from the default context document.
> >
> > The Turtle output would then be:
> >
> > <urn:isbn:978031600000X> a schema:Book ;
> >     schema:author "Herman Melville" ;
> >     schema:dateModified "2015-09-29T17:00:00+00:00"^^xsd:dateTime ;
> >     schema:inLanguage "en" ;
> >     schema:name "Moby-Dick" .
> 
> Almost. If we simply remove "spine" from the context, we get an extra triple:
> 
> [] ns1:sameAs <urn:isbn:978031600000X>.
> 
> Which just junk, but uninteresting junk that we can maybe ignore. (And hope for JSON-LD 1.1 that would make this disappear via the usage of @nest.) In my view, this is better than the current output.
> 
> (And yes, I do not really care about the spine data being part of the LD. What counts is the metadata itself.)
> 
> Ivan
> 
> P.S. Maybe there is an extra trick to make that extra triple disappear, but I do not see it now...
> 
> 
> 
> 
> 
> 
> ----
> Ivan Herman, W3C
> Publishing@W3C Technical Lead
> Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
> mobile: +31-641044153
> ORCID ID: http://orcid.org/0000-0003-0782-2704 <http://orcid.org/0000-0003-0782-2704>

----
Ivan Herman, W3C
Publishing@W3C Technical Lead
Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704 <http://orcid.org/0000-0003-0782-2704>