View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000268 | 10000-003: Address Space | public | 2007-11-28 08:17 | 2010-01-13 18:24 | |
| Reporter | Randy Armstrong | Assigned To | Wolfgang Mahnke | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 1.01 | ||||
| Summary | 0000268: Potential Name Conflict with Optional Nodes | ||||
| Description | Consider an ObjectType "A" with a InstanceDeclaration "B". The TypeDefinition for "B" is "X" and it defines an optional component "Y". When defining "A" the component "Y" could be replaced by another component "Y" with completely different typedefinition/nodeclass/semantics. This would break any client that is programmed against the TypeDefinition "X". The spec needs to state that the BrowseNames of child InstanceDeclarations must be unique across all children of the parent and all children in the parent's fully inheirited TypeDefinition. | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2007-11-28 08:17 | Randy Armstrong | New Issue | |
| 2008-03-11 18:45 | Wolfgang Mahnke | Status | new => resolved |
| 2008-03-11 18:45 | Wolfgang Mahnke | Resolution | open => fixed |
| 2008-03-11 18:45 | Wolfgang Mahnke | Assigned To | => Wolfgang Mahnke |
| 2008-03-11 18:45 | Wolfgang Mahnke | Note Added: 0000621 | |
| 2008-04-25 17:36 |
|
Status | resolved => closed |
| 2008-04-25 17:36 |
|
Note Added: 0000669 | |
| 2010-01-13 18:24 |
|
Fixed in Version | => 1.01 |
