W3C home > Mailing lists > Public > public-html@w3.org > May 2011

RE: follow up on the discussion in HTML5 about metadata access

From: Leonard Rosenthol <lrosenth@adobe.com>
Date: Wed, 4 May 2011 16:52:35 -0700
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, "tmichel@w3.org" <tmichel@w3.org>
CC: "public-html@w3.org" <public-html@w3.org>, "public-media-annotation@w3.org" <public-media-annotation@w3.org>
Message-ID: <D23D6B9E57D654429A9AB6918CACEAA98059D1A2B6@NAMBX02.corp.adobe.com>
> Right now, all use cases discussed on the HTML WG list were solvable
> with server-side APIs.
>
That is NOT true, Silvia!

I raised a number of use cases for non-browser-based UAs - for example EPUB viewers - where server-side was NOT an option.

Leonard

-----Original Message-----
From: public-html-request@w3.org [mailto:public-html-request@w3.org] On Behalf Of Silvia Pfeiffer
Sent: Wednesday, May 04, 2011 4:01 PM
To: tmichel@w3.org
Cc: public-html@w3.org; public-media-annotation@w3.org
Subject: Re: follow up on the discussion in HTML5 about metadata access

Michael,

The argument that other applications expose such an interface is not a
use case for including them in HTML5.

You will need to demonstrate a user situation where the user/web
developer can't do something unless the API is available in the
browser.

Right now, all use cases discussed on the HTML WG list were solvable
with server-side APIs.

Cheers,
Silvia.


On Thu, May 5, 2011 at 12:14 AM, Thierry MICHEL <tmichel@w3.org> wrote:
> Sylvia, HTML WG,
>
> To follow up on your discussion  in HTML5 about metadata access and the
> Ontology and API for Media Resources,  and our previous email [1]followed by
> Sylvia responses [2a, 2b] about the Media API [3]
>
> Sylvia seem to say that you don't need such API in the browser to extract
> video/audio/image metadata. It would be done server-side.
>
> On the other hand Leonard says  [4] that the API for metadata access to
> media would be a appropriate for Web UAs like for axample EPUB3 (based on
> HTML5) allowing scripting.
>
> The MAWG would like to have a better understanding of your concerns. Could
> you please explain more deeply what are your issues for access to these
> metadata, and which requirements are not satisfactorily addressed by the
> MAWG API. Could you provided a few use cases we could study and see how our
> API fits.
>
> Finally, Sylvia as you are part of both the MA WG HTML WG, could you please
> join our next tecon next Tuesday to have a deeper discussion on this topic
> and report the HTML concerns.
>
> Best regards,
>
> Thierry.
>
>
>
>
> [2a]
> http://lists.w3.org/Archives/Public/public-media-annotation/2011Apr/0054.html
>
> [2b]
> http://lists.w3.org/Archives/Public/public-media-annotation/2011May/0001.html
>
> [3]
> http://dev.w3.org/2008/video/mediaann/mediaont-api-1.0/mediaont-api-1.0.html
>
>
> [4]
> http://lists.w3.org/Archives/Public/public-media-annotation/2011Apr/0057.html
>
>
Received on Wednesday, 4 May 2011 23:56:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:31 GMT