<div dir="ltr">I'd suggest creating a ticket at <a href="https://github.com/KhronosGroup/Vulkan-Ecosystem/issues">https://github.com/KhronosGroup/Vulkan-Ecosystem/issues</a><div><br></div><div>-- mew</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 28, 2018 at 9:27 AM, Robert Osfield <span dir="ltr"><<a href="mailto:robert.osfield@gmail.com" target="_blank">robert.osfield@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, 28 Jun 2018 at 14:53, Eric Sokolowsky <<a href="mailto:esok127@gmail.com">esok127@gmail.com</a>> wrote:<br>
> Trademark holders *must* defend their trademarks, or they lose them.<br>
<br>
</span>Indeed this is true. It's only part of the story though.<br>
<br>
Khronos mission is to develop and promote open APIs, as part of this<br>
they trademark projects they undertake, they also develop APIs then<br>
promote their use. If Khronos do view VulkanSceneGraph as potentially<br>
infringing then we'll need to discuss with them about granting<br>
permission to use this name, the benefit for Khronos is the it is<br>
significant step in promoting their own cause.<br>
<br>
We have three options:<br>
<br>
1) Ignore the issue, if Khronos decide they want to discuss the name<br>
then deal with it then.<br>
<br>
2) Reach out to Khronos and be co-operative<br>
<br>
3) Change the name to something else less relevant<br>
<br>
Currently, approach 2 is what Chris has kicked off, no response yet,<br>
so we may need to reach out a bit further.<br>
<br>
I am about head off on holiday for a week so won't be doing any<br>
chasing up myself right away.<br>
<br>
With Siggraph coming up this might be a good time to reach out and<br>
chat face to face. I won't personally be attending, but If you are<br>
attending then let us know.<br>
<br>
The project is less than a month old, so I'm not too concerned about<br>
things as they stand right now. If things don't go the way I'd prefer<br>
then we just fallback to 3, the design and code won't change, it'd be<br>
a wasted opportunity and bit of money spent on URLs but nothing major.<br>
<span class="HOEnZb"><font color="#888888"><br>
Robert<br>
</font></span><div class="HOEnZb"><div class="h5">______________________________<wbr>_________________<br>
osg-users mailing list<br>
<a href="mailto:osg-users@lists.openscenegraph.org">osg-users@lists.<wbr>openscenegraph.org</a><br>
<a href="http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org" rel="noreferrer" target="_blank">http://lists.openscenegraph.<wbr>org/listinfo.cgi/osg-users-<wbr>openscenegraph.org</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Mike Weiblen -- Black Hawk, Colorado USA -- <a href="http://mew.cx/" target="_blank">http://mew.cx/</a></div>
</div>