Element Groups for Imaging Metadata

From MOA2 White Paper

1. Administrative metadata involved in creating the master image (source, scanning date, scanner profile, light source, etc.)
2. Identifying what is needed to view or use the Image (information derived from within a normal header, including" resolution, bit-depth, CLUT, file format, compression format, pixel dimensions, etc.)
3. Linking parts or instaciations (this is probably too broad and should be split; meant to incorporate things ranging from sequence numbers to detail/full-image relationships to versioning)
4. Ownership, Rights

 Other areas to add

1. Identification/Provenance  (see Dublin Core Relation_Type Working Group)

Discussion

• Most of Priscilla's issues of non-technical information are covered in MOA2 #1
• Some of Carl's issues around object-level versus file-level will fall into MOA2 #3.  But if we open up the issue of object vs. file, we'll need to set some parameters on what constitutes an object.  (Just as one person's metadata is another person's data, one person's file is another person's object.)

Begun by Howard Besser  (1/2/99), extended by