1. #N14 Pattern Value (aka Substring attribute) SDD 1.1 Proposal

2. Current Situation descriptorLanguageBundle is an optional attribute for both the Package Descriptor and the Deployment Descriptor –Thus, requires text in the Spec as: The descriptorLanguageBundle attribute can be specified in both the PackageDescriptor and the DeploymentDescriptor, although the latter is not required. If it is included in both, the values entered in the descriptorLanguageBundle attribute MUST match exactly. The schema causes this issue which makes it unnecessarily hard for both SDD creation tools and SDD runtime tools

3. Current Schema DescriptorInfoGroup – – DeploymentDescriptor – PackageDescriptor –

4. Propsed Schema DescriptorInfoGroup – – DeploymentDescriptor – PackageDescriptor –

5. Proposal (new) Both xpath and java’s regular expression support if more complex than what is needed. Thus, to keep it simple –Add an attribute that states what “format” the value of the element is: String (default) Literal –Case sensitive string Variable Reference –$(var) - reference Wildcard –* - wildcard –Prefer “*” over Java’s “.” Negation –Not required for we have the “test value” attribute

6. Proposed Schema Change The elements identified (circled in red) on the next few charts will be changed from type="sdd-dd:VariableExpressionType“ to type="sdd- dd:ElementValueType” 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. –Note: Allows for other types, e.g. pattern syntax, to be supported

7. Proposed Schema Change The following could NOT be changed for they are attributes Thus, they are changed to an xsd:string. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23.

8. Proposed Elements to Change Topology

9. Proposed Elements to Change Resource Constraints - (All places it applies)

11. Proposed Elements to Change Resulting Resource

12. Proposed Elements to Change Resulting Change

13. Proposed Elements to Change Artifacts Note: Applies to all artifact types, e.g. UninstallArtifact

14. Proposed Elements to Change Requisites

15. Proposed Specification Change For the attributes on slide 5, the value should be handled as a literal string. The only exception is that if the value starts with “$(“ and ends with “)”, then the value should be treated as a variable reference. Use this slide for full proposals. It is optional for general direction proposals and would not be expected to be complete.

16. Examples Literal – – Apache Tomcat Variable Reference – – sp:CIM_ConnectedTo.Protocol – $(prototcolType) – –Literal would have been “JDBC” Wildcard – – Oracle* –Literal would have been “Oracle 9iAS”