Re: ISSUE-4 - versioning/DOCTYPEs

CE Whitehead, Fri, 21 May 2010 16:50:32 -0400:
>> Henri Sivonen, Thu, 20 May 2010 05:57:41 -0700 (PDT):
>>> "Leif Halvard Silli" <xn--mlform-iua@målform.no> wrote:

>>>>> What KompoZer and NVu do is not a use case.
>>>> 
>>>> The use case is "an in-document and editor independent signal to
>>>> create polyglot HTML5".
>>> 
>>> I meant what [ARE] you are trying to accomplish that can be helped by 
>>> having an in-band indicator for requesting polyglot output from an 
>>> editor.
>>
>> […] read it as if you asked why, given the existence of a
>> polyglot syntax, there also is need for a indicator for this syntax.
>> 
>> The purpose of something that signifies a certain encoding, is of 
>> course standardization around that encoding. By inserting the polyglot 
>> syntax indicator, one indicates what coding flavor to use. It is very 
>> irritating if you seek to follow a certain standard, and then suddenly, 
>> gets your standardized documents converted into another standard, by a 
>> tool which didn't know that you tried to follow another standard than 
>> the default one - because you were only using a indicator that was only 
>> a private indicator. 
>
> … do you want to spell out to the ways to indicate the various 
> standards and nothing more?

Do I want the polyglot spec to say (aka 'spell out') how one can 
indicate that the document is supposed to follow the polyglot syntax 
rules? Answer: Yes. 

I suppose the alternative to "yes, this is all I want" is "no, I also 
want to settle how to solve the fundamental versioning problem - to 
leave open a way to indicate that a document is written in a new 
version of HTML - including a new version of polyglot HTML".

Answer: Right now, all I want is to have a way to indicate that the 
document follows the polyglot syntax rules.
-- 
leif halvard silli

Received on Friday, 21 May 2010 21:16:00 UTC