This page permanently redirects to gemini://gemini.techrights.org/2008/02/17/data-and-signal-patents/.

● 02.17.08

●● Data and Signals Seen as Patentable in the USPTO

Posted in America, Open XML, Patents, Protocol, Standard at 11:18 pm by Dr. Roy Schestowitz

Several days ago, a couple of OOXML patent issues were brought back to the surface. Then first was incompatibility of Microsoft’s promise with the GNU GPL. The second was its incompatibility with small and lesser-known developers. OOXML was made by the rich, to serve the rich (Microsoft Office) and be caught up by the rich (e.g. Apple).

=> incompatibility with small and lesser-known developers | Apple

Here is a timely news story which teaches us (yet again) why software patent encumbrances can totally ruin a protocol or a standard. These encumbrances shatter to pieces competitors.

=> ↺ can totally ruin a protocol or a standard

A suburban Philadelphia firm whose sole business is to buy up technology patents is trying to force large cable operators and major broadcasters to pay substantial license fees on the transmission of digital TV signals and Internet services.

What is the ownership here? Signals. Yes, signals can be an ownership of a person, at least based on the USPTO’s definition, as was confirmed very recently.

=> ↺ was confirmed very recently

USPTO calling data ‘tangible’ result
I want to see how data processing is producing tangible result. Mere processing a data produces new data. And data is not tangible.

By no stretch of imagination can this be seen as acceptable. What’s next? Patenting a song? Patenting a singer’s voice? █

Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.

Permalink  Send this to a friend

=> Permalink | ↺ Send this to a friend


=> Techrights

➮ Sharing is caring. Content is available under CC-BY-SA.

Proxy Information
Original URL
gemini://gemini.techrights.org/2008/02/17/data-and-signal-patents
Status Code
Success (20)
Meta
text/gemini;lang=en-GB
Capsule Response Time
280.386223 milliseconds
Gemini-to-HTML Time
0.83291 milliseconds

This content has been proxied by September (3851b).