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

Re: RE : RE : Recapitulation of ma:format vs. ma:compression.

From: Pierre-Antoine Champin <pierre-antoine.champin@liris.cnrs.fr>
Date: Thu, 03 Feb 2011 10:00:47 +0100
Message-ID: <4D4A6EBF.20901@liris.cnrs.fr>
To: "Evain, Jean-Pierre" <evain@ebu.ch>
CC: "'tmichel@w3.org'" <tmichel@w3.org>, David Singer <singer@apple.com>, Joakim Söderberg <joakim.soderberg@ericsson.com>, Daniel Park <soohongp@gmail.com>, "public-media-annotation@w3.org" <public-media-annotation@w3.org>
On 02/03/2011 09:14 AM, Evain, Jean-Pierre wrote:
> It is not wrong but it is not elegant. URI#Name is a URI. The
> original definition was right. As I said no need for modification.
> Only add the example in the semantics.

+1

there is no conceptual difference between a hash-uri and a slash-uri. We 
should not constrain that in the ontology. An example should be fine.

   pa

>
> Jean-Pierre
>
> -----Original Message----- From: Thierry MICHEL
> [mailto:tmichel@w3.org] Sent: jeudi, 3. février 2011 09:09 To: Evain,
> Jean-Pierre Cc: David Singer; Joakim Söderberg; Daniel Park;
> public-media-annotation@w3.org Subject: Re: RE : RE : Recapitulation
> of ma:format vs. ma:compression.
>
> Updated to:
>
> compression	(attName="compression", attValue="URI#Name" | "String")
>
> see
> http://dev.w3.org/2008/video/mediaann/mediaont-1.0/mediaont-1.0.html#core-property-lists
>
>
>
> Thierry
>
>
>
> Le 31/01/2011 07:28, Evain, Jean-Pierre a écrit :
>> Hi David,
>>
>> I see you had a safe trip back. Me too but I arrived quite late in
>> Geneva with Touradj.
>>
>> As discussed, fine by me as # constructs are URI and is directly
>> compatible with the way the ontology has been written.
>>
>> However only one additional comment: I would suggest we recommend
>> the use of ea dereferencable URIs, which use a URL basis instead of
>> namespaces.  For example, EBU Skos classification schemes are
>> available as permanent web resources and use URL based URIs.
>>
>> Regards,
>>
>> Jean-Pierre ________________________________________ De :
>> public-media-annotation-request@w3.org
>> [public-media-annotation-request@w3.org] de la part de David Singer
>> [singer@apple.com] Date d'envoi : samedi, 29. janvier 2011 23:26 À
>> : tmichel@w3.org Cc : Joakim Söderberg; Daniel Park;
>> public-media-annotation@w3.org Objet : Re: RE : Recapitulation of
>> ma:format vs. ma:compression.
>>
>> In further discussion, it seems that using anchor syntax and a # as
>> the separator is cleaner.  Can we change to
>>
>>>> attValue="URI#Name"
>>
>>>> compression="urn:example-org:codingnames2010#ITU-H264"
>>>> compression="http://example.net/standards/codecs#G711"
>>
>> with corresponding changes to the text?
>>
>> On Jan 29, 2011, at 23:28 , Thierry MICHEL wrote:
>>
>>>
>>>> compression
>>>>
>>>> (attName="compression", attValue="URI" | "String")
>>>>
>>>> The compression type used. For container files (e.g.,
>>>> QuickTime, AVI), the compression is not defined by the format,
>>>> as a container file can have several tracks that each use
>>>> different encodings. In such a case, several compression
>>>> instances SHOULD be used. Thus, querying the compression
>>>> property of the track media fragments will return different
>>>> values for each track fragment. Note: it is possible to use an
>>>> extendedMIME type as the value for this property, see [RFC
>>>> 4281].
>>>>
>>>>
>>>>
>>>> suggested change to
>>>>
>>>> compression
>>>>
>>>> (attName="compression", attValue="URI, String")
>>>>
>>>> The compression type used. For container files (e.g.,
>>>> QuickTime, AVI), the compression is not defined by the format,
>>>> as a container file can have several tracks that each use
>>>> different encodings. In such a case, several compression
>>>> instances SHOULD be used. Thus, querying the compression
>>>> property of the track media fragments will return different
>>>> values for each track fragment.   The indicator is a pair of
>>>> values, separated by a comma. The first is a URI that
>>>> identifies the naming convention used for the second parameter,
>>>> which is a string.  For some container files, the format
>>>> parameter can also carry an extended MIME type to document
>>>> this; see [RFC 4281] for one such instance.
>>>>
>>>> Examples: compression="urn:example-org:codingnames2010,
>>>> ITU-H264" compression="http://example.net/standards/codecs,
>>>> G711" where ITU-H264 and G711 are defined by example.org (who
>>>> also defined a URN to identify their naming conventions), and
>>>> by example.net (who use a URL to identify theirs).
>>>>
>>>
>>>
>>> Updated the compression Statement.
>>> http://dev.w3.org/2008/video/mediaann/mediaont-1.0/mediaont-1.0.html#core-property-lists
>>>
>>>
>>>
For the examples; I have added a link to the following section, which 
contains the examples.
>>>
>>> 5.1.3.1 Examples for the compression property
>>>
>>> Best,
>>>
>>> Thierry
>>>
>>
>> David Singer Multimedia and Software Standards, Apple Inc.
>
Received on Thursday, 3 February 2011 09:01:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 3 February 2011 09:01:20 GMT