Bill de hÓra wrote:
Julian Reschke wrote:
Graham wrote:
On 2 Aug 2005, at 10:07 am, Bill de hÓra wrote:
The design intent of character-by-character cmp as I understood was for
the URI contained by the element. I think confusing the element content
with the URI is a spec bug.
From atompub-format-10, 4.2.6: "Its content MUST be an IRI"
That to me is demonstrates a very clear intention of the working
group that the content must be exactly equal to the IRI. Changing
this to allow whitespace would represent a major technical change to
the format. I will figuratively lie down in the road if anyone
suggests whitespace should be allowed around any machine-read content
(uris, @type, @rel, etc).
+1
A potential enhancement would be to explicitly state that whitespace
*isÜ significant here (and of course to make the feedvalidator check it).
That still leaves things unsaid - significant in what way? What does
"make the feedvalidator check it" entail? And assuming we did this
enhancement how does whitespace square with our MUST be an IRI.
If you put whitespace inside, it's part of the to-be-IRI. As an IRI can
not contain whitespace, it's an invalid IRI.
Somebody please convince me the spec is adequate here; I'm not seeing
it. I'm feeling an urge to go through all the elements for any other
machine readable tokens living inside element content and filing bugs
against the lot of them. Then I'll do the same with APP constructs like
'draft'.
Seems that the spec may need to define once what it means to say that
the content of an element must be something specific, such as an IRI.
Best regards, Julian
