<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Two (possibly useful) comments:<div><br></div><div>1. One does not know in advance where the language of a resource is located in a resource description. Following the CMDI philosophy this could be embedded anywhere in the CMDI document. Most resources contain more that language specifications, depending upon the element's context.</div><div><br></div><div>2. We are working out the b) route at the moment since the harvesting and indexing step has already been taken care of. So on our side we should simply be able to query for all SRU endpoints on the available CMDI files and start the content search method from there. Or to insert a content search engine widget at the UI level for each resource that has a content search engine link.</div><div><br></div><div>Marc</div><div><br></div><div>Marc</div><div><br><div><div>On Aug 16, 2012, at 2:57 PM, Thomas Zastrow wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Am 16.08.12 14:44, schrieb Herman Stehouwer:<br><blockquote type="cite">Shouldn't corpora already have CMDI files?<br></blockquote><blockquote type="cite">Shouldn't those CMDI files already contain all the information you are going to get about a specific corpus?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Otherwise we can keep adding stuff ...<br></blockquote>Yes - but as I already said:<br><br>a)<br>The center registry is my starting point to get the information, which <br>endpoints are available.<br><br>b)<br>I need information about the corpora at these endpoints, for example the <br>language. If I don't find these information directly via the endpoints, <br>it would mean that<br><br>For every corpus ...<br><br>1.)<br>Find the CMDI file: Resolve the PID and parse that document (most, but <br>not all people are using the handle system which means that at this <br>point I have to probably mind more than one PID-resolver format ...)<br><br>2.)<br>Harvest the CMDI file<br><br>3.)<br>Parse the CMDI file<br><br>So, that would be *much* more effort at the user interface part of the <br>FCS. At the moment, with 10 corpora or so, I can harvest the necessary <br>information from the center registry and the endpoints in realtime. <br>Doing it the way that I have to go the circuit via the CMDI files would <br>slow down everything a lot.<br><br>So, be pragmatic, we have less then 10 months to finish the whole thing <br>and not many people are *really* writing code at the moment ...<br><br>Best,<br><br>Tom<br><br><br>-- <br>Dr. Thomas Zastrow<br>Seminar fuer Sprachwissenschaft<br>Universitaet Tuebingen<br><br>Wilhelmstr. 19<br>D-72074 Tuebingen<br><br><a href="http://www.thomas-zastrow.de">http://www.thomas-zastrow.de</a><br><br>Tel.: 07071/29-73968<br>Fax: 07071/29-5214<br><br>_______________________________________________<br>Dev mailing list<br><a href="mailto:Dev@lists.clarin.eu">Dev@lists.clarin.eu</a><br>https://lists.clarin.eu/cgi-bin/mailman/listinfo/dev<br></div></blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">***************************************************************<br>* Marc Kemps-Snijders<br>* Meertens Instituut (Afdeling Technische Ontwikkeling) <br>* Joan Muyskenweg 25 / <br>* Postbus 94264 <br>* 1090 GG Amsterdam<br>* tel. +31-(0)20-4628550<br> * <a href="mailto:marc.kemps.snijders@meertens.knaw.nl">marc.kemps.snijders@meertens.knaw.nl</a> <br>***************************************************************<br><br><br><br><br><br><br></div></span></span>
</div>
<br></div></body></html>