80 likes | 244 Views
Version Redux. SDD 1.1 General Direction Proposal. Current Situation. Version strings are not normalized Variation from OS to OS Can be variation within an OS (eg. Windows) Multiple version strings Variation from application to application
E N D
Version Redux SDD 1.1 General Direction Proposal
Current Situation • Version strings are not normalized • Variation from OS to OS • Can be variation within an OS (eg. Windows) • Multiple version strings • Variation from application to application • How does an SDD producer specify version information in a form an SDD consumer can use?
Scenario(s)/Use Case(s) • Windows XP example • For a Windows XP requirement which version string does an SDD producer specify in the SDD? • 5.1.2600 • Version 5.1 (Build 2600.xpsp_sp2_rtm.040803-2158 : Service Pack 2 • Windows XP • All are valid version strings for Windows XP
Proposal • Communicate version in the profile • Options • Create a Version complex type • Break the version strings into elements of particular “type” • Specify how the elements should be assembled for evaluation purposes • Make resource definitions in the profile more structured than the current enums and add version to the structure
Proposal • Example: Create complex types for each OS currently listed in the enum • Add 0..n version elements to the new complex types • Primary version • Secondary version • Tertiary version • Etc. • Replace the current CIM_OperatingSystem complex type?
Proposed Schema • TBD • Pending the decided approach
Proposed Specification Change • TBD • Pending the decided approach