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:

Ray Denenberg <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Tue, 9 Aug 2005 14:32:06 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (60 lines)

If this is a real requirement I believe the only sensible solution is the
straightforward one (that I think Matthew is suggesting), that is, add
another parameter -- next version of course. Call it something like
'container', with two sub-parameters (1) name/id of a container schema, e.g.
mets; and (2) one or more "base" schema name/ids, e.g. mods, rec, dc. Or,
if we insist that we cannot have structured parameters in the request then a
space separated list of schema names where the first is a container and
those following are base schemas. Or this could be defined as an extension.

But the point is, don't make it any more complicated than that -- in
particular don't overload the existing schema parameter. Hopefully we've
learned that lesson from Z39.50, where ironically it was almost the exact
same problem we were solving more than 10 years ago, widely cited as a
requirement, we spent enormous effort solving it for version 3, and it was
never widely implemented, if at all -- I don't know if the reason was that
the solution was so complicated or if people decided it really wasn't a
requirement after all. But (1) we really did make it more complicated than
it needed to be, and (2) we really didn't adequately scope out the problem.

I think we've learned our lesson about overloading parameters in the name of
compatibility, and the solution to this problem isn't terribly
omplicated -- however I remain skeptical about whether this is a real
problem - real in the sense that if we solve it (in a reasonable fashion)
people will implement the solution.

--Ray


----- Original Message -----
From: "Matthew J. Dovey" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Tuesday, August 09, 2005 12:30 PM
Subject: Re: rec context set schema


> What's to stop us defining a (potentially infinite) group of
> new schemas, each identified by a URI of the form
> http://loc.gov/sru/mets/<path-to-some-other-schema>
> each of which represents METS records using that nominated schema?

I think the problem here is that a METS record is typically a container
for multiple formats.

So for instance a returned METS record might include the object itself
as an OpenOffice XML doc, the metadata about the object as a MODS XML
doc and the metadata about the record as a rec XML doc (all neatly
wrapped in METS).

So my request would need to be something like
http://loc.gov/sru/mets/path-to-OpenOfficeXMLSchema&path-to-MODS-schema&
path-to-rec-schema - which is workable but messy (and would require a
similar messy mechanism for MPEG21 DIDL and any other wrapper schema)

A neater solution might to be consider how to ask for multiple schemas
within a generic wrapper schema explicitly rather than overloading the
mets/DIDL/etc. schema name - with wildcard support it may even meet
Theo's needs.

Matthew

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