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  March 2011

MODS March 2011

Subject:

Re: Problems with Import(s)

From:

"Ray Denenberg, Library of Congress" <[log in to unmask]>

Reply-To:

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

Date:

Mon, 21 Mar 2011 11:47:18 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (130 lines)

Wolfgang - several of use here are looking into this (trying to decide
whether we still need a separate XLink schema, etc.) but using a different
namespace is not an option.

There's some history here, not all of which is necessary to describe, but to
summarize: we originally DID use a homemade namespace, and found that
stylesheets would not function properly, and further, that using a namespace
other than the W3C XLink namespace for an XLink schema violates the XLink
standard. 

--Ray

> -----Original Message-----
> From: Metadata Object Description Schema List
> [mailto:[log in to unmask]] On Behalf Of Wolfgang Koller
> Sent: Monday, March 21, 2011 10:48 AM
> To: [log in to unmask]
> Subject: Re: [MODS] Problems with Import(s)
> 
> Dear Ray,
> 
> thanks a lot for the explanation. These are all good reasons for you
> doing so, however that still doesn't solve the problem that mods is
> simply incompatible with other schemas which import from the original
> location if a more or less strict validator/parser is used.
> 
> Have you ever thought about adjusting the namespace so that it actually
> uses a custom one? (you can argue if that is correct since it is just a
> second workaround, but in your case it would greatly improve the
> interoperability with other schemas).
> If xlink is a custom version, I think it would be even more correct to
> use a different name space there.
> 
> After all importing different schemas into the same namespace is often
> not supported because for many parsers the same namespace means the
> same schema location (AFAIK the behavior for different schemas imported
> into the same namespace is undefined by the standard). If the parser is
> graceful and tries to parse both schema locations it will result in
> errors complaining about re-defined elements (because your schema is
> not an addition but a copy).
> 
> Best wishes,
> Wolfgang
> 
> 
> Ray Denenberg, Library of Congress schrieb:
> > The xml.xsd question is more easily answered. Several years ago we
> > were forced to find a way to reduce the number of MODS accesses to
> the
> > W3C server. The reason was that W3C was complaining (loudly) about
> > excessive accesses and threatening to block certain clients. Someone
> > was not properly caching xml.xsd and was in addition validating an
> > inordinate number of MODS records.  This happened a number of times,
> > we were unsuccessful at tracking down the culprit, and as a quick fix
> > changed the reference to LC rather than W3C, and the problem has not
> resurfaced.
> >
> > Xlink is more complicated, although you could use the same
> > justification, even if there weren't additional complications. In the
> > Xlink case, the W3C version simply didn't meet MODS requirements.  I
> > can't recall exactly why, I'm tracking that down, and I'll get back
> to
> > you (but I wanted to respond quickly to the question).
> >
> > --Ray
> >
> >> -----Original Message-----
> >> From: Metadata Object Description Schema List
> >> [mailto:[log in to unmask]] On Behalf Of Wolfgang Koller
> >> Sent: Monday, March 21, 2011 4:53 AM
> >> To: [log in to unmask]
> >> Subject: [MODS] Problems with Import(s)
> >>
> >> Dear all,
> >>
> >> I'm currently working on a schema which uses MODS to track the
> >> bibliographic information of an element.
> >> However, unfortunately, there are several critical imports in MODS
> >> which heavily conflict with other schema which try to import into
> the
> >> same namespace (multiple definitions of the same attributes /
> elements).
> >>
> >> Unfortunately MODS uses its own copy of the xml.xsd schema and the
> >> xlink.xsd schema.
> >>
> >> - As far as I found out, the xlink schema is a separate & modified
> >> version of the original xlink schema which can be found at
> >> http://www.w3.org/1999/xlink.xsd. However from my point of view, it
> >> is heavily dangerous to customize a schema but import it into the
> >> same namespace then. I would recommend defining a own namespace for
> >> your custom schemas (even if they are based on an "official" schema).
> >>
> >> - The same applies for the xml.xsd schema (the official version can
> >> be found at http://www.w3.org/2001/xml.xsd). However there I did not
> >> find any difference in the official and the version hosted by loc -
> >> what's the reason for hosting it own your own?
> >>
> >> Is there any chance that you are going to update mods and reference
> >> the official schemas and/or change the target namespace so that mods
> >> can be combined with others schemas trying to import the official
> ones?
> >>
> >> Best wishes,
> >> Wolfgang
> >>
> >> --------------------------------------
> >> Information gemaess UGB Par. 14 Abs. 1
> >>
> >> Naturhistorisches Museum
> >> 1010 Wien, Burgring 7
> >> Firmenbuchnummer: FN 236724z
> >> Firmenbuchgericht: Handelsgericht Wien
> >> UID: ATU 38020609
> >> Rechtsform: Wissenschaftliche Anstalt oeffentlichen Rechts des
> Bundes
> >> --------------------------------------
> 
> --------------------------------------
> Information gemaess UGB Par. 14 Abs. 1
> 
> Naturhistorisches Museum
> 1010 Wien, Burgring 7
> Firmenbuchnummer: FN 236724z
> Firmenbuchgericht: Handelsgericht Wien
> UID: ATU 38020609
> Rechtsform: Wissenschaftliche Anstalt
> oeffentlichen Rechts des Bundes
> --------------------------------------

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

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
https://listserv.loc.gov/cgi-bin/wa?A2=ind1103&L=MODS&P=4595
listserv.loc.gov
crawl=CC-MAIN-2020-10
59721
application/http; msgtype=response
sha1:YPQ4NGYD76W5C5JE4BTYAZYAVZUOHRR6
<urn:uuid:2a46d7ad-eeb5-4b06-97a2-211e4ae8e704>
2020-02-21T16:11:22Z
140.147.55.47
text/html
sha1:JNFYHWEAJJ6JKQRM3Z4DPK7BHZCEUD76
<urn:uuid:5aa1a1b1-c364-4a3a-b665-576fea5c8010>
https://listserv.loc.gov/cgi-bin/wa?A2=ind1103&L=MODS&P=4595
response
<urn:uuid:f63c86eb-464c-486b-902d-e0fc025e4d22>
isPartOf: CC-MAIN-2020-10
publisher: Common Crawl
description: Wide crawl of the web for February 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-123.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/