jsr358
  1. jsr358
  2. JSR358-6

Member vs. Member Representative confusion

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Component/s: Membership roles
    • Labels:
      None

      Description

      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?

        Issue Links

          Activity

          Bill Shannon created issue -
          Hide
          pcurran added a comment -

          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

          Show
          pcurran added a comment - 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
          pcurran made changes -
          Field Original Value New Value
          Tags need_comments
          pcurran made changes -
          Tags need_comments Defer need_comments
          Hide
          pcurran added a comment -

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

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

          Show
          pcurran added a comment - Risk of making fundamental changes at this stage is too great. Agreed at September 29 WG meeting that we will defer this.
          pcurran made changes -
          Tags Defer need_comments Defer
          pcurran made changes -
          Project jsr348 [ 12019 ] jsr358 [ 12683 ]
          Key JSR348-115 JSR358-6
          pcurran made changes -
          Priority Major [ 3 ] Minor [ 4 ]
          Component/s Membership roles [ 14519 ]
          pcurran made changes -
          Tags Defer
          pcurran made changes -
          Link This issue duplicates JCPNEXT4-11 [ JCPNEXT4-11 ]
          pcurran made changes -
          Link This issue is duplicated by JCPNEXT4-11 [ JCPNEXT4-11 ]
          pcurran made changes -
          Link This issue duplicates JCPNEXT4-11 [ JCPNEXT4-11 ]
          Hide
          pcurran added a comment -

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

          Show
          pcurran added a comment - This has been fixed in the version of the Process Document being developed through JSR 364.
          pcurran made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Resolution Fixed [ 1 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              Bill Shannon
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: