Overall

• Correct RFC 2119 words (usage and intention) throughout the entire document
  • Inder & Freek
• Need to worry about references to the base, topology work, and nm-wg.
• May need a motivation/related work section
• Needs Abstract/Conclusion/Acknowledgements sections

Section 1 (Introduction)

• Checked to be sure this sums up the document correctly
• Additional references to related work may be required
• Add Abstract/Conclusion/Ack sections

Writer: Jason Editors: Martin, Jeff, Inder, Roman

Section 2 (MetadataKey)

• Note that many of the XML/Description sections in this part will either derive from the nmc-base (e.g. no changes) or will require a caveat. Each section must be checked:
  • Is the XML correct?
  • Is the description for the XML correct (e.g. required elements/atributes)
  • Add an extra row to each table to signify multiple elements
  • Anything missing?
• Descriptions of why this message was designed/important are necessary too.

Section 3 (SetupData)

• Note that many of the XML/Description sections in this part will either derive from the nmc-base (e.g. no changes) or will require a caveat. Each section must be checked:
  • Is the XML correct?
  • Is the description for the XML correct (e.g. required elements/atributes)
  • Add an extra row to each table to signify multiple elements
  • Anything missing?
• Descriptions of why this message was designed/important are necessary too.

Section 4 (DataInfo)

• Note: used (only?) in pSPS - Jason will describe.
• Note that many of the XML/Description sections in this part will either derive from the nmc-base (e.g. no changes) or will require a caveat. Each section must be checked:
  • Is the XML correct?
  • Is the description for the XML correct (e.g. required elements/atributes)
  • Add an extra row to each table to signify multiple elements
  • Anything missing?
• Descriptions of why this message was designed/important are necessary too.

Section 5 (MeasurementArchiveStore)

• Note: used mostly in MDM - Piotr/Sławomir will describe.
• Note that many of the XML/Description sections in this part will either derive from the nmc-base (e.g. no changes) or will require a caveat. Each section must be checked:
  • Is the XML correct?
  • Is the description for the XML correct (e.g. required elements/atributes)
  • Add an extra row to each table to signify multiple elements
  • Anything missing?
• Descriptions of why this message was designed/important are necessary too.

Writers: Piotr, Sławomir Editors: Jason, Roman, Jeff

Section 6 (Result Codes)

• I would claim we don't need this section if it is covered in nmc-base, especially if we choose the HTTP like codes.