putting rdf in html won't pass vaildation?

[Zhang Weiwu]

Hello. I just read a article "rdf in html: approaches" at
"http://infomesh.net/2002/rdfinhtml" (guided by google).

Looking into the "Embed XML RDF Part II: Embrace Validation" part, there
are an example DTD and xhtml page. I don't know much about xhtml
Modularization, but I think this example should be workable in
cut-and-paste fashion for newcomers to use. In fact I copied the example
xhtml file into my website, it won't pass validation. Here is the error
message:

I was not able to extract a character encoding labeling from any of the
valid sources for such information. Without encoding information it is
impossible to validate the document.

And if I add this line of character encoding info (which I often use)
before the example xhtml page:
<?xml version="1.0" encoding="utf-8"?>
I still get error messages at
http://validator.w3.org/check?uri=ht...et%2Ftest.html
which looks like this:

# /Line 9
<http://validator.w3.org/check?uri=http%3A%2F%2Faliweekly.nease.net%2Ftest. html#line-9>,
column 8/: document type does not allow element "RDF

|<rdf:RDF>|
^

# /Line 10
<http://validator.w3.org/check?uri=http%3A%2F%2Faliweekly.nease.net%2Ftest. html#line-10>,
column 24/: there is no attribute "RDF

|<rdf:Property rdf:about="http://purl.org/net/swn#homepage">|

[snip]

Any suggestions to make it validate? Thank you.

[Nick Kew]

In article <bo**********@mail.cn99.com>, one of infinite monkeys
at the keyboard of Zhang Weiwu <we********@hotmail.com> wrote:

Hello. I just read a article "rdf in html: approaches" at
"http://infomesh.net/2002/rdfinhtml" (guided by google).
Ah, that's a new one to me. I thought Sean's basic answer to that
question was "don't", but you've found a longer one.
Looking into the "Embed XML RDF Part II: Embrace Validation" part, there
are an example DTD and xhtml page.
The difficulty with that approach is you cannot define a generic DTD
for RDF. You have to look at the structure of the particular RDF
you're using and define a module around it.

I played with rdf-in-html about two or three years ago, but nowadays
the only approach I use is <link> to the Metadata.
I don't know much about xhtml
Modularization, but I think this example should be workable in
cut-and-paste fashion for newcomers to use.
Do read Sean's Conclusions section carefully!
I was not able to extract a character encoding labeling from any of the
valid sources for such information. Without encoding information it is
impossible to validate the document.
That's nothing to do with RDF. Read the FAQ.
Any suggestions to make it validate? Thank you.

I'd recommend <link ...>

One point he misses is the different content model for <script> in
HTML (CDATA) and XHTML (#PCDATA) - meaning that it "works" in HTML
but not XHTML. Not that I'd recommend it either way.
See <http://ilrt.org/discovery/chatlogs/rdfig/2003-11-03.html#T04-59-34>
--
Nick Kew

In urgent need of paying work - see http://www.webthing.com/~nick/cv.html

[Henri Sivonen]

In article <bo**********@mail.cn99.com>,
Zhang Weiwu <we********@hotmail.com> wrote:

Looking into the "Embed XML RDF Part II: Embrace Validation" part, there
are an example DTD and xhtml page. I don't know much about xhtml
Modularization, but I think this example should be workable in
cut-and-paste fashion for newcomers to use.
If you don't use one of the XHTML 1.0 DTDs, your XHTML Family document
should be served as application/xhtml+xml, not as text/html.

Why are you putting RDF in XHTML? What are you trying to achieve?
In fact I copied the example
xhtml file into my website, it won't pass validation.
You test file isn't even a well-formed XML document, so it cannot be
valid XML.

Also, http://infomesh.net/2002/m12n/test/rdf.txt is delivered as
text/plain.
I was not able to extract a character encoding labeling from any of the
valid sources for such information. Without encoding information it is
impossible to validate the document.
You don't advertise the character encoding in the Content-Type HTTP
header and you are using a text/* type instead of an application/* type.
Any suggestions to make it validate?

Why do you want to make it validate? RDF doesn't belong in XHTML 1.1 or
XHTML 1.0. What's the benefit of getting a document to validate, if in
order to validate, you have to make the DTD conform to the document and
not vice versa?

--
Henri Sivonen
hs******@iki.fi
http://iki.fi/hsivonen/
Mozilla Web Author FAQ: http://mozilla.org/docs/web-developer/faq.html

[Jim Ley]

On Mon, 03 Nov 2003 08:43:05 +0200, Henri Sivonen <hs******@iki.fi>
wrote:

Why do you want to make it validate? RDF doesn't belong in XHTML 1.1 or
XHTML 1.0.

If RDF doesn't belong in XHTML 1.1, what's the point of XHTML 1.1 ?

Jim.
--
comp.lang.javascript FAQ - http://jibbering.com/faq/

[James Pickering]

The W3C provides an RDF Validation service .....

http://www.w3.org/RDF/Validator/

...... for external/linked RDF documents.

James Pickering
http://www.jp29.org/

[Henri Sivonen]

In article <3f**************@news.cis.dfn.de>,
ji*@jibbering.com (Jim Ley) wrote:

If RDF doesn't belong in XHTML 1.1, what's the point of XHTML 1.1 ?

If SVG doesn't belong in XHTML 1.1, what's the point of XHTML 1.1 ?
If MathML doesn't belong in XHTML 1.1, what's the point of XHTML 1.1 ?

I guess the point of XHTML 1.1 is to provide an example that demostrates
how XHTML DTD modules can be combined and a reference point for
constructing extended DTDs. Such extended DTDs are not equal to the
XHTML 1.1 DTD, though, and documents authored according to such an
extended DTD are not strictly conforming XHTML 1.1 documents.

I think there's little (if any) value in extending the XHTML 1.1 DTD in
order to please the W3C validator. There might be some value in using a
custom DTD internally in server-side system in order to catch bad
output--that is, in order to discover bugs in the software generating
the output. However, considering the issues with namespaces and DTDs, a
Relax NG schema might be better suited for such purpose.

--
Henri Sivonen
hs******@iki.fi
http://iki.fi/hsivonen/
Mozilla Web Author FAQ: http://mozilla.org/docs/web-developer/faq.html