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  April 2002

MODS April 2002

Subject:

Re: Alternate proposal

From:

"Rebecca S. Guenther" <[log in to unmask]>

Reply-To:

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

Date:

Thu, 4 Apr 2002 09:36:58 -0500

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (101 lines)

Concerning the "display form", to give a little background on that element
in MODS: It specifies as a comment that the name is assumed to be
structured, meaning entry form, i.e. surname before forename (or whatever
corresponds to that in the given language). The element "displayForm" is
intended for how it would appear in an unstructured form. Part of the
rationale behind this is from my work with the publishing community,
particularly ebook community, where it is a legal requirement for them to
include the name of the author as it appeared on the work. At one point in
MODS development we talked about two different elements, one called
"file-as" (for the structured) and the other "displayForm". We decided
instead to use the "file-as" form as the default, structured form that
would be expected and added this "displayForm. You will notice that the
mapping uses 245$c for displayForm; of course there may be extraneous
information in 245$c as well as the display form of the name. (In our
ONIX/MARC mapping we also used 245$c for this element which exists in
ONIX.

Rebecca


On Wed, 3 Apr 2002, Geoff Mottram wrote:

> > > I still like the idea of a "display form" element to
> > > distinguish between
> > > sorting and display versions of a field. How would that
> > > affect the idea of
> > > pulling all "text" data from a field?  For example:
> > >
> > > <creator>
> > >     <name>
> > >         <first>Geoff</first>
> > >         <last>Mottram</last>
> > >         <displayForm>Mottram, Geoff</displayForm>
> > >     </name>
> > > </creator>
> > >
> > > Collapsing this name field would be somewhat problematic.
> >
> > To me the <displayForm> is redundant and you are obviously
> > mixing content with presentation.  Something the HTML folks
> > have gotten sorely whipped for doing and was one of the
> > driving reasons why XML came into existence.  You should
> > markup content not try to present it.  That's what XSLT and
> > to a lesser degree CSS is for.  I only need to know the
> > content for <first> and <last>.  Your <displayForm> can be
> > derived from those two elements.  In your system maybe you
> > want to display <name> to your users in the AACR2 form.
> > Maybe I want it displayed as <first> followed by <last>.
> > Different communities will have different standards.  By
> > marking up the content only, each community can extract the
> > relevant content and present it appropriately.
>
> I will have to disagree with you here.  I don't see "displayForm" as
> presentation in the same way that font specifications and layout commands
> are.  I also think you are expecting too much of your data consumers.  If
> you want to subfield your data extensively, it should still be easy for a
> user of your data to display it without having to understand your content
> model.
>
> At the simplest level, MODS should contain the filing version of a field
> and, if its different, a display version.  I shouldn't have to figure out
> what's a first name, a last name or whatever in order to display the record.
> I may not understand anything about the cultural norms for the group who
> created a MODS record and it shouldn't matter.
>
> > This is my biggest complaint about the MODS examples where
> > LC assumes that copying the AACR2 data is good enough.  It's
> > not.  AACR2 is a kind of a specialized markup, where instead
> > of using tags, like XML, it uses punctuation to separate the
> > various content elements.  Using punctuation to separate
> > content elements is bad from an internationalization point
> > of view.  For example a semicolon (;) commonly used in
> > English for these situations is equivalent to question mark
> > in Greek.  When marking up AACR2 data, you should markup the
> > content and throw away the punctuation.  The punctuation can
> > be derived for presentation or conversion purposes.
>
> What's wrong with using whatever punctuation is appropriate for the language
> in use in a given record?  A Greek record would use whatever punctuation
> they would normally use.  If you remove punctuation, I fear an extreme
> amount of markup required and make the standard too difficult to implement.
>
> > However, after having been a little harsh on LC in the prior
> > paragraph, by incorporating the content model I proposed, in
> > an earlier message, into MODS, LC could plop the AACR2 textual
> > string into an element and my community could add refinement
> > elements for the AACR2 textual string.  Thus, LC and my
> > community would both be completely working within the confines
> > of the framework.  Refinements for AACR2 textual strings would
> > probably require my "smart" XSLT transforms to derive the
> > appropriate punctuation when collapsing the refinement
> > elements.  Obviously, refinement elements and "smart" XLST
> > transforms could, and probably should, be shared across
> > communities.
>
> I am concerned with any proposal that requires transforms in order to use
> the data.  A well designed schema should suffice for most users.
>
> Geoff Mottram
>

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

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