[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Notes on draft-hollenbeck-ietf-xml-guidelines-01.txt
Thanks for the comments, Chris. Larry, Marshall, and I have been looking
them over and will do our best to work things in as part of -02. We did
have some thoughts on a few of your thoughts, though:
> 4.5 Namespaces
> "In lieu of such, other permanent URIs can be used, e.g., URNs in the IETF
> namespace (see  and )." That makes me feel uncomfortable, but i
> have articulate arguments right now to clarify the source of discomfort so
> not it here and may get back to it later, or others might.
We're inclined to leave the text as-is in the absence of alternative text.
> 4.5.1 Namespaces and Attributes
> "As described in XML Alternatives there is no standard mechanism in XML
> indicating whether or not new extensions are mandatory to recognize.
> protocol specifications should thus explicitly describe extension
> and requirements to recognize or ignore extensions."
> True in general but there are specific examples of such mechanisms so they
> should be listed here and the advice elsewhere in the document to re-use
> existing mechanisms should be applied here also. I'm thinking of the DOM
> feature tests and the SMIL and SVG requiredFeatures, requiredExtensions
> and test and switch capabilities.
We'd prefer to leave this text as-is instead of attempting to enumerate
extension mechanism options as the purpose of the section isn't to describe
alternatives, but to help ensure that designers explicitly address the issue
> 4.6 Element and Attribute Design Considerations
[long markup options example described]
We're going to rewrite this section, though we don't really want to try to
explain all of the possible ways that an IPv4 address can be represented in
XML. What you see in -02 won't be exactly what you suggested but it'll
hopefully address the spirit of your comments.
> 5. Internationalization Considerations
Again, we're going to try to rewrite this section. The words might not
match yours exactly, but we'll incorporate your thoughts.