Reply to thread

Message

<blockquote data-quote="smetzger" data-source="post: 364225" data-attributes="member: 1230">3 different strategies:1. You shouldn't have to point to a particular part of the executable binary code and say this is OGC.&nbsp; Why couldn't you release the source code as OGC and the binary code as IP?&nbsp; Obviously this would be difficult if anything in the source code used someone elses OGC (including the SRD), but it should be possible.2. I don't think it would be any different from a print publisher publishing his whole product and then at the back of the product he reproduces everything that is OGC and says &quot;everything here is OGC&quot;.&nbsp; Once again difficult since the publisher couldn't put any OGC material that he didn't create himself in the non-OGC section.3. Also, if you designate the whole thing as OGC, that would certainly be easy to identify.&nbsp; Of course if you want to make money off of it, this may not be the wisest choice.So, points 1 &amp; 2 would be very difficult to do with a useful software program.&nbsp; Point 3 would be pretty much an OGL product that couldn't include a description of character advancement.Still point 3 could be useful for say a library of d20 functions.&nbsp; You could release a DLL with functions that would output a standard statblock, a charcter in XML format, etc.&nbsp; And if you could do that you could divide your program up and put all the OGC code in a DLL and then mark that whole DLL as Open Content and its source code.&nbsp; Not human readable (which is in the FAQ but not the license) but is clearly identified (which is in the license).</blockquote>

[QUOTE="smetzger, post: 364225, member: 1230"] 3 different strategies: 1. You shouldn't have to point to a particular part of the executable binary code and say this is OGC. Why couldn't you release the source code as OGC and the binary code as IP? Obviously this would be difficult if anything in the source code used someone elses OGC (including the SRD), but it should be possible. 2. I don't think it would be any different from a print publisher publishing his whole product and then at the back of the product he reproduces everything that is OGC and says "everything here is OGC". Once again difficult since the publisher couldn't put any OGC material that he didn't create himself in the non-OGC section. 3. Also, if you designate the whole thing as OGC, that would certainly be easy to identify. Of course if you want to make money off of it, this may not be the wisest choice. So, points 1 & 2 would be very difficult to do with a useful software program. Point 3 would be pretty much an OGL product that couldn't include a description of character advancement. Still point 3 could be useful for say a library of d20 functions. You could release a DLL with functions that would output a standard statblock, a charcter in XML format, etc. And if you could do that you could divide your program up and put all the OGC code in a DLL and then mark that whole DLL as Open Content and its source code. Not human readable (which is in the FAQ but not the license) but is clearly identified (which is in the license). [/QUOTE]

Verification