Jay! Another sleepiness night due to the stress of how to deal with
unplanned actions of others. I'm not one who thrives on stress, and
not one who enjoys living off 2hrs of sleep. I hate existing like
this, it's neither healthy for my short or long term health.
What makes things difficult is th
On Sat, 30 Jun 2018 at 03:51, Chris Hanson wrote:
>
> Ok. I've done this.
>
> https://github.com/KhronosGroup/Vulkan-Ecosystem/issues/36
>
> Maybe that will get their attention and some response.
Guys, I'm in transit on holiday, it's supposed to be a time for me to
relax, not to start thinking ab
Ok. I've done this.
https://github.com/KhronosGroup/Vulkan-Ecosystem/issues/36
Maybe that will get their attention and some response.
On Fri, Jun 29, 2018 at 2:54 PM Michael Weiblen
wrote:
> I'd suggest creating a ticket at
> https://github.com/KhronosGroup/Vulkan-Ecosystem/issues
>
> -- mew
>
I'd suggest creating a ticket at
https://github.com/KhronosGroup/Vulkan-Ecosystem/issues
-- mew
On Thu, Jun 28, 2018 at 9:27 AM, Robert Osfield
wrote:
> On Thu, 28 Jun 2018 at 14:53, Eric Sokolowsky wrote:
> > Trademark holders *must* defend their trademarks, or they lose them.
>
> Indeed thi
On Thu, 28 Jun 2018 at 14:53, Eric Sokolowsky wrote:
> Trademark holders *must* defend their trademarks, or they lose them.
Indeed this is true. It's only part of the story though.
Khronos mission is to develop and promote open APIs, as part of this
they trademark projects they undertake, they
Trademark holders *must* defend their trademarks, or they lose them.
On Mon, Jun 25, 2018 at 6:43 PM, Chris Hanson wrote:
> I think the Vulkan compliance tests (and name usage) only applies to
> implementations OF the Vulkan API. I don't think it applies to software
> USING Vulkan.
>
> I think V
uiries for me to
> discuss.
>
> We can take this off list if that is best.
>
> John "Double Smiley" Richardson
>
> -Original Message-
> From: osg-users [mailto:osg-users-boun...@lists.openscenegraph.org] On
> Behalf Of Robert Osfield
> Sent: Monday, Ju
lf Of Robert Osfield
Sent: Monday, June 25, 2018 8:18 PM
To: OpenSceneGraph Users
Subject: Re: [osg-users] The naming of VulkanSceneGraph
On Mon, 25 Jun 2018 at 17:01, Chris Hanson wrote:
> Ok, so does anyone have any actual current contacts with Khronos? I have a
few distant ones but they ar
I think the Vulkan compliance tests (and name usage) only applies to
implementations OF the Vulkan API. I don't think it applies to software
USING Vulkan.
I think VulkanSceneGraph is a good and descriptive name, I just don't want
to see a lot of activity sunk into that name and then have it torped
On Mon, 25 Jun 2018 at 17:01, Chris Hanson wrote:
> Ok, so does anyone have any actual current contacts with Khronos? I have a
> few distant ones but they aren't terribly responsive.
I have met a few from the ARB/Khronos over the years but don't have
any personal contacts. If people do then pl
Hi,
https://www.khronos.org/vulkan/adopters/
I think this page will alleviate anymore discussion, at
least it sounds pretty straight forward to me that as long as
VulcanSceneGraph passes their tests it seems OK to use the name.
Of course I am no a lawyer either but this text seems
Ok, so does anyone have any actual current contacts with Khronos? I have a
few distant ones but they aren't terribly responsive.
On Mon, Jun 25, 2018 at 2:39 AM Robert Osfield
wrote:
> On Mon, 25 Jun 2018 at 09:30, Jorge Izquierdo Ciges
> wrote:
> > It is a little bit sad to lose the Open part
On Mon, 25 Jun 2018 at 09:30, Jorge Izquierdo Ciges wrote:
> It is a little bit sad to lose the Open part of the name, why not go for Open
> Vulkan Scene Graph or Open Scene Graph: Vulkan
>
> (The second works better as a serialized book title :P )
"Open Vulkan Scene Graph" doesn't avoid the Vul
Hi all, my 2 cents for the name.
It is a little bit sad to lose the Open part of the name, why not go for
Open Vulkan Scene Graph or Open Scene Graph: Vulkan
(The second works better as a serialized book title :P )
They are a little more clear that we are not stepping on the Kronos IP name
right
On Sat, 23 Jun 2018 at 22:31, Terry Welsh wrote:
> Is it worth asking if this project will be a scene graph or a
> rendering engine?
It'll be a rendering+compute API based Vulkan that represent the Scene
as a Graph. VulkanSceneGraph tells people exactly what it is,
anything else moves away from
On Sat, 23 Jun 2018 at 11:13, Tim Moore wrote:
> Just call it VSG!
That's the planned namespace :-)
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
> Just call it VSG!
There has already been a Vega Scene Graph available from MultiGen
Paradigm for years and years, so I would shy away from VSG or anything
abbreviated VSG. After all, there was some confusion with the two OSGs
last time around.
Is it worth asking if this project will be a scene
Just call it VSG!
Tim
On Fri, Jun 22, 2018 at 3:27 AM, Robert Osfield
wrote:
> On Fri, 22 Jun 2018 at 00:55, Maurizio Vitale wrote:
> > well the case of Apple (computer) vs Apple (the music company) was very
> similar: a common word and very different industries (at the time Apple was
> not in
On Fri, 22 Jun 2018 at 00:55, Maurizio Vitale wrote:
> well the case of Apple (computer) vs Apple (the music company) was very
> similar: a common word and very different industries (at the time Apple was
> not in the music/multimedia industry).
Khronos, a standards body, and an open source pro
>
> If the branding is very distinct, and the word itself isn't something that
> can be owned as there is lots of prior art in active use
>
well the case of Apple (computer) vs Apple (the music company) was very
similar: a common word and very different industries (at the time Apple was
not in the
Hi Chris,
I am not a lawyer, but I think this is in a muddy area and it concerns
> me. I don't think anyone here can answer this, probably the only way to
> know is to ask Khronos directly for their interpretation in writing. But I
> suspect the answer will be "find a different name that doesn'
Something came up in a conversation earlier this week that I thought I
would point out.
Is VulkanSceneGraph potentially opening itself to
trademark-related hassle by incorporating the trademark "Vulkan" name into
its own name?
The Khronos trademark guidelines are here:
https://www.khronos.o
22 matches
Mail list logo
