[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [ebxml-cppa] Placeholder values in CPA templates
Some thoughts below. Regards, Marty ************************************************************************************* Martin W. Sachs IBM T. J. Watson Research Center P. O. B. 704 Yorktown Hts, NY 10598 914-784-7287; IBM tie line 863-7287 Notes address: Martin W Sachs/Watson/IBM Internet address: mwsachs @ us.ibm.com ************************************************************************************* Dale Moberg <dmoberg@cyclonecommerce.com> on 02/05/2002 01:34:34 PM To: CPPA <ebxml-cppa@lists.oasis-open.org> cc: Subject: [ebxml-cppa] Placeholder values in CPA templates While working on updates to the CPA formation appendix, I realized that I did not recall that we have every made a decision about how to mark placeholder values in a CPA template. MWS: I don't recall a decision. Some placeholder values might have a specific type according to schemas, and in general I doubt that it will work to just omit values (have empty strings or whatever datatype is involved.) MWS: Parsers probably would not like that. We would need a valid value that is understood to be changeable. Eventually, an NDD (Negotiation Descriptor Document) would take care of it but we need something now. If no one can find where we have said something about this, I propose that we add an issue to the database that says how to mark placeholder values. MWS: I agree with adding an issue. Some more specific questions arise for specific places that might be subject to placeholders. For example, in PartyId, can we allow the "type" attribute to have a placeholder value? Or should a CPA template always nail down the expected type (eg, "urn:oasis:names:tc:ebxml-cppa:duns")? MWS: A CPA template can nail down the owning party's PartyId but it has to leave the other party free to choose its own. MWS: Another valid question to ask is whether it is necessary for a CPA template to pass parser validation. It would be a good idea but omitting validation before the template is completely filled in would allow for leaving some values empty. Thoughts? ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC