• Changes to specification, remaining issues
  • Conisistency of Range specifications, openness of link types
  • Extension to application/xml resource representation formats
• Topics for the future

Apologies: ScottBosworth

Present

BrendaEllis, DominicTulley, PaulMcMahan, DaveJohnson

Minutes

Consumer PM: Does not consume query. In the RQM implementationqueryis not important. Dave: Core specification could allow "extension" so that application/xml could be specified by the domain spec. PM: what about consistency across domains. We would want them to be consistent. DJ will also take this to the core. (Side issue: application/xml issue in the core.) JSON would be a better longer-term approach.

PM agreed and will CLOSE this issue.

BE: concerns raised about products having overlappingfeatures regarding configuration mgmtn, in particular

How can we address issue that a model element should be a textual requirement. Another example might be how to plan a requirement in acordance with some statement of work. How can there be a resource which crosses domains?

Baselines of resources and their traceability across domains.