> A schema-link-aware client is likely going to be able to look at the
> schema itself to determine what kind of element is defines without the
> use of the for attribute.
But that requires the client to fetch all the schema's that are defined.
That's probably okay for a client that is creating entries, since it will
be set up to only write a specific set of entries anyway, but it's not
clear to me that it's okay for a client that is GET'ing entries. If
people feel strongly that @for is a premature optimization, oh well.
> Of course there's no need to define everything but there are simple
> steps you can take o reduce the number of things that need to be
explained.
I will take another look at your questions.
/r$
--
Visiting Member, IBM Academy
STSM, DataPower Chief Programmer
WebSphere DataPower SOA Appliances
http://www.ibm.com/software/integration/datapower/
