JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for DC-LIBRARIES Archives


DC-LIBRARIES Archives

DC-LIBRARIES Archives


DC-LIBRARIES@JISCMAIL.AC.UK


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

DC-LIBRARIES Home

DC-LIBRARIES Home

DC-LIBRARIES  February 2005

DC-LIBRARIES February 2005

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Mixing and matching - not always! (was Re: XML schema (fwd)

From:

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

Reply-To:

DC-Libraries Working Group <[log in to unmask]>

Date:

Fri, 11 Feb 2005 09:24:43 -0500

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (94 lines)

At the time that mods:location was added to DC-LAP, we were in MODS
version 2.1 and there were no subelements under <location>. In version 3.0
we decided to make the distinction in MODS between an identifier and a URL
(electronic location), so we redefined location with 2 subelements: <url>
and <physicalLocation>. The latter is equivalent to the previous version's
<location>, i.e. it is for a repository that holds the resource. The
location is DC-LAP is intended for the repository, so we had intended to
make <physicalLocation> a global element. Developers of DC-LAP wanted to
specify the institution that held the resource. There was no plan to use
it for a URL.

When the Usage Board first considered the DC-LAP, the decision was made to
include MODS elements because of the general guidelines that DCMI was
following about reuse of metadata elements that already existed. Initially
this discussion about XML elements vs. RDF properties didn't come up. So
DC-LAP has included the MODS elements for quite some time. When the
Collection Description proposal for IsAvailableAt came up, this is when
the Usage Board started discussing the issue of using MODS elements, since
it was clear that the proposed isAvailableAt had essentially the same
semantics as mods:location. And it has been discussed a few times since
then.

On a historical note, edition/version was almost included in the initial
DC element set in 1995, but was thrown out because it was considered by
some not to be "cross-domain, resource discovery" and too library centric.
Since those criteria seem to be no longer the requirements to define a DC
element, who knows if edition/version may creep in.

Rebecca

On Fri, 11 Feb 2005, Ann Apps wrote:

> Hi All,
>
> Apologies for not explaining what I meant by MODS terms not
> being consistent with DC practice. But I think others have
> explained it for me :)
>
> Another (more simplistic) point about using the MODS terms, in
> particular mods:location.
>
> Looking at the MODS XML schema, mods:location has 2 sub-
> elements, according to the hierarchical XML model:
> physicalLocation and url. They are both optional and can occur
> many times (though physicalLocations must precede urls). Thus if
> the sub-elements were promoted to 'first class' elements (ie could
> be used without the surrounding <mods:location> tags) (and
> assuming it were possible to sort out the definition in RDF terms)
> you would end up with 2 location properties rather than a single
> one.
>
> I understood that mods:location was included in the DC-Lib AP so
> that either a physical location or a digital location (or both) could be
> captured within the same property, not to have separate properties.
>
> The situation at the moment is that you need to write:
> <mods:location>
>   <mods:physicalLocation>My Library</mods:physicalLocation>
> </mods:location>
> for a physical location and:
> <mods:location>
>   <mods:url>http://example.com/mylibrary.</mods:url>
> </mosd:location>
> for a digital location
> [<mods:location>My Library</mods:location> is wrong according
> to the schema.]
>
> Whereas if there were a DCMI property for location, like all DC
> properties, it's value could be represented by either a URL or a text
> string.
>
> It also seems to me that a location property must bear some
> similarity to that needed but not yet decided by the Collection
> Description AP (isAvailableAt, isLocatedAt?).
>
> As for 'edition', this sounds akin to my long-lamented 'version'
> property :). But, joking aside, I do think there is a general need for
> a DCMI edition/version property (I seem to remember a question on
> askDCMI not long ago).
>
>         Ann
>
>
>
>
>
> --------------------------------------------------------------------------
> Ann Apps. IT Specialist (Research & Development), MIMAS,
>      The University of Manchester, Oxford Road, Manchester, M13 9PL, UK
> Tel: +44 (0) 161 275 6039    Fax: +44 (0) 0161 275 6040
> Email: [log in to unmask]  WWW: http://epub.mimas.ac.uk/ann.html
> --------------------------------------------------------------------------
>

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
July 2016
June 2016
May 2016
April 2016
March 2016
January 2016
December 2015
October 2015
June 2015
May 2015
March 2015
September 2014
July 2014
June 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
December 2012
November 2012
September 2012
August 2012
March 2012
February 2012
November 2011
October 2011
September 2011
July 2011
June 2011
January 2011
November 2010
October 2010
September 2010
August 2010
June 2010
May 2010
April 2010
March 2010
February 2010
October 2009
September 2009
June 2009
May 2009
March 2009
February 2009
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
February 2008
October 2007
September 2007
August 2007
July 2007
June 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
December 2005
November 2005
October 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
April 2004
March 2004
February 2004
December 2003
November 2003
October 2003
September 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
November 2002
October 2002
September 2002
July 2002
May 2002
April 2002
March 2002
January 2002
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
July 2000
June 2000
April 2000
March 2000
February 2000
January 2000
December 1999


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager