Request for review of Turtle (an RDF serialization) media type:
eric at w3.org
Tue Dec 18 12:45:49 CET 2007
W3C is about to publish a Team Submission for the RDF serialization
Turtle. A mockup of the document to be published is at
Because the document will include the text of the media type
registration, I am vetting this registration with ietf-types before
publishing the document. Some discussion about the claim to force
utf-8 encoding (and not require that in a charset parameter) can be
seen at http://lists.w3.org/Archives/Public/www-archive/2007Dec/
(Subject: Media types for RDF languages N3 and Turtle)
I got moderator-actioned for having too many folks in the Cc so
I'm Bcc'ing them all in this request for review:
"Sean B. Palmer" <sean at miscoranda.com>, Tim Berners-Lee <timbl at w3.org>,
"Daniel W. Connolly" <connolly at w3.org>, Dave Beckett <dave at dajobe.org>,
Lee Feigenbaum <lee at thefigtrees.net>, Garret Wilson <garret at globalmentor.com>,
Graham Klyne <GK at ninebynine.org>, Dan Brickley <danbri at danbri.org>,
The syntax of Turtle is expressed over code points in
Unicode[UNICODE]. The encoding is always UTF-8 [RFC3629]; the
charset parameter is not needed; though it may be included so
long as the value is '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]
Turtle uses IRIs as term identifiers. Applications interpreting data
expressed in Turtle sould address the security issues of
Internationalized Resource Identifiers (IRIs) 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 "o" 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 data in Turtle 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 Unicode Security Considerations [UNISEC] and
Internationalized Resource Identifiers (IRIs) [RFC3987] Section 8.
There are no known interoperability issues.
TBD, in the mean time, see http://www.w3.org/2007/11/21-turtle
Applications which use this media type:
No widely deployed applications are known to use this media type. It
may be used by some web services and clients consuming their data.
Turtle documents may have the strings '@prefix' or '@base' (case
dependent) near the beginning of the document.
The Turtle '@base <IRIref>' term can change the current base URI for
relative IRIrefs in the query language that are used sequentially
later in the document.
Macintosh file type code(s):
Person & email address to contact for further information:
Eric Prud'hommeaux <eric at w3.org>
Restrictions on usage:
The Turtle specification is the product of David Beckett and Tim
Berners-Lee. A W3C Working Group may assume maintenance of this
document; W3C reserves change control over this specifications.
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types",
RFC 3023, January 2001.
[RFC3629] F. Yergeau, "UTF-8, a transformation format of ISO 10646",
RFC 3629, November 2003.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, RFC
3986, January 2005.
[RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource
Identifiers (IRIs)", RFC 3987, January 2005.
[UNICODE] The Unicode Standard, Version 4. ISBN 0-321-18578-1, as
updated from time to time by the publication of new
versions. The latest version of Unicode and additional
information on versions of the standard and of the Unicode
Character Database is available at
[UNISEC] Mark Davis, Michel Suignard, "Unicode Security
office: +1.617.258.5741 NE43-344, MIT, Cambridge, MA 02144 USA
(eric at w3.org)
Feel free to forward this message to any list for any purpose other than
email address distribution.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 481 bytes
Desc: Digital signature
Url : http://www.alvestrand.no/pipermail/ietf-types/attachments/20071218/4606dbc6/attachment.bin
More information about the Ietf-types