Altova Mailing List Archives


Re: Associating DSSSL style sheets with documents

From: "Eve L. Maler" <elm@---------.--->
To: James Clark <jjc@------.--->
Date: 3/14/1997 6:14:00 PM
At 10:57 AM 3/11/97 +0700, James Clark wrote:
>At 12:24 10/03/97 EST, lee@s... wrote:
>>Of course, it'd have to be
>><?XML-STYLE ....?>
>>for XML, no?
>
>Well, this is something that is applicable to SGML in general not just to
>XML. Since <?xml-stylesheet is no more reserved than <?stylesheet in SGML, I
>would rather use simply <?stylesheet for SGML.  A general-purpose SGML
>browser should probably make the keyword user configurable.

This is interesting: Should an XML effort determine a PI that should be
usable in general by SGML documents?  I tend to think that the "authority"
that invents/maintains the format of the PI should be identified, and "XML"
sort of fits the bill, similarly to <?SO.  We did say that the first name
token in a PI functions as a sort of notation.  It would be weird for an
XML spec to specify <?stylesheet .

I've also been beating the drum on the WG list about how our PIs should
have "GIs" as well as "attribute specs," so I'd prefer to see <?XML
stylesheet att1="val1" att2="val2"... ?>.  This way, "<?XML" targets the PI
so that it will be processed by an XML-aware processor, and the rest
identifies the semantics of the instruction.

        Eve

xml-dev: A list for W3C XML Developers
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To unsubscribe, send to majordomo@i... the following message;
unsubscribe xml-dev
List coordinator, Henry Rzepa (rzepa@i...)

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.