From: Pete Muir <pmuir(a)redhat.com&gt; Subject: JSR-346 Public Review Draft Date: 26 October 2012 18:31:09 GMT+01:00 To: spec-submit(a)jcp.org

1) Please see attached 2) 30 days 3) A. Does the specification include software codes in the following format: Binary : No Source (compilable) : No Javadocs : Yes B. Do the codes or the spec call on, contain, use or demonstrate encryption technology? No 4. Licensing is unchanged 5. 12 February 2013 6. Version: 1.1, Release Date: 15 March 2013, Spec Lead: Red Hat, Inc. 1801 Varsity Drive, Raleigh, North Carolina 27606. United States. 7. • The public can read the names of the people on the Expert Group (ie, not just JCP Members) http://jcp.org/en/jsr/detail?id=346 • The Expert Group business is regularly reported on a publicly readable alias. http://lists.jboss.org/pipermail/cdi-dev/ • The schedule for the JSR is publicly available, it's current, and I update it regularly. https://github.com/jboss/cdi/wiki • The public can read/write to a wiki for my JSR. https://github.com/jboss/cdi/wiki • I have a discussion board for my JSR and I regularly read and respond to posts on that board. http://lists.jboss.org/pipermail/cdi-dev/ • There is an issue-tracker for my JSR that the public can read. http://issues.jboss.org/browse/CDI • I have spoken at conferences and events about my JSR recently. Yes, e.g JavaOne • I am using open-source processes for the development of the RI and/or TCK. Yes. https://github.com/weld & https://github.com/jboss/cdi-tck • The Community tab for my JSR has links to and information about all public communication mechanisms and sites for the development of my JSR. Yes