[All] Update AGENDA MLW-LT 2012-08-30

Changes:

- update of action items

- added topic "call time"



See your time at



http://www.timeanddate.com/worldclock/fixedtime.html?iso=20120830T14



DIAL-IN INFORMATION



1. Please join my meeting.



https://global.gotomeeting.com/join/682416317



2. Use your microphone and speakers (VoIP) - a headset is recommended.
Or, call in using your telephone.



Spain: +34 911 23 4170



France: +33 (0) 182 880 932



Germany: +49 (0) 811 8899 6930



Ireland: +353 (0) 19 036 185



United States: +1 (626) 521-0015



Access Code: 682-416-317



Audio PIN: Shown after joining the meeting



Meeting ID: 682-416-317



ACTIONS (3 min)

I closed action-34, Seattle event, for David.

action-162: Pedro, do you have something for us to look at already?. No
update today, Pedro will discuss this next week.

action-164. RDF Ontology: who is going to create and maintain the ontology?
Maxime?

action-179 Work with Olaf-Michael to help draft blurb for international
organizations. Is this moving forward or should we drop it?

action-196 inheritance in the spec done, see
http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2012Aug/0311.html


PRAGUE + TPAC (2 min)

Can you please indicate your attendance for Prague at

http://www.w3.org/International/multilingualweb/lt/wiki/PragueSep2012#Participants

and for TPAC at

https://www.w3.org/2002/09/wbs/35125/TPAC2012/?login

Attendance for LT-Web partners is required in both meetings; for TPAC,
please attend at least 1-2 November. Participation in the technical plenary
day 31 October is highly recommended for networking beyond MLW-LT :)



ISSUES

ISSUE-22 Provenance (5 min). Goal: get an update from Dave: when will a new
draft will be available? What issues need to be resolved? Who is
implementing?

ISSUE-33 Test suite design (10 min). Goal: get feedback on
http://phaedrus.scss.tcd.ie/its2.0/its-testsuite.html
questions:
- is the output format feasible for implementors?
- the output format doesn't "do" anything with the data, e.g. translation,
term processing, provenance processing etc. Is that enough?
- who can contribute more detailed test cases?
Update from Dave on ACTION-139 and ACTION-145.
Action-180 (add HTML5 examples to the spec): I would like to resolve this
by  linking to the HTML5 test suite examples. This doesn't work yet since
the table at
http://phaedrus.scss.tcd.ie/its2.0/its-testsuite.html
doesn't have ID attributes, but Leroy is going to add these.

 ISSUE-34 quality data category (5 min)
See spec text
http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20.html#lqissue
http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20.html#lqprecis
Goal: discuss open issues + find a reviewer who is *not* an expert in the
quality area.
action-168: Arle, any update on contacts to checkmate etc.?
FYI, I closed action-192 "freeze the number of information items in
quality".

ISSUE-36 special requirements (5 min)
See discussion on regex, latest mail at
http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2012Aug/0309.html
Goal: decide whether we can move forward with "forbidden characters". find
a volunteer to edit / create spec text for "storage size". Assure
implementation commitments.

ISSUE-41 mtConfidence (5 min)
Goal: find out whether David can move forward with Felix input on ISSUE-42
http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2012Aug/0304.html
Assure implementation commitments.

ISSUE-44 editorial notes (2 min)
https://www.w3.org/International/multilingualweb/lt/track/issues/44
Goal: find a volunteer to work on these.

ISSUE-45 (3 min). HTML5 API for ITS. Probably not needed, but let's discuss
the idea of an ITS JS library.

SPEC REVIEW
Related Action-186 (make HTML5 draft more reader friendly). I would like to
drop action-186 and have this done by reviewers (see below).

TIME LINE UNTIL PRAGUE
- Data categories that still need quite some work
See also
http://www.w3.org/International/multilingualweb/lt/wiki/Implementation_Commitments#Data_categories_2
Disambiguation, provenance, quality issue, quality precise,
textanalysisannotation, forbiddencharacters, storagesize, mtConfidence
Have I missed something

- Work on general quality of the draft. I have asked Dave, David, Aaron and
Moritz to review the draft in general. That should give us plenty of
feedback to work on.
During the call, I would like to find volunteers to review data categories
they have not worked on. Goal of this slot: create a lot of action items.

*Important*: Now it is getting more important to check the quality of the
draft than discussing details of unstable data categories. We will try to
do all of the above data categories; but if time doesn't allow it, we will
give precedence to the quality of the draft.

TIME LINE BETWEEN PRAGUE AND LYON (TPAC)

- Work on ITS in HTML5 issue. Bottom line: we cannot expect a free ticket
from the HTML WG for all data categories as is. There might be a detailed
review of our spec coming up. This closes my action-199.

CALL TIME
The current time doesn't work for everybody - let's discuss this briefly.

Best,

Felix Sasaki
DFKI / W3C Fellow