I should also say that we have use cases that require <Resource> multiplicity to be 0-n. (Think of an n-tier system resource description where different tiers might require different resource descriptions with different resource counts. It's a single application, albeit composed of n parts.) Karl Czajkowski wrote:
On Apr 20, Andreas Savva loaded a tape reading:
Afaik Resource should be 0-n.... Thanks for pointing it out. I'll confirm it and change the spec.
When were heterogeneous resource mixes discussed and are there any notes of that discussion?
I think it came up at GGF-13 and I thought it was 0-n too at the time. I got confused by the 0-1 section title in the draft...
I thought we said the general model was a sequence of Resource elements each with its own localally scoped attributes and the resource count was just a shorthand to avoid writing redundant sequences for homogeneous scenarios.
If it remains 0-n, I wonder if we should have an enclosing Resources element or something like that to hold the "total" metrics that summarize allocation across all resources?
karl
-- Andreas Savva Fujitsu Laboratories Ltd