14:52:08 <RRSAgent> RRSAgent has joined #i18nits
14:52:08 <RRSAgent> logging to http://www.w3.org/2015/05/18-i18nits-irc
14:52:12 <fsasaki> meeting: ITS IG
14:52:14 <fsasaki> chair: felix
14:52:27 <fsasaki> agenda: https://lists.w3.org/Archives/Public/public-i18n-its-ig/2015May/
14:53:12 <fsasaki> regrets: christian, Phil, David
14:53:24 <fsasaki> topic: roll call
14:53:30 <RRSAgent> I have made the request to generate http://www.w3.org/2015/05/18-i18nits-minutes.html fsasaki
14:53:34 <fsasaki> present+ felix
15:01:12 <dF> dF has joined #i18nits
15:01:27 <dF> my  other meeting got cancelled
15:01:39 <dF> will connect to audio shortly
15:03:50 <Yves_> Yves_ has joined #i18nits
15:05:39 <fsasaki> https://lists.w3.org/Archives/Public/public-i18n-its-ig/2015May/0005.html
15:05:47 <fsasaki> topic: Action items
15:06:16 <fsasaki> action-30?
15:06:16 <trackbot> action-30 -- David Lewis to work on json-ld mapping of its2 -- due 2014-05-30 -- OPEN
15:06:16 <trackbot> http://www.w3.org/International/its/ig/track/actions/30
15:07:10 <Yves_> present+ yves
15:07:17 <fsasaki> topic: XLIFF mapping
15:08:00 <fsasaki> david: there is development on storage size data category
15:08:16 <fsasaki> ... fredrik deveploed a solution on that, should appear shortly in developers draft
15:08:23 <fsasaki> ... other from that situation did not change
15:08:53 <fsasaki> ... summary: there is good text analytics and terminology description in the editors draft
15:09:20 <fsasaki> ... MT confidendence and provenance are still missing from the high priority data categories
15:09:51 <fsasaki> ... to move this forward we need some discussion
15:10:53 <fsasaki> ... we would need a mockup / strawman how provenance would work for june f2f
15:11:03 <fsasaki> ... also for MT confidence
15:11:12 <fsasaki> ... would be good to discuss these to during the f2f
15:11:43 <fsasaki> felix: could I contribute s.t.?
15:12:00 <fsasaki> david: sure - I took the mappings that Yves created in the wiki, then take the behaviour of the attributes
15:12:11 <fsasaki> .. explain the same constraints as constraints of a custom mapping
15:12:19 <fsasaki> .. that is defined as part of ITS module
15:12:28 <fsasaki> ... there is an annotation mechanism in XLIFF
15:12:51 <fsasaki> ... various elements on structural or inline level
15:13:12 <fsasaki> ... that gives control about how the annotations should work
15:13:46 <fsasaki> ... currently sorush working on advanced validation
15:14:54 <fsasaki> ... direct editing in XML source code in oasis is OK
15:15:49 <fsasaki> felix: would be ok to create MT confidence and provenance section
15:15:52 <fsasaki> david: sure
15:17:12 <fsasaki> ... you could also contribute to schematron validation
15:18:48 <fsasaki> topic: ITS in JSON
15:18:51 <Yves_> https://www.w3.org/International/its/wiki/JSON%2BITS
15:19:33 <fsasaki> yves: very basic right now
15:19:45 <fsasaki> ... david had a good point - selection mechanism is defined as json path
15:19:56 <fsasaki> ... could also use other mechnaisms like json select
15:20:10 <fsasaki> ... you could define which selector mechnaism you are using
15:23:27 <fsasaki> serge: very nice demo!
15:23:37 <fsasaki> .. is there a way to look at the IoT demo?
15:23:57 <fsasaki> felix: once we slides of the IoT demo are done I will send them around
15:24:37 <fsasaki> http://www.locworld.com/sessions/the-internet-of-things/
15:27:15 <dF> Yves will also present ITS for json at FEISGILTT http://www.locworld.com/feisgiltt-program/
15:28:26 <fsasaki> discussion on IoT and localisation
15:29:05 <fsasaki> https://sgladkoff.wordpress.com/2015/05/16/riga-summit-personal-report/
15:29:15 <fsasaki> (Riga summit summary from Serge)
15:29:38 <fsasaki> serge: presentation about communication between machines - that can be connected to IoT I think
15:30:28 <fsasaki> "Dr.Robert Dale from ARRIA."
15:31:12 <fsasaki> felix: is there need for ITS locally, e.g. inside a json string?
15:31:26 <fsasaki> yves: yes, in our demo, you have data that you can get dynamically
15:31:44 <fsasaki> ... you would need to add a flag then if things are translatable
15:31:53 <fsasaki> ... local stuff could be done via global rules as well
15:32:00 <fsasaki> ... to trigger specific conditions
15:32:23 <fsasaki> ... so you don't need an ITS specific mechanism, but a flag that the global rules can use
15:32:40 <fsasaki> felix: so like ITS mapping for XML vocabularies?
15:32:44 <fsasaki> yves: corrrect
15:32:55 <fsasaki> ... and you can also have external rules, json is very flexible
15:33:11 <fsasaki> https://groups.google.com/forum/#!forum/json-schema
15:33:47 <fsasaki> felix: what is the best forum to get feedback from json community?
15:34:10 <fsasaki> yves: most developers don't care - if they need it they go to github and use the code ,and things become the defacto standard
15:34:48 <fsasaki> felix: good point - so just move implemnetation forward and try to get some uptake & feedback
15:35:19 <fsasaki> topic: taus TML proposal
15:35:22 <fsasaki> https://lists.w3.org/Archives/Public/public-i18n-its-ig/2015Apr/0004.html
15:36:13 <fsasaki> felix: should we follow up on that?
15:36:23 <fsasaki> .. or just leave things "as is"?
15:36:57 <fsasaki> serge: have discussion in TAUS website is good PR for us. I was busy could not follow up yet
15:37:40 <fsasaki> ... I'll follow up on this
15:38:07 <fsasaki> ... there was a good technical discussion, there is a good argument why ITS makes sense
15:39:31 <fsasaki> felix: CEF community working on language resource collection - should we involve them too?
15:39:44 <fsasaki> serge: metadata for LR at the moment is not an issue, but quality
15:40:25 <fsasaki> ... question is how to evaluate things - not clear how to introduce ITS on legacy resources
15:40:35 <fsasaki> ... e.g.. automatic mapping to standard ITS
15:40:45 <fsasaki> ... if you go forward sure, then ITS adding has value
15:41:43 <fsasaki> felix: agree, and TM or parallel corpora were not in focus for ITS so far
15:42:08 <fsasaki> topic: XLIFF f2f meeting in Berlin 1 July
15:42:33 <fsasaki> felix: any other topics we should prepare for f2f meeting?
15:42:50 <fsasaki> .. in addition to provenance and mt confidence?
15:43:00 <fsasaki> david: review the data categories that are done in the spec
15:44:02 <fsasaki> discussion on XLIFF mapping action items
15:44:37 <fsasaki> david: if you send input this week we can word smith during f2f
15:44:38 <fsasaki> yves: ok
15:45:04 <RRSAgent> I have made the request to generate http://www.w3.org/2015/05/18-i18nits-minutes.html fsasaki
15:45:25 <fsasaki> present+ davidF, serge
15:45:26 <RRSAgent> I have made the request to generate http://www.w3.org/2015/05/18-i18nits-minutes.html fsasaki
15:45:46 <fsasaki> david: will identify gaps and will look for volunteers to close them
15:46:28 <fsasaki> ... could have a small task force for schematron rules
15:46:44 <fsasaki> s/force/force in the XLIFF TC/
15:46:47 <RRSAgent> I have made the request to generate http://www.w3.org/2015/05/18-i18nits-minutes.html fsasaki
15:47:46 <fsasaki> david: looking into other serializations of XLIFF during wednesday
15:49:35 <fsasaki> http://de.slideshare.net/m1ci/nif-tutorial/10
15:51:35 <fsasaki> felix: may be a syngery to the RDF - NIF representation, see NIF link above
15:51:55 <fsasaki> serge: would be nice to explain how this is being done, with RDF applications
15:52:26 <fsasaki> felix: FREME started some related implemtnation, has not gone public yet, hopefully soon
15:53:23 <fsasaki> topic: usual topics & AOB
15:55:22 <fsasaki> david: send a doodle to the whole list for the call?
15:55:28 <fsasaki> .. re-create awareness of the time
15:56:00 <fsasaki> felix: doodle for call time, sure, I'll send one out
15:57:02 <fsasaki> david: we need more working sessions - currently call is more status checking
15:58:56 <fsasaki> adjourned
15:59:03 <RRSAgent> I have made the request to generate http://www.w3.org/2015/05/18-i18nits-minutes.html fsasaki
16:16:23 <camille> camille has joined #i18nits