Re: definition of "publication"

On 09/11/2015 09:42, Hiroshi Sakakibara wrote:

> 1) Where dose POM position in the software architecrue?
>    For ease of use, it should not be implemented in browser. But POM
>    should interact with browser. 

I don't understand this question. POM is a specification that could
or could not be implemented by user agents. If it's implemented, well
that's free sugar for publication editing/browsing authors; if it's not,
a JS framework (for example) could help.

> 2) How should "PWP Control data" be presented?
>    Is this data a part of Web document? 
>    (I'm still wondering content data and control data should be
>    devided or not.  And what "devided" means in fact..)
> 3) (From PWP document) I want to have UI controlling mechanism for
>    contents.
>    Current EPUB have TOC. Most of EPUB viewer has TOC button, and TOC
>    meta information is listed.
>    Travel guide books or other scientific publications require
>    TOC-like button to list up or to point other information.
>    The meta information differs depending on the contents.
>    So, UI controlling way from contents to RS is needed. 
>    (In fact, I talked with JP guide book publishing company and
>    Japanese classics publishing company, and both of them require such
>    mechanism.)

I don't think POM's goal is to dive into UI. It should clearly help
"navigating" into the various table of contents, i.e. allow to reach
previous/next/etc resources, but UI is IMHO out of scope here.

</Daniel>

Received on Monday, 9 November 2015 09:01:27 UTC