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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

ZNG Home

ZNG Home

ZNG  August 2005

ZNG August 2005

Subject:

Re: rec context set schema

From:

Theo van Veen <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Thu, 11 Aug 2005 01:10:04 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (35 lines)

On 10 Aug 2005 at 11:12, Mike Taylor wrote:

>
> What will happen in practice is that when someone needs to ask for,
> say, A Dublin Core record with some record-level metadata, they will
> just make up a schema that contains these things and a URI that
> identifies it. If several people do this separately, they will surely
> end up with different and incompatible schemes. So it seems better to
> me that we provide some guidance.
>

This is exactly the problem. Given the complexity of the current
proposal (the compoundRecordSchema), I will create my local schema
when I need a specific combination of metadata.
The issue is not that it is too complex for SRU. The issue is that no
server-writer will implement this complexity because it is not a real
local requirement to mix and merge according to the
compoundRecordSchema proposal.
So we will end up with servers offering the conventional record
schemes (dc, marcxml) plus a richer local scheme containing dc plus
some elements from rec and some elements from cld etc.

That is in itself not a problem. Ask for DC and you get DC. But it is
a real real pity that no client can tell from explain that the local
scheme offers potentially a lot functionality and contain a lot of
elements that make it worth for the client to request this local
schema or for the client writer to adapt his client.
A server writer is not likely to adapt the server because to handle
comlex requests that cannot be handled when there is no local
requirement (and he won't see them). A client writer however is more
likely to adapt his client because of the availability of useful
metadata elements.

Theo

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