headers
Iain Emsley | 3 Apr 12:02

Versioning Manuscripts

Dear all,

Just thought that I'd let you know that I've taken a little break from  
Milton to do something linked to it whilst I figure out the source of  
the junk error I get from Genshi.

At the conference, mention was made of trying to version  
manuscripts/texts to find the changes. I've been quietly working on a  
Perl programme to begin doing that or at least to demonstrate the  
approach whilst looking at how to fully implement the ideas.

Would you be interested in a Python port to fit in with  
openShakespeare and openMilton, or would Perl be okay until I've done  
the port?

ATB,

Iain

--

Iain Emsley

Blog: www.yatterings.com
Mobile: 07942 259725
Permalink | Reply | 1 comment |
headers
Jonathan Gray | 3 Apr 23:03

Re: openMilton and outreach

Iain Emsley wrote:
> I thought I'd let people know that I've contacted a professor at my old 
> university who has an interest in Milton to get his feedback and 
> thoughts on what would be useful for him or his students / colleagues as 
> well. I'll let the list know if and when I get any reply.

Good news! I look forward to seeing what the outcome is.

I generally think that touching base with those involved in 
teaching/research relevant to open knowledge projects is a good thing.

What about creating advisory boards? One for Open Milton, one for Open 
Shakespeare? I've been meaning to post on the SHAKSPER.NET list for a 
while. I will do this ASAP.

I was speaking with several people at OKCon about working with 
academics, researchers, teachers etc. to build wish lists of features 
for projects like Open Shakespeare/Milton - to help determine what kinds 
of things would be most useful/valuable to those 'on the ground'.

> A thought (and this was tangentially raised in one of the downstairs 
> sessions at OkCon) but is there any place where all the various outreach 
> activities are placed so that effort isn't duplicated or that volunteers 
> can find out what various plans are or might be?

There are several places. For documenting communications (mostly to do 
with OKD + buttons), I've started to use:

   http://www.okfn.org/wiki/Communications
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jonathan Gray | 4 Apr 02:33

MusicBrainz + OKD

Hi all,

As you possibly may have noticed the MusicBrainz team are now displaying 
the Open Knowledge web button [1] in their footer [2] - which is great news!

Brian Schweitzer, who's involved with the project, sent me some comments 
on point 4 of the OKD - 'Absence of Technological Restriction'.

I thought these could be of interest to some of you on this list - so 
they're attached below.

(Incidentally - if anyone can think of any open knowledge projects to 
contact regarding the buttons, please let me know!)

Regards,

Jonathan

[1] http://opendefinition.org/buttons
[2] http://musicbrainz.org/

### First message:

I help out on the MusicBrainz support email addresses, but I'm just
sending this email as an individual, not representing MusicBrainz.

I was just reading your definition of Open Knowledge, and saw one
point which I thought I'd mention to you.

Under point 4, Absence of Technological Restriction
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jonathan Gray | 4 Apr 17:33

Jon Phillips from CC in London

Hi all,

Just a quick note to say that Jon Phillips, Community and Business 
Development Manager of Creative Commons, is going to be in London early 
next week.

I think we're going to meet on Monday evening, and possibly also on 
Wednesday. If anyone would be interested in joining us, please let me know!

Regards,

Jonathan
Permalink | Reply | 0 comments |
headers
Evan Prodromou | 7 Apr 19:06
Gravatar

Public mirrors of Open Content archives

My name is Evan Prodromou, and I'm the founder of a wiki Web site called
Vinismo.com. Vinismo is the Free wine guide -- we have more than 20,000
articles on wines, wineries, and wine regions around the world.

	http://vinismo.com/

Our site is available under the Creative Commons Attribution-ShareAlike
Canada 2.5 license. We make full-site data dumps available in HTML and
XML format, as well as tarballs for our image files:

        http://vinismo.com/download/

We also build some RDF data about wines (it's a red wine, it contains
such-and-such a grape, it costs so many dollars in the US or Australia
or Canada or wherever, etc.), which can be derived from the above dumps,
but which we'll soon be providing in a separate data dump, too.

My plan is to have vinismo.com alive and well forever and ever. But
plans don't always work out as we'd like. It would be great for my peace
of mind, and for all our contributors, to know that our data was being
archived somewhere safe and independent from the Vinismo site. Making Open
Content, it's important to make sure it sticks around for someone else
to use.

Let me be clear that my bandwidth and storage needs are fine, and that I
of course have redundant off-site backups. This kind of mirroring is more of
a social issue than a technical one. Mirrors like this are common in the Free
Software world.

I'd hoped that this was what CKAN was about, but apparently it's more of a
(Continue reading)

Permalink | Reply | 1 comment |
headers
Rufus Pollock | 8 Apr 12:48
Gravatar

Re: Public mirrors of Open Content archives

On 07/04/08 18:06, Evan Prodromou wrote:
> My name is Evan Prodromou, and I'm the founder of a wiki Web site called
> Vinismo.com. Vinismo is the Free wine guide -- we have more than 20,000
> articles on wines, wineries, and wine regions around the world.
> 
>     http://vinismo.com/

Really nice -- I took a look yesterday after seeing it entered on CKAN.

> Our site is available under the Creative Commons Attribution-ShareAlike
> Canada 2.5 license. We make full-site data dumps available in HTML and
> XML format, as well as tarballs for our image files:
> 
>        http://vinismo.com/download/

This is great. And makes you ultra-compliant with the OK/DD 
(http://opendefinition.org/) :)

> We also build some RDF data about wines (it's a red wine, it contains
> such-and-such a grape, it costs so many dollars in the US or Australia
> or Canada or wherever, etc.), which can be derived from the above dumps,
> but which we'll soon be providing in a separate data dump, too.
> 
> My plan is to have vinismo.com alive and well forever and ever. But
> plans don't always work out as we'd like. It would be great for my peace
> of mind, and for all our contributors, to know that our data was being
> archived somewhere safe and independent from the Vinismo site. Making Open
> Content, it's important to make sure it sticks around for someone else
> to use.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jonathan Gray | 8 Apr 20:53

Open Knowledge Bibliography

Hi all,

I've recently been touch with Anne Fitzgerald of the OAK Law Project 
about collaborating on a bibliography for articles, books, etc. about, 
or directly relevant to Open Knowledge issues. They have two volunteers 
who may help with this.

We've got a few things up at:

   http://okfn.org/wiki/Bibliography

I was wondering if anyone on the list might have any suggestions for the 
best (low cost) way to scale this.

Two possible options:

   1. Continue to add to the page as it is with some basic template 
including author(s), title, date, publisher, journal, url, subject area 
and so on. If format is consistent, information could be parsed at some 
point in the future and converted into some other format.

   2. Use template/macros and give each item a separate page, and use 
categories to group them into subject area. (As we currently do with our 
Todo list [1]).

Perhaps it would be worth doing this using some other software, plugin etc.

Regards,

Jonathan
(Continue reading)

Permalink | Reply | 0 comments |
headers
Nate Olson | 10 Apr 00:51

Big hits for open-data repos generally, CKAN particularly...

I'm surprised that nobody seems to have posted here on the excellent  
coverage CKAN has gotten today, precipitated by ex-Googler Bret  
Taylor's weblog entry. Follow the discussion on Techmeme here:

<http://www.techmeme.com/080409/p34#a080409p34>

Is good, no?

Nate
Permalink | Reply | 2 comments |
headers
Rufus Pollock | 10 Apr 11:55
Gravatar

Re: Big hits for open-data repos generally, CKAN particularly...

On 09/04/08 23:51, Nate Olson wrote:
> I'm surprised that nobody seems to have posted here on the excellent  
> coverage CKAN has gotten today, precipitated by ex-Googler Bret  

Thanks for this link Nate -- this is exactly what the discuss list is 
for. I certainly hadn't seen this yet, after all one can't follow all 
feeds all of the time :)

> Taylor's weblog entry. Follow the discussion on Techmeme here:
> 
> <http://www.techmeme.com/080409/p34#a080409p34>
> 
> Is good, no?

This is great. We should also make some effort to go and explicitly post 
some more information about CKAN in the comments in the relevant threads 
  (i'm in the process of posting a comment to Bret Taylor's post).

~rufus
Permalink | Reply | 0 comments |
headers
Rufus Pollock | 11 Apr 12:03
Gravatar

Re: Big hits for open-data repos generally, CKAN particularly...

Just to follow up my previous email, I've now posted something on the 
blog about this under the title 'Open Data Going Mainstream':

<http://blog.okfn.org/2008/04/10/open-data-going-mainstream/>

~rufus

On 09/04/08 23:51, Nate Olson wrote:
> I'm surprised that nobody seems to have posted here on the excellent  
> coverage CKAN has gotten today, precipitated by ex-Googler Bret  
> Taylor's weblog entry. Follow the discussion on Techmeme here:
> 
> <http://www.techmeme.com/080409/p34#a080409p34>
> 
> Is good, no?
> 
> Nate
> 
> _______________________________________________
> okfn-discuss mailing list
> okfn-discuss@...
> http://lists.okfn.org/cgi-bin/mailman/listinfo/okfn-discuss
Permalink | Reply | 0 comments |

Gmane