LISTSERV mailing list manager LISTSERV 16.0

Help for PIG Archives


PIG Archives

PIG Archives


PIG@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

PIG Home

PIG Home

PIG  October 2005

PIG October 2005

Subject:

Re: mandatory elements

From:

Markus Enders <[log in to unmask]>

Reply-To:

PREMIS Implementors Group Forum <[log in to unmask]>

Date:

Wed, 19 Oct 2005 12:27:58 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (86 lines)

Hi Brian,
Hi everybody,

Brian Tingle wrote:

>What about some sort of XPATH / XPOINTER based inclusion mechanism? 
>
Great ;-)
Xpointer and Xpath is a very good mechanism to link sementical related 
elements; but anyhow we need to know where to store the inital metadata 
and where to store the link. It should be one of  the aims that 
people/programs who are just interpreting the METS or just interpreting 
the PREMIS should get as much information as possible without storing 
information redundant.

- structural information:
I would like - as probably many others as well - want to store 
structural information in METS. Premis provides an own 
relationship-element, which might also describe other relationships than 
just structural ones.
Therefore I would not suggest to remove this element - but I would like 
to suggest using METS to describe an object with it's relations, if METS 
offers possibilites for it (as it does for structural relationships). 
Other relationships, which cannot be handled by METS I would prefer 
using the relationship element from Premis.
It might be difficult here at all to avoid redundancies; therefore I 
would not provide links between METS and PREMIS for redundant information.

- linking from Premis (e.g. checksum information):

METS provides already a possibility to store checksums for files. In 
this case I would like to link the <fixity> information from Premis with 
the CHECKSUM attribute in METS. Theoretically you could link both ways - 
from METS to PREMIS or from PREMIS to METS.
As the checksum is attached to the file very closely, I would like to 
keep in the file section of METS and point from PREMIS to METS.

In this case we need to have a field, in which we might store an 
xpointer. There would be several possibilities to store an xpointer: To 
distinguish if the content of the element is a value or a reference to a 
value, the PREMIS schema should contain an attribute.

As the messageDigestOriginator is not stored in METS, it should be 
amended in the <premis:fixity> element, as it is mandatory according to

In the end it might look somehow like the following example.
<fixity>
    <messageDigestAlgorithm reftovalue="true"> xpointer to CHECKSUMTYPE 
element in mets:file element</messageDigestAlgorithm>
    <messageDigest reftovalue="true"> xpointer to CHECKSUM element in 
mets:file element </messageDigest>
    <messageDigestOriginator>...</messageDigestOriginator>
</fixity>

- linking to Premis:
Linking to Premis might be more complicate almost none of the premis 
elements provide a possibiliy to attach xml identifiers to this element. 
Linking can be done using xpath, but as METS/PREMIS files might become 
very big and complex, chances are high that after modifying a file (e.g. 
by adding new data, new metadata sections), that the path to the 
appropriate PREMIS element would not stay the same.
Are there any objections not to have optional ID attributes for every 
premis element. These ID attributes would be xml-ids.

As we are currently discussing the METS 1.5 schema - see Brians mail on 
METS mailing list from end of july:
<file>

    <Flocat />            <!-- location of *tar.gz file -->
    <transformFile /> <!-- Instructions on reversing gzip -->
    <transformFile /> <! Instructions on reversing tar -->
    <file />                 <!-- first embedded file -->
    <file >                  <!-- second embedded file -->
         <stream />      <!-- first embedded stream -->
         <stream />      <!-- second embedded stream -->
</file>

For the instruction how to transform a file (the <transformFile> element) it would be great to point into a PREMIS enviroment information; i would prefer doing this using IDs as well.


As there are some possibilities linking from and to premis, I don't want to suggest, how we should link things, but for me it seems that we need mechanisms to make linking easier. 


Ciao
Markus

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

April 2021
March 2021
January 2021
December 2020
September 2020
August 2020
July 2020
June 2020
April 2020
February 2020
December 2019
November 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager