LISTSERV mailing list manager LISTSERV 16.0

Help for MODS Archives


MODS Archives

MODS 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

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:

Wed, 18 Mar 2009 09:16:59 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (151 lines)

Thanks very much, Ray.

The namespace information page is an really excellent idea--and we METS 
types need to take a page from the MODS book in this regard.  I'm going 
to put this matter on our next METS Board meeting agenda.

Best,
Rick

Ray Denenberg, Library of Congress wrote:
> Ok Rick, we now have the 3.3 schema at 
> http://www.loc.gov/standards/mods/v3/mods.xsd and we'll maintain the 
> latest 3.x version at that URL, as suggested. (Have also put namespace 
> information at http://www.loc.gov/standards/mods/v3).
> --Ray
>
>
> ----- Original Message ----- From: "Rick Beaubien" 
> <[log in to unmask]>
> To: <[log in to unmask]>
> Sent: Tuesday, March 17, 2009 11:51 AM
> Subject: Re: [MODS] URL for the current version of mods
>
>
>> Thanks very much for the clarifications, Ray.
>>
>> I personally would find it clearer, cleaner, safer and potentially 
>> more useful if MODS maintained any generic schema urls at the 
>> integral version level, and if such generic URLS resolved to the most 
>> recent, backwards compatible version of the MODS schema within an 
>> integral version series of MODS schemas.  In other words, I think it 
>> would be better if the most recent version of the mods schema 
>> representing the "http://www.loc.gov/mods/v3" target namespace were 
>> available at "http://www.loc.gov/standards/mods/v3/mods.xsd".  
>> (Offhand I have to wonder how mods users are employing the non 
>> integral version specific, generic mods URL, although I suppose it 
>> does provide a shorthand way of getting to the most recent schema in 
>> an informal context.)
>>
>> Such a practice would also align with the way the METS Board intends 
>> to manage the METS schema generic URL--or at least intended the last 
>> time we discussed the matter.  However, with METS I think we made a 
>> very short-sighted mistake by not including a version 1 designation 
>> in either the target namespace URI (http://www.loc.gov/METS/) or the 
>> generic URL (http://www.loc.gov/standards/mets/mets.xsd) associated 
>> with version 1 of the schema. We are still in Version 1 of METS, but 
>> when and if we move to a version 2 series of the schema, we will 
>> clearly need to add a version designation to the target namespace URI 
>> for version 2 (http://www.loc.gov/METS/v2) as well as create a 
>> generic, version 2 URL 
>> (http://www.loc.gov/standards/mets/v2/mets.xsd) that will always 
>> yield the current METS schema in the version 2 series.
>>
>> Rick Beaubien
>>
>> Ray Denenberg, Library of Congress wrote:
>>> I'll try to address all the points made in this thread.
>>>
>>> -  The most current version of MODS will always be maintainted at:
>>> http://www.loc.gov/standards/mods/mods.xsd
>>> and in addition will be maintained at a version-specific URL.  Since 
>>> 3.3 is the most current version, the schemas at the two URLs
>>> http://www.loc.gov/standards/mods/mods.xsd, and 
>>> http://www.loc.gov/standards/mods/v3/mods-3-3.xsd are identical 
>>> (though at different locations).
>>>
>>> - "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?"   No.  Once we go to version 4.0, then the 
>>> 4.0 schema will be at   http://www.loc.gov/standards/mods/mods.xsd.
>>> We could maintain the most recent 3.x version at 
>>> http://www.loc.gov/standards/mods/v3/mods.xsd   if that would be 
>>> useful. So let's say we have a version 3.4, then 3.5, and then 
>>> 4.0.   Then the version 3.5 schema would remain permanenty at 
>>> http://www.loc.gov/standards/mods/v3/mods.xsd .    Note, we have no 
>>> plans to do this, but we could if there was a demand for it.
>>>
>>> -   "(I believe that there is a break in compatibility between 
>>> version 3.0 and 3.1)."  No, there was a break in compatibility from 
>>> version 2 to version 3.0, but not from version 3.0 to version 3.1.
>>>
>>> -  "I am asking this because of  its implications for how the 
>>> schemaLocation in mods instances should be  set up." schemaLocation 
>>> should never be set to http://www.loc.gov/standards/mods/mods.xsd.   
>>> If you create a MODS record with the intention that it conforms to 
>>> version 3.3 (but not necessarily to any higher version), then 
>>> schemaLocation should  be 
>>> http://www.loc.gov/standards/mods/v3/mods-3-3.xsd
>>>
>>> - On the MODS namespace URI:  when we go to version 4, the namespace 
>>> URI will change.   It will remain the same for all future 3.x versions.
>>>
>>> I've tried to capture all the questions in the thread, let me know 
>>> if I missed any.
>>>
>>> --Ray
>>>
>>>
>>>
>>> From: "Rick Beaubien" <[log in to unmask]>
>>>> 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.
>>>>
>>>> Thanks,
>>>> Rick Beaubien
>>>>
>>>> -- 
>>>> Rick Beaubien
>>>> Software Engineer, Research and Development
>>>> U.C. Berkeley Library
>>>>
>>>> Contact information:
>>>> 505-466-6630
>>>>
>>>> 88 Herrada Rd
>>>> Santa Fe, NM 87508
>>
>> -- 
>> Rick Beaubien
>> Software Engineer, Research and Development
>> U.C. Berkeley Library
>>
>> Contact information:
>> 505-466-6630
>>
>> 88 Herrada Rd
>> Santa Fe, NM 87508 

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

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