Fwd: AW: 1 or 2 xpath expression per negotiatable information item

[Martin Sachs <msachs@cyclonecommerce.com>]

Forwarding off-line discussion that may be relevant to the next draft.

>X-MS-Has-Attach:
>X-MS-TNEF-Correlator:
>Thread-Topic: 1 or 2 xpath expression per negotiatable information item
>Thread-Index: AcPqOSaqVUYRR/TSQ46K+EwjTkNTSAAJ33pQ
>X-XWall-Bayes: 14
>From: "Vetter, Michael" <Michael.Vetter@iao.fraunhofer.de>
>To: Sacha Schlegel <sacha_oasis@schlegel.li> ,
>         "msachs@cyclonecommerce.com" <msachs@cyclonecommerce.com>
>Subject: AW: 1 or 2 xpath expression per negotiatable information item
>Date: Tue, 3 Feb 2004 07:30:06 -0700
>X-Assembled-By: XWall v3.28
>X-OriginalArrivalTime: 03 Feb 2004 14:30:11.0193 (UTC) 
>FILETIME=[3ADF8E90:01C3EA62]
>
>Hi Sacha and Marty
>
>I agree with Sacha that the second XPath is only useful for the NDD that 
>accompanies a CPA template/draft.
>May be two diffent schemata for NDD and MNDD (merged NDD) would reduce the 
>confusion.
>A MNDD could also include conflicts that occur during the merging process.
>
>Kind regards
>
>Michael
>
> > -----Ursprüngliche Nachricht-----
> > Von: Sacha Schlegel [mailto:sacha_oasis@schlegel.li]
> > Gesendet: Dienstag, 3. Februar 2004 10:36
> > An: msachs@cyclonecommerce.com; Vetter, Michael
> > Cc: ebxml-cppa-negot@lists.oasis-open.org
> > Betreff: 1 or 2 xpath expression per negotiatable information item
> >
> >
> > Hi Marty
> > Hi Michael
> >
> > We had once the discussion whether an NDD item needs one or
> > two XPath expression. Michael and me were thinking it needs
> > two XPath expression. I think I know why Michael and me were
> > thinking that.
> >
> > This introduces an issue of the ANCPA Specification.
> >
> > I think we have to differentiate between an NDD for a CPA
> > template and an NDD for a CPP.
> >
> > o An NDD item for a CPA template seems to need 2 XPath
> > expressions. o An NDD item for a CPP seems to need 1 XPath expression.
> >
> > Kind regards
> >
> > Sacha
> >
> >

*************************************
Martin Sachs
standards architect
Cyclone Commerce
msachs@cyclonecommerce.com