[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Platform and WebProfile specs ready to be "jakarta-ized"

I think we need to consider the context of the acronyms in use before making changes.  For example, I just reviewed a section (I think it was the app deployment section) and we shouldn't be changing the deployment descriptors, such as ejb-client-jar.   If those change that would mean apps would have to change, and we can't have that in Jakarta EE 8.  All Applications and Application Servers that are Java EE 8 compliant should not have to make *any* changes when moving to Jakarta EE 8.  

We should also consider the context of "generic" terminology.  For example, I've seen cases where "web and ejb container" is referenced.  Personally, I would leave this as-is since it's a generic use of "ejb" and it's not capitalized.  But, if you really feel it needs to change, then I would do "web and enterprise bean container".  Don't insert "Jakarta Enterprise Bean" in this case.  Overkill.

Thanks!

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn:
https://www.linkedin.com/in/kevinwsutter



From:        Kevin Sutter <kwsutter@xxxxxxxxx>
To:        jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Date:        07/04/2019 05:03 PM
Subject:        [EXTERNAL] Re: [jakartaee-platform-dev] Platform and WebProfile specs ready to be "jakarta-ized"
Sent by:        jakartaee-platform-dev-bounces@xxxxxxxxxxx




Thanks, Emily!

1.  Java SE is fine to use.
2.  Good question on schema location.  For now, I think the current location is fine.

-- Kevin

On Thu, Jul 4, 2019, 14:24 Emily Jiang <emijiang6@xxxxxxxxxxxxxx> wrote:
I've done one PR https://github.com/eclipse-ee4j/jakartaee-platform/pull/39/files

Can I clarify for the following:
1. I think Java SE is still allowed to be mentioned in the spec. Please correct me if I am wrong.

2. For the schemas for Jakarta EE, where should these be hosted?
e.g. for the following one:
http://xmlns.jcp.org/xml/ns/javaee/application_8.xsd

I guess it needs to be hosted by eclipse site. Please clarify.

At the moment, I just updated javaee to jakartaee, which might not be complete.

Thanks
Emily


On Thu, Jul 4, 2019 at 6:07 PM Paul Buck <paul.buck@xxxxxxxxxxxxxxxxxxxxxx> wrote:

The direction from our trademark specialist is to put the TM after Jakarta.

... Paul 


On Thu, Jul 4, 2019 at 12:10 PM Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:
https://www.eclipse.org/legal/logo_guidelines.phpsays Jakarta and Jakarta EE are asserted
https://www.eclipse.org/projects/tools/trademarks.php says Jakarta EE is filed
 
so would be useful to know where to put the tm in the spec docs etc. until Jakarta EE is registered.
 
From: jakartaee-platform-dev-bounces@xxxxxxxxxxx<jakartaee-platform-dev-bounces@xxxxxxxxxxx> On Behalf Of Kevin Sutter
Sent:
04 July 2019 16:57
To:
jakartaee-platform developer discussions <
jakartaee-platform-dev@xxxxxxxxxxx>
Subject:
Re: [jakartaee-platform-dev] Platform and WebProfile specs ready to be "jakarta-ized"

 
Paul, according to our trademark page, it says that "Jakarta EE" is trademarked.  It says nothing about "Jakarta" itself being trademarked...  Which is correct?
 
-- Kevin
 
On Thu, Jul 4, 2019, 10:03 Paul Buck <paul.buck@xxxxxxxxxxxxxxxxxxxxxx> wrote:
 
Please keep the â after Jakarta.
 
... Paul
 
 
On Thu, Jul 4, 2019 at 6:30 AM Omos Aziegbe <omoz4real@xxxxxxxxx> wrote:
Hi Kevin,
 
I would like to assist on this. I am quite naive on this and would like to clarify something. There is the use of Javaâ Platform Enterprise Edition. Should it be changed to Jakartaâ Platform Enterprise Edition or just Jakarta Platform Enterprise Edition? Getting rid of the TM or keeping it.
 
Thanks,
Omos
 
 
 
 
 
On Thu, Jul 4, 2019 at 11:19 AM Scott Stark <starksm64@xxxxxxxxx> wrote:
I made a stab at updating the Security section:
https://github.com/eclipse-ee4j/jakartaee-platform/pull/36
 
On Wed, Jul 3, 2019 at 8:38 PM Kevin Sutter <sutter@xxxxxxxxxx> wrote:
I should point out that the chapter files for the Platform and WebProfile are in the following corresponding directories...

https://github.com/eclipse-ee4j/jakartaee-platform/tree/master/specification/src/main/asciidoc/platform
https://github.com/eclipse-ee4j/jakartaee-platform/tree/master/specification/src/main/asciidoc/webprofile

No other files need to be modified for this requested exercise.


You can either do a "mvn clean install" and look at the generated pdf or html.  Or, you can view the corresponding sections via these urls:


https://github.com/eclipse-ee4j/jakartaee-platform/blob/master/specification/src/main/asciidoc/platform/Platform.adoc
https://github.com/eclipse-ee4j/jakartaee-platform/blob/master/specification/src/main/asciidoc/webprofile/WebProfile.adoc

Have fun!

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail:  
sutter@xxxxxxxxxx    Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn:
https://www.linkedin.com/in/kevinwsutter



From:        
"Kevin Sutter" <sutter@xxxxxxxxxx>
To:        
"jakartaee-platform developer discussions" <jakartaee-platform-dev@xxxxxxxxxxx>
Date:        
07/03/2019 10:19 PM
Subject:        
[EXTERNAL] [jakartaee-platform-dev] Platform and WebProfile specs ready to be        "jakarta-ized"
Sent by:        
jakartaee-platform-dev-bounces@xxxxxxxxxxx





Hi,
Most of you know that the Java EE Platform and WebProfile specs have now been contributed to Eclipse and ready to go through the transformation to Jakarta Platform and WebProfile specs:

https://github.com/eclipse-ee4j/jakartaee-platform/tree/master/specification

I have broken up the individual specs into slightly more manageable pieces of asciidoc (each spec used to be one giant asciidoc file).  I broke them up by chapters.  Of course, some are larger than others, but at least we can now divide and conquer the effort in front of us.  Many of you have been asking "how can I help?".  Now's your chance.  If you are interested and available, we would appreciate PRs with cleaning up the various sections of these two spec documents.

The cleanup required is mostly tedious work.  
We are looking for the minimal work required.  At this point, do not further subdivide the asciidoc files.  I would suggest keeping the PRs short and simple.  Don't try to do "everything" in one PR.  You don't even have to complete a whole chapter in a single PR.  Maybe identify the subsections covered in the title of your PR.  Shorter PRs will be easier for the committers to evaluate and merge into master.  Reference the list of existing PRs before starting on a chapter to avoid duplication of effort.

I am sending out this request now since many of us in the US will be out for the extended weekend.  There are a few committers in other parts of the world, so hopefully we'll make some progress over the weekend.  I didn't want to wait until Monday to start this effort since we need to have these spec docs ready by July 15.

Thanks for your help!

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail:  
sutter@xxxxxxxxxx    Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn:
https://www.linkedin.com/in/kevinwsutter_______________________________________________
jakartaee-platform-dev mailing list

jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev



_______________________________________________
jakartaee-platform-dev mailing list

jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list

jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list

jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list

jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

_______________________________________________
jakartaee-platform-dev mailing list

jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

_______________________________________________
jakartaee-platform-dev mailing list

jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev



--


Thanks
Emily
=================
Emily Jiang

ejiang@xxxxxxxxxx

_______________________________________________
jakartaee-platform-dev mailing list

jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev