All changes to be submitted by the Working Group Chair (or designee) after approval by the working group.
The Change Request sample (http://www.dmtf.org/members/zdata/CRTemplateSample.html) contains more detailed information on how to complete the template.
|
DMTF Change Request Number [sysdevCR006655] |
WIP-WSMAN-CR00004.001.htm |
|
CR Owner Name, Email [My Name, my.name@company.com] |
Josh Cohen, joshco@microsoft.com |
|
Errata [Yes/No] |
No |
|
Short Description |
Clarify Selector Matching |
|
Spec, Document or Model(s) Being Changed [Device Model] |
wsman-baseline-00 |
|
Spec, Document or Model Version Incorporating the Change [V2.9 Final] |
wsman-interop-00 |
|
Filename(s) Incorporating the Change [Device_USB.mof] |
n/a |
|
Date Originated [mm/dd/yyyy] |
12/06/05 |
|
Date of Last Revision of the Change Request [mm/dd/yyyy] |
12/21/05 |
|
Dependencies [smwgCR00567,sysdevCR00555] |
N/A |
Terminology
The terminology used in this CR should conform to the "Rules for the structure and drafting of International Standards", 5th Edition, 2005 available at:
Particular attention shall be paid to Annex H which lays out guidelines for the expression of provisions.
Background/Rationale (Explanation of the background and reason(s) for the requested change, and supporting documentation):
Currently the specification makes statements which allow a service to ignore some of the passed selectors if they are considered to be superfluous. This creates a condition where the service could erroneously return an instance based on some of the selectors rather than returning an error indicating that the resource specified by the full set of selectors does not exist.
Requested Change (Change information such as details before/after the change, readable/indented MOF, and/or references to "Uploaded" MOF and other documents if the changes are too lengthy to include inline):
Section(s): 2.8 Text (p21 top)
Modify the text below removing the text formatted as strikethrough:
If
more than one Selector value is required, the entire set of Selectors is
interpreted by the service in order to reference the targeted object. The
service is free to examine as many Selectors as required and ignore those which
are redundant once the instance has been identified.
Sections(s): 2.8 R2.8-3
Add underlined text and remove the text formatted as strikethrough.
The service MUST examine all
Selectors in a SelectorSet to identify a target
resource.
The service SHOULD examine whatever
Selectors are required to reference
the target, and MAY ignore any
additional Selectors once the target has
been identified. In this sense, the set of Selectors
is logically ANDed and
the service has the option to ignore
any additional redundant Selectors. If
the set of Selectors is insufficient to
reference a resource or contain invalid
names or values for the targeted
resource, then a wsman:InvalidSelectors
fault SHOULD be returned to the client
with the following detail codes:
Change History (Mandatory after submission to the TC, May be used by the WGs):
|
Version |
Date |
Short description of changes |
|
0 |
12/06/05 |
Initial CR |
|
1 |
12/21/05 |
Update from discussion at f2f |
Note that this document is labeled as "DMTF Confidential". It is intended only for DMTF member companies and alliance partners. This Change Request may be withdrawn or modified by subsequent Change Requests.
All submissions MUST comply with the DMTF Patent and Technology policy (http://www.dmtf.org/about/policies/patent-10-18-01.pdf)
Template Sample Version 2.0.0c.