Task and Session Avatar
  1. OMG Specification

Task and Session — Closed Issues

  • Acronym: TSKSES
  • Issues Count: 23
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
TSKSES-30 Structural Feature bound_to TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-31 list_producers and related operations TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-32 NotRemoved exception TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-27 Task history event filter TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-28 AbstractResource key TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-29 Structural Feature is_in TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-24 $issue.summary TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-25 Task consumer/producer terminology TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-26 Produces association retraction. TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-23 Task structural feature list TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-22 Resource event declaration. TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-18 Task process argument TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-21 list_resource_by_type TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-17 create_workspace operation TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-20 Workspace – containment statements TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-19 Message TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-16 max_number argument TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-14 CDL state_set reference in connectstate TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-15 connectstate attribute TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-13 User – Structural Features List TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-12 AbstractPerson TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-10 BaseBusinessObject definition TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed
TSKSES-11 Usage and Containment type redundancy TSKSES 1.0b1 TSKSES 1.0b2 Resolved closed

Issues Descriptions

Structural Feature bound_to

  • Key: TSKSES-30
  • Legacy Issue Number: 2700
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: AbstractResource references the structural feature bound_to with the type Usage, however,
    the operations refer to Tasks as the type.
    Replace Usage with Task.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    resolved and closed

  • Updated: Fri, 6 Mar 2015 21:37 GMT

list_producers and related operations

  • Key: TSKSES-31
  • Legacy Issue Number: 2701
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: AbstractResource does not have operations required to notify it of the association of a Task
    as producer. Operations are required on AbstractResource to set, get, and change
    producer.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    resolved and closed

  • Updated: Fri, 6 Mar 2015 21:37 GMT

NotRemoved exception

  • Key: TSKSES-32
  • Legacy Issue Number: 2702
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: AbstractResource contains the declaration of the exception NotRemoved. This exception is
    not used in the remainder of the interfaces.
    Remove exception declaration.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    resolved and closed

  • Updated: Fri, 6 Mar 2015 21:37 GMT

Task history event filter

  • Key: TSKSES-27
  • Legacy Issue Number: 2697
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The semantics of the filter argument to the list_history operation are undefined.
    Nothing proposed at this stage.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    closed and resolved

  • Updated: Fri, 6 Mar 2015 21:37 GMT

AbstractResource key

  • Key: TSKSES-28
  • Legacy Issue Number: 2698
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Attribute key serves to provide unique identification. This is duplicating functionality of the
    inherited IdentifiableObject semantics.
    Propose removal of the key attribute and retraction of key arguments under the
    create_task, create_workspace, and create_subworkspace operations.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    resolved and closed

  • Updated: Fri, 6 Mar 2015 21:37 GMT

Structural Feature is_in

  • Key: TSKSES-29
  • Legacy Issue Number: 2699
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: AbstractResource references the structural feature is_an with the type Containment,
    however, the operations refer to Workspaces as the type.
    Replace Containment with Workspace.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    resolved and closed

  • Updated: Fri, 6 Mar 2015 21:37 GMT

${issue.summary}

  • Key: TSKSES-24
  • Legacy Issue Number: 2694
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Task state references state_set which is a CDL keyword and should be removed.
    Remove CDL state_set references.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    Remove CDL state_set references.

  • Updated: Fri, 6 Mar 2015 21:37 GMT

Task consumer/producer terminology

  • Key: TSKSES-25
  • Legacy Issue Number: 2695
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The operation add_consumer and add_producer are operations through which consumed
    and produced resources may be associated with a Task. Semantically, the operations are
    not adding “consumers” or “producers”, instead they are adding “consumed” and
    “produced” resources.
    Change the name of the operations to add_consumed and add_produced.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    closed and resolved

  • Updated: Fri, 6 Mar 2015 21:37 GMT

Produces association retraction.

  • Key: TSKSES-26
  • Legacy Issue Number: 2696
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: No operations are provided for the removal of a produces association between a Task and
    a AbstractResource produced by a Task (required on termination of the task).
    Add the operation to the Task interface.
    void remove_produced( in AbstractResource resource );
    Note… additional operations are required on AbstractResource concerning the produces
    association (refer issue 19, AbstractResource key).

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    closed and resolved

  • Updated: Fri, 6 Mar 2015 21:37 GMT

Task structural feature list

  • Key: TSKSES-23
  • Legacy Issue Number: 2693
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Task structural feature list references a consumer feature and equates the type to Usage.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    Updating of text in accordance with the exposed LinkKind constants.

  • Updated: Fri, 6 Mar 2015 21:37 GMT

Resource event declaration.

  • Key: TSKSES-22
  • Legacy Issue Number: 2692
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Workspace and Task both contain the operation oneway void resource_event (in
    ResourceEvent event) These declarations prevent the possibility of a developer
    constructing an interface that inherits from both Task and Workspace. Secondly, the
    definition of ResourceEvent is inconsistent with the currently adopted CosNotification
    definition of a structured event. Thirdly, the specification does not define an interoperable
    mechanisms through which events are propagated to targets (other than a reference to an
    underlying event service).

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    resolved and closed

  • Updated: Fri, 6 Mar 2015 21:37 GMT

Task process argument

  • Key: TSKSES-18
  • Legacy Issue Number: 2688
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Tasks represents user units or work, associated with consumed and produced resources.
    Consumed resource represent both execution and data resources and are exposed
    through the operation list_consumed. The combining of execution and data resources is
    inconsistent with the explicit declaration of the process argument (the execution resource)
    supplied during task creation. Secondly, the process argument type is inconsistent with
    the state semantics expected from a process (namely the exposure of state in a form
    equivalent to a task state).

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    resolved and closed

  • Updated: Fri, 6 Mar 2015 21:37 GMT

list_resource_by_type

  • Key: TSKSES-21
  • Legacy Issue Number: 2691
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The workspace operation – list_resource_by_type contains the resourcetype argument that
    is a string, however semantics of the string are undefined.
    Recommend that the type argument be considered as a filter against which object
    references are tested. The resourcetype operation argument should be changed to a
    CORBA::TypeCode.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    resolved and closed

  • Updated: Fri, 6 Mar 2015 21:37 GMT

create_workspace operation

  • Key: TSKSES-17
  • Legacy Issue Number: 2687
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The create_workspace operation takes a sequence of Users as an argument qualifying an
    access control list. However, no operations are available on Workspace to retrieve or
    modify the rights granted under the ACL. The list_workspaces operation is provided as a
    mechanism through which all workspaces to which a User is associated can be retrieved.
    In the case of the list_workspaces operation there is not mechanisms through which users
    other than the creating user can be notified of the association to a workspace.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    resolved and closed

  • Updated: Fri, 6 Mar 2015 21:37 GMT

Workspace – containment statements

  • Key: TSKSES-20
  • Legacy Issue Number: 2690
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Specification states “These operations will add and remove Containments of resources in a
    Workspace.” This statement is misleading in that Containment types are not referenced.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    resolved and closed

  • Updated: Fri, 6 Mar 2015 21:37 GMT

Message

  • Key: TSKSES-19
  • Legacy Issue Number: 2689
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Structural Feature list is inconsistent with IDL. The feature sent_to is not declared in the IDL
    of the Message object. This is ok if we assume that message is a locality constrained
    relative to the domain of the User object that the message belongs to. However, if Message
    is locally constrained, we need a user centric factory through which messages can be
    created.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    resolved and closed

  • Updated: Fri, 6 Mar 2015 21:37 GMT

max_number argument

  • Key: TSKSES-16
  • Legacy Issue Number: 2686
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The semantics of max_mumber argument used in several list operations is undefined.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    resolved and closed

  • Updated: Fri, 6 Mar 2015 21:37 GMT

CDL state_set reference in connectstate

  • Key: TSKSES-14
  • Legacy Issue Number: 2684
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: CDL delcaration of state_set are redundant with respect to the IDL definition.
    Remove CDL and integrate enumeration table with Connection State description.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    Remove CDL and integrate enumeration table with Connection State description.

  • Updated: Fri, 6 Mar 2015 21:37 GMT

connectstate attribute

  • Key: TSKSES-15
  • Legacy Issue Number: 2685
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Operation are provided for changing state from connected to disconnected. This is
    duplicated by the nature of the connectstate attribute declaration.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    Change connectstate to a readonly attribute.

  • Updated: Fri, 6 Mar 2015 21:37 GMT

User – Structural Features List

  • Key: TSKSES-13
  • Legacy Issue Number: 2683
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Features listed under the “Structural Features List are inconsistent with the specification and
    redundant with respect to the subsequent documented features within the User sub-section.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    resolved and closed

  • Updated: Fri, 6 Mar 2015 21:37 GMT

AbstractPerson

  • Key: TSKSES-12
  • Legacy Issue Number: 2682
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The current specification of AbstractPerson is declared as a placeholder for the definition of
    a generally agreed definition of person. Current initiatives within the OMG are addressing
    this in the light of definitions of person within the healthcare, manufacturing and finance
    domains. As an interim measure some level of interoperability is required to support the
    declaration of attributed data to the AbstractPerson as it is currently not possible to
    attribute the name of a person (or other information) in an interoperable manner.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    resolved and closed

  • Updated: Fri, 6 Mar 2015 21:37 GMT

BaseBusinessObject definition

  • Key: TSKSES-10
  • Legacy Issue Number: 2680
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: BaseBusienssObject is defined as an identifiable, transactional and life-cycle aware
    object. Two issues are identified with the currently IDL definition.
    · the inherited TransactionalObject is currently a depreciated interface
    · the interface uses CosObjectIdentity::IdentifiableObject as the means through which
    objects are comparable (e.g. used to identify an object such as a resource during an
    operation to remove the identifies instance from a Workspace). IdentifiableObject
    provides identity within a single administrative domain, however, Workspaces may
    contain references from local and remote domains. As such, the identity as returned
    from IdentifiableObject may be the same for two distinctly different references
    contained within a single workspace, creating an ambiguity for operations such as
    object removal.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    issue resolved, see below

  • Updated: Fri, 6 Mar 2015 21:37 GMT

Usage and Containment type redundancy

  • Key: TSKSES-11
  • Legacy Issue Number: 2681
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Usage and Containment are declared under the list of core Task and Session interfaces,
    however, both Usage and Containment are empty interfaces that are not referenced by
    any operations within the specification.

  • Reported: TSKSES 1.0b1 — Wed, 2 Jun 1999 04:00 GMT
  • Disposition: Resolved — TSKSES 1.0b2
  • Disposition Summary:

    resolved and closed

  • Updated: Fri, 6 Mar 2015 21:37 GMT