ETSI's Bug Tracker - Part 09: Using XML with TTCN-3
|
|||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0003310 | Part 09: Using XML with TTCN-3 | Technical | public | 06-05-2008 13:26 | 15-07-2008 12:45 |
| Reporter | user363 | ||||
| Assigned To | Gyorgy Rethy | ||||
| Priority | normal | Severity | major | Reproducibility | N/A |
| Status | closed | Resolution | duplicate | ||
| Platform | OS | OS Version | |||
| Product Version | v3.3.1 (published 2008-04) | ||||
| Target Version | v4.1.1 (published 2009-06) | Fixed in Version | |||
| Clause Reference(s) | 5.1 | ||||
| For STF discussion | |||||
| Source (company - Author) | |||||
| Summary | 0003310: Module Names | ||||
| Description | The mapping of XSD files and name spaces
to TTCN-3 modules shall be handled analog to part 8 of the standard
(IDL). I. e. in particular that the XSD file names shall have no
influence on the mapping; the XSD namespaces shall be mapped (after some
necessary name mangling) to TTCN-3 module names. Proposed text: "Every namespace used in an XSD Schema is mapped to a separate TTCN-3 module, containing the entities defined in the particular namespace. (The namespace URIs are mangled to syntactically correct TTCN-3 module names as described in clause 5.2.) This means that XSD import-statements (which allow the use of entities of another namespace) imply the generation of another module for the imported entities; XSD include-statements (which include entities, defined in another namespace, into the same namespace the include-statement appears in) lead to the generation of the included entities in the current module. No maintenance effort shall result from changes of the internal structure of an XSD Schema which does not change its outside appearance (interface)." Reasoning: (A) This approach has already been proven suitable in the IDL-to-TTCN-3 mapping (part 8 of the standard). Handling analog things differently is not intuitive for the user. (B) The XSD file names are part of the internal structure of a Schema; changes within this internal structure should not result in changes of the interface (e. g. TTCN-3 module names) of the generated TTCN-3 code as this would result in maintenance efforts for users of the generated code each time the internal structure of the Schema changes. |
||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 06-05-2008 13:26 | user363 | New Issue | |||
| 06-05-2008 13:26 | user363 | Status | new => assigned | ||
| 06-05-2008 13:26 | user363 | Assigned To | => Gyorgy Rethy | ||
| 06-05-2008 13:26 | user363 | Clause Reference(s) | => 5.1 | ||
| 06-05-2008 13:26 | user363 | Source (company - Author) | => | ||
| 09-05-2008 10:55 | Ina Schieferdecker | Target Version | => Edition 4.1.1 (not yet published) | ||
| 15-07-2008 12:45 | Ina Schieferdecker | Note Added: 0006275 | |||
| 15-07-2008 12:45 | Ina Schieferdecker | Status | assigned => closed | ||
| 15-07-2008 12:45 | Ina Schieferdecker | Resolution | open => duplicate | ||
| 15-07-2008 12:45 | Ina Schieferdecker | Note Deleted: 0006275 | |||
| 15-07-2008 12:45 | Ina Schieferdecker | Note Added: 0006276 | |||
| Notes | |||||
|
|
||||