Bernie, our intention is to have an image extension schema that embodies
the NISO plan (elements/fields list, I guess I mean). Our image
extension schema represents an attempt to do that but if we did not
succeed, others should guide us to changes that would comply. Of
course, when there is an official NISO XML schema, we will simply use
Our general view regarding NISO imaging and (maybe) the Audio
Engineering Society developments (and other parallel efforts) is this:
if those organizations assume that a framework like METS or MPEG21
exists, and agree that their specialized data can "fit" well within it,
then they can concentrate on the "engineering" issues that they know
best without having to fret one more time over the devils represented by
descriptive/intellectual/ bibliographic metadata, access/rights
metadata, structural (in our meaning of structural) metadata, etc.
This contrasts (I think) with, say, DIG35 which tries to be an
all-inclusive block of data.
To be continued . . .
National Digital Library Program
Library of Congress
Bernie Hurley wrote:
> Hi Carl...
> Priscilla Caplan asked me a question that I couldn't answer last
> Friday. "What is the relationship between NISO's work on Technical
> Metadata for Digital Still Images and METS?"
> Are your combined allfilesMD and imageMD extension schemas "compliant"
> with the data dictionary for technical metadata for still images
> created by NISO? It seems there may be an opportunity here to work
> together, as NISO does not yet have an encoding scheme proposed for
> image technical metadata.
> Thanks, Bernie
> Bernie Hurley
> Director of Library Technologies
> The UC Berkeley Library [log in to unmask]
> Rm. 245, Doe Library - 6000 Voice: (510) 642-3773
> Berkeley, CA 94720-6000 Fax: (510) 642-8179
> Name: Technical
> Metadata for
> Digital Still
> Technical Metadata for Digital Still Images (Committee AU).url Images
> Type: Plain Text