[Bug 5522] The term "containing element" is not clear

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5522


John Arwe <johnarwe@us.ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |johnarwe@us.ibm.com




--- Comment #8 from John Arwe <johnarwe@us.ibm.com>  2008-06-12 17:59:46 ---
Given an example (to remind everyone of the SML URI syntax)

<foo sml:ref="true">
  <sml:uri>http://www.example.org/someDocument#smlxpath1(/fred)</sml:uri>
</foo>

My _skim_ of 
http://www.w3.org/TR/xml-infoset/#infoitem.character
http://www.w3.org/TR/xml-infoset/#infoitem.element
http://www.w3.org/TR/xml-infoset/#infoitem.attribute
is that the entire URI value
"http://www.example.org/someDocument#smlxpath1(/fred)" is a sequence of one or
more character information items, whose parent is the "<sml:uri>" element
information item.

Thus, as Kumar points out, the current text (which has changed since the bug
was opened due to other bugs) uses terminology that appears to be consistent
with the infoset spec.

It appears though that 4.3.1 SML URI Reference Scheme bullet 1 does refer to
sml:ref as a child of the SML reference element (here, "<foo>") which is
inconsistent with the same spec.  This is true in the Jan, March, and current
editor's draft: 

An SML reference is identified as using the SML URI reference scheme if and
only if exactly one element information item whose [local name]  is uri and
whose [namespace name]  is http://www.w3.org/2008/03/sml is present as a child
of that reference element.

It appears that we would want to change 
from: is present as a child of that reference element.
to  : is owned by              that reference element.

The editors should probably scan both specs (Core, aka SML, being the more
likely) for other instances where attributes are called children, as well.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 12 June 2008 18:00:20 UTC