Scot,
Your write-up is wonderful. I enthusiastically support anything done in
the "spirit of solving problems and making this data available to
everyone else"!
One quick comment: I'd recommend oXygen or other XML editor for looking
at the CTS Text Inventory locally. Or if you're feeling adventurous and
want to try out XQuery, I believe BaseX is a pretty easy way to get
started with that.
Best,
Bridget
On 04/10/2013 09:42 AM, Scot Mcphee wrote:
> On 10/04/2013, at 02:37 , Neel Smith <[log in to unmask]> wrote:
>
>> Hugh's right that there's not a separate request in the CTS protocol to expand CTS namespaces to URIs, but the GetCapabilities request requires information about how to expand namespaces that apply to all other requests. Within a CTS implementation, therefore, the loop *is* closed.
>
> A perfect URL scheme may be desirable but -- "the perfect is the enemy of the good enough" is what comes to mind here** -- it's useless if the user can't discover where the resources are.
>
> Questions of data format and interchange are also good things, but, to quote the Agile Manifesto, one must value "Working systems over comprehensive documentation". The current Perseus HTML-and-XML implementation is such a working system, however imperfect, but the CTS needs to become one.
>
> In the spirit of solving problems and then making this data available to everyone else, I've written up what I worked out about the procedure that governs how to get from the Catalogue Entry to the actual edition of the text on my blog, here: http://inlustre.net/2013/04/how-to-retrieve-ancient-text-data-from-perseus/
>
> I'd be very interested in comments and corrections.
>
> regards
> Scot.
>
> ** I wonder if that quote has a classical antecedent.
|