ASSEMBLY-43

for implentations.*'s fix attributes that should show qnames as values

ASSEMBLY-1

Is binding.sca always present?

If a component service is configured with binding.ws, can be accessed by a component reference in the same composite with binding.sca?

ASSEMBLY-3

Is interface.java specification normative in SCA-Assembly spec?

No action is required

ASSEMBLY-5

component type allows to specify wire targets on references

Push teh getTargets() method from Reference to ComponentReference

ASSEMBLY-6

usage of not promoted references

Make sure the reference resolution follows what's described by the assembly spec

ASSEMBLY-23

SCA <anyAttribute.../> declarations should use namespace ##other rather than ##any

8

SCDL artifact resolution underspecified

Adjust the artifact resolution based on the proposal in this JIRA Update the xsd from OASIS

ASSEMBLY-25

Can Implementation change property values after instantiaion

14

Conflicting Specification of Values for Many-Valued StringProperties

Adjust the property value processing to conform to the new syntax No action is required

ASSEMBLY-28

Missing XSD for contributions

16

Component URI is not well described

Tuscany needs to support the structural URI based on this proposal Update the xsd from OASIS. Update the Import/Export model to
be extensible as the XSD allows xsd:any and xsd:anyAttribute

ASSEMBLY-38

Clarify whether a Default Value for a Property must appear inthe componentType of an implementation

17

Need to define Namespace handling for included Composites

Tuscany needs to adjust how the composite include is aggregated based on the proposal in this JIRA No action is required

ASSEMBLY-39

Permit intents and PolicySets on <interface/> elements

The policy model needs to be changed so that interface can have intents/policySets attached.

18

XSD definitions of Component Service and Component Referencehave unintended features

ASSEMBLY-40

Autowire at the domain level

23

SCA <anyAttribute.../> declarations should use namespace ##other rather than ##any

Update the xsd from OASIS Tuscany needs to decide if/how it will support the domain-level autowiring

ASSEMBLY-42

Autowire value for the logical domain composite

25

Can Implementation change property values after instantiaion

No action is required I think Tuscany is OK here as the autowire=false for the domain composite

ASSEMBLY-57

Unresolved bindings on references

28

Missing XSD for contributions

Update the xsd from OASIS. Update the Import/Export model to
be extensible as the XSD allows xsd:any and xsd:anyAttribute Add the support for "componentName/serviceName/bindingName" as the wire target

ASSEMBLY-67 Component Type file name is too restrictive 32

"SCA schema fixes requested for sca-core.xsd (based on OSOA site versions that may be copied to OASIS site)"

ASSEMBLY-68 ComponentType Properties should not have a source 35

Confusing words in Section 5.3 relating to ConversationalIntent

ASSEMBLY-35

Confusing words in Section 5.3 relating to ConversationalIntent

38

Clarify whether a Default Value for a Property must appear inthe componentType of an implementation

No action is required  

ASSEMBLY-32 "SCA schema fixes requested for sca-core.xsd (based on OSOA site versions that may be copied to OASIS site)" 39

Permit intents and PolicySets on <interface/> elements

The policy model needs to be changed so that interface can have intents/policySets attached.

ASSEMBLY-60

Description elements in SCDL

Support documentation element in the model and processors

40

Autowire at the domain level

Tuscany needs to decide if/how it will support the domain-level autowiring

ASSEMBLY-53

No schema or extension model definitions for contributions

42

Autowire value for the logical domain composite

I think Tuscany is OK here as the autowire=false for the domain composite  

ASSEMBLY-5

component type allows to specify wire targets on references

43

for implentations.*'s fix attributes that should show qnames as values

  Push teh getTargets() method from Reference to ComponentReference

ASSEMBLY-9257

Unresolved bindings on references

Add the support for "componentName/serviceName/bindingName" as the wire target Assembly Specification should not state what marks a Javainterface as Local

ASSEMBLY-71 Implementation.composite pseudo-schema incorrect 67

Component Type file name is too restrictive

ASSEMBLY-14

Conflicting Specification of Values for Many-Valued StringProperties

68

ComponentType Properties should not have a source

  Adjust the property value processing to conform to the new syntax

ASSEMBLY-22

WSDL extension should not be required for conversations

60

Description elements in SCDL

Support documentation element in the model and processors Make sure conversational intent is supported at interface and service

ASSEMBLY-1853

No schema or extension model definitions for contributions XSD definitions of Component Service and Component Referencehave unintended features

ASSEMBLY-6392

Specification wording unclear on how local and remoteable interfaces are specified

Assembly Specification should not state what marks a Javainterface as Local

  Remotable is IDL specific

ASSEMBLY-65 Constraining Type talks about non-optional references but does not define what they are 71

Implementation.composite pseudo-schema incorrect

ASSEMBLY-7722

WSDL extension should not be required for conversations

Make sure conversational intent is supported at interface and service

ASSEMBLY-63

Specification wording unclear on how local and remoteable interfaces are specified

Remotable is IDL specific

How to map WSDL 1.1. portType to WSDL 2.0 interface and vice versa?

Remove the wsdl2.0 specfics from sca namespace. Potentially add interface.wsdl2 under tuscany ns

ASSEMBLY-69 Language neutrality edits 65

Constraining Type talks about non-optional references but does not define what they are

ASSEMBLY-4577

How to map WSDL 1.1. portType to WSDL 2.0 interface and vice versa?

Remove the wsdl2.0 specfics from sca namespace. Potentially add interface.wsdl2 under tuscany ns

ASSEMBLY-69

Language neutrality edits some smaller things we need to fix in the assembly specification

ASSEMBLY-5645

some smaller things we need to fix in the assembly specification

ASSEMBLY-56

Need to clarify definition of Bidirectional Interfaces

Make sure Tuscany is consistent with the specified behavior

ASSEMBLY-41

Conflicting domain-level <wire> deployments

Tuscany needs to implement the proposal

ASSEMBLY-79

Identifying wire format and operation selection

add "wireFormat" and "operationSelector" for bindings

ASSEMBLY-62

What is the default value for many and mustSupply on Properties?

remove "mustSupply" from <component>

ASSEMBLY-26

SCA Composite Visibility

This seems to be a clarification by the spec

ASSEMBLY-51

Composite Completeness

Tuscany needs to add more validations to ensure the completeness of the composite for implementaiton.composite

ASSEMBLY-36

Compatability of component type side files

Each implementation type has to decide how to support the componentType file

ASSEMBLY-44

Allow multiple definitions.xml files

Tuscany should allow META-INF/definitions.xml from SCA contributions. These definitions become visible to the SCA domain

ASSEMBLY-89

Need for a Callback annotation for WSDL interface files

Tuscany needs to handle sca:callback extensibility elements in WSDL

ASSEMBLY-16

Component URI is not well described

Tuscany needs to support the structural URI based on this proposal

ASSEMBLY-8

SCDL artifact resolution underspecified

Adjust the artifact resolution based on the proposal in this JIRA

ASSEMBLY-17

Need to define Namespace handling for included Composites

Tuscany needs to adjust how the composite include is aggregated based on the proposal in this JIRA to the SCA domain

ASSEMBLY-30

Incorrect description of <Operation/> child elements inAssembly

I see this conflicts with  http://www.osoa.org/jira/browse/POLICY-58

ASSEMBLY-33

Long-Running Request-Response Operations

Tuscany needs to support the proposal

ASSEMBLY-96

Add a Section documenting naming conventions to the start ofthe SCA Assembly Specification

No action is required /browse/POLICY-58

ASSEMBLY-74

Corrections to the contributions schema

33

Long-Running Request-Response Operations

Tuscany needs to support the proposal See ASSEMLY-28

ASSEMBLY-81 Duplicated atributes in sca-binding-sca.xsd and sca-implementation-composite.xsd 72

Do we need appendix A (pseudo-schema)?

No action is required

ASSEMBLY-74

Corrections to the contributions schema

See ASSEMLY-28

ASSEMBLY-75

"Section on ""Wire"" in Appendix is Incorrect"

Tuscany already has the correct model, model, No action is required

ASSEMBLY-81

Duplicated atributes in sca-binding-sca.xsd and sca-implementation-composite.xsd

No action is required

ASSEMBLY-89

Need for a Callback annotation for WSDL interface files

Tuscany needs to handle sca:callback extensibility elements in WSDL

ASSEMBLY-72 Do we need appendix A (pseudo-schema)? 96

Add a Section documenting naming conventions to the start ofthe SCA Assembly Specification

No action is required