IIIF Discovery Strawperson

iiif_agg_disc_import.md

IIIF Aggregation, Discovery, and Import

Introduction

Audience and Scope

• Carefully acknowledge somehow that this extends the scope of IIIF, but is at least controlled mission creep (i.e. similar to a controlled burn :-))

• Use cases:

  • thematic registries and portals
  • ad-hoc reuse/remixing/mashups
  • NOT indended for transmission ( METS)

Terminology

• distinguish bet. aggregation, discovery, and import
• Sitemaps
• refs to other specs (for eg. seeAlso),
• RFC 2119 keywords

Aggregation

• Via sitemaps, optionally w/ ResourceSync extensions
• Distinct from curated collections in that they're just a list.
  • No repetiton
  • No order
  • No hierarchy
  • (Not necessarily thematic, no labels)

Discovery

• (happens after aggregation)
• seeAlso profiles

Import

(i.g. drag & drop - you've found this thing, now what?)

• Start with http://zimeon.github.io/iiif-dragndrop/
• Maybe doesn't belong here, it's a little disjoint, but maybe easier than a separate spec
• Logo use
  • IIIF Logo
  • Source Institution Logo (per Prezi spec))

Looks like a good framework to me.

More specific comments:

• I think there should be order ... by most recent changed. Otherwise you kind of need a ResourceSync changelist, and that's starting to become overhead.
• This looks like a spec to me, rather than a note. There are real testable requirements, and if you don't do it the same way, interop doesn't work.
• I (like you, I think) would resist putting in any details about the aggregator. This is a spec for content providers and client providers (for the drag and drop part).