KDM 1.4 RTF Avatar
  1. OMG Issue

KDM14 — Standardize naming of InventoryItem children

  • Key: KDM14-60
  • Legacy Issue Number: 14171
  • Status: closed  
  • Source: Benchmark Consulting ( Alain Picard)
  • Summary:

    Currently the KDM defines 6 classes that are derived from InventoryItem and each of those is documented to represent files of some sort, but the naming is inconsistent. 3 of them have the File suffix and the other 3 don’t, leaving the user to question the categorization difference, which doesn’t seem to really exist when reading the documentation.

  • Reported: KDM 1.2 — Fri, 31 Jul 2009 04:00 GMT
  • Disposition: Resolved — KDM 1.4
  • Disposition Summary:

    Rationalization of InventoryItem

    Proposed subclasses of InventoryItem:
    InventoryItem
    .. SourceFile
    .. Model (new)
    .. LinkableFile (former BinaryFile)
    ......ObjectFile
    ......LibraryFile
    ..ExecutableFile
    ..ConfigFile (former Configuration)
    ..DataFile (new)
    ..ImageFile (former Image)
    ..Document (new)
    ..AudioFile (new)
    ..WebService (new)

    remove ResourceDescription (can't distinguish from ConfigFile)

    Assume InventoryItem has attribute path:URL (see KDM14-131)
    Rename generic Platform::ResourceType into Platform::PlatformResource because the old name conflicts with the use of resource in the InventoryModel.

    Add attribute format:String to InventoryItem
    format:String Optional description of the format of the InventoryItem
    add semantics: format attribute describes the organization of the InventoryItem. Examples of format for various subclasses of InventoryItem are: "xml", "html", "json", "csv", "text", "ms word", "coff", "java class", "jpeg","mp3","css"

  • Updated: Tue, 12 Jul 2016 14:44 GMT