Definition Type: ComplexType
Name: AcknowledgeType
Namespace: http://ns.hr-xml.org/2007-04-15
Containing Schema: ApplicationAcknowledgement.xsd
Abstract
Collapse XSD Schema Diagram:
Drilldown into UserArea in schema userarea_xsd Drilldown into PayloadDisposition in schema applicationacknowledgement_xsd Drilldown into PayloadResponseSummary in schema applicationacknowledgement_xsd Drilldown into lang in schema xml_xsdXSD Diagram of AcknowledgeType in schema applicationacknowledgement_xsd (HR-XML - Human Resources XML)
Collapse XSD Schema Code:
<xsd:complexType name="AcknowledgeType">
    <xsd:sequence>
        <xsd:element name="PayloadResponseSummary" type="PayloadResponseSummaryType" />
        <xsd:element name="PayloadDisposition" type="PayloadDispositionType" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation> Should the detail be optional?  Or should this be a choice between the element as it is now and a "no-op" element that indicates total success of the transaction.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element ref="UserArea" minOccurs="0" />
    </xsd:sequence>
    <xsd:attribute ref="xml:lang" />
</xsd:complexType>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
PayloadResponseSummary hr:PayloadResponseSummary (1) (1)
PayloadDisposition hr:PayloadDisposition 0 (1)
UserArea hr:UserArea 0 (1)
Collapse Child Attributes:
Name Type Default Value Use
lang nsA:lang (Optional)
Collapse Derivation Tree:
Collapse References:
hr:ApplicationAcknowledgement