[Bug 136] New: Use of begin with context and nested context needs more specification

[bugzilla-daemon@arjuna.com]

http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=136

           Summary: Use of begin with context and nested context needs more
                    specification
           Product: WS-Context
           Version: 1.0
          Platform: PC
        OS/Version: Windows 2000
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Text and diagrams
        AssignedTo: ws-caf@lists.oasis-open.org
        ReportedBy: peter.furniss@choreology.com
         QAContact: mark.little@arjuna.com


A context can contain a list of child-contexts; in the absence of explicit 
constraint, these can themselves contain child-contexts to any level. The 
specification of begin states that a contextualized begin causes the creation 
of a nested context, but there are unspecified details:

a) if the context on a begin already contains child-contexts, is the new 
context a child of the received parent (a sibling of the existing children), or 
a child of one of the children ? (or grand-children ?).  

b) whatever the answer to a), how does one create the opposite - how to add a 
grandchild if begin+context adds a first level child; how to add a sibling if 
begin+context adds at the lowest level

A possible answer is to add a "parent-identifier" attribute to begin, which is 
the context identifier in the supplied nest that is to be the immediate parent 
of the new context. If the parameter is absent, the new context is a first-
generation child of the supplied context.

c) can the context on a begin be supplied by reference ?

if the answer to c) is yes, is it a requirement of a context service 
implementation that it supports this ?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.