The local repository of legacy devices must be free to have their own store, independent of the structure of the repository, and this working group's effort should accommodate this. PFDL is a higher level language than the schema, from which schema can be derived. PDP then uses the information gained via PFDL to churn and produce what each PEP needs. John agreed that the working group's focus should be on simple things done quickly. We manage complexity through limiting the scope to QOS initially.
Experience is necessary.
Related to this, someone commented that the framework should address linking to SLA's, but this is different than discussing business models. No, not used to dynamically add object classes to the schema. Time is important in the schema. Once this is done, the needed dynamics are captured. PolicyRules will need pointers to DN's of other objects to which they are linked, since they are distributed throughout the directory, typically.