-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm sorry, but it's not clear to me from your posting who is meant to
be in control of whether 'strict' or 'loose' constraints are imposed.

At the schema level, one way to manage this is to define the 'loose'
versions in one schema document, and redefine them by restriction to the
'strict' version in a second schema document.  Then either at import
time or at validation time you control the strict/loose choice by
which of the two documents you load.

Hope this helps,

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)

iD8DBQFDkEJRkjnJixAXWBoRAluGAJ4zxckEv/UhJgNFMGLSxMy1bIUxAgCcDwZn
ljT1N7ro1E1SyzYtiMXG1II=
=eSsF
-----END PGP SIGNATURE-----