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: RE: [ebxml-bp] TimeToPerform tag in ebxmlbp-2.0.4-Example-os-PIP7C7For2.04-en.xml


[informational example. needs resolution of how and where corrections to informational artifacts are to be made]

 

TimeToPerform tag in ebxmlbp-2.0.4-Example-os-PIP7C7For2.04-en.xml

In ebxmlbp-2.0.4-Example-os-PIP7C7For2.04-en.xml, the TimeToPerform tag has neither attributes nor a variable
What is it useful for then?

1.      For expressing that a TimeToPerform should be specified when using a ebBP spec. for two particular partners?
Then why not using type="configuration"?

2.      For expressing that a TimeToPerform should be computed at runtime?
Then why not using type="runtime"?

 

The example PIP7C7For2.04 was produced by running a 1.1 RosettaNet PIP BP example through an XSLT script to convert versions.

 

The example from RosettaNet was missing time to perform information, and the script generated an empty element.

 

So perhaps we need a script fix to handle this situation so the output is misleading.

 

On the other hand, it is a good idea to have time to perform information in a robust ebBP specification.

 

But your observation that the empty value is not useful is definitely correct!

 

 

 



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