80 likes | 238 Views
RAMLET & METS: . A Brief Explanation. Background Info. Purpose for the “ standard ” : functional not content based Use cases that provide context & scope “ Aggregation formats ” that serve as the basis (MPEG 21, Atom, IMS-CP, METS, OAI-ORE) Based on METS version 1.7.
E N D
RAMLET & METS: A Brief Explanation Prepared for the MEB meeting 2 November 2011
Background Info • Purpose for the “standard”: functional not content based • Use cases that provide context & scope • “Aggregation formats” that serve as the basis (MPEG 21, Atom, IMS-CP, METS, OAI-ORE) • Based on METS version 1.7
Somewhat “flattened” Relationships not necessarily hierarchical Elements / attributes – Classes / subclasses Concept of “properties” that provide controlled value restrictions, for example Key differences b/w XML & RDF
topnode descriptorobject anchor locatordescriptor remotenode Mets root element, p. 52 (WD) “descriptive” MD about object p. 17 (WD) Location(s) w/in a resource p. 11 (WD) Network location of resource p. 31 (WD) Location of resource outside p. 38 (WD) Key classes / subclasses
structMap div, fptr fileSec staticstructure p. 47 (WD) vs. dynamicstructure p. 20 (WD)(for mpeg:container) staticstructurenode inventory Key classes / subclasses, cont.
XML ID TYPE attributes SEQ GROUPID elementID Depends upon function Hasorder groupingID Key classes / subclasses, cont.
Useful for our data model discussion? • Classes derived from a functional point of view; skirts the content object issue
Status • Just released to ballot – • Those interested are welcome to join; let me know if you’d like to join the Ballot group • or to let me know what the issues are and I can add them as ballot issues • to njhoebel@gmail.com