W3C home > Mailing lists > Public > www-svg@w3.org > September 2006

SVG Tiny 1.2 CR2006-08-10: type = "<media/type>" or "<ContentType>"

From: Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de>
Date: Mon, 4 Sep 2006 10:04:00 +0200
To: www-svg@w3.org
Message-Id: <200609041004.01173.Dr.O.Hoffmann@gmx.de>


some comments about type = "<media/type>"

1. the list L.2 Attribute Table it is noted,
that type is of (4.1 Basic Data Types)

But for video, audio and image the 
description is type = "<media/type>"
without a link to 4.1.

For handler (15.5) and script (15.2) it is 
type = "content-type".

I think, the type descriptions should fit
together and a link to 4.1 is helpful, 
if 4.1 has any function. A description
as done for type of image would be
helpful too in 4.1 (including a link
to 'TAG finding Authoritative Metadata').

2. if a hint for the media or content type is 
useful for image, audio, video, handler and script,
why isn't it applicable for a, foreignObject, 
prefetch and animation (if it is possible to
use ofther formats as SVG for animation as
suggested in the mailing list)?
As far as I understand, requiredFormats has
a different meaning as type and it is
often not the correct way to use requiredFormats
instead of type.

3. if it is believed, that the type attribute
has any function, why is it not animatable if
the related xlink:href is animatable? 
It should be enough, if the author can use 
the same timing for the type attribute as
for the xlink:href animation to get a useful
timed format description.

This is related to the comment about video and audio
but it is similar for image too - or if type
is added for a and foreignObject.

The type attribute is maybe not very important, if
the documents are requested form web servers always
sending any content types with higher priorities,
but it is maybe important for applications on the
local file system, for example for SVG games or
conference presentations or if there is no further 
information from the webserver.
And animation of the xlink:href and type attributes 
will get very important soon, if authors want to 
realise slide shows, music boxes or video boxes with 
interactivity and declarative animation.

4. something related for video and audio
(I have not much experience with video and 
audio productions, but related problems occur 
sometimes, if I try to view videos from internet): 
Wouldn't it be useful too to have something 
similar as type or requiredFormats for the 
used codecs? For example something like 
typeCodecs and requiredCodecs?
Probably to late for SVG Tiny 1.2 but nice for 
the Full profile just to avoid downloading 
multimedia containers with codecs not usable
for the viewer.

Best wishes
Received on Monday, 4 September 2006 08:12:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:09 UTC