Re: draft-freed-sieve-in-xml status?
2009-01-07 10:09:45
Alexey Melnikov writes:
If we want to allow for magic comments, it make sense for them to be
in a separate namespace. But then magic comments are typically
implementation specific. So I unless we want to startadize them, I
don't think the document needs another namespace.
Each generator may want to use a namespace of its own for its particular
foo. I am not an expert in this. If that's considered good XML taste,
then that should be illustrated in an example or two.
Arnt
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: draft-freed-sieve-in-xml status?, Robert Burrell Donkin
- Re: draft-freed-sieve-in-xml status?, Ned Freed
- Re: draft-freed-sieve-in-xml status?, Alexey Melnikov
- Re: draft-freed-sieve-in-xml status?, Arnt Gulbrandsen
- Re: draft-freed-sieve-in-xml status?, Alexey Melnikov
- Re: draft-freed-sieve-in-xml status?,
Arnt Gulbrandsen <=
- Re: draft-freed-sieve-in-xml status?, Kjetil Torgrim Homme
- Re: draft-freed-sieve-in-xml status?, Ned Freed
- Re: draft-freed-sieve-in-xml status?, Cyrus Daboo
- Re: draft-freed-sieve-in-xml status?, Robert Burrell Donkin
- Re: draft-freed-sieve-in-xml status?, Ned Freed
- Re: draft-freed-sieve-in-xml status?, Robert Burrell Donkin
- Re: draft-freed-sieve-in-xml status?, Ned Freed
- Re: draft-freed-sieve-in-xml status?, Aaron Stone
- Re: draft-freed-sieve-in-xml status?, Ned Freed
- Re: draft-freed-sieve-in-xml status?, Arnt Gulbrandsen
|
|
|