- From: Yves Savourel <ysavourel@enlaso.com>
- Date: Tue, 9 Jul 2013 23:04:00 +0200
- To: "'Dave Lewis'" <dave.lewis@cs.tcd.ie>
- CC: "'Felix Sasaki'" <fsasaki@w3.org>, "'Phil Ritchie'" <philr@vistatec.ie>, <public-i18n-its-ig@w3.org>, <kevin@spartanconsultinginc.com>, <chase@spartanconsultinginc.com>
> 1) Do you think we need a quick intro to each > data category just introducing its role in an XLIFF setting? Sure. I've tried to use the same short description from the specification at the very top of each section, and add the link. But we could expand on this. > 2) Several data categories may be used in several > places in an XLIFF file. Would it be helpful to have some > way of checking correct use of ITS in a XLIFF file against > these best practices, e.g. a merged schema? That would be nice. > 3) Should we provide best practice on where ITs > elements and attributes, e.g. the stand-off element > for proveneance and LQI, should go in the XLIFF structure Isn't it what we already do? (except that we haven't described any entry with standoff yet) > 4) Should it have a TOC to aid navigation? Would be nice. But it should be limited to two levels probably, otherwise it'll be just too long. Not sure how you can do this. > 5) In the section about ITs rules at the end, > should we add some explicit text about the role of these > rules and (not) using its rules otherwise in xliff > (also - I corrected the name of targetPointerRule rule in the example.) Yes. -ys
Received on Tuesday, 9 July 2013 21:04:33 UTC