[OPC] Discrepancy 1: Two charcters { (U+005b) and } (U+005d)

[MURATA Makoto]

Oops, I made a mistake.  As John correctly wrote in the
attachment of his mail   "Part 2 schema regex for
ST_ContentType", { and } are disallowed as part of
a token by HTTP 1.1 (RFC 2616).

I mistakenly quoted the rules from RFC 2045.

Regards,
Makoto



2015-04-07 19:01 GMT+09:00 MURATA Makoto <eb2m-mrt at asahi-net.or.jp>:

> Folks,
>
> I am going to post a sequence of emails for describing
> syntactical discrepancies among OPC, legacy HTTP 1.1,
> and revised HTTP 1.1.
>
> This e-mail is about two charcters { (U+005b) and } (U+005d).  Are
> they allowed as part of a token (and thus type/subtype/parameter
> name)?
>
> OPC as of now:  Disallowed
>
>   [\p{IsBasicLatin}-[\p{Cc}\(\)<>@
> ,;:\\"/\[\]\?=\{\}\s\t]]
>
> Legacy HTTP 1.1: Allowed
>
>   (tspecials are excluded (a negative list) )
>
>      tspecials :=  "(" / ")" / "<" / ">" / "@" /
>                    "," / ";" / ":" / "\" / <">
>                    "/" / "[" / "]" / "?" / "="
>                    ; Must be in quoted-string,
>                    ; to use within parameter values" /
>
> Revsied HTTP 1.1: Disallowed
>
>   (tchar is a positive list)
>
>      tchar          = "!" / "#" / "$" / "%" / "&" / "'" / "*"
>                     / "+" / "-" / "." / "^" / "_" / "`" / "|" / "~"
>                     / DIGIT / ALPHA
>                     ; any VCHAR, except delimiters
>
>
> Regards,
> Makoto
>



-- 

Praying for the victims of the Japan Tohoku earthquake

Makoto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20150409/9eb2d727/attachment.html>