OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-bp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Signals questions from Moberg


Dale asked two questions recently about signals. These will be part of 
an upcoming work item session. See below.

>Fixes on signals are now proposed as follows.
>
>1. All BSI signals are to be extensions from SignalEnvelopeType. 
>
><xsd:complexType name="ReceiptAcknowledgementType">
>	<xsd:complexContent>
>		<xsd:extension base="SignalEnvelopeType">
>			<xsd:attribute name="isPositiveReceipt"
>type="xsd:boolean" fixed="true"/>
>		</xsd:extension>
>	</xsd:complexContent>
></xsd:complexType>
><xsd:complexType name="ReceiptAcknowledgementExceptionType">
>	<xsd:complexContent>
>		<xsd:extension base="SignalEnvelopeType">
>			<xsd:attribute name="isPositiveSignal"
>fixed="false"/>
>		</xsd:extension>
>	</xsd:complexContent>
></xsd:complexType>
><xsd:complexType name="AcceptanceAcknowledgementType">
>	<xsd:complexContent>
>		<xsd:extension base="SignalEnvelopeType"/>
>	</xsd:complexContent>
></xsd:complexType>
><xsd:complexType name="AcceptanceAcknowledgementExceptionType">
>	<xsd:complexContent>
>		<xsd:extension base="SignalEnvelopeType"/>
>	</xsd:complexContent>
></xsd:complexType>
>
>
>2. An element whose type is derived from SignalEnvelopeType has
>attributes that can point to signals
>
><xsd:attribute name="signalDefinitionIDREF" type="xsd:IDREF"/>
><xsd:attribute name="signalDefinition" type="xsd:string"
>use="required"/>
>
>These Signal elements are defined in the BPSS instance in a list of
>Signal (the Signals container 
>is not needed.) These signals are of type Signal type and have a
>required Specification element in their content. Is this all they need?
>Should we permit the actual schema for the signal to be included in the
>content model? Also there is an optional ConditionExpression element in
>the signal.
>I assume this was in there to maintain the parallelism between
>DocumentEnvelope and Document with SignalEnvelope and Signal. Is it
>needed though? I would like someone to suggest a use case for this? Can
>a SignalEnvelopeNotation also be used somehow? If so we should have an
>example of its usage.
>
>
>  
>





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]