This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Name and Address Priority"
Jump to navigation
Jump to search
(New page: {{MnM Open Hot Topic}} * I have been told that uers have a requirement to capture the priority of different telecom addresses. * I have been told that uers have a requirement to capture...) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | {{MnM | + | {{MnM Closed Hot Topic}} |
* I have been told that uers have a requirement to capture the priority of different telecom addresses. | * I have been told that uers have a requirement to capture the priority of different telecom addresses. | ||
* I have been told that uers have a requirement to capture the priority of different postal addresses. | * I have been told that uers have a requirement to capture the priority of different postal addresses. | ||
* How can I support this? | * How can I support this? | ||
| + | |||
| + | = Resolution = | ||
| + | January 2010 WGM, Sunday Q3 | ||
| + | |||
| + | Datatypes R2 addresses this by defining AD as a COLL. COLL can be constrained to LIST. Where priority is relevant, the LIST collection type should be used, with addresses appearing earlier in the list having priority over those appearing later. | ||
Latest revision as of 01:39, 18 January 2010
This page documents a Closed, fully actioned MnM Hot Topic, i.e. a methodology issue requiring a resolution from Modeling and Methodology.
- I have been told that uers have a requirement to capture the priority of different telecom addresses.
- I have been told that uers have a requirement to capture the priority of different postal addresses.
- How can I support this?
Resolution
January 2010 WGM, Sunday Q3
Datatypes R2 addresses this by defining AD as a COLL. COLL can be constrained to LIST. Where priority is relevant, the LIST collection type should be used, with addresses appearing earlier in the list having priority over those appearing later.
