The schema namespace for Java EE 7 APIs are moving from java.sun.com to now perhaps a more fitting xmlns.jcp.org. You are encouraged to take a look at the latest Java EE 7 draft schemas at: http://xmlns.jcp.org/xml/ns/javaee/index.html (it is still a work in progress since as you know, Java EE 7 has not been finalized yet). Some of the updated schemas include:

• application_7.xsd
• application-client_7.xsd
• connector_1_7.xsd
• ejb-jar_3_2.xsd
• javaee_7.xsd
• jsp_2_3.xsd
• javaee_web_services_1_4.xsd
• javaee_web_services_client_1_4.xsd
• web-app_3_1.xsd
• web-common_3_1.xsd
• web-fragment_3_1.xsd
• web-facelettaglibrary_2_2.xsd
• web-facesconfig_2_2.xsd

Independent consultant, ardent Java EE advocate and long-time JCP expert Antonio Goncalves had this to say about the change - "technically changing a namespace is not difficult, so this is not a major Java EE 7 technical update. But it's a symbol. For many years we were wondering what would happen to java.sun.com namespaces. Most of us thought it would be renamed to java.oracle.com. But no, it went back to where it originally belonged, to the JCP. Lately the JCP has moved towards greater transparency (i.e. JCP.next) and having the JCP namespaces strenghens this move."

Note, not all API namespaces will be updated right away since some APIs are not changing in Java EE 7. For example, JAX-WS will likely not be updated. All the older namespaces will continue to be maintained for backwards compatibility.

Now is the time to share your views. Here is the relevant EG discussion: http://java.net/projects/javaee-spec/lists/jsr342-experts/archive/2013-02/message/36.