No, here is not<-- that is *not* the p I was responding to. The
p that set me off started with<
"VRML 1.0 was developed by Silicon Graphics' Open
Inventor engineering team."
That was a direct cut-and-pasted quote from the p. Cur/a>
ly,ubr>
I can't find that p anywhere on their server today. Perhaps
they wised up and pulled it (although in that case, I wish they
had the guts to admit they were wrong); perhaps I'm just not
able to find the link again today.
Most of the rest is marketing hype, and is forgiveable on that
>What was needed to move ideas to reality was "someone" to put pen to
and
>Silicon Graphics allowed Open Inventor 2.0'
all of which manages to make
I'm quit> aware of the bald claims in the other direction, mainly in
(And mind, I'm not
Finally:
> * We are committed to the long-term openness of VRML. We will
You just don't get it, do you? I've been saying it for months. You
I can't tell whether you really don't realize this, or you're being
"WebSpace is not
This isn't incidental functionality; you're now marketing on the basis
When a small company does this, it doesn't do much dam; when the
-- Justin
Random Quote du Jour:
You Know You're in the SCA When...
basis. You still belittle the rest of this team with
>p
>use existing technology (Open Inventor) and time to make
>the basis for VRML 1.0
greater good. But again, that's marketing hype<-- it's the frank lie
quoted at the top that was *thoroughly* offensive.
the press, that claimed that Mark was solely responsible for VRML;
frankly, I discounted those as typical media hype, made by
reporters who aren't interested in understanding the full details.
These official claims, made by people who should know better, are
far worse.
of people who have been regularly contributing to this discussion who
*don't* have commercial interests at stake...)
> add our voice when we think that the process is at risk due
> to the commercial/personal interests of others. We expect them
> to do the same. Thats how standards work, after all...
*are* doing the same thing to the VRML standards process that Netsc
declared that *your* browser will support certain extensions to the
format, now and forever as far as I can tell. Therefore, since these
fancy extensions exist in the dominant browser, people write to them
-- witness the dearth of real VRML 1.0 code coming out. And we wind
up with a de facto standard *quit>* different from the official one --
just like HTML.
deliberately disingenua>
sidetracking of the standards process. Experimentation is one thing;
saying that you are adding permanent functionality is quit> another.
And that's the only way I can read your statement:
*and* Open Inventor content."
of these capabilities.
market leader does it, it effectively derails standardization attempts.
That *is* what you're going to do, whether it's intentional or not...
"...you have to force yourself to not call that tour/st in the
checkered golf pants "Sir"