That will be ok for OASIS members so long as you extract it into some stand alone document that can be brought into Kavi. The survey couldn't be the archive of the final SoUs.
It won't work for non-OASIS contributors though given that the language in the TC Process is unambiguous. They *must* send their statements in via xliff-comment@
I would rather see something like you propose, actually - there's a lot of value in having consistent, structured input. But unfortunately the process doesn't allow for that right now.
/chet
On Tue, Apr 1, 2014 at 2:31 PM, Dr. David Filip <> wrote:
Thanks, Chet,
the reason we go through the questionnaire is to obtain accurate, comparable and structured info, from all implementers, not to source candidates.
We could make the survey monkey respondent click approval with the relevant IPR policy, i.e. make the IPR link part of the boiler plate they will be approving, or put the full language inside whatever you prefer..
Does that sound as an avenue?
Thanks
dF
How does that sound?
Dr. David Filip
=======================
LRC | CNGL | LT-Web | CSIS
University of Limerick, Ireland
telephone: +353-6120-2781
cellphone: +353-86-0222-158
facsimile: +353-6120-2734
http://www.cngl.ie/profile/?i=452
mailto:
On Tue, Apr 1, 2014 at 7:22 PM, Chet Ensign <> wrote:
This will need some tweaking to work.
Here is the definition of SoU from 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. 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 only 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.
Note the emphasized part requiring submission to xliff-comment@ for non-OASIS members.
So the Survey Monkey entry alone won't satisfy that requirement. Not sure how we could make that work. Submitters to xliff-comment have to subscribe - that's how we ensure that they have been exposed to the IPR obligations. What if you use this to gather your candidates and then follow up with them to get the actual SoU. So instead of
"I understand that the SOU MAY be used..."
Put
"The TC is welcome to contact me to obtain a written Statement of Use."
?
/chet
On Tue, Apr 1, 2014 at 1:45 PM, Dr. David Filip <> wrote:
Thanks, Chet,
I just wanted to run some of the language we plan to use by you.
Our plan is to use a Survey Monkey questionnaire to collect the statements.
The questionnaire has a tick box for each feature and for agent profiles defined in the spec, so I think it exceeds the requirement for specifying which parts of the spec each statement conforms to
I copy paste here the language that I had proposed to make the questionnaire collected data count as SOU.
And the plan is of course to approve those SOU in our next meeting in 2 weeks time.
The proposed questionnaire language follows, can you please let us know if it sounds OK?
===============================
The responses provided through this questionnaire are intended as a Statement of Use (SOU) for
[XLIFF-2.0]
XLIFF Version 2.0. Edited by Tom Comerford, David Filip, Rodolfo M. Raya, and Yves Savourel. 31 March 2014. OASIS Committee Specification 01. http://docs.oasis-open.org/xliff/xliff-core/v2.0/cs01/xliff-core-v2.0-cs01.html. The latest version: http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html.
I understand that the SOU MAY be used by the XLIFF TC [TC link] to progress the Committee Specification to OASIS standard.
X I agree
X My organization is an OASIS member
[below is only relevant if they are OASIS member]
X I am the primary representative of my organization in OASIS
[XOR]
X This SOU will be endorsed by my organizations primary representative on the TC mailing list or the TC comment list.
==============end of the SOU language to make the questionnaire data count
Dr. David Filip
=======================
LRC | CNGL | LT-Web | CSIS
University of Limerick, Ireland
telephone: +353-6120-2781
cellphone: +353-86-0222-158
facsimile: +353-6120-2734
http://www.cngl.ie/profile/?i=452
mailto:
On Tue, Apr 1, 2014 at 6:17 PM, Chet Ensign <> wrote:
If you all will now be soliciting Statements of Use, make sure they meet the requirements (definition 'ar' in the TC Process - https://www.oasis-open.org/policies-guidelines/tc-process):
the name the party
the name the CS by title and version and include the approval date
they refer to the conformance clauses they met
they state whether the use included multiple independent interoperable implementations
Here is an example of an SoU that meets those:
I, Angus Telfer, as INETCO Systems Ltd's OASIS Primary Representative, endorse this Statement
of Use from INETCO Systems Ltd.
INETCO Systems Ltd. has successfully implemented the OASIS AMQP Version 1.0
Committee Specification 01 ""amqp-core-complete-v1.0-cs01.pdf" dated 20 July
2012 in accordance with the conformance clauses defined in Section 0.2
Conformance for Parts 1 through 5 of the specification. This use of the
specification includes interoperation with other similar independent
implementations.
Also, the TC will at some point need to pass a resolution accepting the SoUs.
Best,
/chet
On Tue, Apr 1, 2014 at 1:07 PM, Dr. David Filip <> wrote:
The boiler plate could be as simple as this:
(Please send feedback)
The responses provided through this questionnaire are intended as a Statement of Use (SOU) for
[XLIFF-2.0]
XLIFF Version 2.0. Edited by Tom Comerford, David Filip, Rodolfo M. Raya, and Yves Savourel. 31 March 2014. OASIS Committee Specification 01. http://docs.oasis-open.org/xliff/xliff-core/v2.0/cs01/xliff-core-v2.0-cs01.html. The latest version: http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html.
I understand that the SOU MAY be used by the XLIFF TC [TC link] to progress the Committee Specification to OASIS standard.
X I agree
X My organization is an OASIS member
[below is only relevant if they are OASIS member]
X I am the primary representative of my organization in OASIS
[XOR]
X This SOU will be endorsed by my organizations primary representative on the TC mailing list or the TC comment list.
Dr. David Filip
=======================
LRC | CNGL | LT-Web | CSIS
University of Limerick, Ireland
telephone: +353-6120-2781
cellphone: +353-86-0222-158
facsimile: +353-6120-2734
http://www.cngl.ie/profile/?i=452
mailto:
On Tue, Apr 1, 2014 at 5:58 PM, Dr. David Filip <> wrote:
This is the specification link
http://docs.oasis-open.org/xliff/xliff-core/v2.0/cs01/xliff-core-v2.0-cs01.html
Again, this is not yet life, but should become bfeore we start collecting the SOUs
The spec should be identified using this block
[XLIFF-2.0]
XLIFF Version 2.0. Edited by Tom Comerford, David Filip, Rodolfo M. Raya, and Yves Savourel. 31 March 2014. OASIS Committee Specification 01. http://docs.oasis-open.org/xliff/xliff-core/v2.0/cs01/xliff-core-v2.0-cs01.html. The latest version: http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html.
Dr. David Filip
=======================
LRC | CNGL | LT-Web | CSIS
University of Limerick, Ireland
telephone: +353-6120-2781
cellphone: +353-86-0222-158
facsimile: +353-6120-2734
http://www.cngl.ie/profile/?i=452
mailto:
On Tue, Apr 1, 2014 at 5:56 PM, Dr. David Filip <> wrote:
Yves, thanks for this, very useful. especially the boiler plate, date and spec link.
These indeed need to be added to fulfill the OASIS SOU requirement
Cheers
dF
Dr. David Filip
=======================
LRC | CNGL | LT-Web | CSIS
University of Limerick, Ireland
telephone: +353-6120-2781
cellphone: +353-86-0222-158
facsimile: +353-6120-2734
http://www.cngl.ie/profile/?i=452
mailto:
On Tue, Apr 1, 2014 at 5:40 PM, Yves Savourel <> wrote:
Hi Lucia,
A few notes on the survey/SUO:
- in " Does your tool prevent the creation of duplicated trans-unit IDs? " we should have 'unit' not 'trans-unit'
- "21. Please select from the following required XLIFF attributes the ones that your tool can process:" list only some of the
<xliff> element (trgLang is missing)
- " 17. Which XLIFF version does your tool support?" : I assume we will remove all version but 2.0?
- There should be a place for people to provide links to their implementation, extra info, etc. (a field labeled as such, not as a
general comment area).
- All SOU I see at OASIS are looking like explicit statements, (see
https://www.oasis-open.org/search/google/statment%20of%20use?query=statment%20of%20use) maybe we need a boiler plate text field for
this. Something like:
[ ] do you want to make this survey response an official SUO
And if yes, move to a page with the boilerplate text and a field for the name of the person/organization doing the statement
and a check box saying 'I agree'.
Or something similar.
I think we also need the version and date of the spec stated somewhere.
-ys
--
/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open
--
/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open
--
/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open
