----- Original Message ----- From: <[EMAIL PROTECTED]> > In a message dated 1/28/03 8:47:38 AM Eastern Standard Time, > [EMAIL PROTECTED] writes: > > > > << > > If however the db is used by a front end to provide access > > to the OGC content stored within then it would be the > > responsibility of the front end to clearly indicate what is > > and what isn't OGC when the content is displayed. > > >> > > I disagree. I think there's no requirement that any front end necessarily > label displayed data as OGC/non-OGC. So long as it can be determined from > looking at the DB, there doesn't seem to be a clear requirement that the > front end also has to redundantly indicate OGC as it is displayed. > >
I would have to recheck the license to be certain, but AFAIK it said that OGC content be clearly indicated whereever it is used. If I declared a text file to be 100% OGC, and then had a front end which displayed that text file along with other data, I would AFAIK have to identify in some way the OGC been displayed. My reasons for saying I would need to id it in the front end, is that in theory the text file is like the appendix idea which was previously discussed and dismissed. I could be wrong and usually are :P but I was under the impression that OGC had to be clearly distinguished where ever it be used. so in the case above you would say "text file abc.txt is 100% OGC. Also any text that is displayed by the program in a shaded box is OGC." Even if the text in the shaded box is loaded direct from the text file, I would imagine it must still be clearly identifiable. Gary. _______________________________________________ Ogf-l mailing list [EMAIL PROTECTED] http://mail.opengamingfoundation.org/mailman/listinfo/ogf-l
