[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Low-hanging fruit: compulsory namespaces



/ Bill de hÓra <bill@xxxxxxxxxx> was heard to say:
| Tim Bray wrote:
|
|> I went back and reviewed the examples, and I totally disagree.  They
|> really are the same, and any chain of processing software that makes
|> them come out different is severely buggy, and I don't think
|> bugginess at that level is prevalent in widely-used XML-processing
|> tools.
|
| Ok, I won't dispute that re deployed processor behaviour. But I went
| back and reread the 1.1 Namespaces spec today and I didn't see where
| behaving the way you and Norm say they should not is considered a
| processing error. Seriously, did I miss it?

I'm not actually sure what you're asking. Given this document

  <atom:feed xmlns:atom="http://example.org/atom";>
    <atom:content mode="xml">
      <no-ns>Non-namespaced element</no-ns>
    </atom:content>
  </atom:feed>

What transformation do you think should be valid that you believe
I think is not valid?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@xxxxxxxxxx> | In great affairs men show themselves as
http://nwalsh.com/            | they wish to be seen, in small things
                              | they show themselves as they are.--
                              | Chamfort

Attachment: pgp00132.pgp
Description: PGP signature