1. 1:1 Reconsidered DC-6, November 4, 1998

2. History zJuly 97: RLG Metadata Summit yArchives, museums, libraries yIdentified need for flexible description of resource manifestations yMetadata Summit: Meeting Report. Willy Cromwell-Kessler and Ricky Erway. July, 1997..

3. History zDC-5, Helsinki, October 97 yRLG proposal raised y1:1 principle emerges

4. 1:1 Status zPublished in D-Lib Magazine yThe [DC-5] discussion resulted in consensus concerning what came to be known as the 1:1 principle -- each resource should have a discrete metadata description, and each metadata description should include elements relating to a single resource. It is desirable to be able to link these descriptions in a coherent and consistent manner [emphasis added]. yDC-5: The Helsinki Metadata Workshop: A Report on the Workshop and Subsequent Developments (http://www.dlib.org/dlib/february98/02weibel.html)

5. 1:1 Status zCrept into DC vocabulary zNot represented in RFC zLacks operational definition and application guidelines zAdoption by implementers uncertain

6. Our Best Understanding of 1:1 zAny given set of metadata refers to a single discrete resource

7. Implications of 1:1 zPrecise granularity zProliferation of metadata records yLarge retrieval sets yIncreased record maintenance zAccess vocabulary split over multiple records zConfusion applying selected elements, e.g., Creator, Publisher

8. Example zOne record for resource with compound characteristics yDigital image from photograph xMetadata conveys aspects of original resource (e.g., photographer), and xMetadata conveys aspects of digital manifestation (e.g., Format)

9. Example zOne record for multiple formats yElectronic text manifest in ASCII, Word, PDF xMetadata conveys aspects of each manifestation

10. Example zOne record for set of resources yCollection of images xMetadata conveys aspects of collection and each discrete resource

11. RDF Model z zAppears to accommodate examples

12. Summary zIf 1:1 (as we understand it) does not enable implementers to accomplish the requirements expressed above, specific expressed user needs are not addressed zIf 1:1 does enable implementers to accomplish the requirements expressed above, then the concept appears to accommodate user needs zRegardless...

13. Action Items zRevisit 1:1 zDetermine usefulness and necessity as a DC precept zEnsure that user needs are determined and addressed zFormally adopt, allow, or reject

14. Action Items zIf adopt, then: zDefine and ratify in RFC zDevelop application guidelines zMonitor implementation experiences and user satisfaction