search

IIIF / api

Source for API and model specifications documents (api and model)
http://iiif.io/api
106 stars 54 forks source link

Document a pattern for seeAlso profiles #841

Closed jpstroop closed 6 years ago

jpstroop commented 8 years ago

Media types don't exist or aren't granular enough. seeAlso is really just a refined service so document at http://iiif.io/api/annex/services/ one example of how to use the namespace (or XSD?) as the profile, e.g.:

seeAlso: {
  "@id": "http://wellcomelibrary.org/service/alto/b19956435/0?image=0",
  "format": "text/xml",
  "profile": "http://www.loc.gov/standards/alto/v3/alto.xsd",
  "label": "METS-ALTO XML"
}
azaroth42 commented 8 years ago

:-1: on putting it in services, but :+1: to documenting how to decide and record profile URI choice.

mikeapp commented 8 years ago

👍 to the profile in seeAlso

jpstroop commented 8 years ago

@azaroth42 where instead? Another note?

azaroth42 commented 8 years ago

I would prefer another note, parallel to the services one. Otherwise it will be confusing as to which of service and seeAlso to use. We should also maybe clarify the distinction as to when one would use one or the other, as I agree that there's overlap.

zimeon commented 8 years ago

Hmmm... this seems a bit like "6 of one, and half a dozen of the other". In separate docs one see one and not the other, if combined then they get confused... Might be worth trying to write it separately but then revisiting the question before we decide.

glenrobson commented 7 years ago

In the Newspaper group we've been discussing linking to ALTO, hOCR and Text and have proposed the profiles mentioned in the following doc (linking to text section): http://bit.ly/2a63PR6

azaroth42 commented 6 years ago

This is now a duplicate of the broader #1310. Closing.