LISTSERV mailing list manager LISTSERV 16.0

Help for ZNG Archives


ZNG Archives

ZNG 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

ZNG Home

ZNG Home

ZNG  April 2008

ZNG April 2008

Subject:

Re: DCX Schema

From:

Theo van Veen <[log in to unmask]>

Reply-To:

SRU (Search and Retrieve Via URL) Implementors

Date:

Fri, 25 Apr 2008 00:20:28 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (192 lines)

As far as I am concerned it is OK. Thanks. 
BTW, I will be on holiday from now on so will not respond to mail for the next two weeks.
 
Theo

________________________________

From: SRU (Search and Retrieve Via URL) Implementors on behalf of Ray Denenberg
Sent: Thu 4/24/2008 8:48 PM
To: [log in to unmask]
Subject: Re: DCX Schema


Theo - I will change the schema as you suggest, if there are no further suggestions or comments.
 
Any comments on this, please post by next Friday, May 2.
 
--Ray

	----- Original Message ----- 
	From: Theo van Veen <mailto:[log in to unmask]>  
	To: [log in to unmask] 
	Sent: Wednesday, April 23, 2008 1:07 PM
	Subject: Re: DCX Schema


	The way we currently use dcx is different. We use a single container to contain dc, dcterms and other namespaces and separate containers for simpleDc,. dcTerms and otherElements. My preferred schema would look like the one below. I do not know if it is possible, but it would be handy if we could also use oai_dc and srw_dc:dc as container name.

	 

	Theo

	___________________________

	<xs:schema

	  xmlns:xs="http://www.w3.org/2001/XMLSchema" 

	  xmlns:dc="http://purl.org/dc/terms/">

	 

	<xs:element name="dcx" type="dcxType"/>

	 

	<xs:complexType name="dcxType">

	     <xs:sequence>

	            <xs:choice maxOccurs="unbounded">

	                  <xs:element ref="dc:title"/>

	                  <xs:element ref="dc:creator"/>

	                  <xs:element ref="dc:subject"/>

	                  ..........

	                  <xs:element ref="dc:mediator"/>

	                  <xs:element ref="dc:educationLevel"/>

	                  <xs:element ref="dc:accessRights"/>

	                  <xs:element ref="dc:license"/>

	                  <xs:element ref="dc:bibliographicCitation"/>

	            </xs:choice>

	            <xs:any maxOccurs="unbounded" namespace="##any" processContents="lax"/>

	      </xs:sequence>

	</xs:complexType>

	</xs:schema>

	 

	
________________________________


	Van: SRU (Search and Retrieve Via URL) Implementors [mailto:[log in to unmask]] Namens Ray Denenberg, Library of Congress
	Verzonden: dinsdag 22 april 2008 23:46
	Aan: [log in to unmask]
	Onderwerp: DCX Schema

	 

	Please see the new DCX schema, at:

	http://www.loc.gov/standards/sru/resources/dcx/dcx.xsd

	 

	I think this schema addresses the issues raised in recent discussion.

	 

	There is a sample instance xml file at:

	http://www.loc.gov/standards/sru/resources/dcx/dcx.xml

	Which tells you just about all you need to know.

	 

	 

	But for those of you with a perverse interest in the convoluted world of namespaces here are a few additional notes, that I don't recommend reading. 

	 

	1.  The schema imports the dcterms schema from the dc website.  That schema in turn references two additional schemas, dc and dcmitype.   I have copied all three schemas to LC and dcx references them from here, because I had to make a small modification for this to work. There is an ambiguity in the definition of the dcterms schema, it is described in a comment I added to the local version at http://www.loc.gov/standards/sru/resources/dcx/dcterms.xsd

	This problem has been reported to the DC folks and when it is resolved we can reference the schema from the official site.  Apparently nobody had tried to combine elements in this fashion so the ambiguity was not discovered. 

	 

	2.  The instance file uses different prefixes for simple dc and dcterms, e.g. dc:title vs. dcterms:alternative, and thus apparent different namespaces. In reality the two namespaces are the same. So you could actually use the dc prefix for all elements and it won't make any difference or have any different meaning.   These are all defined in the same namespace by Dublin Core.    I'm not really sure whether it is a good idea or not to introduce this artificial distinction, and will remove it if people argue that it is not a good idea.  I introduced it because I have the impression from the discussion we had that people want to explicitly segregate the simple elements from the new ones. 

	 

	3. Firefox has a nasty habit of streamlining xml, hiding what it thinks is irrelevant but often is important.  The instance file is better seen with IE.  For convenience, here it is:

	 

	--------------------------------------------------------------------------------------

	 <?xml version="1.0" encoding="UTF-8" ?> 

	- <!-- 

	
	 this is a sample instance document for the dcx schema 

	  --> 

	- <http://www.loc.gov/standards/sru/resources/dcx/dcx.xml>  <dcx xmlns="info:lc/xmlns/dcx-v1" xmlns:dc="http://purl.org/dc/terms/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="info:lc/xmlns/dcx-v1 dcx.xsd">

	- <http://www.loc.gov/standards/sru/resources/dcx/dcx.xml>  <simpleDc>

	  <dc:title /> 

	  <dc:description /> 

	  </simpleDc>

	- <http://www.loc.gov/standards/sru/resources/dcx/dcx.xml>  <dcTerms>

	  <dcterms:alternative /> 

	  <dcterms:audience /> 

	  </dcTerms>

	- <http://www.loc.gov/standards/sru/resources/dcx/dcx.xml>  <otherElements>

	  <mods:genre xmlns:mods="http://www.loc.gov/mods/v3" schemaLocation="http://www.loc.gov/standards/mods/v3/mods-3-3.xsd">fiction</mods:genre> 

	  <other:xyz xmlns:other="info:xxx">xxx</other:xyz> 

	  </otherElements>

	  </dcx>

	------------------------------------------------------------------------

	 

	So you can see that xmlns:dc and xmlns:dcterms are the same namespace. 

	 

	 

	4. Note that the <otherElements> is defined in the schema as validation "lax" meaning that if a schema is supplied, validate, if not, don't. So in the example there are two "other" elements. One is a MODS element and the MODS schema is supplied, so it is validated. For the other, no schema is supplied so there is no validation. 

	 

	 

	--Ray

	 

	 

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

July 2017
October 2016
July 2016
August 2014
February 2014
December 2013
November 2013
October 2013
February 2013
January 2013
October 2012
August 2012
April 2012
January 2012
October 2011
May 2011
April 2011
November 2010
October 2010
September 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
October 2009
September 2009
August 2009
July 2009
May 2009
April 2009
March 2009
February 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
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
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager