LISTSERV mailing list manager LISTSERV 16.0

Help for METS Archives


METS Archives

METS Archives


[email protected]


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  April 2008

METS April 2008

Subject:

Revised PREMIS schema

From:

"Rebecca S. Guenther" <[log in to unmask]>

Reply-To:

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

Date:

Fri, 4 Apr 2008 16:03:58 -0400

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (81 lines)

I thought that subscribers to the METS and PIG lists might be interested
in some of the features of the new PREMIS schema that were not discussed
in the more general announcement of PREMIS 2.0 that went out yesterday.

1. We have combined what was 5 separate schemas (PREMIS container, Object,
Event, Rights, Agent) into one. This will facilitate maintenance and will
have no practical effect on how it is used. There are 5 root elements
defined, premis, object, event, rights, agent and <premis> may be used as
a container or not. This means that in the case of implementing in METS,
any of the elements may be used as root in appropriate metadata sections
of METS (as was possible in the previous version).

2. We have implemented most of the suggestions made by LANL early in the
PREMIS review process. This includes defining all elements globally so
that they can be reused alone if desired. Secondly, we have separate
definitions for the three levels of object: representation, file, and
bitstream. This will allow us to validate the applicability of a given
element for a specific level of object, which we were unable to do before.

3. We are including a mechanism for extensibility for a number of
elements. This is documented in the data dictionary as well. Thus,
extension elements may use structures from another XML namespace. The
elements that allow for extensibility are:
creatingApplication
environment
eventOutcomeDetail
keyInformation
objectCharacteristics
signatureInformation
significantProperties
rights

Note that the objectCharacteristicsExtension is intended to include format
specific metadata from other schemas-- to be used if an implementer wants
to keep all technical metadata together rather than separated as in METS
in separate techMD sections.

4. We have incorporated some additional constructs for expressing date and
date/time. These are in the draft PREMIS schema now, although we may issue
it as a separate schema later on so that other XML schemas may use it
(e.g. MODS). This includes the ability to encode a date using ISO 8601
basic format (i.e. without the hyphens, which is not covered by xs:date,
but is covered by ISO 8601) and the ability to express special types of
dates. This is like a profile of ISO 8601, discarding unnecessary features
and extending it with features that are needed. Some examples of special
dates that are included are questionable dates, open dates, approximate
dates. For now we are calling this "Extended Date/Time format: edtf"

5. In the next incremental version we will include a mechanism to be able
to specify controlled vocabularies used with PREMIS and validate
them. This will be based on work we are doing establishing a database to
maintain PREMIS controlled values. Those that are in the data dictionary
as "suggested values" will be included in the database and will be able to
be validated by an XML schema. The scheme (or authority) for the
controlled vocabulary will be obvious from the URI used for the controlled
value. Since this is a work in progress, it is not yet ready, but these
are the plans. We will encourage other implementers to contribute their
controlled vocabularies to the database. 

These are the key features. There are also numerous other changes,
including of course all changes to the data dictionary that were made in
version 2.0. Because of the restructuring and significant changes we made,
we have released it as a draft schema so that we can have a one month
comment period.

Please take a look and send comments by April 25, 2008 to Ray Denenberg
([log in to unmask]). Or discuss on this list.

Rebecca
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^  Rebecca S. Guenther                                   ^^
^^  Senior Networking and Standards Specialist            ^^
^^  Network Development and MARC Standards Office         ^^
^^  1st and Independence Ave. SE                          ^^
^^  Library of Congress                                   ^^
^^  Washington, DC 20540-4402                             ^^
^^  (202) 707-5092 (voice)    (202) 707-0115 (FAX)        ^^
^^  [log in to unmask]                                          ^^
^^                                                        ^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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

May 2023
April 2023
March 2023
January 2023
November 2022
December 2021
November 2021
November 2020
October 2020
September 2020
July 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
May 2019
April 2019
March 2019
November 2018
October 2018
September 2018
July 2018
June 2018
April 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
April 2017
January 2017
October 2016
August 2016
July 2016
June 2016
May 2016
April 2016
January 2016
September 2015
August 2015
June 2015
May 2015
April 2015
March 2015
February 2015
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
January 2014
December 2013
October 2013
September 2013
August 2013
June 2013
May 2013
April 2013
February 2013
November 2012
October 2012
September 2012
August 2012
June 2012
May 2012
March 2012
February 2012
January 2012
November 2011
October 2011
September 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
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
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager