1 herbert van de sompel CNRI meeting June 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)

2 herbert van de sompel OpenURL framework fundamental goodies open reference linking gives users the freedom to decide where to obtain reference links from

3 herbert van de sompel 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 herbert van de sompel OpenURL specs 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 herbert van de sompel OpenURL specs 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 contextualized services relating to the referenced item based on the delivered metadata concrete behaviour/actions of the service component is not specified

6 herbert van de sompel 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 herbert van de sompel Motivation for Bison-Futé OpenURL framework OpenURL choices/assumptions have been made

8 herbert van de sompel Motivation for Bison-Futé OpenURL framework OpenURL 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

9 herbert van de sompel Motivation for Bison-Futé OpenURL framework OpenURL choices/assumptions have been made 2 contextual entities  the “source” (service providing OpenURL)  service component

10 herbert van de sompel Motivation for Bison-Futé OpenURL framework OpenURL choices/assumptions have been made way to reference the item:  metadata-zone  global-identifier-zone  local-identifier-zone

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

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

13 herbert van de sompel Motivation for Bison-Futé OpenURL framework OpenURL 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 Bison-Futé model web ContextObject descriptor

14 herbert van de sompel Remember it is all about delivery of metadata of the referenced item and of contextual entities

15 herbert van de sompel 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 herbert van de sompel 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 herbert van de sompel referent referring entity referrer requester resolver ContextObject serviceType entity

18 herbert van de sompel 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 herbert van de sompel 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 herbert van de sompel referent referring entity referrer requester resolver ContextObject descriptor serviceType entity

21 herbert van de sompel A descriptor describes an entity by means of: entity-id metadata-id metadata-description metadata-description-pointer private-identifier Bison-Futé: descriptor

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

23 herbert van de sompel A descriptor describes an entity by means of: metadata-id NID & identifier that is unique in namespace identified by NID pmid & 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 Bison-Futé: descriptor -- metadata-id

24 herbert van de sompel 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 Bison-Futé: descriptor -- metadata-description

25 herbert van de sompel 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 Bison-Futé: descriptor -- metadata-description-pointer

26 herbert van de sompel 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 Bison-Futé: descriptor

27 herbert van de sompel ContextObject descriptor entity-id metadata-id metadata-desc metadata-desc-ptr private-zone referent resolver referrer referring entity requester serviceType            

28 herbert van de sompel reference to referentservice closed link click

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

30 herbert van de sompel OpenURL standardization & Bison-Futé use Bison-Futé for its concepts only, as inspiration for the standardization process get real ! By elimination: 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 herbert van de sompel 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 herbert van de sompel ContextObjectdescriptor y/n# id mid mdesc mdescpt mpid referent resolver referrer referring e requester serviceType Example of procedure

33 herbert van de sompel ContextObjectdescriptor 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 Example of procedure

34 herbert van de sompel ContextObjectdescriptor 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 serviceType y 1 y Example of procedure

35 herbert van de sompel OpenURL ContextObjectdescriptor y/n# id mid mdesc mdescpt mpid referent y + ( same ) y * -- y resolver y 1 y referrer y 1 y referring e n requester n serviceType n Bison-Futé’s ContextObjectdescriptor 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 1 y serviceType y + y

36 herbert van de sompel 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? Example of procedure

37 herbert van de sompel 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 Example of procedure

38 herbert van de sompel 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 Example of procedure