--- a/model/prov-dm.html	Thu Jun 28 21:16:23 2012 +0100
+++ b/model/prov-dm.html	Thu Jun 28 21:40:51 2012 +0100
@@ -346,7 +346,7 @@
                 company: "Oracle Corporation" },
               { name: "Stephen Cresswell",
                 company: "legislation.gov.uk"},
-              { name: "Tom De Nies", url:"http://users.ugent.be/~tdenies/",
+              { name: "Sam Coppens", url:"http://users.ugent.be/~scoppens/",
                 company: "IBBT - Ghent University"},
               { name: "Yolanda Gil",
                 company: "Invited Expert", url:"http://www.isi.edu/~gil/"},

--- a/model/prov-n.html	Thu Jun 28 21:16:23 2012 +0100
+++ b/model/prov-n.html	Thu Jun 28 21:40:51 2012 +0100
@@ -212,6 +212,12 @@
           "<a href=\"http://www.w3.org/TR/prov-aq/\"><cite>Provenance Access and Query</cite></a>. "+
           "2011, Working Draft. "+
           "URL: <a href=\"http://www.w3.org/TR/prov-aq/\">http://www.w3.org/TR/prov-aq/</a>",
+
+        "UNISEC":
+       " Mark Davis and Michel Suignard. " +
+       "<a href=\"http://www.unicode.org/reports/tr36/\"><cite>Unicode Security Considerations<cite></a>. " +
+       " 4 August 2010. " +
+       "URL: <a href=\"http://www.unicode.org/reports/tr36/\"http://www.unicode.org/reports/tr36/</a>",
       };
       var respecConfig = {
           // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
@@ -2657,8 +2663,79 @@
 <div class="note">
 <p>
 See <a href="http://www.w3.org/2002/06/registering-mediatype">http://www.w3.org/2002/06/registering-mediatype</a> for Register an Internet Media Type for a W3C Spec.</p>
+Following text adapted from <a href="http://www.w3.org/TeamSubmission/turtle/#sec-mediaReg">turtle</a>.
 </div>
 
+
+ <dl> 
+      <dt>Contact:</dt> 
+      <dd>TBD</dd> 
+      <dt>See also:</dt> 
+      <dd><a href="http://www.w3.org/2002/06/registering-mediatype">How to Register a Media Type for a W3C 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> 
+    </dl> 
+    <p>The Internet Media Type / MIME Type for PROV-N is &quot;text/prov-n&quot;.</p> 
+    <p>It is recommended that PROV-N files have the extension &quot;.pn&quot; (all lowercase) on all platforms.</p> 
+    <p>It is recommended that PROV-N files stored on Macintosh HFS file systems be given a file type of &quot;TEXT&quot;.</p> 
+    <p>This information that follows has been <a href="TBD">submitted to the IESG</a> for review, approval, and registration with IANA.</p> 
+    <dl> 
+      <dt>Type name:</dt> 
+      <dd>text</dd> 
+      <dt>Subtype name:</dt> 
+      <dd>prov-n</dd> 
+      <dt>Required parameters:</dt> 
+      <dd>None</dd> 
+      <dt>Optional parameters:</dt> 
+      <dd><tt>charset</tt> — this parameter is required when transferring non-ASCII data. If present, the value of <tt>charset</tt> is always <tt>UTF-8</tt>.</dd> 
+      <dt>Encoding considerations:</dt> 
+      <dd>The syntax of PROV-N is expressed over code points in Unicode [<a href="#UNICODE">UNICODE</a>]. The encoding is always UTF-8 [<a href="#rfc3629">RFC3629</a>].</dd> 
+      <dd>Unicode code points may also be expressed using an \uXXXX (U+0 to U+FFFF) or \UXXXXXXXX syntax (for U+10000 onwards) where X is a hexadecimal digit [0-9A-F]</dd> 
+      <dt>Security considerations:</dt> 
+      <dd>PROV-N is a general-purpose language for describing the provenance of things; applications may evaluate given data to infer more descriptions or to dereference URIs, invoking the security considerations of the scheme for that URI. Note in particular, the privacy issues in [[RFC3023]] section 10 for HTTP URIs. Data obtained from an inaccurate or malicious data source may lead to inaccurate or misleading conclusions, as well as the dereferencing of unintended URIs. 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.</dd> 
+      <dd>PROV-N 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 PROV-N documents. Security/privacy protocols must be imposed which reflect the sensitivity of the embedded information.</dd> 
+      <dd>PROV-N can express data which is presented to the user, for example, label attributes. Application rendering strings retrieved from untrusted PROV-N documents 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.</dd> 
+      <dd>PROV-N uses qualified names mappeable to IRIs as term identifiers. Applications interpreting data expressed in PROV-N should address the security issues of
+  <a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a> [[RFC3987]] Section 8, as well as
+  <a class="norm" href="http://www.ietf.org/rfc/rfc3986.txt">Uniform Resource Identifier (URI): Generic Syntax</a> [[RFC3986]] Section 7.</dd> 
+      <dd>Multiple IRIs may have the same appearance. Characters in different scripts may 
+look similar (a Cyrillic &quot;&#1086;&quot; may appear similar to a Latin &quot;o&quot;). 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).
+<!-- (<code>foo:resum&#40751;code> and <code>f&#1086;&#1086;:resume&#769;</code>)--> 
+Any person or application that is writing or interpreting data in PROV-N must take care to use the IRI that matches the intended semantics, and avoid IRIs that make look similar.
+Further information about matching of similar characters can be found 
+in <a class="inform" href="http://www.unicode.org/reports/tr36/">Unicode Security 
+Considerations</a> [[UNISEC]] and
+<a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource 
+Identifiers (IRIs)</a> [[!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> 
+      <dt>Additional information:</dt> 
+      <dt>Magic number(s):</dt> 
+      <dd>PROV-N documents may have the strings 'bundle' near the beginning of the document.</dd> 
+      <dt>File extension(s):</dt> 
+      <dd>".pn"</dd> 
+      <dt>Base URI:</dt> 
+      <dd>None</dd> 
+      <dt>Macintosh file type code(s):</dt> 
+      <dd>&quot;TEXT&quot;</dd> 
+      <dt>Person &amp; email address to contact for further information:</dt> 
+      <dd>TBD</dd> 
+      <dt>Intended usage:</dt> 
+      <dd>COMMON</dd> 
+      <dt>Restrictions on usage:</dt> 
+      <dd>None</dd> 
+      <dt>Author/Change controller:</dt> 
+      <dd>The PROV-N specification is the product of Luc Moreau and Paolo Missier. A W3C Working Group may assume maintenance of this document; W3C reserves change control over this specifications.</dd> 
+    </dl> 
+ 
 </section>