Ogl license on Ip in electronic form.

[herald]

Am I right in thinking that if I wanted to produce a piece of game mechanics in a type of electronic format that could only be read in a specific program. (i.e. adobe acrobat, word ect.) that the ogl license with declarations should be contained in the same said file, or would it be ok to contain the license in a .txt file with the electronic file.

I'm inclined to think it's the former rather than the latter.

 

[Planesdragon]

Am I right in thinking that if I wanted to produce a piece of game mechanics in a type of electronic format that could only be read in a specific program. (i.e. adobe acrobat, word ect.) that the ogl license with declarations should be contained in the same said file, or would it be ok to contain the license in a .txt file with the electronic file.

I'm not a lawyer, this isn't legal advice, if you get sued for doing this you agree to indemnify me for any damages that arise from you following my advice and ignoring the "capitulate to all lawyers or hire one of your own" part.

That said.

The common standard for including the OGL is that it has to be easy to find and included with every copy that you send, though the preferred method is to make it accessible through the common interface for whatever the heck it is that you're sending. A seperate text file is accessable for some things (I used to do ZIP'd RTFs with the OGL as a text file), but not for others (In the PDFs that I do now, I include it in the the body of the document in a small font.)

So, to be safe, include it in the body of each .DOC or .PDF that you make. If you want to save space, however, you could put it in a seperate text file, but only if you bundle the DOCs and PDFs in some kind of archive file and it's clear what OGL goes with what document. (Though, theoretically, you could just lump them all together...)

 

[herald]

I'm not a lawyer, this isn't legal advice, if you get sued for doing this you agree to indemnify me for any damages that arise from you following my advice and ignoring the "capitulate to all lawyers or hire one of your own" part.

That said.

The common standard for including the OGL is that it has to be easy to find and included with every copy that you send, though the preferred method is to make it accessible through the common interface for whatever the heck it is that you're sending. A seperate text file is accessable for some things (I used to do ZIP'd RTFs with the OGL as a text file), but not for others (In the PDFs that I do now, I include it in the the body of the document in a small font.)

So, to be safe, include it in the body of each .DOC or .PDF that you make. If you want to save space, however, you could put it in a seperate text file, but only if you bundle the DOCs and PDFs in some kind of archive file and it's clear what OGL goes with what document. (Though, theoretically, you could just lump them all together...)

Thanks for the information. I understand that you are not a lawyer and that you are mearly expressing a opinion and not legal advice. If I need to in the future I need full advice I will get a lawyer.