Charles Roper wrote:
On 20/10/06, Lachlan Hunt <[EMAIL PROTECTED]> wrote:
Where does it say in the spec that an href attribute has to point to to
a network-retrievable resource? It explicitly allows URIs, including
both URLs and URNs.
OK, I should rephrase that to "If it were a URL then that would be
more practical for an href surely?"
You're only saying that because most implementations don't support LSID
URIs yet, but you already showed me a working implementation of it that
does make it practical for those users.
However, providing a *direct* link to the resource described by the
LSID isn't the intended aim of the microformat; the LSID is in there
as metadata that describe a resource, while the normal hyperlink, if
there is one, probably points to something else entirely.
What's wrong with providing 2 links? One to the LSID, another to the
related information.
How might that work, given that you probably don't want the user to
see the LSID?
Why wouldn't you want the user to see it? What benefit does it provide
if a user can't do anything with it?
That LSID implementation you showed me earlier seems like quite a good
reason to show it. The fact that it's not a widely deployed extension,
nor a widely supported URI scheme, is a rather minor point if you think
about how fast such implementations can spread. If you give users a
reason to add support to their browser and given that there is already
at least 3 separate LSID implementations, it probably will.
http://lsid.biopathways.org/lsid_browser/lsid_browser_1_0_0.html
http://lsid.mozdev.org/
http://lsid.sourceforge.net/
Just consider how fast the feed:, skype:, callto: and other URI schemes
have spread and became relatively widely supported in feed readers and
IM clients. My point is lack of widely deployed implementations now is
not a reason to avoid using it in the future.
For example say I have this markup:
<a href="http://www.species.com/lutra_lutra/";>View information about
<span class="taxon LSIDHere">Otters</span></a>
What wrong with something like this structure?
<span class=="taxon">
<a href="/lutra_lutra/">View information about <span
class="species">Otters</span></a>
(<a href="lsidres:..." class="lsid">LSID</a>)
</span>
There's probably an even better way, but I have no idea about species or
this microformat, so I'm probably not the best person to come up with
the format.
--
Lachlan Hunt
http://lachy.id.au/
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
