Hacker News new | past | comments | ask | show | jobs | submit login

It's much less ambiguous to exclude APIs from copyright. Otherwise, you'll have endless battles trying to prove that someone really did have access to the API documentation, or some derivative work thereof. Or, someone will argue that reverse engineering an API should not be permitted.

On the flip side, API copyrights could be rendered moot by simply reverse engineering everything, which isn't really that hard.

That is already an issue with many areas of copyright law where assessment needs to be made. If doing reverse engineering you would need to document your approach and be careful to stick to it.

Whether it is or isn't hard will depend on the size and scale of the API that you are trying to recreate. It is probably hard enough that it would normally be easier to create your own API except where you were doing it to create an alternative platform for existing code.

This is correct, doing away with API copyright all together is only solution.

'only solution' that is a very absolute response, is there not even room for discussion? I would have downvoted you if I could and I have upvoted comments I don't agree with in this thread that added depth and thought to the discussion.

Secondly exactly what is it a solution to?

Have you considered any possible costs or downsides to the proposal?

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact