Documentation URL for current version missing

0 views
Skip to first unread message

Rubén Navarro Piris

unread,
Feb 26, 2016, 5:08:36 AM2/26/16
to Stardog
Hi!

I noticed that the online documentation can be requested for a specific version by adding the version as path variable (e.g. http://docs.stardog.com/4.0.3/#_snarl_protocol_buffers).
However, this doesn't work with the latest version (e.g. http://docs.stardog.com/4.0.5/#_snarl_protocol_buffers).

Cheers!

Ruben

Kendall Clark

unread,
Feb 26, 2016, 8:33:57 AM2/26/16
to Stardog
Ruben,

Thanks for the feedback. That is by design. The "head" of the docs URL always points to the latest released version.

Cheers,
Kendall

--
-- --
You received this message because you are subscribed to the C&P "Stardog" group.
To post to this group, send email to sta...@clarkparsia.com
To unsubscribe from this group, send email to
stardog+u...@clarkparsia.com
For more options, visit this group at
http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en

Rubén Navarro Piris

unread,
Feb 26, 2016, 1:48:33 PM2/26/16
to sta...@clarkparsia.com

Hi Kendall!

Yes, that's fine. But I would like for the specific versioned URL to work. Otherwise I need to change the URL scheme whenever I want to reference either an older version or the latest one (which is kind of annoying).

Is it possible to support both the HEAD and the version URL for latest?

Cheers!

Ruben

---
You received this message because you are subscribed to a topic in the Google Groups "Stardog" group.
To unsubscribe from this topic, visit https://groups.google.com/a/clarkparsia.com/d/topic/stardog/SlfqTn_jDLo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to stardog+u...@clarkparsia.com.

Kendall Clark

unread,
Feb 29, 2016, 9:34:27 AM2/29/16
to sta...@clarkparsia.com
I'm not sure I understand the requirement, except that it sounds like you want to automate downloading the docs to some internal site or something. Otherwise I can't see how this matters.

I'd be more inclined to change this if I understood why it's necessary. :>

Cheers,
Kendall

Rubén Navarro Piris

unread,
Mar 4, 2016, 7:33:40 AM3/4/16
to Stardog
Hi Kendall!

My biggest concern is referencing the actual version used when writing my documentation. If I test it again version 4.0.5 (the current), I don't get a permalink to this documentation, meaning that the day version 4.0.6 (or whatever comes) is released, my link will be (semantically) broken (since it will not point to 4.0.5, but 4.0.6, and maybe one week later 4.1.0 and so on).

If a link with the version tag also for the latest version was available, I wouldn't have this problem.

Best regards

Ruben

Rubén Navarro Piris

unread,
May 24, 2016, 7:42:39 AM5/24/16
to Stardog
Hi Kendall!

Since the recent release of stardog 4.1, the problem I was talking about occurs. Since all my links referenced the "current release" (at the moment 4.0.5), they are all now inconsistent, since they point to version 4.1.0. When are you planning on exposing the current release with the corresponding version tag also?

Cheers!

Ruben
Reply all
Reply to author
Forward
0 new messages