wok annotate thunderbird/stuff/mimeTypes.rdf @ rev 8727

Fixed tcl.
author Christopher Rogers <slaxemulator@gmail.com>
date Sat Feb 19 01:00:28 2011 +0000 (2011-02-19)
parents
children
rev   line source
domcox@6080 1 <?xml version="1.0"?>
domcox@6080 2
domcox@6080 3 <!--
domcox@6080 4 This file is used as a persistent data store for helper application
domcox@6080 5 information about both MIME type and protocol scheme helpers.
domcox@6080 6
domcox@6080 7 The root of the data are the two containers
domcox@6080 8 <RDF:Seq about="urn:mimetypes:root"/> and <RDF:Seq about="urn:schemes:root"/>.
domcox@6080 9
domcox@6080 10 These contain one <RDF:li/> entry per MIME type/protocol. Each <RDF:li/> entry
domcox@6080 11 corresponds to a "urn:<class>:<type>" resource, where <class> is either
domcox@6080 12 "mimetype" or "scheme" and <type> is either a MIME type in "major/minor" format
domcox@6080 13 or a scheme. For example, for HTML we would have "urn:mimetype:text/html",
domcox@6080 14 while for mailto: we would have "urn:scheme:mailto".
domcox@6080 15
domcox@6080 16 Typically, this resource will be in the <RDF:Description/> node which has the
domcox@6080 17 corresponding "about" attribute.
domcox@6080 18
domcox@6080 19 Each "urn:<class>:<type>" resource can have the following properties:
domcox@6080 20
domcox@6080 21 NC:Value - the MIME type or scheme string
domcox@6080 22 NC:editable - a "true" or "false" depending on whether this entry is
domcox@6080 23 editable
domcox@6080 24 NC:description - a description of the type ("HTML Document" for text/html)
domcox@6080 25 NC:fileExtensions - for MIME types, there will be one of these properties
domcox@6080 26 per extension that corresponds to this MIME type,
domcox@6080 27 each one having a single extension as its value.
domcox@6080 28 NC:handlerProp - the way the type should be handled. This corresponds to a
domcox@6080 29 "urn:<class>:handler:<type>" resource. Eg, the way HTML is
domcox@6080 30 handled would be stored in the
domcox@6080 31 "urn:mimetype:handler:text/html" resource.
domcox@6080 32
domcox@6080 33 Each "urn:<class>:handler:<type>" resource can have the following properties:
domcox@6080 34
domcox@6080 35 NC:useSystemDefault - "true" if we should handle per default OS setting,
domcox@6080 36 "false" or not set otherwise
domcox@6080 37 NC:saveToDisk - "true" if the data should be saved to disk, "false" or not
domcox@6080 38 set otherwise.
domcox@6080 39 (Note - if both of these are false, that means "open in helper app")
domcox@6080 40 NC:alwaysAsk - "true" if the user should always be prompted before handling
domcox@6080 41 data of this type, false otherwise.
domcox@6080 42 NC:externalApplication - the preferred helper application to use for this
domcox@6080 43 type. This corresponds to a
domcox@6080 44 "urn:<class>:externalApplication:<type>" resource.
domcox@6080 45 NC:possibleApplication - a helper application that can be used for this type.
domcox@6080 46 Since there can be multiple possible applications,
domcox@6080 47 there can be multiple assertions in the graph with
domcox@6080 48 this property for a given handler resource.
domcox@6080 49
domcox@6080 50 Each "urn:<class>:externalApplication:<type>" resource, and each resource
domcox@6080 51 that represents a possible application, can have the following property:
domcox@6080 52
domcox@6080 53 NC:prettyName - the "pretty name" of the application ("Acrobat Reader" for
domcox@6080 54 /usr/bin/acroread, eg).
domcox@6080 55
domcox@6080 56 If the resource represents a local application, then it can have the following
domcox@6080 57 property:
domcox@6080 58
domcox@6080 59 NC:path - the path to the application on the local filesystem, for example
domcox@6080 60 /usr/bin/test or C:\windows\system32\cmd.exe.
domcox@6080 61
domcox@6080 62 If the resource represents a web application, then it can have the following
domcox@6080 63 property:
domcox@6080 64
domcox@6080 65 NC:uriTemplate - a URI pointing to the web application to which the type
domcox@6080 66 should be handed off, with %s in the template representing
domcox@6080 67 the place where the content should be inserted. For example,
domcox@6080 68 here is a URI template for a service that lets you email
domcox@6080 69 an address in a mailto: link:
domcox@6080 70 http://www.example.com/sendmail?link=%s
domcox@6080 71 -->
domcox@6080 72
domcox@6080 73 <RDF:RDF xmlns:RDF="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
domcox@6080 74 xmlns:NC="http://home.netscape.com/NC-rdf#">
domcox@6080 75
domcox@6080 76 <RDF:Seq RDF:about="urn:schemes:root">
domcox@6080 77 <RDF:li RDF:resource="urn:scheme:http"/>
domcox@6080 78 </RDF:Seq>
domcox@6080 79
domcox@6080 80 <RDF:Description RDF:about="urn:scheme:externalApplication:http"
domcox@6080 81 NC:prettyName="midori"
domcox@6080 82 NC:path="/usr/bin/midori" />
domcox@6080 83 <RDF:Description RDF:about="urn:scheme:handler:http"
domcox@6080 84 NC:alwaysAsk="false">
domcox@6080 85 <NC:externalApplication RDF:resource="urn:scheme:externalApplication:http"/>
domcox@6080 86 <NC:possibleApplication RDF:resource="urn:handler:local:/usr/bin/midori"/>
domcox@6080 87 </RDF:Description>
domcox@6080 88
domcox@6080 89 <RDF:Description RDF:about="urn:schemes">
domcox@6080 90 <NC:Protocol-Schemes RDF:resource="urn:schemes:root"/>
domcox@6080 91 </RDF:Description>
domcox@6080 92
domcox@6080 93 <RDF:Description RDF:about="urn:scheme:http"
domcox@6080 94 NC:value="http">
domcox@6080 95 <NC:handlerProp RDF:resource="urn:scheme:handler:http"/>
domcox@6080 96 </RDF:Description>
domcox@6080 97
domcox@6080 98 <RDF:Description RDF:about="urn:mimetypes">
domcox@6080 99 <NC:MIME-types RDF:resource="urn:mimetypes:root"/>
domcox@6080 100 </RDF:Description>
domcox@6080 101
domcox@6080 102 <RDF:Seq RDF:about="urn:mimetypes:root">
domcox@6080 103 </RDF:Seq>
domcox@6080 104 <RDF:Description RDF:about="urn:root"
domcox@6080 105 NC:en-US_defaultHandlersVersion="-1"
domcox@6080 106 NC:fr_defaultHandlersVersion="-1" />
domcox@6080 107 <RDF:Description RDF:about="urn:handler:local:/usr/bin/midori"
domcox@6080 108 NC:prettyName="midori"
domcox@6080 109 NC:path="/usr/bin/midori" />
domcox@6080 110 </RDF:RDF>