- From: Martin J. Dürst <duerst@it.aoyama.ac.jp>
- Date: Mon, 30 Jul 2012 11:05:24 +0900
- To: Bjoern Hoehrmann <derhoermi@gmx.net>
- CC: Luc Moreau <l.moreau@ecs.soton.ac.uk>, "team-prov-chairs@w3.org" <team-prov-chairs@w3.org>, public-prov-comments@w3.org, ietf-types@ietf.org
On 2012/07/27 21:41, Bjoern Hoehrmann wrote: > * Luc Moreau wrote: >> Type name: >> text >> >> Subtype name: >> provenance-notation >> >> Required parameters: >> None >> >> Optional parameters: >> charset — this parameter is mandatory. The value of charset is always UTF-8. > > This seems to need work, it's not optional if it is mandatory, is it. > And The second sentence is a statement of fact that is easily contr- > dicted by content. > >> Encoding considerations: >> The syntax of PROV-N is expressed over code points in Unicode >> [UNICODE5]. 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] Why [UNICODE5]? The newest version is Unicode 6.2. Is PROV-N limited to Unicode version 5? That would be a very bad idea. Regards, Martin. > This field should contain one of the values in RFC 4288 or its successor > if that has been approved already, like "binary". > >> 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. > > You can remove the first sentence, this is to give people an idea > whether this is for Word processing applications or cryptographic > key exchange systems or whatever. > >> Person& email address to contact for further information: >> public-prov-comments@w3.org > > This does not qualify as "Person& email address".
Received on Monday, 30 July 2012 02:06:04 UTC