| 21 | Copy or move the contents (not the folder!) of the myrdfhomepage/ directory to your public html space. |
| 22 | |
| 23 | |
| 24 | ---- |
| 25 | == Longer installation instructions == |
| 26 | |
| 27 | === FOAF / RDF === |
| 28 | |
| 29 | First of all: You MUST have a FOAF file for rdfhomepage to work! [[BR]] |
| 30 | But: Care has to be taken when creating a FOAF file. |
| 31 | |
| 32 | There are a lot of tools out there for creation and management of your foaf file, however, (nearly) all of them produce a more or less crappy/ugly/bad/impractical RDF file. I am sorry, but I must advise to use a text editor for that concern. If you adapt the foaf RDFS to contain the right domain and range constraints, then Protege may also be useful, but a text editor together with disciplined(!) indentation is the best, fastest and easiest way. [[BR]] |
| 33 | The easiest way to come up with a good foaf file is to copy mine: http://www.dfki.uni-kl.de/~schwarz/foaf.xml open it in some text editor and edit everything ;) |
| 34 | |
| 35 | For all RDF files to be used in rdfhomepage you have to follow the following rules (btw, you should follow these rules for all software using RDF). This holds especially for your FOAF file: |
| 36 | |
| 37 | * Resources to be referenced from outside the RDF file need a URI => Your foaf:Person needs a URI. |
| 38 | * Blank/anonymous nodes can't be referenced from outside the RDF file. => Your foaf:Person needs a URI, no blank/anonymous node! So: don't use nodeID="...", but use rdf:about="...". |
| 39 | * Some (most!) RDF parsers do not like relative URIs (or NodeIDs). => It is generally better to use ABSOLUTE URIs. So: don't use rdf:about="#me" in your foaf file, better use something like rdf:about="http://www.dfki.uni-kl.de/~schwarz/foaf.xml#me". |
| 40 | * Generally, every thing described in an RDF file, that could be relevant and/or referenced outside the RDF file, should have an absolute URI. However, the foaf:Persons I link with foaf:knows do not have a URI, because so many people out there do not have a URI for their foaf:Person. |
| 41 | |
| 42 | If you have a FOAF file and a foaf description of your foaf:Person, then the URI of that foaf:Person has to set in your config.php file. |