Ok, here's the model version. I extracted some of this information from the architecture mostly. I didnt put as much energy on this as i did on the protocol version. But it is a starting point.
cheers, jamal
1) The data model MUST be able to describe the target objects a) with formal constraints for validation purpose b) basic read-write access permissions c) class object capabilities and capacities d) event object definitions with publish-subscribe semantics 2) The model MUST be object oriented. This allows it to extensible in the form of templating and sub-classing. 3) The data model MUST be able to express semantics of instances. This is a side product of being object oriented. 4) The data model MUST be able to manage variation a) Presence compliance of defined objects should be possible to express. (eg optional vs mandatory) b) Default values MUST be possible to specify c) Hierarchies MUST be possible to specify 5) Data Model MUST be able to handle Object Life cycle management. Typically this means: a) Versioning support b) being able to handle both backward and forward compatibility
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
