> >Why does the DTD make the xlink:href attribute on the simple element > >REQUIRED, when 5.2 specifically allows this? It makes the link > >untraversable, but so would an extended link with fewer than two > >resources, yet the DTD does not disallow this. > You're right. It should be #IMPLIED. I think I cut and pasted (blush). But the intro to the DTD says that "only constructs that have XLink-defined meaning are allowed." What's the XLink-defined meaning of a simple-type element with no href? Is the DTD trying to allow only "traversable" constructs? The comment below the location element seems to imply this--thus the reason for requiring href and label. Curiously, though, the label attribute is not required on resource. Are inline resources considered automatically traversable? Without a label, I don't see that it's possible to refer to a resource from an arc-type element. I understand that the DTD is non-normative but I'm trying to understand what an XLink-aware processor should be reporting to an application. An XLink infoset would be really nice. Jason Diamond http://injektilo.org/Received on Thursday, 18 January 2001 11:58:34 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:39:41 GMT