Next in thread → Next in month →

RE: [xri] Fwd: [Asis-standards] FW: NISO Ballot-OpenURL, Z39.88-200X

From
Drummond Reed <>
Date
2004-01-28T05:39:56+00:00
ID
Thread
RE: [xri] Fwd: [Asis-standards] FW: NISO Ballot-OpenURL, Z39.88-200X
Eamonn,

 

Thanks for
the excellent info on OpenURL. This really helps to explain the context.

 

Speaking
on behalf of the XDI TC (which some XRI TC members are involved in and others
are not), we would love to have you involved there. It sounds like it does
fully generalize what OpenURL has been aiming at.

 

Best,

 

=Drummond 

 

-----Original Message-----

From: Eamonn Neylon
[mailto:]

Sent: Tuesday, January 27, 2004
12:14 PM

To: Wachob, Gabe;


Subject: RE: [xri] Fwd:
[Asis-standards] FW: NISO Ballot-OpenURL, Z39.88-200X

 

Hi Gabe

 

OpenURL in bullets:

 

- started life as a means of
transporting metadata packaged in a URL string - hence the name (which is now
something of a misnomer, but since we have not come up with anything better,
we're stuck with it)

- OpenURL really took off in library
community to address appropriate copy problem - looking at local holdings in
preference to an authoritative (chargeable) version of a work

- was supposed to be fast tracked,
but the standardization involved a complete generalization of the earlier work
which was specific to different metadata formats

- the generalization makes it
transport/format independent (was always application independent) in general
terms it allows the use of defined vocabularies (from a registry) in
contextualized applications

- since the transport/packaging is
unspecified, OpenURL metadata packages can be used in arbitrary
applications and allow the mixing of packages of metadata to build up
context(s) in an information exchange

- uses metadata terms directly (by-value)
and indirectly (by-reference) which can be strings or URI identifiers
(was initially a custom identifier syntax, but public review led to the
specification of URIs)

- the use of custom identifiers led to
various feedbacks after which a sub-committee was agreed to establish the info:
URI scheme to allow discussion of common resources that do not already have URI
identifiers

- OpenURL has the potential to make a big
impact, but is currently ghettoised within the library communities (there is
little understanding of it outside this community (even within it there is
suspicion that many will stop at the 0.1 version))

- it is basically the work of two people
(with a couple of agitators ;): Tony Hammond (the more technical, recently
ex-Elsevier and looking for a gig) and Herbert van der Sompel (the organizer,
now at Los Alamos and the driver behind the OAI metadata harvesting protocol)

- they are good guys and would surely like
to have this work developed further.

 

Perhaps I should join in this XDI
initiative after all.

 

Hope this helps - please let me know if
you need more details/insight.

 

Regards

 

Eamonn

 

Eamonn Neylon

Manifest Solutions

Tel: +44 1869 357156

http://www.manifestsolutions.com/ 

-----Original Message-----

From: Wachob, Gabe
[mailto:]

Sent: 27 January 2004 18:25

To: 

Subject: RE: [xri] Fwd:
[Asis-standards] FW: NISO Ballot-OpenURL, Z39.88-200X

Eamonn-

    Do you have a summary
of activity here? We've looked at OpenURL in the distant past and I'm very
curious to hear whats going on there. 

 

    -Gabe

-----Original
Message-----

From: James Bryce Clark
[mailto:]

Sent: Tuesday, January 27, 2004
8:49 AM

To: ;
; ;


Cc: ;


Subject: [xri] Fwd:
[Asis-standards] FW: NISO Ballot-OpenURL, Z39.88-200X

   
FYI to our TCs concerned with distributed resource discovery.   I
have omitted the PDF attachments here.  Jamie

-----Original Message-----

From: NISO Headquarters [mailto:]

Sent: Monday, January 26, 2004
4:17 PM

To: 

Subject: NISO Ballot-OpenURL,
Z39.88-200X

* * * I am pleased to
transmit for ballot the final text of the OpenURL standard, ANSI/NISO
Z39.88-200X. The ballot period is: January 26, 2004-March 10, 2004.

The OpenURL standard is a syntax to create web-transportable packages of
metadata and/or identifiers about an information object. Part 1 of the Standard
introduces the ContextObject; Part 2 lists the initial content of the Registry
to support implementation of the standard.

As you begin your review of the document please take time to read the Foreword
as important background information is provided.

In February NISO will host a conference call-briefing session on this standard.
As soon as the date and time are set you will receive a meeting announcement.
Please send me any questions that come up in your review of the standard; your
questions and early feedback will help frame the agenda for the briefing.

NISO standards represent a consensus built on the dedicated efforts of skilled,
knowledgeable, and very hard working members of our community.  Reaching
the ballot stage is an important benchmark in the standards development cycle;
thanks and congratulations to the members of Standards Committee AX for their
achievement:

Eric F. Van de Velde, Committee Chairperson

California Institute of Technology

Ann Apps

MIMAS-Manchester Computing University of Manchester

Oren Beit-Arie

ExLibris (USA), Inc.

Karim Boughida

Getty Research Institute

Karen Coyle

California Digital Library, University of California (now retired)

Todd Fegan

ProQuest Information and Learning

Tony Hammond

Elsevier Science Ltd.

Eric Hellman

Openly Informatics, Inc.

Lou Knecht

National Library of Medicine

Larry Lannom

Corporation for National Research Initiatives (CNRI)

Clifford Morgan NISO SDC Liaison

John Wiley & Sons Ltd

Mark H. Needleman

SIRSI Corporation

Eamonn Neylon

Manifest Solutions

Philip Norman

OCLC, Inc

Oliver Pesch

EBSCO Publishing

Harry Samuels

Endeavor Information Systems, Inc.

Herbert Van de Sompel

Los Alamos National Laboratory

~   James Bryce Clark

~   Manager, Technical Standards Development, OASIS

~   http://www.oasis-open.org/who/staff.shtml

~   +1 978 667 5115 x 203 central office

~   +1 310 293 6739 direct To unsubscribe from this mailing list (and
be removed from the roster of the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/xri/members/leave_workgroup.php.
Next in thread → Next in month →