|Larry Masinter||Sep 23, 1999 12:15 pm|
|Jukk...@hut.fi||Sep 24, 1999 2:45 am|
|Walter Ian Kaye||Sep 24, 1999 10:39 am|
|Arjun Ray||Sep 27, 1999 6:32 pm|
|Harald Tveit Alvestrand||Sep 28, 1999 10:51 am|
|Arjun Ray||Sep 28, 1999 5:02 pm|
|Harald Tveit Alvestrand||Sep 30, 1999 11:41 am|
|Arjun Ray||Sep 30, 1999 11:55 pm|
|Larry Masinter||Oct 4, 1999 1:06 pm|
|Arjun Ray||Oct 4, 1999 9:57 pm|
|Larry Masinter||Oct 5, 1999 6:55 am|
|Arjun Ray||Oct 6, 1999 12:05 am|
|Arjun Ray||Oct 6, 1999 3:29 am|
|Rick Jelliffe||Oct 6, 1999 6:37 am|
|Arjun Ray||Oct 6, 1999 6:39 am|
|Russell Steven Shawn O'Connor||Oct 6, 1999 6:43 am|
|Arjun Ray||Oct 6, 1999 10:18 am|
|Arjun Ray||Oct 7, 1999 10:00 pm|
|Larry Masinter||Oct 8, 1999 2:56 am|
|Jukk...@hut.fi||Oct 8, 1999 3:28 am|
|Arjun Ray||Oct 8, 1999 3:50 pm|
|Subject:||Dropping the Normative Reference to SGML (was: I-D ACTION..)|
|From:||Arjun Ray (ar...@q2.net)|
|Date:||Oct 6, 1999 3:29:30 am|
On Tue, 5 Oct 1999, Larry Masinter wrote:
The one really important fixing it needs is to drop all normative references to ISO8879. [...]
I can note in the revision of the 'text/html' document that current practice on the Internet includes much non-compliant behavior, and that implementors must be prepared to be "bug-compatible" with popular browsers in order to work with many HTML documents on the net.
I don't think this reduces the value of specifying what 'text/html' *should* be, although I agree it makes implementation hard.
There's a further problem here. Whatever text/html should be, it can't be a conforming SGML application. There's a bunch of stuff in the spec that hides behind the fig-leaf of "application convention", an euphemism that's needed *only* to reconcile what is essentially ad hoc practice with SGML requirements.
But there's more. Clause 15 of ISO 8879 deals with Conformance.
: 15.2. Conforming SGML Application : If an SGML application meets the requirements of this sub-clause it : is a conforming SGML application. : : 15.2.1 Application Conventions : A conforming SGML application's conventions can affect only areas that : are left open to specification by applications. : NOTE - Some examples are: naming conventions for elements and entities, : or a content convention that data characters not in the syntax-reference : character set always be entered by references rather than directly. : : 15.2.2 Conformance of Documents : A conforming SGML application shall require its documents to be : conforming SGML documents, and shall not prohibit any markup that this : International Standard would allow in such documents. : NOTE - For example, an application convention could recommend that only : certain minimization functions be used, but could not prohibit the use : of other functions if they are allowed by the formal specification.
Going past the handwaving, the plain intent of Section 7 in the 4.01 spec is to disallow internal subsets. This "application convention" has been in place since RFC 1866 (earlier I cited a usenet post by Dan Connolly specifically emphasizing this point.) However, since ISO 8879 does not afford applications the leeway to prohibit internal subsets, it follows that the letter of the HTML spec automatically disentitles it to be a conforming SGML application. Consequently, the assertion in the Abstract section at the beginning:
| HTML 4.01 is an SGML application conforming to International Standard | ISO 8879 -- Standard Generalized Markup Language [ISO8879].
The normative reference *must* go.