Re: [jakarta.ee-spec.committee] JAXB restructuring

[Werner Keil <werner.keil@xxxxxxx>]

That would correspond well with „jsonb“.

 

Werner

 

Sent from Mail for Windows 10

 

From: Wayne Beaton
Sent: Tuesday, May 28, 2019 23:16
To: Bill Shannon
Cc: Jakarta specification committee
Subject: Re: [jakarta.ee-spec.committee] JAXB restructuring

 

"xml-binding" feels too wordy to me for a short name, but it would work. Did we consider "xmlb"?

 

It's common that the short name is used in Java package names (e.g. the Eclipse EGit Project has short name "egit" and Java packages "org.eclipse.egit.*"). I'm not adding this as a requirement, but rather am adding it to provide a bit more information about how we traditionally use short names.

 

To constraint as I understand it is to avoid names and acronyms that conflict with Oracle's stable of registered and common-law trademarks. While I can appreciate a desire to avoid potential confusion with JCP acronyms, I believe that it is unreasonable to take "J" off the table.

 

Wayne 

 

On Tue, May 28, 2019 at 4:50 PM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

It may be inevitable that the community will acronym-ize these names, but we were trying to choose names where that would be less likely.  And personally I believe we should avoid "J" acronyms so as not to cause confusion with the existing JCP spec acronyms.

Is "xml-binding" not a good enough short name?

Wayne Beaton wrote on 5/24/19 7:07 AM:

Short names can only use alphanumerics and dashes (no dots). Short names need to be unique across our project space. We use these short names in web URLs, download directories, ..., so concise is better. 

 

How about "jxb"?

 

For now the full id of the project will be "ee4j.jxb".

 

There's a little more about this in the handbook.

 

Wayne

 

On Wed, May 22, 2019 at 3:19 PM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

David Blevins wrote on 5/22/19 10:52 AM:
> As we're doing this restructuring I get increasingly uncomfortable we're not
> splitting specifications and implementations into distinct brands; Jakarta and
> EE4J
>
> These repos are Specification Projects and need Jakarta branding:
>
>  - https://github.com/eclipse-ee4j/jaxb-api
>  - https://github.com/eclipse-ee4j/jaxb-tck
>
That raises the issue of exactly what Eclipse "short name" we should use for
things like this.

Assuming the new spec name is "Jakarta XML Binding", would the short name be
"xml-binding" or "jakarta.xml-binding" (with corresponding GitHub repo names of
https://github.com/eclipse-ee4j/xml-binding or
https://github.com/eclipse-ee4j/jakarta.xml-binding)?  If the namespace scope
for these short names is relative to EE4J, the former is probably fine.

_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee

 

--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

 

_______________________________________________

jakarta.ee-spec.committee mailing list

jakarta.ee-spec.committee@xxxxxxxxxxx

To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee

 

 

--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.