Ticket #711 (closed Task: fixed)

Opened 22 months ago

Last modified 12 months ago

review whether any CVs should _not_ be extensible

Reported by: allyn Owned by: allyn
Priority: blocker Milestone: CIM v1.5
Component: WP2 - CIM etc Version:
Keywords: Cc:
Requirement:

Description

from a recent email:

<snip> All,

Is this extensibility a questionnairism or a CIMism b/c it seems like in the CIM all vocabs should be extensible over time and that would trump any issues in the questionnaire.

Sylvia

On Apr 20, 2010, at 7:18 AM, Gerard Devine wrote:

Hi,

I've just been looking at the CIM and, as you say Rupert some of the machine specific vocab lists are extensible whilst others are not. Allyn, was there a particular reason for the difference? If not, I don't see any reason why processorType and interconnectType shouldn't be open.

Regards, Gerry

On 18/04/2010 23:23, rupert wrote:

Hi Sylvia,

I am scanning the latest file you sent looking for differences etc. One thing I noticed is that some values have quotes around them an others don't. Since they are all strings, perhaps we want something consistent?

<machineOperatingSystem value="Unicos"/> <machineVendor value="Cray Inc"/> <machineInterconnect>Cray Interconnect</machineInterconnect>

In xml, attributes always have quotes and elements don't, irrespective of their content.

As for the reason for the different syntax, it is to do with whether the set of values for a particular concept has been classed as an extensible, or a closed, list in the CIM UML.

The concepts "machineOperatingSystem" and "machineVendor" have an extensible controlled vocabulary. For example, it is possible to add new vocabulary by doing the following ...

<machineOperatingSystem value="Other">MyNewOS</machineOperatingSystem>

In contrast, "machineInterconnect" has a closed list and it is currently only possible to provide values that are defined in the CIM schema's enumerated list (if one wants valid CIM xml).

Now, you might ask why machineInterconnect is a closed list. Well that would be a good question :-).

Regards

-- Rupert

</snip>

Change History

comment:1 follow-up: ↓ 2 Changed 12 months ago by allyn

  • Status changed from new to closed
  • Resolution set to fixed

I am satisfied that there are no CVs that ought to be extensible; they are all "open."

comment:2 in reply to: ↑ 1 Changed 12 months ago by allyn

Replying to allyn:

I am satisfied that there are no CVs that ought to be extensible; they are all "open."

Sorry, make that "I am satisfied that there are not CVs that ought _not_ to be extensible."

Note: See TracTickets for help on using tickets.