W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > October 2012

[Agenda] MLW-LT call 8 October, 3 p.m. UTC

From: Felix Sasaki <fsasaki@w3.org>
Date: Thu, 4 Oct 2012 17:42:33 +0200
Message-ID: <CAL58czrH6R13f2NCsURjgVv3=5E4-dp0T5xncYnrftsfaa9KJg@mail.gmail.com>
To: public-multilingualweb-lt@w3.org
Hi all,

Below is an agenda draft for Monday. NOTE: it contains a proposal for a
time schedule what to do in October, that is, before the next publication
and TPAC. The co-editors need time to implement “your” material, so please
let us know whether you can make the deadlines.

Time: 8 October, 3 p.m. UTC. See



Dial-in details:

1) Work schedule

Below is boring, but we need to do it: get a realistic overview of what to
do in “conference and work prime time” October.

1.1) PUBLICATION DATE: I propose week of 22 October. The week after is
TPAC, and there won’t be publications in that week. See


This means that the last edits need to be done by 19. October.

1.2) Data categories provenance, disambiguation and text analytics need
(new) drafts. Phil, Tadej, can you provide these this week (by 5 October =
tomorrow), so that the co-editors can put the material into the draft next
week? See the related action items in tracker.

1.3) Separation of HTML and XML in the draft. Jirka has a related action
https://www.w3.org/International/multilingualweb/lt/track/actions/220 . He
also had mentioned to remove the “productions”, e.g.

[12] att.local.no-ns.attribute.translate ::= attribute translate { "yes" |
"no" }?

>From the spec. That would make it really much shorter and readably.

1.4) Update of ITS schema. Jirka is working on this as well. Given the
workload of this, the other co-editors should take over other editing

1.5) Localization workflow manager
https://www.w3.org/International/multilingualweb/lt/track/actions/222 .
David, can you provide the text this week?

1.6) NIF section and test cases: this one is for me.

1.7) Various:

- Canonical data category names

- Editorial notes


My hope is that during the Monday call we can distribute above work to get
it done next two weeks, so that the editors have another buffer week to
implement this in the spec.


Line break


This was resolved last week. Co-editor colleagues, can somebody implement
the resolution in the spec?

Too many pointers / global rules


Would this


be a resolution? If yes, the co-editors would implement that after the call.



No need to keep this open for the moment – it won’t influence the spec, so
closing it for now

Domain in HTML5


I’ll send an update about this soon.

Tool information


With new input from terminology data category, see


3) Editing call

After or – if we adjourn early – starting during the call. Goal: to
distribute editing work for the next two weeks in a realistic schedule.
Arle has a related action item


And we will update


during the call.

4) AOB



Felix Sasaki
DFKI / W3C Fellow
Received on Thursday, 4 October 2012 15:43:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:31:55 UTC