Hi again Martin,<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">Good point -- that is important! Content licensing should be under a<br>
well known liberal license (GPL, GFDL, some of the Creative<br>
Commons...), otherwise even RACHEL will have problems with it.<br></blockquote><br>Right now our content has a melange of licenses, with the majority being CC. Of course we do request permission from all of our content holders before packaging anything, which gets us past a few issues, but I suppose inclusion in derivative work (including RACHEL in XS) remains sketchy... this will require deeper study.<br>
<br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">Well, a bare HTML index *is* a perfectly valid index :-) and it beats<br>
the performance and portability of any other solutions. How do you<br>
maintain it? Is there any metadata around (dublin core or otherwise)?<br></blockquote><br>Ha :-) AFAIK we have no metadata so far, above or beyond that provided by the filesystem, and we maintain and list the content by simply adding links on the index page when we acquire, package, and verify the new content. Search and flexible indexing will be challenges in the near future. Thanks for pointing me at DC!<br>
<br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">> This project has a voracious appetite for content, and as such we'd rather<br>
> stuff the project with content first regardless of compatibility with open<br>
> projects like Gnash.<br>That is a reasonable approach I guess for your project. At the same<br>
time, it limits its usability to OLPC and to low-cost netbooks.<br></blockquote><br>Great point made! I'll put this on the list for things to look into. Is there a set of compatibility guidelines we should look at, or is there a checker tool so we won't have to bother the content providers as much?<br>
<br>On another note, I just took a look through the XO content library at <a href="http://wiki.laptop.org/go/Library_grid">http://wiki.laptop.org/go/Library_grid</a> and to my delight discovered that everything was a self-contained website in a .zip file! This is a great thing. Perhaps we could work something out whereby on our content hunting we could package some content for you folks, permissions and licenses permitting.<br>
<br clear="all">Dennis Nguyen<br>
<br><br><div class="gmail_quote">On Tue, Sep 29, 2009 at 12:13 AM, Martin Langhoff <span dir="ltr"><<a href="mailto:martin.langhoff@gmail.com">martin.langhoff@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tue, Sep 29, 2009 at 5:13 AM, Dennis Nguyen<br>
<div class="im"><<a href="mailto:denniskdnguyen@alumni.duke.edu">denniskdnguyen@alumni.duke.edu</a>> wrote:<br>
</div><div class="im">> Hi Martin, thanks for the warm welcome!<br>
<br>
</div>My pleasure!<br>
<div class="im"><br>
> We would definitely welcome re-use of the content, but since I'm relatively<br>
> new to this particular project I don't have an expert sense of the<br>
> particular permissions we have with the content providers as is. I will look<br>
> into it.<br>
<br>
</div>Good point -- that is important! Content licensing should be under a<br>
well known liberal license (GPL, GFDL, some of the Creative<br>
Commons...), otherwise even RACHEL will have problems with it.<br>
<div class="im"><br>
> Indexing: none! All of the content is currently listed on the index page<br>
> with bare HTML. In our defense, this is a relatively new and shorthanded<br>
<br>
</div>Well, a bare HTML index *is* a perfectly valid index :-) and it beats<br>
the performance and portability of any other solutions. How do you<br>
maintain it? Is there any metadata around (dublin core or otherwise)?<br>
<div class="im"><br>
> The wikislice we're using for the moment is the 2008/9 Wikipedia Selection<br>
> for schools, which is handpicked front-to-back to fit the UK national<br>
> curriculum. The website with details for that is at<br>
> <a href="http://schools-wikipedia.org/" target="_blank">http://schools-wikipedia.org/</a><br>
<br>
</div>Wasn't aware it existed. Interesting. Still, of limited use to us,<br>
being English only.<br>
<div class="im"><br>
> what we can get away with as we go. We have English and Spanish content so<br>
> far.<br>
<br>
</div>That's a good start.<br>
<div class="im"><br>
> This project has a voracious appetite for content, and as such we'd rather<br>
> stuff the project with content first regardless of compatibility with open<br>
> projects like Gnash.<br>
<br>
</div>That is a reasonable approach I guess for your project. At the same<br>
time, it limits its usability to OLPC and to low-cost netbooks.<br>
<div class="im"><br>
<br>
> You can probably tell from this that this project is in a very early stage<br>
> as far as maturity of the platform is concerned. I'm working to engage you<br>
> folks at an early stage in case you have something grand to teach us :-)<br>
<br>
</div>I wish :-) -- all I can point to is the work and evolution of Linux<br>
"distributions" (such as Debian, RH, SuSE, Ubuntu). They take software<br>
developed by other projects, add a tiny bit of metadata, wrap it in an<br>
installable package.<br>
<br>
We are needing the same for content ATM, and the time is ripe for it.<br>
<div><div></div><div class="h5"><br>
<br>
<br>
m<br>
--<br>
<a href="mailto:martin.langhoff@gmail.com">martin.langhoff@gmail.com</a><br>
<a href="mailto:martin@laptop.org">martin@laptop.org</a> -- School Server Architect<br>
- ask interesting questions<br>
- don't get distracted with shiny stuff - working code first<br>
- <a href="http://wiki.laptop.org/go/User:Martinlanghoff" target="_blank">http://wiki.laptop.org/go/User:Martinlanghoff</a><br>
</div></div></blockquote></div><br>