1. #N14 Pattern Value (aka Substring attribute) SDD 1.1 Initial Discussion XXX = [Proposal | Initial Discussion | General Direction Proposal]

2. Current Situation Values for multiple elements, e.g. PropertyConstraint, are of type VariableExpressionType –Spec defines this as: A literal string, e.g. “foo” –OR A variable reference, e.g. $(bar) –Schema defines this as a String w/a restriction Not sure the restriction works as needed There is no way to describe an expression, e.g. substring like “Oracle*” nor the syntax being used in forming the expression.

3. Proposal (original) Add an attribute that states what “format” the value of the element is: –Literal (default) –Variable Reference –Expression Declare it to be defined as an XML pattern facet –A regular expression using "|" and "^" may be specified, as in XPATH expressions. In addition, the occurrence of a "*" in the string content will be interpreted as a wildcard for matching. The escape character is "\". Examples of valid patterns are: red | blue | green ^(red) web* | http* Examples – – *Tomcat* Suggested to look at Java’s regular expression suppport

4. Proposal (new) Both xpath and java’s regular expression support if more complex than what is needed. Thus, to keep it simple –Add an attribute that states what “format” the value of the element is: String (default) Literal –Case sensitive string Variable Reference –$(var) - reference Wildcard –* - wildcard –Prefer “*” over Java’s “.” Negation –Not required for we have the “test value” attribute

5. Proposed Schema Show the exact and complete proposed changed, added or deleted schema. Use this slide for full proposals. It is optional for general direction proposals and would not be expected to be complete.

6. Proposed Specification Change Add attribute to Elements of type Variable Expression – –Allows for other types, e.g. pattern syntax, to be supported Remove current restriction on VariableExpression, i.e. just a String Use this slide for full proposals. It is optional for general direction proposals and would not be expected to be complete.

7. Examples Literal – – Apache Tomcat VariableExpression – – sp:CIM_ConnectedTo.Protocol – $(prototcolType) – –Literal would have been “JDBC” XPath Pattern – – Oracle* –Literal would have been “Oracle 9iAS”