This Confluence wiki site, maintained by DuraSpace prior to the recent merger with LYRASIS, will transition from the duraspace.org domain to the lyrasis.org domain on Saturday, Nov 16 beginning at approximately 7pm ET. A period of downtime of 2-3 hours is expected. After the transition, this wiki will be available at https://wiki.lyrasis.org/. All links to duraspace.org wiki pages will be redirected to the correct lyrasis.org URL. If you have questions prior to or following the transition please contact: wikihelp@lyrasis.org.
Page tree

Bleeding Edge

This documentation covers the bleeding edge version of Fedora. Looking for another version? See all documentation.

Skip to end of metadata
Go to start of metadata

Namespaces

A Fedora repository includes a number of predefined namespace bindings (essentially, a mapping that connects a particular prefix to a URI, allowing for a more convenient and human-readable rendering of RDF).  Predefined namespaces include DC, FOAF, Fedora, and LDP, among others.  As additional namespaces are used in the course of depositing materials into the repository, each new namespace will automatically be bound to its own prefix the first time it is used.  Once a URI is bound to a particular namespace prefix, it cannot be changed. A full list of the bound namespaces for a given Fedora repository at any given moment can be seen in the HTTP REST interface, as a list of pre-populated "PREFIX ..." bindings in the SPARQL update query text-box.

Custom Namespace registry

This optional feature allows an administrator to provide a list of custom namespace prefixes that will override the default prefix registry. The custom namespaces are loaded on start-up via a YAML file.  The namespaces can be modified while Fedora is running.  Changes may take a few minutes to take effect.

Below is a sample YAML namespace configuration file, custom_namespaces.yml.  Notice the "awesome" prefix definition at the bottom of the list. We will use this in the following example. NB: the custom file will override all default namespace prefixes.  In other words, the custom file becomes the definitive registry.  Any namespaces that are not prefixed will be returned as full URIs in the response.

premis:  http://www.loc.gov/premis/rdf/v1#
test:  info:fedora/test/
memento:  http://mementoweb.org/ns#
rdfs:  http://www.w3.org/2000/01/rdf-schema#
webac:  http://fedora.info/definitions/v4/webac#
acl:  http://www.w3.org/ns/auth/acl#
vcard:  http://www.w3.org/2006/vcard/ns#
xsi:  http://www.w3.org/2001/XMLSchema-instance
xmlns:  http://www.w3.org/2000/xmlns/
rdf:  http://www.w3.org/1999/02/22-rdf-syntax-ns#
fedora:  http://fedora.info/definitions/v4/repository#
xml:  http://www.w3.org/XML/1998/namespace
ebucore:  http://www.ebu.ch/metadata/ontologies/ebucore/ebucore#
ldp:  http://www.w3.org/ns/ldp#
dcterms:  http://purl.org/dc/terms/
iana:  http://www.iana.org/assignments/relation/
xs:  http://www.w3.org/2001/XMLSchema
fedoraconfig:  http://fedora.info/definitions/v4/config#
foaf:  http://xmlns.com/foaf/0.1/
dc:  http://purl.org/dc/elements/1.1/
awesome: http://example.com/awesome/

Fedora can activate the file by using the -Dfcrepo.namespace.registry system parameter, either on the command line or by adding it to the list of other params that provide paths to other configuration files:

mvn jetty:run -Dfcrepo.namespace.registry=/my/fedora/path/custom_namespaces.yml

In order to demonstrate how this feature works,  try starting Fedora without  defining a custom namespace registry:

mvn jetty:run

Once Fedora is running,  run the following curl command

echo "@prefix awesome: <http://example.com/awesome/> . <> awesome:stuff 'waffle' ." | curl -u fedoraAdmin:fedoraAdmin http://localhost:8080/rest/test  -X PUT -H "Content-Type: text/turtle" --data-binary "@-"

When you retrieve this resource,

curl -i -u fedoraAdmin:fedoraAdmin http://localhost:8080/rest/test

notice the new predicate is expressed as the full URI.

output
@prefix rdf:  <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix fedora:  <http://fedora.info/definitions/v4/repository#> .
@prefix ldp:  <http://www.w3.org/ns/ldp#> .

<http://localhost:8080/rest/test>
...
        <http://example.com/awesome/test>  "waffle" ;
...  

Also notice there are built in prefixes for common namespaces.  Now restart Fedora with the custom namespaces yml enabled:

mvn jetty:run -Dfcrepo.namespace.registry=/my/fedora/path/custom_namespaces.yml

Retrieve the item and see how your custom namespace prefix is being used.

curl -ufedoraAdmin:fedoraAdmin  http://localhost:8080/rest/test
@prefix awesome:  <http://example.com/awesome/> .
@prefix rdf:  <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix fedora:  <http://fedora.info/definitions/v4/repository#> .
@prefix ldp:  <http://www.w3.org/ns/ldp#> .

<http://localhost:8080/rest/test>
...
        awesome:test           "waffle" ;
...

Suppose, you later decide that the "awesome" namespace was mislabelled. Instead you really wanted the namespace to be "justokay". Edit the file /my/fedora/path/custom_namespaces.yml to change "awesome" to "justokay", save the file and wait a few seconds, then check the namespace output again:

curl -ufedoraAdmin:fedoraAdmin  http://localhost:8080/rest/test

@prefix justokay:  <http://example.com/awesome/> .
@prefix rdf:  <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix fedora:  <http://fedora.info/definitions/v4/repository#> .
@prefix ldp:  <http://www.w3.org/ns/ldp#> .

<http://localhost:8080/rest/test>
...
		justokay:test          "waffle" ;
...
  • No labels