On Thu, 2002-01-17 at 18:32, Graham Klyne wrote:
Well, we now have ways to express other (non-primary) content types.
E.g., per RFC 2912, RFC 2913, ...
Content-Type: multipart/mixed; boundary="break"
Content-features:
(& (Type="text/plain") (Type="image/jpeg") (Type="audio/wav") )
Can we simply say (for an XHTML document also containing SVG, MathML,
SMIL, and XLink):
Content-Type: application/xhtml+xml
Content-features: (&
(xmlns="http://www.w3.org/1999/xhtml")
(xmlns="http://www.w3.org/2000/svg")
(xmlns="http://www.w3.org/1998/Math/MathML")
(xmlns="http://www.w3.org/2001/SMIL20/")
(xmlns="http://www.w3.org/1999/xlink")
)
If so, then we may already be out of the brush, though my reading of RFC
2913 suggests that we would need to add xmlns to RFC 3023's existing
structure.
--
Simon St.Laurent
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!
http://simonstl.com