- From: David Orchard <dorchard@bea.com>
- Date: Tue, 23 Jan 2007 08:45:50 -0800
- To: "Felix Sasaki" <fsasaki@w3.org>
- Cc: "Philippe Le Hegaret" <plh@w3.org>, <public-ws-policy-eds@w3.org>
So this works for "stock" xmlpsec? > -----Original Message----- > From: public-ws-policy-eds-request@w3.org > [mailto:public-ws-policy-eds-request@w3.org] On Behalf Of Felix Sasaki > Sent: Tuesday, January 23, 2007 8:39 AM > To: David Orchard > Cc: Philippe Le Hegaret; public-ws-policy-eds@w3.org > Subject: Re: WSDL 1.1 element identifiers > > > David Orchard wrote: > > Yes.. > > > > The problem is that we have to use the WSDL 2.0 xmlspec > because it has > > support for <emph> inside <code>, which is in the table of > identifiers. > > The WG wanted the table to look like the WSDL 2.0 table. > > I solved the problem, but did not commit yet. I used markup like this: > <td><code>wsdl11.types(</code><code > role="code-emph">types</code><code>)</code></td> > and munged the xslt to produce HTML like this: > <code style="font-style: italic;">types</code> You can see > the look at > http://www.w3.org/2002/ws/policy/7/01/wsdl11-elementidentifier > / (not finished for publication yet, only member-visible.) > > Felix > > Regards, Felix. > > > > > Thanks, > > Dave > > > >> -----Original Message----- > >> From: Philippe Le Hegaret [mailto:plh@w3.org] > >> Sent: Tuesday, January 23, 2007 7:15 AM > >> To: David Orchard > >> Subject: WSDL 1.1 element identifiers > >> > >> David, > >> > >> a long time ago, you mentioned troubles with xmlspec and > the WSDL 1.1 > >> element identifiers. I promised to look into that and > never did. Do > >> you still have them? > >> > >> Philippe > >> > >> > >> > > > > >
Received on Tuesday, 23 January 2007 16:46:32 UTC