Reply to thread

Message

<blockquote data-quote="Mynex" data-source="post: 320415" data-attributes="member: 2136">You are correct.&nbsp; That is because we were under the mistaken notion that we were following copyright issues not OGL issues.Since we have been informed that by using OGC content we unknowingly agreed to abide by the OGL.&nbsp; Note, abiding is different then accepting the license.&nbsp; That has been misconstrued as well by several people on this thread (and many like it).Since we are now well aware that we have accepted the OGL, we are now working to abide and accept the license as well as the D20 license (which is related but seperate).And we have a clear way to handle to the OGL license display/reprint/whatever you want to call it...As for updating section 15, we make no changes to anything, only use the mechanics as they are presented in the works.&nbsp; We are not making derivitive works, so there is nothing to update on that part (I may have that wrong, I'm still going over this stuff, and that part is particularly fuzzy for me, but Wizards is being very helpful on that front, so if I'm wrong, I'll correct myself).As for the LPGL, you are mixing software and data... the code for PCGen falls under the LPGL and is what is/can/will be D20 Compliant, the data sets DO NOT fall under the LPGL, they are not code.&nbsp; THOSE must be OGL compliant.there is a clear delineation here, and that's what is tripping most people up.. there is the code, a dumb interface that does only/exactly what the data/list files tell it to do, and the data, which is human readable and editable, that tell the code what to do.they are 2 different things people, please stop mixing them up, each one of them has different roles to play here in this overall issue.</blockquote>

[QUOTE="Mynex, post: 320415, member: 2136"] You are correct. That is because we were under the mistaken notion that we were following copyright issues not OGL issues. Since we have been informed that by using OGC content we unknowingly agreed to abide by the OGL. Note, abiding is different then accepting the license. That has been misconstrued as well by several people on this thread (and many like it). Since we are now well aware that we have accepted the OGL, we are now working to abide and accept the license as well as the D20 license (which is related but seperate). And we have a clear way to handle to the OGL license display/reprint/whatever you want to call it... As for updating section 15, we make no changes to anything, only use the mechanics as they are presented in the works. We are not making derivitive works, so there is nothing to update on that part (I may have that wrong, I'm still going over this stuff, and that part is particularly fuzzy for me, but Wizards is being very helpful on that front, so if I'm wrong, I'll correct myself). As for the LPGL, you are mixing software and data... the code for PCGen falls under the LPGL and is what is/can/will be D20 Compliant, the data sets DO NOT fall under the LPGL, they are not code. THOSE must be OGL compliant. there is a clear delineation here, and that's what is tripping most people up.. there is the code, a dumb interface that does only/exactly what the data/list files tell it to do, and the data, which is human readable and editable, that tell the code what to do. they are 2 different things people, please stop mixing them up, each one of them has different roles to play here in this overall issue. [/QUOTE]

Verification