[JSR358-62] Add named anchors for all defined terms in the Process Document Created: 08/Apr/14  Updated: 24/Feb/15  Resolved: 24/Feb/15

Status: Closed
Project: jsr358
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: pcurran Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by JCPNEXT4-24 Add named anchors for all defined ter... Resolved

 Description   

Mark Reinhold suggests:

It'd be very helpful if each term in the Definitions section had an HTML anchor, so that other documents could refer directly to specific terms.

Example: If the HTML for the definition of Profile Specification looked like this:

<p><a name="def-profile-specification">
<b>Profile Specification (Profile)</b>: A Specification that references
one of the Platform Edition Specifications and zero or more other JCP
Specifications (that are not already a part of a Platform Edition
Specification.) APIs from the referenced Platform Edition must be
included according to the referencing rules set out in that Platform
Edition Specification. Other referenced Specifications must be
referenced in their entirety.</p>

Then I could refer to it like this:

... is a Profile Specification <a
href="http://jcp.org/en/procedures/jcp2#def-profile-specification">as
defined in the Java Community Process</a>.

so that if someone clicks on the link they're taken directly to the term rather than to the top of the Process Document page.



 Comments   
Comment by heathervc [ 06/May/14 ]

We will add when we update the process document for JSR 364.

Comment by pcurran [ 24/Feb/15 ]

Fixed in the version of the Process Document being developed through JSR 364.

Generated at Mon Mar 30 14:28:01 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.