Issues for Mailing list of the Lightweight CCM 2003 Finalization Task Force

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 6254: LWCCM issue - Section 1.5.3 Exclusion
Issue 7027: LwCCM issue - Section 1.4.3.3 Exclusion
Issue 7028: LwCCM issue - Section 1.6.8 Exclusion
Issue 7126: lwCCM issues - transaction
Issue 7127: lwCCM issues - security
Issue 7128: lwCCM issues - persistence
Issue 7129: lwCCM issues - entity components
Issue 7130: lwCCM issues - section 4.1.2
Issue 7131: lwCCM issues - abstract storage type
Issue 7132: lwCCM issues - abstract storage home
Issue 7133: lwCCM issues - CIDL
Issue 7141: lwCCM issues - locator
Issue 7142: lwCCM issues - segmentation
Issue 7143: lwCCM issues - get_all_facet, ...
Issue 7144: lwCCM issues - primary key
Issue 7145: lwCCM issues - Section 4.1
Issue 7146: lwCCM issues - configurators
Issue 7147: lwCCM issues - proxy homes
Issue 7148: lwCCM issues - home finders and finder operations
Issue 7149: lwCCM issues - invalid rows
Issue 7150: lwCCM issues - Entity2Context
Issue 7363: Dependency on D+C FTF

Issue 6254: LWCCM issue - Section 1.5.3 Exclusion (lwccm-ftf)

On page 11: The Normative Impact "Disable get_connections, get_all_receptacles, get_named_receptacles operations in the Receptacles interface" does not match the Document Impact: "Section 1.5.3: remove". Removal of section 1.5.3 removes the Receptacles interface in it entirety, including the description of the generic connect and disconnect operations, which are referred to by comment in the previous item. The Document Impact needs to be narrowed.

While reviewing Victor's issue on section 1.5.3, I noticed
that a similar problem exists with respect to the Navigation
interface.


While the normative exclusion "disable get_all_facets, get_
named_facets, same_component operations in Navigation
interface" retains the generic provide_facet operation,
removing section 1.4.3.3 would remove the entire Navigation
interface.


On the other hand, the still-present section 1.4.3.4 references
the disabled operations.


Proposed resolution:


In section 10.3, in the "Document Impact" column of the second
row, replace the text


  1.4.3.3: remove


with


  1.4.3.3: remove these operations from the Navigation
  interface. Also remove the PortDescription, FacetDescription
  and FacetDescriptions types.

  1.4.3.4: remove

While reviewing Victor's issue on section 1.5.3, I noticed 
that a similar problem exists with respect to the Events 
interface. 

While the normative exclusion "disable get_all_consumers 
[...]" (8th row of section 10.3) retains the generic 
get_consumer, subscribe, unsubscribe, connect_consumer 
and disconnect_consumer operations, removing section 1.6.8 
would remove the entire Events interface. 

Proposed resolution: 

In section 10.3, in the "Document Impact" column of the 
8th row, replace the text 

  Section 1.6.8: remove 

with 

  Section 1.6.8: remove these operations from the Events 
  interface. Also remove the ConsumerDescription, 
  EmitterDescription, SubscriberDescription and 
  PublisherDescription types. 

This issue concerns the table 4.4 "exluding support for transaction", there
are still references to the transaction feature in the following sections:
4.2 (§1), 4.2.1, 4.2.12 (basic), 4.5.1.1 (point 2), 4.5.1.4, 4.5.2.4



Proposed resolution:


Add a row in the table 4.4 with :
"Normative Exclusion" column : Exclude support for transaction
"Document Impact" column : Section 4.2, paragraph 1: remove reference to
transaction
        Section 4.2.1, paragraph 1: remove reference to transaction
        Section 4.2.12: remove reference to transaction
        Section 4.5.1.1, point 2: remove reference to transaction
        Section 4.5.1.4: remove reference to transaction
        Section 4.5.2.4: remove reference to transaction

This issue concerns the table 4.5 "exluding support for security", there are
still references to the security feature in the following sections:
4.2 (§1), 4.2.1, 4.2.12 (basic), 4.5.1.1 , 4.5.1.5, 4.5.2.5



Proposed resolution:


Add a row in the table 4.5 with :
"Normative Exclusion" column : Exclude support for security
"Document Impact" column : Section 4.2, paragraph 1: remove reference to
security
        Section 4.2.1, paragraph 1: remove reference to security
        Section 4.2.12: remove reference to security
        Section 4.5.1.1: remove reference to security
        Section 4.5.1.5: remove reference to security
        Section 4.5.2.5: remove reference to security

This issue concerns the table 4.1 "exluding support for Persistence"; there
are still references to persistence in the following sections:
4.2 §1, 4.2.1 §1, 4.2.12



Proposed resolution:


Add a row in the table 4.1 with :
"Normative Exclusion" column : Exclude support for persistence
"Document Impact" column : Section 4.2, paragraph 1: remove reference to
persistence
        Section 4.2.1, paragraph 1: remove reference to persistence
        Section 4.2.12: remove reference to persistence

This issue concerns the table 4.1 "exluding support for Persistence", row 7;
there are still references to entity components in the following sections:
3.3.3.3, 4.5.1.3 (§1), 4.5.2.3 (point 3)



Proposed resolution:


Row 7 in the table 4.1, add in the "Document Impact" column : 
Section 3.3.3.3: remove references to entity components
Section 4.5.1.3, paragraph 1: remove references to entity components
Section 4.5.2.3, point 3: remove references to entity components

This issue concerns the table 4.1 "exluding support for Persistence", row 7;
the section 4.1.2 doesn't have to be fully removed. Only the references to
entiy  container have to.



Proposed resolution:


Row 7 in the table 4.1, add in the "Document Impact" column, replace
"Section 4.1.2: remove" by "Section 4.1.2: remove reference to entity
container API types".

This issue concerns the table 4.1 "exluding support for Persistence", row 4;
there are still references to abstract storage type in the following
sections:
3.2.2 (§2), 3.2.6, 3.2.9 (point 4)



Proposed resolution:


Row 4 in the table 4.1, add in the "Document Impact" column : 
Section 3.2.2, paragraph 2: remove references to abstract storage type
Section 3.2.6: remove references to abstract storage type
Section 3.2.9, point 4: remove references to abstract storage type

This issue concerns the table 4.1 "exluding support for Persistence", row 3;
there are still references to abstract storage homes in the following
sections:
1.7.4, 3.2.5 (§4), 3.2.6



Proposed resolution:


Row 3 in the table 4.1, add in the "Document Impact" column : 
Section 1.7.4: remove references to storage home
Section 3.2.5, paragraph 4: remove references to abstract storage home
Section 3.2.6: remove references to abstract storage home

This issue concerns the table 4.1 "exluding support for Persistence", row 2;
and the table 4.3 "exluding support for segmentation", row 1: there are
still references to CIDL in the following sections:
1.5.2.1 (§1), 3.1 (§1)


Proposed resolution:


Row 2 in the table 4.1 and Row 1 in the table 4.3, add in the "Document
Impact" column : 
Section 1.2.2.1, paragraph 1: remove references to CIDL
Section 3.1, paragraph 1: remove references to CIDL

This issue concerns the table 4.3 "exluding support for segmentation", row
3; there are still references to locator in the following sections:
3.3.3.5, paragraph 4 and last paragraph



Proposed resolution:


Row 3 in the table 4.3, in the "Document Impact", add: 
Section 3.3.3.5, paragraph 4 and last paragraph: remove references to
locator

This issue concerns the table 4.3 "exluding support for segmentation", there
are still references to segmentation in the following sections:
: 3.2.1.6 (§1), 3.2.11 (§1), 3.2.9 (point 2), 4.2.12 (extended)

This issue concerns the table 4.2 "exluding support introspection,
navigation, ...", row 2; there are still references to these operations in
the following sections:
1.4.3, point 3 and 4, section 1.4.3.4, paragraph 1



Proposed resolution:


Row 2 in the table 4.2, in the "Document Impact", add: 
Section 1.4.3, point 3 and 4: remove references to these operations
Section 1.4.3.4, paragraph 1: remove references to these operations 

This issue concerns the table 4.1 "exluding support for Persistence", row 1;
there are still references to primary key in the following sections:
1.7.1 (§1 & §3), 1.7.4, 1.7.5.1 (§1, §2), 1.7.5.2 (§1, §2)



Proposed resolution:


Row 1 in the table 4.1, add in the "Document Impact" column : 
Section 1.7.1, paragraph 1 and 3: remove references to primary key
Section 1.7.4: remove references to primary key
Section 1.7.5.1, paragraph 1and 2: remove references to primary key
Section 1.7.5.2, paragraph 1and 2: remove references to primary key

This issue concerns the table 4.1 "exluding support for Persistence"; in the
"Document Impact" column, row 1, the § 3 doesn't exist in the section 1.1.4.


Proposed resolution:
Table 4.1, row 1, column "Document Impact": replace "Section 1.1.4,
paragraph 3: remove" by "Section 1.1.4, paragraph 2: remove"

This issue concerns the table 4.6 "exluding support for configurators";
there are still references to configurators in the following sections:
1.10.2 (second point), 1.10.2.1 (§2), 1.11.1 (configuration_complete)

This issue concerns the table 4.7 "exluding support for proxy homes", row 1;
in section 3.2.5, the last paragraph should be removed.



Proposed resolution:


Row 1 in the table 4.7, in the "Document Impact", add: 
Section 3.2.5 last paragraph:remove

This issue concerns the table 4.8 "exluding support for home finders" there
are still references to finder operations and home finders in the following
sections:
1.7.1 (§2), 1.7.1.1, 1.7.3, 1.7.3.3, 1.7.4 (§1), 1.7.5 (heterodox), 3.3.6
(point 5), 4.3.2.1 (get_CCM_home), 4.5, 4.5.1 (point 4, last §), 4.5.1.1
(last point), 4.5.1.2
The following sections have to be removed:
1.7.3.2, 4.5.1.3, 4.5.2.3



Proposed resolution:


Add a row in the table 4.8 with :
"Normative Exclusion" column : Exclude support for home finders and finder
operations
"Document Impact" column : 
        Section 1.7.1, paragraph 2: remove reference to home finders and
finder operations.
        Section 1.7.1.1: remove reference to home finders and finder
operations.
        Section 1.7.3: remove reference to home finders and finder
operations.
        Section 1.7.3.3: remove reference to home finders and finder
operations.
        Section 1.7.4 paragraph 1: remove reference to home finders and
finder operations.
        Section 1.7.5 (heterodox): remove reference to home finders and
finder operations.
        Section 3.3.6, point 5: remove reference to home finders and finder
operations.
        Section 4.3.2.1 (get_CCM_home): remove reference to home finders and
finder operations.
        Section 4.5: remove reference to home finders and finder operations.
        Section 4.5.1, point 4 and last paragraph: remove reference to home
finders and finder operations.
        Section 4.5.1.1, last point: remove reference to home finders and
finder operations.
        Section 4.5.1.2: remove reference to home finders and finder
operations.
        Section 1.7.3.2: remove
        Section 4.5.1.3: remove
        Section 4.5.2.3: remove

This issue concerns the table 4.7 "exluding support for proxy homes", row 2
and 3 are not valid



Proposed resolution:

remove the rows 2 and 3 of the table 4.7

This issue concerns the table 4.1 "exluding support for Persistence", row 7;
there are still references to Entity2Context in the following sections:
 3.2.11 (§2)



Proposed resolution:


Row 7 in the table 4.1, in the "Document Impact", add: 
Section 3.2.11, paragraph 2:remove reference to the Entity2Context
interface.

Lightweight CCM replaces CCM's Packaging and Deployment chapter
with the "Deployment and Configuration of Component-based Distributed
Applications" (D+C) specification, and thus Lightweight CCM cannot be
finalized before D+C.


I propose to defer this issue to a second FTF, to be resolved by the
availability of D+C.