Where/how to publish implementation-specific schemas? [BS]
Suggestion: Add implementation specific namespaces under https://jakarta.ee/xml/ns/ [IG]
Use a separate url for the implementation-specific schemas (ie. glassfish). Something like https://org.eclipse/xml/ns
Ivar will follow up with the EF to see if a separate url/repo can be setup for the implementation-specific schemas.
Who’s handling Enterprise Web Services (JSR 109) schemas? [BS]
Need to update https://github.com/eclipse-ee4j/jax-ws-api/issues/98 with this request. Request for IBM to drive since they originally owned this JSR 109 spec.
FYI, also JAXB schemas here. [BS]
Lukas has already started moving on this request…
New suggestion for Schemas at https://jakarta.ee/xml/ns/jakartaee/: https://deploy-preview-700–jakartaee.netlify.com/schemas/ [IG]
Ivar will add some introductory text like the xmlns.jcp.org
Subpage per sub-namespace. Or, perhaps divide up this one page with multiple namespaces. Need to experiment with the layouts.
jaxb and jaxws namespaces should change to something else
[SM] Use of non-Eclipse Copyright date formatting in TCK
This came up on https://github.com/eclipse-ee4j/jakartaee-tck/pull/175, should this be raised on a ml or discussed here?
We can send mail if that makes more sense.
Also posted to the PMC mailing list: https://www.eclipse.org/lists/ee4j-pmc/msg02598.html
When updating TCK source for EE 9, should we follow existing convention?
GlassFish copyright tool could be used.
Or follow Eclipse formatting for Copyright dates.
Keep following Eclipse formatting: [, ]
All existing Oracle Copyright statements in the code should be left intact.
Except when updating the for the jakarta.* namespace update.
If new content is being provided, then an additional Copyright can be inserted citing the organization, individual, or the Eclipse Foundation as contributors. Follow the conventions outlined in the Eclipse Handbook.