Advertisement
Guest User

Untitled

a guest
Apr 9th, 2015
1,334
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.68 KB | None | 0 0
  1. Patent Troll sent me this:
  2.  
  3. Hi Daniel,
  4.  
  5. Maybe you are already aware of it since we questioned the W3C and Google about it, and sent about the same message, thanks to acknowledge the receipt and redirect to the right service at Mozilla if needed (are you still at Mozilla? Your Mozilla email address seem not to be working, if not thanks if you can let me know who can be the right contact at Mozilla).
  6.  
  7. While trying to participate to different W3C APIs, I completely missed the Web Components specifications, for the reason explained below.
  8.  
  9. We own the patent hereattached, it is in French, trying to translate the specific patent language for the main claim gives:
  10.  
  11. 1- A process to display a gadget coming from a source web page from a web site in a target web page including the following steps:
  12. a) individualization of different objects contained in the source web page, each of them being defined by a proper content and proper description parameters describing a structure of the object
  13. b) selection of at least one of the object in the source page
  14. c) selective extraction, for the selected object, of its description parameters and its content, or of its description parameters alone; and
  15. d) display of the gadget in the target web page, from the description parameters and content, or from the description parameters alone
  16.  
  17. This is very exactly what the "Web Components" specifications are doing, we have checked the anteriority and from our standpoint clearly nothing related did exist before we issued the patent in 2010.
  18.  
  19. Therefore the projects implementing these specifications such as Google Polymer and Mozilla X-Tags, are reusing the concepts of the patent and an exception should be made for them in France.
  20.  
  21. The patent extends the perimeter of the Web Components, since additionnaly it describes methods (called "Extract Widget" [1]) to extract real time web pieces and to retarget it on any devices, such as mobiles.
  22.  
  23. Ironically, Google that is presenting the Web Components as a big revolution in the web development today, did kill all of our projects ([2] to [8]) around this patent some years ago when Google deprecated its Search API, and Google did not seem to really study at that time our queries regarding possible synergies between the patent's concepts and their projects, exactly related to what they are doing today.
  24.  
  25. We are more focusing now on privacy/anonymity projects ([9] and [10]), so we have not checked yet very precisely who could possibly reuse some other parts of the patent but we will.
  26.  
  27. We are willing to transfer the rights of the patent with a reasonable agreement asssuming that it can help us to finance these projects and solve some financial issues we have related to past aborted projects mentioned above, maybe it can be coordinated by the W3C, even if the patent is only covering France we would not like to bring this matter to further steps if we don't get within reasonable delays the feedback of the different parties that we contacted about it.
  28.  
  29. Regards,
  30.  
  31. Aymeric
  32.  
  33. ------------
  34.  
  35. My reply to patent troll:
  36.  
  37. Salutations Aymeric,
  38.  
  39. As you know, I worked at Mozilla on Web Components, and have been involved in open source web technology for quite some time. However, I recently left Mozilla to start an emerging maple syrup conglomerate - but as it happens, it's very much tied to the fate of Web Components. Let me tell you a bit about it:
  40.  
  41. Our maple syrup company relies solely on online sales. Our primary strategy for driving exposure to our product is a web component that lets site owners easily include an interactive maple syrup experience (ex: one of the component's views is a WebGL syrup bottle that lets you 'feel' how the syrup pours). This web component generates all our click-through and sales, which in turn earns site owners Maple Coins (our internal, blockchain-based digital tokens, which can be cashed out for their equivalent value in our delicious maple syrup).
  42.  
  43. Web Components are central to our maple syrup sales strategy, so we'd hate to lose the ability to use them. We are in a bit of a sticky situation though (no pun intended): we have all the company's investment capital tied up in a secure store of syrup we use to back the value of our Maple Coins. It has worked out well so far, as all of our supply chain partners and site affiliates have agreed to use Maple Coins as the exclusive payment instrument for settlement, and subsequently, cash them out for syrup. As such, the only way we would be able to pay for the rights you speak of is in Maple Coins.
  44.  
  45. Please advise us on how you would like to proceed - we don't want anything to interrupt the flow of our syrup business.
  46.  
  47. Respectfully,
  48.  
  49. Daniel Buchner
  50. Chairman and CEO
  51. Syrupdipidy, Inc
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement