<<
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.
<<In the end its going to take a court case to determine what
is considered reasonable or not. If I were going to do any
of the above though I would do my best to use tools that
you can ship with the product to allow users to clearly
identify what is and isn't ogc....
>>
This is all true.
<<
But in addition to that a tool would not satisy the OGL
if the user is able to open the access db and read the
contents because it is at that point where they view the
material that they need to be able to ID the OGC.
So adding a field to the DB to say OGC Y or N
would settle that IMHO.
>>
Or alternately to include a database schema declaring specific database fields or tables to be OGC would work as well.
Lee
