HTML5 - securing intellectual property

Forum|Forum|13 years ago
November 23, 2012
10 replies
1900 views

Hi,

Currently when I publish in Captivate project then the content and how we created it is hidden from view (unless someone decompiles it) .

With HTML5 my understanding is that everthing is in plain text and there is no way of doing DRM or hiding content.

http://en.wikipedia.org/wiki/Comparison_of_HTML5_and_Flash

Is this right ?

Is this really an issue ?

regards Renovator

This topic is closed to new replies. Start a new post to keep the conversation going.

Correct answer RodWard

If you take a look at the complexity of the code behind an HTML5 output you realise that you'd need to be a gifted programmer to understand it well enough to debug issues. And you also need to be a gifted programmer in several technologies (HTML, CSS, JavaScript, as well as AS3) not just one.

HTML5 makes EVERYTHING harder for developers. DRM is just one of the issues we'll be grappling with in years to come with this beastie.

RodWard

Community Expert

You are correct. Digital Rights Management is an area for which HTML5 currently has no provision.

renovator99Author

Known Participant

Thank-you Rod.

So its a big worry then because we like to support widget developers and protect our own stuff and html5 makes this harder

On the other hand html5 means that it would be easier to debug some captivate issues

I found this discussion on stack exchange

http://gamedev.stackexchange.com/questions/32435/html5-game-obfuscation

The options were

- hide code on the server

- accept that things will get stolen and concentrate on making them better

- embrace open source

- use copyright notices

- obfuscate variables at the expense of making bug tracking harder

- use native code objects

- leave some code on the server- I know this means the user has to be connected

There is also some talk that google, ms etc may get together to do DRM

RodWard

Correct answer

Community Expert

If you take a look at the complexity of the code behind an HTML5 output you realise that you'd need to be a gifted programmer to understand it well enough to debug issues. And you also need to be a gifted programmer in several technologies (HTML, CSS, JavaScript, as well as AS3) not just one.

HTML5 makes EVERYTHING harder for developers. DRM is just one of the issues we'll be grappling with in years to come with this beastie.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.