...
| Item | Title | Time | |||
|---|---|---|---|---|---|
| 1 | Welcome | 1000 | |||
| 2Introduction | to the topics and way of workingDiscussion on Understanding and recording mappings | 1005 | |||
| 3 | Discussion on Differentiating the traces | 1015 | 4 | Discussion on Recording details metadata required by the specification | 11151100 |
| 54 | Any other business | 11451115 | |||
| 65 | Close | 1200 |
Comments received for Differentiating the traces Understanding and recording mappings
- How many traces are sufficient/enough?
- would it be helpful to give advice on how many traces are "ok"? Maybe something like "up to 5 traces" or so?
- if there are too much traces needed maybe think about a change request?
- Multiple traces: Conceptual vs. Logical Model - which to prefer?
...
- is it possible to be aware of potential AIRM CRs outside the AIRM community?
- maybe somebody just wants to build a service (e.g. a METAR service) but can't find an applicable trace. What does that person do? Is it really necessary to register at the AIRM community, review all CRs and decide if there is already a CR matching the issue?
- Note: maybe add the need to join the AIRM community to the handbook to give better guidance on how to find the list of AIRM CRs. Promotes the avoidance of duplicate CRs.
- Items for face-to-face