Date
May 26, 2016
Attendees
Goals
- Spec revision and decisions regarding issues
- What was discussed:
- Group decided that JSON format would be the default (but not mandatory), so the data dictionary (data fields) would be used to determine conformance with the spec, with guidance given for minimum security and privacy
- Conformace can be achieved with the essential field descriptions being met
- If JSON is used, conformance would be achieved by using the JSON fields as defined in the spec
- XACML or other formats could be considered in future but for now, we will focus on the JSON format, data dictionary and guidelines.
- Group decided that JSON format would be the default (but not mandatory), so the data dictionary (data fields) would be used to determine conformance with the spec, with guidance given for minimum security and privacy
Discussion Items
| Time | Item | Who | Notes |
|---|---|---|---|
Action Items
- John Wunderlich work up a couple of table examples for the data dictionary and send to group
- Mark Lizar (Unlicensed), Former user (Deleted), iainh1 NA (Unlicensed) will take table examples and comment