11:52:31 <RRSAgent> RRSAgent has joined #i18nits
11:52:31 <RRSAgent> logging to http://www.w3.org/2014/06/18-i18nits-irc
11:52:35 <fsasaki> meeting: ITS IG
11:52:36 <fsasaki> chair: felix
11:52:43 <fsasaki> agenda: http://lists.w3.org/Archives/Public/public-i18n-its-ig/2014Jun/0016.html
11:52:54 <fsasaki> regrets: david, christian
11:52:57 <fsasaki> present+ felix
11:54:22 <fsasaki> topic: roll call
11:54:27 <fsasaki> checking attendees ...
11:54:31 <RRSAgent> I have made the request to generate http://www.w3.org/2014/06/18-i18nits-minutes.html fsasaki
11:58:04 <Arle> Arle has joined #i18nits
11:58:23 <camille> camille has joined #i18nits
12:00:40 <Yves_> Yves_ has joined #i18nits
12:01:10 <fsasaki> present+ arle, yves
12:02:27 <daveL> daveL has joined #i18nits
12:03:25 <fsasaki> present+ daveL
12:03:34 <daveL> present+ DaveLewis
12:03:50 <fsasaki> present- daveL
12:03:52 <RRSAgent> I have made the request to generate http://www.w3.org/2014/06/18-i18nits-minutes.html fsasaki
12:04:34 <fsasaki> topic: Open Data Management position statement
12:04:42 <fsasaki> https://www.w3.org/International/its/wiki/Open_Data_Management_for_Public_Automated_Translation_Services
12:05:43 <fsasaki> dave: have a tbd section - one area is licensing
12:05:52 <fsasaki> .. that would take up e.g. work done in META-SHARE and tda
12:06:03 <fsasaki> yves: I have read the doc, didn't see any issues
12:06:25 <fsasaki> "tbd: purpose help to formulate reqdocs. then: mention projects."
12:09:06 <fsasaki> dave: trying to attract other projects - would be good to run this pass @@@
12:09:28 <fsasaki> .. there is not in the way of terminology integration
12:09:39 <fsasaki> s/@@@/chris wendt/
12:09:45 <fsasaki> .. also may be relevant for alolita
12:10:17 <fsasaki> .. from wikimedia
12:10:44 <fsasaki> "tbd: cef out of focus."
12:11:01 <fsasaki> " tbd: mention other standards explicitly? what is a standard? "
12:11:13 <fsasaki> dave: point to current projects - there is also ongoing work that we can point to
12:11:28 <fsasaki> .. e.g. bitext access on the web, we are doing that in the bpmlod group
12:11:38 <fsasaki> ... there is licensing work in the ld4lt group
12:12:04 <fsasaki> .. need to have a way to point to these group
12:12:56 <fsasaki> felix: raise awareness in above groups and make them aware that we'd like their input
12:13:10 <fsasaki> dave: also ontolex and the tbx / RDF work, need input from Philipp here
12:13:34 <fsasaki> .. I will present this in the MLi panel at the LT-Innovate event in brussels next week
12:13:50 <fsasaki> .. maybe have a little questionnaire that people can pick up to follow
12:13:55 <fsasaki> s/follow/follow up/
12:14:17 <fsasaki> "Open standards. Open standards are standards that can be implemented on a royalty-free basis, that is, without any licensing requirements."
12:14:34 <fsasaki> arle: need to add to the above: there needs to be a policy for maintaining them in an open way as well
12:15:39 <fsasaki> dave: bring up this week bpmlod call; had raised it at ld4lt last week.
12:16:02 <fsasaki> felix: I'll contact ontolex and alolita
12:17:49 <fsasaki> dave: if any of this feeds into the CEF call, that would help
12:18:04 <fsasaki> .. would help to get the right people on board here
12:18:32 <fsasaki> .. might help to talk to EU people to see if they have guidance
12:19:30 <fsasaki> "tbd: mention other standards explicitly? what is a standard?"
12:20:30 <fsasaki> dave: two elements of this:
12:20:37 <fsasaki> .. listing things that are already availabe
12:20:56 <fsasaki> .. you can say: relevant existing standards, and standards that are worked on: lemon, XLIFF 2.0, ...
12:21:05 <fsasaki> .. and then saying: where are the gaps?
12:21:33 <fsasaki> .. one objective is: we don't know the answers always - there are some areas in which gaps need to be filled and there may be new work to be done
12:21:42 <fsasaki> .. that may also help e.g. EU to decide what to support
12:21:59 <fsasaki> .. put in DCAT
12:22:03 <fsasaki> felix: MQM?
12:22:15 <fsasaki> arle: it is not a standard yet, but moving into that direction
12:22:52 <fsasaki> dave: so one could have several categories: final standard, draft standard, technology areas that need standardaration
12:24:30 <fsasaki> "Bitext Data Management Requirements" - here MQM would fit very well as s.t. being prepared
12:25:03 <fsasaki> .. e.g. lemon would very well
12:25:16 <fsasaki> .. in that way too
12:25:50 <fsasaki> .. section at the end - "gap analysis"
12:27:38 <fsasaki> .. table . we now have numbered requirements. we tick of maturity of avail. solutions
12:28:23 <fsasaki> felix will add at the beginning about intention to do an IG draft (to be discussed)
12:28:31 <fsasaki> dave: also have a contributors section
12:29:47 <fsasaki> arle: get feedback from gala too, contacting several people
12:32:48 <fsasaki> felix: have a section for mentioning meta-net and other efforts those community, who would benefit from this
12:32:51 <fsasaki> dave: good idea
12:33:11 <fsasaki> s/community, who /those communities/
12:34:03 <fsasaki> dave: lot of mt researchers are now using wikipedia for mt training, maybe a good collab. point with meta-net, e.g. experience in a particular country
12:34:11 <fsasaki> felix: I'll check with the meta-net guys
12:35:43 <fsasaki> arle: josef v.g. may be the right person to check that
12:39:23 <fsasaki> topic: xliff web IDL
12:41:21 <fsasaki> felix describing web IDL choice options - web IDL for defining interfaces, plain json for serializing the current XML - XLIFF
12:41:38 <fsasaki> yves: web IDL relation is confusing (CR versus other draft)
12:42:00 <fsasaki> .. in XLIFF we need two things, both API and data format aspect
12:42:40 <fsasaki> .. API is not useful if you don't have a clear object definition
12:42:50 <fsasaki> dave: your existing API - is that a good model?
12:42:56 <fsasaki> yves: needs to be more generic
12:43:10 <fsasaki> .. main problem is data format - depends on what you want to represent
12:43:24 <fsasaki> .. e.g. how to represent inline code is quite complex, you have distinct solutions
12:43:29 <fsasaki> .. not sure on how to proceed
12:43:50 <fsasaki> dave: talked to david about this - general feeling is: inline codes dealing with overlapping annotations is in the heart of this
12:44:19 <fsasaki> yves: if this is then not XML people would see things differently
12:44:23 <fsasaki> .. inline representation is key
12:44:59 <RRSAgent> I have made the request to generate http://www.w3.org/2014/06/18-i18nits-minutes.html fsasaki
12:46:19 <fsasaki> .. will talk to david about this again e.g. on the next call
12:46:59 <fsasaki> arle: worth looping in linport in this, they are discussing APIs right now, trying to clarify relationsships to others
12:47:16 <fsasaki> topic: MQM + ITS
12:47:52 <fsasaki> dave: we had discussion in FEISGILTT about MQM and relationship to ITS "localization quality issue" types
12:48:05 <fsasaki> .. there then was exchange on the list about this, Arle clarifying things
12:48:16 <fsasaki> http://lists.w3.org/Archives/Public/public-i18n-its-ig/2014Jun/0000.html
12:48:51 <fsasaki> dave: arle saying how to map MQM into ITS or into other things - is that correct?
12:49:06 <fsasaki> arle: to some extend. MQM allows you to declare that you check
12:49:15 <fsasaki> .. ITS can be more or less of what you check
12:49:34 <fsasaki> .. so you could declare an MQM model that is ITS
12:49:59 <fsasaki> .. the idea: ITS provides broad interop, if people map their categories they know what is there
12:50:20 <fsasaki> .. MQM would not know in advance what is in a metrics
12:50:29 <fsasaki> dave: in ITS you have the loc quality profile ref
12:50:42 <fsasaki> .. in the MQM doc you could put the reference to the precise MQM type
12:51:00 <fsasaki> .. so the mapping will be definitive
12:51:30 <fsasaki> .. MQM structure details would be lost or would need to be in the string of ITS locProfileRef
12:52:03 <fsasaki> arle: you would define a mapping and point to a file that has the mappings
12:52:44 <fsasaki> yves: I think in ITS you cannot declare things at the top
12:52:49 <fsasaki> Arle: ok
12:53:03 <fsasaki> .. the reference could point to an MQM declaration
12:53:19 <fsasaki> .. that looses the ability of what the overall profile is
12:53:35 <fsasaki> .. one could use MQM without having MQM specific markup in ITS
12:53:50 <fsasaki> dave: you hit all problems if you start with an XML vocabulary
12:54:36 <fsasaki> arle: felix had said a while ago if we should use RDF instead of XML - we may end up doing that for MQM (or have both)
12:54:49 <fsasaki> dave: sometimes people have a vocabulary and a document in parallel
12:55:09 <fsasaki> .. but you can put definitions into RDF and then generate an HTML document which is human readable
12:55:54 <fsasaki> dave: what is your timeline on this, Arle?
12:56:16 <fsasaki> arle: development is planned to continue in qt21 and potentially in other projects
12:57:53 <fsasaki> dave: in ld4lt it works quite well to team up with people to do some specific work items, e.g. taking an existing model, do rdf related things - but the group who brings in the topic still owns it
12:58:59 <fsasaki> .. the benefit for the group who bring in the topic is more feedback and visibility, but they don't loose ownership
12:59:11 <fsasaki> .. good example is meta-share schema discussion
13:00:48 <fsasaki> .. I am one of the ld4lt co-chairs, we could bring it up on the ld4lt call next week (Thursday 3 p.m.)
13:03:01 <fsasaki> felix: arle could bring his material to the call and we'd see what the ontology engineers can do with that
13:03:47 <fsasaki> dave: agree. one reasons also why the MQM / RDF disucssion is interesting: they are opportunistics, using what is avail. from wikipedia or babelnet
13:04:12 <fsasaki> .. many resources are under active curation. being avail. to report such things back in an open way would be a great use case for MQM
13:04:30 <fsasaki> .. MQM would have a lot of the semantics for such error reporting
13:04:56 <fsasaki> arle: perfect, that is exactly what we want to do
13:05:50 <fsasaki> dave: great - I will email ld4lt group and CC Arle, saying we are planning to put it on the agenda
13:05:51 <fsasaki> arle: ok
13:06:04 <fsasaki> dave: and you can reply to that providing more info
13:06:07 <fsasaki> arle: ok
13:09:53 <fsasaki> topic: aob
13:09:56 <fsasaki> adjourned
13:10:00 <RRSAgent> I have made the request to generate http://www.w3.org/2014/06/18-i18nits-minutes.html fsasaki
13:18:50 <fsasaki> fsasaki has joined #i18nits