LISTSERV mailing list manager LISTSERV 16.0

Help for MODS Archives


MODS Archives

MODS Archives


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

MODS Home

MODS Home

MODS  March 2009

MODS March 2009

Subject:

Re: URL for the current version of mods

From:

Rick Beaubien <[log in to unmask]>

Reply-To:

Metadata Object Description Schema List <[log in to unmask]>

Date:

Fri, 13 Mar 2009 15:40:21 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (119 lines)

The METS Board also has a generic URL that points to the current version 
of the METS schema.  However,  at least the last time we--the METS 
Board--discussed the matter, we agreed that the schema we maintain at at 
the generic METS URL would always be backwards compatible with previous 
versions of METS.  (There have, in fact and alas, been two exceptions to 
this rule--but these were to correct outright schema errors--in 
particular our incorrect xlink target namespace reference).  If we ever 
implement a non-backwards compatible version of METS, we expect both to 
assign it a new version number (version 2) and to make it available both 
at a "generic" version 2 location (something like 
http://www.loc.gov/standards/mets/v2/mets.xsd) and at a specific version 
2 location (something like 
http://www.loc.gov/standards/mets/version21/mets.xsd for version 2.1).  
However, this is a matter that the METS Board should probably take up 
again to make sure we are all still in agreement.

A generic URL for the location of a metadata schema can be a great 
convenience--providing, as Karen notes, that the updates are backwards 
compatible.

Rick Beaubien



Karen Coyle wrote:
> Andrew, it sounds like you are saying that there shouldn't be a 
> generic URL... ? I believe that people asked for it in the past, but 
> maybe it's not a good idea. It seems to work when updates are backward 
> compatible but not when they aren't.
>
> kc
>
> Houghton,Andrew wrote:
>>> From: Metadata Object Description Schema List [mailto:[log in to unmask]] On
>>> Behalf Of Rick Beaubien
>>> Sent: Thursday, March 12, 2009 5:02 PM
>>> To: [log in to unmask]
>>> Subject: [MODS] URL for the current version of mods
>>>
>>> The current version of MODS is available both through a version
>>> specific
>>> URL (http://www.loc.gov/standards/mods/v3/mods-3-3.xsd) as well as a
>>> more generic URL (http://www.loc.gov/standards/mods/mods.xsd).  Can
>>> users count on the more generic URL always pointing to the most recent
>>> version of the MODS schema that is backwards compatible through version
>>> 3.1?  (I believe that there is a break in compatibility between version
>>> 3.0 and 3.1).  Or, to phrase the question a little differently, if a
>>> new
>>> version of the MODS schema was produced that was not backwards
>>> compatible with versions 3.1-3.3, would it replace the 3.3 schema that
>>> is now available via the generic URL
>>> http://www.loc.gov/standards/mods/mods.xsd?  I am asking this because
>>> of
>>> its implications for how the schemaLocation in mods instances should be
>>> set up.
>>>     
>>
>> What goes in xsi:schemaLocation is the namespace URI and a URI to the 
>> XML
>> schema for MODS.  The namespace URI must match the targetNamespace 
>> attribute
>> in the XML schema for MODS which currently is:
>>
>>   targetNamespace="http://www.loc.gov/mods/v3"
>> for the XML schema URI you should be using the version specific URI 
>> in the
>> xsi:schemaLocation attribute of your XML instance document.  
>> Otherwise, as
>> your question suggests when version 4 of the MODS specification comes 
>> out
>> and it is not backward compatible, LC will have to change the target
>> namespace URI to something like:
>>
>>   targetNamespace="http://www.loc.gov/mods/v4"
>> anybody still using version 3 of MODS and who mistakenly used the 
>> generic URI in their xsi:schemaLocation attribute of their XML 
>> instance documents will now have a problem since the targetNamespace 
>> in the XML schema returned from the generic URI will not match the 
>> namespace URI they used in the xsi:schemaLocation attribute specified 
>> in their XML instance documents.  If
>> the XML instance document is being read by an XML parser that is schema
>> aware, then the XML parser will throw an error, otherwise the 
>> application processing the MODS instance document will not know there 
>> is a problem.  The generic XML schema URI should never be used in 
>> xsi:schemaLocation.
>>
>> Unfortunately, the LC web site doesn't make it clear which one you 
>> should be
>> using and when you dereference the generic URI you get back an HTTP 
>> 200 OK
>> status with the HTTP entity containing the latest version of the MODS 
>> schema.
>> What I believe the LC web site should be doing when dereferencing the 
>> generic URI is to respond back with an HTTP 302 Found status and an 
>> HTTP Location
>> header containing the URI to the latest version of the MODS schema.  
>> Then it
>> would be obvious that you should be using the version specific URI 
>> instead
>> of the generic URI.
>>
>>
>> Andy.
>>
>>
>>   
>

-- 
Rick Beaubien
Software Engineer, Research and Development
U.C. Berkeley Library

Contact information:
505-466-6630

88 Herrada Rd
Santa Fe, NM 87508

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 2020
January 2020
December 2019
October 2019
September 2019
August 2019
June 2019
May 2019
March 2019
February 2019
January 2019
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 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
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
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
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
February 2008
January 2008
December 2007
November 2007
October 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
July 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

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager