OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [xliff] Re: XLIFF 1.2 Committee Draft Spec


Hi Everyone,

I also vote for option #3.

Best Regards,

AZ

Doug Domeny wrote:
> I favor option #2. It keeps the schedule and helps motivate us to 
> review—I know I tend to wait until the last day. If for some reason many 
> people can’t attend the conference call, then option #3 become the back 
> up plan. That is, vote next Tuesday if quorum is met, otherwise, post it 
> as an online ballot.
> 
>  
> 
> Regards,
> 
>  
> 
> Doug Domeny
> 
> Software Analyst
> 
>  
> 
> Ektron, Inc.
> 
> +1 603 594-0249 x212
> 
> http://www.ektron.com
> 
>  
> 
> ------------------------------------------------------------------------
> 
> *From:* Tony Jewtushenko [mailto:tony.jewtushenko@productinnovator.com]
> *Sent:* Tuesday, May 09, 2006 11:00 AM
> *To:* xliff@lists.oasis-open.org
> *Cc:* ddomeny@ektron.com
> *Subject:* RE: [xliff] Re: XLIFF 1.2 Committee Draft Spec
> 
>  
> 
> Thanks to allwho submitted their spec issues.  While I can complete the 
> revisions to the spec spotted and submitted bar one,  I couldn't get it 
> done by the deadline for the ballot, which has in fact passed (10am or 
> even 11am EST).
> 
>  
> 
> Although most of the revisions are small,there are a lot of them and 
> then there's the one pointed out by Rudolfo regarding use of spaces in 
> seg-source between mrk's which can't be fixed by a simple revision.  
> We'll have to discuss it and make a decision.  In any case I'll send out 
> a revised 1.2 Committee Draft spec late today that will address the 
> typos, missing bits and details that were submitted.
> 
>  
> 
> We had twoscenarios outlined as of last week for how the ballot would 
> proceed:
> 
> 1/publish finalcommittee draft spec today - have 1 week ballot in time 
> for next Tuesday's TC meeting.
> 
> 2/if not published today, spec would be published before next Tuesday 
> and would have a role call ballot to approve as Committee Draft.
> 
>  
> 
> I would like to propose a 3rd option - to postpone the TC teleconference 
> for one week until Tuesday 23 May, so we work towards publishing a final 
> committee draft before next Tuesday 16 May, and set up a web ballot 
> commencing 1 week before the TC teleconference.
> 
>  
> 
> Option 1 is no longer viable, - so we're down to 2 options still - #2 
> and #3.
> 
>  
> 
> Any thoughts?
> 
>  
> 
> Regards,
> 
> Tony
> 
>  
> 
> -----Original Message-----
> *From:* Doug Domeny [mailto:ddomeny@ektron.com]
> *Sent:* 09 May 2006 09:55
> *To:* xliff@lists.oasis-open.org
> *Subject:* RE: [xliff] Re: XLIFF 1.2 Committee Draft Spec
> 
>  
> 
> We are definitely making good progress cleaning up these little things.
> 
>  
> 
> See comments below.
> 
>  
> 
> Regards,
> 
>  
> 
> Doug Domeny
> 
> Software Analyst
> 
>  
> 
> Ektron, Inc.
> 
> +1 603 594-0249 x212
> 
> http://www.ektron.com <http://www.ektron.com/>
> 
>  
> 
> ------------------------------------------------------------------------
> 
> *From:* Rodolfo M. Raya [mailto:rmraya@heartsome.net]
> *Sent:* Monday, May 08, 2006 11:38 PM
> *To:* Tony Jewtushenko
> *Cc:* xliff@lists.oasis-open.org
> *Subject:* Re: [xliff] Re: XLIFF 1.2 Committee Draft Spec
> 
>  
> 
> Hi All,
> 
> Some details that need attention:
> 
> 1) In section 3.2.5 the description of <mrk> element mentions the 
> optional attribute equiv-text but the attribute is not included in the 
> list of optional attributes for that element.
> 
> [doug] The equiv-text attribute is not valid in the <mrk> element.
> 
> 
> 3) <seg-source> is a new element born with old bad habits. It has an 
> optional "ts" attribute that is deprecated. I don't see a reason for 
> adding deprecated stuff to something new.
> 
> [doug] In principle, I agree that deprecated items should not be added 
> to new structures. However, I can see the need to duplicate <source> 
> attributes in <seg-source>. Since <source> supports ‘ts’, it may be 
> helpful to use it in <seg-source>, but I can go either way.
> 
> :
> 
> 
> 
> 
> ---------------------------------------------------------------------------------------------------
> *Text inserted by Panda Platinum 2005 Internet Security:*
> 
> This message has NOT been classified as spam. If it is unsolicited mail 
> (spam), click on the following link to reclassify it: It is spam! 
> <http://127.0.0.1:6083/Panda?ID=pav_51599&SPAM=true>
> ---------------------------------------------------------------------------------------------------


-- 


email - azydron@xml-intl.com
smail - c/o Mr. A.Zydron
	PO Box 2167
         Gerrards Cross
         Bucks SL9 8XF
	United Kingdom
Mobile +(44) 7966 477 181
FAX    +(44) 1753 480 465
www - http://www.xml-intl.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
may not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version. Unless
explicitly stated otherwise this message is provided for informational
purposes only and should not be construed as a solicitation or offer.






[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]