Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] FW: [mqtt] Statements of Use

Sounds good. If we need to help from the Foundation please let me know.


-----Original Message-----
From: paho-dev-bounces@xxxxxxxxxxx [mailto:paho-dev-bounces@xxxxxxxxxxx] On
Behalf Of Roger Light
Sent: May-15-14 7:03 PM
To: General development discussions for paho project
Subject: Re: [paho-dev] FW: [mqtt] Statements of Use

Hi Ian,

As Ian says - it's in hand. It's about the busiest time of the year for me
though, never mind anything else, so I haven't looked at it properly yet.



On Thu, May 15, 2014 at 10:56 PM, Ian Craggs
<icraggs@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> Ian,
> I've spoken to Richard and I believe all is in hand.  I am told that 
> Roger has agreed to submit a statement for Mosquitto.  I suggested to 
> Richard that Paho wasn't yet ready to submit a statement, as we are 
> planning to implement
> 3.1.1 support in all the clients for June. Perhaps I was being too 
> rigorous when I said that.
> Also "A party can only issue one Statement of Use for a given
> - I'm not clear whether that means one for the Eclipse Foundation in 
> its entirety...
> But I believe that the needed statements are forthcoming anyway. I'll 
> keep in touch with Richard in case that changes.
> Ian
> On 05/15/2014 06:45 PM, Ian Skerrett wrote:
>> Will the Paho and Mosquitto project teams submit a Statement of Use 
>> to the Oasis TC?
>> -----Original Message-----
>> From: mqtt@xxxxxxxxxxxxxxxxxxxx [mailto:mqtt@xxxxxxxxxxxxxxxxxxxx] On 
>> Behalf Of Mr. Richard Coppen
>> Sent: May-15-14 1:03 PM
>> To: mqtt@xxxxxxxxxxxxxxxxxxxx
>> Subject: [mqtt] Statements of Use
>> Hi all,
>> We're at the point in the OASIS standardisation process where we need 
>> to obtain Statements of Use for MQTT 3.1.1. This will enable us to 
>> proceed to Candidate OASIS Specification and then into the final 
>> stages of standardisation. The full OASIS process can be found here > 
>> < In 
>> summary, a statement of use if defined as follows:
>> "Statement of Use", with respect to a Committee Specification, is a 
>> written statement that a party has successfully used or implemented 
>> that specification in accordance with all or some of its conformance 
>> clauses specified in Section 2.18, identifying those clauses that 
>> apply, and stating whether its use included the interoperation of 
>> multiple independent implementations. The Statement of Use must be 
>> made to a specific version of the Committee Specification and must 
>> include the Specification's approval date. The party may be an OASIS 
>> Member or a non-member. In case of a non-member, the Statement of Use 
>> must be submitted on the TC comment-list. A TC may require a 
>> Statement of Use to include hyperlinks to documents, files or 
>> demonstration transcripts that enable TC members to evaluate the 
>> implementation or usage. A Statement of Use submitted to the TC must 
>> be approved by TC resolution as an acceptable Statement of Use with 
>> respect to the Committee Specification. A party can o
> nl
>>   y issue one Statement of Use for a given specification. When issued 
>> by an OASIS Organizational Member, a Statement of Use must be 
>> endorsed by the Organizational Member's Primary Representative.
>> To qualify, an implementer just needs to notify the Technical 
>> Committee, by submitting their 'statement of use' to the mqtt-comment 
>> list
>> (mqtt-comment@xxxxxxxxxxxxxxxxxxxx) TC Members may notify the TC via 
>> the TC's mailing list. This should be in the format of:
>> ...
>> <insert name / org here> has successfully implemented the OASIS MQTT 
>> Version 3.1.1 Committee Specification <link to MQTT 3.1.1 Committee
>> Specification> dated <nn may 2014>, in accordance with the 
>> Specification> conformance
>> clauses <Client | Server | Both> defined in Section 7 Conformance of 
>> the specification. This use of the specification includes 
>> interoperation with other similar independent implementations.
>> ...
>> The final link to the Committee Specification will be available once 
>> the current ballot closes. In terms of conformance clauses this will 
>> be the same as for CSD02 and our most recent 'non-material' update 
>> available here > 
>> wg_abbrev=mqtt
>> <
>> If you would like to submit (or propose) a Statement of Use for an 
>> 3.1.1 implementation please reply to this email and let the TC know.
>> Best regards
>> Richard
>> _______________________________________________
>> paho-dev mailing list
>> paho-dev@xxxxxxxxxxx
> --
> Ian Craggs
> icraggs@xxxxxxxxxx                 IBM United Kingdom
> Committer on Paho, Mosquitto
> _______________________________________________
> paho-dev mailing list
> paho-dev@xxxxxxxxxxx
paho-dev mailing list

Back to the top