14:50:25 RRSAgent has joined #mlw-lt 14:50:25 logging to http://www.w3.org/2013/01/16-mlw-lt-irc 14:50:32 meeting: MLW-LT WG 14:50:34 chair: felix 14:50:51 agenda: http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jan/0090.html 14:51:01 topic: roll call 14:51:06 tbd ... 14:52:52 Zakim has joined #mlw-lt 14:53:39 present+ felix 14:53:45 present+ karl 14:54:18 present+ Marcis 14:55:20 philr has joined #mlw-lt 14:55:21 leroy has joined #mlw-lt 14:55:26 present +philr 14:55:52 daveL has joined #mlw-lt 14:56:01 regrets+ dom 14:57:44 Ankit has joined #mlw-lt 14:58:20 present+ leroy 14:58:23 present +Ankit 14:58:45 joerg has joined #mlw-lt 14:59:00 present+ shaunm 14:59:37 present+ joerg 14:59:50 mdelolmo has joined #mlw-lt 14:59:57 renatb has joined #mlw-lt 15:00:15 Clemens has joined #mlw-lt 15:00:41 I have made the request to generate http://www.w3.org/2013/01/16-mlw-lt-minutes.html fsasaki 15:00:57 Jirka has joined #mlw-lt 15:00:58 present + Clemens 15:01:03 Des has joined #mlw-lt 15:01:04 present +Jirka 15:01:12 present +Clemens 15:01:23 present+ dave 15:01:26 present +Des 15:01:52 present+ mdelolmo 15:02:00 I have made the request to generate http://www.w3.org/2013/01/16-mlw-lt-minutes.html fsasaki 15:02:04 present+ renatb 15:02:45 Arle has joined #mlw-lt 15:02:51 pnietoca has joined #mlw-lt 15:03:14 scribe: daveL 15:03:36 http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jan/0090.html 15:03:50 topic: Meeting time 15:03:56 Can someone post the Germany dial in info? 15:04:02 http://www.doodle.com/pn6xa86rfbypmd2k 15:04:31 +49 (0) 811 8899 6930 15:04:52 tadej has joined #mlw-lt 15:04:54 omstefanov has joined #mlw-lt 15:05:16 And the meeting number? 15:05:17 Yves_ has joined #mlw-lt 15:05:17 Marcis_ has joined #mlw-lt 15:05:27 +present pnietoca 15:05:29 present+ Yves 15:05:44 present+ guiseppe 15:05:53 can someone please post the gotomeeting link, I lost it 15:06:05 +present omstefanov 15:06:10 https://global.gotomeeting.com/join/682416317 15:06:14 +present tadej 15:07:31 thanks 15:07:49 felix; there is no apparent slot that works. felix willl distribute a weekly alternating proposal 15:08:01 topic: state of XLIFF mapping 15:08:36 scribe: fsasaki 15:08:46 dave: haven't updated the mapping page a lot 15:09:05 .. there is more work to be done to formalize the mapping 15:09:11 .. and come up with examples 15:09:24 .. I think we won't to focus on XLIFF 1.2 mapping first 15:09:39 .. we were hoping that XLIFF 2 would be stable, but there is a dely 15:09:44 s/dely/delay/ 15:10:01 dave: focus on XLIFF 1.2 also helps with putting a demonstrator together 15:10:08 yves: dave summarized everythign right 15:10:19 .. in okapi we implemented ITS mapping on what we have 15:10:26 .. it is partially implemented, ongoing 15:10:36 dave: we will come back shortly on that 15:10:39 Pedro has joined #mlw-lt 15:10:56 .. wrt to interop between solas and CMS lion, also using okapi 15:11:03 .. with the preparation for rome 15:11:22 phil: it is now on our critical path for our implementation 15:11:32 .. david said he would have a prototype a few weeks ago 15:11:39 .. even if there is nothing final 15:11:47 .. even if we would have a rough direction 15:12:00 .. e.g. yves said that with xliff 1.2, he would use mrk markup 15:12:18 .. even if we had directions what is easily acceptable 15:12:26 .. otherwise it could hold up my implemetnation 15:12:38 yves: the xliff 1.2 mapping is what we used for implementations 15:12:45 .. most of the time it made sense 15:13:02 .. we have tackled some of the standoff stuff 15:13:10 giuseppe has joined #mlw-lt 15:13:10 Naoto has joined #mlw-lt 15:13:15 .. it is also in the git repository (for okapi, scribe assumes)? 15:13:26 yes 15:13:55 phil: provenance and loc quality issue, rating are relevant for us here 15:13:56 Location: http://code.google.com/p/okapi/source/list?name=html5 15:14:40 phil: Yves' page for 1.2. we can certainly use that as our direction 15:14:50 dave: will talk to david tomorrow about that 15:14:53 phil: tx 15:15:15 topic: New value for localization quality type "conformance" 15:15:19 scribe: daveL 15:15:45 felix: asks if anyone has further thoughts, or supported for this new type 15:15:52 topic: Regular expression change 15:15:56 ... no respeonses yet 15:16:39 shaun: no update on this 15:17:07 action: shaunm to work on regex for validating regex subset proposal 15:17:07 Error finding 'shaunm'. You can review and register nicknames at . 15:17:39 action: shaun to work on regex for validating regex subset proposal 15:17:39 Created ACTION-385 - Work on regex for validating regex subset proposal [on Shaun McCance - due 2013-01-23]. 15:17:54 topic: Disambiguation and term 15:18:34 topic: disambiguation and term 15:18:55 felix: has been discussed in response to christian comment 15:19:05 ... any further comments 15:19:21 marcis: what is the goal? 15:19:47 felix: christian suggested merging term and disambig data categories 15:20:23 ... but response was that both had distinct use cases, that could merge by are valid individually 15:20:58 marcis: would not want to drop data category, term is easier to implement and purpose is clear 15:21:25 ... not so clear on disambiguation category, in terms of what is possible to do with this 15:21:44 Milan has joined #mlw-lt 15:22:05 ... for example there may be other types that might be useful in the disambiguation use case 15:22:17 I have made the request to generate http://www.w3.org/2013/01/16-mlw-lt-minutes.html fsasaki 15:22:42 ... and doing term management with disambig would make it very heavy 15:23:02 present+ milan, tadej 15:23:03 I have made the request to generate http://www.w3.org/2013/01/16-mlw-lt-minutes.html fsasaki 15:23:35 marcis: so there might need to be more atribute specifically for named entity 15:23:46 ... referencing input form W3C india recvied today 15:24:39 tadej: motivation for separate data category was because it covered some use cases that fell out of the scope of terminology 15:25:07 ... by providing some additional context 15:25:23 ... but do see that there is some commonality 15:25:56 ... Also term must remain to keep compatibility with named entity 1 15:26:26 correction, > with terminology in ITS1 15:26:57 jorge: still in favour of having the two data categories 15:27:28 ... since dismabiguation can cover many other tasks in content or NLP processing 15:27:40 ... whereas term is more specific 15:28:32 s/jorge/jörg/ 15:28:37 pedro: the sort of text we mark up is different in both cases so it makes sense to keep the distinction 15:30:45 tadej; agree granularities are quite limiting, or should we have more identifiers to support this 15:30:56 ... but this might be more comlicating 15:31:19 jorge: yes this would be more complicated, clearer as it is 15:31:28 http://tinyurl.com/its20-testsuite-dashboard 15:31:54 felix: christian will dial in to f2f to discuss this and resolve the topic next week 15:32:52 ... we also need to consider number of implementations, which are not so many, when considering any possible merger 15:33:18 Dec: agree with jorge, keep them separate as they are distinct use cases 15:33:38 s/Dec:/Des:/ 15:33:58 jorge: clarified, attributes as defined currently are clearer than making them more fine grained 15:36:11 felix:reminds that W3C process requires responding which involves some work 15:36:50 could we talk about annotorsRef https://www.w3.org/International/multilingualweb/lt/track/issues/71 a bit during this call? 15:37:02 felix: the current level of commetn is good currently 15:37:05 topic: annotorsRef 15:38:29 yves; for two data categories, proc and locqualiss, can have information from multiple annotators, but we have no way of doing this for annotatorRef 15:38:40 s/yves;/yves: 15:39:32 ... for current implementation, we assume the most recent annotator is the correct one, but this is not ideal 15:40:16 ... provenance especially has multiple items and requires annotationRef 15:40:28 daveL: will onto this 15:40:42 scribe: daveL 15:41:30 phil: lets talk about the ordering of proveance 15:41:33 provenance data category https://www.w3.org/International/multilingualweb/lt/track/issues/72 15:41:55 Arle_ has joined #mlw-lt 15:42:02 zakim, Arle_ is Arle 15:42:02 sorry, Arle_, I do not recognize a party named 'Arle_' 15:42:59 http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jan/0090.html 15:43:02 I am back on the call. 15:43:11 http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jan/0061.html 15:43:15 http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jan/0066.html 15:43:17 felix: this was a discussion of whether there was any implication between ordering and time of record 15:43:21 http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jan/0055.html 15:43:35 (mails related to the discussion) 15:43:43 topic: provenance record ordering 15:43:53 phil: asks whether there should be a lack of date stamp 15:44:11 daveL: a date stamp was discussed 15:44:17 .. there is two aspects: 15:44:34 .. a lot of original requirements didn't have a strong need for a time stamp 15:45:00 .. the original requirement was about identifying rich enough so that we can differentiate 15:45:13 .. see e.g. "agent provenance" that used to include taht 15:45:26 .. the 2nd aspect: 15:45:46 .. we discussed whether the order of the proveancen records are added is significant 15:46:00 .. but from an implementation point of view it is again compliciated 15:46:16 .. and there hadn't be much a call for this during requirements gathering 15:46:36 .. "time" also has various aspects: start of a translation, finish, duration, ... 15:46:52 .. it is also a point that the provenance wg in w3c had addressed 15:47:10 .. so we just provide identifiers of who made the translation and revision 15:47:13 dF has joined #mlw-lt 15:47:35 .. for knowing more there is a the provenance model 15:47:41 .. more = more about time 15:48:11 .. so in summary, there was no big requirement to have a time stamp 15:48:22 .. and *if* you want to do that, you can use the w3c prov model 15:48:30 .. I'll reply to that mail thread 15:48:49 pablo: I think provenance can stay as is 15:49:14 .. adding a time stamp can be useful and interesint - if every implementer is fine with that i'm fine too 15:49:51 scribe: daveL 15:50:20 felix: adding tiestamp is a substantive change and would require another call, plus tests etc 15:51:35 topic: Test suite 15:51:43 http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jan/0090.html 15:52:27 felix: from this week on be aware that people should stop using the google docs and they update the test suite master themselves 15:52:40 http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2012Dec/0087.html 15:53:04 ... we need still some input on tests still related to assertion (MUSTs0 which need suggestion for test for them 15:53:27 topic: prague f2f 15:53:30 http://www.w3.org/International/multilingualweb/lt/wiki/PragueJan2013f2f 15:53:39 http://www.w3.org/International/multilingualweb/lt/wiki/PragueJan2013f2f#Objectives 15:53:54 felix: thanks to jirka for organising this 15:54:00 http://www.w3.org/International/multilingualweb/lt/wiki/PragueJan2013f2f#Participants 15:54:24 jirka: is you are not yet register, please do so numbers are known for wifi etc. 15:54:29 present+ dF 15:55:08 felix: also need to know in advance when people want to dial in for organising the agenda 15:55:12 http://www.w3.org/International/multilingualweb/lt/wiki/PragueJan2013f2f#Objectives 15:56:52 felix: go through objectives 15:57:43 http://www.w3.org/International/multilingualweb/lt/wiki/Use_cases_-_high_level_summary 15:58:15 ... in particular the relationship between the different posters and links to where people can access them and update high level summary, adding any new use cases 15:58:25 present+ Naoto 15:58:58 daveL: some time to discuss preparing EU project review? 15:59:09 ... also brainstorm on activities for rest of year and new projects and synergy between them 15:59:42 felix: the Rome preparation should cover that. 16:00:20 scribe: fsasaki 16:00:21 as I will not be able to take part in the f2f Prague, but definitely intend to come to Rome, so please make sure preps for Rome are recording in writing 16:00:41 topic: xliff mapping implementation update 16:01:06 david: phil asked on that, we got good comments from xyz 16:01:22 .. status of xliff mapping - only written piece is xliff mapping wiki 16:01:23 http://www.w3.org/International/multilingualweb/lt/wiki/XLIFF_Mapping 16:02:02 david: will work on this today, yesterday / today was EC deadline 16:02:28 .. we should publish this as a note / PC 16:02:40 .. what is the editorial setup for such a note? 16:03:11 .. we will need an additional namespace itsx 16:03:40 felix: update on implementation prototype? 16:03:53 david: solas is consuming ITS2 categories 16:03:57 .. like OKAPI does 16:04:11 .. that is being tested as part of the test suite 16:04:27 .. that is consumed by various components of solas architecture 16:04:34 .. one is an MT broker 16:04:46 .. works with different MT systems 16:05:16 .. depends on the MT systems whether they can deal with ITS metadata 16:05:27 .. moravia is contributing to that 16:05:37 .. m4loc can be used as middleware 16:05:58 .. in our current prototype the mt services exposes the m4loc service 16:06:14 .. from the deliverable - open source xliff roundtripp 16:06:23 .. the okapi filter interprets the ITS decoration 16:06:39 .. then the mapping in the wiki is used 16:06:56 .. it is consumed by middle ware open source component 16:07:50 felix: would be good to see a demo 16:08:18 david: will do, in prague and in rome 16:09:23 topic: metadata harvesting 16:09:37 ankit: we are waiting for some sort of data from cocomore 16:09:53 felix: what data? 16:10:13 ankit: we said that cocomore would provide us with annotated data 16:12:26 ankit will provide module by prague f2f 16:13:14 pedro: will have annotated data from spanish client 16:13:48 pedro: client is the spanish gov tax office 16:13:58 .. they will annotate with ITS metadata for this show case 16:14:05 .. spanish content in HTML5 16:14:12 .. we will generate english content 16:14:21 .. and annotate it in the output of the real time system 16:14:49 felix: so ankit could later use the data to test the module? 16:15:07 ankit: training data is as much as you can get 16:15:26 pedro: annotated data from cocomore is html content 16:15:35 .. we will generate content in chinese and french 16:16:08 .. so ankit can take that into account chinese, french, german in his system 16:16:14 .. and spanish 16:16:35 ankit: this will be german to english, german to french, german to chinese, german to spanish 16:16:59 s/ankit:/pedro:/ 16:17:21 Showcase WP3 (Cocomore-Linguaserve) is German to Chinese and German to French 16:17:43 right! 16:18:10 Showcase WP4 (Linguaserve-Lucy-DCU) is the full demo Spanish to English, and partial demo Spanish to French and Spanish to German 16:19:01 Jirka has left #mlw-lt 16:19:29 dF has left #mlw-lt 16:19:32 thanks for everybody for staying longer, meeting adjourned 16:19:38 I have made the request to generate http://www.w3.org/2013/01/16-mlw-lt-minutes.html fsasaki 16:20:41 mdelolmo has left #mlw-lt 16:38:23 present+ olaf 16:38:30 I have made the request to generate http://www.w3.org/2013/01/16-mlw-lt-minutes.html fsasaki 17:55:20 Zakim has left #mlw-lt