Re: [dxwg] Conneg action 356 (#1037)

@larsgsvensson addressing your points above. 

For 1., text changed to:

> For any given pair of communicating machines, the the roles of <em>client</em> and <em>server</em> may be reversed as information is requested back and forth.

For 2., text changed to:

> As per [ยง 6.2 Profile Identification](, all profiles MUST be identified by URI since URIs are universally unique and therefore do not require registration to avoid identifier duplication. However, systems conforming to either of the QSA functional profiles of this specification, instead of using URIs to identify profiles during client/server interactions, MAY use un-registered and non-universally unique tokens to identify profiles but, if they do, they MUST provide a way for clients to discover profile token/URI mappings. 

GitHub Notification of comment by nicholascar
Please view or discuss this issue at using your GitHub account

Received on Monday, 12 August 2019 22:39:55 UTC