Command-line wrapper on proprietary APIs
Is it legal to write a (human-friendly) open-source command-line interface
to a program whose own (not human-friendly) API documentation is labeled
"proprietary"?
This open-source tool would not include any code or files from the
proprietary tool. It would be able to communicate with the proprietary
tools (assuming it's installed and licensed).
I'm inclined to think that the precedent set with Oracle vs. Google
suggests this is OK.
No comments:
Post a Comment