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  May 2003

ZNG May 2003

Subject:

Metaresponse

From:

Theo van Veen <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Fri, 23 May 2003 14:33:27 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (50 lines)

- I think the ZNG list should be open for everyone but should still
require people to join via Ray befor sending contributions.

- I agree with Bill Oldroyd that it should also be possible retrieve
fullr records  via a record id, additionallly to to requesting them via
a position in a resultset. The recordid should become part of the
SRU/SRW specifications as request parameter and in the SRU/SRW response.


- With respect to metasearching of several databases on the same system
I think it would be a good step forwards to have a parameter in which we
can specify database names or collection names. When the database name
is returned as a parameter (like recordid) for each record the receiver
can use this for sorting records from different databases.

-   There has been a discussion on the Z39.50 list some time ago with
respect to requesting XML records. I mentioned the idea on DCX: Dublin
Core eXtended. Especially in metasearching the DCX concept can be
valuable. The concept of DCX is explained below and I will submit a
proposal to the DCMI to adopt this concept. I would like to propose
support of DCX (rather than DC) as compulsary in SRU/SRW.
Please give me your opnion on this.

Theo


DCX:
The problem is that there will grow lots of services where DC plus
extensions is being used. The number of slightly different schemas or
metadata application profiles can grow dramatically and it becomes more
difficult for applications to now which schema to request or to provide
in case of metasearching. At the same time most many applications are
capable of ignoring terms that they do not understand and only using
terms that they do understand. To allow the exchange of records with
different schemas but sharing Qualified Dublin Core terms the "DCX"
schema is invented.
DCX means that the XML records are encoding according to the DCMI
guidelines and contain terms from the dc and dcterms namespaces. The
records may contain terms from other namespaces when they could not -
within reason - be expressed by terms from the dc and dcterms
namespaces. It is recommended that as much as possible terms from DCMI
registered elementsets are being used.

So in practice: when a client requests for recordSchema=dcx the server
will return dcx as recordSchema without the need to strip terms that are
not qualified dc and regardless of the schema or application profile
actually being used (as long as it also uses dc). To harmonize the
addition of new terms a registry (or perhaps several) should be
available to store submitted proposals for new terms.

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