RE: Some comments on the requirements

Hi - comments inline :

At 11:44 05/02/2003 +0000, you wrote:

>Bert Bos wrote some comments on the requirements...
>
> > 2 Have a valid XML representation
>Have to agree - an XML representation might bring advantages - but it should
>not be a pre-requisite. Would it be possible to have an XML representation

External namespace support should be mandated.

BTW, SMIL2 supports this, so that for example display extensions can be 
loaded by SMIL viewers (though currently only real player has a useful 
implementation of this).

http://service.real.com/help/library/guides/realone/IntroGuide/HTML/htmfiles/smilsynx.htm 
(Search down for "RealNetworks Extension Namespace")

>(with external documents?) that has a streamable format that is more
>efficient and elegant than its XML representation?

??? Can you explain this more John - I don't get what you just said :-)

The reduced format would be derivable from the XML format by using XSL to 
transform the document into whatever format was requested by the client.

> > 8 Allow the language of the text to be identified using xml:lang
>If the representation is XML - then XML should be fully utilised - but TT
>should IMHO support multiple language streams.

But not *require* them I would have thought.

> > 11 Have a default UNICODE font
>
> > Is it really a requirement to have a standard font? What font
> > would that be? Arial? Maybe the intention was to require that the
> > format supports all Unicode characters, rather than a specific font?
>
>Somewhere in the charter it says that font is something to be left out of
>TT. TT should require support for Unicode **characters**.

This is a function of the encoding used in XML documents, and is specified 
in the document declaration on the 1st line of conforming XML documents.

>Could motion be part of the style rather than the text?

*All* display attributes should be external to the document IMO.

This could do with  including positioning (% of display height and width 
for example) for open caption devices. All of this sort of thing can be 
specified in css by linking the stylesheet to the document.

>Absolutely, though it would be nice to be able to transfer glyphs that have
>no unicode representation by some mechanism within TT (e.g. trademarks and
>logos). Could this be by private data inclusion? Reference to external
>streams?

I think theres a data: url scheme which might work for some small snippets. 
Anybody got other ideas ?

Cheers,
Neil Smith.

Received on Wednesday, 5 February 2003 09:00:08 UTC