Subject: Re: [xliff] Re: Survey/SUO feedback
Lucía, in the light of Chet's comments, the company name and responder name should be made obligatory..ThanksdFOn Tue, Apr 1, 2014 at 6:17 PM, Chet Ensign <firstname.lastname@example.org> 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 partythe name the CS by title and version and include the approval datethey refer to the conformance clauses they metthey 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 Statementof Use from INETCO Systems Ltd.INETCO Systems Ltd. has successfully implemented the OASIS AMQP Version 1.0Committee Specification 01 ""amqp-core-complete-v1.0-cs01.pdf" dated 20 July2012 in accordance with the conformance clauses defined in Section 0.2Conformance for Parts 1 through 5 of the specification. This use of thespecification includes interoperation with other similar independentimplementations.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 <David.Filip@ul.ie> 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 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 agreeX 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.
On Tue, Apr 1, 2014 at 5:58 PM, Dr. David Filip <David.Filip@ul.ie> wrote:This is the specification linkAgain, this is not yet life, but should become bfeore we start collecting the SOUsThe spec should be identified using this block
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.On Tue, Apr 1, 2014 at 5:56 PM, Dr. David Filip <David.Filip@ul.ie> 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 requirementCheersdFOn Tue, Apr 1, 2014 at 5:40 PM, Yves Savourel <email@example.com> 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.
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
Primary: +1 973-996-2298
Mobile: +1 201-341-1393Check 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: