W3C

- DRAFT -

ITS IG

18 May 2015

Agenda

See also: IRC log

Attendees

Present
felix, yves, davidF, serge
Regrets
christian, Phil, David
Chair
felix
Scribe
fsasaki

Contents


roll call

<dF> my other meeting got cancelled

<dF> will connect to audio shortly

https://lists.w3.org/Archives/Public/public-i18n-its-ig/2015May/0005.html

Action items

action-30?

<trackbot> action-30 -- David Lewis to work on json-ld mapping of its2 -- due 2014-05-30 -- OPEN

<trackbot> http://www.w3.org/International/its/ig/track/actions/30

XLIFF mapping

david: there is development on storage size data category
... fredrik deveploed a solution on that, should appear shortly in developers draft
... other from that situation did not change
... summary: there is good text analytics and terminology description in the editors draft
... MT confidendence and provenance are still missing from the high priority data categories
... to move this forward we need some discussion
... we would need a mockup / strawman how provenance would work for june f2f
... also for MT confidence
... would be good to discuss these to during the f2f

felix: could I contribute s.t.?

david: sure - I took the mappings that Yves created in the wiki, then take the behaviour of the attributes
... explain the same constraints as constraints of a custom mapping
... that is defined as part of ITS module
... there is an annotation mechanism in XLIFF
... various elements on structural or inline level
... that gives control about how the annotations should work
... currently sorush working on advanced validation
... direct editing in XML source code in oasis is OK

felix: would be ok to create MT confidence and provenance section

david: sure
... you could also contribute to schematron validation

ITS in JSON

<Yves_> https://www.w3.org/International/its/wiki/JSON%2BITS

yves: very basic right now
... david had a good point - selection mechanism is defined as json path
... could also use other mechnaisms like json select
... you could define which selector mechnaism you are using

serge: very nice demo!
... is there a way to look at the IoT demo?

felix: once we slides of the IoT demo are done I will send them around

http://www.locworld.com/sessions/the-internet-of-things/

<dF> Yves will also present ITS for json at FEISGILTT http://www.locworld.com/feisgiltt-program/

discussion on IoT and localisation

https://sgladkoff.wordpress.com/2015/05/16/riga-summit-personal-report/

(Riga summit summary from Serge)

serge: presentation about communication between machines - that can be connected to IoT I think

"Dr.Robert Dale from ARRIA."

felix: is there need for ITS locally, e.g. inside a json string?

yves: yes, in our demo, you have data that you can get dynamically
... you would need to add a flag then if things are translatable
... local stuff could be done via global rules as well
... to trigger specific conditions
... so you don't need an ITS specific mechanism, but a flag that the global rules can use

felix: so like ITS mapping for XML vocabularies?

yves: corrrect
... and you can also have external rules, json is very flexible

https://groups.google.com/forum/#!forum/json-schema

felix: what is the best forum to get feedback from json community?

yves: most developers don't care - if they need it they go to github and use the code ,and things become the defacto standard

felix: good point - so just move implemnetation forward and try to get some uptake & feedback

taus TML proposal

https://lists.w3.org/Archives/Public/public-i18n-its-ig/2015Apr/0004.html

felix: should we follow up on that?
... or just leave things "as is"?

serge: have discussion in TAUS website is good PR for us. I was busy could not follow up yet
... I'll follow up on this
... there was a good technical discussion, there is a good argument why ITS makes sense

felix: CEF community working on language resource collection - should we involve them too?

serge: metadata for LR at the moment is not an issue, but quality
... question is how to evaluate things - not clear how to introduce ITS on legacy resources
... e.g.. automatic mapping to standard ITS
... if you go forward sure, then ITS adding has value

felix: agree, and TM or parallel corpora were not in focus for ITS so far

XLIFF f2f meeting in Berlin 1 July

felix: any other topics we should prepare for f2f meeting?
... in addition to provenance and mt confidence?

david: review the data categories that are done in the spec

discussion on XLIFF mapping action items

david: if you send input this week we can word smith during f2f

yves: ok

david: will identify gaps and will look for volunteers to close them
... could have a small task force in the XLIFF TC for schematron rules
... looking into other serializations of XLIFF during wednesday

http://de.slideshare.net/m1ci/nif-tutorial/10

felix: may be a syngery to the RDF - NIF representation, see NIF link above

serge: would be nice to explain how this is being done, with RDF applications

felix: FREME started some related implemtnation, has not gone public yet, hopefully soon

usual topics & AOB

david: send a doodle to the whole list for the call?
... re-create awareness of the time

felix: doodle for call time, sure, I'll send one out

david: we need more working sessions - currently call is more status checking

adjourned

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2015/05/18 15:59:08 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/force/force in the XLIFF TC/
No ScribeNick specified.  Guessing ScribeNick: fsasaki
Inferring Scribes: fsasaki
Present: felix yves davidF serge
Regrets: christian Phil David
Agenda: https://lists.w3.org/Archives/Public/public-i18n-its-ig/2015May/
Got date from IRC log name: 18 May 2015
Guessing minutes URL: http://www.w3.org/2015/05/18-i18nits-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]