[OASIS Issue Tracker] Commented: (OBIX-35) Detailed comment on URIs

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/OBIX-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35323#action_35323 ] 

Craig Gemmill  commented on OBIX-35:
------------------------------------

I believe the changes made in WD16 will address this.  RFC3986 is now referenced directly in the affected section.

> Detailed comment on URIs
> ------------------------
>
>                 Key: OBIX-35
>                 URL: http://tools.oasis-open.org/issues/browse/OBIX-35
>             Project: OASIS Open Building Information Exchange (oBIX) TC
>          Issue Type: Improvement
>          Components: OBIX 1.1 Specification
>    Affects Versions: oBIX 1.1 PR01
>         Environment: Toby Considine
>            Reporter: Toby Considine
>            Assignee: Craig Gemmill 
>
> 207-218 See example of how the full use of a URI is described in Web Sockets:
> Quoting:
> The term "URI" is used in this document as defined in [RFC3986].
>  
>    When an implementation is required to _send_ data as part of the
>    WebSocket Protocol, the implementation MAY delay the actual
>    transmission arbitrarily, e.g., buffering data so as to send fewer IP
>    packets.
>  
>    Note that this document uses both [RFC5234] and [RFC2616] variants of
>    ABNF in different sections.
>  
> This specification defines two URI schemes, using the ABNF syntax
>    defined in RFC 5234 [RFC5234], and terminology and ABNF productions
>    defined by the URI specification RFC 3986 [RFC3986].
>  
>           ws-URI = "ws:" "//" host [ ":" port ] path [ "?" query ]
>           wss-URI = "wss:" "//" host [ ":" port ] path [ "?" query ]
>  
>           host = <host, defined in [RFC3986], Section 3.2.2>
>           port = <port, defined in [RFC3986], Section 3.2.3>
>           path = <path-abempty, defined in [RFC3986], Section 3.3>
>           query = <query, defined in [RFC3986], Section 3.4>
>  
>    The port component is OPTIONAL; the default for "ws" is port 80,
>    while the default for "wss" is port 443.
>  
>    The URI is called "secure" (and it is said that "the secure flag is
>    set") if the scheme component matches "wss" case-insensitively.
>  
>    The "resource-name" (also known as /resource name/ in Section 4.1)
>    can be constructed by concatenating the following:
>  
>    o  "/" if the path component is empty
>  
>    o  the path component
>  
>    o  "?" if the query component is non-empty
>  
>    o  the query component
>  
>    Fragment identifiers are meaningless in the context of WebSocket URIs
>    and MUST NOT be used on these URIs.  As with any URI scheme, the
>    character "#", when not indicating the start of a fragment, MUST be
>    escaped as %23.
>  
>    1.  The components of the WebSocket URI passed into this algorithm
>        (/host/, /port/, /resource name/, and /secure/ flag) MUST be
>        valid according to the specification of WebSocket URIs specified
>        in Section 3.  If any of the components are invalid, the client
>        MUST _Fail the WebSocket Connection_ and abort these steps.
>  
>  
> Notice that the result  is clearer, and easier to code to. The commenter is *not* suggesting* these are the oBIX rules, merely stating that a form similar to this would be better for declaring what is expected.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira