Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] schema key/keyRef question

From: ht@---.--.--.-- (----- -. --------)
To: Doug Marttila <doug@---------.--->
Date: 1/5/2006 10:50:00 AM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Doug Marttila writes:

> I am using a node in my xml to define variables. The defined variables
> are referenced by ID in another node (a project). The problem is that
> some variables have sub-ids (the variables are "buckets" instead of
> numeric values, they can have values like "high" "med" "low")

This is, I'm sorry to say, a Frequently Requested Feature, i.e. there
is no simple way to achieve what you want.

I think of this as the licence-plate problem -- cars have licence
plates, which specify state and plate number.  Within states, plate
numbers are unique.  Presuming a set of States keyed by @code, each
containing a sequence of IssuedPlates keyed by @number, to check an
ObservedPlate with @state and @number we need a _chained_ KeyRef,
i.e. use @state to identify a State, then use @number to identify an
IssuedPlate _within that State_.

The work-around you suggest (as it were, copying @code down from State
onto all IssuedPlates) is the only one I'm aware of.

ht
- -- 
 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@i...
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDvPIlkjnJixAXWBoRAtwnAJ9tlo6T26W5xXh0aHEHbgWRUmhiBwCeNrrq
58tk9hQGA87lf6jcQOlXG+0=
=RcnZ
-----END PGP SIGNATURE-----


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent