Re: Paginating with Annotation

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" <> 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": "",
      "id": "",
      "type": "Annotation",
      "motivation": "paginating",
      "target": {
        "type": "List",
        "items": [
          {"source": "", "stylesheet": ""},
          {"source": "", "stylesheet": ""},
          {"source": "", "stylesheet": ""},
          {"source": "",
            "selector": {
              "type": "CssSelector",
              "value": "#mw-content-text"
            "stylesheet": ""
          {"source": "", "stylesheet": ""}   
    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