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: SRU Record Metadata and DCX Schema (was: Price information in SRU responses)

From:

"LeVan,Ralph" <[log in to unmask]>

Reply-To:

SRU (Search and Retrieve Via URL) Implementors

Date:

Thu, 3 Apr 2008 14:34:11 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (92 lines)

Well, Mike and I agree about as often as he and Theo do, so this is
going to be a red letter day!

First, I don't think we should go down the path of creating a schema in
which we encourage folks to dump whatever useful stuff they can think
of.  It smacks of the bib-1 attribute set.

Second, I don't think that the semantics of new elements dropped
randomly into a schema are any better understood than random elements
taken from any other schema.  In other words, I don't think that the
newly added dmd:ralphsStuff element will be any better understood in a
DC record than just dropping onix:price would be.  Just because the
element is defined in our ever-changing schema does not mean that it
will be understood by the client.  And please, don't suggest that schema
versioning will solve that problem.  It is just namespace mangling and
does nothing to help interoperability.

Now, here's where Mike and I probably stop agreeing.  I think we should
just go ahead and do what Theo asks.  He's already said that ONIX is not
an acceptable choice for him because his usual clients don't know what
to do with it.  That said, they probably won't know what to do with an
onix:price element in a DC record either.  But they probably won't blow
up and Theo has reason to believe that the clients will just display the
data to the user who WILL recognize it as price information, even if the
client doesn't.

There is NO easy solution for incorporating unexpected data into an
existing schema, other than hoping that the clients are smart, robust
and flexible.  The growing use of microformats in all sorts of records
depends on that and I think we should too.

Ralph

> -----Original Message-----
> From: SRU (Search and Retrieve Via URL) Implementors
> [mailto:[log in to unmask]] On Behalf Of Ray Denenberg
> Sent: Thursday, April 03, 2008 12:46 PM
> To: [log in to unmask]
> Subject: Re: SRU Record Metadata and DCX Schema (was: Price
information
> in SRU responses)
> 
> 
> 
> From: Mike Taylor
> >Finally, there is the proposal that you posted, namely the ability to
> extend Dublin Core records with elements from the Record Metadata
> namespace.
> I think this is a good and useful proposal, but it has nothing to do
> with
> the particular problem we set out to solve.
> 
> 
> I think you're still not grasping what I'm proposing.
> 
> I'm NOT proposing to extend our DC schema with the RMD namespace.  I'm
> proposing to extend the DC schema with both the RMD namespace AND the
> DMD
> namespace.
> 
> The DMD namespace  will be a discrete set of descriptive metadata
> elements
> that we come up with collectively (just as we did for the DMD
> namespace) one
> of which will be 'price'.  Note that extending DC for RMD was a one
> line
> addition to the schema <xs:any namespace="dmd> , and extending it
> further
> for AMD will be another one line addition <xs:any namespace="DMD">.
> 
> This approach does not have the interoperability problem you cite
> because,
> dmd:price for example,  will be a well-known element from a well-known
> namespace.
> 
> If the person who started this discussion, about price, wants to use
> ONIX,
> fine, but at least we'll have this in place for the next time someone
> has a
> similar need.
> 
> We can simply call this schema DCPlus.
> 
> And I can trivially create the schema that Theo asks for  (DCX)also
> with a
> one-line addition <xs:any namespace="any"> (or something to that
> effect).
> Which I'll do as soon as I'm back in the office (I'm away for a few
> days).
> 
> --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