<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16481" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi,</FONT></DIV>
<DIV><FONT face=Arial size=2>I am currently implementing Tapir metadata
responses and have some issues.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>-indexing preferences frequency in the
documentation states @Frequency (starting with uppercase), the schema uses
@frequency. I assume I have to implement @frequency.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>-dc:language is mandatory. What to do with data
that is not language specific? Example: we are going to use Tapir for sharing
lists of scientific names. Should the language be Latin in that case? We think
about using specifying English (eng) as default in that case. The
recommendation is to use IANA Language subtags. Probably better to recommend the
languages from ethnologue.org (3-letter abbreviations). This because the data
can be in much more languages then the IANA Languages, for instance common names
in extinct languages. This is different from the xml:lang attribute, which is
primarily for application development.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>-the example for an accesspoint is <A
href="http://example.net/tapir.cgi">http://example.net/tapir.cgi</A> I
think this may be misleading, it would perhaps be better to use
<A
href="http://example.net/tapir.cgi/yourdatasource">http://example.net/tapir.cgi/yourdatasource</A> as
example.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Wouter</FONT></DIV></BODY></HTML>