SharedCanvas Zones in IIIF

[azaroth42]

Requested Feature: MITH use Zones extensively in the Shelley Godwin Archive from the Shared Canvas ontology. These are not available in the IIIF Metadata specification, and hence are preventing them from adopting it. University of York also need it (2/26)

Notes:

• Zones are separately manipulable regions (like a mini-canvas on top of another canvas) - think spinners, volvels, parts of letters, paste-downs, fold-outs, etc.
• Discussion is required as to whether, and if so how, to do this.
• IIIF should engage with this issue
• Defer further discussion. Rob will put forward proposal “sooner” than next IIIF meeting.

[jpstroop]

Support for zones opens up the newspaper space too, no? That seems like a big +

[azaroth42]

You could do articles more easily with Ranges rather than Zones. Zones are
good when you need to manipulate all of the annotations in a particular
area on a single canvas together (eg hide/show them to mimic fold outs,
rotate them to some useful reading orientation, etc)

But yes, if/when implemented, Zones will make several things much fancier :)

On Thu, Feb 27, 2014 at 12:11 PM, Jon Stroop notifications@github.comwrote:

Support for zones open up the newspaper space too, no? That seems like a
big +

Reply to this email directly or view it on GitHubhttps://github.com//issues/42#issuecomment-36278933
.

[azaroth42]

Zones

URI pattern: {scheme}://{host}{/prefix}/{identifier}/zone/{name}.json

{
  "@id": "mandatory-uri",
  "@type": "sc:Zone",
  "label": "optional label",
  "height": 1200,           // mandatory
  "width": 800,             // mandatory

  // other fields for zone manipulation
  "viewingOrientation": 270,
  "viewingHint": "foldout",

  "images": [ ... ],
  "otherContent": [ ... ]
}

Then aggregate them in an AnnotationList referenced from otherContent from the Canvas that it is associated with.

{
  "@context":"http://www.shared-canvas.org/ns/context.json",
  "@id":"http://www.example.org/iiif/book1/annotation/p1zone.json",
  "@type":"oa:Annotation",
  "motivation":"sc:painting",
  "resource": {
    "@id": "mandatory-uri",
    "@type": "sc:Zone",
    "label": "optional label",
    "height": 1200,           // mandatory
    "width": 800,             // mandatory

    // other fields for zone manipulation
    "viewingOrientation": 270,
    "viewingHint": "foldout",

    "images": [ ... ], // images annotated onto Zone go here
    "otherContent": [ ... ] // links to annotationlists for other annos on Zone
  },
  "on":"http://www.example.org/iiif/book1/canvas/p1.json"
}

[azaroth42]

Proposal is to have separate document to describe zones, as above, but to put any new properties into the baseline context.json. Currently there's only viewingOrientation.

[azaroth42]

Propose to discuss with @edsu as the representative of MITH, who have the most compelling use case.

[azaroth42]

Given current thinking of removing Zones completely and just allowing canvases to be annotated onto canvases ... I propose close wontfix.

[jpstroop]

👍 Do we need a SharedCanvas label?

[azaroth42]

@IIIF/editors Other +1s to closing the issue?

[azaroth42]

AV Call on 8/8/17: Propose to close (+1s all round, including @azaroth42 @mikeapp) Unless @jpstroop @zimeon @tomcrane object?

[zimeon]

👍 close wontfix

[jpstroop]

👍 close wontfix

[azaroth42]

Closing in favor of #1191.