[tracker] Updated NIE explanation about URI assignations



commit 9b1d952c186b7a1628df69acd9f85c47016590ca
Author: Ivan Frade <ivan frade nokia com>
Date:   Wed Dec 9 09:49:32 2009 +0200

    Updated NIE explanation about URI assignations

 docs/ontologies/nie/explanation.html |    7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)
---
diff --git a/docs/ontologies/nie/explanation.html b/docs/ontologies/nie/explanation.html
index cffc541..c9d982e 100644
--- a/docs/ontologies/nie/explanation.html
+++ b/docs/ontologies/nie/explanation.html
@@ -73,9 +73,10 @@ worth to comment few of them with special relevance:
 <p>One of the most common resources in a desktop is a file. Given the split between Data Objects and Information Elements, some times it is not clear how a real file is represented into Nepomuk. Here are some indications:</p>
 <ol>
  <li>Every file (local or remote) should generate one DataObject instance and an InformationElement instance.</li>
- <li>Even when Data Objects and Information Elements are completely different things, for efficency reasons in Tracker we use the URI for both of them.</li>
- <li>The URI will be an autogenerated ID, and the real location of the 
- <li>To link both things together, every InformationElement must have the property <a href="#isStoredAs">nie:isStoredAs</a>, that points to the location of the resource, and should be used by any program that wants to access it.</li>
+ <li>Even when Data Objects and Information Elements are completely different things, for efficency reasons in Tracker we use the same URI for both of them.</li>
+ <li>The URI will be an autogenerated ID, and the real location of the item (e.g. ''file://path/to/file.mp3'') is a property of the Data Object</li>
+ <li>Every DataObject must have the property <a href="#url">nie:url</a>, that points to the location of the resource, and should be used by any program that wants to access it.</li>
+ <li>There is a deprecated property in the ontology: <a href="#isStoredAs">nie:isStoredAs</a> . We discourage its use in the code: in the best case it is a loopback to the nie:url value, but in general it can contain any value or not be set at all.</li>
 </ol>
 
 <p>Here comes an example, for the image file /home/user/a.jpeg:</p>



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]