11:55:38 RRSAgent has joined #i18nits 11:55:38 logging to http://www.w3.org/2014/05/14-i18nits-irc 11:55:44 meeting: its IG 11:55:46 chair: felix 11:55:58 agenda: http://lists.w3.org/Archives/Public/public-i18n-its-ig/2014May/0003.html 11:56:03 regrets: christian 11:56:10 topic: roll call 11:56:16 checking attendees ... 11:56:20 I have made the request to generate http://www.w3.org/2014/05/14-i18nits-minutes.html fsasaki 11:59:32 I have made the request to generate http://www.w3.org/2014/05/14-i18nits-minutes.html fsasaki 12:00:01 fsasaki has joined #i18nits 12:00:49 Yves_ has joined #i18nits 12:02:54 present: yves, dave, renat, felix 12:03:01 I have made the request to generate http://www.w3.org/2014/05/14-i18nits-minutes.html fsasaki 12:03:08 renatb has joined #i18nits 12:03:30 daveL has joined #i18nits 12:03:38 present+ DaveLewis 12:03:48 present+ 12:04:15 dF has joined #i18nits 12:04:23 present+ dF 12:04:29 I have made the request to generate http://www.w3.org/2014/05/14-i18nits-minutes.html fsasaki 12:04:42 present- dave 12:04:43 I have made the request to generate http://www.w3.org/2014/05/14-i18nits-minutes.html fsasaki 12:05:24 http://lists.w3.org/Archives/Public/public-i18n-its-ig/2014May/0003.html 12:05:33 GaryLefman has joined #i18nits 12:05:36 topic: namespace bindings and CSS selectors 12:05:41 skip - jirka not here 12:05:50 topic: update on XLIFF mapping 12:06:06 david: volunteered to review 12:06:14 .. started doing some minor editorial changes today 12:06:19 .. not done yet 12:06:30 .. only typos to fix 12:06:55 .. only review, did not go through "todo" parts of the mapping 12:07:06 dave: what is the process of the mapping becoming a module in XLIFF 2? 12:07:15 .. do we need to support that with a test suite? 12:07:19 .. or s.t. like that? 12:07:32 david: would be good to have "in" and "out" files 12:07:39 .. yves has examples 12:07:49 .. how it looks in native format (usually HTML) 12:07:53 regrets+ ankit 12:08:02 david: would be more complex compared to other modules 12:08:12 .. in other modules you worry just about localisation roundtrip 12:08:24 .. but not about what the information was before extraction 12:08:43 .. the XLIFF spec has not a lot of instruction for extraction / merger 12:08:50 .. they expect that both have the some knowledge 12:08:57 .. the extraction is not really described 12:09:20 .. the extraction parts would be non normative 12:09:33 .. it is a new situation: some W3C work to be submitted to OASIS 12:09:44 .. a member like LRC submits this to OASIS 12:10:15 .. no need to have w3c membership, OASIS membership is sufficient 12:10:31 yves: for tests - would be possible to have input with ITS markers, output in XLIFF 12:11:14 .. process and have same kind of output like we had with ITS test suite 12:11:21 felix: makes sense 12:11:36 yves: so we need a set of rules and spell them out into a rule file 12:11:50 renat: could we use okapi framework for file conversion purposes? 12:11:52 yves: sure 12:12:03 renat: okapi could convert almost any format into XLIFF 12:12:04 yves: yes 12:12:18 renat: it could develop or extend existing converters to support ITS 12:12:26 david: Okapi is a reference implementation 12:12:36 I have made the request to generate http://www.w3.org/2014/05/14-i18nits-minutes.html fsasaki 12:12:58 david: having more than input + output files is probably not realistic 12:14:08 felix: Okapi provides low level parsing with ITS "events" but not "real" implementations for all data categories 12:14:32 david: we hope for other low level implementattions that should create the same results 12:14:45 .. we need a good selection of stakeholders in dublin 12:14:52 .. to get buy in of the people 12:15:33 felix: could provide xslt for test suite, but not for real processing 12:15:39 david: would be good for test suite 12:15:53 .. bryan should be able to work on something similar 12:16:22 felix: any requirements in terms of numbers of implementations? 12:16:29 david: we put test suite in our charter 12:16:38 .. but it is not even an OASIS requirement 12:16:57 .. it is a statement of use, it is up to the TC to decide what level of verification is needed 12:17:24 .. having input + output files is the minimum I think 12:17:58 felix: what is the timeline for the input + output files and how about the location? 12:18:06 david: we have SVN repository 12:18:16 .. oasis admin are OK with links to SVN 12:18:51 .. next tc call will be next week - we then should talk about new template for XLIFF 2.1 12:19:00 .. will have a different svn than XLIFF 2.0 12:19:32 .. about the time frame: this will be another session in feisgiltt 12:19:48 .. Kevin will propose an early release schedule - to be discussed next month 12:19:53 present+ phil 12:20:08 present+ garyLefman 12:20:24 david: implementations should be ready by November, file in place no later than september 12:20:48 philr has joined #i18nits 12:20:56 present+ philr 12:21:29 yves: the more comments we get on the mapping the better 12:21:37 .. the parts that map to modules, e.g. size and constraints 12:22:48 present- phil 12:22:52 I have made the request to generate http://www.w3.org/2014/05/14-i18nits-minutes.html fsasaki 12:23:52 [discussion about storage size in ITS2 and how it maps to XLIFF2] 12:24:23 david: yves, any other things you think need input except storage size? 12:24:37 yves: yes, the standoff things, e.g. provenance 12:24:43 .. also implementation feedback 12:26:16 fsasaki_ has joined #i18nits 12:26:42 I have made the request to generate http://www.w3.org/2014/05/14-i18nits-minutes.html fsasaki_ 12:27:10 david: conceptual aspect of "Translate" - what is it for? 12:27:24 .. yves has fallback solution: you can extract non translatable text into code 12:27:33 .. not sure about this: we are mixing up things 12:27:55 .. if s.t. is natural language not translatable for business reasons it should not go into codes 12:28:14 .. it should be marked up as translate=no or not go into the extracted content 12:28:21 I have made the request to generate http://www.w3.org/2014/05/14-i18nits-minutes.html fsasaki_ 12:28:32 dave: the ITS "Translate" does not say anything why we annotate it 12:29:00 .. in XLIFF it is complicated since the extraction process says s.t. about this as well 12:29:12 david: depends on the semantics of the underlying format 12:29:28 .. e.g. in some formats you have assumptions like: markup is not translatable 12:29:38 dave: for ITS I think it only applies to the textual content 12:29:51 .. would not apply to markup unless it is textual content of attribute 12:30:14 .. maybe ok to have code extraction fallback 12:31:01 felix: besides okapi who would implement the mapping? 12:31:34 yves: leroy I assume 12:31:43 david: bryan is esp. interested in the CMS scenario 12:32:06 .. he would be interested in that issue, esp. DITA based 12:32:52 I have made the request to generate http://www.w3.org/2014/05/14-i18nits-minutes.html fsasaki_ 12:33:18 dave: we are still using mapping for mapping to RDF 12:34:38 topic: update on RDF mapping 12:34:55 http://www.babelfy.org/ 12:36:35 dave: useful for advancing this may be: 12:36:44 .. for advancing ontology + test suite 12:36:52 .. we could do that in LIDER 12:37:00 .. that will help to motivate people 12:37:12 .. same for qLabel library 12:37:32 .. they only highlight 1-2 data categories 12:37:51 .. but some are good XML>RDF data categories 12:38:21 felix: no need to publish a note, we can also just point to the ontology and document it 12:38:46 topic: working with ITS in RDF 12:39:02 I have made the request to generate http://www.w3.org/2014/05/14-i18nits-minutes.html fsasaki 12:39:13 yves: you get a lot of data - how to make use of it is hard 12:39:18 dave: exactly 12:39:23 I have made the request to generate http://www.w3.org/2014/05/14-i18nits-minutes.html fsasaki 12:40:40 felix: working with various data sets - how is the impact? 12:40:57 yves: babelnet was mostly useful for the translators it seems 12:41:15 .. maybe that is the case with other data sets too - they use same linked data? 12:41:31 dave: there are some data set differences, or different data clean up processes 12:41:46 .. good to hear from people like yves: what is more useful? 12:41:58 I have made the request to generate http://www.w3.org/2014/05/14-i18nits-minutes.html fsasaki 12:42:14 dave: how to decide which one works well under which circumstances 12:43:24 dave: we are close to feisgiltt now - for yves a good opportunity to met linked data guys and talk to localisation people too 12:43:43 .. people don't want to be in too many groups, but if we track a specific issue it'd helped 12:45:11 topic: event report 12:46:51 felix reports on ITS metadata in json discussion held at the workshop 12:47:20 dave: there was a discussion at the end of the workshop - doing e.g. inline markup thing would be a horror in json 12:47:31 .. json-ld mapping from the ITS ontology could help 12:47:44 yves: did not try yet to put anything in json 12:47:54 .. not sure - this is really like a transport format 12:47:59 I have made the request to generate http://www.w3.org/2014/05/14-i18nits-minutes.html fsasaki 12:48:09 david: think it would have traction in industry 12:48:56 dave: there is two use cases: 12:49:03 .. one is internationalisation of apps that use json 12:49:22 .. the other one: use json like you use xliff, but talking to javascript browser cat tool 12:49:47 .. example: prototype cat tool having xliff+its working in the browser 12:50:05 .. from a web developers point of view, it would be more natural to have everything in json 12:50:38 felix: so having ITS > XLIFF mapping and then that represented as json? 12:50:49 dave: yes - and there is i18n requirements for apps that use json 12:50:58 david: yes, that is different use cases 12:51:12 I have made the request to generate http://www.w3.org/2014/05/14-i18nits-minutes.html fsasaki 12:53:15 felix: anything else to report about the workshop? 12:53:22 dave: three interesting groups of people: 12:53:27 .. the wikipedia translation group 12:53:47 [see slides now here http://www.w3.org/International/multilingualweb/2014-madrid/slides/sharma.pdf ] 12:54:01 [and here http://www.w3.org/International/multilingualweb/2014-madrid/slides/giner.pdf ] 12:54:16 dave: also interesting: publication office discussion 12:54:20 FEISGILTT links: home http://bit.ly/1c4RC5Y reg http://bit.ly/1lxmkvr Speakers: http://bit.ly/QnVdI0 Program: http://bit.ly/1lxn0kr 12:54:32 .. they will start publishing legal text 12:54:53 .. they are interesting in understanding good ways to leverage ITS > RDF mapping 12:54:57 I have made the request to generate http://www.w3.org/2014/05/14-i18nits-minutes.html fsasaki 12:55:28 dave: and then discussion how to get access to "deep web" data 12:56:38 felix: would hope that wikipedia would use ITS (without necessarily showing the markup to the author / editor) 12:56:57 dave: also libraries like qlabel help to show value of ITS 12:57:34 topic: AOB 12:57:39 adjourned 12:57:45 I have made the request to generate http://www.w3.org/2014/05/14-i18nits-minutes.html fsasaki 13:25:47 camill has joined #i18nits 13:43:30 camille has joined #i18nits