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

MODS October 2004

Subject:

info:xv proposal

From:

"Ray Denenberg, Library of Congress" <[log in to unmask]>

Reply-To:

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

Date:

Tue, 19 Oct 2004 12:57:39 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (89 lines)

We had an inconclusive discussion several months ago about extensibility of
enumerated values of elements and attributes. I sketched a proposed approach
using 'info' URIs.  There was no response.

We now have a more well-developed proposal and in order to move along with
MADS, as well as the next version of MODS, this time we need some feedback.

As background,
see http://info-uri.info/registry about the 'info' URI,
http://www.loc.gov/z3950/agency/zing/srw/infoURI.html, about how SRW uses
them, and
http://www.loc.gov/z3950/agency/zing/srw/infoURI.html, about how NetRef uses
them.


We propose to introduce the 'info:xv' namespace, where 'xv' is "XML value"

info:xv syntax:
info:xv/<registrationAuthority>/<schema-name>/<part-name>[/<value>]

part-name is an element or attribute name.

Example:
info:xv/1/mods/titleType/    -- identifies the element
info:xv/1/mods/titleType/abbreviated   -- identifies a value
info:xv/1/mods/titleType/translated
info:xv/1/mods/titleType/alternative
info:xv/1/mods/titleType/uniform

1= Library of Congress, LC registers the string "mods" to mean the MODS
schema. It also registers
info:xv/1/mods/titleType/ as the URI for the attribute titleType, and the
latter four URIs to represent the four values.

If another organization wants to register one or more schemas for purposes
of assigning 'info:xv' URIs, then  the 'info:xv' registration authority
would assign a string to that organization, e.g. '2'.  So, conceivably, some
organization (for example the Museum of Discovery and Science) might define
a MODS schema, which would be distinguished from the first MODS schema by
the registrationAuthority string.

The MODS schema would be changed so that these values are not explicitly
enumerated, and the datatype instead is URI. This way, we can add a value
without changing the schema.


Another example, this time an element rather than attribute:
info:xv/1/mods/resourceType/   -- identifies the element
info:xv/1/mods/resourceType/text  -- identifies a value of the element
info:xv/1/mods/resourceType/cartographic
info:xv/1/mods/resourceType/notated music
    (Note we will need to deal with spaces. Either %encode, or change the
values to get rid of spaces.)

Note that the primary purpose of info:xv is to register these enumerated
values for elements and attributes, but that elements and attributes
themselves are also identified, as a side benefit.


---------------------------

Now, there is an outstanding issue that we've kicked around here.  We
originally wanted to allow organizations to define their own (additional)
values for a given element or attribute.  We had drafted the following
syntax:

info:xv/<registrationAuthority>/<schema-name>/<part-name>/[<subRegistrationA
uthority>][/<value>]
(Compare with:
info:xv/<registrationAuthority>/<schema-name>/<part-name>[/<value>]
the difference is an additional registration authority.)

Thus an organization, say LC, would register the MODS schema, and a core set
of values for each given part, but another organization, say OCLC, could
register additional values.
For example, in
info:xv/1/mods/resourceType/1/cartographic
the first '1' is LC who registers MODS, and the second '1' is also LC who
registers the core values. However, in
info:xv/1/mods/resourceType/2/cartoon
the  '1' is still LC, but the '2' is OCLC who has registered an additional
resource type.

Some of us here feel that two registration authorities is much too
cumbersome. (Some think one is; but there doesn't seem to be a way around
it.)  The alternative would be to register all values in a single list. Thus
if your organization had a value to add for a part, it would need to get the
authority for that schema to add it to the list.

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