-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
A couple of days ago I created SHINDIG-1878 as I've found some discrepancies between the OpenSocial 2.5 specification and the current code. Most apparently, the Person entity appears to be quite a bit off with respect to the spec. I'd like to supply some patches to help out resolving this issue, but have some questions about how to proceed. For example: the inconsistent use of PluralFields in Person: should it be implemented as a simple ordered list, or a List<ListField>? Or the use of enumerations for, for example, the drinker-field, should those be converted back to strings? Anybody care to share their thoughts on this? - -- Met vriendelijke groeten | Kind regards Jan Willem Janssen | Software Architect +31 631 765 814 /My world is:/ Luminis Technologies B.V. IJsselburcht 3 6825 BS Arnhem +31 88 586 46 30 http://www.luminis-technologies.com http://www.luminis.eu KvK (CoC) 09 16 28 93 BTW (VAT) NL8169.78.566.B.01 -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQd7mSAAoJEKF/mP2eHDc435YQALSxb3W9yvt9fUwH86EjlOmJ JNCYYPxZWd65ZL0vHdSUOzIofn0ODVvbVU3wBBq2oMBfq+q5wuE/G1AKlE838VSv k4JZIVfBO59jiyoJByCEYM+0KWq6G8hMdsSgcP00MTytom5REqx9g7PD24I88ZeE IbetwdpRO1Rrs5OCq/dR5OzhC8ge2ySSDTl4l5Ye1YlEwjb6O0HlNQBMD9r+Ge7K esUzT8V8f/NM1ai/jhTbr76O81EAgpz0fCMquH1b++Z7FDHmIAsEmbgI40rgU8pQ owKlm8LbhBwqtnAtlCoggaqhgbOGgFMohsglRVxstdbAkEc9T7v9k+koDfyTwRpJ Pp/7PfxPBZfI39/eJPZvZ9nHG7xA6VnmxJ9jk4wBrpIsozwdSrXB8ocWgSvsUDMp 3XwzxkohndGRmMFQn+E922NjFxT2FkTYDeZ4SfTDx9fXx4wiqKPSVQeMtOlusD/M 88aM3YiH/qrGdW6gILGiK0lfGb2PxQ/gFIXC2BNFpOKoMk2Uwzc58xZlAcfRRBwo 75ymQDQo9wtni8nl79aCTtao/h6gOZoqtqh1pKq6JR2Eprchs8neer3xgv8rOj5t FeM6BDVyd3x9k+SAwnkKKu9zbYMVNedH8nJGMwxe02PI1b8oFFAIsKwkrflV+ETE CTh+DYbXi/rRyXjRtZip =FsRy -----END PGP SIGNATURE-----
