the process for the use of a trademark (such as "asciidoc") by
other projects or groups. This alternate project (asciidoc-hs) should
send a note to license@xxxxxxxxxxx asking for permission to use it. Or,
you could do it on their behalf (if you support this usage). We had
a similar situation with MicroProfile since there were other user groups
and activities that wanted to use the "MicroProfile" trademark.
We encouraged this usage, but it still had to go through the EF for
--------------------------------------------------- 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
Barbero <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx> To:
for new Eclipse projects <incubation@xxxxxxxxxxx> Date:
Re: [incubation] Question about trademark protection (AsciiDoc) Sent
As the AsciiDoc language specification
gets underway under the umbrella of the AsciiDoc Working Group, I'm curious
to know how the process for protecting the trademark works (in this case,
AsciiDoc). One of the main reasons we chose the Eclipse Foundation to host
the specification is to prevent the AsciiDoc name from being used in ways
that dilute its meaning. To cite a concrete example, we received the following announcement on the
AsciiDoc WG list about a new project named asciidoc-hs that aims to develop
a new processor for AsciiDoc. Here's that message: https://www.eclipse.org/lists/asciidoc-wg/msg00110.html
I want to state right up front that we in no way want to discourage this
effort. The goal of the AsciiDoc WG is to encourage the creation of multiple
implementations. However, right now, there's no official spec or TCK in
place for the AsciiDoc language, so it's not possible for a library to
claim it parses AsciiDoc (apart from grandfathered projects like Asciidoctor
and AsciiDoc Python). And since the project cannot yet self-certify as
compliant, our understanding is that the trademark "asciidoc"
cannot be used in the name.
What's the process for handling this situation? Will the Eclipse Foundation
help with situations like this? How serious is the Eclipse Foundation about
protecting its trademarks? How do we communicate with the project maintainer(s)
that the AsciiDoc name cannot be used until the software is compliant with
the spec (which depends on the existence of a TCK)? And in what way can
the name be used once it is?