W3C home > Mailing lists > Public > www-xml-linking-comments@w3.org > April to June 2001

uniqueness constraint on arcs in extended links

From: Vun Kannon, David <dvunkannon@kpmg.com>
Date: Tue, 19 Jun 2001 10:53:23 -0400
Message-Id: <53A3C10BA714D511BA9300805FA7FB2A01B5D86E@usmnyexc05.us.kworld.kpmg.com>
To: "'www-xml-linking-comments@w3.org'" <www-xml-linking-comments@w3.org>
	The XLink spec says that arcs in extended links must be unique over
the pair (from, to). It is as if the arcs were rows in a relational
database, and (from, to) was the key. I think it would be helpful if the key
was variable, to include user attributes and especially arcrole. In my
application of XLink for the next version of XBRL (Extensible Business
Reporting Language), there are many times when two locators are joined by
several arcs with different arcroles. The way the spec is written today, I
believe that I have to create several extended links, basically one for each
arcrole, in order to maintain uniqueness over (from, to). This forces a
duplication of the locator definitions.
	It is also possible that uniqueness can only be enforced over a
combination of XLink attributes and user attributes (or even broader
definitions of keys to include element content as in XML Schema). 
	My request is that XLink allow a broader definition of the arc
uniqueness constraint than is currently written in the spec.

Cheers,
David vun Kannon
Specification WG Co-chair, XBRL
*****************************************************************************
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 

If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter.         
*****************************************************************************
Received on Tuesday, 19 June 2001 10:53:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:08:12 UTC