I suggest that you could also use xlink:href , for example :

<dc:identifier xlink:href="the url">URL or whatever as
text</dc:identifier>

Bill

> -----Original Message-----
> From: Z39.50 Next-Generation Initiative [mailto:[log in to unmask]] On Behalf
Of
> Theo van Veen
> Sent: 13 October 2005 09:15
> To: [log in to unmask]
> Subject: Betr.:
> 
> Peter,
> Let the partner use qualified dc with encoding schemes and do not go
for
> less although  there might be a trend to use namespace prefixes when
there
> is no qualification like:
> <dc:identifier>ISBN:12345678....
> instead of
> <dc:identifier xsi:type:dcterms:ISBN>1234.....
> At the same time you have to take the world as it is and accept both
ways
> of encoding.
> 
> Theo
> 
> 
> >>> [log in to unmask] 10/13/05 1:19  >>>
> A probably really dumb question:
> 
> A partner of ours wants to use a URL as a "dc:identifier" for their
> records.
> No problem so far this is one of the recommended values. They want it
to
> be
> used as the link to read the record. Also no problem .
> 
> However as a metasearch engine we need to be able to identify that it
is a
> URL and a link within a set of records from a number of different
Sources
> (for the sake of being awkward - like real life - assume all are
queried
> via
> SRU and are returning records in simple DC). They don't want to go
beyond
> using simple DC, so qualification is not an option. Using a "urn:url"
type
> namespace identifier would work. If everybody used it, which they
won't,
> we
> would be home free. [What is the 'namespace' identifier for a URL when
> used
> within the DC set in SRU anyway? ISSNs ("urn:issn:") and DOIs
> ("info:doi/")
> are all listed, but URLs are not]
> 
> Are we limited to detecting "http://" and deducing that it is not an
ISBN?
> Of course some will start "www." and others will be just
> "anywhere.com/..."
> So this is a bit of a nightmare.
> 
> I don't want to have to produce hard coded variants of our SRU
Connector
> to
> handle this sort of issue. I want to keep a single Connector which is
> configured for different Sources - if it has to be. The less variation
> there
> is the less configuration there is and the more likely things are to
work.
> 
> So the (main) dumb question is: How do they put this link URL in a
> returned
> record in simple DC in a way that it can be recognized by dumb
computer
> programs? Or are we stuck with configuration?
> 
> 
> Peter
> 
> Dr Peter Noerr
> Chief Technical Officer
> Museglobal, Inc.
> 
> tel: +1 801 208 1880
> fax: +1 801 208 1889
> cell:+1 801 910 4912
> 
> [log in to unmask]
> www.museglobal.com

**************************************************************************
 
Experience the British Library online at www.bl.uk
 
Help the British Library conserve the world's knowledge. Adopt a Book. www.bl.uk/adoptabook
 
The Library's St Pancras site is WiFI - enabled
 
**************************************************************************
 
The information contained in this e-mail is confidential and may be legally privileged. It is intended for the addressee(s) only. If you are not the intended recipient, please delete this e-mail and notify the [log in to unmask] : The contents of this e-mail must not be disclosed or copied without the sender's consent. 
 
The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of the British Library. The British Library does not take any responsibility for the views of the author. 
 
**************************************************************************