Changes between Version 1 and Version 2 of Taskforces/FCS/Workshop20150529
- Timestamp:
- 06/24/15 12:47:30 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Taskforces/FCS/Workshop20150529
v1 v2 1 = Notes from FCS-taskforce workshop meeting 2015-05-29=1 = Notes from FCS-taskforce workshop meeting 2015-05-29 = 2 2 3 What info can we provide to foster the community to work together collaboration 3 What info can we provide to foster the community to work together collaboration? 4 4 * wiki template 5 5 * software stack 6 6 7 == Advanced FCS==7 == Advanced FCS == 8 8 *Goal: Spec in 2-3 months, endpoints end of year 9 9 * Agree on features … … 13 13 What are essential decisions in order to be able to move forward? 14 14 15 == POS==15 == POS == 16 16 Different tagsets. Tools or language? 17 17 Universal dependencies. Mappings. 18 18 19 == MSD==19 == MSD == 20 20 There is already a working group in Clarin-D for this to find use cases. First results from the group in a few weeks. 21 21 22 == Layers==22 == Layers == 23 23 As discussed before: fulltext, lemma, token/word, pos, orth trans, phon trans, headword, ner, gestures, signs, discourse, translation, depency trees, constituents, glosses 24 24 … … 30 30 Easy downgrade in case of failure, not hits if no resources are found. 31 31 32 == Communicate capabilities==32 == Communicate capabilities == 33 33 Features, max better than dynamical minimal set? 34 34 35 == Output/result transport format for advanced-FCS==35 == Output/result transport format for advanced-FCS == 36 36 Focus on overview level today and save details for later 37 37 … … 41 41 Bart stand-off will be a problem. Aggregator has to do something with it? 42 42 43 == Summary Dataviews==43 == Summary Dataviews == 44 44 * We should keep generic dataviews. 45 45 * Make comparison of current or inhouse transport format.
