1. #N12 Additional variable types (including non-scalar) [e.g. #S2 Interoperability; identifier comes from “Version 1.1 Candidate Items” spreasheet on TC Documents page] SDD 1.1 General Direction Proposal XXX = [Proposal | Initial Discussion | General Direction Proposal]

2. Current Situation Extend the set of variable types: –Available variable types in V1.0 shall be extended with more types, including non-scalar types (non such available in v1.0) –Currently following types are available IntegerParameterType (extends BaseParameterType) StringParameterType (extends BaseParameterType) BooleanParameterType (extends BaseParameterType) URIParameterType (extends BaseParameterType) ResourcePropertyType DerivedVariableType

3. Proposal The idea is additionally existing types to introduce two new types –ComplexParameterType is a new type –ArrayParameterType is subtype BaseParameterType Additionally a hierarchy of new elements called data-types is introduced

4. Scenario(s)/Use Case(s) Let’s recall the variables definition: Variables provide a way to associate user inputs, resource property values, fixed strings and values derived from these with input arguments for artifacts and with constraints on resources. It makes sense to define two more variable types –a record of elements of different base types – to structure parameters that belong logically together (user account for example) –an array of the same base type – to declare unknown number of common inputs (file locations for example) With respect to the purpose of variables in SDD I was not able to define a use case where table-structure may be used therefore the proposal does not contain a table

5. Proposed Schema ParametersType

6. Proposed Schema ComplexParameterType

7. Proposed Schema ArrayParameterType

8. Proposed Schema Data Types

9. Examples SequenceParameterType 1. 2. 3. 4. ArrayParameterType 1. 2. 3. $dbDVDLocation 4. $appSrvDVDLocation 5.

10. Proposed Schema Change 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11.

11. Proposed Schema Change 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15.

12. Proposed Schema Change 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16.

13. Proposed Schema Change 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24.