OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (MQTT-186) 1.2 Normative References, Unicode version 6.3.0 - or later?


     [ https://tools.oasis-open.org/issues/browse/MQTT-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Niblett updated MQTT-186:
-------------------------------

    Proposal: 
There is no text in the specification that depends on a specific version of Unicode, therefore we should use the "versionless" citation for the Unicode spec.  This means 

1. In section 1.2 remove

[Unicode63]
The Unicode Consortium. The Unicode Standard, Version 6.3.0, (Mountain View, CA: The Unicode Consortium, 2013. ISBN 978-1-936213-08-5) http://www.unicode.org/versions/Unicode6.3.0/

and replace it with  

[Unicode] 
The Unicode Consortium. The Unicode Standard. http://www.unicode.org/versions/latest/ 

2. Replace [Unicode63] with [Unicode] wherever it appears in the remainder of the document

  was:Clarify if conformance was intended to be in terms of Unicode 6.3.0 or if conformance was intended to be allowed for conformance to later versions of the Unicode standard. 


> 1.2 Normative References, Unicode version 6.3.0 - or later?
> -----------------------------------------------------------
>
>                 Key: MQTT-186
>                 URL: https://tools.oasis-open.org/issues/browse/MQTT-186
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.1.1
>         Environment: References
>            Reporter: Patrick Durusau
>
> The citation of a specific version of Unicode, without more, does not allow for applications that conform to a later version of Unicode to conform to your specification.
> For example, under 1.4.1.2 UTF-8 encoded strings, you say in part:
> *****
> The encoded data MUST be well-formed UTF-8 as defined by the Unicode spec [Unicode63] and restated in RFC 3629 [RFC 3629].
> *****
> I take that to be a normative statement that requires conformance to UTF-8 as defined by Unicode version 6.3.0. Do you agree?
> That would mean an application that conforms to Unicode version 7.0, would not conform to your specification, even if it meets all other requirements.
> I don't think that was your intent. 
> There is a phrase used in ISO work that might be adaptable to your situation:
> *****
> The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. 
> *****
> I would have 1.2 Normative References as your title and then use the last two sentences, thus: 
> *****
> For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. 
> *****
> That gives you the flexibility to decide if you want to define conformance against a particular version of a normative reference or if you want to allow later versions of the same reference to be used for conformance purposes. 



--
This message was sent by Atlassian JIRA
(v6.1.1#6155)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]