Re: [jakarta.ee-spec.committee] TCK process and committee operation docs

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

Alasdair Nottingham wrote on 7/30/19 2:05 PM:
> I’ve converted the project names and codes into an asciidoc and created a PR here: https://github.com/jakartaee/specification-committee/pull/6

Thanks!

> There are a few things I’ve noticed (and this isn’t complete).
> 
> I can’t find the github repo for the following specs:
> 
> * Jakarta Debugging Support for Other Languages (part of ee4j.jsp)

No separate repo, it's integrated with the JSP implementation.

> * Jakarta Web Services Metadata (part of ee4j.jaxws)

No separate repo, it's integrated with the JAX-WS implementation.

> 
> I also notice there are a few places where the PR’s for the specs don’t follow the codes in the original spreadsheet. For example:
> 
> * tags -> JSTL
> * xml-ws -> xml-web-services
> * restful-ws -> restful-web-services
> 
> I don’t know if we want to update the project codes to match what is being used in the specs, or vice versa. I updates tags to jstl in the asciidoc, but I’m not sure if that was right.

Stick with the original codes.  Some of the PRs will need to be updated.

> 
> The JAX-WS specs also have inconsistent spec names to codes:
> 
> * Jakarta SOAP Attachments -> soap
> * Jakarta XML Web Services -> xml-ws
> * Jakarta Web Services Metadata -> ws-metadata
> 
> it kind of seems to me that soap seems overly general for SOAP Attachments, and it kind of seems odd that they don’t all have a common prefix (either ws or xml-ws).
> 
> Not sure if any of this is important, but having noticed it I wanted to raise it.

I think all the codes were chosen by Eclipse.  We probably should've reviewed
them more carefully and been better about consistency, but I'm not sure we
want to disrupt things right now by changing them.