Export the repository's contents as RDF into the Semantic Web.

This commits adds a module dspace-rdf. The module will convert the
metadata stored in DSpace into RDF. The converted data will be provided
over a webinterface and a SPARQL endpoint.
rdfの文字化けを修正
Uses jena version 2.12.0 and removes workaround for bug JENA-663.
RDFConfiguration: added a method to load comma separated config values.
Enhanced and renamed the DSORelationsConverterPlugin into SimpleDSOR...

Renamed the DSORelationsConverterPlugin into
SimpleDSORelationsConverterPlugin.
Overhault the Plugin: it can be configured now and it can create
multiple links per DSO Relation.
Uses all possible identifiers to generate URIs.

This commit enables dspace-rdf to use all PersistentIdentifiers minted
by DSpace and not only handles. It makes advantage of the changes
introduced to DSpace by DS-1990. Persistent Identifers should and will
be used as fully functional http URIs only (e.g. a DOI will be used in
the form http://dx.doi.org/<doi> and not as doi:<doi>).
The DSpace Matadata Mapping vocabulary moved to digital-repositories.org
Repaired the build process after rebasing.

The dspace rdf war project wasn't build anymore as the activation of the
modules changed with the Mirage 2 contribution.
Enhanced the dspace-rdf command line interface.

Added the RDFizer to the launcher.xml configuration.
Added a command --convert-all.
Prints help if no options were given instead of starting reconvertion of
all content (which may take a lot of time).
makes CC module work via HTTPS
Uses DSpace Repository Ontology from digital-repositories.org.
Changed the CLI help for conformance with launcher script name.
New REST api

New REST api with CRUD operations over community, collections, items,
bitstreams.
HTTPS

Change from HTTP access to HTTPS method.
Repaired compilation bug annouced by CI.

Removed only one line with import of non exsiting class.
Added lincense headers.

Added lincense headers.
Added finally statements.

Added finally statements with context.abort() to cover all exception.
Batch import into multiple collections

If no -c argument is given ItemImport checks if a file named
'collections' exists inside the directory of each item.

This file must contain either the handles or the numeric ids of the
collections, one per line. The item is added to all those
collections. The collection specified in the first line is the owning
collection.
Added code to handle edge case

If one of the 'collections' files contains a handle or an id that cannot
be resolved to a collection, the specific item is skipped but the
procedure continues with subsequent items.
Bug fix for multiple import

If a collection could not be resolved the logic would add the item in
the same collections it added the previous item.