[JSR358-4] The JSPA contains definitions - verify that Process Doc definitions do not conflict Created: 17/Aug/11  Updated: 10/Apr/14

Status: Open
Project: jsr358
Component/s: Editorial
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: pcurran Assignee: pcurran
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by JCPNEXT4-10 Verify that Process Doc definitions d... Resolved
Related
is related to JSR348-153 Licensor Name Space is not formally d... Closed
Tags: jsr364

 Description   

The summary says it all. Since we're not modifying the JSPA in this JSR we must be careful not to introduce definitions that conflict with the equivalent definitions in the JSPA.

We need to conduct a review to verify this.



 Comments   
Comment by pcurran [ 14/Sep/11 ]

Not practical, nor particularly valuable...

Comment by pcurran [ 01/Oct/11 ]

Rather than copying definitions from the JSPA to the Process Document, maybe we should say "the definitions in version x.y of the JSPA apply here."

Version x.y would be the version in effect when the Process Doc was finalized. Presumably there would never be a later version of the JSPA without a corresponding revision to the Process Doc?

Comment by pcurran [ 01/Oct/11 ]

I'll review the existing definions to make sure they don't conflict. However, I'm keeping this open (by deferring it) so we can address the broader issue in the future.

Comment by lightguard [ 06/Jul/12 ]

I think it makes sense to reference the definitions in the JSPA document which corresponds to the Process Document. There may be times we need to update them, but is that really much of an issue and push out a new Process Document point version updating the link between the two documents?

Generated at Wed Jul 01 02:30:40 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.