> Hi Folks,
>
> 1. Use the right schema language for the right job.
+1
But I think the interaction between skills, tools, language capabilities
and meeting project objectives is quite complex.
> 2. It's the XML vocabulary that matters, not the particular schema
> language used to implement the vocabulary.
+1
But this is not a statement of principle but a technical goal, actually.
> 3. Create a metaschema that abstracts away the schema language
> implementations, thus enabling applications to focus on processing the
> XML vocabularies, and not worrying about the particular schema
> languages they're implemented in.
+1
And this has impact on standards developers:
http://www.oreillynet.com/xml/blog/2007/11/standardize_the_jellybeans_not.html
> 4. Multiple validations on the data should be the norm, not the
> exception.
+1
Cheers
Rick jelliffe
