| Re: [jakarta.ee-spec.committee] Who decide the Jakarta spec namespace? |
|
Hi Andrew,
My understanding is that jakartanamespace is limited to API artifacts not to the testing artifacts. In other words, the Jakarta TCK projects do not use the namespace of jakarta.xx. It did not suggest API artifacts must use this namespace.
As for the process, my understanding is that the spec project comes up with a namespace and it should be acceptable as long as it complies with EF guidance, which only mentions the IP concerns. Therefore, I think the usage of
org.eclipse.microprofile is allowed in Jakarta Specifications.
Thanks
Emily
================ Emily Jiang Java Champion, Fellow of BCS
STSM, Jakarta and MicroProfile Architect @IBM
Liberty Cloud Native Architect & Advocate
LinkedIn: https://www.linkedin.com/in/emilyfhjiang/
From: Andrew Pielage <andrew.pielage@xxxxxxxxxxx>
Sent: 02 June 2025 19:04 To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx> Cc: Wayne.Beaton@xxxxxxxxxxx <Wayne.Beaton@xxxxxxxxxxx>; Emily Jiang <EMIJIANG@xxxxxxxxxx> Subject: [EXTERNAL] Re: Who decide the Jakarta spec namespace?
This Message Is From an External Sender
This message came from outside your organization.
Wayne can provide further context and the EMO stance, but generally the Spec Committee approves specifications according to their own criteria whereas the EMO provides overall governance.
Source: a lingering Paul Buck (paraphrased) 🙂
So it probably is up to the Jakarta Specification what namespace they use, as long as it's within the boundaries defined by the Spec Commitee and EMO?
It may be something the spec committee needs to discuss and agree on - currently it seems we don't have a defined stance for it past what was already written in the JESP (presumably in the context of the javax migration).
"Use of the
jakarta namespace is limited to API artifacts (all API jars, javadoc, and schema namespaces)."
To me that sentence could be read as an intention that all published API artifacts must conform to the jakarta namespace, though I accept it could also be read as "if you're using the jakarta namespace, then...".
Thanks,
From: Emily Jiang <EMIJIANG@xxxxxxxxxx>
Sent: Monday, June 02, 2025 15:24 To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx> Cc: Andrew Pielage <andrew.pielage@xxxxxxxxxxx>; Wayne.Beaton@xxxxxxxxxxx <Wayne.Beaton@xxxxxxxxxxx> Subject: Re: Who decide the Jakarta spec namespace?
Thank you, Andrew, for your prompt response! According to the
EMO doc as per your email, my understanding is that the namespace of org.eclipse.microprofile can be kept after moving MicroProfile specification to Jakarta EE.
Wayne, do you agree with my above assumption? also, the namespace for a Jakarta Specification is decided by the project rather than the Jakarta EE spec committee. Did I understand correctly.
Thanks
Emily
================ Emily Jiang Java Champion, Fellow of BCS
STSM, Jakarta and MicroProfile Architect @IBM
Liberty Cloud Native Architect & Advocate
LinkedIn: https://www.linkedin.com/in/emilyfhjiang/
From: jakarta.ee-spec.committee <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx> on behalf of Andrew Pielage via jakarta.ee-spec.committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Sent: 02 June 2025 14:00 To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx> Cc: Andrew Pielage <andrew.pielage@xxxxxxxxxxx> Subject: [EXTERNAL] Re: [jakarta.ee-spec.committee] Who decide the Jakarta spec namespace?
This Message Is From an External Sender
This message came from outside your organization.
I don't know the concrete answer, but I found some references implying we at least have some way in it.
The JESP has some notes about usage of the "jakarta" namespace.
"
All development that modifies content in the
javax namespace must be moved to a
jakarta namespace. All jakarta namespace development must occur within the scope of a Specification Project operating under the purview of the Jakarta EE Working Group’s Specification Committee and must implement the process as defined
by the most recently adopted revision of the JESP. Use of the jakarta namespace is limited to API artifacts (all API jars, javadoc, and schema namespaces). It must not be used for any deployment, including applications, TCKs, tools, libraries
or any other assets produced by Specification Projects.
"
The EFSP which the JESP is based on doesn't seem to say much about namespace though (or if it does my eyes are glazing over it).
If I'm reading the EDP correctly, it seems to indicate that namespaces are controlled by the EMO.
"
Namespaces are assigned to a Project by the EMO. All Project source code must be organized in the assigned namespaces and Projects can only Release code under their own namespace (that is, they cannot infringe on another Eclipse Project’s namespace).
"
From: jakarta.ee-spec.committee <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx> on behalf of Emily Jiang via jakarta.ee-spec.committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Sent: Monday, June 02, 2025 11:11 To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx> Cc: Emily Jiang <EMIJIANG@xxxxxxxxxx> Subject: [jakarta.ee-spec.committee] Who decide the Jakarta spec namespace? In the recent discussion of hosting MicroProfile in Jakarta EE, there was a discussion about the namespace. I have the following question:
Does the Jakarta Spec committee decide the namespace or the spec project decide the namespace?
e.g. in Jakarta Config, would our Jakarta Spec committee decide the namespace or the committers in the Jakarta Config decide the namespace?
Thanks
Emily
================ Emily Jiang Java Champion, Fellow of BCS
STSM, Jakarta and MicroProfile Architect @IBM
Liberty Cloud Native Architect & Advocate
LinkedIn: https://www.linkedin.com/in/emilyfhjiang/
Unless otherwise stated above:
IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: Building C, IBM Hursley Office, Hursley Park Road, Winchester, Hampshire SO21 2JN Unless otherwise stated above:
IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: Building C, IBM Hursley Office, Hursley Park Road, Winchester, Hampshire SO21 2JN
Unless otherwise stated above:
IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: Building C, IBM Hursley Office, Hursley Park Road, Winchester, Hampshire SO21 2JN |