[OASIS Issue Tracker] (AMQPBINDMAP-38) Grammer, sect 1, 2nd bullet

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

    [ https://issues.oasis-open.org/browse/AMQPBINDMAP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62186#comment-62186 ] 

Stefan Hagen commented on AMQPBINDMAP-38:
-----------------------------------------

+1 for the rewording as published in https://www.oasis-open.org/apps/org/workgroup/amqp-bindmap/download.php/57834/amqp-wsb-v1.0-wd09.pdf?referring_url=%2Fkws.

A nit: The comma is misplaced in rendered last line of first list item of pdf "there":

I would change "an AMQP client library and an AMQP message broke,r separated by a firewall." accordingly to "an AMQP client library and an AMQP message broker, separated by a firewall."

Thanks for letting an async comment inspire ;-)


> Grammer, sect 1, 2nd bullet
> ---------------------------
>
>                 Key: AMQPBINDMAP-38
>                 URL: https://issues.oasis-open.org/browse/AMQPBINDMAP-38
>             Project: OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) TC
>          Issue Type: Bug
>          Components: Websockets Binding
>    Affects Versions: wd08
>            Reporter: Steve Huston
>            Assignee: John Fallows
>            Priority: Trivial
>
> "Browser-based messaging. Since many Web browsers have built-in support for the WebSocket protocol, then this binding can be used to enable AMQP messaging through to the browser thereby enable a broad range of browser-based messaging scenarios."
> remove "then", change 2nd "enable" to "enabling"
> change to:
> "Browser-based messaging. Since many Web browsers have built-in support for the WebSocket protocol, this binding can be used to enable AMQP messaging through to the browser thereby enabling a broad range of browser-based messaging scenarios."



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)