I do not know whether Google Docs may be an appropriate location for publishing TEI documents, but I did experiment with Google Sites (and the recently released Google Data API for it) for publishing scholarly projects.
I've jotted down the results of my experiments in two blog posts, which you may find here:
http://doingdigitalhistory.wordpress.com/2010/02/13/publishing-scholarly-projects-using-google-sites/
http://doingdigitalhistory.wordpress.com/2010/02/13/publishing-scholarly-websites-using-google-sites-pt-2-automating-the-process/
Best, Thomas Crombez
University of Antwerp
On 18-jan-2010, at 00:58, Syd Bauman wrote:
> Interesting thought, Stuart. I'm glad to learn about the expansion of
> Google Docs, and it may well prove useful to Scott's group as they
> move forward, but I doubt it will serve as a replacement to what
> they're trying to produce. First, I think many scholars will be quite
> hesitant to trust Google with their data. But leaving the politics
> aside, if I understand correctly, the service Google is providing is
> a far cry from the service Scott's group is trying to create.
>
> The former is merely a storage platform, albeit one that will accept
> a TEI file. After it has stored the TEI file, all it can do is fetch
> it and give it back to you or someone else. This is "publishing" only
> in the most primitive sense of the word. I suppose if the file itself
> has an <?xml-stylesheet?> PI in it, you might be able to transform it
> client-side. Add CSS to that, and it gets you something that might be
> reasonable.
>
> If I understand correctly, however (and I may not), the latter would
> be a publishing platform which, after you've uploaded your TEI file
> to it, would make it available both in raw form and via at least one
> of a variety of stylesheets and user interfaces, perhaps including
> the capability to search over a set of files.
>
>
>>> *Join Us to Plan a Service for Publishing TEI Documents*
>> I immediately though of this project when I read (via several
>> channels) the google docs now supports files of arbitrary kinds:
>> http://www.wired.com/epicenter/2010/01/google-docs-storag/
>> We already use google docs spreadsheets for a wide-range of project
>> coordination tasks. Typically they're shared with upstream or
>> downstream partners (or both) and everyone seems to find they have
>> a low barrier to entry.
|