I also have the following questions of clarification about the
documentation... (I put page numbers for my own reference, though they
may not be critical for the question.)
1) Is there any limitation on supported schemes for XPTR? (p. 20) If so,
or even if not, I think it might be mentioned.
2) Pages 29-30 mention <file/> as recursive allowing for sub-files or
components files--is this along the lines of being part of a zip, or
just broken in pieces (like each page of a book having a separate file)?
3) Might an example be given showing the difference of USE when used on
<file/> and when on <FLocat/>?
4) While I know it is application-specific, what exactly would an XLink
show value of "embed" mean in the context of a METS file. Embedding the
file within the document would not seem to make sense, as the document
is not really meant to be formatted, I presume, so might it be used to
refer to how the document should be displayed subsequently. For example,
if I am using METS to browse reassembled packages of files in my web
browser, it might refer to embedding the file in the current window, as
opposed to opening a new window? (p. 44)
5) I think the use of both XLink's arcrole and role in an example would
6) file: is used as a prefix for relative files in the METS docs; is
this a standard?