SourceForge : Post

Project: Editor Discussion > REC: WS-Agreement spec > Business Value Table > List of Posts

Forum Topic - Business Value Table: (2 Items)

View: as

02/17/2005 6:13 PM

post4521

Business Value Table

It is often convenient to define business value as a simple table of variable values and the corresponding business 
value.

Proposed change to the schema:

    <xs:complexType name="BusinessValueTableType">
	<xs:sequence>
          <xs:element name="Entry" type="wsag:BusinessValueTableEntryType"
                      maxOccurs="unbounded"></xs:element>
	</xs:sequence>
      <xs:attribute name="Variable" type="xs:NCType"/>
    </xs:complexType>

    <xs:complexType name="BusinessValueTableEntryType">
		<xs:sequence>
          <xs:element name="VariableValue" type="xs:anyType"></xs:element>
          <xs:element name="BusinessValue" type="xs:anyType"></xs:element>
		</xs:sequence>
	</xs:complexType>

and for the BusinessValueListType:

	<xs:complexType name="BusinessValueListType">
		<xs:sequence>
			<xs:element name="Importance" type="xs:integer" minOccurs="0"/>
			<xs:element name="Penalty" type="wsag:CompensationType" minOccurs="0"/>
			<xs:element name="Reward" type="wsag:CompensationType" minOccurs="0"/>
 			<xs:element name="Preference" type="wsag:PreferenceType" minOccurs="0"/>
 			<xs:element name="BusinessValueTable" type="wsag:BusinessValueTableType" minOccurs="0"/>
			<xs:element name="CustomBusinessValue" type="xs:anyType" minOccurs="0" maxOccurs="unbounded"/>
		</xs:sequence>
	</xs:complexType>

Jim Pruyne

04/20/2005 12:07 PM

post4522

group response

The concept
  is a good one, but we can already capture this with various of
  guarantee terms.  We'd rather wait until we have more experience
  rather than introduce this now since it is a conveince thing rather
  than a required thing.

Return