W3C home > Mailing lists > Public > public-digipub-ig@w3.org > October 2016

Re: Paginating with Annotation

From: Leonard Rosenthol <lrosenth@adobe.com>
Date: Wed, 26 Oct 2016 01:16:57 +0000
To: Benjamin Young <byoung@bigbluehat.com>, W3C Digital Publishing IG <public-digipub-ig@w3.org>
Message-ID: <B39B41CA-708A-4051-8FD8-1F1DD8566835@adobe.com>
I have to admit that using the Annot Data Model for such things is interesting, Ben – but I don’t see how what you propose below has anything to do with pagination.  Can you explain how that data model (which I understand in the context of annots) implies anything to a UA about pagination (either logical or physical)?


On 10/25/16, 11:26 AM, "Benjamin Young" <byoung@bigbluehat.com> wrote:

    Hi all,
    This is a potentially less than sane idea for using Web Annotation Data Model to create a pagination definition regardless of ownership, access, or control over various resources or specific resources (a resource + a narrowing selection).
    Here's what the data structure looks like (cribbing heavily from Example 12 in the Web Annotation Data Model specification):

      "@context": "http://www.w3.org/ns/anno.jsonld",
      "id": "http://example.org/anno12",
      "type": "Annotation",
      "motivation": "paginating",
      "target": {
        "type": "List",
        "items": [
          {"source": "http://example.com/book/cover.png", "stylesheet": "http://example.com/css/position-cover.css"},
          {"source": "http://example.com/book/toc", "stylesheet": "http://example.com/css/toc.css"},
          {"source": "http://example.com/book/intro", "stylesheet": "http://example.com/css/us-letter-size.css"},
          {"source": "http://wikipedia.com/PageAboutThisBook",
            "selector": {
              "type": "CssSelector",
              "value": "#mw-content-text"
            "stylesheet": "http://example.com/css/us-letter-size.css"
          {"source": "http://example.com/book/another-page", "stylesheet": "http://example.com/css/us-letter-size.css"}   
    The only thing above not currently defined in the Web Annotation Data Model is the `paginating` motivation--everything else is "stock" Web Annotation Data Model.
    Obviously, there are worlds (and probably dragons) beyond this point, but I wanted to share this as I find thinking about it inspiring.
    If you feel this has merit in some way, I'd be happy to explore it further with anyone interested.
    Information Standards
    John Wiley & Sons



Received on Wednesday, 26 October 2016 01:17:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 25 April 2017 10:44:46 UTC