[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [dsml] Proposal: Batch* -> DsmlBatch*
Yes. However, since as far as I can tell the only other constructs that use the Dsml prefix are type and group names, not element names, and I could live with them either way. Shon Vella Software Engineer, Consultant svella@novell.com Novell, Inc., the leading provider of Net services software www.novell.com >>> Jeff Parham <jeffparh@windows.microsoft.com> 10/15/01 02:26PM >>> Then do you advocate taking the "Dsml" prefix out of other constructs in the schema? -----Original Message----- From: Shon Vella [mailto:SVELLA@novell.com] Sent: Monday, October 15, 2001 12:25 PM To: dsml@lists.oasis-open.org; Jeff Parham Subject: Re: [dsml] Proposal: Batch* -> DsmlBatch* I don't like include Dsml in the element name since it is already qualified by the dsml namespace. Shon Vella Software Engineer, Consultant svella@novell.com Novell, Inc., the leading provider of Net services software www.novell.com >>> Jeff Parham <jeffparh@windows.microsoft.com> 10/15/01 12:49PM >>> Here's a (hopefully) non-controversial proposal: In the baseline schema the envelopes were named DsmlEnvelopeRequest and DsmlEnvelopeResponse. In the current schema they're BatchRequest and BatchResponse. I propose we take the best of both and name them DsmlBatchRequest and DsmlBatchResponse. -J ---------------------------------------------------------------- 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