[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Updated RE: [ebxml-msg] complex type for PModeBusinessInfoType for discussion
Including the complexType definition for
PayloadProfileType. This type definitely needs some discussion concerning
cardinality. Role is included here instead of with Party related
identification. This is for discussion and reflects Role being a basic
category of ebBP or BPSS. Types for EII are tentative. I think we might need some
attributes. xsd:string is probably not restrictive enough. <xsd:complexType
name="PModeBusinessInfoType">
<xsd:sequence>
<xsd:element name="Service" type="xsd:string"/>
<xsd:element name="Action" type="xsd:string"/>
<xsd:element name="Role" type="xsd:string"/>
<xsd:element name="PayloadProfile"
type="tns:PayloadProfileType" maxOccurs="unbounded"/>
<xsd:element name="MPF"/>
<xsd:element name="Properties"/>
</xsd:sequence>
</xsd:complexType> [Added referenced type below. A given
document may include elements from many namespaces. Is it expected that all are
listed, some, just the namespace for the root element, or what?] <xsd:complexType
name="PayloadProfileType"> <xsd:sequence> <xsd:element
minOccurs="0" maxOccurs="unbounded"
name="Namespace"/> <xsd:any
namespace="##other"/> </xsd:sequence> <xsd:attribute
name="name" type="xsd:string"/> <xsd:attribute
name="mimeType" type="xsd:string"/> <xsd:attribute
name="maxSize" type="xsd:string"/> <xsd:attribute
name="MPF" type="xsd:string"/> <xsd:anyAttribute
namespace="##other"/> </xsd:complexType> |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]