RE: Purpose of your Group(Web App Source Code Protection Community Group)?

Dear Thomas,

Thanks for your questions.

What are the reasons for source-code-protection to be in the browser?(soundcloud.com already proved it that it can protect it's content from the main script-kiddies without such a standard, and there are also "pay-walls", these 2 in compination with the blacklisting of a member when attempting to circumvent it are a good match I think)
>> Because web apps become more and more popular, and many web app stores have appeared. Like native app store’s mode, developers also want to gain profit from the web apps in the web app store, so they never hope their web apps be easily copied by others, especially for the innovative apps. However, nowadays web apps’source code and resources are all openness, plagiarism is inevitable. Therefore, we need a standard level web app protection mechanism, which can be realized by browsers, web os providers and used by developers.

Is there a list of Organizations and Persons funding this research, because this specific group is currently not listed, it seems (http://www.w3.org/Consortium/nmfunds).
>> No, not yet.

Best Regards

Gao Wenmei
Huawei Technologies Co., Ltd.
From: sleazydude@freenet.de [mailto:sleazydude@freenet.de]
Sent: Sunday, October 06, 2013 4:24 PM
To: public-webappscp@w3.org
Subject: Purpose of your Group(Web App Source Code Protection Community Group)?

Dear Sir/Madam,

Thinking about lobbyists, standards, latest agencyscandals and Drive-By-Attacks in the light of new features in the HTML5-Standard(EME)
has led me to your site.
I find it interesting that a community-group was created for this type of problem.
After all Standards should not only be open but also promote openness.

Problems with Code-Protection should be delt with otherwise.

Like it has been done many times before(obfuscators, etc.) at the domain-level of the application, not in the standard.

e.g. You are listing Firefox OS as an example.
It might thrive on HTML, but Mozilla can implement a CRM-Module for their own OS, they do not need a standard for that.

My questions are:
What are the reasons for source-code-protection to be in the browser?(soundcloud.com already proved it that it can protect it's content from the main script-kiddies without such a standard, and there are also "pay-walls", these 2 in compination with the blacklisting of a member when attempting to circumvent it are a good match I think)
Is there a list of Organizations and Persons funding this research, because this specific group is currently not listed, it seems (http://www.w3.org/Consortium/nmfunds).

Sincerely

Thomas
P.s.:I have to appologize for my email-alias, the one I intended to use was locked down, by MS because I haven't used it in years.


---
Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! Rundum glücklich mit freenetMail<http://email.freenet.de/basic/Informationen>