[no subject]

["Eddie Arthurs" <EArthurs at golegacy.com>]

 This is the same meaning, but by saying MUST NOT, clients who do
 depend on the server for referential integrity will be considered
 non-compliant whereas without those words, some could argue that
 non-dependence is not a requirement as specified by section 3.
 Similar cases could probably be made for other sections in the
 draft.


Section 7.10.  Fetch Namespace Bindings

 A slight grammatical correction:

   If a client wishes to insert an element or attribute into a document,
 > and that element or attribute is part of a namespace declared
   elsewhere in the document, the client will need to know the namespace

 The following discussion outlines why I feel the handling of
 namespaces as defined in this draft will surprise people who are
 used to XML namespaces.

 Namespace prefixes are shorthand for the full namespace
 specifications.  The handling of namespace prefixes in this draft
 seems to be out of step with the expectations that someone
 conversant in XML would have.

 For example, if I have the following snippet of XML,

 <root-element xmlns:ns1="some:url"  xmlns:ns2="some:url">
  <ns1:sub-element/>
  <ns2:sub-element/>
 </root-element>

 then the XPath expression "//ns1:sub-element" should select two
 elements.  The XPath expression "//ns2:sub-element" should select
 the same two elements.

 From http://www.w3.org/TR/REC-xml-names :

 Section 1. Motivation and Summary

  The prefix, which is mapped to a URI reference, selects a
  namespace. The combination of the universally managed URI namespace
  and the document's own namespace produces identifiers that are
  universally unique.

 Section 3. Qualified Names

  Note that the prefix functions _only_ as a placeholder for a
  namespace name. Applications should use the namespace name, not the
  prefix, in constructing names whose scope extends beyond the
  containing document.

 (end of quoting from REC-xml-names)

 The two sections use two different names for the same things:
 namespace name and URI reference.  This is evident by looking
 through section 2.

 To comply with the XML Namespace spec, The server MUST be able to
 translate the namespace prefixes specified by a client PUT or DELETE
 request to the namespace names (or URI references) used internally
 in the server's document that is being modified.

--
James Smith <JGSmith at TAMU.Edu>, 979-862-3725
Texas A&M CIS Operating Systems Group, Unix

_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf