- From: Marcos Caceres <w3c@marcosc.com>
- Date: Tue, 26 Feb 2013 18:11:47 +0000
- To: Bjoern Hoehrmann <derhoermi@gmx.net>
- Cc: Fabrice Desre <fabrice@mozilla.com>, "public-sysapps@w3.org" <public-sysapps@w3.org>
Hi Bjoern,
WOW! Thanks for the speedy check! One small query below, if you have a minute.
On Tuesday, 26 February 2013 at 18:02, Bjoern Hoehrmann wrote:
> * Marcos Caceres wrote:
> > Required parameters:
> > n/a
> >
> > Optional parameters:
> > n/a
>
>
>
> These should be uppercase per RFC 6838.
Fixed.
>
> > Encoding considerations:
> > 8bit if UTF-8; binary if UTF-16 or UTF-32
>
> This should defer to other specifications per RFC 6839, I believe.
Is it ok if I just defer to the JSON spec? Would I just say "See RCFXXXX"?
>
> > Applications that use this media type:
> > FireFox OS, ??
>
> This is supposed to list the kind of application that uses the type, not
> a list of individual products ("Spreadsheet applications", not "Excel").
Ah right.
> > Additional information:
> >
> > Magic number(s):
> > n/a
>
> As above.
Fixed
> > File extension(s):
> > .webapp
>
>
> That choice requires some justification.
Um … FireFox OS did it?
> > Intended usage:
> > Common
>
>
> The convention is all-uppercase.
OK THEN :)
> > Author:
> > W3C's System Application Working Group.
> >
> > Change controller:
> > W3C's System Application Working Group.
>
>
> The convention is to make the W3C the change controller, not a WG; one
> reason is that Working Group ordinarily cease to exist after some time.
Makes sense.
>
> I note that the Fragment Identifier considerations are absent.
I will add one, but it's N/A (or does not apply).
Received on Tuesday, 26 February 2013 18:12:19 UTC