Re: New draft: 13-Mar-2001

[Norman Walsh <ndw@nwalsh.com>]

/ Tony Coates <Tony.Coates@reuters.com> was heard to say:
| In the spec, the sentence "In addition, unqualified attributes other
| than the attributes explicitly described in this Specification, are
| reserved for future use." seems to have either one comma to many, or
| one too few.  I would suggest either adding one before "other" or
| removing the one after "Specification".

Ok.

| Also, if our two modes are "prefer system identifier" and "prefer
| public identifier", then having these selected by the "override"
| being "yes" or "no" is just going to be confusing (i.e. "was that
| 'yes' for prefer system, or 'no' ...  I can't remember now ...").
| It would be much easier to understand the document as it stands now
| if there was a "prefer" attribute with values "public" or "system".
| Can we discuss this at today's meeting?

(As you can see, I'm finally catching up on my ER email. I'll revisit
this if I don't find the answer in subsequent email :-)

| With regard to "delegate entries ordered by the length of the start
| string, longest first", how is the length determined?  Characters or
| bytes?  Is "%20" a longer string than " " (i.e. a space)?  Is this
| the issue you were referring to when you wrote "[What about
| differently %-escaped escaped characters? Does RFC 2396 cover
| this?]"?

Yes, that's one aspect.

| Where it says "Elements from other namespaces are are allowed, but
| they are ignored by this specification.", should it say "Elements
| and attributes ...". 

Yes, I think so.

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@East.Sun.COM    | Time wounds all heels.
XML Standards Engineer       |
Technology Development Group | 
Sun Microsystems, Inc.       |