← Prev in month ← Prev in thread
Next in thread → Next in month →

FW: [handle-dev] OpenHandle

From
Matthew Dovey <>
Date
2003-04-03T22:05:09+00:00
ID
Thread
FW: [handle-dev] OpenHandle
This looks interesting.

Matthew Dovey
Oxford University

> 
> -----Original Message-----
> From: Hammond, Tony (ELSLON) [mailto:] 
> Sent: Wednesday, March 26, 2003 12:33 PM
> To: ''
> 
> 
> For something different - an OpenHandle servlet:
> 
> 	http://hdl.handle.net/1014/open
> 
> You should be able to try any legitimate handle, eg
> 
> * for Elsevier handle service (1014)
> 
> 	1014/oboe
> 	1014/yads
> 	1014/1
> 
> * for DOI handle service (10)
> 
> 	10.1006/geno
> 	10.1016/S0888-7543(03)00007-7
> 	10.1000/240
> 
> * for Global handle service (0) - the most interesting
> 
> 	0.serv/10
> 	0.na/10
> 
> (service and naming authority handles for DOI)
> 
> Tony
> 
> 
> A few rough edges here and there but anyway. What is it?
> 
> 
> * A simple declarative means for a user to interact with handle
> 
> * Uses the ANSI/NISO OpenURL Framework to query handle and
>   receive back a structured XML response. (OpenURL drafts posted
>   at <http://library.caltech.edu/openurl/Public_Comments.htm>)
> 
> * Alternate responses could include resolution to stored URI,
>   service referral, etc
> 
> * OpenURL Framework allows contextual information to be bundled along
>   with the query/response messaging
> 
> * An RDF schema (using OWL) is defined for the ContextObject Format
>   of the OpenURL Framework
> 
> * A handle is given as an OpenURL Referent Identifier - the full
>   handle record is then returned as Referent Private Data
> 
> * An RDF Schema is defined for a handle record - supports the
>   predefined handle types HS_ADMIN, HS_SITE, HS_SERV, HS_PRIMARY,
>   HS_ALIAS, HS_VLIST
>  
> * Service data is passsed up as ServiceType Identifiers (for service
>   directives - eg authoritative query, etc) or as ServiceType
>   Metadata (service filtering - on index/type), and is passed back
>   as ServiceType Private Data (service messages)
> 
> * Controversial point - handle references are given compactly in
>   handle URIref form - eg <hdl://0.NA/1006#index=200> indicates
>   the handle value at index 200 for the handle 0.NA/1006
> 
> * Handle URIref form is how a handle client would address into a
>   handle resource - suggest that an alternate means of filtering
>   handle values is to use a fragment identifier syntax, eg
>   <#index=2;type=url> to return values of type URL at index 2 
> 
> * In sum - Resource Description Framework over OpenURL Framework
> 
> _______________________________________________
> handle-dev mailing list
> 
> http://www.cnri.reston.va.us/mailman/listinfo/handle-dev
>
← Prev in month ← Prev in thread
Next in thread → Next in month →