> No, because the work that is OGC in your software cannot be clearly
> identified. Putting it in a separate folder just means you've conveniently
> separated it from the larger work - but the larger work can still be
> distributed by someone without the separate folder, thus violating the terms
> of the OGL.
But larger work may (and probably should) not work without that folder.... However i
don't really
understand your example. "Someone" is deliberately corrupting the software
installation by removing
OGC folder - why his hypothetical actions should concern the software author?
Following same logic
that "someone" can strip OGC header and copyright notices from D20 SRD and distribute
this corrupted
version - IMHO its "someone" breach, not D20 authors.
Folder idea my be technically necessary in some cases. How for example would you
recommend to
"clearly identify" as OGC a binary file? Author made a map of a town, and he wants to
make this town
OGC. However map format is binary so he can't include OGC text header in the map.
Seems to me he can
put OGC header only in accompanying description file - with same risk of file being
deleted during
redistribution.
- Max
_______________________________________________
Ogf-l mailing list
[EMAIL PROTECTED]
http://www.opengamingfoundation.org/mailman/listinfo/ogf-l
