[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [starter-dev] [jakarta.ee-community] Full vs Platform
|
Closing the loop on this matter. Please look here for the
resolution (not ideal in my opinion but an improvement over
current state):
https://github.com/eclipse-ee4j/starter/issues/238#issuecomment-1522200139.
On 4/5/2023 8:28 AM, Reza Rahman wrote:
Response in-line for context. Good discussion points, certainly.
On Tue, 4 Apr 2023 at 11:07, mengqy <mengqy@xxxxxxxxxxxx>
wrote:
In fact,
furthermore, I have a suggestion new here maybe not
be relevant to the current topic which is:
4\ One
Jakarta EE to the world.
To
simplify and focus our promotion resource on one
thing and get the best from it, maybe we do not need
to highlight too much the Web and the Core on the
release page of the official site, etc., we say to
the world Jakarta EE is the cloud-native Java
specification, people just need to know one thing is
that Jakarta EE is both for web and microservice,
but no need to know the detail in profiles in the
first time, this will simplify the understanding of
Jakarta EE and be good to promote it in the long
run.
Web and Core profiles can still have
their development plan, certification plan, etc. But
no need to show all the content and description in
the official content. Vendors or people who want to
know the detail, or to certificate, can contact us
for more information. So we can focus all of our
resources to build only one brand, developers can
also talk about one thing and not need to discuss
the difference between like this.
RR: I think this again comes down to how one chooses to see the
somewhat ambiguous concept of the "Platform" and how it relates
to profiles. In my view, we should avoid giving what is
effectively the "Full Profile" (the term used by Red Hat)
significant special status. This may prove to be very important
as things like the Core Profile potentially make profiles even
more relevant than in the past. That's the thought behind how
things are outlined in the UI and Archetype now.
That said, this is also perhaps something that we should not
make a firm decision in the starter project but bring it to to
the Platform mailing list for consensus and guidance for us to
implement.
------------------ Original ------------------
Date: Tue, Apr 4, 2023 12:52 PM
Subject: Re: [jakarta.ee-community] Full
vs Platform
Agree with removing the profile
Hi,
Maybe just remove
'profile' from the title:
- Web Profile
- Core Profile
Maybe even a better solution
is to rethink the whole Platform/Profile
option in the Starter. Now, the option’s
title is “Jakarta EE Profile”, but (full)
Jakarta EE Platform is not a profile
itself:
What about changing it to:
Jakarta EE API
collection:
- Jakarta EE Platform
- Web Profile
- Core Profile
What do you think?
Ondro
Another response on
Twitter, more towards using Jakarta
EE Platform rather than Full
Platform:
Also sharing the
conversation with the
broader community on the
mailing lists.
Thanks
Ondro for sharing
the conversation
with the broader
community. Hopefully
we will get a bit
more independent
user feedback on the
subtle, but real
problem some of us
have observed for
some time now.
If this
remains an
unresolved
discussion on
Friday, I’ll bring
it up to the
platform. I believe
it is legitimate
discussion there
too.
I
am not so
sure. I don’t
think things
are so
draconian that
we couldn’t
add a simple
parenthetical
term that may
in practically
aid usability.
I think the
least we can
do is hear
people out.
To
be honest, I
don't see why
this has to be
debated any
longer.
The
Platform
Project is
pretty clear
on the
terminology.
It's not up to
this project
to change
that.
Ivar
Please
consider
weighing in on
this matter,
especially as
a committer. I
think by this
Friday should
be sufficient
time to
resolve this
matter in one
direction or
the other.
I'm
strongly in
favor of
keeping the
word "full" in
the option.
Probably
something like
Platform
(full), or
full Platform,
with "full"
all in lower
case, not
"Full".
My
reasoning:
Although
the name of
the full
specification
is just
Jakarta EE
Platform,
there are
several
mentions of
the word
"full" in the
Platform spec.
Including
"full
platform" in
the section
2.2 Profiles:
https://jakarta.ee/specifications/platform/10/jakarta-platform-spec-10.0.html#profiles,
which
specifically
mentions
"Jakarta EE
platform”
umbrella as
something that
unites all
profiles or
"the full
platform".
Here a
screenshot, my
email
continues
below:
So, I
would say that
Platform
is generally
used for the umbrella
over all
profiles and
full platform,
while "full
platform"
means the whole
Jakarta EE
Platform.
I believe
that's how
most other
people
understand it
and use the
terms. Also a
lot of vendors
use "Full" to
refer to the
Jakarta EE
Platform, and
Web to refer
to the Web
Profile.
Examples:
Hi Reza,
I had the
same comment
regarding the
`full` instead
of `platform`.
We had to
correct people
saying `full`
in the past
and now I
think the
correct word
`platform` is
used across
the board. I
will vote for
`Platfiorm`
not saying
anything such
as `Full` to
be consistent
with the
specification
release.
Thanks
Emily
To
be honest, I
think this is
a usability
hiccup we
basically have
with Jakarta
EE. We have
the notion of
profiles, but
there isn’t
actually a
“Full
Profile”. It’s
just the
“Platform”. In
my experience,
this
invariably
confuses
newcomers.
I
tried to
reconcile this
by simply
saying “Full
Platform” in
the UI. I
think either
“(Full)
Platform” or
“Platform
(Full)” does
the trick too.
What
do others
think? To be
clear, I am
not
categorically
opposed to
just saying
“Platform”. I
don’t think
it’s the best
but it is
workable. It’s
certainly what
the actual
specification
says.
P.S.:
I opposed this
nomenclature
almost ten
years ago.
Bill and Linda
had many
opinions I
never fully
agreed with
including
keeping EJB
going much
past its
expiration
date. To me
this is yet
another one of
the Bill/Linda
legacies.
_______________________________________________
starter-dev
mailing list
starter-dev@xxxxxxxxxxx
To unsubscribe
from this
list, visit https://dev.eclipse.org/mailman/listinfo/starter-dev
--
_______________________________________________
starter-dev
mailing list
starter-dev@xxxxxxxxxxx
To unsubscribe
from this
list, visit https://dev.eclipse.org/mailman/listinfo/starter-dev
_______________________________________________
jakarta.ee-community mailing
list
jakarta.ee-community@xxxxxxxxxxx
To unsubscribe from this list,
visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
--
Best
regards,
Walid
Largou
Solution
Architect / IBM Champion
Power
Maroc
320
Bd Zertouni 6th Floor, Casablanca, Morocco
![null]()
This message is confidential .Its contents do
not constitute a commitment by Power Maroc
S.A.R.L except where provided for in a written
agreement between you and Power Maroc S.A.R.L.
Any authorized disclosure, use or dissemination,
either whole or partial, is prohibited. If
you are not the intended recipient of the
message, please notify the sender immediately.
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community