W3C home > Mailing lists > Public > xmlschema-dev@w3.org > February 2005

RE: Use of key/keyref - any best practices? warnings?

From: Dan Vint <dvint@dvint.com>
Date: Fri, 25 Feb 2005 15:48:36 -0800
Message-Id: <6.1.0.6.2.20050225154815.03118d90@mail.dvint.com>
To: "Michael Kay" <mike@saxonica.com>,"'Dan Vint'" <dvint@dvint.com>, <xmlschema-dev@w3.org>

What do you mean by different scope?

..dan

At 03:33 PM 2/25/2005, Michael Kay wrote:
>I think key/keyref is quite widely implemented and you can certainly use it.
>
>I would personally steer clear of defining keys and keyrefs that have
>different scope. It's just mindblowingly complicated to work out what's
>going on. I think I understood it for a couple of weeks last year when I was
>implementing it, but I don't now.
>
>Michael Kay
>http://www.saxonica.com/
>
>
> > -----Original Message-----
> > From: xmlschema-dev-request@w3.org
> > [mailto:xmlschema-dev-request@w3.org] On Behalf Of Dan Vint
> > Sent: 25 February 2005 23:20
> > To: xmlschema-dev@w3.org
> > Subject: Use of key/keyref - any best practices? warnings?
> >
> >
> > My organization is going to start looking at the use of key/keyref. I
> > haven't seen many questions or recommendations about the use of this
> > feature. Is anyone really using this functionality? What sort
> > of problems
> > (if any) are you finding? Is this functionality well
> > supported by the tools
> > and vendors - or is this another one of these features they are not
> > implementing?
> >
> > Thanks for any help you can provide.
> > ..dan
> > --------------------------------------------------------------
> > -------------
> > Danny Vint
> >
> > Specializing in Panoramic Images of California and the West
> > http://www.dvint.com
> >
> > voice: 510-522-4703
> >
> >
> >
> >
> >
> >
> >

---------------------------------------------------------------------------
Danny Vint

Specializing in Panoramic Images of California and the West
http://www.dvint.com

voice: 510-522-4703


     
Received on Friday, 25 February 2005 23:44:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:49 GMT