5. Format Requirements - Continue|
5.2 FINE must support modularity in Incident description to allow aggregation and filtering of data.
The structure will contain several components and some components may be structures themselves. Each component of a structure will have a well defined semantics.
5.3 FINE must provide the possibility for recording the evolution of Incident Report during its whole lifetime. In particular, FINE should contain the record of all communications that happened in course of current Incident.
5.4 FINE must support the application of an access restriction policy to individual components.
5.5 An FINE report must be globally uniquely identifiable.
5.6. The Format for Incident report Exchange itself must be extensible.