xsl-list
[Top] [All Lists]

RE: [xsl] xlink:href

2009-12-14 09:23:27

Off-list reply, because you're off-topic, and Tommie doesn't like that...

Two slashes is always wrong, but some software tolerates it. You want either
one slash or three. There's technically a difference but in practice they
are equivalent.

With the file:/ or file:/// prefix you have a rooted (absolute) path.
Without any prefix you have a relative path, for example scan0001.tif
selects a file in the same directory as the current document (the one
containing the link).

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay  

-----Original Message-----
From: ivanmacculi(_at_)libero(_dot_)it 
[mailto:ivanmacculi(_at_)libero(_dot_)it] 
Sent: 14 December 2009 13:03
To: XSL user
Subject: [xsl] xlink:href

Hi all, i've problems to determine the right path for a 
internal resource with xlink's attribute, href.

i found this different ways suggested:

<mets:FLocat xmlns:xlink="http://www.w3.org/1999/xlink"; 
LOCTYPE="URL" xlink:href="file://Scan00001.tif"/>

this second one:

<mets:FLocat xmlns:xlink="http://www.w3.org/1999/xlink"; 
LOCTYPE="URL" xlink:href="file:///Scan00001.tif"/>

(with 3 slash... i don't understand the difference)

and the last:

<mets:FLocat xmlns:xlink="http://www.w3.org/1999/xlink"; 
LOCTYPE="URL" xlink:href="Scan00001.tif"/>

when can i use these ways? are there differences?
thanks to all.



--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--



--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--

<Prev in Thread] Current Thread [Next in Thread>