[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] Inline Markup Subcommittee
Hi Yves, Your proposal looks good to me. Best, Magnus -----Original Message----- From: Yves Savourel [mailto:ysavourel@translate.com] Sent: Wednesday, March 03, 2010 8:01 AM To: xliff@lists.oasis-open.org Subject: [xliff] Inline Markup Subcommittee Hi everyone, Just a few notes to get the ball rolling for the new subcommittee on inline markup representation. As Bryan noted, the OASIS handbook says little about subcommittees: ========== 2.14 TC Subcommittees The TC may by Resolution create a subcommittee (SC). The Resolution must be minuted, and must include the name, statement of purpose, list of deliverables, and name of the Chair of the SC. All of these items must fall within the Charter of the TC and conform to OASIS policy. The deliverables of the SC are made only to the TC. Members of the SC must first be Members of the TC. Observers of a TC may be Observers of a SC, but may not become SC members without first becoming a Member of the TC. An SC member may resign from the SC and remain a Member of the TC. ========== I certainly don't want to get us bogged down on procedural details, but it sounds like the resolution itself needs to includes name, statement, deliverables and chair, to be valid. So, I would propose to hammer down the remaining details by email and just re-issue one resolution stating all the required entries when we have everything. Name: Inline Markup Subcommittee (we'll need a path abbreviation, maybe: 'xliff-inline'). Statement of purpose (almost verbatim from the Feb-02 resolution): "The purpose of this subcommittee is to come up an inline markup for XLIFF and TMX based on the requirements gathered by the TC so far (http://wiki.oasis-open.org/xliff/OneContentModel/Requirements?action=re call&rev=38" And the part we are missing, the deliverables: Maybe something like: "The deliverables of this subcommittee is a written proposal for the XLIFF TC regarding how to markup information within text content. The document will include specification-like parts defining the element(s) and attribute(s) proposed. It may also include some notes about processing expectations, and notes about correspondences with TMX." Any thoughts? -yves --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php </pre> <BR style="font-size:4px;"> <a href = "http://www.sdl.com"><img src="http://www.sdl.com/images/email logo_150dpi-01.png" alt="www.sdl.com" border="0"/></a> <BR> <font face="arial" size="2" "><a href = "http://www.sdl.com" style="color:005740; font-weight: bold">www.sdl.com</a> <BR> <BR> <font face="arial" size="1" color="#736F6E"> <b>SDL PLC confidential, all rights reserved.</b> If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us.<BR> SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207.<BR> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. </font>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]