Re: [ietf-types] Request for review of N-Triples (an RDF serialization) media type: application/n-triples

Bjoern Hoehrmann <> Sat, 05 May 2012 20:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1273021F8611 for <>; Sat, 5 May 2012 13:10:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_48=0.6]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id JGAxuw967Z6z for <>; Sat, 5 May 2012 13:10:45 -0700 (PDT)
Received: from ( []) by (Postfix) with SMTP id 1413221F860E for <>; Sat, 5 May 2012 13:10:44 -0700 (PDT)
Received: (qmail invoked by alias); 05 May 2012 20:10:43 -0000
Received: from (EHLO HIVE) [] by (mp039) with SMTP; 05 May 2012 22:10:43 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1+S5QZiPmiSDVJ7vqvO5itNRenQHxW6dmwM5lcOmg rAeYA3nj3luH+5
From: Bjoern Hoehrmann <>
To: Eric Prud'hommeaux <>
Date: Sat, 05 May 2012 22:10:45 +0200
Message-ID: <>
References: <>
In-Reply-To: <>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Subject: Re: [ietf-types] Request for review of N-Triples (an RDF serialization) media type: application/n-triples
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 05 May 2012 20:10:57 -0000

* Eric Prud'hommeaux wrote:
>Type name:
>    application
>Subtype name:
>    n-triples
>Required parameters:
>    None
>Optional parameters:
>    None
>Encoding considerations:
>    The syntax of N-Triples is expressed over code points in Unicode [UNICODE]. The encoding is always UTF-8 [UTF-8].
>    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]

This is supposed to simply say something like "8bit" or "binary", see
RFC 4288 for details.

>Security considerations:

I have not look at these, but since this is very long, it might make
more sense to have this as part of the Security Considerations section
of the document that defines the format, and simply put a reference
into the template.

>Published specification:
>    This specification.

As I recall it, unlike for RFC registrations, IANA would put this in
a document on their site, so this should give a full(er) citation.

If you want to say anything about fragment identifiers, like what the
`#example` in `` refers to, or
if you want to discourage such usage, that should be included. Not a
requirement currently, but since this is an RDF type, this might be
Björn Höhrmann · ·
Am Badedeich 7 · Telefon: +49(0)160/4415681 ·
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 ·