CTS, the retrieval protocol, should be distinguished from CTS URNs, the citation format.
On Apr 11, 2013, at 6:42 PM, Scot Mcphee <[log in to unmask]> wrote:
>
> But why does the catalogue not have the actual CTS URN as a field within it's data structure?
Probably because if you don't like the structure of the CTS GetCapabilities reply, it provides all the information you need to engineer around it, and validates against a schema, so it shouldn't require much effort to parse
<textgroup n="ns:groupid">
<work n="ns:workid">
<edition n="ns:editionid">
....
</edition>
</work>
</textgroup>
and generate urn:cts:ns:groupid.workid.editionid
>
> My point here is, not there there is no search "feature", but that anyone building such a feature is instantly crippled because the two data sets returned by the "getCapabilities" (catalogue) and "validateReff" services are almost entirely disconnected. It is possible a technology such xPath to build the URNs from the rather large XML catalogue, but data that's presented is not clearly explained. Plus, a technology like xPath is runtime, and expensive in memory and CPU, and would struggle to be performed on a mobile device. And as the catalogue can't be pre-filtered on the Perseus side, it's an all-or-nothing document.
>
> My argument is that the "textgroup", "work", "edition" and "translation" elements should all have a child "urn" element, not that there should be a search feature.*
>
> At that point it becomes possible for a third party to decently implement a search feature or any other document interaction protocol. And without a search feature, no-one will be using the URNs to identify anything because they won't know about them.
>
> *By "search" here I don't mean "full text search" I just mean, author/title lookup to URN discovery.
Sure --so one approach would be to batch process a GetCapabilities reply to implement a search app, by mapping group names, work titles, etc, to appropriate level urns.
Alternatively, a third party could also independently create a simple mapping of searchable labels/names to CTS URNs and layer that on top of a CTS. Think of something like the skos RDF vocabuary and implement something like
<urn:cts:greekLit:tlg0012.tlg001> skos:prefLabel "Iliad"@en .
<urn:cts:greekLit:tlg0012.tlg001> skos:prefLabel "Ilias"@de .
>
> regards
> scot
|