 |
 |
Sorry if I've repeated anything here, I wasn't paying attention to the previous messages in this thread... Surely, the language of a linked resource would be specified in that resource's metadata? Is it really necessary to duplicate that information in the link to that resource? If you want to tell people "There's this resource available, and it's in English"... then that should be part of whatever user interface you're designing. Make the user interface more intelligent, rather than making the metadata more unintelligible. If the rights statement is just another document on the Web, then it could (nay, *should*) have its own metadata. Even if the "DC.Rights" field in the metadata for the rights statement just points to itself, at least you know that the "DC.Language" field is going to be in the metadata for that document. IMHO, the only time the "LANG" attribute should be used is if the "DC.Rights" field actually contains the rights statement. Regards, Alex Satapa (just another malapert pedagogue) Andy Powell wrote: > On Thu, 15 Oct 1998, Titia van der Werf wrote: > > > In general the question is: > > would it make sense to specify the language of the resource you are > > linking to through the URL, with the LANG qualifier here? > > or would a LANG qualifier at this level only refer to the language of the > > link itself = the URL (in which case it is not very relevant) ? > > In this case the URL simply provides an indirection to the content - so > LANG referes to the language of the rights statement the URL points to. > > > A similar example with the DC.Description tag could be given. > > Not sure. Given the current wording of the RFC, Description cannot be 'an > identifier that links to a description' in the way that Rights can be 'an > identifier that links to a rights management statement'. > > Andy. > -- > UK Office for Library and Information Networking > University of Bath, Bath, BA2 7AY, UK Voice: +44 1225 323933 > http://www.ukoln.ac.uk/ukoln/staff/a.powell.html Fax: +44 1225 826838