15:55:52 <RRSAgent> RRSAgent has joined #i18nits
15:55:52 <RRSAgent> logging to http://www.w3.org/2015/01/12-i18nits-irc
15:55:55 <fsasaki> meeting: ITS IG
15:55:57 <fsasaki> chair: felix
15:56:01 <fsasaki> scribe: fsasaki
15:56:12 <fsasaki> agenda: http://lists.w3.org/Archives/Public/public-i18n-its-ig/2015Jan/0001.html
15:56:19 <fsasaki> regrets: christian, david
15:58:17 <fsasaki> topic: roll call
15:58:24 <fsasaki> checking attendance ....
15:58:28 <fsasaki> present+ fsasaki
15:58:32 <RRSAgent> I have made the request to generate http://www.w3.org/2015/01/12-i18nits-minutes.html fsasaki
15:59:48 <YvesS> YvesS has joined #i18nits
16:00:44 <Serge> Serge has joined #i18nits
16:00:58 <YvesS> present+ Yves
16:01:37 <renatb> renatb has joined #i18nits
16:02:21 <renatb> present+ renatb
16:02:36 <Ankit> Ankit has joined #i18nits
16:02:42 <Ankit> present+ Ankit
16:03:08 <fsasaki> present+ serge
16:03:17 <fsasaki> http://lists.w3.org/Archives/Public/public-i18n-its-ig/2015Jan/0001.html
16:03:37 <fsasaki> topic: action items
16:03:37 <fsasaki> https://www.w3.org/International/its/ig/track/actions/open
16:04:29 <fsasaki> close action-54
16:04:29 <trackbot> Closed action-54.
16:04:56 <fsasaki> action-9?
16:04:56 <trackbot> action-9 -- David Lewis to Look at the XLIFF 2.0 change tracking module for provenance -- due 2014-05-30 -- OPEN
16:04:56 <trackbot> http://www.w3.org/International/its/ig/track/actions/9
16:05:23 <fsasaki> felix: will ping Dave about action-9
16:05:29 <fsasaki> present+ phil
16:05:56 <fsasaki> action-50?
16:05:56 <trackbot> action-50 -- Serge Gladkoff to Draft outreach mail for doc for others to re-use -- due 2014-07-23 -- OPEN
16:05:56 <trackbot> http://www.w3.org/International/its/ig/track/actions/50
16:06:40 <philr> philr has joined #i18nits
16:06:48 <philr> present+ philr
16:06:57 <fsasaki> close action-50
16:06:58 <trackbot> Closed action-50.
16:07:04 <fsasaki> serge: did the announcement on linkedin
16:07:57 <fsasaki> ... on linkedin groups many postings, but very few unfold into real discussions with many replies - linkedin changes the way the groups are working
16:08:16 <fsasaki> .. people got the announcement, volume of reaction is unclear
16:08:47 <fsasaki> .. if we want to do wider email outreach I can do that
16:08:55 <fsasaki> .. but it is important to get a more concrete message in
16:09:16 <fsasaki> .. in ITS I saw other topics like business value and benefits per data category
16:09:26 <fsasaki> .. I can do a broad outreach once this content is done
16:09:43 <fsasaki> .. it would be nice to ask s.t.  - email that does not require any reaction will not cause any
16:10:08 <fsasaki> .. so then "business value" content is done, we will do announcement via linkedin etc.
16:10:16 <fsasaki> .. also gala standards list
16:10:37 <fsasaki> .. but also need to see some request, e.g. what do we ask? feedback, request for further participation etc.
16:11:51 <fsasaki> serge: we know that new calls are about big data, we need to connect ITS to big data, and when it will be picked up more
16:13:28 <fsasaki> topic: big data networking day
16:13:28 <fsasaki> https://ec.europa.eu/digital-agenda/en/news/horizon-2020-ict-16-big-data-networking-day
16:14:01 <fsasaki> felix: will present "FREME" project
16:14:30 <fsasaki> .. that has some relation to ITS as well
16:15:09 <fsasaki> phil: we are partner in FREME project
16:15:19 <fsasaki> .. we are adding some additional facilities to ocelt
16:15:35 <fsasaki> .. that will allow us to consume FREME services output
16:15:44 <fsasaki> ... that includes terminology and entity annotation services
16:16:05 <fsasaki> ... as somebody is translating and reviewing, that will be extra facilities that will add add. value to translators services
16:16:24 <fsasaki> .. not all thing we add will be open source, but part of FREME, core things will be available
16:16:53 <fsasaki> .. so it is about adding to the business proposition of translation services - adding some things to translation that would not be part of the standards workflow
16:17:09 <fsasaki> .. adding some things that will be ITS2 or XLIFF2 etc. metadata
16:18:07 <fsasaki> felix: FREME will fudn work on ITS2 in XLIFF module
16:18:37 <fsasaki> yves: another topic taht could be related to ITS
16:18:45 <fsasaki> .. people are using more and more web services like JSON output
16:18:51 <fsasaki> topic: ITS and JSON
16:18:59 <fsasaki> yves: a lot of service output is carried by JSON
16:19:08 <fsasaki> .. had some discussion we coudl do in JSON to use ITS
16:19:32 <fsasaki> .. you easily can do something with JSONpath to mimic ITS rules, that could be an area of interest as well
16:19:36 <fsasaki> phil: could be interesting
16:19:51 <fsasaki> .. would like the web services endpoints to be restful
16:21:22 <fsasaki> felix: would be nice to discuss things in W3C related to FREME, will see what other FREME partners see
16:21:41 <fsasaki> phil: I am part of LD4LT group, happy to do some connection in that directoin too
16:22:16 <fsasaki> topic: XLIFF mapping
16:22:36 <fsasaki> https://lists.oasis-open.org/archives/xliff/201412/msg00045.html
16:22:46 <fsasaki> " preserve Space "
16:23:29 <fsasaki> yves: for the mapping of preserver space - for structural data there is no issue
16:23:43 <fsasaki> .. for inline text that has to be preserved, there is an issue
16:23:50 <fsasaki> .. in XLIFF you can have overlapping elements
16:23:57 <fsasaki> .. that creates issues for ITS
16:24:13 <fsasaki> ... xml:space applies to the content of the element - so ITS would apply to empty elements
16:24:22 <fsasaki> ... instead of that we would define specific attributes
16:24:53 <fsasaki> ... we looked into how to make that backward compatible
16:24:57 <fsasaki> .. but that is hard
16:25:07 <fsasaki> .. david drafted a list of fallback solutions
16:25:22 <fsasaki> ... they all had some issues, I proposed a diferent one
16:25:46 <fsasaki> ... summary is: if you have an inline code that should preserve space, you do normalization during extraction
16:26:02 <fsasaki> .. anything that could be normalized should be normalized
16:26:19 <fsasaki> .. I had some text proposal and re-arrangement in the spec, that is there the discussion is
16:26:51 <fsasaki> yves: do we need an inline representation for preserve space?
16:27:18 <fsasaki> ... if you use the fallback there is no need for the attribute
16:27:51 <fsasaki> felix: normalization during extraction is a way to avoid the attribute?
16:27:54 <fsasaki> yves: yes
16:28:14 <fsasaki> .. you create a preserve space around the complete output
16:28:26 <fsasaki> .. so there is no need to say anything inline
16:28:31 <fsasaki> phil: sounds reasonable
16:29:08 <fsasaki> felix: agreement on the call to have a way without inline preserve space
16:29:21 <fsasaki> discussion is here: http://www.w3.org/2015/01/12-i18nits-irc#T16-29-08
16:30:00 <fsasaki> yves: during XLIFF TC discussion david was the only one not agreeing
16:31:06 <fsasaki> topic: other XLIFF TC feedback
16:31:24 <fsasaki> yves: some ITS data categories are overlapping with XLIFF features
16:31:29 <fsasaki> .. like provenance
16:31:35 <fsasaki> .. that has not been addressed so far
16:32:15 <fsasaki> .. mapping is not completely done, mapping not either
16:32:28 <fsasaki> .. either we will have to limit the data categories or to push the deadline
16:33:26 <fsasaki> felix: are tehre are some data categoires that are very important for you?
16:33:36 <fsasaki> phil: everything we are using in ocelot is very well advanced
16:33:46 <fsasaki> .. if we do find anything we will find it very quickely
16:33:58 <fsasaki> .. language quality and provenacne are very well advanced
16:34:16 <fsasaki> yves: in provenance and quality not everything is mapped yet, there is some work here
16:36:30 <fsasaki> topic: other topics
16:36:42 <fsasaki> http://lists.w3.org/Archives/Public/public-i18n-its-ig/2015Jan/0001.html
16:37:10 <fsasaki> serge: one of new features of linkedin: you can do posts. before you only could do a discussion
16:37:28 <fsasaki> .. would encourage all ITS group participants to make these posts, outreach would be wider
16:37:40 <fsasaki> .. you will see more with the example screenshot
16:38:14 <fsasaki> topic: next call
16:40:33 <fsasaki> felix will make a doodle
16:41:25 <fsasaki> adjourned
16:41:30 <RRSAgent> I have made the request to generate http://www.w3.org/2015/01/12-i18nits-minutes.html fsasaki
16:41:51 <fsasaki> present - phil
16:41:52 <RRSAgent> I have made the request to generate http://www.w3.org/2015/01/12-i18nits-minutes.html fsasaki