Table of Contents

  1. PIDs
    1. Syntax
    2. Examples
    3. Normalization
  2. URIs for Objects
    1. Syntax
    2. Examples
    3. Normalization
  3. URIs for Disseminations
    1. Syntax
    2. Examples
    3. Normalization

  1. PIDs

    A PID is a unique, persistent identifier for a Fedora digital object. PIDs may be user-defined or automatically assigned by a repository. In this section we describe the syntactic and normalization considerations for PIDs.

    1. Syntax

      PIDs are case-sensitive and consist of a namespace prefix and a simple string identifier. The syntax is described below using augmented BNF: 
      object-pid    = namespace-id ":" object-id
namespace-id  = 1*( ALPHA / DIGIT / "-" / "." )
object-id     = 1*( ALPHA / DIGIT / "-" / "." / "~" / "_" / escaped-octet )
escaped-octet = "%" HEXDIG HEXDIG
      The maximum length of a PID is 64 characters.
      For convenience, we provide the following single regular expression, which can be used to validate a normalized PID string: 
      ^([A-Za-z0-9]|-|\.)+:(([A-Za-z0-9])|-|\.|~|_|(%[0-9A-F]{2}))+$

    2. Examples

      • demo:1
      • demo:A-B.C_D%3AE
      • demo:MyFedoraDigitalObject

    3. Normalization

      HEXDIG characters may occur in lowercase, but should be capitalized for normalization purposes. The separator character may occur as "%3A" or "%3a", but should be changed to a colon ":" for normalization purposes.

  2. URIs for Objects

    It is often useful to have Uniform Resource Identifiers ("URIs") that refer to Fedora Objects. For instance, semantic web technologies require the use of a URI to identify a subject. Other benefits of exposing and using URIs are described in section 2 of the W3C's Architecture of the World Wide Web.

    Every Fedora object has an implicit URI associated with it. These identifiers exist within the "fedora" namespace of the info URI scheme. We chose this URI scheme due to it's resolution protocol independence and syntactic freedom.

    1. Syntax

      The URI for a Fedora object is constructed simply by appending the PID to the string "info:fedora/".

    2. Examples

      • info:fedora/demo:1
      • info:fedora/demo:A-B.C_D%3AE
      • info:fedora/demo:MyFedoraDigitalObject

    3. Normalization

      To normalize an object URI, normalize the PID part as described above.

  3. URIs for Disseminations

    Every dissemination of an object also has an implicit URI associated with it. This is useful when describing or referring to the the representations provided by a digital object.

    1. Syntax

      Dissemination URIs take one of two forms. In the case of a method call the URI indicates the behavior definition and the method (along with any parameters). In the case of a datastream dissemination, the URI indicates the datastream id. 
      dissemination-uri = "info:fedora/" pid "/" ( method-call / datastream-id )
method-call       = bDef-pid "/" method-name [ "?" param *( "&" param ) ]
param             = paramName "=" paramValue
      Note that datastream-ids and method-names may consist of XML NCName characters. NCName characters that are not URI-safe must be escaped using one to four escaped UTF-8 octets per character, each of the form "%" HEXDIG HEXDIG.

    2. Examples

      • info:fedora/demo:1/demo:MyBDef/method
      • info:fedora/demo:1/demo:MyBDef/method?param1=value1
      • info:fedora/demo:1/title.jpg
      • info:fedora/demo:1/DC

    3. Normalization

      To normalize a dissemination URI:
      1. Normalize the PID portion(s) of the URI.
      2. Un-escape any URI-escaped characters that do not need escaping according to the definition of the "info" scheme.
      3. Make all remaining escaped octets use UPPERCASE (%ff becomes %FF).
      4. Parameters should be alphabetized in order by name, then by value. The order should be according to occurence in UTF-8.