IRC log from today's meeting

Hi All,
Unfortunately i failed to make sure the RSS engine was running correctly 
from today's call so i could geenrate the minutes yet, so below I've 
just attached the IRC log.

(Felix, do you have some magic script that will turn that into minutes - 
we decided to run it as #mlw-lt since there were WG topics to cover)

Quick summary:

ITS Spec updates:
------------------------
any objections called on felix's proposals for minor spec updates:
http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jul/0021.html
and an approach to the 'script' issue (leaving it as is and working on 
more ideal solution in IG)
http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jul/0014.html
but none were forthcoming.

So we agreed to start an issue to work on a 'win-win' solution for 
script in IG.

mtConfidence comment by Yves;
----------------------------------------------

http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jul/0022.html

  Agreed in general that we had an incomplete understanding on the call 
of whether external confidence scores were a use case and how they 
related to quality estimation and how that in turn related to the 
conformance LQI type. Ankit summarized that confidence score were 
generated in reference to existing translations, while quality 
estimation did not use such reference translations. Dave to seek further 
input from some of the MT and QE experts in CNGL and report back.

LQI-MQM mapping:
----------------------------
After call last week and subsequent discussion, GALA-CRISP agreed it 
would be best to advance this in W3C, with the ITS WG or a community 
group. for now, especially while the mapping is on the table the IG 
seems the natural place. Arle will set up IG product for this and drive 
discussion on list and calls.

inline LQR in XLIFF mapping
---------------------------------------
  Phil confirmed this would be needed for voting uses of LQR, so dave to 
fix.

IG tracker
-------------
Dave summarised the gradual movement of WG issues/actions (apart from 
ITS spec and test suite) to IG. These should be linked to concrete 
products with people driving them forward, and should be more fine 
grained and specific than 'various best practice' as used in WG. IG 
should avoid discussions, issues, actions that are not tied to a 
concrete product to maintain focus and timely completion.

cheers,
Dave