[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Comments on specifications and schema
Hi everyone Today I started to create an ebBP XML instance. The goal is to use more than 2 roles and use one fork and one join. Along the way I came across several questions and comments. Regards Sacha ------------------------------------------------------------- OASIS ebBP 2-0 spec wd-10 23 February 2005 COMMENTS :: from :: Sacha ------------------------- Should the defaultValue attribute of ConditionExpressionType be xsd:boolean instead of xsd:string ? eg ConditionExpression must be TRUE or FALSE -------------------------- BusinessDocument examples in spec. (1084 ff and 2530 ff) us specificationLocation but there is no specificationLocation in the schema. -------------------------- line 676 there are ";" characters in the XML file ------------------------------ BusinessCollaboration element in schema: annotation documentation has: Two or more roles - Two or more roles ------------------------------ RoleType element in schema: name, nameID can be replaced by <attributeGroup ref="name"/> ------------------------------- in schema: ConditionExpressionType: todo: add linebreaks isConcurrent: todo: add linebreaks -------------------------------- performs type: difficult to understand what the attributes mean. ------------------------------- BusinessTransactionActivityType[@businessTransactionRef] could need some more documentation to indicate why we reference the business transaction. ------------------------------- page 14 of specification takes long time to load with xpdf pdf reader ------------------------------- BusinessTransactionHead is difficult to understand. an abstract XML element. an abstract superclass ... if this is not advanced XML Scheme ;) then specific Business Transactions are substitution groups. Once someone understands ... then its is OK. ------------------------------- scheme: has tabs (on my editor a tab is 8 spaces which results in wide document) What is normal to do? keep tabs or replace tabs with fixed spaces? Changing editor setting is one approach. -------------------------------- documentSecurity: all attributes are optional, right? Would default values be set to "none"? eg does commercial transaction overwrite these values? eg if commercial transaction is used, some security options must be used? -------------------------------- DocumentEnvelopeType attribute isPositiveResponse is optional. this means that users can forget to set the isPositiveResponse on a response message. ------------------------------- ReceiptAcknowledgementType@isPositiveReceipt has a xsd:boolean type ReceiptAcknowledgementExceptionType@isPositiveReceipt has no xsd:boolean type AcceptanceAcknowledgementType has no isPositiveReceipt="true" attribute AcceptanceAcknowledgementExceptionType has no isPositiveReceipt="false" attribute GeneralExceptionType has no isPositiveReceipt="false" attribute -------------------------------- http://www.oasis-open.org/committees/ebBP/BPS/2.0/Signals.xsd does not exist. -------------------------------- quality attributeGroup: all attributes are optional! should there be a default value? -------------------------------- Spec. line 2085 FROM ...is to not intended to be TO ...is not intended to be ---------------------------------- RetryCount is a business retry and is used in the following BT's o InformationDistribution o CommercialTransaction o RequestConfirm o RequestResponse o QueryResponse o InformationDistribution o BusinessTransaction (will be deprecated) but not in these BT's: o DataExchange o Notification is this intended? --------------------------------- retryCount is a business retry. -> only used in a RequestingBusinessActivity if there is no default value does that mean there is no retry? if retryCount is set: o Does sending a retry after a ReceiptAcknowledgementException business signal counts as one retry? o Does sending a retry after an AcceptanceAcknowledgementException business signal counts as one retry? Is it right that I cannot send a retry after an ReceiptAcknowledgment and not after an AcceptanceAcknowledgement business signal? A retry proabably works as defined in the RequestingBusinessActivity? Example: _A is party A _B is party B backend_A generates purchase order (po). po goes to BSI_A which uses MSH_A to send ebXML message with id 1. MSH_B receives ebXML message with id 1 and goes through a BSI_B and to a backend_B. Backend_B sends ReceiptAcknowledgement to A side. Backend_B for example checks credit status of party A and has to say NO. So backend_B generates a AcceptanceAcknowledgementException (or based on some implementation dependent action a non-logical-abstract-BSI recognises the situation and generates an AcceptanceAcknowledgementException business signal. question A: I guess this is exactly what for business people is important. If the underlying Business transaction pattern requires to send Acceptance business signals, it is necessary to also send a AcceptanceAcknowledgementException and NOT to skip it and send a negative Response. The BSI_B sends the AcceptanceAcknowledgementException to MSH_B which sends to MSH_A, which sends to BSI_A which sends to backend_A. Backend_A must associate AcceptanceAcknowledgementException (as it had to do with ReceiptAcknowledgement) to po. My question is: How can the backend_A find out WHY po was rejected? Is there a standardized AcceptanceAcknowledgementException reason value defined? If backend_A does not know WHY po was rejected ..... it will have a hard time to figure out how the next retry po should look like... -------------------------------- if a retry after a negative AcceptanceAcknolwegment or negative ReceiptAcknowledgment is not executed or used, does time simply timeout and an exception happens? (guess so ;) -------------------------------- if retry count is equal or larger than 1 and a retry occurs: does a retry (from retryCount) reset: o timeToAcknowledgeReceipt? o timeToAcknowledgeAcceptance? -------------------------------- So there is Notification of Failure AND General Exception Both signals are not modelled in the business collaborations. -------------------------------- Are there standardizd ebBP Business Signals XML Schemas or can these be made up independently (proprietary)? -------------------------------- The example ebBP business signals seem to Spec: 2784: <bpssignal:OriginalMessageIdentifier> does this reference the ebXML Message ID? That would mean that some component (MSH or some non-logical-abstract-BSI) must make this correlation as the backend might not know about the ebXML Message ID. -------------------------------- How does a NotificationOfFailure message look like? There is no such type. Does it use the "Notification" business transaction? -------------------------------- Spec. example on 2521 seems to be old as in 2608 uses toRole attribute of BinaryCollaboration which is no longer there. Role element should be used. Seems example is outdated.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]