dbXML has autolinking which is pretty much a combination between XInclude and XLink. It's just an experimental feature though and has issues in relation to the current API. It's also of course specific to dbXML and ties the inserted documents to our server. Overall we don't recommend people use this because of that. I still believe the functionality is valuable though and a more interoperable mechanism will need to be developed.
Tamino also has a schema based way of doing linking but that is even less XLink like then dbXML's autolinking.
Beyond that I'm not aware of any other products that have anything similar.
Kimbro,
Excelon's XML platform also has an experimental linking facility. As with XLink, an element is recognized as a link by the presence of an attribute with a certain namespace URI and local name. The value of the attribute is a relative or absolute pathname to another XML document. So far, we do not support fragment identifiers, so a link target can only be a document root. When a link is recognized, DOM and XPath operations behave as if the link element (and its attributes and descendents) were replaced by the document element of the target document (and its attributes and descendents). With respect to indexes and to query, update, or XSLT operations, documents together with their link targets are treated as if they were single documents.
By default, link traversal is automatic. DOM and XPath extensions are provided to disable link traversal.
Although this feature has caused more than its share of implementation headaches, it is very widely used by our customers. The most common use is for binder documents, in which all children of the document element are link elements, and for which special API support is provided. But some customers are using raw links to create their own document structures.
Paul
On Monday, July 23, 2001, at 05:18 PM, Ronald Bourret wrote:
Kimbro Staken wrote:On Monday, July 23, 2001, at 08:39 AM, Jeremias Maerki wrote:- Discussion about how to do linking (using XLink). First, define requirements, then define API and finally do experimental implementations.
This seems like a separate project. Do you really see it being part of the API?
Do any XML databases support XLink yet? I'm not aware of any, although many have talked about it. Putting XLink into the interface may be premature, although we might be able to drive development this way.
-- Ron ---------------------------------------------------------------------- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Contact adminstrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ ----------------------------------------------------------------------
Kimbro Staken The dbXML Project htttp://www.dbxml.org ---------------------------------------------------------------------- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Contact adminstrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ ----------------------------------------------------------------------
---------------------------------------------------------------------- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Contact adminstrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ ----------------------------------------------------------------------
