Presentation on theme: "IODEF datamodel update. Stability of the datamodel Datamodel stable since Feb 2003 interim meeting Draft stable since publication March 31st."— Presentation transcript:
IODEF datamodel update
Stability of the datamodel Datamodel stable since Feb 2003 interim meeting Draft stable since publication March 31st
Issues IANA considerations –Apply to the enumerated lists in the datamodel. Options: “Designated experts are appointed by the relevant Area Director of the IESG.” IETF consensus (IDWG did this) –Preference for latter
Issues (2) Enumerated lists need review (implementation experiences) Moving to XML Schema (Yuri) Internationalization and language issues (under active discussion on list)
Issues (3): mandatory fields What can be mandatory is context-dependant (initial incident reports, incident updates) Mandatory now are IncidentID, ReportTime, Assessment (!), Contact (!) Problems that occur: –Duplicate data when sending incident-updates? (with mandatory) –Have the ability to send meaningless IODEF-Document messages? (with (almost) no mandatory)
Issues (3): mandatory fields Ways to enforce mandatory fields and ensure no meaningless documents are sent: –Using XML and its validation mechanism –Move it to the IODEF-Document processor and do it in the backend –?
Roadmap New draft out before mid September Add XML-Schema next to DTD for transitioning to Schema.