[Dots] draft-andreasen-dots-info-data-model-01 feedback

["Roman D. Danyliw" <[e-mail]>]

Hello Flemming and Tiru!

(chair hat off)
In reading through draft-andreasen-dots-info-data-model-01, I had the following comments/questions:

(1) The title suggests that the goal is for an information _and_ data model to be documented.  I didn't see much distinction made between the two in the text.  Is the thinking to cover both?

(2) I really like the enumeration of information elements in Section 3.4 and think this will be helpful for the authors of the solutions drafts.  I struggled with the Section 3.2 a bit and may not fully understand what you had in mind.  My thinking for an information model document would be enumerating and describing information elements; and where appropriate, the interrelationship between them.  The current text seems to go one step further with protocol semantics and abstract message formats.  I would have considered these out of scope for an information model.

(3) In Section 3.1, the parameters categorized as mandatory, optional and extensions.  Is the text implying that these are three mutually exclusive categories?  For example, an extension, when used, cannot have mandatory fields?

(4) Section 3.1 - 3.3 discuss message parameters.  Section 3.4 enumerates information elements.  The link between parameters and information elements is never explicitly stated.

Roman