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

I am sorry. My reply below applies to what we discussed for the upcoming for the WP metadata. This thread is on the Readium WP Manifest, and I am of course not in position to give an authoritative answer.

B.t.w.: this becomes a side issue as far as this thread is concerned. It was exclusively on a very specific issue around the JSON-LD representation of that Manifest format, which, at this moment, is just a proposal for the WP manifest format. If there are specific questions re the WP spec, we should go back to the issue list...

Ivan

> On 10 Jan 2018, at 14:03, Ivan Herman <ivan@w3.org <mailto:ivan@w3.org>> wrote:
> 
> 
> 
>> On 10 Jan 2018, at 13:01, Daniel Glazman <daniel.glazman@disruptive-innovations.com <mailto:daniel.glazman@disruptive-innovations.com>> wrote:
>> 
>> Le 10/01/2018 à 11:01, Hadrien Gardeur a écrit :
>> 
>>> They don't conflict. All metadata defined in the manifest are metadata
>>> about the collection, while all the elements that you've listed apply to
>>> a specific resource.
>> 
>> So what's the progression direction if the collection says ltr and if
>> the specific resource says rtl and has more than one page? IMO, that
>> example alone clearly requires an importance order to be specified, the
>> directions are conflicting.
> 
> (At the moment) the direction applies for the metadata only (author, editor, license, etc). The direction for individual resources are defined by the rules for that type of resource. Ie, in the case of an HTML content, the HTML spec applies.
> 
> Ivan
> 
> 
>> 
>>>   Example: the html document is in english, ltr with title "foo" while
>>>   the manifest, referenced from there, says the title is "bar", the
>>>   language is hebrew and the direction rtl. What happens?
>>> 
>>>   Note: when I mean "conflict" there, I mean "what will be the expected
>>>   behaviour of a Web browser's rendering engine?".
>>> 
>>> 
>>> IMO, nothing at all. The browser will entirely ignore collection level
>>> metadata when rendering.
>> 
>> While Reeading Systems won't. That's an issue, see above.
>> 
>> </Daniel>
>> 
> 
> 
> ----
> 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>