<br><br><div><span class="gmail_quote">On 9/8/06, <b class="gmail_sendername">Frank Richter</b> <<a href="mailto:frank.richter@gmail.com">frank.richter@gmail.com</a>> wrote:</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hm, but wouldn't "didn't look at MSDN" also include "rewording"? To<br>reword something, you need to look at the original, after all. So in the<br>strictest interpretation, it looks to me that only "clean-room docs"
<br>(infer the documentation by looking at the source code) would be acceptable.</blockquote><div><br>As far as I understand US and Internation Copyright law the interface cannot be copywritten so it would be permissable to look at the documentation
<br>when learning how to implement the function and then closing your browser and writting the documentation from memory. At least thats how it was explained to me at the first wineconf. Its a stretch I know but there is nothing legally that I can tell that prevents the developer from reading the API documentation and later writting his own documentation. IANAL so take that with a grain of salt. Perhaps the standard should be that the same developer that writes the API cannot document it. Julliards point of view seems to be when you write the interface your free to look at MSDN however don't write the API docs at the same time. Go back later, look at what you have done and base your documentation on your own work.
<br></div></div><br>-- <br>Steven Edwards<br><br>"There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo