db.effectivity.attributes definition

[Camille Bégnis <camille@neodoc.biz>]

-----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

iD8DBQFEsiyOjv9P65BfOUMRAj7bAKCZITZp7BZ1kYD4TMIt4ogiQ7iLhgCfZI/G
ch/Z5qDuo49oarRr4xq3XUY=
=YkOL
-----END PGP SIGNATURE-----
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:Domaine du petit Arbois BP 88;;CEEI;Aix en Provence Cedex 4;;13545;France
email;internet:camille@neodoc.biz
tel;work:+33.4.42.22.62.35 
tel;cell:+33.6.33.15.10.23
note;quoted-printable:Rejoignez mon r=C3=A9seau sur viaduc:=0D=0A=
	=0D=0A=
	http://www.viaduc.com/invitationpersonnelle/002lm14bc0jlkfk
x-mozilla-html:FALSE
url:http://neodoc.biz
version:2.1
end:vcard