Yeah, I don't blame Ivar for linking to
the .adoc as source (they get aggregated into the spec
doc from there) for now. We don't have the files checked
into batch-api as source .xsd files.
I'd like to move batch to jakartaee-schemas
we also used a common NS in the past.
We're not going to be changing frequently
(so I don't think I need to be a committer there, a PR
would work).
If we're OK with that plan, I'll go ahead
and open an issue (to remind me to do this).
Though of course will wait to see https://github.com/jakartaee/jakarta.ee/issues/592 close before finalizing the new namespace of:
https://xmlns.jakarta.ee/xml/ns/jakartaee
Thanks,
------------------------------------------------------
Scott Kurz
WebSphere Batch and Developer Experience
skurz@xxxxxxxxxx
--------------------------------------------------------
Bill
Shannon ---03/18/2020 12:07:32 PM---Very nice, thank
you! Can you make it so the first column doesn't
scroll? The spreadsheet is very
From: Bill Shannon <bill.shannon@xxxxxxxxxx>
To: JakartaEE
Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>,
Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>
Date: 03/18/2020 12:07 PM
Subject: [EXTERNAL] Re: [jakartaee-spec-project-leads]
XML namespace under Jakarta
Sent by: jakartaee-spec-project-leads-bounces@xxxxxxxxxxx
Very nice, thank you! Can you make it so the first column
doesn't scroll? The spreadsheet is very wide and it's hard
to correlate the schema name with the owner.
Also, the batch file schema source being adoc files seems
very weird, are you sure that's correct? If I click on the
links, what's displayed looks like a normal xsd file; I
don't know why they're named as adoc files.
Note also that all the schemas in the jakartaee-schemas repo
are generated files. They're generated using a _javascript_
program run with the Mozilla Rhino scripting engine that
processes some files that define parts of the schema. The
source links in the spreadsheet (*.xsds - xsd source) point
to the top level source file for each of the schemas.
Finally, note that most of the files managed in the
jakartaee-schemas repo are "owned" by the various spec
projects that define them. We should decide whether
Committers from some of these other spec projects should
also be Committers on the platform project in order to
maintain their schemas, or whether we can just depend on
them submitting pull requests to get their changes
incorporated.
Ivar Grimstad wrote on 3/18/20 3:50 AM:
Hi,
I have created a spreadsheet with a list of the schemas
for Jakarta EE 9 and the projects responsible for them.
The source I used was http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/index.html#8
Please have a look and add/edit where needed.
https://docs.google.com/spreadsheets/d/1cCGLYsCVz9pkUnMCdwaiLraepcxuemMbmUymgdMKUQY/edit?usp=sharing
Ivar
On Mon, Feb 3, 2020 at 8:25 PM Kevin Sutter <sutter@xxxxxxxxxx>
wrote:
Scott,
We don't have a Platform call tomorrow. Tomorrow's
time slot is reserved for the PMC.
As long as the adopted name doesn't directly affect
how it is hosted, then I'm good with this
direction. I've posted this question to the Issue:
https://github.com/jakartaee/jakarta.ee/issues/592#issuecomment-581576314
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: Scott Stark <starksm64@xxxxxxxxx>
To: JakartaEE Spec
Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>
Date: 02/03/2020 12:16
Subject: [EXTERNAL] Re:
[jakartaee-spec-project-leads] XML namespace under
Jakarta
Sent by: jakartaee-spec-project-leads-bounces@xxxxxxxxxxx
This issue is holding up RC releases as one cannot
have a proposed final release without the schemas
having a proper namespace. Can we just bring this up
for a decision on tomorrow's platform call and move to
adopt https://xmlns.jakarta.ee/xml/ns/jakartaee xas the
namespace? The details of the 592 issue regarding how
this is hosted under the jakarta.eewebsite
can be resolved in parallel.
On Wed, Jan 15, 2020 at 9:01 AM Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>
wrote:
Hi all,
Thanks, Bill and Gunnar for providing input!
I have created an issue here: https://github.com/jakartaee/jakarta.ee/issues/592
Please comment on this issue if you see something I
have missed or that is wrong...
Ivar
On Wed, Jan 15, 2020 at 8:28 AM Gunnar Morling <gmorling@xxxxxxxxxx>
wrote:
Thanks for the info, nice timing :)
If it actually should be a resolveable URL, I'd
suggest to go for http*s*, so to play nicely with the
general trend towards TLS by default.
That said, does it really have to be a resolveable URL
to begin with, or was it also considered to use an URN
namespace (https://www.w3.org/TR/uri-clarification/#urn-namespaces)?
Such as "urn:jakartaee:validation:configuration"?
I've been bitten a few times in the past where
misconfigured tools or libraries would try and
download a schema from the given namespace URL instead
of using a local version of the file. That issue is
avoided by using URN namespaces which don't create the
perception of being resolveable URLs to begin with.
Both would work from my PoV, but I thought I'd bring
it up so do see what others here think.
Best,
--Gunnar
----- Original Message -----
> From: "Bill Shannon" <bill.shannon@xxxxxxxxxx>
> To: "JakartaEE Spec Project Leadership
discussions"
> <jakartaee-spec-project-leads@xxxxxxxxxxx>,
"Steve Millidge (Payara)"
> <steve.millidge@xxxxxxxxxxx>
> Sent: Wednesday, 15 January, 2020 8:22:22 AM
> Subject: Re: [jakartaee-spec-project-leads] XML
namespace under Jakarta
> Just for the record, the proposed path was
> to replace http://xmlns.jcp.org/xml/ns/javaee/...
with
> http://jakarta.ee/xml/ns/jakartaee/...
> So if the old URL has "javaee" in the file name
part of the path,
> it would be replaced by "jakartaee" in the file
name part of the new
> path, and the host would change to jakarta.ee.
> But we need to wait for Ivar and Eclipse to make
a final decision.
> They might decide that they want a subdomain (xmlns.jakarta.ee)
> to better be able to split the traffic based on
load.
> Steve Millidge (Payara) wrote on 1/14/20 2:05 PM:
> > This was discussed on the platform call
today. My recollection is that Ivar
> > was going to discuss internally at Eclipse
and get a resolvable URL we can
> > use on the Jakarta.ee website and once that
is agreed we'll put out a
> > namespace recommendation. I think the idea
was to add also add jakartaee
> > in the path before the spec name as well as
the hostname.
> >
> > Steve
> >
> > -----Original Message-----
> > From: jakartaee-spec-project-leads-bounces@xxxxxxxxxxx
> > <jakartaee-spec-project-leads-bounces@xxxxxxxxxxx>
On Behalf Of Gunnar
> > Morling
> > Sent: 14 January 2020 21:43
> > To: JakartaEE Spec Project Leadership
discussions
> > <jakartaee-spec-project-leads@xxxxxxxxxxx>
> > Subject: [jakartaee-spec-project-leads] XML
namespace under Jakarta
> >
> > All,
> >
> > Is there already an agreed on shared
namespace prefix for XML descriptors
> > of the different specs?
> >
> > E.g. in Bean Validation we have
> > http://xmlns.jcp.org/xml/ns/validation/configurationand
> > http://xmlns.jcp.org/xml/ns/validation/mapping;
is there any pattern to
> > adopt for Jakarta EE 9?
> >
> > If there's none yet, something like
> > https://xmlns.jakarta.ee/xml/ns/validation/configurationmight
be a first
> > idea? Or rather something that doesn't
indicate an actually resolveable
> > URL?
> >
> > Thanks,
> >
> > --Gunnar
> >
> >
_______________________________________________
> > jakartaee-spec-project-leads mailing list
> > jakartaee-spec-project-leads@xxxxxxxxxxx
> > To change your delivery options, retrieve
your password, or unsubscribe
> > from this list, visit
> > https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
> >
_______________________________________________
> > jakartaee-spec-project-leads mailing list
> > jakartaee-spec-project-leads@xxxxxxxxxxx
> > To change your delivery options, retrieve
your password, or unsubscribe
> > from this list, visit
> > https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
> >
> _______________________________________________
> jakartaee-spec-project-leads mailing list
> jakartaee-spec-project-leads@xxxxxxxxxxx
> To change your delivery options, retrieve your
password, or unsubscribe from
> this list, visit
> https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
--
Ivar
Grimstad
Jakarta EE
Developer Advocate | Eclipse Foundation,
Inc.
Eclipse
Foundation: The
Platform for Open Innovation and Collaboration
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
--
Ivar
Grimstad
Jakarta EE
Developer Advocate | Eclipse Foundation, Inc.
Eclipse
Foundation: The Platform for
Open Innovation and Collaboration
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads__;!!GqivPVa7Brio!JDt5gMLnfD1Ve0Ra03BKm4aZbyAcojLp8AkXIt7Axg5dtXaosb2ZRvI3VU3aYkf5eg$
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads