[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Fw: Guidance on using relative links in OASIS specifications
Chet, any update on this? We're looking to finish up changes to the 7 part OSLC Core specs and they have quite a few relative links that will either be broken, or will require manual updates when published to the OASIS document repository.
I think the primary issue is that we can't use relative links because the file names get changed when the documents are published.Â For example, OSLC Core Vesion 3.0. Part 1: Overview Committee Specification revision 03 has published URL:
However, the actual file name in the GitHub repo is simply oslc-core.html.
Perhaps OASIS could consider changing the naming guidelines to not put variable information like version, revision number and document status in the published file name. This should be unnecessary because it is also included in the path and results in variable but redundant information. In the URL above, oslc-core-v3.0-csprd03-part1-overview.html is redundant with oslc-core/v3.0/csprd03/part1-overviewin the path. If this redundancy could be eliminated, then the file name would be unchanged when published, and all relative links would work fine.
If you would like to consider this, we could certainly change the names of the files to better reflect their title and part.
Jim Amsden, Senior Technical Staff Member
OSLC and Linked Lifecycle Data