Next in thread → Next in month →

RE: [soa-rm] Good article about OASIS IPR

From
Jones, Steve G <>
Date
2005-11-22T16:28:41+00:00
ID
Thread
RE: [soa-rm] Good article about OASIS IPR
Its certainly interesting

 

“, as evidenced by the most popular
Web server's (Apache) inability to embrace one of the most important new
security standards (WS-Security), the licensors of the technology behind
certain, supposedly open standards are realizing that those standards could
face market rejection (which in turn could lead to product rejection) unless
the license incompatibilities between the market's favorite software and the
most important standards are resolved.”

 

This will probably come as a surprise to
the Axis group @ apache.org, and certainly the Apache(web server) team, both
that Apache (web server) should worry about WS-Security and that Axis aren’t
supporting WS-Security.

 

There are some interesting points in the
article but a lots of misunderstanding (and wrong information) about how things
operate.  It tends to miss that many of these groups (look at Paul Fremantle
over on WS-RX) have active OSS participation and its often the case that OSS are first out the door with the standards (not that they lag).

 

Cracker of a comment at the end

 

“Just not by enough
people because it's hard to fight the FUD and get the word out” 

 

I’m not sure he has cleared the
debate up for me, especially given the new OASIS IP licensing policy.

 

Steve

 

 

 

From:
prasanta behera [mailto:] 

Sent: 22 November 2005 16:15

To: 

Subject: [soa-rm] Good article
about OASIS IPR

 

http://blogs.zdnet.com/BTL/?p=1597

/Prasanta

This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient,  you are not authorized to read, print, retain, copy, disseminate,  distribute, or use this message or any part thereof. If you receive this  message in error, please notify the sender immediately and delete all  copies of this message.
Next in thread → Next in month →