1 / 38

NISO Committee AX (OpenURL)

CNRI meeting June 28-29 2001 Herbert Van de Sompel Oren Beit-Arie [edited version with revised terminology, as a result of discussions at the meeting – July 11th 2001]. NISO Committee AX (OpenURL). OpenURL framework fundamental goodies. open reference linking

ivanbritt
Télécharger la présentation

NISO Committee AX (OpenURL)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CNRI meetingJune 28-29 2001Herbert Van de SompelOren Beit-Arie[edited version with revised terminology, as a result of discussions at the meeting – July 11th 2001] NISO Committee AX (OpenURL)

  2. OpenURL framework fundamental goodies • open reference linking • gives users the freedom to decide where to obtain reference links from

  3. OpenURL framework fundamental goodies • open reference linking • gives users the freedom to decide where to obtain reference links from • OpenURL framework: • collaborative model: • information providers introduce a hook; • hook is URL; • URL is there to deliver metadata and identifiers to service component. • service component: • target of the URL; • provides services when user clicks URL; • user chooses service component. • OpenURL: specification for the URL

  4. OpenURLspecs fundamental goodies • Facilitates the delivery of metadata about a referenced item and about the context in which the item is referenced to a service component as a result of an explicit request • by value delivery: metadata is on the OpenURL • by reference delivery: information is delivered on the OpenURL that allows the service component to fetch (additional) metadata

  5. OpenURLspecs fundamental goodies • Facilitates the delivery of metadata about a referenced item and about the context in which the item is referenced to a service component as a result of an explicit request • by value delivery: metadata is on the OpenURL • by reference delivery: information is delivered on the OpenURL that allows the service component to fetch (additional) metadata • Service component will provide contextualizedservices relating to the referenceditem based on the delivered metadata • concrete behaviour/actions of the service component is not specified

  6. Motivation for Bison-Futé Bison-Futé is about taking a step backwards in order to see the picture more clearly. looking at contextual provision of services relating to referenced items without making assumptions that have been made in OpenURL framework & OpenURL specs not l’art pour l’art: using the newly gained perspective to inform the OpenURL standardization process

  7. Motivation for Bison-Futé OpenURL framework choices/assumptions have been made OpenURL

  8. Motivation for Bison-Futé OpenURL framework • choices/assumptions have been made • referenced item is a scholarly work • the terminology of the framework is specific for scholarly information environment • the OpenURL specs are focused on scholarly environment OpenURL

  9. Motivation for Bison-Futé OpenURL framework • choices/assumptions have been made • 2 contextual entities • the “source” (service providing OpenURL) • service component OpenURL

  10. Motivation for Bison-Futé OpenURL framework • choices/assumptions have been made • way to reference the item: • metadata-zone • global-identifier-zone • local-identifier-zone OpenURL

  11. Motivation for Bison-Futé OpenURL framework • choices/assumptions have been made • way to reference the 2 contextual entities: • origin-description • BASE-URL • local-identifier-zone OpenURL

  12. Motivation for Bison-Futé OpenURL framework • choices/assumptions have been made • way to encode as URL • name=value pairs • target at service component OpenURL

  13. Bison-Futé model web ContextObject descriptor ------------ Motivation for Bison-Futé OpenURL framework • choices/assumptions have been made: • scholarly domain • within that domain: • the entities involved • the way to reference entities • the way to encode references to entities on a URL OpenURL

  14. Remember it is all about delivery of metadata of the referenced item and of contextual entities

  15. Bison-Futé: ContextObject • OpenURL makes choices regarding the entities that must be involved in the contextual provision of services • local-identifier-zone has been (ab)used for provision of contextual information that OpenURL does not explicitely support (service types)

  16. Bison-Futé: ContextObject • OpenURL makes choices regarding the entities that must be involved in the contextual provision of services • private-identifier-zone has been (ab)used for provision of contextual information that OpenURL does not explicitely support (service types) • => ContextObject • the ContextObject is a construct that -- we think -- contains all entities that are required for the contextual provision of services

  17. entity resolver requester serviceType referring entity referrer referent ContextObject

  18. Bison-Futé: descriptor • OpenURL makes choices regarding the way to reference the entities that are involved in the contextual provision of services • The way in which these references are made is different from entity to entity • local-identifier-zone has been used to reference entities in ways not supported by OpenURL

  19. Bison-Futé: descriptor • OpenURL makes choices regarding the way to reference the entities that are involved in the contextual provision of services • The way in which these references are made is different from entity to entity • private-identifier-zone has been used to reference entities in ways not supported by OpenURL • => descriptor • descriptor is a uniform construct tailored for referencing all entities involved in the contextual provision of services (we think) • descriptor serves the purpose of delivering identifiers and metadata of entities • descriptor builds on the “by value” and “by reference” concept of OpenURL

  20. descriptor entity resolver requester serviceType referring entity referrer referent ContextObject

  21. Bison-Futé: descriptor • A descriptor describes an entity by means of: • entity-id • metadata-id • metadata-description • metadata-description-pointer • private-identifier

  22. Bison-Futé: descriptor -- entity-id • A descriptor describes an entity by means of: • entity-id • NID & identifier that is unique in namespace identified by NID • doi & 10.1074/jbc.M004545200 • serves 2 purposes: • delivery of identifier = first class citizen • identifier can be a key to access metadata (think CrossRef) • by value & by reference

  23. Bison-Futé: descriptor -- metadata-id • A descriptor describes an entity by means of: • metadata-id • NID & identifier that is unique in namespace identified by NID • pmid & 10942764 • serves 2 purposes: • delivery of identifier of metadata description = first class citizen • identifier can be a key to access metadata (think PubMed) • by value & by reference

  24. Bison-Futé: descriptor -- metadata-description • A descriptor describes an entity by means of: • metadata-description • MFTID & metadata description rendered according to the format identified by MFTID • PubMedSGML & record formated according to PubMedSGML • serves purpose: • delivery of metadata description • by value

  25. Bison-Futé: descriptor -- metadata-description-pointer • A descriptor describes an entity by means of: • metadata-description-pointer • MFTID & explicit pointer to metadata description rendered according to the format identified by MFTID • PubMedSGML & URL pointing at record formated according to PubMedSGML • serves purpose: • delivery of metadata description • by reference

  26. Bison-Futé: descriptor • A descriptor delivers metadata by value & by reference: • by value: • entity-id • metadata-id • metadata-description • by reference: • no intelligence required to get to metadata • metadata-description-pointer • intelligence required to get to metadata: • entity-id • metadata-id

  27. referent resolver referrer referring entity requester serviceType ContextObject entity-id metadata-id metadata-desc metadata-desc-ptr private-zone descriptor

  28. closed link reference to referent service click

  29. encoding descriptor ContextObject encoding referent resolver requester referring entity referrer serviceType private zone OpenResolutionLink click resolver service ....s resolves referent’s descriptor into services reference to referent

  30. OpenURL standardization & Bison-Futé • use Bison-Futé for its concepts only, as inspiration for the standardization process • get real ! Byelimination: use only those parts of Bison-Futé that are essential for making fast progress in the core area (open reference linking) • Within the core area apply a phased approach • 1st: encoding scheme for simple OpenURL’s (meaning of simple to be defined) • 2nd: encoding scheme for complex OpenURL’s (meaning of complex to be defined)

  31. Example of procedure • Simple OpenURL’s: • only 1 referent • only use certain entities of ContextObject • only use certain parts of descriptors to describe entities • only certain namespaces • only certain metadataformats

  32. Example of procedure ContextObject descriptor y/n # id mid mdesc mdescpt mpid referent resolver referrer referring e requester serviceType

  33. Example of procedure ContextObject descriptor y/n # id mid mdesc mdescpt mpid referent y 1 resolver y 1 referrer y 1 referring e y 1 requester n 0 serviceType y 1

  34. Example of procedure ContextObject descriptor y/n # id mid mdesc mdescpt mpid referent y 1 y y y y y resolver y 1 y -- -- -- -- referrer y 1 y -- -- -- -- referring e y 1 y -- -- -- -- requester n 0 -- -- -- -- -- serviceType y 1 y -- -- -- --

  35. OpenURL ContextObject descriptor y/n # id mid mdesc mdescpt mpid referent y + ( same ) y *-- y resolver y 1 y -- -- -- -- referrer y 1 y -- -- -- -- referring e n0 ---- -- -- -- requester n 0 -- -- -- -- -- serviceType n 0 -- -- -- -- -- Bison-Futé’s ContextObject descriptor OpenURL y/n # id mid mdesc mdescpt mpid referent y 1 y y y y y resolver y 1 y -- -- -- -- referrer y 1 y -- -- -- -- referring e y 1 y -- -- -- -- requester y 1y -- -- -- -- serviceType y + y -- -- -- --

  36. Example of procedure • Determine: • regarding id, mid: • global namespaces that are crucial for open reference linking (referent, resolver, ….) • define; • accord NIDs. • allow local namespaces? how to distinguish from globals?

  37. Example of procedure • Determine: • regarding id, mid: • global namespaces that are crucial for open reference linking (referent, resolver, ….) • define; • accord NIDs. • allow local namespaces? how to distinguish from globals? • re mdesc, mdescpt: metadataformat(s) that are crucial for open reference linking (referent). • define • accord MFTID

  38. Example of procedure • Determine: • regarding id, mid: • global namespaces that are crucial for open reference linking (referent, resolver, ….) • define; • accord NIDs. • allow local namespaces? how to distinguish from globals? • re mdesc, mdescpt: metadataformat(s) that are crucial for open reference linking (referent). • define • accord MFTID • Spec to encode everything as URL => Revised OpenURL

More Related