[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (EMERGENCY-48) Data Dictionary - Normative Content?
Darrell O'Donnell created EMERGENCY-48: ------------------------------------------ Summary: Data Dictionary - Normative Content? Key: EMERGENCY-48 URL: https://issues.oasis-open.org/browse/EMERGENCY-48 Project: OASIS Emergency Management TC Issue Type: Bug Environment: Normative Reporter: Darrell O'Donnell TAB-1219 "4 Data Dictionary is only a reference to a generated PDF file in Appendix A. The document in Appendix A is very difficult to read and the annotations don't follow the usage of RFC 2119, as declared in 1.1 Terminology. For example (this isn't exhaustive): Outdated reference: Element Have - ""Language code that is used throughout this document. Code MUST comply with RFC3066."" Element Have / reportingPeriod - ""...the duration may change..."" Is that ""may"" normative? Element FacilityType / geolocation *** The single geometry that represents the Facility location. A WGS84 SRS element is mandatory and alternate SRS geometry elements can be provided. All geometry elements should be reflecting the same physical location. *** Does ""mandatory"" = ""must"" under RFC2119? Why depart from RFC2119? Element GeoLocationType / wg84Location - more ""mandatory"" language and lowercase ""can."" Element ServiceType / bedCapacity *** An indication of the bed capacity that the facility makes available for the community to know. It reflects fully staffed and equipped beds. The intention here is to provide an external view of where beds may be available in a health network. The intent is not for HAVE to become a hospital administration tool. *** Non-normative? Yes? I stopped here. There are another fourty (40) pages of such issues. " Emergency Data Exchange Language (EDXL) Hospital AVailability Exchange (HAVE) Version 2.0 CSPRD01 -- This message was sent by Atlassian JIRA (v6.2.2#6258)