Call for Participation in Web App Source Code Protection Community Group
W3C has launched the Web App Source Code Protection Community Group
The goal of this community group is to explore solutions for protecting web app source codes.
It is well-known that web page source codes are visible to the public due to the openness of the Internet and the W3C standards.
With the advent of HTML5, the web apps become popular, especially the mobile web apps. Web apps can be classified as either Hosted App or Packaged App. The source code of Packaged Apps (such as the apps in Firefox OS or Tizen OS) are installed and running locally. Users can easily view the source code. Similarly front end source code of Hosted App can also be easily seen by anyone.
In this case, the publicity of source codes becomes a problem. Because web developers never hope their web apps are easily copied by others.
Therefore, this group intends to find mechanisms of code protection for web apps, especially for packaged apps, making the source codes (e.g. HTML, CSS, JavaScript), as well as relevant resource files (image, audio and video, etc.) cannot be seen easily. Thus, the interests of web developers will be protected.
In order to join the group, you will need a W3C account.
This group was originally proposed on 2013-05-30 by Wenmei Gao. The following people supported its creation: Wenmei Gao, yahui wang, Hao Jing, xiaoqiang lv, Li Li.
If you believe that there is an issue with this group that requires the attention of the W3C staff, please send us email on site-comments@w3.org
Thank you,
W3C Community Development Team
Does this proposition not contradict the whole principle of the W3C ??
Hi Swinhoe,
I would like to make sure that everyone understands that Community Groups are created and shaped by the community. W3C hosts these conversations (including comments like this thread) but that does not imply W3C endorsement of the particular topics or outcomes.
Community Groups do not have the same level of endorsement at Working Groups, where the Membership reviews proposals, W3C management allocates staff resources, and so on.
Ian
In the spirit of community groups being able to discuss whatever they want, I’m exercising my right to comment that this idea, while hardly new, remains technically ignorant, misguided in spirit, and fundamentally dangerous to the success of the Web. I hope and will work towards it going nowhere.
A solution for this problem is long overdue. What is needed is an encryption system that encodes HTML/CSS/Javascript which is only decryptable using an on chip TPM module. TEH INTARWEB CODES MUST BE PROTECTED.
I also have an idea for physical books that prevent users from STEALING key insights on how the author used letters, words, punctuation and paragraph structures to formulate a literary work. Which I hope to sell to the highest bidding patent trol^H^H^H^H^H^H^H^H… intellectual property guardian. Please contact me for details!