Hi,

A small update for the ontology that should finish of the ontology
related issues on: http://xesam.org/main/XesamUpdates

Summary of the attached patch:

 * Add a xesam:error field to our root item xesam:DataObject. This new
xesam:error field is put in the Xesam Convenience onto

 * Specify that we use IANA subtags (just like all FDO operating
systems) in the xesam:language field

 * Introduce a new field called xesam:urlHint (this field has been
called xesam:urlScheme and xesam:urlVendor in the past). xesam:urlHint
goes in the Core onto

 * Add note to xesam:url that a hint for interpreting the url may be
found in xesam:urlHint

Comments?

-- 
Cheers,
Mikkel
=== modified file 'xesam-convenience.rdfs'
--- xesam-convenience.rdfs	2008-11-07 10:39:50 +0000
+++ xesam-convenience.rdfs	2008-12-03 22:24:50 +0000
@@ -165,5 +165,11 @@
 	<rdfs:comment>The MIME type supported by this application</rdfs:comment>
 </rdf:Property>
 
+<rdf:Property rdf:about="&xesam;error">
+	<rdfs:label>xesam:error</rdfs:label>
+	<rdfs:domain rdf:resource="&xesam;DataObject"/>
+	<rdfs:range rdf:resource="&xsd;string"/>
+	<rdfs:comment>Free form error message. Not meant for display but as a place for debugging information for the metadata framework and a simple mechanism for flagging of broken files</rdfs:comment>
+</rdf:Property>
 
 </rdf:RDF>

=== modified file 'xesam.rdfs'
--- xesam.rdfs	2008-09-02 18:11:19 +0000
+++ xesam.rdfs	2008-12-03 22:23:05 +0000
@@ -316,7 +316,7 @@
 	<rdfs:label>xesam:language</rdfs:label>
 	<rdfs:domain rdf:resource="&xesam;Content"/>
 	<rdfs:range rdf:resource="&xsd;string"/>
-	<rdfs:comment>Content language</rdfs:comment>
+	<rdfs:comment>Content language specified with IANA subtags: http://www.iana.org/assignments/language-subtag-registry</rdfs:comment>
 </rdf:Property>
 
 
@@ -1792,7 +1792,14 @@
 	<rdfs:label>xesam:url</rdfs:label>
 	<rdfs:domain rdf:resource="&xesam;Source"/>
 	<rdfs:range rdf:resource="&xss;Url"/>
-	<rdfs:comment>URL to access the content</rdfs:comment>
+	<rdfs:comment>URL to access the content, this must be a qualified URL and not just a file path. A hint on how to open or interpret the URL may be provided in xesam:urlHint</rdfs:comment>
+</rdf:Property>
+
+<rdf:Property rdf:about="&xesam;urlHint" xss:maxCardinality="1">
+	<rdfs:label>xesam:urlHint</rdfs:label>
+	<rdfs:domain rdf:resource="&xesam;Source"/>
+	<rdfs:range rdf:resource="&xsd;string"/>
+	<rdfs:comment>An optional hint on how to open or interpret the contents of the xesam:url field. The value of the field may be the vendor name of a .desktop file (the file name without the .desktop extension) for an application that can open the given URL or it may be a free form string signifying some standardized URL scheme</rdfs:comment>
 </rdf:Property>
 
 <rdf:Property rdf:about="&xesam;localRevision" xss:maxCardinality="1">

_______________________________________________
Xesam mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/xesam

Reply via email to