Hi Dan, It's not my area of expertise, but I'd suggest (if you did not do it already) you read the Foundation trademark usage guidelines (https://www.eclipse.org/legal/logo_guidelines.php <https://www.eclipse.org/legal/logo_guidelines.php>) and the supplement made by the Jakarta EE WG for their own trademark guidelines (https://jakarta.ee/legal/trademark_guidelines/ <https://jakarta.ee/legal/trademark_guidelines/>).
North American offices are closed until July 6th, but I'm sure they will come back to you after that with more details. Cheers, Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > On 1 Jul 2020, at 23:25, Dan Allen <[email protected]> wrote: > > To introduce myself, I'm a representative from the lead organization for the > AsciiDoc Working Group > (https://www.eclipse.org/org/workinggroups/asciidoc-charter.php > <https://www.eclipse.org/org/workinggroups/asciidoc-charter.php>) and > Language Specification > (https://projects.eclipse.org/proposals/asciidoc-language > <https://projects.eclipse.org/proposals/asciidoc-language>) at the Eclipse > Foundation. I'm also the maintainer of the Asciidoctor project, which has > served as the steward for the AsciiDoc language. > > 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 > <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? > > I look forward to your guidance. > > Sincerely, > > Dan Allen > > p.s. We have a similar issue with libasciidoc, found at > https://github.com/bytesparadise/libasciidoc > <https://github.com/bytesparadise/libasciidoc>. > > -- > Dan Allen, Vice President | OpenDevise Inc. > Pronouns: he, him, his > Content ∙ Strategy ∙ Community > opendevise.com <https://opendevise.com/> > _______________________________________________ > incubation mailing list > [email protected] > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/incubation
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ incubation mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/incubation
