<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span><br></span></div>>>> If I use software that builds an in-memory data structure which you<br><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;">>>> believe to be a database in order to make a produced work, how<br>>>> would you suggest that I fulfil my obligation to make such derived<br>>>> database available on request?<br>>> <br>>> I have absolutely no idea. It's one of the many things I don't know<br>>> about how the produced works part of the ODbL will work in practice.<br><br>>Thinking about this more, the problem would only occur if you have a black-box software wich might or might not create a database internally, and the thing that falls out
of the black box is a >produced work that you will publicly use.<br>><br>>Because then, and only then, will you have to share the derived database upon which the produced work is based.<br><br>No, this happens with all software, regardless of the software license. Who is reading the source code of a free software just to know if creates internal database?<br></div></div></div></body></html>