search

tdwg / vocab

Vocabulary Maintenance Specification Task Group + SDS + VMS
11 stars 6 forks source link

Should navigation methods be specified in the documentation spec? #30

Closed baskaufs closed 8 years ago

baskaufs commented 8 years ago

The previous specification said that items in the table of contents should be hyperlinks to the text. I'm not sure that this matters as long as there is some navigation system. I don't think that DwC or AC follow this strictly, but use the navigation system that works well with the content management system that they use. See section 3.2.3.2 of the documentation spec

tucotuco commented 8 years ago

I agree that the previous specification is too constraining.

On Sat, Apr 16, 2016 at 1:09 PM, Steve Baskauf notifications@github.com wrote:

The previous specification said that items in the table of contents should be hyperlinks to the text. I'm not sure that this matters as long as there is some navigation system. I don't think that DwC or AC follow this strictly, but use the navigation system that works well with the content management system that they use.

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/tdwg/vocab/issues/30

ramorrismorris commented 8 years ago

How connected is this to decisions about hash vs slash as in #33 ? E.g., does one choice of hash vs slash make navigation easier of harder. It wouldn't seem to ...

baskaufs commented 8 years ago

I suppose in the olden days, one would use a hash to allow a browser to jump to an anchor. However, there must be ways to make this happen through URL re-writing on the server or something like that. Just try http://purl.org/dc/terms/replaces in your browser.

jar398 commented 8 years ago

That DC hack is quite old, it's just an HTTP redirect where the Location: header value contains a hash. It used to be this was a violation of the HTTP spec, and different browsers did different things with it, so it was considered Not a Good Idea. However, the issue was taken up by the HTTPbis WG, and in the recently revised HTTP spec, it's allowed. https://tools.ietf.org/html/rfc7231#section-7.1.2 It's highly likely the browsers have caught up. So you should consider it an option, if you like it.

baskaufs commented 8 years ago

References to hyperlinking were removed from Section 3.2.3.2.