I'd ask Eclipse for clarification of what they would like us to
do, regarding their notice from the EFSL.
Since each specification needs this to be updated when it is
included in any component, new or revised (This seems to be
required by the embedded instruction: [title and URI of the
Eclipse Foundation specification
document]), I'd add/extend the copyright date with the new
copyright year.
Since the URL (in my opinion) ought to be referring to the
normative document, I would point to the jakarta.ee/specification
URL. (I would recommend neither of the other two options suggested
since those aren't "normative")
I think we are already allowing prospective material at this site
so pointing to that site should be okay, in my opinion. Once it's
final, the "under development" markings ought to be removed.
So, I think I'm almost giving a plus-one for Hussain's initial
suggestion, but starting at 2018 since that's the initial
copyright of the Specification itself. (I don't know if the
circle-c or circle-r will be a problem in some text file formats)
Regardless what I think -- Eclipse should probably clarify what
they would like (initial years, commas, etc.).
Good, fair
questions.
I'm going to re-post this discussion to the Spec Committee
public
mailing list to allow some additional input. (Not everyone from
that
team follows the Platform mailing list.) Thanks.
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From:
Werner
Keil <werner.keil@xxxxxxx>
To:
jakartaee-platform
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Date:
05/09/2020
16:18
Subject:
[EXTERNAL]
Re: [jakartaee-platform-dev] Question about EFSL notice
Sent
by: jakartaee-platform-dev-bounces@xxxxxxxxxxx
Ok
than go for it, probably just a template saying 2018, the
Jakarta EE 8
year was 2019, so unless there was a Prior art by Oracle that
sounds OK.
Sent
from Mailfor Windows 10
From:
Hussain.NM@xxxxxxxxxxxxx
Sent: Saturday, May 9, 2020 23:15
To: jakartaee-platform-dev@xxxxxxxxxxx
Subject: Re: [jakartaee-platform-dev] Question about
EFSL notice
Both
the javadocs and specification document have copyright year as
2019 in
the Jakarta EE 8 release.
This
got me thinking about the URL, there are three possibilities:
Which
of the above should be used?
Thanks
Hussain

From:jakartaee-platform-dev-bounces@xxxxxxxxxxx
<jakartaee-platform-dev-bounces@xxxxxxxxxxx>
on behalf of Werner Keil <werner.keil@xxxxxxx>
Sent: Saturday, May 9, 2020 08:17 PM
To: jakartaee-platform developer discussions
<jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] Question about
EFSL notice
[External]
I
would have thought 2018, 2020 in this case.
Werner
Sent
from Mailfor Windows 10
From:
Hussain.NM@xxxxxxxxxxxxx
Sent: Saturday, May 9, 2020 11:55
To: jakartaee-platform-dev@xxxxxxxxxxx
Subject: [jakartaee-platform-dev] Question about EFSL
notice
Hi,
The
EFSL notice that is included in the API javadocs and
Specification documents
has the following placeholder line:
The
notice
is:
"Copyright
© 2018 Eclipse Foundation. This software or document includes
material
copied from or derived from [title and URI of the Eclipse
Foundation specification
document]."
Should
this be changed to reflect the copyright years and the
placeholder should
be filled with the specification name and URL like below:
"Copyright
© 2019, 2020 Eclipse Foundation. This software or document
includes material
copied from or derived from Jakarta® Enterprise Beans https://jakarta.ee/specifications/enterprise-beans/4.0/."
Thanks
Hussain
This
e-mail and any files transmitted with it are for the sole use
of the intended
recipient(s) and may contain confidential and privileged
information. If
you are not the intended recipient(s), please reply to the
sender and destroy
all copies of the original message. Any unauthorized review,
use, disclosure,
dissemination, forwarding, printing or copying of this email,
and/or any
action taken in reliance on the contents of this e-mail is
strictly prohibited
and may be unlawful. Where permitted by applicable law, this
e-mail and
other e-mail communications sent to and from Cognizant e-mail
addresses
may be monitored. This e-mail and any files transmitted with
it are for
the sole use of the intended recipient(s) and may contain
confidential
and privileged information. If you are not the intended
recipient(s), please
reply to the sender and destroy all copies of the original
message. Any
unauthorized review, use, disclosure, dissemination,
forwarding, printing
or copying of this email, and/or any action taken in reliance
on the contents
of this e-mail is strictly prohibited and may be unlawful.
Where permitted
by applicable law, this e-mail and other e-mail communications
sent to
and from Cognizant e-mail addresses may be monitored.
This
e-mail and any files transmitted with it are for the sole use
of the intended
recipient(s) and may contain confidential and privileged
information. If
you are not the intended recipient(s), please reply to the
sender and destroy
all copies of the original message. Any unauthorized review,
use, disclosure,
dissemination, forwarding, printing or copying of this email,
and/or any
action taken in reliance on the contents of this e-mail is
strictly prohibited
and may be unlawful. Where permitted by applicable law, this
e-mail and
other e-mail communications sent to and from Cognizant e-mail
addresses
may be monitored. This e-mail and any files transmitted with
it are for
the sole use of the intended recipient(s) and may contain
confidential
and privileged information. If you are not the intended
recipient(s), please
reply to the sender and destroy all copies of the original
message. Any
unauthorized review, use, disclosure, dissemination,
forwarding, printing
or copying of this email, and/or any action taken in reliance
on the contents
of this e-mail is strictly prohibited and may be unlawful.
Where permitted
by applicable law, this e-mail and other e-mail communications
sent to
and from Cognizant e-mail addresses may be monitored.
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev