This is the second version of the specification
regulating publications on
http://www.andonyar.com/rec/. It replaces Version 1
| Todo | Check |
|---|---|
| Create this document, second version | ✓ |
| Revise namespaces | ✓ |
| Revise rules |
Unrelated publications reside in the namespace
http://www.andonyar.com/rec/. Let us call such
publications RecPubs. In order to assure a simple publication process
and automtical indexing, these publications have to adhere to a small
set of rules made explicit in this document. The namespace is only
suitable for static, public publications. Beyond that, no more
restrictions on the type of a publications are put in place. There are
however some requirements what metadata publications must contain.
The following namespaces are used in metadata provided by RecPubs:
| Prefix | Namespace | Description |
|---|---|---|
| recpub | http://www.andonyar.com/rec/2007-01/aspec/recpub# | Used for the description of RecPubs |
| dc | http://purl.org/dc/elements/1.1/ | Used by version 1 of this specification. In this version, dcterms is used instead. |
| dcterms | http://purl.org/dc/terms/ | The namespace for Dublin Core metadata tems. |
| foaf | http://xmlns.com/foaf/0.1/ | Friend of a Friend. Used to describe people. |
| rdf | http://www.w3.org/1999/02/22-rdf-syntax-ns# | |
| rdfs | http://www.w3.org/2000/01/rdf-schema# | |
| xsd | http://www.w3.org/2001/XMLSchema# |
Every publication has to be placed in a namespace of the form
http://www.andonyar.com/rec/YYYY/name_of_publication/ or
http://www.andonyar.com/rec/YYYY-MM/name_of_publication/
at the choice of the maintainer. (This mainly depends on how many
publications have been already added in the same year.) YYYY denotes
the year and MM the month. The name of the publication can be chosen
freely as long as it resides in a sane range of characters. Note that
when refering to the whole publication in RDF, use the full URL as
given above, including te trailing /.
In a publication, filenames must not start with a dot, except for
.htaccess. Files with a name beginning with a dot will
never be serverd. .htaccess is used to change the
behaviour of the server.
Content negotiation is activated by default. A request to a
directory will be served with the appropriate index.*.
The file A.rdf must be present in the top directory of
the publication. It must contain metadata about this publication as
described later. It must be encoded as
application/rdf+xml.
In the top directory of the publication, there must be a file
called A.rdf with Content-type application/rdf+xml and it
must be valid RDF/XML. The file must contain at least the triples
required here, but can contain additional information.
Let P be the URL denoting the publication the file
A.rdf belongs to.
The following triples must be included, with the correct values:
P rdf:type recpub:RecPub . P recpub:aspec <http://www.andonyar.com/rec/2007-01/aspec/rec2> . P dcterms:title ""@language . P dcterms:created "YYYY-MM-DD"^^xsd:date . P dcterms:modified "YYYY-MM-DD"^^xsd:date .
Optional but recommended:
P dcterms:creator <http://u.andonyar.com/people/SomeAuthor> .
<http://u.andonyar.com/people/SomeAuthor> rdf:type foaf:Person ;
foaf:name "Firstname Surname" .
P dcterms:subject <http://example.org/resource/something> .
P dcterms:description "Short description"@en .
P dcterms:language <http://example.org/resource/somelanguage> .
It is recommended to also indicate the date the publication has been copyrighted and under which license it is published.
TODO
TODO
It is recommended to use and adhere to the following standards.
The files named .htaccess can be used to influence the
behaviour of the server. It will mostly be used to set set HTTP status
codes (redirections, gone, see also). It can also be used to configure
content negotiation.
Advanced features like URL rewriting should be avoided.
It is forbidden to use .htaccess files to restrict
access to resources, because the rec namespace is only for public
resources.