This version 1.0 schema defines data elements related to OpenURL resolvers for the OCLC OpenURL Resolver registry. Author: Phil Norman, OCLC. Date last Updated: 20060524. An IP Address that matches the following form: 132.174.95.5 An IP Address that matches the following form: 132.174.95.5-60 An IP Address that matches the following form: 132.174.95-98.* An IP Address that matches the following form: 132.174.95.* An IP Address that matches the following form: 132.174.*.* An IP Address that matches the following CIDR form: 132.174.0.0/27 The root element, resolverRegistryEntry, contains resolver information and elements associated with the resolver such as IP Address Range The Insitution Name which has typcially configured the Resolver. For example, "Hogwarts School of Wizardry and Witchcraft". This element is required. An IP Address range associated with the resolver. If the IP address of the requester matches any IP address range in the registry the requester will be redirected to the associated resolver's Base URL. This element is required. Examples: 132.174.95.5 132.174.95.5-60 132.174.95-98.* 132.174.95.* 132.174.*.* 132.174.0.0/27 The domain name associated with the Institution. For example, "hogwarts.edu". The OCLC Institution Symbol associated with the Institution. See http://www.oclc.org/contacts/libraries/ to search for symbols. Limited to 6 characters. The Institution ID associated with OCLC Institution Symbol in the Institution Registry. The element is not required. Geographical address information City State County The required resolver element contains required elements such as the source of the element, the base URL, and the link text. It also includes elements that describe the resolver's capabilites such as which identifiers it supports and which OpenURL version(s) it supports. The required unique ID identified each openURL resolver record The required source element describes where the resolver is coming from. For example it could be from the OCLC OpenURL resolver registry input form, an external provider, or a specific library. The optional contactName element describes a contact name. Generally, this will be used if the source is an external provider. The optional contactMailto element describes a contact e-mail address. Generally, this will be used if the source is an external provider. Example: mailto:elharo@metalab.unc.edu The required baseURL element is the Base URL of the resolver. For example, "http://hogwarts.edu/OpenURLResolver. The optional linkIcon element is a link to an image which brands the OpenURL resolver. For example, "http://hogwarts.edu/OpenURLResolver/resolver.jpg". The required linkText element is text which is to be provided with the resolver href. For example, "Hogwart's potion collection". If the linkIcon element is present then the linkText will be the alt text for the link icon. The optional OpenURL Version element describes which OpenURL versions the resolver supports. This schema only supports the current choices which are:: OpenURL 0.1 Z39.88-2004 If the OpenURLVersions element is not present then OCLC will assume both versions are supported. If the OpenURLVersions element is present and no versions are specified, OCLC will assume both are supported. If only one is specified, it will be inferred that the other is not supported. The presence of this empty element indicates that the resolver supports OpenURL 0.1. The presence of this empty element indicates that the resolver supports Z39.88-2004. The optional repeating Z39.88-2004_CommunityProfile element describes which community profiles the resolver supports for any entity. If this element is omitted OCLC will assume that no community profiles are supported. These identifiers must be in the pattern of info:ofi/pro:.*. Here is a list of the community profile registry identifiers currently supported by Z39.88-2004. info:ofi/pro:sap1-2004 info:ofi/pro:sap1 info:ofi/pro:sap2-2004 info:ofi/pro:sap2 See http://openurl.info/registry for information about Z39.88-2004 Community Profiles. The optional keyname element is a placeholder field to include identifiers that could be used at some time in the future in the requester entity to lookup registry entries via the OCLC gateway. The identifiers should be as unique to the resolver or institution as possible. The optional Resolver vendor. Examples include: BIBSYS ILLIAD linkSource 1Cate Serials Solutions Sirsi TDNet The name of the product and any version information available The optional OpenURL_0.1_Identifiers element describes which OpenURL 0.1 identifiers the resolver supports. If this element is omitted and the OpenURL_0.1 OpenURL version is supported then OCLC will assume that all 0.1 Identifiers are supported. If the element exists each empty sub-element indicates that identifier is supported. The absence of the sub-element indicates it is not supported. OpenURL version 0.1 is defined at http://www.openurl.info/registry/docs/pdf/openurl-01.pdf. The presence of this empty element indicates that the resolver supports the Digital Object Identfier (doi). The presence of this empty element indicates that the resolver supports the PubMed Identfier (pmid). The presence of this empty element indicates that the resolver supports the Astrophysics Bibcode Identfier (bibcode). The presence of this empty element indicates that the resolver supports the Open Archives Initiative Identifier namespace (oai). The optional repeating Z39.88-2004 namespace element describes which OpenURL 1.0 namespaces the resolver supports for any entity. If no Z39.88-2004 namespace elements are specified and the Z39.88-2004 OpenURL version is supported and either the info:ofi/pro:sap1-2004 or the info:ofi/pro:sap1-2004 community profiles is supported, OCLC will assume that all San Antonio Profile (sap1-2004) namespaces are supported. If any Z39.88-2004_namespace elements are specified then those that are not specified will be assumed not to be supported. These namespaces must be in the pattern of info:ofi/.*. Here is a list of the identifier namespaces currently supported by the sap1-2004 profile: info:ofi/nam:ftp: info:ofi/nam:http: info:ofi/nam:https: info:ofi/nam:ldap: info:ofi/nam:mailto: info:ofi/nam:urn:ISBN: info:ofi/nam:urn:ISSN: info:ofi/nam:urn:NBN: info:ofi/nam:info:bibcode: info:ofi/nam:info:doi: info:ofi/nam:info:hdl: info:ofi/nam:info:lccn: info:ofi/nam:info:oai: info:ofi/nam:info:oclcnum: info:ofi/nam:info:pmid: info:ofi/nam:info:sid: info:ofi/nam:info:sici: The optional OpenURL_0.1_genres element describes which OpenURL 0.1 genres the resolver supports. If this element is omitted and the OpenURL_0.1 OpenURL version is supported then OCLC will assume that all 0.1 genres are supported. If the element is present, the presence of each empty sub-element indicates that identifier is supported. The absence of the sub-element indicates it is not supported. OpenURL version 0.1 is defined at http://www.openurl.info/registry/docs/pdf/openurl-01.pdf. The presence of this empty element indicates that the resolver supports the book metadata format or the OpenURL 0.1 genre. The presence of this empty element indicates that the resolver supports the journal metadata format or the OpenURL 0.1 genre. The presence of this empty element indicates that the resolver supports the article genre of the journal metadata format or the OpenURL 0.1 article genre. The presence of this empty element indicates that the resolver supports the conference genre of the book and/or journal metadata format or the OpenURL 0.1 conference genre. The presence of this empty element indicates that the resolver supports the proceeding genre of the book and/or journal metadata format or the OpenURL 0.1 proceeding genre. The presence of this empty element indicates that the resolver supports the bookitem genre of the book metadata format or the OpenURL 0.1 bookitem genre. The presence of this empty element indicates that the resolver supports the preprint genre of the journal metadata format or the OpenURL 0.1 preprint genre . The optional repeating Z39.88-2004_metadataFormat element describes which OpenURL 1.0 metadata formats the resolver supports for any entity. The Z39.88-2004_metadataFormat matches the pattern of info:ofi/fmt:.*. If no Z39.88-2004_metadataFormat elements are specified and the Z39.88-2004 OpenURL version is supported and the info:ofi/pro:sap1-2004 community profile is supported, OCLC will assume that the following sap1-2004 metadata formats are supported: info:ofi/fmt:kev:mtx:journal info:ofi/fmt:kev:mtx:book info:ofi/fmt:kev:mtx:patent info:ofi/fmt:kev:mtx:sch_svc info:ofi/fmt:kev:mtx:dissertation If no Z39.88-2004_metadataFormat elements are specified and the Z39.88-2004 OpenURL version is supported and the info:ofi/pro:sap2-2004 community profile is supported, OCLC will assume that the following sap2-2004 metadata formats are supported: info:ofi/fmt:xml:xsd:journal info:ofi/fmt:xml:xsd:book info:ofi/fmt:xml:xsd:patent info:ofi/fmt:xml:xsd:sch_svc info:ofi/fmt:xml:xsd:dissertation info:ofi/fmt:xml:xsd:MARC21 info:ofi/fmt:xml:xsd:oai_dc If any Z39.88-2004_metadataFormat elements are specified then those that are not specified will be assumed not to be supported. The optional repeating Z39.88-2004 _transport element describes which OpenURL 1.0 transports the resolver supports. . These identifiers must be in the pattern of info:ofi/tsp:.*. If no Z39.88-2004 transport elements are specified and the Z39.88-2004 OpenURL version is supported and either the info:ofi/pro:sap1-2004 or the info:ofi/pro:sap1-2004 community profiles is supported, OCLC will assume that all San Antonio Profile (sap1-2004 and sap2-2004) transports are supported. If any Z39.88-2004_transport elements are specified then those that are not specified will be assumed not to be supported. Here is a list of the transports currently supported by the sap1-2004 and the sap2-2004 profiles: info:ofi/tsp:http:openurl-by-ref info:ofi/tsp:http:openurl-by-val info:ofi/tsp:http:openurl-inline Also currently available in the registry are https transports: info:ofi/tsp:https:openurl-by-ref info:ofi/tsp:https:openurl-by-val info:ofi/tsp:https:openurl-inline The optional repeating Z39.88-2004 _encoding element describes which OpenURL 1.0 character encodings the resolver supports. . These identifiers must be in the pattern of info:ofi/enc:.*. If no Z39.88-2004_encoding elements are specified and the Z39.88-2004 OpenURL version is supported and the info:ofi/pro:sap1-2004 community profile is supported, OCLC will assume that the following sap1-2004 character encodings are supported: info:ofi/enc:ISO-8859-1 info:ofi/enc:UTF-8 If no Z39.88-2004_encoding elements are specified and the Z39.88-2004 OpenURL version is supported and the info:ofi/pro:sap2-2004 community profile is supported, OCLC will assume that the following sap1-2004 character encoding is supported: info:ofi/enc:UTF-8 If any Z39.88-2004_encoding elements are specified then those that are not specified will be assumed not to be supported. The optional repeating Z39.88-2004 _contextObject element describes which OpenURL 1.0 context object formats the resolver supports. . These identifiers must be in the pattern of info:ofi/fmt:.*. If no Z39.88-2004_contextobject elements are specified and the Z39.88-2004 OpenURL version is supported and the info:ofi/pro:sap1-2004 community profile is supported, OCLC will assume that the info:ofi/fmt:kev:mtx:ctx contextObject metadata format is supported. If no Z39.88-2004_contextobject elements are specified and the Z39.88-2004 OpenURL version is supported and the info:ofi/pro:sap2-2004 community profile is supported, OCLC will assume that the info:ofi/fmt:xml:xsd:ctx contextObject metadata format is supported. If any Z39.88-2004_transport elements are specified then those that are not specified will be assumed not to be supported.