- From: Arle Lommel <arle.lommel@gmail.com>
- Date: Mon, 21 Jan 2013 10:34:48 +0100
- To: "Lieske, Christian" <christian.lieske@sap.com>
- Cc: Felix Sasaki <fsasaki@w3.org>, public-multilingualweb-lt-comments@w3.org
Thanks Christian, Good point about an example. We'll have to discuss this in Prague. However, with regard to EN-15038, it is out of scope since it describes general process requirements for service providers and is completely agnostic as to the quality assessment methods used. TS-11669 describes details about the expectations that can (admittedly, somewhat indirectly) be turned into actual metrics, and has a slot that can point as well to information on metrics. Thus is it much more clearly (at least to me) in scope than EN-15038, which I see as completely out of scope since there is no way to go from EN-15038 to any sort of quality issue markup: the two are separate issues. -Arle On 2013 Jan 21, at 10:19 , "Lieske, Christian" <christian.lieske@sap.com> wrote: > Dear all, > > I would benefit from seeing a specific example of how to use ISO/TS-11669 in the context of itsLocQualityProfileRef. From my understanding, ISO/TS-11669 is "Translation Project Guidance". itsLocQualityProfileRef according to the ITS 2.0 draft is a reference to a "quality assessment model". > > Best regards, > Christian > > Aside: If ISO/TS-11669 is mentioned, wouldn't EN 15038 "Translation Service Requirements" also need to be mentioned? > -----Original Message----- > From: Felix Sasaki [mailto:fsasaki@w3.org] > Sent: Samstag, 19. Januar 2013 19:02 > To: Arle Lommel > Cc: Lieske, Christian; public-multilingualweb-lt-comments@w3.org > Subject: Re: Comment on ITS 2.0 specification WD > > Hi Arle, all, > > it's OK to add non-normative text; however there needs to be agreement > in the group that this addition is ok. All, if you have concerns, please > speak up in this thread. > > Best, > > Felix > > Am 18.01.13 15:45, schrieb Arle Lommel: >> Not entirely. It's already there, but we don't define what the content at the other end of the pointer is. So the suggestion was to add non-normative text about one kind of thing it might be. So no, I'm not talking about introducing anything new. >> >> -Arle >> >> On 2013 Jan 18, at 15:43 , "Lieske, Christian" <christian.lieske@sap.com> wrote: >> >>> Hi Arle, >>> >>> If I understand correctly, you are suggesting to introduce its-loc-quality-profile-ref in the spec. Is this understanding correct? >>> >>> Cheers, >>> Christian >>> ________________________________ >>> From: Arle Lommel <arle.lommel@gmail.com> >>> To: "public-multilingualweb-lt-comments@w3.org" <public-multilingualweb-lt-comments@w3.org> >>> Cc: alan melby <alan.melby@gmail.com> >>> Sent: Tuesday, January 15, 2013 4:55 AM >>> Subject: Re: Comment on ITS 2.0 specification WD >>> >>> >>> We could also state that the object pointed to by its-loc-quality-profile-ref (currently undefined) can be a set of ISO/TS-11669-compliant specifications. Since that leaves other options open, it doesn't make any normative change to the specification. >>> >>> -Arle >>> >>> >>> On 2013 Jan 15, at 12:29 , Arle Lommel <arle.lommel@dfki.de> wrote: >>> >>> Hi all, >>>> >>>> A few notes on the quality sections: >>>> >>>> >>>> 1. There is a minor typo in the listing of quality categories (in part I wrote, no less). >>>> >>>> >>>> A professzor azt modta Smithnek, hogy he would hear from his lawyer. >>>> >>>> Should read >>>> >>>> >>>> A professzor azt mondta Smithnek, hogy he would hear from his lawyer. >>>>> >>>> 2. Section 8.17.1 should mention that a determination of what issue categories are appropriate for consideration depends on the nature of the project and that for more information on setting project specifications, readers may consult ISO/TS-11669. This reference is non-normative, but it is essential to show that the ITS 2.0 quality model is related to broader standards-based trends in this area. This will also add ISO/TS-11669 to the list of references. >>>> >>>> >>>> I will work on the needed text in the next few days and submit it. >>>> >>>> >>>> Best, >>>> >>>> >>>> Arle >>> --1234169369-1608882830-1358257175=:95958 >>> Content-Type: text/html; charset=us-ascii >>> >>> <html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:14pt">Allowing for a link to ISO/TS-11669-compliant specifications, leaving other options open, would be a good start, and enough for ITS 2.0.<br><br>AKM<br><br>= = =<br><div><span><br></span></div><div><br></div> <div style="font-family: times new roman, new york, times, serif; font-size: 14pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Arle Lommel <arle.lommel@gmail.com><br> <b><span style="font-weight: bold;">To:</span></b> "public-multilingualweb-lt-comments@w3.org" <public-multilingualweb-lt-comments@w3.org> <br><b><span style="font-weight: bold;">Cc:</span></b> alan melby <alan.melby@gmail.com> <br> <b><span style="font-weight: bold;">Sent:</span></b> >>> Tuesday, January 15, 2013 4:55 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: Comment on ITS 2.0 specification WD<br> </font> </div> <br> >>> <meta http-equiv="x-dns-prefetch-control" content="off"><div id="yiv781717750"><div>We could also state that the object pointed to by its-loc-quality-profile-ref (currently undefined) can be a set of ISO/TS-11669-compliant specifications. Since that leaves other options open, it doesn't make any normative change to the specification.<div><br></div><div>-Arle<br><div> >>> >>> >>> </div> >>> <br><div><div>On 2013 Jan 15, at 12:29 , Arle Lommel <<a rel="nofollow" ymailto="mailto:arle.lommel@dfki.de" target="_blank" href="mailto:arle.lommel@dfki.de">arle.lommel@dfki.de</a>> wrote:</div><br class="yiv781717750Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap:break-word;">Hi all,<div><br></div><div>A few notes on the quality sections:</div><div><br></div><div>1. There is a minor typo in the listing of quality categories (in part I wrote, no less).</div><div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px;"><span style="font-family:sans-serif;background-color:rgb(255, 255, 255);">A professzor azt modta Smithnek, hogy he would hear from his lawyer.</span></blockquote><font face="sans-serif"><br></font><div><font face="sans-serif">Should read</font></div><div><font face="sans-serif"><br></font></div><div><blockquote style="margin:0 0 0 40px;border:none;padding:0px;"><div><span >>> style="font-family:sans-serif;background-color:rgb(255, 255, 255);">A professzor azt <b>mondta</b> Smithnek, hogy he would hear from his lawyer.</span></div><div><span style="font-family:sans-serif;background-color:rgb(255, 255, 255);"><br></span></div></blockquote><font face="sans-serif"><br></font></div><div><font face="sans-serif">2. Section 8.17.1 should mention that a determination of what issue categories are appropriate for consideration depends on the nature of the project and that for more information on setting project specifications, readers may consult ISO/TS-11669. This reference is non-normative, but it is essential to show that the ITS 2.0 quality model is related to broader standards-based trends in this area. This will also add ISO/TS-11669 to the list of references.</font></div><div><font face="sans-serif"><br></font></div><div><font face="sans-serif">I will work on the needed text in the next few days and submit >>> it.</font></div><div><font face="sans-serif"><br></font></div><div><font face="sans-serif">Best,</font></div><div><font face="sans-serif"><br></font></div><div><font face="sans-serif">Arle</font></div></div></blockquote></div><br></div></div></div><meta http-equiv="x-dns-prefetch-control" content="on"><br><br> </div> </div> </div></body></html> >>> --1234169369-1608882830-1358257175=:95958-- >>> >>> >> > > >
Received on Monday, 21 January 2013 09:35:19 UTC