Re: 1.8 issues

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

Hi,

my 2 cents from MidCOM PoV:

- --Piotras wrote on 2006-03-07 12:50:
> 	* dot and colon separator used in QB's constraints
> 	We didn't make any clear decision yet.

I am still against having different separators depending on context. Reasons
have been elaborated in detail. The short version: API consistency and Ease of Use.


> 	* metadata properties
> 	Frankly speaking I count on Torben's help in this matter as we do not 
> 	want to support '_' in properties'  names, and those midcom related
> 	contain underscores.

MidCOM has an abstraction layer for this, so renaming properties on the Midgard
core level is ok in the case that this _ restriction remains.


Live long and Prosper!
Torben Nehmer

- --
Torben Nehmer, Guenzburg, Bavaria, Germany
http://www.nathan-syntronics.de, mailto:[email protected]
PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEDXWVJPh4Kn6d5FYRAnUqAJ9tAgHC0Wn1cjAMn4pscqU7e6UWHwCggWNa
Uc3Lv5GTLKMv+P/RtS+WREI=
=gBaR
-----END PGP SIGNATURE-----