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

> On 10 Jan 2018, at 11:16, Hadrien Gardeur <hadrien.gardeur@feedbooks.com <mailto:hadrien.gardeur@feedbooks.com>> wrote:
> 
> Mostly, relabeling `@id` as `identifier` and tucking it inside `metadata` seems very confusing. It look more like rel="identifier" or schema:identifier--but both of those can have multiple values and would be used for different purposes (especially within a WP).
> 
> rel=identifier is simply a proposal at this point and schema:identifier is specific to schema.org <http://schema.org/> and nowhere nearly as useful as @id for an RDF parser/client.
> 
> We avoided most properties prefixed with @ at this point for two reasons:
> identifier is more consistent with EPUB (dc:identifier) than @id
> we minimize our usage of @ properties as much as possible, mostly because we don't necessarily want all the powerful but complex stuff that JSON-LD can handle (I'm thinking mostly about local @context definition and @graph)
+1; plus JSON-LD also advices not to use @ properties to avoid later clashes with possible new version of JSON-LD.

> As I already told Ivan earlier in this thread, JSON-LD is always a balancing act between pure JSON and its RDF output, and in our case (Readium) JSON and hypermedia are clearly the priorities.
> Keep in mind too that the goal for RWPM is slightly different than WP:
> we want maximal compatibility with the EPUB 2.x/3.x infosets, not just WP
> it's meant to be a generic hypermedia format that can be used for specific publications profiles (comics, audiobooks) as well as distribution (OPDS 2.0)
> This could easily be revisited, we'd simply avoid mapping identifier to @id in the default context document.

Personally, I do not see any problem mapping "identifier" to @id in the context file. This is also what we did for the annotation model[1] (except that the term "id" was used instead of "identifier"). It is clean and hides the RDF specific stuff from those who do not want to see them.

Ivan


[1] http://www.w3.org/ns/anno.jsonld <http://www.w3.org/ns/anno.jsonld>



----
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>