Changes between Version 6 and Version 7 of Taskforces/FCS/VidConf20150624
- Timestamp:
- 06/24/15 13:47:05 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Taskforces/FCS/VidConf20150624
v6 v7 18 18 Not much examples except for Oliver's. We need more. 19 19 20 Matej ,are these exampel formats for Advanced dataview adhoc or based on something?20 Matej: are these exampel formats for Advanced dataview adhoc or based on something? 21 21 22 22 Oliver: mental model of that one dataview will convey all layers etc. E g no msd dataview or explict elements for some layers. It is a container format. 23 23 24 Pavel ,looks nice. Reason behind it?24 Pavel: looks nice. Reason behind it? 25 25 26 26 Any tree? Complex tree view? Multiple layers? … … 28 28 Press stop broadcasting 2-3 secs after you stop talking. 29 29 30 == Questions on Hierarchical structure==30 === Questions on Hierarchical structure === 31 31 32 32 We need to define a proper scope of work. 33 Transport hierarchy34 Matej, really another complexity level. Start with query annotation layers, and only when we master that move forward.35 33 36 Pavel, second suggestion multi annotations. Fine with forgetting trees for now. Structured/hierarchical attributes. 34 Matej: hierarchy is really another complexity level. Start with query annotation layers, and only when we master that move forward. 35 36 Pavel: second suggestion multi annotations. Fine with forgetting trees for now. Structured/hierarchical attributes. 37 37 I think it can be nice in terms of ease of understanding that some things belong together. 38 38 39 Matej, what do you mean? Provide example. 40 41 case 39 Matej: what do you mean? Provide example. 40 case example 42 41 43 42 Oliver: question of course is, if structured, how would it be structured ;) 44 43 a client like the aggregator needs to make sense of that 45 44 46 We need to harmonize if they are structured. No good solution yet.45 We need to harmonize any structured content. No good solution yet. 47 46 48 47 Dieter: Pavel: is there a standard way for that in the universal dependencies? … … 50 49 Matej: If we go this route we need to come up with even more controlled vocabularies, like for POS the UD-17 we decided on. 51 50 52 Jörg: not every endpoint will provide UD-17. We are not going to retag all corpora.51 Jörg: Not every endpoint will provide UD-17. We are not going to retag all corpora. 53 52 54 Pavel: agree hierarchical attributes istoo complex for now.53 Pavel: I agree hierarchical attributes are too complex for now. 55 54 56 55 Jörg: bidrectional translation is needed. 56 LJO: Sometimes mappings cannot be twoways, but preferably yes 57 57 58 Dieter: limited list layers 59 before making a choice 58 Dieter: Start with limited list of layers before making a choice on any proposal 60 59 61 == Question about first proposal, syllables==60 === Question about first proposal, syllables === 62 61 Oliver: Finer granularity. In worst case every single characters. 63 62 … … 75 74 silence, background noice are interpretations/computed annotations 76 75 77 What about combination of dataviews 78 allow to reference other layeritems. This was disussed at the workshop as one alternative LJO wants to provide proposal.76 === Question about combination of dataviews === 77 Allow to reference other layer's items. This was disussed at the workshop as one alternative LJO wants to provide proposal. 79 78 80 79 Oliver: non-superior layers, order is not defined in the current proposals … … 91 90 The transport format and its data could be transformed to standard format if needed. 92 91 93 == Question about parallel corpora==92 === Question about parallel corpora === 94 93 Adds another annotation layer, potentially translation also 95 94 … … 106 105 107 106 108 == Question about lexical resources==107 === Question about lexical resources === 109 108 Matej raises the question about how to handle lexical resources. 110 109 111 110 112 == Actions summary==111 === Actions summary === 113 112 * ALL: Toying with the current proposals and example 114 113 * ALL: Provide proposals 115 114 * ALL: Provide examples 116 115 * LJO: add page for advanced datawiew to trac where these can be put for reference, still important to use mailing list for discussion 116 * LJO: Add EAF to comparison matrix wehen we have more examples. 117 117 * Next meeting, 2-3 weeks, might be flash again or adobe connect 118 118 119 ''Provide you examples on this wiki [[Taskforces/FCS/Advanced DataView Example|wiki page]]''.120 119 121 120 == Documents ==
