Re: spec bug: can we fix for draft-11?

Using Sun's 'relames' [1] it is *nearly* possible to validate an instance as is intended by the text! Where (datetime for instance) an element content must not have whitespace, relames picks it up nicely. There must be no white space before or after a date time value

Re: spec bug: can we fix for draft-11?

On Thu, 2005-08-04 at 09:31 -0700, Tim Bray wrote: > > I'm getting increasingly grumpy and "just fail" is looking better and > better. > So for now, I'm -1 on an weakening or removing "The element's content > MUST be an IRI" or analogous text in any other section. I'll stop > shouting if

Re: spec bug: can we fix for draft-11?

On Thu, 2005-08-04 at 17:45 +0200, Danny Ayers wrote: > > I don't want to allow whitespace. But this > > > > > > urn:foo > > > > > > is going to happen, is going to cause problems, and working around it > > does not strike me as being something you can foist entirely onto the > > spec's end

Re: spec bug: can we fix for draft-11?

On Tue, 2005-08-02 at 19:11 +0200, Bjoern Hoehrmann wrote: > For RFCs see . Thanks. Just playing. With schema The example below parses well with James Clarks relax tools and the sun validator. http://www.example.com";> http://exam

Re: spec bug: can we fix for draft-11?

On Tue, 2005-08-02 at 15:24 +0100, Bill de hÓra wrote: > Sam Ruby wrote: > > > Even if we decide that whitespace is not significant, I do believe that > > having the feedvalidator issue a warning in such cases is appropriate. > > +1 What is the IETF version of an errata sheet? Is that the right

Re: Feed History -02

On Sat, 2005-07-23 at 09:14 -0700, Mark Nottingham wrote: > > Archives *should not* change. I think any librarian will agree with > > that. > > I very much agree that this is the ideal that should be striven for. > The underlying problem, I think, is that different feeds have > different s

Re: Notes on the latest draft.

On Thu, 2005-07-21 at 11:17 +0100, Graham wrote: > On 21 Jul 2005, at 4:43 am, James Cerra wrote: > > > In an XSLT-based Atom-to-XHTML processor, that is a large cost when > > HTML > > includes many many many entities. At least, I think so and have > > ignored the > > problem because I can't

Re: Atom 1.0 xml:base/URI funnies

If anyone comes to a definitive conclusion on this, would they post to the list, or a website please. TIA -- Regards, Dave Pawson XSLT + Docbook FAQ http://www.dpawson.co.uk

Re: RNG validators capable of fully using the Atom schema?

On Tue, 2005-07-12 at 12:16 -0400, Norman Walsh wrote: > / Henri Sivonen <[EMAIL PROTECTED]> was heard to say: > | I'm wondering which validator was used for testing the Atom > | RNG+Schematron schema. Which validators support Compact Syntax with > | embedded Schematron? I am particularly interest

Re: RNG validators capable of fully using the Atom schema?

terested in Java solutions. > > http://www.topologi.com/products/validator/ is said to support it. I used Norm's relax-ng schema + msv. Seems good to me? http://www.dpawson.co.uk/nodesets/nodesets.xml You tell me if it's bad[==invalid] The spec doesn't ... in language I underst

Re: Clearing a "discuss" vote on the Atom format

On Fri, 2005-07-01 at 16:13 -0400, Sam Hartman wrote: > Paul, two points. > > For me to be happy, your specification must mandate that xmldsig be > used whenever encryption is used. > > As a consequence of this and your decision not to support MACs, then > in order to encrypt a document, you mus

Re: FWD: I-D ACTION:draft-nottingham-atompub-feed-history-00.txt

On Wed, 2005-06-29 at 15:03 +0200, Thomas Broyer wrote: > Dave Pawson wrote: > > Any one site could now have n instances, each being a feed, the only > > variant (apart from entries) being the links to previous feeds. > > If I'm to say *this* is my feed, I guess

Re: FWD: I-D ACTION:draft-nottingham-atompub-feed-history-00.txt

keeping all entries in one feed. It won't take long for the instance to become significant in size. -- Regards, Dave Pawson XSLT + Docbook FAQ http://www.dpawson.co.uk

Re: The atom:uri element

are authors out here too, who need that information. That I believe is the interop issue. -- Regards, Dave Pawson XSLT + Docbook FAQ http://www.dpawson.co.uk

Re: The atom:uri element

lained. Current version, for thicko's|users, like me, is not good. -- Regards, Dave Pawson XSLT + Docbook FAQ http://www.dpawson.co.uk

Re: The atom:uri element

. > > == Proposal == > > Rename the "atom:uri" element or change its type to a Link Construct. I support the rationale for changing. I'd appreciate even more some semantics for the element? Were you going to add those to the proposal? -- Regards, Dave Pawson XSLT + Docbook FAQ http://www.dpawson.co.uk

Re: More on Atom XML signatures and encryption

explicitly' don't you grok? -- Regards, Dave Pawson XSLT + Docbook FAQ http://www.dpawson.co.uk

Re: feed or entry

On Thu, 2005-06-16 at 12:09 -0700, James Cerra wrote: > Dave Pawson, > > > I'm not having much luck working > > out how I can write (daily or there abouts) > > an entry, without having to duplicate > > feed metadata. > > I don't follow. Could you g

feed or entry

I'm not having much luck working out how I can write (daily or there abouts) an entry, without having to duplicate feed metadata. Am I alone in this? Xinsert isn't common yet.. is it? -- Regards, Dave Pawson XSLT + Docbook FAQ http://www.dpawson.co.uk http://www.dpawson.co.uk/blog/