“
The W3C consortium announced a campaign to identify earlier use of technologies noted in Apple’s patent 7,743,336, filed May 10, 2006. This patent prevents the adoption of a specification defining an API for controlling access to web widgets. ” - OpenNet
I will reveal the essence of disassembly.
It is very strange to receive such a setup from the Yabloko ... They patented an electronic signature of the content downloaded from the Internet. In particular, the patent describes the architecture of working with widgets signed with an electronic key, in which there is a detailed description of such concepts:
Dashboard, Multiple Dashboards, Dashboard Client, Dashboard Server, Widget Format, Widget Security, Widget Security Manager, Security Module, Security Action Manager, Widget Security Process, Detection of Security Events, Download Security Events, Post-Launch Security Administrative Security, Content Security, Resource Access Security
')
I feel that Apple will relinquish its positions in the W3C, and WebKit will go to Google / Nokia / KDE.
Wishing to join the W3C initiative -
go hereFootcloths with patents can be viewed here and here.
Here are the titles of the patents themselves in free translation:
Patent UWB 7743336:There are a number of ways that you can use it.
The security system of a widget, the method by which a security compromising event is detected, determines the level of its risk and takes actions based on that risk.
Patent application UWB 20070101146:A cryptographic hash of content (eg, applications, documents, widgets, software, music, videos, etc.). The ticket file can be cryptographically signed to ensure its authenticity. The user has been able to download the user’s system (eg, from computer, mobile phone, media player / recorder, personal digital assistant (PDA), etc.). The user has to ensure that the content has not been compromised. This is a list of information such as the Uniform Resource Identifier (URI) and other meta-data (eg, hash type, content information, public key, size, version, etc.).
A cryptographic hash of content (for example, applications, documents, widgets, programs, music, video, etc.) that was created and published on the Web (or something similar) as part of a ticket file. A ticket can be cryptographically signed to confirm its authenticity. Ticket and content can be downloaded separately (for example, from different websites) to the user's system (eg computer, mobile phone, media player or media encoder, personal organizer, etc.). The user's system checks the ticket signature and hash contents to ensure that the content has not been compromised. A ticket may contain information related to downloading content (for example, URI) and other meta-information (eg, hash type, content information, public key, size, version, etc.)
I apologize in advance to all of the ministers in this topic, obviously he will become the topic of evil.