[ckan-discuss] Clear scoping of requirements

William Waites william.waites at okfn.org
Thu Sep 9 14:31:51 BST 2010

On 10-09-09 05:32, Richard Cyganiak wrote:
> I don't want to stifle discussion on architectural issues, but this
> scares me a bit. If such a migration would compete for the same
> resources as fixing front-end issues like those raised by Christopher
> Gutteridge last week, then please please please make some progress on
> the front-end first. It's the front-end that makes or breaks CKAN, not
> the back-end.

I agree. For my part I am far more comfortable working
with APIs than I am with user interfaces. One reason
I suggested working on decoupling the UI more is to
make it easier to improve the front end without worrying
too much about what the back-end is doing or how it is
implemented. I still think this is worthwhile quite apart
from the RDF/noSQL/SQL debate.

As Friedrich also said in another branch of this
discussion improving useability is the top priority and
I am in full agreement. I think he is keen to concentrate
on this. If you know any python developers or clueful
HTML/CSS/JavaScript people, we could always use help.


William Waites           <william.waites at okfn.org>
Mob: +44 789 798 9965    Open Knowledge Foundation
Fax: +44 131 464 4948                Edinburgh, UK

RDF Indexing, Clustering and Inferencing in Python

More information about the ckan-discuss mailing list