- From: Daniel Veillard <daniel@veillard.com>
- Date: Sat, 9 Jul 2005 12:57:02 +0200
- To: Bjoern Hoehrmann <derhoermi@gmx.net>
- Cc: daniel@veillard.com, www-xml-linking-comments@w3.org
On Sat, Jul 09, 2005 at 12:49:49PM +0200, Bjoern Hoehrmann wrote: > * Daniel Veillard wrote: > >In general is sounds unwise to try to add to XLink behaviour expectations > >about all the upper layers which may interract with XLink defined linking > >constructs. The level of recognition an processing applied by other layers > >can't be put within XLink, it would make XLink conflict with the specification > >of those application layers or the evolution of them over time. > > If someone implements a XML 1.0 + CSS + XLink 1.1 user agent there are > basically just three specifications that can define the rules here. If > it's a bad idea to make such a user agent, this needs to be clear from > XLink 1.1, if not there need to be clear processing rules. How the XML > Core Working Group achieves this is of less concern to me. Then you have your answer, CSS says "link" and XLink-1.1 defines links, so :link applies to links defined by XLink-1.1 constructs. That's my answer not the XML Core WG one. Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel@veillard.com | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ |
Received on Saturday, 9 July 2005 10:57:03 UTC