[tdwg-guid] Embedding LSID links within Publications

[Donat Agosti]

Hi Rich

I think, there are two issues. There are two versions of the publications,
the underlying xml and the pdf/hard copy.

1. What we need is an xml version of the document which includes all the
lsids, etc. For a name, that would look like

               <tax:name>
                    <tax:xid source="HNS" identifier="141015"/>
                    <tax:xmldata>
                        <dc:Genus>Formica</dc:Genus>
                        <dc:Species>rubra</dc:Species>
                    </tax:xmldata>rubra</tax:name>
                <tax:status>nov. spec.</tax:status>

Replace HNS with LSID, or ZooBank, etc.

This needs to be the original document.

2. Then you need an XSLT which transforms it into whathever style and layout
you want, such as pdf, or what journal style it has to be.

3. Whether you want to expose the lsid, make it clickable is then up to you,
and need be discussed on an individual base. In most cases it would be
enough to be able to click on a name and get back the data the  LSID
resolver delivers - which is what you have to decide at Zoobank. This allows
also displaying documents in various ways, such as generic html with links,
the original pdf, xml, etc.

If we are serious about access to the content of publications, we need focus
on the xml version rather then pdf.


Donat





-----Original Message-----
From: tdwg-guid-bounces at lists.tdwg.org
[mailto:tdwg-guid-bounces at lists.tdwg.org] On Behalf Of Richard Pyle
Sent: Monday, December 03, 2007 9:52 AM
To: 'Paul Kirk'; 'Gregor Hagedorn'; tdwg-guid at lists.tdwg.org
Subject: RE: [tdwg-guid] Embedding LSID links within Publications


Let's distinguish between the two separate places where there may be LSIDs
in the document:

1) Underneath the header for each of the five new species described in the
article.

2) Embedded within clicakble links scattered through the introduction,
discussion, etc. (what I call "prose"), which are not themselves registered
nomenclatural acts; but are simply "links of convenince" to allow someone
reading the PDF to simply click on a highlighted word or symbol and be
redirected (presumably through a web browser) to some sort of online
resource (image, video, SDD document, whatever...)

As for #1, I believe that the LSID should be displayed to the human reader
in full, and probably should *also* be a clickable link directly to the
ZooBank record for that LSID. Displaying the full LSID here is appropriate,
because the publication itself represents the Code-governed creation event
behind that LSID. It also does not interrupt the "flow", because there is no
"flow" to the header of a new species account.

As for #2, there is "flow" here, because people are reading a normal
paragraph or text. Offsetting a clickable word in blue or underlined or with
some sort of Mouseover highlighting does not interrupt the flow -- but
inserting an LSID in parentheses within the text does interrupt the flow of
reading.

So....in this context, my current preferred way of displaying it in the
formatted PDF is:

1) Show the LSID for the 5 new species names, as part of header for the new
species treatment (just like listing a holotype, etc.) The only question
here is whether I show only the UUID, or do I show the UUID "wrapped" within
the LSID syntax.  In order to help promote LSIDs (in keeping with the
TDWG/GBIF agenda at the moment), I'm leaning towards displaying the complete
LSID; but perhaps mentioning in the methods that the ZooBank Registration ID
is the UUID, but they are shown formatted with complete LSID resolving
syntax.

2) Do not show the LSID for other clickable links within the "prose" of the
document, but embed those LSIDs in the (hidden) link URL. I'm still not sure
whether the word/name itself will be the clickable "thing", or whether I'll
add some sort of standard symbol analagous to a footnote number that the
user would click.

3) Display full URLs in an "Appendix" sort of section, at the end of the
rest of the article, so they can be seen via the paper-printed version.

Does this make sense?  Or am I stoned...? :-)

Rich

> -----Original Message-----
> From: Paul Kirk [mailto:p.kirk at cabi.org] 
> Sent: Sunday, December 02, 2007 10:39 PM
> To: Richard Pyle; Gregor Hagedorn; tdwg-guid at lists.tdwg.org
> Subject: RE: [tdwg-guid] Embedding LSID links within Publications
> 
> But Rich, the prose you refer to are the ... 'this is a 
> really neat fish, just look at the video' discussion rather 
> than the techie ICZN stuff ... Aus bus sp. nov ... LSID, 
> Latin daignosis, holotype etc ...
> which, at the risk of being stoned (having rocks thrown at me 
> ... ;-) ... I mean) as an heretic, could perhaps be usefully 
> lost in an appendix, and thus disposed would not interrupt the flow.
> 
> Paul
> 
> -----Original Message-----
> From: tdwg-guid-bounces at lists.tdwg.org
> [mailto:tdwg-guid-bounces at lists.tdwg.org] On Behalf Of Richard Pyle
> Sent: 01 December 2007 00:48
> To: 'Gregor Hagedorn'; tdwg-guid at lists.tdwg.org
> Subject: RE: [tdwg-guid] Embedding LSID links within Publications
> 
> 
> Thanks, Gregor -- this is very helpful, and I pretty much agree.
> 
> > In short: allow any normal publishing practice, consider it as a 
> > special form of reference (like doi or ISBN) and observe the normal 
> > publishing practices of citing, especially avoid 
> redundancies. Rich, I
> 
> > think you are too much thinking about general rules how to always 
> > handle it - but publishing practice for good reasons does 
> almost the 
> > opposite (once and never again...).
> 
> Fair enough....and I'm sure I am over-thinking this.  
> However, I still see problems with your proposed approached, 
> in that I do not want big, cumbersome LSIDs (even once) 
> interrupting the flow of prose.
> 
> I think I still favor the idea of a superscript indicator 
> that can be easily ignored, easily clicked, and easily used 
> to refer to a printed (not hidden) set of hyperlinks 
> following the "Literature Cited" section.
> I think this strikes a resonable compromise/balance between 
> how things are done in the publishing world, and how *I* 
> think things *should* be done in the publishing world.... 
> 
> :-)
> 
> Rich
> 
> 
> _______________________________________________
> tdwg-guid mailing list
> tdwg-guid at lists.tdwg.org
> http://lists.tdwg.org/mailman/listinfo/tdwg-guid
> **************************************************************
> **********
> The information contained in this e-mail and any files 
> transmitted with it is confidential and is for the exclusive 
> use of the intended recipient. If you are not the intended 
> recipient please note that any distribution, copying or use 
> of this communication or the information in it is prohibited. 
> 
> Whilst CAB International trading as CABI takes steps to 
> prevent the transmission of viruses via e-mail, we cannot 
> guarantee that any e-mail or attachment is free from computer 
> viruses and you are strongly advised to undertake your own 
> anti-virus precautions.
> 
> If you have received this communication in error, please 
> notify us by e-mail at cabi at cabi.org or by telephone on +44 
> (0)1491 829199 and then delete the e-mail and any copies of it.
> 
> CABI is an International Organization recognised by the UK 
> Government under Statutory Instrument 1982 No. 1071.
> 
> **************************************************************
> ************
> 
> 


_______________________________________________
tdwg-guid mailing list
tdwg-guid at lists.tdwg.org
http://lists.tdwg.org/mailman/listinfo/tdwg-guid