Robert Sayre wrote:
[snip: an example with mixed XHTML and MicroSoft stuff]
Thank you, Asbjørn: this is a delightful little problem. You see, XHTML
validity is specified in terms of DTDs. Near as I can tell, that example
and some of the XHTML examples in the spec are 'invalid' because the
Anne van Kesteren wrote:
Norman Walsh wrote:
| XHTML 2 does have a different namespace.
Ouch. I had forgotten or failed to notice that.
Yeah, using namespaces for versioning sucks...
I don't have any. I'll tailor my content to suit what the major
vendors support, just like I do with my plain old
On Apr 14, 2005, at 10:07, Thomas Broyer wrote:
[1] http://www.w3.org/TR/xhtml1-schema/
For the record, James Clark has made Relax NG schemas for some flavors
of XHTML 1.x. Surely James Clark is at least as good an authority as
the W3C. :-)
http://www.thaiopensource.com/relaxng/xhtml/
--
Henri
On Thursday, April 14, 2005, at 06:04 AM, Bill de hÓra wrote:
I don't think is comes under the category of namespaces for versioning
problem. We made this problem ourselves, due to the consensus view
that says default namespaces are so valuable we have the bake an
inverted dependency into
Henri Sivonen wrote:
On Apr 14, 2005, at 10:07, Thomas Broyer wrote:
[1] http://www.w3.org/TR/xhtml1-schema/
For the record, James Clark has made Relax NG schemas for some flavors
of XHTML 1.x. Surely James Clark is at least as good an authority as the
W3C. :-)
This a far less exotic dangerous tags example for
PaceRecommendPlainTextContent:
content type=xhtml
div xmlns=http://www.w3.org/1999/xhtml;
img src=W.png alt=W class=drop-cap /e are offering a
15 img src=euro.png alt=euros / rebate on our last product!
/div
/content
Said that,
Bill de hra wrote:
If there is not a tidy way out of this, or we don't just agree to
scope it as a point solution for a particular flavour of XHTML, I
suggest we revisit the xhtml:div approach altogether.
Bill, I don't think the problem is exclusive to the outer div. I can't
find any version of
...back in town, and ready to express opinions...
Thomas Broyer wrote:
Bob Wyman wrote:
Robert Sayre wrote:
You can point to an alternate feed like this
link rel=alternate type=some/feed href=... /
Of course, you can't have two alternates with the same media type...
Yes, you can point to an
Robert Sayre wrote:
I can't find any version of XHTML that allows xh:p/ where xh is
bound to the XHTML namespace URI.
!DOCTYPE xh:div PUBLIC -//W3C//DTD XHTML 1.1//EN [
!ENTITY % NS.prefixed INCLUDE
!ENTITY % XHTML.prefix xh
]
xh:div xmlns:xh=http://www.w3.org/1999/xhtml; xml:lang=en
This
Bill de hÓra wrote:
while I do realize that XML in XML tends be a broader problem that just
Atom, one counter-example on prefixed Atom+XHTML not working would
probably shut me up.
I'm not looking to shut you up, but I thought I'd do some experiments.
The two feeds below are identical (save
Klotz, Leigh wrote:
I think that casting this problem as XML-in-XML is a problem in itself,
It's a problem, but I don't see as casting. But like I said, if that's
not the technical problem, I'll gladly shut up. If it is, we could do
worse than be cognizant as to what we're working around.
and
11 matches
Mail list logo
