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: Swenson 3/25/2004: [RSD] WI-55 Addl Potential Attributes for LateBound Elements


Dear Colleagues,
I agree with Keith Swenson about the possibility that certain attributes could/should be defined on a TTP element that allows conditionality.

As I mentioned in point 4 in my mail "Late binding summary" (http://www.oasis-open.org/archives/ebxml-bp/200402/msg00000.html) I think we might need a way to say that a certain value in TTP in a BPSS instance is allowed or not allowed to be changed at a later stage. This could also be true for other statements in a BPSS instance, and not only for TTP (se my point 3 in the same mail). 

For example we might need an attribute to say if a TTP-value (or other statment) in a BPSS instance is allowed to be a) changed (or specified/negotiated for the first time) during CPPA negtiation or b) changed (or specified/negotiated for the first time) at BPSS callaboration instansiation time or c) renegotiated and changed during runtime?

I also think that we might need a way to specify during a) BPSS instance specification/definition time or b) CPPA negotiation time - that the TTP-value is
1) not yet specified/defined at all
2) specified as one discrete value
3) specified as a set of discrete values (with possibly one of them as the default value)
4) specified as a range of values (with possibly one value as the default value). This range could possibly be specified with both a min-TTP and a max-TTP, or as an 'open range' with just one of the min-TTP or max-TTP values specified.

Just my 2 cents...

* Lars.Abrell@TeliaSonera.com * +46 (0) 705 619080
* Kilsgatan 4, Box 299, SE-401 24 Gothenburg, Sweden

-----Original Message-----
From: Monica J. Martin [mailto:Monica.Martin@Sun.COM]
Sent: Tuesday, April 06, 2004 9:03 PM
To: Abrell, Lars E. /TSS - Networks and Production /+46-31-7709080,
+46-705-619080
Cc: Keith Swenson; Anders W. Tell
Subject: Re: Swenson 3/25/2004: [RSD] WI-55 Addl Potential Attributes
for LateBound Elements


Lars,
Per our conversation, late Friday, here is a summary of the inputs from 
Keith Swenson on late binding.  Anders and I discussed this Saturday, 
and the capability to put constraints or conditions on the elements 
(indicating whether or not they are changeable, for example).

Any feedback would be greatly appreciated.
Thanks.

> Discussion.OASIS.ebBP.WI55-Late Binding;
> Topic;
> Attachment|http://www.oasis-open.org/archives/ebxml-bp/200403/msg00041.html; 
>
> Point|Conditional Time to Perform Attributes;
>
> mm1@
>
> Keith Swenson has indicated there may be additional characteristics we 
> consider related to time to perform.
>
> Using....."a fixed value that is changed" implies that a particular 
> solution (or elements of the solution) are predetermined and limits 
> the range of responses. I don't think the question is at all about 
> anything being "changed"....Partners should to be able to agree up 
> front on 'time to perform' being conditional......"
>
> Swenson points out:
>
>    * Process specifies possibilities without preference.
>    * Process defines static or fixed TTP.
>    * Partners may agree that the same process has >1 TTP.
>
> This raises the possibility that certain attributes be defined on a 
> TTP element [1] that allows conditionality.
>
> I'd encourage comment on if this and other characteristics should be 
> captured for TTP (which may influence v3.0 as well).
>
> Please think about this comment from Keith and send your ideas to the 
> list. Thank you.
>
> [1] In line with affirmative vote on direction of resolution for 
> WI-55, Late Binding.
>
> @mm1
>





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