--- a/ldpatch.html Wed Nov 19 22:34:49 2014 +0100
+++ b/ldpatch.html Wed Nov 19 20:08:44 2014 -0500
@@ -963,20 +963,76 @@
</section>
+ <section class="appendix" id="media-registration">
+ <h2>Internet Media Type, File Extension and Macintosh File Type</h2>
+
+ <dl>
+ <dt>Contact:</dt>
+ <dd>Andrei Vlad Sambra</dd>
+ <dt>see also:</dt>
+ <dd><a href="http://www.w3.org/2002/06/registering-mediatype">How to Register a Media Type for a <abbr title="World Wide Web Consortium">W3C</abbr> Specification</a></dd>
+ <dd><a href="http://www.w3.org/2001/tag/2002/0129-mime">Internet Media Type registration, consistency of use</a><br>
+ TAG Finding 3 June 2002 (Revised 4 September 2002)</dd>
+
+ <p>The Internet Media Type / MIME Type for LD Patch is "text/ldpatch".</p>
+
+ <p>It is recommended that LD Patch files have the extension ".ldp" (all lowercase) on all platforms.</p>
+ <div class="ldp-issue">
+ Possible namespace conflict for .ldp!
+ </div>
+
+ <p>It is recommended that LD Patch files stored on Macintosh HFS file systems be given a file type of "TEXT".</p>
+ </dl>
+
+ <dl>
+ <dt>Type name:</dt>
+ <dd>text</dd>
+ <dt>Subtype name:</dt>
+ <dd>ldpatch</dd>
+ <dt>Required parameters:</dt>
+ <dd>None</dd>
+ <dt>Optional parameters:</dt>
+ <dd>charset — this parameter is required when transferring non-ASCII data. If present, the value of charset is always UTF-8 [[!UTF-8]].</dd>
+ <dt>Encoding considerations:</dt>
+ <dd>The syntax of LD Patch is expressed over code points in Unicode [[!UNICODE]]. The encoding is always UTF-8. Unicode code points may also be expressed using an <code>\uXXXX</code> (U+0000 to U+FFFF) or <code>\UXXXXXXXX</code> syntax (for U+10000 onwards) where <code>X</code> is a hexadecimal digit <code>[0-9A-Fa-f]</code>.</dd>
+ <dt>Security considerations:</dt>
+ <dd>Because of it's relation with Turtle, the same security considerations can be applied here. Applications may evaluate given data to infer more assertions or to dereference IRIs, invoking the security considerations of the scheme for that IRI. Note in particular, the privacy issues in [[!RFC3023]] section 10 for HTTP IRIs. Data obtained from an inaccurate or malicious data source may lead to inaccurate or misleading conclusions, as well as the dereferencing of unintended IRIs. Care must be taken to align the trust in consulted resources with the sensitivity of the intended use of the data; inferences of potential medical treatments would likely require different trust than inferences for trip planning.
+ <!-- Turtle is used to express arbitrary application data; security considerations will vary by domain of use. Security tools and protocols applicable to text (e.g. PGP encryption, MD5 sum validation, password-protected compression) may also be used on Turtle documents. Security/privacy protocols must be imposed which reflect the sensitivity of the embedded information. -->
+ Application rendering strings retrieved from untrusted LD Patch sources must ensure that malignant strings may not be used to mislead the reader. The security considerations in the media type registration for XML ([[!RFC3023]] section 10) provide additional guidance around the expression of arbitrary data and markup.
+ LD Patch uses IRIs as term identifiers. Applications interpreting data expressed in LD Patch should address the security issues of Internationalized Resource Identifiers (IRIs) [[!RFC3987]] Section 8, as well as Uniform Resource Identifier (URI): Generic Syntax [[!RFC3986]] Section 7.
+ Multiple IRIs may have the same appearance. Characters in different scripts may look similar (a Cyrillic "о" may appear similar to a Latin "o"). A character followed by combining characters may have the same visual representation as another character (LATIN SMALL LETTER E followed by COMBINING ACUTE ACCENT has the same visual representation as LATIN SMALL LETTER E WITH ACUTE). Any person or application that is writing or interpreting LD Patch data must take care to use the IRI that matches the intended semantics, and avoid IRIs that may look similar. Further information about matching of similar characters can be found in Unicode Security Considerations [[!UNICODE-SECURITY]] and Internationalized Resource Identifiers (IRIs) [[!RFC3987]] Section 8.</dd>
+ <dt>Interoperability considerations:</dt>
+ <dd>There are no known interoperability issues.</dd>
+ <dt>Published specification:</dt>
+ <dd>This specification.</dd>
+ <dt>Applications which use this media type:</dt>
+ <dd>No widely deployed applications are known to use this media type. It may be used by some web services and clients consuming their data.</dd>
+ <br>
+ <dt>Additional information:</dt>
+ <dt>Magic number(s):</dt>
+ <dd>LD Patch documents may have the string '@prefix' (case sensitive) near the beginning of the document.</dd>
+ <dt>File extension(s):</dt>
+ <dd>".ldp"</dd>
+ <dt>Macintosh file type code(s):</dt>
+ <dd>"TEXT"</dd>
+ <dt>Person & email address to contact for further information:</dt>
+ <dd>Andrei Vlad Sambra <andrei@w3.org></dd>
+ <dt>Intended usage:</dt>
+ <dd>COMMON</dd>
+ <dt>Restrictions on usage:</dt>
+ <dd>None</dd>
+ <dt>Author/Change controller:</dt>
+ <dd>The LD Patch specification is the product of the LDP WG. The W3C reserves change control over this specifications.</dd>
+ </dl>
+ </section>
+
<section id="acknowledgements" class="appendix informative">
<h2>Acknowledgements</h2>
- <p>TODO</p>
+ <p>The following people (in alphabetic order) have been instrumental in providing thoughts, feedback, reviews, content, criticism and input in the creation of this specification:</p>
+
+ <p style="margin-left: 3em;">Andy Seaborne, Arnaud Le Hors, Henry Story, John Arwe, Eric Prud'hommeaux, Sandro Hawke, Steve Speicher, Tim Berners-Lee</p>
</section>
-
-
- <section class="appendix" id="media-registration">
- <h2>Internet Media Type, File Extension and Macintosh File Type</h2>
-
- <p>TODO: here comes the section about "text/ldpatch" registration.</p>
-
- </section>
-
</body>
</html>