Re: XLink 1.1, let's get the party started

/ John Cowan <jcowan@reutershealth.com> was heard to say:
| Norman Walsh scripsit:
|
|> I believe anyElem has to allow simple|extended, otherwise after you
|> get into the "anyElem" branch, you can never get back out.
|
| In fact we don't want to be able to get out, because XLink 1.1 doesn't
| support links inside links.

Really? Consider the case of simple links, the XLink text seems very
carefully worded:

  The simple-type element may have any content. The simple-type
  element itself, together with all of its content, is the local
  resource of the link, as if the element were a resource-type
  element. If a simple-type element contains nested XLink elements,
  such contained elements have no XLink-specified relationship to the
  parent link.

By my reading, this text does not prohibit:

<para xlink:href="http://example.org/paragraph">Some
text with a <emphasis xlink:href="http://example.org/emphasis">nested</emphasis>
link.</para>

It only says that the nested xlink:href has no relationship to the
outer xlink:href.

I don't think XLink 1.0 forbids nested links and I don't believe that
we want XLink 1.1 to do so.

| But there are other problems: in particular,
| currently I don't allow the root to be a link.  Here's a revised
| definition clearly separating "foreignElem" and "anyElem".

Hmm. I thought I found a valid document that your schema rejected, but
I can't reproduce the problem. Maybe the document wasn't valid. :-)

| (Editorial note: grep your draft for "Xlink-specified relationship";
| there are still some of those left, like the one in the third graf of
| 5.1.1, which should say that a resource element with other XLink elements
| inside it is not conformant.)

I'm not sure those are incorrect.

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc.
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.