
My reasoning is 1) consistency and 2) in the examples a float value of 2.0 is shown as being quoted. Perhaps this is unintended and should be unquoted. If so then 1) is a minor consideration and '.' does not need be included in the separator list, unless for a want of consistency. Andy -----Original Message----- From: Ralf Nyren [mailto:ralf@nyren.net] Sent: Monday, August 16, 2010 3:32 PM To: Edmonds, AndrewX; Andy Edmonds Cc: occi-wg@ogf.org Subject: Re: [occi-wg] HTTP Header Serialization Format, use of Attribute header On Mon, 16 Aug 2010 16:19:05 +0200, Edmonds, AndrewX <andrewx.edmonds@intel.com> wrote:
As we use '.' as a character to denote namespace delineation we should also add this to the list of separators, incl. 2616.
We could but I do not see why that would be necessary. The comma separates field values and the equal sign separate attribute name from attribute value. So from the parser's perspective only those two characters need be quoted. However, for consistency I thought it to be a good idea to include the full separator list from RFC2616. But you maybe have an example where the use of an unquoted '.' would confuse the parser? I do however think we should add a policy on attribute names. Both valid characters etc but also the naming policy because the namespace is shared by all categories. This could perhaps go into the Extensions document we talked about. regards, Ralf ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.