CNS (NISO Z39.88 2004 The OpenURL Framework for Context-Sensitive Services The Key/Encoded-Value KEV Format Implementation Guidelines ) 96 ( 1D15960125-20)
The OpenURL Framework for Context-Sensitive Services The Key/Encoded-Value (KEV) Format Implementation Guidelines 1....2 2....4 3....7 4....7 5.... 12 6.... 28 7.OpenURL... 69 8.OpenURL... 76 9.OpenURL... 79 10.OpenURL link-to... 82 11.... 82 A... 128 B... 137 C... 141... 144 1
1. OpenURL OpenURL OpenURL ( 0.1 ) OpenURL HTML ( ) HTTP(S) GET POST OpenURL 0.1 ( OpenURL ) URL / XML XML 1.Scope Within the scholarly information community the major application of the OpenURL Framework is to enable context-sensitive linking from a reference in a scholarly information system to resources relevant to the referenced item. Prior to the publication of the OpenURL Framework Standard, applications have been based on the draft OpenURL (now know as version 0.1). The traditional use of the OpenURL Framework is when a user clicks a link or button in an HTML page, typically within an abstracting and indexing database application or the reference list of an electronic journal article. The result of activating this link is to transport a description of a scholarly resource, such as a journal article, to a linking server along with information about the dynamic context of the reference. Passing the dynamic context enables the provision of a list of relevant services 2
appropriate for the user. The Transport is based on HTTP(S) GET or POST and is referred to as an OpenURL. Using OpenURL version 0.1, the information, or payload of the OpenURL, is transported inline as the query string of a URL. The Key/Encoded-Value Format provides a similar means of transporting a description of a reference and its context. The XML Format allows XML descriptions to be transported. / (Key/Encoded-Value, KEV) OpenURL (draft standard for trial use) This document provides implementation guidelines for the Key/Encoded-Value Format. It is not an integral part of the Standard and is for information only. These guidelines will evolve over time as implementation experience is gained. Although it is intended that the OpenURL Framework Standard and the pre-defined content of the Registry will remain static, these guidelines may be updated when deemed appropriate. But note that there were some changes to the Registry during the draft standard for trial use period. This document follows the notational convention used in the Standard in that terms defined in the Glossary of the Standard are shown in italics font. 3
1.1 (Community Profile) San Antonio (San Antonio Community Profiles) (Level 1 KEV) (Level 2 XML ) OpenURL (machine readable definition) (Simple Dublin Core Community Profile) San Antonio C D 1.1 Community Profile A selection from the Registry of a consistent core set of components appropriate to a particular application domain is a Community Profile. The definitions of Community Profiles are also included in the Registry. The San Antonio Community Profiles, Level 1 (KEV) and Level 2 (XML), provide support for the scholarly information community, the community in which the OpenURL Framework originated. The San Antonio Profiles are defined in Appendices C and D of the Standard. They have machine readable definitions and identifiers in the Registry. There is also a Simple Dublin Core Community Profile under development. 2. 2.1 (ContextObject) 4
2.2 (ServiceType) 2.3 (Community Profile) 2.4 (Referrer) 2.5 (ReferringEntity) 2.6 (Referent) ContextObject 2.7 (Dublin Core) 1995 3 (OCLC) National Center for Supercomputing Applications(NCSA) 52 2.8 (Resolver) 2.9 (Digital Object Identifier, DOI) (International DOI Foundation IDF) DOI 2.10 (Requester) 2.Terms and definitions 2.1 ContextObject 5
The description of a referenced resource, and the descriptions of the associated resources that comprise the context of the reference, bundled together are called a ContextObject. 2.2 ServiceType The Entity that defines the type of service requested. 2.3 Community Profile A selection from the Registry of a consistent core set of components appropriate to a particular application domain is a Community Profile. 2.4 Referrer The Entity that generated the ContextObject. 2.5 ReferringEntity The Entity that references the Referent. 2.6 Referent The Entity about which the ContextObject was created a referenced resource. 2.7 Dublin Core The March 1995 Metadata Workshop, sponsored by the Online Computer Library Center (OCLC) and the National Center for Supercomputing Applications (NCSA), convened 52 selected researchers and professionals from librarianship, computer science, text encoding, and related areas, to advance the state of the art in the development of resource description (or metadata) records for networked electronic information objects. 2.8 Resolver The Entity at which a request for services is targeted. 2.9 DOI (Digital Object Identifier) A character string used in a System conforming to the rules of, and deposited in the Directory administered by, the IDF. 6
2.10 Requester The Entity that requests services pertaining to the Referent. 3. ANSI/NISO Z39.88-2004. OpenURL (The OpenURL Framework for Context-Sensitive Services) Registry for the OpenURL Framework. OpenURL OpenURL Syntax Description, Draft version 0.1. OpenURL 0.1 Dublin Core Community Profile (DCCP) for Simple Dublin Core in KEV. 3.Normative reference ANSI/NISO Z39.88-2004. The OpenURL Framework for Context-Sensitive Services Registry for the OpenURL Framework. http://www.openurl.info/registry/ OpenURL Syntax Description, Draft version 0.1. http://www.openurl.info/registry/docs/pdf/openurl-01.pdf Dublin Core Community Profile (DCCP) for Simple Dublin Core in KEV. http://www.openurl.info/registry/docs/pdf/dublincoreprofile.pdf 4. (ContextObject) (Representation) KEV OpenURL 7
4.The ContextObject, its Entities and their Descriptors The description of a referenced resource, and the descriptions of the associated resources that comprise the context of the reference, bundled together are called a ContextObject. It is a Representation of a ContextObject that is transported when a user makes a request by clicking a link. A KEV OpenURL may contain only one ContextObject. (Entities) (Referent) (ReferringEntity) (Requester) Resolver (ServiceType) (Referrer) The ContextObject may contain up to six Entities. One of these, the Referent, conveys information about the referenced item. It must always be included in a ContextObject. The other five entities ReferringEntity, Requester, Resolver, ServiceType and Referrer hold information about the context of the reference and are optional. ( 1 5 ) Jane Doe Elsevier ScienceDirect McArthur, James G. et al. 2001. p27-p16 Chimera: A Superior Antiproliferative for the Prevention of Neointimal Hyperplasia. Molecular Therapy. 3(1) 8-13. <doi:10.1006/mthe.2000.0239> 8
Bergelson, J. 1997. Isolation of a common receptor for coxsackie B viruses and adenoviruses 2 and 5. Science. (275) 1320-1323. <doi:10.1126/science.275.5304.1320> <pmid:9036860> The following scenario is used for illustration (this is the same scenario used in Section 5, Part 1, of the Standard): Jane Doe, a University student at Caltech, reads the following article in the Elsevier ScienceDirect collection: McArthur, James G. et al. 2001. p27-p16 Chimera: A Superior Antiproliferative for the Prevention of Neointimal Hyperplasia. Molecular Therapy. 3(1) 8-13. <doi:10.1006/mthe.2000.0239> In the reference list of that article she finds a reference to the following article and would like to view its full text: Bergelson, J. 1997. Isolation of a common receptor for coxsackie B viruses and adenoviruses 2 and 5. Science. (275) 1320-1323. <doi:10.1126/science.275.5304.1320> <pmid:9036860> 4.1 OpenURL (Resolver) (ServiceType) KEV 9
The Entities of a ContextObject and the constraints on their maximum (Max) and minimum (Min) occurrence are given in Table 3.1. Although the OpenURL Framework allows multiple Resolvers and ServiceTypes their maximum is constrained to one for current KEV community profiles. 4.1 (ContextObject) ContextObject Bergelson 1 1 (Referent) McArthur 0 1 (ReferringEntity) (Requester) 0 1 Jane Doe Jane Bergelson 0 1 (ServiceType) (Resolver) (Referrer) 0 1 Elsevier s 0 1 ScienceDirect Table 4.1 ContextObject Entities Entity Definition Min Max Example Referent The Entity about which the ContextObject was created a 1 1 The article by Bergelson referenced resource ReferringEntity The Entity that references the Referent 0 1 The article by McArthur Requester The Entity that requests services pertaining to the Referent 0 1 Jane Doe 10
ServiceType Resolver Referrer The Entity that defines the type of service requested The Entity at which a request for services is targeted The Entity that generated the ContextObject 0 1 Jane requests the full text of the Bergelson article 0 1 The Caltech linking server 0 1 Elsevier s ScienceDirect (Descriptor) 1 6.2 (1) 1 (info:doi/10.1126/science.275.5304.1320) 2 PubMed (info:pmid/9036860) 3 (mailto:jane.doe@caltech.edu) 4 http URI(http://links.caltech.edu/menu) (2) (By-Value Metadata)( 6 ) (3) (By-Reference Metadata)( 6 ) (4) (Private Data) KEV (Identifier Descriptor) Information about an Entity is detailed by a Descriptor. There are four types of Descriptor, defined in Section 6.2, Part 1 of the Standard. Identifier. For example: A Digital Object identifier 11
(info:doi/10.1126/science.275.5304.1320); a PubMed identifier (info:pmid/9036860); an email address (mailto:jane.doe@caltech.edu); a http URI (http://links.caltech.edu/menu) By-Value Metadata. (Examples are given in Section 6 below) By-Reference Metadata. (Examples are given in Section 6 below) Private Data. In KEV, an Entity may be detailed by multiple Identifier Descriptors. But it may have at most one each of By-Value Metadata, By-Reference Metadata and Private Data Descriptors. 5. 5.Entity Description Each of the six Entities of a ContextObject may be detailed by: several Identifier Descriptors; a By-Value Metadata Descriptor; a By-Reference Metadata Descriptor; a Private Data Descriptor. When a ContextObject contains more than one Descriptor for an Entity all the Descriptors must refer to the same Entity. Guidelines are given below for the description of each Entity. 12
Z39.88-2004 (http://www.openurl.info/registry/docs/info:ofi/fmt:kev:mtx:ctx) KEV Keys for ContextObject component Entities are defined by the Z39.88-2004 Matrix in the Registry at http://www.openurl.info/registry/docs/info:ofi/fmt:kev:mtx:ctx. The Keys available for use in KEV for each Entity are listed in the following subsections. SAP1 6 The values available for Identifier Descriptors are the SAP1 selection from the Registry, listed in Section 6. OpenURL Private Data Descriptors are not defined by the OpenURL Framework Standard. Private data is specific to the providing Referrer, and thus its comprehension requires a prior understanding between a Referrer and a Resolver. Implementers should be aware that the use of Private Data Descriptors could compromise more general interoperability. 6.4 13
KEV By-Value Metadata and By-Reference Metadata descriptions are both based on similar metadata descriptions of an Entity using metadata keys from the Metadata Formats described in Section 6.4. The difference is that for a By-Value Metadata description the metadata is contained within the ContextObject, whereas for a By-Reference Metadata description the metadata is held elsewhere at a network location identified in the ContextObject. Also By-Value Metadata keys are prefixed by an indicator of the Entity to which they refer. In the guidelines below only By-Value Metadata is described, but with the above provisos the guidelines also apply to By-Reference Metadata. Note that an Entity may be described by only one KEV Metadata Format, thus it is not possible to mix Metadata Formats, for example using Keys from both journal metadata and Simple Dublin Core metadata is illegal. 5.1 (Referent) 14
Every ContextObject must have a Referent, the referenced resource for which the ContextObject is created. Within the scholarly information community the Referent will probably be a document-like object, for instance: a book or part of a book; a journal publication or part of a journal; a report; etc. 5.1 The Keys listed in Table 5.1 may be used when describing a Referent. 5.1 KEV rft_id rft_val_fmt rft_ref_fmt rft_ref rft_dat rft. (info:ofi/fmt:kev:mtx:*) (info:ofi/fmt:kev:mtx:*) [ rft_ref] [ rft_ref_fmt] Table 5.1 KEV Referent Keys Key rft_id rft_val_fmt rft_ref_fmt rft_ref rft_dat rft. Description Referent Identifier By-Value Metadata Format (info:ofi/fmt:kev:mtx:*) By-Reference Metadata Format (info:ofi/fmt:kev:mtx:*) [rft_ref also required] By-Reference Metadata Location [rft_ref_fmt also required] Private Data Metadata Key Prefix 15
6.4 Bibcode(Astrophysics Bibcode) ISBN ISSN OAI PubMed SICI 6.3 (National Bibliographic Number, NBN) 6.3 A Referent may be specified using Identifier Descriptors. Identifiers from most of the Namespaces listed in Table 6.4 would be suitable for detailing a scholarly information Referent depending on the particular type of the resource: Astrophysics Bibcode; Digital Object Identifier; ISBN; ISSN; OAI identifier; PubMed identifier; SICI. From the Namespace listed in Table 6.3, a National Bibliographic Number would be a suitable Identifier for a scholarly resource. A Referent may be detailed by multiple Identifiers, in which case all the Identifiers must identify the same resource. Example 6.3 shows a Referent detailed by Identifier Descriptors. 6.4.1-4 6.5( ) 6.6( ) 16
A Referent may be specified using a Metadata Descriptor. Any of the Metadata Formats listed in Section 6.4.1-4 would be suitable for describing a scholarly information Referent depending on the particular type of the resource: Book; Dissertation; Journal; Patent. If a Referent is described by both metadata and Identifiers, these must refer to the same resource. Examples 6.5 (a journal article) and 6.6 (a book)show a Referent described by a Metadata Descriptor. 5.2 (ReferringEntity) (Referent) The ReferringEntity is the Entity that references the Referent. It is optional in the ContextObject. Within the scholarly information community the ReferringEntity could be a journal article that cites the Referent. Or it could be a record within an abstracting and indexing database. 5.2 The Keys listed in Table 4.2 may be used when describing a ReferringEntity. 5.2 KEV rfe_id rfe_val_fmt (info:ofi/fmt:kev:mtx:*) 17
rfe_ref_fmt rfe_ref rfe_dat rfe. (info:ofi/fmt:kev:mtx:*) [ rft_ref] [ rft_ref_fmt] Table 5.2 KEV ReferringEntity Keys Key rfe_id rfe_val_fmt rfe_ref_fmt rfe_ref rfe_dat rfe. Description ReferringEntity Identifier By-Value Metadata Format (info:ofi/fmt:kev:mtx:*) By-Reference Metadata Format (info:ofi/fmt:kev:mtx:*) [rfe_ref also required] By-Reference Metadata Location [rfe_ref_fmt also required] Private Data Metadata Key Prefix 6.4 11.3.2 A ReferringEntity may be specified using Identifier Descriptors. Identifiers from most of the Namespaces listed in Table 6.4 would be suitable for detailing a scholarly information ReferringEntity, as described above for a Referent. A ReferringEntity may be detailed by multiple Identifiers, in which case all the Identifiers must identify the same resource. Example 11.3.2 shows a ReferringEntity detailed by Identifier Descriptors. 18
6.4.1-4 6.6( ) 11.8.2( ) A ReferringEntity may be specified using a Metadata Descriptor. Any of the Metadata Formats listed in Section 6.4.1-4 would be suitable for describing a scholarly information ReferringEntity depending on the particular type of the resource: Book; Dissertation; Journal; Patent. If a ReferringEntity is described by both metadata and Identifiers, these must refer to the same resource. Example 6.6 (a journal article) and 11.8.2 (a book) show a ReferringEntity described by a Metadata Descriptor. 11.3.2 11.4.2 URL 11.6.2 When a ReferringEntity is a record in an abstracting and indexing database it is better to describe it by the record Identifier rather than by metadata, because the metadata for the ReferringEntity will be the same as that for the Referent. Examples 11.3.2 and 11.4.2 show ReferringEntities that are described by 19
public and private information service record data respectively. In some cases a ReferringEntity may be a Web page. For instance a researcher may cite published articles on a Home page. A ReferringEntity that is a Web page can be described by an Identifier that is the URL of the Web page, as in Example 11.6.2. 5.3 (Requester) (Referent) The Requester is the Entity that requests services pertaining to the Referent. It is optional in the ContextObject. Within the scholarly information community the Requester is generally a human end-user who clicks a link within a digital library application. 5.3 KEV The Keys listed in Table 5.3 may be used when describing a Requester. The KEV ContextObject definition also includes Keys for metadata description of a Requester, but the Registry does not currently include any appropriate Metadata Formats. 5.3 KEV req_id 20
req_dat Table 5.3 KEV Requester Keys Key req_id req_dat Description Requester Identifier Private Data 6.3 LDAP mailto 6.2 A Requester may be specified using Identifier Descriptors. Identifiers from the Namespaces listed in Table 6.3 that would be suitable for detailing a Requester are: LDAP; mailto. A Requester may be detailed by multiple Identifiers, in which case all the Identifiers must identify the same resource. Example 6.2 shows a Requester detailed by an Identifier Descriptor. (Private Data) OpenURL Some applications may wish to pass Requester authentication related information. This may be the authentication system used. Or it could be the location information such as the institution or company to which the Requester 21
belongs. Or it could be an Identifier for the Requester that would indicate their preference profile within some system. At present this information would be described using Private Data and will depend on prior understanding by both Referrer and Resolver. It would be inadvisable to include authentication details such as passwords within a Requester Descriptor. As well as concerns about the security of the OpenURL Transport, including such detailed authentication data would probably contravene the terms and conditions of the authentication system in use. 5.4 (ServiceType) The ServiceType is the Entity that defines the type of service requested. It is optional in the ContextObject. Within the scholarly information community the ServiceType could be a request for; the full text of an article; the abstract of an article; an inter-library loan request, etc. 5.4 KEV The Keys listed in Table 5.4 may be used when describing a ServiceType. The KEV ContextObject definition also includes a Key for an Identifier description of a ServiceType, but the Registry does not currently include any appropriate Identifiers. 22
5.4 KEV svc_val_fmt svc_ref_fmt svc_ref svc_dat svc. (info:ofi/fmt:kev:mtx:*) (info:ofi/fmt:kev:mtx:*) [ svc_ref] [ svc_ref_fmt] Table 5.4 KEV ServiceType Keys Key svc_val_fmt svc_ref_fmt svc_ref svc_dat svc. Description By-Value Metadata Format (info:ofi/fmt:kev:mtx:*) By-Reference Metadata Format (info:ofi/fmt:kev:mtx:*) [svc_ref also required] By-Reference Metadata Location [svc_ref_fmt also required] Private Data Metadata Key Prefix 6.4.5 11.2.4 A ServiceType may be specified using a Metadata Descriptor. The Metadata Formats described in Section 6.4.5 would be suitable for describing a scholarly information ServiceType. Example 11.2.4 shows a ServiceType detailed by a Metadata Descriptor. 23
5.5 (Resolver) OpenURL (OpenURL Transport) URL(base URL) URL The Resolver is the Entity at which a request for services is targeted. It is optional in the ContextObject. This need not be the same Resolver as that specified as the base URL for an OpenURL Transport and does not replace that base URL. 5.6 KEV ContextObject The Keys listed in Table 5.6 may be used when describing a Resolver. The KEV ContextObject definition also includes Keys for metadata description of a Resolver, but the Registry does not currently include any appropriate Metadata Formats. 5.6 KEV res_id res_dat Table 5.6 KEV Resolver Keys Key res_id Description Resolver Identifier 24
res_dat Private Data 6.3 HTTP A Resolver may be specified using Identifier Descriptors. An Identifier from the Namespaces listed in Table 6.3 that would be suitable for detailing a Resolver is http. A Resolver may be detailed by multiple Identifiers, in which case all the Identifiers must identify the same resource. 5.6 (Referrer) The Referrer is the Entity that generated the ContextObject. It is optional in the ContextObject, but its inclusion is strongly encouraged. Within the scholarly information community the Referrer will be an information provider such as an electronic journal application or an abstracting and indexing service. 5.7 KEV 25
The Keys listed in Table 5.7 may be used when describing a Referrer. The KEV ContextObject definition also includes Keys for metadata description of a Referrer, but the Registry does not currently include any appropriate Metadata Formats. 5.7 KEV rfr_id rfr_dat Table 5.7 KEV Referrer Keys Key res_id res_dat Description Referrer Identifier Private Data ( info:ofi/nam:info:sid: ) info:sid/ (http://openurl.info/registry/docs/pdf/info-sid.pdf) DNS ( ) info:sid/firstsearch.oclc.org:inspec, info:sid/wiley.com Referrer Identifiers are defined in the source identifier Namespace info:ofi/nam:info:sid:. They are identified using the info:sid/ scheme for the identification of collections of information assets defined in the Registry at http://openurl.info/registry/docs/pdf/info-sid.pdf. Such a collection could be 26
an organization, a website, a publisher, or a database. Within this scheme a Referrer Identifier consists of a DNS identifier (Internet domain name, sub-domain or host name) for the Referrer s collection, followed by an optional name providing further details about the nature of the collection, for example a particular service or database. Example Referrer Identifiers are: info:sid/firstsearch.oclc.org:inspec ; info:sid/wiley.com. 11 It is strongly recommended that genuine Referrer Identifiers are included in ContextObjects. In particular a genuine Referrer Identifier is necessary if Referrer-specific Private Data is included in a ContextObject, in order to define the provenance of that private data. All the examples in Section 11 show Referrers detailed by Identifier Descriptors. Resolvers make use of Referrer Identifiers to avoid circular linking and to compile usage statistics. 1.4 1.3 ofi/rfr:db Note that the Referrer scheme changed from in version 1.4 of this document from version 1.3. The ofi/rfr:db scheme is no longer available. 27
6. KEV OpenURL 6.Registry Selections The following selection of KEV OpenURL Framework components from the Registry would be appropriate within the scholarly information community. 6.1 (ContextObject Format) (Key/Encoded-Value KEV) & ( ) URL (URL-encoded) = KEV URL ( transport ready ) KEV 3 URL B.3 KEV (Registry Identifier) info:ofi/fmt:kev ContextObjects are represented using the Key/Encoded-Value (KEV) Format, as a string of ampersand-delimited pairs. Each pair consists of a label (Key) and an associated Value that is URL-encoded, separated by an equals ( = ). All values of KEV pairs must be URL-encoded so that the ContextObject Representation is transport ready. The KEV Format is defined in Part 3 of the Standard. URL-encoding is explained below in Annex B.3. The Registry Identifier of the KEV Format is info:ofi/fmt:kev. KEV Z39.88-2004 MTX (Z39.88-2004 MTX 28
Constraint Definition) (Registry Identifier) info:ofi/fmt:kev:mtx KEV info:ofi/fmt:kev:mtx:ctx Keys for a KEV ContextObject are defined by the Z39.88-2004 MTX Constraint Definition. The Registry Identifier of the MTX Constraint Definition is info:ofi/fmt:kev:mtx and the Registry Identifier of the KEV ContextObject Format is info:ofi/fmt:kev:mtx:ctx. ( ) KEV As well as defining Keys used to describe the component entities of a ContextObject (see Section 4 above), the KEV ContextObject also includes optional administrative keys for the ContextObject. 6.1: KEV ctx_ver ctx_enc ctx_id ctx_tim Z39.88-2004 (Z ) ( 5.2) (Timestamp) ISO8601 W3CDTF YYYY-MM-DDThh:mm:ssTZD YYYY-MM-DD. Table 6.1 KEV ContextObject Administrative Keys Key ctx_ver Description Version of the ContextObject. Fixed value: Z39.88-2004 ( Z must be uppercase) 29
ctx_enc ctx_id ctx_tim Character Encoding used (see Section 5.2 below) Identifier for the ContextObject Timestamp for the ContextObject, a date and time to the seconds level of the W3CDTF profile of ISO 8601, of the form YYYY-MM-DDThh:mm:ssTZD or YYYY-MM-DD 6.2 (Character Encoding) IANA( ) (http://www.iana.org/assignments/character-sets) KEV The following Character Encodings from the IANA character sets (http://www.iana.org/assignments/character-sets) to be used for Values within a KEV ContextObject are included in the initial Registry, where further description of these character sets may be found. 6.2 KEV UTF-8 info:ofi/enc:utf-8 ISO Latin 1 info:ofi/enc:iso-8859-1 Table 6.2 KEV Character Encodings Encoding Registry Identifier UTF-8 Unicode info:ofi/enc:utf-8 ISO Latin 1 info:ofi/enc:iso-8859-1 ctx_enc 30
UTF-8 ctx_enc (By-Reference Metadata) UTF-8 The Character Encoding used within a ContextObject is specified using the ctx_enc Key. The default Character Encoding is UTF-8. Thus if UTF-8 is used the ctx_enc Key may be omitted. For By-Reference Metadata UTF-8 Character Encoding is the default, but it can declare its own encoding. 6.1 ISO Latin 1 &ctx_enc=info%3aofi%2fenc%3aiso-8859-1 Example 6.1 Character Encoding Specification of ISO Latin 1 Character Encoding &ctx_enc=info%3aofi%2fenc%3aiso-8859-1 UTF-8 OpenURL C(Unicode Normalization Form C) ASCII When forming an OpenURL encoded using Unicode UTF-8, best practice is to use Unicode Normalization Form C. The practice of reducing Unicode characters to ASCII is discouraged. ( ) SAP1 31
Other encoding schemes may be used in the future, provided they are registered, but they will not be included in the scholarly information profile SAP1. 6.3 (Namespaces) (Identifier Namespace) info:ofi/nam: URI mailto info:ofi/nam:mailto: 6.2 mailto:jane.doe@caltech.edu The following sub-sections list the Identifier Namespaces appropriate for the scholarly information community. Namespaces have Registry Identifiers within the info:ofi/nam: Namespace. But for an Identifier Descriptor just the URI is used. For example, the Registry Identifier for mailto is info:ofi/nam:mailto: but an Identifier Descriptor would be mailto:jane.doe@caltech.edu as shown in Example 6.2. 1.1 1.2 URI uri: ORI info: XRI (Private Data Descriptor) Note that this section changed significantly from versions 1.1 to 1.2 of this document. All Namespaces now follow URI schemes and the uri: prefix has been dropped. The previous ORI Namespaces are now URI info: Namespaces. 32
The private XRI Namespace is no longer available and a Referrer-specific identifier should be encoded within a Private Data Descriptor. 6.3.1. (Namespaces) 6.3 info: 6.2 mailto Table 6.3 lists the Namespaces suitable for scholarly information from URI schemes other than the info: scheme. Identifiers from these Namespaces may be used as Identifier Descriptors. They may also be used to specify network locations for By-Reference Metadata descriptions. The following example, 6.2, shows a Requester detailed by a mailto Identifier. 6.2 URI &req_id=mailto%3ajane.doe%40caltech.edu Example 5.2 Requester URI Namespace Identifier Descriptor &req_id=mailto%3ajane.doe%40caltech.edu 6.3 URI URI URI FTP info:ofi/nam:ftp: ftp: HTTP info:ofi/nam:http: http: LDAP info:ofi/nam:ldap: ldap: mailto info:ofi/nam:mailto: mailto: ISBN info:ofi/nam:urn:isbn: urn:isbn: 33
ISSN National Bibliographic Number (NBN) info:ofi/nam:urn:issn: urn:issn info:ofi/nam:urn:nbn urn:nbn: Table 6.3 URI Namespaces URI Namespace Registry Identifier URI FTP info:ofi/nam:ftp: ftp: HTTP info:ofi/nam:http: http: LDAP info:ofi/nam:ldap: ldap: mailto info:ofi/nam:mailto: mailto: ISBN info:ofi/nam:urn:isbn: urn:isbn: ISSN info:ofi/nam:urn:issn: urn:issn National Bibliographic Number (NBN) info:ofi/nam:urn:nbn urn:nbn: 6.3.2 info ( info Namespaces) 6.4 info URI 6.3 PubMed Table 6.4 lists the Namespaces suitable for scholarly information from the info URI scheme. Identifiers from these Namespaces may be used as Identifier Descriptors. The following example, 6.3, shows a Referent detailed by both a PubMed Identifier and a Digital Object Identifier. 6.3 info ( URL ) &rft_id=info:pmid/9036860 &rft_id=info:doi/10.1126/science.275.5304.1320 (URL ) &rft_id=info%3apmid%2f9036860&rft_id=info%3adoi%2f10. 34
1126%2Fscien ce.275.5304.1320 Example 6.3 : Referent info Namespace Identifier Descriptors &rft_id=info:pmid/9036860 &rft_id=info:doi/10.1126/science.275.5304.1320 (URL-encoded) &rft_id=info%3apmid%2f9036860&rft_id=info%3adoi%2f 10.1126%2Fscien ce.275.5304.1320 6.4 info URI Astrophysics Bibcode info:ofi/nam:info:bibcode: info:bibcode/ Digital Object Identifier info:ofi/nam:info:doi: info:doi/ CNRI Handle info:ofi/nam:info:hdl: info:hdl/ LCCN Info:ofi/nam:info:lccn: info:lccn/ Open Archives Initiative (OAI) info:ofi/nam:info:oai: info:oai/ OCLC WorldCat info:ofi/nam:info:oclcnum: info:oclcnum/ PubMed info:ofi/nam:info:pmid: info:pmid/ SICI info:ofi/nam:info:sici: info:sici/ Source Identifier info:ofi/nam:info:sid: info:sid/ Table 6.4 info Namespaces Namespace Registry Identifier URI Astrophysics Bibcode info:ofi/nam:info:bibcode: info:bibcode/ Digital Object Identifier info:ofi/nam:info:doi: info:doi/ CNRI Handle info:ofi/nam:info:hdl: info:hdl/ LCCN Info:ofi/nam:info:lccn: info:lccn/ Open Archives Initiative (OAI) info:ofi/nam:info:oai: info:oai/ OCLC WorldCat info:ofi/nam:info:oclcnum: info:oclcnum/ 35
PubMed info:ofi/nam:info:pmid: info:pmid/ SICI info:ofi/nam:info:sici: info:sici/ Source Identifier info:ofi/nam:info:sid: info:sid/ 6.4 (Metadata Formats) KEV KEV Entities within a ContextObject may be described by metadata. These metadata descriptions may be contained within the ContextObject itself, known as By-Value Metadata. Alternatively the metadata descriptions may be held elsewhere, in which case, known as By-Reference Metadata, the network location of the metadata is contained in the ContextObject. When an Entity is described by KEV By-Value Metadata the metadata keys must have a metadata prefix indicating the Entity. This metadata key prefix should not be used for KEV By-Reference Metadata. 6.5 KEV The initial KEV Metadata Formats are listed in Table 6.5. These Metadata Formats provide a means to describe resources within the scholarly 36
information community. They are described in more detail in the following sub-sections. 6.5 / info:ofi/fmt:kev:mtx:book info:ofi/fmt:kev:mtx:dissertation info:ofi/fmt:kev:mtx:journal info:ofi/fmt:kev:mtx:patent info:ofi/fmt:kev:mtx:sch_svc Table 6.5 Key/Encoded-Value Metadata Formats Metadata Format Book and Book component Dissertation Journal and Journal component Patent Scholarly Service Type Registry Identifier info:ofi/fmt:kev:mtx:book info:ofi/fmt:kev:mtx:dissertation info:ofi/fmt:kev:mtx:journal info:ofi/fmt:kev:mtx:patent info:ofi/fmt:kev:mtx:sch_svc 6.4.1 (Journal Metadata) Z39.88-2004 (http://www.openurl.info/registry/docs/info:ofi/fmt:kev:mtx:journal) The Metadata Format to represent a journal publication is defined by a Z39.88-2004 Matrix in the Registry at: http://www.openurl.info/registry/docs/info:ofi/fmt:kev:mtx:journal. This Matrix includes a description for the use of each of the metadata items. That information is not reproduced here but guidelines for a few of the 37
metadata items are given below. The Matrix defines the permissible occurrences of the metadata keys. ( ) (a) rft_val_fmt ( rfe_val_fmt) info:ofi/fmt:kev:mtx:journal (b) rft. ( rfe. ) When a Referent (or ReferringEntity) is described with By-Value Metadata using the journal Metadata Format: The rft_val_fmt (or rfe_val_fmt) Key in the ContextObject has the value: info:ofi/fmt:kev:mtx:journal The metadata keys must be prefixed with rft. (or rfe. ) ( ) (a) rft_val_fmt ( rfe_val_fmt) info:ofi/fmt:kev:mtx:journal (b) KEV rft_ref ( rfe_ref) (c) (d) UTF-8 When a Referent (or ReferringEntity) is described with By-Reference Metadata using the journal Metadata Format: 38
The rft_ref_fmt (or rfe_ref_fmt) Key in the ContextObject has the value: info:ofi/fmt:kev:mtx:journal The metadata at the location specified by the rft_ref (or rfe_ref) Key is in KEV journal Metadata Format The metadata keys must not be prefixed Character Encoding default is UTF-8, but it can declare its own encoding (1) (genre) 6.6 / / (volume / part / issue) (1) Genre The journal Metadata Format is a general purpose Format to describe all levels within a journal or serial publication. It may also be used to describe a conference proceedings or paper where these are published in a journal, or a serial publication preprint. The specific genre of the resource within the journal publication type may be indicated by the genre metadata key. The possible values for the genre metadata key are shown in Table 6.6. It would be expected that the granularity of metadata provided would be consistent 39
with the specified genre. For example a resource described with a genre issue would have appropriate volume / part / issue metadata. 6.6 (Genre Value) (journal) (issue) (article) (conference) (proceeding) (preprint) (unknown) Table 6.6 Journal Metadata Genre Values Genre Value journal issue Article conference proceeding preprint unknown Description Serial publication issued in several parts One instance of a serial publication Document published in a journal Record of a conference published in a journal Single conference presentation published in a journal Single paper or report published prior to its publication in a journal Unknown genre (2) aulast aufirst auinit aunit1 auinitm ausuffix 40
aucorp au aulast au (2) Author The Journal Metadata Format provides several keys to detail the author of an article or paper. For the purpose of matching citations it is generally the first author s name that is significant. The first author should be specified using aulast to indicate their family name and one or more of aufirst, auinit, aunit1, auinitm for their given name or initials. An ausuffix key may also be used if a name suffix is significant. If the main creator of a document is an organization the aucorp key should be used instead. A general au key is also provided. This may be used to contain the full name of an author where splitting the author s name is not possible. But it is recommended that aulast, with separate family name or initials, be used to specify the first author rather than au whenever possible. The au key is repeatable so may be used to list the co-authors of an article. 6.5 6.6 The following examples show the use of the Journal Metadata Format. Example 6.5 shows By-Value Metadata for a Referent. Example 6.6 shows By-Reference Metadata for a ReferringEntity. 41
6.5 ( URL ) &rft_val_fmt=info:ofi/fmt:kev:mtx:journal &rft.genre=article &rft.atitle=isolation of a common receptor for coxsackie B &rft.jtitle=science &rft.aulast=bergelson &rft.auinit=j &rft.date=1997 &rft.volume=275 &rft.spage=1320 &rft.epage=1323 (URL KEV ) &rft_val_fmt=info%3aofi%2ffmt%3akev%3amtx%3ajournal& rft.genre=article&rf t.atitle=isolation+of+a+common+receptor+for+coxsackie+b&rf t.jtitle=science&rft.aulast=bergelson&rft.auinit=j&rft.date=19 97&rft.volume=275&rft.spage=1320&rf t.epage=1323 Example 6.5: By-Value Journal Metadata for a Referent &rft_val_fmt=info:ofi/fmt:kev:mtx:journal &rft.genre=article &rft.atitle=isolation of a common receptor for coxsackie B &rft.jtitle=science &rft.aulast=bergelson &rft.auinit=j &rft.date=1997 &rft.volume=275 &rft.spage=1320 &rft.epage=1323 (URL-encoded KEV Format) &rft_val_fmt=info%3aofi%2ffmt%3akev%3amtx%3ajourna 42
l&rft.genre=article&rf t.atitle=isolation+of+a+common+receptor+for+coxsackie+b &rft.jtitle=science&rft.aulast=bergelson&rft.auinit=j&rft.d ate=1997&rft.volume=275&rft.spage=1320&rf t.epage=1323 6.6 ( URL ) &rfe_ref_fmt=info:ofi/fmt:kev:mtx:journal &rfe_ref=http://www.example.org/temp/1234.txt http://www.example.org/temp/1234.txt ( URL ) &genre=article &atitle=p27-p16 Chimera: A Superior Antiproliferative &jtitle=molecular Theory &aulast=mcarthur &aufirst=james &date=2001 &volume=3 &issue=1 &spage=8 &epage=13 (URL KEV ) &rfe_ref_fmt=info%3aofi%2ffmt%3akev%3amtx%3ajournal&rfe_ref=http%3a% 2F%2Fwww.example.org%2Ftemp%2F1234.txt http://www.example.org/temp/1234.txt (URL KEV ) &genre=article&atitle=p27- p16+chimera%3a+a+superior+antiproliferative&jtitle=molecular+theory&aulast =McArthur&aufirst=James&date=2001&volume=3&issue=1&spage=8&epage=13 43
Example 6.6 By-Reference Metadata for a ReferringEntity Within the ContextObject: &rfe_ref_fmt=info:ofi/fmt:kev:mtx:journal &rfe_ref=http://www.example.org/temp/1234.txt At http://www.example.org/temp/1234.txt : &genre=article &atitle=p27-p16 Chimera: A Superior Antiproliferative &jtitle=molecular Theory &aulast=mcarthur &aufirst=james &date=2001 &volume=3 &issue=1 &spage=8 &epage=13 Within the ContextObject: (URL-encoded KEV Format) &rfe_ref_fmt=info%3aofi%2ffmt%3akev%3amtx%3ajournal&rfe_ref=http%3a% 2F%2Fwww.example.org%2Ftemp%2F1234.txt At http://www.example.org/temp/1234.txt : (URL-encoded KEV Format) &genre=article&atitle=p27- p16+chimera%3a+a+superior+antiproliferative&jtitle=molecular+theory&aulast =McArthur&aufirst=James&date=2001&volume=3&issue=1&spage=8&epage=13 6.4.2 (Book and General Document Metadata) Z39.88-2004 44
(http://www.openurl.info/registry/docs/info:ofi/fmt:kev:mtx:book) The Metadata Format to represent a book, book component, report or general document is defined by a Z39.88-2004 Matrix in the Registry at: http://www.openurl.info/registry/docs/info:ofi/fmt:kev:mtx:book. This Matrix includes a description for the use of each of the metadata items. That information is not reproduced here but guidelines for a few of the metadata items are given below. The Matrix defines the permissible occurrences of the metadata keys. ( ) (a) rft_val_fmt ( rfe_val_fmt) info:ofi/fmt:kev:mtx:book (b) rft. ( rfe. ) When a Referent (or ReferringEntity) is described with By-Value Metadata using the book Metadata Format: The rft_val_fmt (or rfe_val_fmt) Key in the ContextObject has the value: info:ofi/fmt:kev:mtx:book The metadata keys must be prefixed with rft. (or rfe. ) ( ) 45
(a) rft_val_fmt ( rfe_val_fmt) info:ofi/fmt:kev:mtx:book (b) KEV rft_ref ( rfe_ref) (c) (d) UTF-8. When a Referent (or ReferringEntity) is described with By-Reference Metadata using the book Metadata Format: The rft_ref_fmt (or rfe_ref_fmt) Key in the ContextObject has the value: info:ofi/fmt:kev:mtx:book. The metadata at the location specified by the rft_ref (or rfe_ref) Key is in KEV book Metadata Format: The metadata keys must not be prefixed Character Encoding default is UTF-8, but it can declare its own encoding (1) 6.4.7 (genre) 6.7 46
(1) Genre The book Metadata Format is a general purpose Format to describe books, book components, and similar documents. It may be used to describe a conference proceedings or paper, or a report. Book metadata may also be used to describe a general document where some bibliographic information, such as author and title, are known, but the specific type of the resource cannot be determined. It could possibly be used to describe non-text items as described in Section 6.4.7. The specific genre of the resource within the book metadata type may be indicated by the genre metadata key. The possible values for the genre metadata key are shown in Table 6.7. 6.7 (Genre Value) (book) (bookitem) (conference) (proceeding) (report) (document) (unknown) Table 6.7 Book Metadata Genre Values Genre Value book bookitem conference proceeding report document unknown Description Book Section of a book Record of a conference Single conference presentation Published report General document Unknown genre 47
(2) 6.4.1 (2) Author The recommendations for detailing authors are the same as those for the Journal Metadata Format described in Section 6.4.1 above. 6.7 The following example, 6.7, shows By-Value Book Metadata for a Referent. 6.7 ( URL ) rft_val_fmt=info:ofi/fmt:kev:mtx:book &rft.genre=book &rft.btitle=professional XML Meta Data &rft.aulast=dodds &rft.afirst=david &rft.date=2001 &rft.isbn=1861004516 (URL KEV ) &rft_val_fmt=info%3aofi%2ffmt%3akev%3amtx%3abook&rf t.genre=book&rft.bt itle=professional+xml+meta+data&rft.aulast=dodds&rft.afirs t=david&rft.date=2 001&rft.isbn=1861004516 Example 6.7: By-Value Book Metadata for a Referent 48
&rft_val_fmt=info:ofi/fmt:kev:mtx:book &rft.genre=book &rft.btitle=professional XML Meta Data &rft.aulast=dodds &rft.afirst=david &rft.date=2001 &rft.isbn=1861004516 (URL-encoded KEV Format) &rft_val_fmt=info%3aofi%2ffmt%3akev%3amtx%3abook &rft.genre=book&rft.bt itle=professional+xml+meta+data&rft.aulast=dodds&rft.af irst=david&rft.date=2 001&rft.isbn=1861004516 6.4.3 (Dissertation Metadata) Z39.88-2004 (http://www.openurl.info/registry/docs/info:ofi/fmt:kev:mtx:dissertation) The Metadata Format to represent a dissertation is defined by a Z39.88-2004 Matrix in the Registry at: http://www.openurl.info/registry/docs/info:ofi/fmt:kev:mtx:dissertation. This Matrix includes a description for the use of each of the metadata items, and defines the permissible occurrences of the metadata keys. ( ) 49
(a) rft_val_fmt ( rfe_val_fmt) info:ofi/fmt:kev:mtx:dissertation (b) rft. ( rfe. ) When a Referent (or ReferringEntity) is described with By-Value Metadata using the dissertation Metadata Format: The rft_val_fmt (or rfe_val_fmt) Key in the ContextObject has the value: info:ofi/fmt:kev:mtx:dissertation The metadata keys must be prefixed with rft. (or rfe. ) ( ) (a) rft_val_fmt ( rfe_val_fmt) info:ofi/fmt:kev:mtx:dissertation (b) KEV rft_ref ( rfe_ref) (c) (d) UTF-8 When a Referent (or ReferringEntity) is described with By-Reference Metadata using the dissertation Metadata Format: The rft_ref_fmt (or rfe_ref_fmt) Key in the ContextObject has the value: info:ofi/fmt:kev:mtx:dissertation The metadata at the location specified by the rft_ref (or rfe_ref) Key is in KEV dissertation Metadata Format 50
The metadata keys must not be prefixed Character Encoding default is UTF-8, but it can declare its own encoding (1) 6.4.1 (1) Author The recommendations for detailing authors are the same as those for the Journal Metadata Format described in Section 6.4.1 above. 6.8 The following example, 5.8, shows By-Value Dissertation Metadata for a Referent. 6.8 ( URL ) &rft_val_fmt=info:ofi/fmt:kev:mtx:dissertation &rft.title=the effects of the rare earth elements yttrium, gadolinium and dysprosium &rft.aulast=apps &rft.afirst=peter &rft.auinitm=j &rft.date=2001 &rft.co=united Kingdom &rft.inst=university of Manchester &rft.degree=phd (URL KEV ) &rft_val_fmt=info%3aofi%2ffmt%3akev%3amtx%3adissertat ion&rft.title=the 51
effects+of+the+rare+earth+elements+yttrium%2c+gadolinium+ and+dysprosium &rft.aulast=apps&rft.afirst=peter&rft.auinitm=j&rft.date=2001 &rft.co=united+kin gdom&rft.inst=university+of+manchester&rft.degree=phd Example 6.8: By-Value Dissertation Metadata for a Referent &rft_val_fmt=info:ofi/fmt:kev:mtx:dissertation &rft.title=the effects of the rare earth elements yttrium, gadolinium and dysprosium &rft.aulast=apps &rft.afirst=peter &rft.auinitm=j &rft.date=2001 &rft.co=united Kingdom &rft.inst=university of Manchester &rft.degree=phd (URL-encoded KEV Format) &rft_val_fmt=info%3aofi%2ffmt%3akev%3amtx%3adisser tation&rft.title=the effects+of+the+rare+earth+elements+yttrium%2c+gadoliniu m+and+dysprosium &rft.aulast=apps&rft.afirst=peter&rft.auinitm=j&rft.date=2 001&rft.co=United+Kin gdom&rft.inst=university+of+manchester&rft.degree=phd 6.4.4 (Patent Metadata) 52
Z39.88-2004 (http://www.openurl.info/registry/docs/info:ofi/fmt:kev:mtx:patent) The Metadata Format to represent a patent is defined by a Z39.88-2004 Matrix in the Registry at: http://www.openurl.info/registry/docs/info:ofi/fmt:kev:mtx:patent. That Matrix includes a description for the use of each of the metadata items, and defines the permissible occurrences of the metadata keys.. ( ) (a) rft_val_fmt ( rfe_val_fmt) info:ofi/fmt:kev:mtx:patent (b) rft. ( rfe. ) When a Referent (or ReferringEntity) is described with By-Value Metadata using the patent Metadata Format: The rft_val_fmt (or rfe_val_fmt) Key in the ContextObject has the value: info:ofi/fmt:kev:mtx:patent The metadata keys must be prefixed with rft. (or rfe. ) ( ) (a) rft_val_fmt ( rfe_val_fmt) 53
info:ofi/fmt:kev:mtx:dissertation (b) KEV rft_ref ( rfe_ref) (c) (d) UTF-8, When a Referent (or ReferringEntity) is described with By-Reference Metadata using the patent Metadata Format: The rft_ref_fmt (or rfe_ref_fmt) Key in the ContextObject has the value: info:ofi/fmt:kev:mtx:patent The metadata at the location specified by the rft_ref (or rfe_ref) Key is in KEV patent Metadata Format: The metadata keys must not be prefixed Character Encoding default is UTF-8, but it can declare its own encoding 6.4.5 (Scholarly Service Type Metadata) Z39.88-2004 (http://www.openurl.info/registry/docs/info:ofi/fmt:kev:mtx:sch_svc) yes no The Metadata Format to represent a scholarly service type is defined by a 54
Z39.88-2004 Matrix in the Registry at: http://www.openurl.info/registry/docs/info:ofi/fmt:kev:mtx:sch_svc. This Matrix includes a description for the use of each of the metadata items. That information is not reproduced here but the metadata items are listed below. Possible values for each metadata item are yes or no. The Matrix defines the permissible occurrences of the metadata keys. OpenURL (hint) Because the OpenURL Framework does not prescribe Resolver behavior there is no guarantee that a Resolver will provide the requested service when one of these ServiceType Metadata Keys is included in a ContextObject. Requested ServiceTypes should be regarded as a hint to the Resolver. In particular it should be noted that requesting fulltext will not override any subscription restrictions. (a) svc_val_fmt info:ofi/fmt:kev:mtx:sch_svc (b) svc. When a ServiceType is described with By-Value Metadata using the 55
scholarly service type Metadata Format: The svc_val_fmt Key in the ContextObject has the value: info:ofi/fmt:kev:mtx:sch_svc The metadata keys must be prefixed with svc. (a) svc_ref_fmt info:ofi/fmt:kev:mtx:sch_svc (b) KEV svc_ref (c) (d) UTF-8 When a ServiceType is described with By-Reference Metadata using the scholarly service type Metadata Format: The svc_ref_fmt Key in the ContextObject has the value: info:ofi/fmt:kev:mtx:sch_svc The metadata at the location specified by the svc_ref Key is in KEV scholarly service type Metadata Format The metadata keys must not be prefixed Character Encoding default is UTF-8, but it can declare its own encoding 6.8 (Key) (abstract) (citation) 56
(fulltext) (holdings) (ill) (any) Table 6.8 Scholarly Service Type Keys Key abstract citation fulltext holdings ill any Description Abstract of the Referent Bibliographic citation of the Referent Full text of the Referent Holdings information related to the Referent Inter-library Loan request for the Referent Any service type The following example shows the use of the scholarly service type Metadata Format. 6.9 ( URL ) &svc_val_fmt=info:ofi/fmt:kev:mtx:sch_svc &svc.fulltext=yes (URL KEV ) &svc_val_fmt=info%3aofi%2ffmt%3akev%3amtx%3asch_svc &svc.fulltext=yes Example 6.9: By-Value Scholarly Metadata for a ServiceType &svc_val_fmt=info:ofi/fmt:kev:mtx:sch_svc &svc.fulltext=yes 57
(URL-encoded KEV Format) &svc_val_fmt=info%3aofi%2ffmt%3akev%3amtx%3asch_ svc&svc.fulltext=yes (1.3 ) Note the scholarly service type Metadata Format supersedes the service type identifiers detailed in previous versions (1.3 and below) of this document, which are no longer available. 6.4.6 (Dublin Core Metadata Format) info:ofi/fmt:kev:mtx:dc (http://www.dublincore.org) 15 6.9 An experimental metadata format for Simple Dublin Core is currently under development. Its eventual Identifier in the Registry will be info:ofi/fmt:kev:mtx:dc.it provides metadata Keys for the 15 elements of Simple Dublin Core (http://www.dublincore.org) listed in Table 6.9. 6.9 (Key) (title) (creator) (subject) (description) (publisher) 58
(contributor) (date) (type) (format) (identifier) (source) (language) (relation) (coverage) (rights) Table 6.9 Simple Dublin Core Metadata Keys Key title creator subject description publisher contributor date type format identifier source language relation coverage rights Description Name of the resource Primary creator of the content of the resource Topic of the content of the resource Description of the content of the resource Entity making resource available Contributor to content of resource Date of an event in lifecycle of resource Nature or genre of content of resource Physical or digital manifestation of resource Unambiguous reference to resource in a given context Resource from which this resource was derived Language of intellectual content of resource Reference to a related resource Extent or scope of content of resource Rights held in or over resource ( ) The following example shows a use of the simple Dublin Core Metadata 59
Format for a Referent and a ServiceType. 6.10 ( URL ) &rft_val_fmt=info:ofi/fmt:kev:mtx:dc &rft.title=jstor business &rft.subject=business &svc_val_fmt=info:ofi/fmt:kev:mtx:dc &svc.format=text/xml (URL KEV ) &rft_val_fmt=info%3aofi%2ffmt%3akev%3amtx%3adc&rft. title=jstor+business &rft.subject=business&svc_val_fmt=info%3aofi%2ffmt%3ak ev%3amtx%3adc& svc.format=text%2fxml Example 6.10: By-Value Simple Dublin Core Metadata &rft_val_fmt=info:ofi/fmt:kev:mtx:dc &rft.title=jstor business &rft.subject=business &svc_val_fmt=info:ofi/fmt:kev:mtx:dc &svc.format=text/xml (URL-encoded KEV Format) &rft_val_fmt=info%3aofi%2ffmt%3akev%3amtx%3adc&r ft.title=jstor+business &rft.subject=business&svc_val_fmt=info%3aofi%2ffmt%3 Akev%3Amtx%3Adc& svc.format=text%2fxml 60