david.meredith@stfc.ac.uk [mailto:david.meredith@stfc.ac.uk] said:
I would be in favour of adding new 2.1 cloud entities provided:
* 2.1 only adds new (cloud) implementations that are derived from the 2.0 abstract entities. * There are no changes to the 2.0 entities, especially no changes to the core abstract entities.
Can I clarify exactly what you're saying: you want no completely new free- standing objects (analogous to e.g. Benchmark or StorageServiceCapacity)? And you don't want even optional attributes added to the abstract classes? Both of those would be OK in LDAP in the sense that if a server doesn't publish new objects/attributes it makes no difference whether the schema contains them or not.
What I'd like to try and avoid, if possible, is making changes to the 2.0 core abstract entities because this would require changes to the published 2.0 XSD - i.e. new attributes would need to be added to the base XSD. Conversely, only adding new attributes to new (cloud) entity sub-types would not require change to the base XSD (since we're just extending). Isn't this the whole point for inheritance and sub-type specialisation? -- Scanned by iCritical.