Re: XLink 1.1: Error handling

/ Bjoern Hoehrmann <derhoermi@gmx.net> was heard to say:
| * Norman Walsh wrote:
|>This link does not conform to XLink:
|>
|>  <someElement xlink:type="foobar">foo</someElement>
|>
|>Nor does this one:
|>
|>  <someElement xlink:show="foobar">bar</someElement>
|>
|>Those elements don't conform to 3.2 and therefore per my earlier
|>suggestion:
|>
|>  Would the following rewording of point 3 of Section
|>  3.3 make things clearer?
|>
|>  3. it applies XLink semantics only to those elments which satisfy
|>     the markup conformance criteria outlined in [3.2 Markup Confromance].
|>
|>those elements would not have XLink semantics.
|
| Well, you said that in XLink 1.0 error handling is implementation-
| defined and that the WG rejects my request to define error-handling
| in XLink 1.1; the text above does define error handling, so I'm not
| really sure what the Working Group's response might be here.

Perhaps I'm being inconsistent, but I don't think so. I'm reluctant to
try to define error handling behavior, to try to say what XLink
processors should/may/must do with markup that doesn't conform to
XLink (but which looks like maybe it was supposed to).

However, I do think we must say when elements do or do not conform to
the XLink specification. For elements that do conform, the question of
error handling does not arise. For elements that do not conform, all
bets are off and I think we can safely say that the behavior is
implementation defined.

| Could you give an example of markup that involves XLink, does not
| conform to XLink 1.1, but does not trigger the error handling re-
| quirements you propose?

I don't think I'm proposing any error handling requirements. I'm saying
that an element that doesn't meet the criteria of 3.2 Markup Conformance
has no XLink semantics.

                                        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.

Received on Wednesday, 11 January 2006 15:40:36 UTC