LISTSERV mailing list manager LISTSERV 16.0

Help for PIG Archives


PIG Archives

PIG 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

PIG Home

PIG Home

PIG  August 2007

PIG August 2007

Subject:

Re: Premis in METS: versioning

From:

Zhiwu Xie <[log in to unmask]>

Reply-To:

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

Date:

Wed, 29 Aug 2007 09:22:08 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (82 lines)

Thanks a lot for the comments, Evan.

We've been discussing the compatibility issues for many times within the 
PREMIS-EC. The initial conclusion seems to be that maintaining 
compatibility with version 1 of the schema is going to be very 
difficult, because the revisions of both the data dictionary and the XML 
schema have touched the structure of many semantic units that the 
existing XML schema compatibility techniques are not going to help. Our 
goal then moves to develop an extensible PREMIS schema version 2 and 
hopefully provide more compatibilities thereafter. For systems that 
already implemented PREMIS v1, we may provide a XSLT file to assist the 
transition.

We are, indeed, in the process of incorporating some <other>-like 
elements in the PREMIS schema v2. I would like to welcome all schema 
experts to join us help developing and evaluating the new schema before 
it goes public. Anyone interested please contact me at [log in to unmask]

Thanks a lot,

Zhiwu Xie





Evan Owens wrote:
> The discussion of version identifiers in PreMIS in METS caught my eye.
>  
> In the XML DTD world, it is really important to indicate the DTD and DTD 
> version to which the document instance conforms.  We at Portico see lots 
> of publisher e-journal XML and SGML files where it is not at all 
> clear what DTD goes with what instance. 
>  
> In the XML schema world where namespaces are being used to merge several 
> schemas, it is not clear to me that anything is necessary beyond 
> well-constructed namespaces that indicate proper versioning.   Redundant 
> information only raises the issue of what to do when there is a conflict 
> and doesn't really gain much. 
>  
> The larger question for all of us is whether or not we expect to be 
> maintaining objects in our archives that have metadata in 
> different versions of the same schemas at the same time. I personally 
> cannot see any answer to that but yes, but that idea has driven some of 
> our programmers crazy.   At a minimum, we expect to have technical 
> metadata in different versions as it would be painful to have to 
> reprocess all objects immediately before implementing a new technical 
> metadata standard. And we may well have different METS versions in use, 
> at least temporarily. To make that happen, we have to have really good 
> control on versioning; in our case, through namespace identifiers.  
> There is a cost in maintaining the patchwork set of schemas that we all 
> use (METS, technical MD, descriptive MD, PreMIS), each with its own 
> versioning and future development path.  It may be that at some happy 
> point in the future all the standards will be stable and unchanging, but 
> I doubt it.        
>  
> The interesting technical question is forwards and backwards 
> compatibility in standards.  There are threads going on right now on the 
> xml-dev list on the topic of compatability and extensibility and 
> versioning of standards, technically and politically.   There is also a 
> really interesting white paper on versioning strategies at the W3C site 
> that presents a useful vocabulary for understanding this problem:
>  
> http://www.w3.org/2001/tag/doc/versioning.html
>  
> Anyone designing schemas should read this and decide which strategy they 
> have chosen and ask whether that is really what they want.  (grin).   We 
> are rethinking some of our own internal schemas in light of this paper. 
>  
> Evan
>  
>  
> ==================================
> Evan Owens, Chief Technology Officer
> Portico  www.portico.org <http://www.portico.org/>
> [log in to unmask] <mailto:[log in to unmask]> 
> (609) 986 2224
> 100 Campus Drive, Suite 100
> Princeton, NJ 08540
>  
>  

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

February 2024
January 2024
December 2023
August 2023
July 2023
June 2023
March 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
May 2022
April 2022
January 2022
December 2021
October 2021
August 2021
July 2021
June 2021
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