The metS (metadata encoding and transmission Standard) is a specification for exchanging and storing metadata independent of specific project needs. The only mandatory section in METS is the structMap section. Digital objects can be described from different perspectives, resulting in different structMap sections. The physical perspective may describe pages, columns, and text areas and their layout relative to each other. The logical perspective may describe sequences, such as the sequence of songs on a CD, or containment, such as the containment of a chapter in a book. These perspectives are captured in separate hierarchical tree structures. Objects in structMap sections can be linked to each other. They also can be linked to the file section which describes the corresponding files. Files in the file section can be organized into one or more file groups. Files may be grouped according to user needs, for example by file format, image resolution, or the intended use of the file (preservation copy, access copy, thumbnail, etc.). Every object defined in the structMap section, as well as every file, may have descriptive or administrative metadata (divided into provenance, source, and technical or rights metadata within METS) describing them outside the structMap or file section. Even though METS endorses the use of particular extension schemas, it supports every kind of well-formed XML in these sections. METS uses XML’s ID/IDREF linking mechanism for attaching the metadata section to the object. Figure 4 illustrates the METS architecture.
The metS (metadata encoding and transmission Standard) is a specification for exchanging and storing metadata independent of specific project needs. The only mandatory section in METS is the structMap section. Digital objects can be described from different perspectives, resulting in different structMap sections. The physical perspective may describe pages, columns, and text areas and their layout relative to each other. The logical perspective may describe sequences, such as the sequence of songs on a CD, or containment, such as the containment of a chapter in a book. These perspectives are captured in separate hierarchical tree structures. Objects in structMap sections can be linked to each other. They also can be linked to the file section which describes the corresponding files. Files in the file section can be organized into one or more file groups. Files may be grouped according to user needs, for example by file format, image resolution, or the intended use of the file (preservation copy, access copy, thumbnail, etc.). Every object defined in the structMap section, as well as every file, may have descriptive or administrative metadata (divided into provenance, source, and technical or rights metadata within METS) describing them outside the structMap or file section. Even though METS endorses the use of particular extension schemas, it supports every kind of well-formed XML in these sections. METS uses XML’s ID/IDREF linking mechanism for attaching the metadata section to the object. Figure 4 illustrates the METS architecture.
การแปล กรุณารอสักครู่..