[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Let's get real on W3C XForms 1.0 (why it stinks, to day)

  • From: PaulT <pault12@p...>
  • To: Ann Navarro <ann@w...>, Don Park <donpark@d...>,xml-dev@l...
  • Date: Fri, 05 Oct 2001 16:31:21 -0700

xforms not working


> > > >1) do their best to ensure against patent fringement in our specs
> > > >2) disclose patents affecting any W3C activities or forfeit profit
from
> >them
> > > >3) will challenge legally any patent disputes that may arise after
> > > >recommendation
> > > >4) will deprecate recommendations if patent challenge fails
> > > >
> > > >I think such a policy will provide reasonable level of protection
against
> > > >patents in standards.
> > >
> > > Unfortunately, that's really what they have now, and it clearly hasn't
> >worked.
> >
> >If it *clearly*  hasn't worked, may I ask for some example?
>
> Nearly every patent claim faced by the W3C.

According to the principles above, this is (?) just covered
by (3) and (4).

Don says: "the principles are 1,2,3,4"

You say: "These principles is the currect situation
with W3C and it has not worked".

I'm trying to understand what do you mean by
'has not worked'.

> Let's consider:
>
> CSS -- Microsoft participated in the WG - then later claimed "oh, we did
> that years ago, we own the patent". Their AC rep claimed no knowledge of
> prior claims/property -- did his "best" to disclose.

So, there are some *particular* problem, influencing
the creative work of W3C, other than MS
trying to steal something again?

What is the *problem* here?

Do I understand right that  some parts of CSS have been
thrown away only because MS has tried to claim that
CSS is yet another invention of MS? Please confirm.

If this is not the case, may I repeat - what is *particular*
problem with CSS, that can not be resolved
by the principles, descibed above ( according to
your words - those principles are 'de-facto'
situation in W3C already - am I right? ).

> XPointer - Sun -- "we helped create this, heck, even were primary driving
> force in the WG, and "oops", we have a patent on it".

The same question. I don't see any difference between
these two ( CSS, and XPointer ) other than ... maybe ...
XPointer it is kinda useless. Comparing to CSS.
But I don't think that's relevant.

> Ad nauseum.

Let us understand what is the problem? Really. I honestly
don't get it.

I think it is simple. Either W3C makes it simple for
MS or other big guys to make stupid patent claims,
or it does not. Sofar W3C was trying to restrict
those 'inventors' and I think that *it*has*worked*just*fine*.

You say - it has not. Why?

Rgds.Paul.



PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.