ETSI's Bug Tracker - Part 09: Using XML with TTCN-3
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0006746 | Part 09: Using XML with TTCN-3 | Editorial | public | 24-04-2014 12:06 | 13-01-2015 14:28

Reporter | Tomas Urban |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | trivial | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.5.1 (published 2013-04) |
Target Version | v4.6.1 (published 2015-06) | Fixed in Version | v4.6.1 (published 2015-06) |
Clause Reference(s) | 5, 6, 7, 8, C, D
For STF discussion |
Source (company - Author) | STF 475

Summary | 0006746: Inconsistent namespace prefixing in examples

Description

The current specification uses different prefix style in the examples. Sometimes the schema namespace ("http://www.w3.org/2001/XMLSchema" [^]) is the default (unprefixed) namespace, but it can have also xsd or xs prefix. The same is valid for the target namespace which is either unprefixed or ns. There might be other variants too as I didn't check the whole document thoroughly.
In my opinion the naming convension should be the same in the whole document. Suitable combinations would be either no prefix for the schema namespace and ns for the local one or xsd for the schema namespace and no prefix for the local one. This convension should be generalized somewhere (maybe in the section 3).
Different naming might be justified in some examples, but if it is the case, the example should contain namespace prefix definitions as well.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files |

Issue History
Date Modified | Username | Field | Change
24-04-2014 12:06 | Tomas Urban | New Issue |
24-04-2014 12:22 | Tomas Urban | Note Added: 0012053 |
15-06-2014 17:16 | Gyorgy Rethy | Assigned To | => Gyorgy Rethy
15-06-2014 17:16 | Gyorgy Rethy | Status | new => assigned
15-06-2014 18:03 | Gyorgy Rethy | Target Version | => v4.6.1 (published 2015-06)
04-11-2014 14:09 | Gyorgy Rethy | Note Added: 0012402 |
04-11-2014 14:09 | Gyorgy Rethy | Status | assigned => resolved
04-11-2014 14:09 | Gyorgy Rethy | Fixed in Version | => v4.6.1 (published 2015-06)
04-11-2014 14:09 | Gyorgy Rethy | Resolution | open => fixed
13-01-2015 14:28 | Gyorgy Rethy | Note Added: 0012670 |
13-01-2015 14:28 | Gyorgy Rethy | Status | resolved => closed

Notes

(0012053)
Tomas Urban
24-04-2014 12:22

In some cases, there are different prefices for one namespace within one example (e.g. 7.5.3, example 2) which is actually an error.

(0012402)
Gyorgy Rethy
04-11-2014 14:09

Comment is correct, a unified namespace prefix convention to be used in examples: xsd: for the XSD namespave, ns: for the target namespace. This is to be done during final editing of the draft, to allow using the time of the joint working sessions to work on technical issues.

(0012670)
Gyorgy Rethy
13-01-2015 14:28

Implemented in draft V4.6.4