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

MODS June 2004

Subject:

Re: Fwd: [MODS] MADS: XML schema for authorities (fwd)

From:

Andrew E Switala <[log in to unmask]>

Reply-To:

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

Date:

Wed, 23 Jun 2004 10:53:29 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (215 lines)

Hi Rebecca,

    I'd briefly commented on this in an earlier post.  On further
reflection, the relationship between authorities and XML namespaces
seems (to me) even closer.  Just as an XML schema defines some or all of
the contents of an XML namespace, a <madsCollection> (or just <mads>)
defines the contents of an authoritative list.  The authority attribute
is analogous to the xmlns pseudo-attribute.  The interpretation of a
<mads> or <related> element with no authority="" would be, as with
namespaces, it inherits the authority of its closest ancestor with an
authority="".
    Both for backwards-compatibility with MODS 3.0, and for
convenience, there should be a mechanism to alias authority URIs, where
some aliases are reserved for LoC use to specify standard lists, like
the namespace prefix "xml:" is fixed by the W3C.  For example, "marcgt"
could be a predefined alias for the authority URI
"http://www.loc.gov/marc/sourcecode/genre/genresource.html".  Maybe
better would be to reserve values for *non-LoC* use, since the lists of
existing authorities are already so extensive (33 for genre alone).  All
user-defined authority URI aliases must begin with a capital letter,
say, or with the string "local:".

--Andy

>>> [log in to unmask] 2004-06-23 09:49:39 >>>
[snip]

As for authority, we made it optional for because there could be a
record
for an entity that is not controlled by a specified authority list.
However, we could use something like "local" as a value for that. As
for
having a defined list of values, we maintain lists of thesauri and
authority files which have hundreds of entries. Also, we add new values
to
these regularly, so wouldn't want to have to maintain a specified list
in
the schema. Couldn't we just use a URI to reference these lists of
values?

Rebecca
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^  Rebecca S. Guenther                                   ^^
^^  Senior Networking and Standards Specialist            ^^
^^  Network Development and MARC Standards Office         ^^
^^  1st and Independence Ave. SE                          ^^
^^  Library of Congress                                   ^^
^^  Washington, DC 20540-4402                             ^^
^^  (202) 707-5092 (voice)    (202) 707-0115 (FAX)        ^^
^^  [log in to unmask]                                          ^^
^^                                                        ^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^


> ---------- Forwarded message ----------
> Date: Sat, 05 Jun 2004 12:18:54 +0200
> From: Stefano Mazzocchi <[log in to unmask]>
> To: simile general <[log in to unmask]>
> Subject: Re: Fwd: [MODS] MADS: XML schema for authorities
> Resent-Date: Sat,  5 Jun 2004 06:18:58 -0400 (EDT)
> Resent-From: [log in to unmask]
>
>
> MacKenzie Smith wrote:
>
> >
> > FYI -- this is possibly relevant to the work on name matching since
much
> > of the name data comes from MARC name authority records, and this
new
> > XML schema is a substitute for that format. It's still XML, but it
> > should make conversion to RDF a lot more straightforward if it's
adopted
> > for the big name authority files like the Library of Congresses.
>
> Not sure how "straight forward" this could be.
>
> I've looked at the schema and it's a very general one, it's used to
> encode a bunch of things with the same exact elements and all the
> semantic information is encoded in attribute values.
>
> For example:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <mads xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>        xsi:noNamespaceSchemaLocation="/mads-v.3.xsd">
>       <authority>
>         <topic authority="LCSH">Computer programming</topic>
>       </authority>
>       <refs>
>         <ref relatedType="broader">
>               <topic>Computers</topic>
>         </ref>
>         <ref relatedType="narrower">
>               <topic>Programming languages</topic>
>         </ref>
>         <ref relatedType="otherRelated">
>               <topic>Systems Analysis</topic>
>         </ref>
>       </refs>
> </mads>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <mads xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>        xsi:noNamespaceSchemaLocation="/mads-v.3.xsd">
>       <authority>
>          <geographic authority="naf">Ceylon</geographic>
>       </authority>
>       <refs>
>          <ref relatedType="later">
>               <geographic>Sri Lanka</geographic>
>          </ref>
>       </refs>
> </mads>
>
> All the semantics is in the attribute values relatedType="" and
> authority="".
>
> relatedType="" values are constrolled by the schema, but the
attribute
> itself is optional.
>
> authority="" values are *not* controlled by the schema and the
attribute
> is optional.
>
> Converting this schema to a useful RDF is algorithmically impossible
> since too much information is kept implicit and/or optional.
>
> The only graph topology that can be inferred from this MADS schema
is
> that some literals have some sort of relationship with others
(optinally
> labelled) and that this relationship is optionally backed up by a
literal.
>
> If all the attributes were required and all the attributes value
were
> controlled and restricted by the schema, then the migration could be
> straightforward.
>
> HTH
>
> > MacKenzie
> >
> >> Date:         Fri, 4 Jun 2004 09:34:04 -0400
> >> Reply-To: Metadata Object Description Schema List <[log in to unmask]>
> >> From: "Rebecca S. Guenther" <[log in to unmask]>
> >> Subject: [MODS] MADS: XML schema for authorities
> >>
> >> In response to numerous requests, the Library of Congress'
Network
> >> Development and MARC Standards Office has drafted an XML schema
for an
> >> authority element set that may be used to provide metadata about
agents
> >> (people, organizations), events, and terms (topics, geographics,
genres,
> >> etc.).  This Metadata Authority Description Schema (MADS) was
created to
> >> serve as a companion to the Metadata Object Description Schema
(MODS).
> >> As such, MADS has a relationship to the MARC 21 Authority format,
as MODS
> >> has to MARC 21 Bibliographic-- both carry selected data from MARC
21.
> >> There is a high level of compatibility between the MADS and MODS
schemas.
> >> MADS is expressed using the XML schema language of the World Wide
Web
> >> Consortium.  Note that once the schema is finalized, a few changes
may be
> >> made to MODS for consistency. An example is that MADS uses the
term
> >> "event" instead of "conference".
> >>
> >> The MADS draft schema is now available for broad review to inform
its
> >> completion. Based on input from prospective users, the schema will
be
> >> revised and made available for experimentation. The review period
will be
> >> between June 4 and July 16, 2004.
> >>
> >> The Web site is at:
> >> http://www.loc.gov/mads
> >> Included is the XML schema itself, a document describing the
purpose of
> >> MADS and details about definitions of the most important elements,
and an
> >> outline of elements and attributes. A mapping to the MARC 21
Authority
> >> Format will be available shortly.
> >>
> >> We look forward to comments from prospective users about this new
schema.
> >>
> >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >> ^^  Rebecca S. Guenther                                   ^^
> >> ^^  Senior Networking and Standards Specialist            ^^
> >> ^^  Network Development and MARC Standards Office         ^^
> >> ^^  1st and Independence Ave. SE                          ^^
> >> ^^  Library of Congress                                   ^^
> >> ^^  Washington, DC 20540-4402                             ^^
> >> ^^  (202) 707-5092 (voice)    (202) 707-0115 (FAX)        ^^
> >> ^^  [log in to unmask]                                          ^^
> >> ^^                                                        ^^
> >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> --
> Stefano.
>
>
>

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