Subject: [jats-list] Ambiguity in <uri> definition From: "Tony Graham" <tgraham@xxxxxxxxxx> Date: Mon, 10 Mar 2014 20:56:19 -0000 (GMT) |
The definition for <uri> in "Article Authoring Tag Library NISO JATS Draft Version 1.1d1" is: Identifies a Uniform Resource Identifier (such as a URL) that may be used as a live link, typically naming a website, such as: <uri>http://www.mulberrytech.com</uri>). "may be used as a live link", to my mind, implies that the example "<uri>http://www.mulberrytech.com</uri>" is sufficient to make a 'live link' in a styled output, but making it live requires uri/@xlink:href as well. That <uri> "may or may not be a traversable link" is discussed under "Related Elements" without saying what makes a <uri> into a traversable link, and none of the three examples show a uri/@xlink:href. (There's also an unpaired ")" in the definition.) FWIW, the current JATS Preview Stylesheets come at it from the other direction and, for FO output at least, assume that uri/@xlink:href is always present and will show the uri/@xlink:href value as the link's text if the <uri> doesn't have a string value. Regards, Tony Graham tgraham@xxxxxxxxxx Consultant http://www.mentea.net Chair, Print and Page Layout Community Group @ W3C XML Guild member -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Mentea XML, XSL-FO and XSLT consulting, training and programming
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [jats-list] Update requested fo, Bruce Rosenblum | Thread | Re: [jats-list] Ambiguity in <uri> , Debbie Lapeyre |
[jats-list] Update requested for ex, Bruce Rosenblum | Date | Re: [jats-list] Ambiguity in <uri> , Debbie Lapeyre |
Month |