Sprint Parking Lot

Dropping the key value pair as an administration

• There is, today, a name value pair. This hints at a broader requirement.
• Requirement for a run time solution for one time extensions which may involve structured information or simply name value pairs
• There is another requirement for an easy way to extend the model and design time. To meet the first requirement it would be possible to have a key value pair to have structured content in the value.

Software and metadata quality objects

In the administrative information discussion, there is currently a software object and its properties and a metadata quality objects and its properties. these could be objects in the model but they don't necessarily exist at this time. The requirement for this administrative information still exists. Someone call Santa and tell him to bring a lot of coal.

Access to metadata

There is a big issue about access to metadata. In removing the 'is published' attribute the question of how at publish action access is managed is raised. XACML? DDI should have means to support this standard. One idea is to replace 'is published' with 'is final' like SDMX (or is dead)

Links to presentation materials

It might be desirable to have an attribute which can be typed to cover cases such as 'links to presentational materials (CSS)' or access control to resource such as XACML. Note this may be related to parking lot issue about key value pairs. 

Document the style of modelling

Addition to the style of the modelling regarding default values. There is a question of whether we should default values in the model and related representations or only in the documentation. The background is the so called heisenbag. The way to deal with default values should be documented. The style of XML schema model should be documented very well.

Controlled Vocabularies

We need to clarify the decision regarding what CVs are included in the specification in-line and those that are merely links to external CVs