Changes between Version 3 and Version 4 of Taskforces/FCS/VidConf20150624

Timestamp:

06/24/15 12:56:17 (9 years ago)

Author:

Leif-Jöran

Comment:

draft minutes

Taskforces/FCS/VidConf20150624

@@ -13 +13 @@
  1. !DataView(s)
 
-== Outcome: Minutes, Decisions and Actions ==
- will be here today.
+== Outcome: Minutes, Decisions and Actions (currently draft) ==
+ Main focus Dataview return format
+
+Not much examples except for Oliver's.
+
+Advanced dataview
+Adhoc or based on something?
+Oliver mental model one dataview will convey all layers etc
+
+So no msd dataview
+explict elements for some layers
+container format.
+Pavel, looks nice. Reason behind it?
+Any tree? Complex tree view? Multiple layers?
+
+Press stop 2-3 secs after stop talking.
+Hierarchical structure.
+Proper scope of work.
+Transport hierarchy
+Matej, really another complexity level. Start with query annotation layers, and only when we master that move forward.
+
+Pavel, second suggestion multi annotations. Fine with forgetting trees for now. structured/hierarchical attributes.
+I think it can be nice in terms of ease of understanding that some thing belong together.
+
+Matej, what do you mean? Example.
+
+case 
+
+Oliver (IDS): question of course is, if structured, how would it be structured ;)
+a client like the aggregator needs to make sense of that 
+
+harmonize if they are structured.
+No good solution yet.
+
+Dieter: Pavel: is there a standard way for that in the universal dependencies?
+
+Controlled vocab
+Like for POS the UD-17 we decided on.
+Jörg not every endpoint will provide UD-17 we are not going to retag all corpora.
+
+Pavel, agree hierarchical attributes is too complex for now. 
+
+Jörg bidrectional translation.
+
+Dieter, limited list
+choice
+first proposal, syllables.
+finer granularity. In worst case every single character.
+
+Candidate for speech
+or primarily for textual resources?
+
+time lined signal
+"textual" annotations
+
+Dieter concrete example. Silence is best covered by example 1.
+Transcribed speech corpora.
+
+Matej, generic way to describe atomic units. So time stamp could be fitted with example 2.
+
+Oliver, yes, offsets can well be timestamps
+
+silence background noice
+
+Combination of dataviews
+allow to reference other layer items
+non-superior layers
+order is not defined, but
+Dieter: I have the impression we are re-inventing formats like EAF: https://corpus1.mpi.nl/media-archive/demo/Ams_Demo/versioning_demo/Annotations/118_fishing2-fire-2011.eaf
+
+Comparison matrix.
+
+Keep things simple.
+
+Keep it fairly straight forward.
+
+Keep non-textual formats in mind.
+
+Doing concrete proposals. More are needed.
+
+transform to standard format.
+
+What about parallel corpora?
+another annotation layer trans
+
+More discussion is needed. Concrete proposals.
+
+Hanna, concrete examples? Propose new layers?
+Mappings are welcome.
+
+Use second view in examples
+
+Need attribute for unit.
+
+Matej, lexical resources.
+
+Toying
+
+
+LJO: add page for advanced datawiew to trac.
+Next meeting, 2-3 weeks
+Might be flash or adobe connect
+
 
 == Documents ==