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

MODS January 2005

Subject:

Re: Using the <extension> element

From:

Ruth Bogan <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Wed, 12 Jan 2005 15:00:24 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (140 lines)

Jenn,

Thanks for the response. I want to find out more about what you are doing.
In particular, I'd like to see the XML of a record with your categories in
use.

I have a couple of very general question about MODS. I need to start
slowly. At any step I could go horribly wrong and start a landslide :-)

1. Is there any reason we cannot build an application profile based on MODS
(primarily) but incorporating elements from other recognized schemas?
2. If we do this, and declare the various namespaces of the schemas in use,
and preface all the element names with their sources, e.g. <mods:titleInfo>
<cidoc:aquisitionSource> <rulib:objectArchitecture>, do we need to use the
<extension> element?

Ruth



> [Original Message]
> From: Riley, Jenn <[log in to unmask]>
> To: <[log in to unmask]>
> Date: 1/12/2005 1:40:19 PM
> Subject: Re: [MODS] Using the <extension> element
>
> Hi all-
>
> For the exchange listed below, I ended up not using <mods:extension>,
> and instead fitting some of the information into a label attribute.
>
> We are, however, for a different project, using <mods:extension> to
> record information about which of our project categories a specific
> subject-type term falls into. A first draft of this schema can be found
> at <http://www.dlib.indiana.edu/metadata/eviada/eviadacv/eviadacv.xsd>.
> We ended up going with a local schema within <mods:extension> for this
> type of data because we never could find a good way of recording for a
> given term what vocabulary a term originally came from (a lot were from
> LCSH) AND at the same time recording which of our local categories the
> term belonged to (e.g., "Venue" "Culture Group" or "Theme"). So we're
> recording this data in the format most useful for us underneath
> <mods:extension>, and also recording them as subject terms (where
> applicable, some belong in genre) in the MODS document proper (without
> an indication of which project category the term is in), for
> interoperability reasons. This isn't fully implmented yet, but that's
> the plan, at least. :-)
>
> This exact schema outlines our local categories so I'm not sure how much
> use it will be outside of this project, but the idea of <mods:extension>
> for subject categories more granular than MODS offers I think might be
> useful to others.
>
> Jenn
>
> ========================
> Jenn Riley
> Metadata Librarian
> Digital Library Program
> Indiana University - Bloomington
> Main Library E170
> (812) 856-5759
> www.dlib.indiana.edu
>
>
> ________________________________
>
>         From: Metadata Object Description Schema List
> [mailto:[log in to unmask]] On Behalf Of Ruth Bogan
>         Sent: Wednesday, January 12, 2005 10:49 AM
>         To: [log in to unmask]
>         Subject: [MODS] Using the <extension> element
>
>
>
>                 I'm interested in hearing about uses of the <extension>
> element in MODS. I copied out a fairly recent exchange, because this is
> the type of extension I am interested in. I also found a declaration of
> MODS extension for dates that Oxford University uses at
> http://www2.odl.ox.ac.uk/data/aaaaaa/schema/odl.xsd
> <http://www2.odl.ox.ac.uk/data/aaaaaa/schema/odl.xsd>
>
>
>
>         Are there more examples out there?
>
>
>
>         Ruth
>
>
>         Ruth A. Bogan
>         Head, Database and Catalog Portal Management
>         Rutgers University Libraries
>         47 Davidson Rd., Busch Campus
>         Piscataway NJ 08854
>
>
>         Rebecca Guenther to Jenn Riley: 20041104
>
>
>
>         Another alternative might be to use the <extension> element,
> where you can use elements from another schema. Using that you could
> point to the
>
>         namespace for MIX and then use the MIX element.  Here is what it
> would
>
>         like like:
>
>
>
>         <extension><CameraCaptureSettings xmls:
>
>         "http://www.loc.gov/standards/mix/mix.xsd"
> <http://www.loc.gov/standards/mix/mix.xsd> >
>
>         then you would parse the data into its appropriate subelements
> as detailed in MIX. (see: http://www.loc.gov/standards/mix/mix.xsd
> <http://www.loc.gov/standards/mix/mix.xsd>  or the example at:
>
>         http://www.loc.gov/standards/mix/instances/mix_test.xml
> <http://www.loc.gov/standards/mix/instances/mix_test.xml> )
>
>
>
>         Another alternative if you are just using this locally is to use
> the
>
>         <extension> element with your own local element, e.g.
>
>         <extension><cameraSettings>100 f 4.5 TL</cameraSettings>
>
>
>
>         The intent of extension is to either use a local element or
> bring in one from another namespace. If the latter, including the
> namespace allows it to validate against that other schema. If you just
> use a local element, it doesn't validate the data under it.

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

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