Re: API at client/server side

I agree with option 1. For option 2, I don't understand why the
implementation as a web service requires a user agent and a java script
library to call a service. Shouldn't that be any API in any programming
languages that knows how to work with the Media Resource API? I am thinking
about a scenario like metadata harvester who does the harvesting without any
relation to a user interface, and wants to talk to the Media Resource API.

Appologies in advance if I missed some bits of the discussion. Except that
(minor) bit, I think the figure is very good.

Best,

Felix

2010/2/7 Bailer, Werner <werner.bailer@joanneum.at>

> Dear all,
>
> if the options outlined in the figure are agreed, I can write propose some
> initial text (based on the short discussion on the list after I sent the
> figure). Probably Chris, Wonsuk and others have things to add from their
> experience.
>
> Best regards,
> Werner
> ________________________________________
> Von: public-media-annotation-request@w3.org [
> public-media-annotation-request@w3.org] im Auftrag von Joakim Söderberg [
> joakim.soderberg@ericsson.com]
> Gesendet: Sonntag, 07. Februar 2010 16:28
> An: public-media-annotation@w3.org
> Betreff: API at client/server side
>
> Dear all,
> Do you agree with me to include a section in the API doc about
> implementation issues? I think it would be helpful for the test
> implementers, and it can serve as an initial effort on a Primer doc.
>
> If so do we have volunteers to write this section? Werner has already drawn
> a nice figure (included).
>
> Regards
> Joakim
>
>