LISTSERV mailing list manager LISTSERV 16.0

Help for METS Archives


METS Archives

METS Archives


METS@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

METS Home

METS Home

METS  June 2002

METS June 2002

Subject:

METS v1.1 Proposal

From:

Jerome McDonough <[log in to unmask]>

Reply-To:

Metadata Encoding and Transmission Standard <[log in to unmask]>

Date:

Wed, 5 Jun 2002 11:19:05 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (108 lines)

Greetings,

At the recent meeting of the METS editorial board, two deficiencies with
the current (v.1.0 zeta) METS schema were identified:

1. As Robin Wendler noted in a recent post, people working with large,
multi-track
audio files face a significant problem with regards to the current schema's
structural map section.  Typically, they will have one byte stream per track,
where each byte stream is so large (for master files) that they cannot be
contained in a single file on the file system (each  byte stream exceeds the
operating system's limits for maximum file size).  While
the v1.0 schema has the <par> element within the structMap to allow you to
indicate
that multiple files should be played in parallel, it is inadequate in those
cases where
a single byte stream must be placed in more than one file.  To rectify
this, the board
is proposing that the schema be modified to allow the <seq> element to
appear as
a subelement of <par>.  This would allow those encoding structural metadata to
group a series of files together as a single bytestream to be played in
parallel
with another series of files, e.g.,

         <par>
                 <seq>
                         <area FILEID="tract1part1"/>
                         <area FILEID="tract1part2"/>
                 </seq>
                 <seq>
                         <area FILEID="tract2part1"/>
                         <area FILEID="tract2part2"/>
                 </seq>
         <par>

2. There have been numerous questions on the list over the past year as to how
to record the hyperlink structure of a website within a METS document.  To
date,
METS has made no provision for recording such information.  While it could
record
the hierarchical tree structure of a website, recording the links between
the nodes of
that tree was impossible.  To rectify this, the editorial board is
proposing the addition
of a new, major section to the METS schema, <structLink>.  <structLink> allows
you to encode one or more <smLink> elements, where each <smLink> records a
hypertext link between two nodes in the <structMap> section of a METS document
using the 'to' and 'from' attributes.  Note that to record these links your
<structMap>
will have to contain at least a <div> for the origin and target of each
link.  That is, if you have
an HTML page with 3 links to other pages, you'd probably want something like
the following in your <structMap>

         <div ID="p1" LABEL="page1">
                 <div ID="p1L1" LABEL="link1">
                 <div ID="p1L2" LABEL="link2">
                 <div ID="p1L3" LABEL="link3">
         </div>
         <div ID="p2" LABEL="page2"/>
         <div ID="p3" LABEL="page3"/>
         <div ID="p4" LABEL="page4"/>

and then the following in <structLink>

         <smLink to="p2" from="p1L1"/>
         <smLink to="p3" from="p1L2"/>
       &n