W3C home > Mailing lists > Public > public-media-annotation@w3.org > January 2011

Re: Open action items

From: Florian Stegmaier <stegmai@dimis.fim.uni-passau.de>
Date: Mon, 24 Jan 2011 14:23:17 +0100
Cc: <public-media-annotation@w3.org>
Message-Id: <4B290A84-7A86-4B7B-8FD5-B3E27717FB13@dimis.fim.uni-passau.de>
To: <Chris.Poppe@UGent.be>
Hi Chris!

Thanks for brining this up again!

My main concern with sync and async was not the differentiation, but the reflection in the text - here, we have to be precise and complete! We have to clearly state, why someone should implement the sync case and not just use the async with an immediate answer. We have to give arguments for this and esp. we have to define a scenario, where we differ exactly between sync and async to rely on. At the moment, the specification is a little bit weak looking at its "global" consistency/clarity.

The last comment on the specification is from an implementors point of view: the call by reference things may be a really good thing for a javascript lib, but only very hard to handle with a Webservice. A Webservice per se is not able to handle call by reference calls - here the client has to implement the defined interfaces and then somehow communicate with a server to handle the references in the specified way. Due to the fact, that we mention explicitly a Webservice scenario in the API, i think it is not desirable to have an API, which is more or less against these paradigms.

Nevertheless, i really like the changes related to the object structure, which makes it possible to simply iterate over the parameters.

Best,
Florian


Am 24.01.2011 um 12:37 schrieb Chris Poppe:

> Dear all,
>  
> This is a re-post of an earlier mail to make sure it is known of during tomorrow’s telco.
>  
> Action 385
> The floats were changed to doubles (there are no floats left in the current
> draft...)
>  
> Action 397
> Additionally, the issue regarding HTML 5 was solved when incorporating the comment of Robin (see my mail: Re: [todo] Response to your LC Comment -2419 on Media API spec, sent to the mailing list on Monday November first). This mail was a repost of a previous mail in which I summarized my comments on Robin's questions.
> In this I explained the changes made according to the HTML 5 part (quote)
>  
>  
> Lastly, I roughly agree with Florian's comments and can do those editorial(!) changes that the group agrees on.
>  
> The strong differentiation between sync and async API is based on Robin’s comments on the specification.
>  
> Kind regards,
> Chris
>  
>  
> Ghent University - IBBT
> Faculty of Engineering
> Department of Electronics and Information Systems (ELIS)
> Multimedia Lab Gaston Crommenlaan 8 bus 201
> B-9050 Ledeberg-Ghent
> Belgium
>  
> t: +32 9 33 14985
> f: +32 9 33 14896
> t secr: +32 9 33 14911
> e: chris.poppe@ugent.be
>  
> URL: http://multimedialab.elis.ugent.be
>  

_____________________________
Dipl. Inf. Florian Stegmaier
Chair of Distributed Information Systems
University of Passau
Innstr. 43
94032 Passau

Room 248 ITZ

Tel.: +49 851 509 3063
Fax: +49 851 509 3062

stegmai@dimis.fim.uni-passau.de
https://www.dimis.fim.uni-passau.de/iris/
http://twitter.com/fstegmai
_____________________________
Received on Monday, 24 January 2011 13:23:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 24 January 2011 13:23:52 GMT