It should be no surprise. CS Transform handed over their original work to the TC as a formal “Contribution” that served to bootstrap the whole endeavor. Several
people with whom they worked wanted to be parties to the work’s further development in OASIS. I think that it is quite common for new TC’s who bring new members to OASIS to be involved with a key sponsor of the work.
The important thing is that any OASIS member can join any TC – and many did, like myself, who had no prior knowledge of or affiliation with CS Transform. I
found the work challenging in terms of the OASIS process – which is historically designed to work with technical and directly implementable specifications (and which possibly is at the origin of some of Patrick’s concerns – but we ensured that the process
was respected in every detail.
The proposal may not be to everyone’s liking but to claim as Patrick does that we have somehow “broken the rules” is simply not true.
Thanks for taking a detailed look at the work and I hope that you can support it
From: Paul Fremantle [mailto:firstname.lastname@example.org]
Sent: Tuesday, 23 April, 2013 17:53
To: Patrick Durusau
Subject: Re: [chairs] TGF Minutes Report
One thing that I find interesting is in relation to this aspect of the TC process.
""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."
With regard to the five statements of use:
One of the SOU's comes from CS Transform (whose CEO is one of the editors).
Two more come from clients of CS Transform.
Two are not linked (as far as I know) to CS Transform.
In addition the Chair is a retired employee of CS Transform.
If this was an interoperability standard with a requirement for multiple independent implementations I would be questioning the independence of at least 3 of the 5 statements of use. But its not.
On 24 April 2013 00:23, Patrick Durusau <email@example.com> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
I did promise to review the TGF minutes for discussion of conformance.
As part of that review, note that file: TCminutes2013_02_21.rtf has
the correct date but the document has the header: "Meeting 21 March
2013" but refers to the minutes of 17th of January for approval. So
the file name is correct, but the heading in the file is wrong.
The TGF TC did discuss conformance clauses, but in 2011. Look at
IssuesList-2011-12-14.xlsx to find the notes.
While the wording of the conformance clauses is discussed, the issues
that I raised of allowing *any* model were not.
For the various posts following my initial one, I would note that no
one had addressed the merits of my objection.
As several of the posts have made clear, the timing of these
objections is not an issue. The TC would have dismissed them and we
would be exactly where we are today.
Only the vote of OASIS members controls the quality of OASIS standards.
Are you an "any model" OASIS member?
If not, vote no.
Hope everyone is having a great day!
Technical Advisory Board, OASIS (TAB)
Former Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
Another Word For It (blog): http://tm.durusau.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -
-----END PGP SIGNATURE-----
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair, VP, Apache Synapse
UK: +44 207 096 0336
US: +1 646 595 7614
wso2.com Lean Enterprise Middleware
Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply
to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any errors or omissions.