Re: [DISCUSS] beanval module name
gerhard/thomas The problem I have with bv is that no one refers to BeanValidation as bv (in fact, Bean Validation is the shortened form of JavaBeans Validation). Doing a quick google search on bv shows me some STDs. Since google is typically stalking me and knows I ask lots of programming questions, it would typically return the programming references first. Doing a google search for bv bean validation shows beanvalidation.org, however there are no references to bv on that site. romain Yes, I think using bval ties us closely to the Apache impl. I think I generally prefer longer names. For example, we chose partial-bean rather than pb. If it were bean-val instead of beanval, would anyone mind that? John On Sun, Jun 16, 2013 at 9:45 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi john, in codi we used bv1 (like jpa1, jsf12, jsf20,...). if we don't plan to support multiple versions with separated modules, i tend to like just bv (since we use jpa and jsf for the modules of the corresponding specs). regards, gerhard 2013/6/16 Romain Manni-Bucau rmannibu...@gmail.com As a short name bval is fine but maybe too close of apache impl. So id use bean-validation. Being explicit is good when naming things Le 16 juin 2013 15:25, John D. Ament john.d.am...@gmail.com a écrit : Hi all One of the comments in the introduction of a Bean Validation module is that the name I gave it isn't descriptive/useful. I chose the name beanval since it was a shortened version of Bean Validation that could easily be read via maven. To me, it's descriptive of being related to JSR303 support. One of the other names proposed is bv. If anyone has any recommended names, or questions about the given names, could you speak up? John
Re: [DISCUSS] beanval module name
whatever the list is IMO, the point was already mentionned: how many times did you use bv to say bean validation? You never say Java Persistence API but always jpa, for bval that's the opposite IMO. I commonly see bval or beanvalidation but not others. *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/6/16 John D. Ament john.d.am...@gmail.com Gerhard, They may use [bv-dev] as a prefix, but the mailing list name is beanvalidation-dev. On Sun, Jun 16, 2013 at 10:11 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi john, please check e.g. the official eg/dev list [1]. the subject of mails starts with [bv-dev] regards, gerhard [1] http://lists.jboss.org/pipermail/beanvalidation-dev/ 2013/6/16 John D. Ament john.d.am...@gmail.com gerhard/thomas The problem I have with bv is that no one refers to BeanValidation as bv (in fact, Bean Validation is the shortened form of JavaBeans Validation). Doing a quick google search on bv shows me some STDs. Since google is typically stalking me and knows I ask lots of programming questions, it would typically return the programming references first. Doing a google search for bv bean validation shows beanvalidation.org, however there are no references to bv on that site. romain Yes, I think using bval ties us closely to the Apache impl. I think I generally prefer longer names. For example, we chose partial-bean rather than pb. If it were bean-val instead of beanval, would anyone mind that? John On Sun, Jun 16, 2013 at 9:45 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi john, in codi we used bv1 (like jpa1, jsf12, jsf20,...). if we don't plan to support multiple versions with separated modules, i tend to like just bv (since we use jpa and jsf for the modules of the corresponding specs). regards, gerhard 2013/6/16 Romain Manni-Bucau rmannibu...@gmail.com As a short name bval is fine but maybe too close of apache impl. So id use bean-validation. Being explicit is good when naming things Le 16 juin 2013 15:25, John D. Ament john.d.am...@gmail.com a écrit : Hi all One of the comments in the introduction of a Bean Validation module is that the name I gave it isn't descriptive/useful. I chose the name beanval since it was a shortened version of Bean Validation that could easily be read via maven. To me, it's descriptive of being related to JSR303 support. One of the other names proposed is bv. If anyone has any recommended names, or questions about the given names, could you speak up? John
Re: [DISCUSS] beanval module name
even when speaking? Then the point is who should understand the name, the EG or users. *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/6/16 Gerhard Petracek gerhard.petra...@gmail.com we (= bv-eg) ~always used bv. it's even used in the bv-spec. document. regards, gerhard 2013/6/16 Romain Manni-Bucau rmannibu...@gmail.com whatever the list is IMO, the point was already mentionned: how many times did you use bv to say bean validation? You never say Java Persistence API but always jpa, for bval that's the opposite IMO. I commonly see bval or beanvalidation but not others. *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/6/16 John D. Ament john.d.am...@gmail.com Gerhard, They may use [bv-dev] as a prefix, but the mailing list name is beanvalidation-dev. On Sun, Jun 16, 2013 at 10:11 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi john, please check e.g. the official eg/dev list [1]. the subject of mails starts with [bv-dev] regards, gerhard [1] http://lists.jboss.org/pipermail/beanvalidation-dev/ 2013/6/16 John D. Ament john.d.am...@gmail.com gerhard/thomas The problem I have with bv is that no one refers to BeanValidation as bv (in fact, Bean Validation is the shortened form of JavaBeans Validation). Doing a quick google search on bv shows me some STDs. Since google is typically stalking me and knows I ask lots of programming questions, it would typically return the programming references first. Doing a google search for bv bean validation shows beanvalidation.org, however there are no references to bv on that site. romain Yes, I think using bval ties us closely to the Apache impl. I think I generally prefer longer names. For example, we chose partial-bean rather than pb. If it were bean-val instead of beanval, would anyone mind that? John On Sun, Jun 16, 2013 at 9:45 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi john, in codi we used bv1 (like jpa1, jsf12, jsf20,...). if we don't plan to support multiple versions with separated modules, i tend to like just bv (since we use jpa and jsf for the modules of the corresponding specs). regards, gerhard 2013/6/16 Romain Manni-Bucau rmannibu...@gmail.com As a short name bval is fine but maybe too close of apache impl. So id use bean-validation. Being explicit is good when naming things Le 16 juin 2013 15:25, John D. Ament john.d.am...@gmail.com a écrit : Hi all One of the comments in the introduction of a Bean Validation module is that the name I gave it isn't descriptive/useful. I chose the name beanval since it was a shortened version of Bean Validation that could easily be read via maven. To me, it's descriptive of being related to JSR303 support. One of the other names proposed is bv. If anyone has any recommended names, or questions about the given names, could you speak up? John
Re: [DISCUSS] beanval module name
we never had an issue with that in codi where we use bv since 2010. regards, gerhard 2013/6/16 Romain Manni-Bucau rmannibu...@gmail.com even when speaking? Then the point is who should understand the name, the EG or users. *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/6/16 Gerhard Petracek gerhard.petra...@gmail.com we (= bv-eg) ~always used bv. it's even used in the bv-spec. document. regards, gerhard 2013/6/16 Romain Manni-Bucau rmannibu...@gmail.com whatever the list is IMO, the point was already mentionned: how many times did you use bv to say bean validation? You never say Java Persistence API but always jpa, for bval that's the opposite IMO. I commonly see bval or beanvalidation but not others. *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/6/16 John D. Ament john.d.am...@gmail.com Gerhard, They may use [bv-dev] as a prefix, but the mailing list name is beanvalidation-dev. On Sun, Jun 16, 2013 at 10:11 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi john, please check e.g. the official eg/dev list [1]. the subject of mails starts with [bv-dev] regards, gerhard [1] http://lists.jboss.org/pipermail/beanvalidation-dev/ 2013/6/16 John D. Ament john.d.am...@gmail.com gerhard/thomas The problem I have with bv is that no one refers to BeanValidation as bv (in fact, Bean Validation is the shortened form of JavaBeans Validation). Doing a quick google search on bv shows me some STDs. Since google is typically stalking me and knows I ask lots of programming questions, it would typically return the programming references first. Doing a google search for bv bean validation shows beanvalidation.org, however there are no references to bv on that site. romain Yes, I think using bval ties us closely to the Apache impl. I think I generally prefer longer names. For example, we chose partial-bean rather than pb. If it were bean-val instead of beanval, would anyone mind that? John On Sun, Jun 16, 2013 at 9:45 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi john, in codi we used bv1 (like jpa1, jsf12, jsf20,...). if we don't plan to support multiple versions with separated modules, i tend to like just bv (since we use jpa and jsf for the modules of the corresponding specs). regards, gerhard 2013/6/16 Romain Manni-Bucau rmannibu...@gmail.com As a short name bval is fine but maybe too close of apache impl. So id use bean-validation. Being explicit is good when naming things Le 16 juin 2013 15:25, John D. Ament john.d.am...@gmail.com a écrit : Hi all One of the comments in the introduction of a Bean Validation module is that the name I gave it isn't descriptive/useful. I chose the name beanval since it was a shortened version of Bean Validation that could easily be read via maven. To me, it's descriptive of being related to JSR303 support. One of the other names proposed is bv. If anyone has any recommended names, or questions about the given names, could you speak up? John
Re: [DISCUSS] beanval module name
codi is not that used, and not sure bv is explicit enough in all languages. hibernate uses validator, other can use jsr330/jsr349. Since this module can be an in between 330 and 349 maybe using jsr330 is good but IMO has the same drawback as bv. If you don't follow specs and/or dev them you don't know what it is. *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/6/16 Gerhard Petracek gerhard.petra...@gmail.com we never had an issue with that in codi where we use bv since 2010. regards, gerhard 2013/6/16 Romain Manni-Bucau rmannibu...@gmail.com even when speaking? Then the point is who should understand the name, the EG or users. *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/6/16 Gerhard Petracek gerhard.petra...@gmail.com we (= bv-eg) ~always used bv. it's even used in the bv-spec. document. regards, gerhard 2013/6/16 Romain Manni-Bucau rmannibu...@gmail.com whatever the list is IMO, the point was already mentionned: how many times did you use bv to say bean validation? You never say Java Persistence API but always jpa, for bval that's the opposite IMO. I commonly see bval or beanvalidation but not others. *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/6/16 John D. Ament john.d.am...@gmail.com Gerhard, They may use [bv-dev] as a prefix, but the mailing list name is beanvalidation-dev. On Sun, Jun 16, 2013 at 10:11 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi john, please check e.g. the official eg/dev list [1]. the subject of mails starts with [bv-dev] regards, gerhard [1] http://lists.jboss.org/pipermail/beanvalidation-dev/ 2013/6/16 John D. Ament john.d.am...@gmail.com gerhard/thomas The problem I have with bv is that no one refers to BeanValidation as bv (in fact, Bean Validation is the shortened form of JavaBeans Validation). Doing a quick google search on bv shows me some STDs. Since google is typically stalking me and knows I ask lots of programming questions, it would typically return the programming references first. Doing a google search for bv bean validation shows beanvalidation.org, however there are no references to bv on that site. romain Yes, I think using bval ties us closely to the Apache impl. I think I generally prefer longer names. For example, we chose partial-bean rather than pb. If it were bean-val instead of beanval, would anyone mind that? John On Sun, Jun 16, 2013 at 9:45 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi john, in codi we used bv1 (like jpa1, jsf12, jsf20,...). if we don't plan to support multiple versions with separated modules, i tend to like just bv (since we use jpa and jsf for the modules of the corresponding specs). regards, gerhard 2013/6/16 Romain Manni-Bucau rmannibu...@gmail.com As a short name bval is fine but maybe too close of apache impl. So id use bean-validation. Being explicit is good when naming things Le 16 juin 2013 15:25, John D. Ament john.d.am...@gmail.com a écrit : Hi all One of the comments in the introduction of a Bean Validation module is that the name I gave it isn't descriptive/useful. I chose the name beanval since it was a shortened version of Bean Validation that could easily be read via maven. To me, it's descriptive of being related to JSR303 support. One of the other names proposed is bv. If anyone has any recommended names, or questions about the given names, could you speak up? John
