W3C home > Mailing lists > Public > public-media-annotation@w3.org > August 2009

Re: Media Annotations API implementation - asking for confirmation and a few questions

From: David Singer <singer@apple.com>
Date: Tue, 4 Aug 2009 11:40:02 -0700
Message-Id: <p0624082fc69e3091b97c@[]>
To: Felix Sasaki <felix.sasaki@fh-potsdam.de>, "public-media-annotation@w3.org" <public-media-annotation@w3.org>
At 11:30  +0200 3/08/09, Felix Sasaki wrote:
>Hello all,
>I had a look at the Strawman API design and notes Wiki
>and made up a user interface design based on the
>"get-mawg-unstructured-value" method. Could you please have a look at
>and tell me if I have interpreted the strawman correctly?
>Also, I have a few questions:
>1) What is a fragment-indicator?

a media fragment, presumably phrased to the media 
fragment group's recommendations.  e.g. 
"time="10s-20s" to select a 10 second fragment (I 
made up the syntax).

>2) Where are the subtype definitions needed for the sub-type-filter ?
>I had a look at the mapping table but could not find them.

That was to handle properties that can have 
sub-types (eg the role of a contributor).  we 
didn't get to a syntax for that (or anything 

>3) The language-code-filter is a bit unclear to me.
>- RFC 4647 http://www.ietf.org/rfc/rfc4646.txt defines two matching
>schemes for language tags: lookup or filtering. Lookup returns one or
>no value ("give me the resource if it is French"), and is often
>combined with priority information (e.g. "French" with priority 1.0,
>"English" with priority 0.5, ...). Filtering returns a possibly empty
>set of values ("give me all resources which are French"). Is your
>intention here really "only" filtering?
>- For filtering there are two variants: basic filtering and extended
>filtering. Basic filtering matches the language tag against a
>so-called basic language range. For a match the language range needs
>to be
>	identical to the language tag, e.g. the language range "en" = the
>language tag "en" or
>	a prefix, e.g. the language range "en" = the prefix of the language
>tag "en-us".
>Extended filtering uses extended language ranges, that is a
>specification of an ordered sequence of sub tags. For example, the
>extended language range "de-de" matches de-de, de-latn-de, de-latf-de,
>de-de-1901, since the sequence "de-de" is always given. However, it
>does not match "de-x-de".
>My question is what we want: basic filtering or also extended filtering?

ah, yes.  I think we need to talk about it.

>Many thanks for the feedback in advance. Note that I will be on
>holiday now for two weeks, so my follow up might take some time.
>Content-Type: text/html; charset=US-ASCII; name="Overview.html"
>Content-Disposition: attachment; filename="Overview.html"
>X-Attachment-Id: file0
>Attachment converted: DaveG49:Overview 2.html (TEXT/«IC») (0023F8F9)

David Singer
Multimedia Standards, Apple Inc.
Received on Tuesday, 4 August 2009 18:41:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:17:35 UTC