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

MODS January 2004

Subject:

Re: Putting nonSort in attributes

From:

Roy Tennant <[log in to unmask]>

Reply-To:

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

Date:

Fri, 23 Jan 2004 09:49:04 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (71 lines)

Frankly, I find it strange to have a <title> tag that is no such thing.
In other words, the <title> cannot be found in the <title>, it must be
found in <nonSort> (if such exists) and <title>. How intuitive is that?
But if that is the collective wisdom of the group, I can live with it.
Meanwhile, to use a local example, this is a sample from one of our
MODS records for our online books (see
<http://texts.cdlib.org/escholarship/>:

<titleInfo>
<nonSort>A </nonSort>
<title>shield in space? [electronic resource] :</title>
<subTitle>
technology, politics, and the strategic defense initiative : how the
Reagan Administration set out to make nuclear weapons "impotent and
obsolete" and succumbed to the fallacy of the last move
</subTitle>
</titleInfo>

It is utterly unusable for any public display (e.g., what is
"[electronic resource]" doing in the <title> tag?!). Thank god we have
another metadata record from an internal UC Press database, from which
we can extract information we can actually put in front of a user. I
would like to see MODS actually become something usable beyond
perpetuating the many mistakes of MARC/AACR2, which I believe is the
rightful role of MARCXML.
Roy

On Jan 23, 2004, at 8:13 AM, Brian Tingle wrote:

>>
>>>>>> [log in to unmask] 2004-01-23 10:20:12 >>>
>>> You should be able to define them as xs:string, in which case white
>>> space is retained. Well, in theory, anyway.
>
>
>> On Fri, 2004-01-23 at 07:30, Andrew E Switala wrote:
>>> Whitespace normalization is done at the level of the XML parser, so
>>> by
>>> the time schema validation happens the attributes have already been
>>> normalized.
>
> On Fri, 2004-01-23 at 07:49, Karen Coyle wrote:
>> Well, it sounds like "the parser" isn't schema compliant.
>
> Well, you have XML parsers, and some of them optionally implement
> schema
> validation and some of them don't.  But an XML parser that is just
> trying to get DOM from a well formed XML document has to make the same
> DOM weather it is bothering to do schema validation or not.
>
>> In which case
>> the same would be true for the strings within the <nonSort> element.
>> So
>> this whole nonSort thing really doesn't work.
>
> That does not follow at all.  He made an assertion about *attribute*
> space normalization rules in XML parsers, not white space in
> *elements*.  My understanding is that whitespace rules in elements are
> not the same as in attributes.
>
>> In which case, we should
>> go with Roy's solution, even though that's not how MARC does it.
>
> Okay, now this is really a stretch.  Please leave it the way it is
> now:)
>
> -- Brian Tingle
>    Content Management Designer
>    California Digital Library
>

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

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=ind0401&L=MODS&P=30711
listserv.loc.gov
crawl=CC-MAIN-2019-35
56355
application/http; msgtype=response
sha1:2BBMC62TAOP4GS4IQJOXVJTTBMET5WMS
<urn:uuid:62f3fb9d-a29c-4abe-9b31-37a6317da277>
2019-08-20T23:35:14Z
140.147.55.47
text/html
sha1:55UUOW5YSYAOVL5OQYWMF2EV5FBVSAE3
<urn:uuid:7f1679d7-ca06-4ef5-832a-9c0322e740e5>
https://listserv.loc.gov/cgi-bin/wa?A2=ind0401&L=MODS&P=30711
response
<urn:uuid:d77bd319-3a9a-4a44-8f32-2207ced3b9e4>
isPartOf: CC-MAIN-2019-35
publisher: Common Crawl
description: Wide crawl of the web for August 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-38.ec2.internal
software: Apache Nutch 1.15 (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/