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

MODS November 2003

Subject:

Re: Reusing MODS elements

From:

"Rebecca S. Guenther" <[log in to unmask]>

Reply-To:

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

Date:

Fri, 7 Nov 2003 11:05:17 -0500

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (129 lines)

Yes, I guess assigning URIs to elements is another issue, and one that we
haven't clearly worked out, nor do we completely understand yet. I was
told that the point of it was to be able to do just this, reuse elements,
but I realize now that there are some technical issues that need to be
addressed in the schema itself. And you are right, there is no commitment
to getting something at the other end when you use that element URI
(ideally it would be some documentation about it). We need to take that
issue separately.

I agree that it is worth doing something about this in the schema, and Ray
is going to send a message to the list about it. In any case, we would
need to do something because the DC-Library Application Profile uses some
MODS elements. At some point when that is completed someone will write a
schema for it and will need to use a few MODS elements (location and
edition).

Rebecca

On Thu, 6 Nov 2003, Robin Wendler wrote:

> Hi, Rebecca --
>      As others have pointed out for me (thank you!), I need to be able to
> use the "ref" attribute of XML or another mechanism to say within
> an XML schema that a particular element from MODS is to be considered
> valid, and in such a way that a standard XML parser could determine if an
> instance document with that element is valid.
>
> "Ref" must point to a global element in the target namespace. If an element-
> level URI can help me do that, I do not know how. And from what I remember
> of CORES, there wasn't any expectation that the URIs would be actionable.
> Thus, even if XML schema provided the mechanism to use them to invoke an
> element definition, which I don't think it does, there's no guarantee that
> anything would be on the other end, or that if there was something that it
> would be machine-interpretable.
>
> As you know, I love that fact that MODS enables element hierarchy. What I
> am suggesting would not get rid of that. It would, however, enable the use of
> individual components such as edition, frequency, etc. in other schemas
> without requiring that they enable the entire, for example, originInfo element.
> originInfo is the most compelling case I see in MODS. That groups several
> things which do not depend on the context of their parent to be meaningful.
> In contrast, the subelements of name are not independent characteristics.
> This might be an unacceptable can of worms, but I think it's worth looking
> into.
>
> --Robin
>
> At 05:29 PM 11/5/2003 -0500, you wrote:
> >Robin:
> >
> >There may be some technicalities with XML schema that makes this true that
> >I don't know. But I thought that the real issue is whether you can
> >identify a metadata element with a URI. If you can, then you could use it
> >in another schema. We have been involved in an agreement (CORES) to
> >provide URIs for our metadata elements. This would apply to MARC elements
> >as well as MODS element. For the moment, we would start with giving a
> >policy for assignment of persistent URIs for elements. In the future, we
> >would mark up our documentation explicitly using these URIs for the
> >elements. So, in fact, there are MODS elements that are used in the
> >DC-Library application profile for the reasons you suggested: that they
> >are metadata elements already defined and just as though they can be
> >referenced with a URI they could theoretically be used.
> >
> >The article in D-Lib magazine is:
> >http://www.dlib.org/dlib/july03/baker/07baker.html
> >In the article it gives some examples of likely assignments. One is:
> >http://www.loc.gov/mods/originInfo.edition
> >So we've used this convention to refer to a subelement.
> >
> >The elements in the DC-Library application profile that are referenced
> >are:
> >originInfo/dateCaptured
> >location
> >(I admit, there is yet no schema for DC-Lib AP.)
> >
> >In the case of Dublin Core, the documentation does assign URIs for
> >elements, which I think is the reason they can be used globally. In any
> >case, Dublin Core is flat and there is no hierarchy in the elements, which
> >is another reason why all the elements are "global". The hierarchy in MODS
> >is not something we would want to drop.
> >
> >We do have some further work to do to make all this implementable. But I
> >do think the important thing is the ability to reference the element-- and
> >then you would include the namespace of course in any instance or schema
> >that uses the MODS elements.
> >
> >Rebecca
> >
> >
> >On Wed, 5 Nov 2003, Robin Wendler wrote:
> >
> > > Could I beg for a little Schema for Dummies advice?
> > >
> > > Did the MODS schema authors consider making more of
> > > the MODS subelements global elements, and "ref-ing" them
> > > within the larger elements such as originInfo?
> > >
> > > The reason I ask is that in trying to draft an Eresources Management
> > > schema for the DLF ERM Initiative, I would prefer to incorporate
> > > MODS elements rather than define brand new ones where there is overlap.
> > > Unfortunately, XML schema only permits the referencing of global elements,
> > > when what the ERM data dictionary calls for correspond to subelements of
> > > MODS such as publisher and frequency. For example, ERM doesn't
> > > need "place", but I do want to be able to specify which pieces of
> > originInfo
> > > ERM records should use. I can't even "ref" originInfo, either because it is
> > > not global, is a complexType or both. (I wonder if the xlink and Dublin
> > Core
> > > schemas were created the way they were expressly to facilitate the reuse of
> > > their elements in other schemas.)
> > >
> > > Is there another technique that would permit the use of specific MODS
> > > subelements within another schema? The concepts I want are in MODS, but
> > > I haven't found a way to use them.
> > >
> > > The usual apologies for asking dumb questions apply. Thanks,
> > >
> > > --Robin
> > >
> > > Robin Wendler
> > > Harvard University Library
> > > Office for Information Systems
> > > 1280 Massachusetts Ave., Suite 404
> > > Cambridge, MA 02138 USA
> > > 617-495-3724 (W)
> > > 617-495-0491 (F)
> > > [log in to unmask]
>

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

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