[JSR358-6] Member vs. Member Representative confusion Created: 19/Sep/11  Updated: 24/Feb/15  Resolved: 24/Feb/15

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

Type: Bug Priority: Minor
Reporter: Bill Shannon Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
is duplicated by JCPNEXT4-11 Member vs. Member Representative conf... Closed


An Expert can be either a Member (company) or Member Representative (person).

A Spec Lead is an Expert.

A Spec Lead Member is an individual JCP member (Member?), or the company that
employs the Spec Lead.

It seems weird that an Expert can be a company or a person and thus that a
Spec Lead can be a company or a person, and then we need Spec Lead Member
to refer to one of the cases.

Wouldn't it be simpler for Expert and Spec Lead to always be a person, and then
have Spec Lead Member (and Expert Member, if needed), to cover the cases where
you need to refer to the company?

Or, define Expert Representative and Spec Lead Representative to parallel
Member Representative.

Depends on whether most uses of (e.g.) Spec Lead intend to refer to the person
or the company.

It seems weird for Expert to be a company since part of the definition is
"has expert knowledge" and "an active practitioner in the technology". Can
a company do either of those?

Comment by pcurran [ 27/Sep/11 ]

You're probably right (my head is spinning) but remember that we're inheriting definitions from the JSPA and we must be careful not to re-define or contradict.

Please either suggest specific changes, or agree that we can defer this until later

Comment by pcurran [ 29/Sep/11 ]

Risk of making fundamental changes at this stage is too great.

Agreed at September 29 WG meeting that we will defer this.

Comment by pcurran [ 24/Feb/15 ]

This has been fixed in the version of the Process Document being developed through JSR 364.

Generated at Thu Jul 30 14:36:35 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.