On Sun, 7 Apr 2013 18:50:57 +0200, Peter Boot <[log in to unmask]> wrote:
> I always thought of json as
>mostly meant for data structures, and not so much for texts with spans
>and further embedded spans having various (rendering) properties and
>hyperlinks attached to them. But that may be my lack of familiarity with
>client-side programming.

I sympathize with your discomfort, though it makes me feel quite old-fashioned.  In the past I've used libraries that converted XML to JSON and back, though if I recall correctly, the XML had a rather simple schema.

If the project is or will be public, the one thing I'd want to research is how search engines behave with the kinds of "single page" applications you describe.  If pages and index entries can't be crawled effectively by search engines, the edition may miss out on traffic by interested researchers.  I'm not saying that this is a necessary side-effect of Backbone.js, but I'd really want to make sure before commiting.

The reason I mention this is that the most active user editing my great-great grandmother's diaries is totally unrelated to the project -- the grand-nephew of the diarist's postman, who found the site doing a vanity search for his own name.

Ben Brumfield
http://opensourceindexing.org/