FYI Begin forwarded message:
> From: Emmanuel Bernard <[email protected]> > Date: 10. Januar 2011 18:38:55 MEZ > To: Lukas Kahwe Smith <[email protected]> > Subject: Re: implementing JSR 303 in another language > > > On 10 janv. 2011, at 18:11, Lukas Kahwe Smith wrote: > >> >> On 10.01.2011, at 18:06, Emmanuel Bernard wrote: >> >>> >>> On 10 janv. 2011, at 15:26, Lukas Kahwe Smith wrote: >>> >>>> >>>> On 10.01.2011, at 14:39, Emmanuel Bernard wrote: >>>> >>>>> Hi Lukas, >>>>> The intent of the spec lead of JSR-303 (aka me, Red Hat) is to have an >>>>> open specification. That being said, we had to deal with Sun at the time >>>>> and what you've quoted is basically the only license that could get us in >>>>> Java EE 6 on time (it would have been a lawyer battle to get ASL accepted >>>>> by Sun and we would have missed the boat for certain). >>>>> >>>>> Can the spec be implemented in other languages even with this spec, that >>>>> I don't know and I'm not a lawyer but that's certainly the intent of the >>>>> spec lead to foster adoption in Java and outside Java. AFAIK there is a >>>>> JavaScript and a Flex implementation of the spec already. >>>> >>>> Ok, interesting. >>>> >>>>> Are you planning a PHP impl? >>>> >>>> >>>> There is already an implementation in PHP: >>>> http://docs.symfony-reloaded.org/master/guides/validator/overview.html >>> >>> Hehe interesting, the Symphony ecosystem is influenced by one more brick >>> from us ;) >> >> Symfony2 is Spring for PHP in a lot of ways .. >> >>>> >>>> The JCR people said they have also released their spec under the Apache >>>> license, though they are having a bit of trouble finding some "proof" of >>>> that :) >>>> http://dev.day.com/content/ddc/blog/2010/12/apache_leaves_thejc.html?cq_ck=1294317161681 >>>> >>>> I am not so worried about copyright, because I would assume our >>>> implementation to be sufficiently different due to the nature that PHP is >>>> a loosely typed scripting language. However I am a bit worried about >>>> patents. Are you aware of patents that were assigned to JSR 303? >>> >>> The API, impl and TCK are released under the ASL 2.0 so you won't have >>> copyright issue even if you "borrow" from the impl, just stay true to the >>> ASL 2.0 obligations. >>> >>> To my personal knowledge, I am not aware of any patents (of any company) >>> that read on JSR-303. Of course, I can't guarantee that no such patents >>> exist. >>> If that can reassure you, the ASL 2.0 (which is the license all of our work >>> around JSR 303 has been done has a patent provision clause. >> >> >> Just as with JCR, I am trouble finding any reliable documentation on the >> available licenses. For the TCK I found the following: >> http://docs.jboss.org/hibernate/stable/beanvalidation/tck/reference/html_single/ >> >> Would be great if these contributions would be made clear on some trusted >> site. > > AFAIK all of our distributions contain the license we use and our Maven POMs > reference the right license. > The website also indicates we use the ASL (logo) > http://validator.hibernate.org > > finally our source code includes the license > https://github.com/beanvalidation/beanvalidation-tck > https://github.com/beanvalidation/beanvalidation-api > https://github.com/hibernate/hibernate-validator > > But I agree with you. I've created > http://opensource.atlassian.com/projects/hibernate/browse/HV-410 to improve > that state. > Lukas Kahwe Smith [email protected] -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
