Subject: Re: [jats-list] checking URIs From: "Beck, Jeff (NIH/NLM/NCBI) [E]" <beck@xxxxxxxxxxxxxxxx> Date: Thu, 14 Jun 2012 09:21:31 -0400 |
Hi Kevin, A URI could be nearly anywhere that character data is allowed, of course. But you should find most of the intended to be URIs in @xlink:href. But, because it is not a required attribute on either <ext-link> or the wildly unpopular <uri>, you may need to check the content of those two elements also - especially if the @ext-link-type or @content-type leads you to believe that is content you are interested in. Jeff On 6/13/12 5:30 PM, "Kevin Hawkins" <kevin.s.hawkins@xxxxxxxxxxxxxxxxxx> wrote: >I am interested in checking all URIs in JATS files. Well, not all URIs. > I am happy to ignore a URI that might for some reason be mentioned in >the prose of the article, but I'm interested in any actionable URIs, >even relative URIs giving the location of, say, a graphic. > >Given that scope ... > >a) Is it true that all such URIs are found in @xlink:html? Are there >any other attributes whose value is a URI? Or possibly an element whose >content is supposed to be a URI? > >b) Do people have suggestions on whether it's better to test that they >resolve (a link checker), testing for well-formedness as a URI, or both? > That is, does anyone know of URIs that resolve using some software but >which aren't valid according to RFC 3986? If so, for preservation >purposes, I think I would want to catch these. > >--Kevin
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[jats-list] checking URIs, Kevin Hawkins | Thread | Re: [jats-list] checking URIs, Kevin Hawkins |
[jats-list] checking URIs, Kevin Hawkins | Date | Re: [jats-list] checking URIs, Bruce Rosenblum |
Month |