LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


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

CODE4LIB Home

CODE4LIB Home

CODE4LIB  February 2011

CODE4LIB February 2011

Subject:

Re: XML Schema vs Library APIs (OAI-PMH/SRU/unAPI)

From:

Jakob Voss <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Fri, 25 Feb 2011 10:18:14 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (51 lines)

Hi Rob,

 > This is just a rehash of a previous discussion on this list, between
 > us:
 >
 > [log in to unmask]" target="_blank">http:[log in to unmask]
 >
 > So I guess I'm wasting my time ;)

Thanks, I added a link to the previous discussion. You wrote:

> Referring to your blog post, you can say how the four inter-relate:
>
> Schema Identifier uniquely identifies the format.
> Schema Location is a non-unique description of the format.
> Schema Name is a short, human readable, non-unique name for the format
> and Namespace is a non-unique namespace used by the format.

These definitions can help to clarify things, but they are of little 
practical value. The practical question is how to refer to a particular 
format. If you have to manually look at each particular server and 
collection to find out what format is *actually* served, then names and 
identifiers are of little help to code against. Both schema identifiers 
and schema names only help you to guess a format. A precise format needs 
an authoritative reference that you can validate against. If there 
exists an official XML Schema, this and only this schema defines the 
format (or the commonly agreed upon subset that you can work with 
without manually adopting each single data source).

 > A single schema may contain multiple namespaces, and there isn't a
 > unique identifier for a schema.  For example, any simple Dublin Core
 > based syntax must have at least two Namespaces, Dublin Core and the
 > wrapper element. SchemaLocation is not unique as there can be many
 > copies of the same schema.  A single schema may define multiple root
 > elements, such as MODS does with both item and collection level
 > elements.

A unique identifier for a schema is helpful because you do not need to 
actually look up a schema that you already know by its identifier. But 
it's not a must. If there is no single root namespace, you just should 
not use a namespace to point to a particular format.

Ok, enough :-)

Jakob

-- 
Jakob Vo▀ <[log in to unmask]>, skype: nichtich
Verbundzentrale des GBV (VZG) / Common Library Network
Platz der Goettinger Sieben 1, 37073 G÷ttingen, Germany
+49 (0)551 39-10242, http://www.gbv.de

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

November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
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
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 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
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 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

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager