db.effectivity.attributes definition

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

Hi,

while writing a specialization of DB5, I noticed the
db.effectivity.attributes definition directly holds the list
of
attributes, instead of further referencing attributes
definitions.

That forces to redefine the whole db.effectivity.attributes
definition
just to specialize userlevel for instance.
Since some of those attributes are used in profiling, I
think it will
not be uncommon to see them specialized by constraining them
to a fixed
list of possible values. Hence the interest of separate
definitions for
each of those attributes.

I hope it makes sense, if so should I submit a RFE?

Camille.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


iD8DBQFEsiyOjv9P65BfOUMRAj7bAKCZITZp7BZ1kYD4TMIt4ogiQ7iLhgCf
ZI/G
ch/Z5qDuo49oarRr4xq3XUY=
=YkOL
-----END PGP SIGNATURE-----
------------------------------------------------------------
---------
To unsubscribe, e-mail: docbook-unsubscribelists.oasis-open.org
For additional commands, e-mail: docbook-helplists.oasis-open.org