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

RE: Agreed Changes in the 5.1.2 Descriptive properties (Core Set) table for the Type definition column.

From: Thierry Michel <tmichel@w3.org>
Date: Tue, 15 Feb 2011 22:16:47 +0100 (CET)
Message-ID: <a3ce30c487a7544fce05d498cd259363.squirrel@webmail.sophia.w3.org>
To: "Evain, Jean-Pierre" <evain@ebu.ch>
Cc: "'Thierry Michel'" <tmichel@w3.org>, "public-media-annotation@w3.org" <public-media-annotation@w3.org>

> Hello Thierry,
>
> I guess you could have asked all the meeting participants to review this
> too ;-))


Right, I copied the Group but I should have asked everyone to review, in
particular David Singer.
>
> It is important to remind the group that the changes have been decided as
> summarised in your notes in the following context:
>
> - the notation used in the table follows the convention defined in the
> paragraph before the section with the table.
> - it was decided to continue with these conventions as other changes would
> have an impact on the API but more dramatically on the mapping tables.


Right, this was our conclusion from this morning discussion. Thankyou for
clarifying it.

>
> The table has been reviewed in details and remaining inconsistencies have
> hopefully been resolved.


>
> Jean-Pierre
>
> -----Original Message-----
> From: Thierry Michel [mailto:tmichel@w3.org]
> Sent: mardi, 15. février 2011 22:03
> To: Evain, Jean-Pierre
> Cc: public-media-annotation@w3.org
> Subject: Agreed Changes in the 5.1.2 Descriptive properties (Core Set)
> table for the Type definition column.
>
> Here are the changes in the Ontology for the 5.1.2 Descriptive properties
> (Core Set) table for the Type definition column.
>
> Identification
> identifier 	(attName="identifier", attValue="URI") 					[NO change]
> title 	  { (attName="title", attValue="String"), (attName="type",
> attValue="URI" | "String"")? } 		[CHANGED]
> language    (attName="language", attValue="URI" | "String") [NO change]
> locator 	  (attName="locator", attValue="URI") 						[NO change]
>
> Creation
> contributor 	{ (attName="contributor", attValue="URI" | "String"),
> (attName="role", attValue="URI" | "String")? } 	[CHANGED]
> creator 	    { (attName="creator", attValue="URI" | "String"),
> (attName="role", attValue="URI" | "String")? }      [CHANGED]
> date 	        { (attName="date", attValue="Date"), (attName="type",
> attValue="URI" | "String")? } 	                [CHANGED]
> location 	    { (attName="name", attValue="URI" | "String")?,
> (attName="longitude", attValue="Double")?, (attName="latitude",
> attValue="Double")?, (attName="altitude", attValue="Double")?,
> (attName="coordinateSystem", attValue="URI" | "String")? } 	[CHANGED]
>
> Content description
> description 	(attName="description", attValue="String") 	[NO change]
> keyword 	    (attName="keyword", attValue="URI" | "String")
> genre 	      (attName="genre", attValue="URI" | "String") 	[NO change]
> rating 	    { (attName="value", attValue="Double"),
> (attName="ratingSystem", attValue="URI" | "String")?, {(attName="min",
> attValue="Double"), (attName="max", attValue="Double")}? } 	[CHANGED]
>
> Relational
> relation 	{ (attName="target", attValue="URI" | "String"),
> (attName="type", attValue="URI" | "String")? } 	[CHANGED]
> collection 	(attName="collection", attValue="URI" | "String") [NO change]
>
> Rights
> copyright 	{ (attName="copyright", attValue="URI" | "String"),
> (attName="holder", attValue="URI" | "String")? } [CHANGED]
> policy 	    { (attName="statement", attValue="URI" | "String"),
> (attName="type", attValue="URI" | "String")? }   [CHANGED]
>
> change the text to ....
> A tuple containing a policy statement either human readable as a string or
> machine resolvable as a URI, and the type of the policy to provide more
> information as to the nature
> of the policy. See examples.
>
> Distribution
> publisher 	      (attName="publisher", attValue="URI" | "String") 	[NO
> change]
> targetAudience 	{ (attName="audience", attValue="URI" | "String"),
> (attName="classificationSystem", attValue="URI" | "String") } [CHANGED]
> A tuple identifying the classification @@@ system @@@ (e.g., a parental
> guidance issuing agency, or a targeted geographical region) and the value
> given in this classification.
>
> Fragment
> fragment 	      { (attName="identifier", attValue="URI"), (attName="role",
> attValue="URI" | "String")? } 	[CHANGED]
> namedFragment 	{ (attName="identifier", attValue="URI"), (attName="label",
> attValue="String") } 	        [NO change]
>
>
> Technical Properties
> frameSize 	{ (attName="width", attValue="Double"), (attName="height",
> attValue="Double"), (attValue="unit", attValue="String")? } 	[NO change]
> compression 	(attName="compression", attValue="URI" | "String") 	[NO
> change]
> change the text to ....
> 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.
> Either or both of two values may be supplied: a free-form string which can
> be used for user display or when the naming convention is lost or unknown.
> The URI consists of a absolute-URI (RFC 3986, section 4.3) and fragment
> (RFC 3986, section 3.5), that is, e.g. in the form absolute-URI#name. The
> absolute-URI identifies the naming convention used for the second
> parameter, which is a string name from that convention.  A URL is
> preferred for the URI, and if it is used, it (a) might contain a date in
> the form mmyyyy, indicating that the owner of the domain in the URL agreed
> to its use as a label around that date and (b) should be de-referencable,
> yielding an informative resource about the naming convention.
> Note that this use of URIs with fragments also closely matches RDF (see
> <http://www.w3.org/TR/rdf-concepts/#section-fragID>).
> Note that for some container files, the format parameter can also carry an
> extended MIME type to document this; see [RFC 4281] for one such instance.
>
>
>
> duration 				(attName="duration", attValue="Double") 						[NO change]
> format 					(attName="format", attValue="URI" | "String") 			[CHANGED]
> samplingRate 		(attName="samplingRate", attValue="Double") 			  [NO
> change]
> frameRate 			(attName="frameRate", attValue="Double") 						[NO change]
> averageBitRate 	(attName="averageBitRate", attValue="Double") 	    [NO
> change]
> numTracks 	  { (attName="number", attValue="Integer"), (attName="type",
> attValue="String")? } [NO change]
>
>
>
>
> Change the Statement before the table as follows ... in 5.1.1 Description
> of the approach followed for the property definitions
>
>
>
> The following syntax is used for the type descriptions:
>
>     *   ( ) (parentheses) are used to indicate a attribute/value pair
>     *   | (vertical bar) is used to indicate a choice between different
> values
>     *   { } (curly brackets) are used to define a complex type, i.e., a
> tuple of attribute/value pairs
>     *    ? (question mark) is used to indicate an optional element
>
> contributor 	{ (attName="contributor", attValue="URI" | "String"),
> (attName="role", attValue="URI" | "String")? }
> is interpreted as a complex type that has two elements.
> The first identifies the contributor of a media resource by using a URI or
> a string.
> The second specifies an optional role, which is defined by a string.
> Elements are comma separated, and the collection of elements that makes up
> the complex type is enclosed in curly brackets.
>
>
> Change the compression example to ....
> @@@ TBD
>
>
> --
> Thierry Michel
> W3C
>
>


-- 
Thierry Michel
W3C
Received on Tuesday, 15 February 2011 21:17:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 15 February 2011 21:17:17 GMT