That would correspond well with „jsonb“. Werner Sent from Mail for Windows 10 "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. 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 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
-- Director of Open Source Projects | Eclipse Foundation, Inc. |