W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > October 2001

Re: use cases for Literal? RSS? Dublin Core? PRISM? DAML? XAP?

From: dehora <dehora@eircom.net>
Date: Sun, 14 Oct 2001 09:35:31 +0100
To: <w3c-rdfcore-wg@w3.org>
Message-ID: <011f01c1548b$2fe1d080$01000001@MITCHUM>

>> Dan Connolly:
No, I think the tests are fine; the spec is just sloppy.

You'll have to do better than this. XML well formedness is one of the
few areas surrounding literals where the M&S is neither sloppy nor
ambiguous. The refactoring syntax draft also insists upon well
formedness; it's not sloppy on this point either. Please don't assume
that the tests and specifications can stand in isolation. As things are
I can code two different behaviours against the body of work. That
wastes everyone's time, hurts interop, slows adoption; it's hardly

Think the spec is wrong? Then propose to kill the well formedness
constraint in view of implementation feedback. The best place to exact
that change is in the refactoring syntax draft, you'll find text to that
effect below. 

Think the tests are wrong? Then propose to change the tests to reflect
the M&S and the refactoring syntax draft. You'll find text to that
effect below.



remove the well formedness constraint from to allow certain rdf tests to
stand. Please be aware that this change allows XML literal fragments to
be non-well formed.

Old text: Section 3.1

"6.34 literal any well-formed XML "

new text:

"6.34 literal any XML"

Old text: section 4.20

"4.20 Production literal (was 6.34 literal)
Any non-empty well-formed XML."

New text:

"4.20 Production literal (was 6.34 literal)
Any non-empty XML."


Change the rdf literal tests and errors to be consistent with both the
M&S and the refactoring syntax draft. Add a surrounding element pair
<em></em> to each free text literal element content. Add another error
file without a surrounding element pair and indicate that this should
not generate a triple.
Received on Sunday, 14 October 2001 04:37:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:24:05 UTC