[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: schema key/keyRef question

• To: Doug Marttila <doug@v...>
• Subject: Re: schema key/keyRef question
• From: ht@i... (Henry S. Thompson)
• Date: Thu, 05 Jan 2006 10:17:09 +0000
• Cc: xml-dev@l..., www-xml-schema-comments@w...
• In-reply-to: <43BC4718.4080608@v...> (Doug Marttila's message of "Wed, 04 Jan 2006 17:07:20 -0500")
• References: <43BC4718.4080608@v...>
• User-agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.17 (linux)

-----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-----

• Follow-Ups:
  • Re: schema key/keyRef question - matching multiple keys
    • From: Doug Marttila <doug@v...>

• References:
  • schema key/keyRef question
    • From: Doug Marttila <doug@v...>

• Prev by Date: schema key/keyRef question
• Next by Date: OT: Corporate Blog Policies
• Previous by thread: schema key/keyRef question
• Next by thread: Re: schema key/keyRef question - matching multiple keys
• Index(es):
  • Date
  • Thread