Re: [emergency] Groups - EDXL-DE spec discussion materials (EDXL_DE_materials.zip) uploaded

[Michelle Raymond <michellearaymond@gmail.com>]

All,

This message contains the modifications and volunteers mentioned in
today's meeting.

Best regards,

Michelle


Volunteers:
Sukumar - coordinate content for section 1 and section 2.  
    1. send initial material to Michelle
    2. collect modifications and rewrites
    3. send updates to Michelle
Sylvia - coordinate content for Appendix B: XML Schema
    ...
    n. send updates to Michelle
David - update example 1 for Appendix A: XML Examples
    1. send updates to Michelle
Michelle - update example 2 for Appendix B: XML Examples
             - format all content received
             - fix conversion to PDF where formatting and links don't match up.
Elysa - send content for Appendix C: Acknowledgements
All - review, comment, review, comment, continue loop ...

These are the modifications we discussed today (they are also in the
attached file):
1. rename <EDXLDist> to <EDXLDistribution>

2. bold the required elements - messageID, senderID, dateTimeSent,
messageStatus, messageType

3, keyXmlContent should be one container with multiple content - make
the definition clear - may contain multiple xml elements and the
content of those xml elements from within the contentObject xmlContent

4. put <contentKeyword> in MessageElement - ex: responseType

5. <keyword> and <contentKeyword> definitions should end with "inform
message routing and/or processing decisions."

6. remove <responseType> from <messageElement>

7. <contentObject> - i) Art needs to respond on contentObject
reasoning or ii) contentObject has an attribute indicating the content
type or add iii) <contentType> sub-element to <messageElement>. Note:
use of option (iii) will be used at this point.

8. <explicitAddress> is for addresses for recipients that are
specifically called out.  This needs to be clear in the definition.

9. rename <lowestConfidentiality> to <combindedConfidentiality>. In
the definition indicate that this is the  confidentiality of the
combined <messageElement> sub-elements and that generally it is the
most restrictive of the <confidentiality> elements in the contained
<messageElement> element, but that it could be more restrictive than
any of the individual <confidentiality> elements.

10. fix PDF translation for links placement.  It doesn't perform as it
does in a browser.

11. rename all <EDXLDistribution> sub-elements in the form message* to
the form distribution*. Ex: <messageID> becomes <distributionID> and
<messageStatus> becomes <distributionStatus>.
1. rename <EDXLDist> to <EDXLDistribution>

2. bold the required elements - messageID, senderID, dateTimeSent, messageStatus, messageType

3, keyXmlContent should be one container with multiple content - make the definition clear - may contain multiple xml elements and the content of those xml elements from within the contentObject xmlContent

4. put <contentKeyword> in MessageElement - ex: responseType

5. <keyword> and <contentKeyword> definitions should end with "inform message routing and/or processing decisions."

6. remove <responseType> from <messageElement>

7. <contentObject> - i) Art needs to respond on contentObject reasoning or ii) contentObject has an attribute indicating the content type or add iii) <contentType> sub-element to <messageElement>. Note: use of option (iii) will be used at this point.

8. <explicitAddress> is for addresses for recipients that are specifically called out.  This needs to be clear in the definition.

9. rename <lowestConfidentiality> to <combindedConfidentiality>. In the definition indicate that this is the  confidentiality of the combined <messageElement> sub-elements and that generally it is the most restrictive of the <confidentiality> elements in the contained <messageElement> element, but that it could be more restrictive than any of the individual <confidentiality> elements.
				
10. fix PDF translation for links placement.  It doesn't perform as it does in a browser.	

11. rename all <EDXLDistribution> sub-elements in the form message* to the form distribution*. Ex: <messageID> becomes <distributionID> and <messageStatus> becomes <distributionStatus>.