[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ws-rx-editors] RE: publish WS-RX CD-02 artifacts
Gilbert, I sincerely apologize: please forgive me. I'm not the OASIS webmaster (indeed, we don't have one just now), but this reasonable request came in front of me, and I failed to make sure it was handled. I'll [turn off the stove, cooking supper and] do this right now. I saw Marc's reference to the RDDLs on the ASIS review thread; we need to get your poster children lookin' good. Humbly, Robin ------------------- On Tue, 28 Feb 2006, Gilbert Pilz wrote: > Robin and/or Mary, > > Any information on updating > http://docs.oasis-open.org/ws-rx/wsrm/200510/wsrm-1.1-rddl-cd-02.html > and > http://docs.oasis-open.org/ws-rx/wsrmp/200510/wsrmp-1.1-rddl-cd-02.html > as indicated below? > > - gp > > > -----Original Message----- > > From: Robin Cover [mailto:robin@oasis-open.org] > > Sent: Thursday, February 23, 2006 1:42 PM > > To: Gilbert Pilz > > Cc: Marc Goodner; Mary McRae; Robin Cover; > > ws-rx-editors@lists.oasis-open.org > > Subject: RE: [ws-rx-editors] RE: publish WS-RX CD-02 artifacts > > > > On Thu, 23 Feb 2006, Gilbert Pilz wrote: > > > > > Robin, > > > > > > First thanks to Mary and yourself for working on this. > > > > > > I agree with you that the WS-RX public installation is still in the > > > experimental stage. I've fixed the "important" links in > > both the wsrm > > > and wsrmp documents and uploaded them to Kavi: > > > > > > > > http://www.oasis-open.org/apps/org/workgroup/ws-rx-editors/download.ph > > > p/ > > > 16880/wsrm-1.1-rddl-wd-02.html > > > > > > > > http://www.oasis-open.org/apps/org/workgroup/ws-rx-editors/download.ph > > > p/ > > > 16881/wsrmp-1.1-rddl-wd-02.html > > > > > > (I'm hoping you have access to the WS-RX Editors pages) > > > > > > If you or Mary could upload these pages to > > docs.oasis-open.org I would > > > apprecitate it. > > > > We will do this. > > > > > > > > As for the desired behavior; one thing I *do* know is that, from a > > > machine processing perspective, doing an HTTP GET on > > ".../wsrm/200510" > > > (no trailing slash, exactly the same as the WS-RM namespace > > URI) must > > > return the RDDL document. If this doesn't work, then there > > isn't much > > > point in using RDDL. This means that a human also sees the RDDL > > > document when browsing to the same URI. > > > > Absolutely: that's what a namespace document is designed to > > do, RDDL or otherwise. We will change the implementation, but > > the effect will be the same, as everyone expects. > > > > > As for what a human sees when they browse to ".../wsrm/200510/" > > > (trailing slash, *not* the WS-RM namespace URI), I think that they > > > should see the RDDL document as well. I don't really see > > the need for > > > humans to be able to see the "directory index" view for this URI. > > > Everything we want them to see (specs, schema, WSDL, etc.) > > is linked > > > from the RDDL doc so, in theory, they shouldn't be missing > > anything . . > > > . > > > > I think that's a defensible position, especially in the case > > of /wsrm/200510/ where the directory /200510/ has four user files. > > > > We want to also support the scenario where we have: > > > > http://docs.oasis-open.org/fooTC/barSpec/200601 /* > > namespace URI */ > > http://docs.oasis-open.org/fooTC/barSpec/200601/ /* directory */ > > http://docs.oasis-open.org/fooTC/barSpec/200601/a/ > > http://docs.oasis-open.org/fooTC/barSpec/200601/b/ > > http://docs.oasis-open.org/fooTC/barSpec/200601/c/ > > http://docs.oasis-open.org/fooTC/barSpec/200601/d/baz/index.html > > > > given than the directory /200601/ might contain the > > prose-format spec docs, and the /a/ - /d/ directories > > collectively have 500 files/directories. UBL and DITA TCs > > have large numbers of files in spec distributions, with deep > > hierarchy. > > > > In this case, some TC might want an index file to live at > > http://docs.oasis-open.org/fooTC/barSpec/200601/ > > > > Alternately, the better answer might be to use the namespace > > document at > > http://docs.oasis-open.org/fooTC/barSpec/200601 > > to document the files and file locations for all versions of > > the spec which use that namespace. > > > > TBD... > > > > > > > > > > I'll be working on fixing up some of the images etc. and > > I'll keep you > > > posted. > > > > > > - gp > > > > > > > -----Original Message----- > > > > From: Robin Cover [mailto:robin@oasis-open.org] > > > > Sent: Wednesday, February 22, 2006 6:31 PM > > > > To: Marc Goodner > > > > Cc: Mary McRae; Gilbert Pilz; Robin Cover; > > > > ws-rx-editors@lists.oasis-open.org > > > > Subject: RE: [ws-rx-editors] RE: publish WS-RX CD-02 artifacts > > > > > > > > Gilbert and Marc, > > > > > > > > I have answered your request (nominally) to have the server treat > > > > the following two HTTP scheme URI namespaces as > > dereferenceable to > > > > the corresponding RDDL documents that you supplied: > > > > > > > > http://docs.oasis-open.org/ws-rx/wsrm/200510 > > > > http://docs.oasis-open.org/ws-rx/wsrmp/200510 > > > > > > > > There are a number of other kinks in this CD-02 > > installation, so I > > > > think we need to consider it somewhat experimental (ask > > Mary McRae > > > > for the Chapter and Verse which allows experimentation). > > > > > > > > A number of links in the RDDL documents need to be > > repaired, and I > > > > noted at least one mismatch between this install and the URIs > > > > advertised in the PDF specs (e.g., for /wsrm/ > > > > > > http://docs.oasis-open.org/ws-rx/wsrm/200510/wsrm-1.1-spec-cd-02.pdf > > > > I read: > > > > > > > > "The normative schema for WS-ReliableMessaging can be found at: > > > > http://docs.oasis-open.org/ws-rx/wsrm/200510/wsrm-1.1.xsd " > > > > > > > > whereas the install has: > > > > > > > > http://docs.oasis-open.org/ws-rx/wsrm/200510/wsrm-1.1-schema-2 > > > 00510.xsd > > > > > > > > We could create a symlink to fix this, but I'll refer you to Mary > > > > McRae for ideal solutions in this case. > > > > > > > > The mechanism currently used to force the server to deliver RDDL > > > > namespace documents (dereferenced namespace URIs) is not > > ideal, and > > > > will probably need to be changed: it uses a redirect -- > > actually two > > > > redirects, because the first simply fixes the slashless directory > > > > (from the file system and Apache server POV) > > > > http://docs.oasis-open.org/ws-rx/wsrm/200510 > > > > to be http://docs.oasis-open.org/ws-rx/wsrm/200510/, and > > the second > > > > uses an HTTP redirect (meta refresh) to get the RDDL document. > > > > > > > > It's slow, and a kludge -- pending use of the server > > directives to > > > > establish a proper mapping. > > > > > > > > In addition to the latency that comes from redirects, we now face > > > > the issue that I mentioned some months ago on the WS-RX list: > > > > > > > > conflict between the desire to have a namespace URI match a > > > > directory/folder in which the artifacts are stored: > > > > > > > > /ws-rx/wsrm/200510/ > > > > /ws-rx/wsrm/200510/wsrm-1.1-schema-200510.xsd > > > > /ws-rx/wsrm/200510/wsrm-1.1-spec-cd-02.pdf > > > > /ws-rx/wsrm/200510/wsrm-1.1-wsdl-200510.wsdl > > > > > > > > Normally, dereferencing a URI that matches a directory (trailing > > > > slash or none) gets you an index for the directory; if > > you comandeer > > > > (use) the directory as the namespace URI, you (may) forfeit the > > > > expected behavior, unless you consider the RDDL namespace > > document > > > > to BE the index. > > > > > > > > We have several solutions (I think), all with positive > > and negative > > > > features. If you can explain what you think you WANT to > > happen in > > > > (a) and (b), when dereferenced, we'll study options at the server > > > > level: > > > > > > > > (a) http://docs.oasis-open.org/ws-rx/wsrm/200510 > > > > (b) http://docs.oasis-open.org/ws-rx/wsrm/200510/ > > > > > > > > If it's possible to map (a) to your RDDL and (b) to a traditional > > > > index, that would still be confusing to users, > > potentially... dunno. > > > > > > > > As you can see, it's all experimental, including the ad hoc index > > > > files I created to initially solve the index problem: > > > > > > > > http://docs.oasis-open.org/ws-rx/wsrm/wsrm-200510-CD02-TOC.html > > > > visible here: http://docs.oasis-open.org/ws-rx/wsrm/ > > > > > > > > http://docs.oasis-open.org/ws-rx/wsrmp/wsrmp-200510-CD02-TOC.html > > > > visible here: http://docs.oasis-open.org/ws-rx/wsrmp/ > > > > > > > > -rcc > > > > > > > > > > > > On Wed, 22 Feb 2006, Marc Goodner wrote: > > > > > > > > > Robin knows how to setup sym links for that. Basically > > > > there would be > > > > > a symlink "file" called index that would point to the > > RDDL file. > > > > > That's how we keep the latest link for the issues lists. > > > > > > > > > > Marc Goodner > > > > > Technical Diplomat > > > > > Microsoft Corporation > > > > > Tel: (425) 703-1903 > > > > > Blog: http://spaces.msn.com/mrgoodner/ > > > > > > > > > > > > > > > -----Original Message----- > > > > > From: Mary McRae [mailto:marypmcrae@gmail.com] > > > > > Sent: Wednesday, February 22, 2006 1:50 PM > > > > > To: 'Gilbert Pilz' > > > > > Cc: ws-rx-editors@lists.oasis-open.org; 'Robin Cover' > > > > > Subject: RE: [ws-rx-editors] RE: publish WS-RX CD-02 artifacts > > > > > > > > > > Sounds great - but I don't think we can do that right now. > > > > I think the > > > > > only way that would work would be to rename the file "index" > > > > > but I need Robin's confirmation on that. If you have updated > > > > > files, I'll try to get them uploaded as soon as I can. > > > > > > > > > > mary > > > > > > > > > > > -----Original Message----- > > > > > > From: Gilbert Pilz [mailto:Gilbert.Pilz@bea.com] > > > > > > Sent: Wednesday, February 22, 2006 4:32 PM > > > > > > To: mary.mcrae@oasis-open.org > > > > > > Cc: ws-rx-editors@lists.oasis-open.org; Robin Cover > > > > > > Subject: RE: [ws-rx-editors] RE: publish WS-RX CD-02 artifacts > > > > > > > > > > > > Mary, > > > > > > > > > > > > There are a number of problems and most of them are my fault > > > > > > (how come you never see the obvious stuff until its live?). > > > > > > The one thing I was wondering if you could do anything > > > > about is to > > > > > > make "wsrm-1.1-rddl-cd-02.html" the default page for > > > > > > "http://docs.oasis-open.org/ws-rc/wsrm/200510/";? That way > > > > if anyone > > > > > > dereferences the namespace URI they will immediately see the > > > > > > RDDL document. > > > > > > > > > > > > - gp > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: Mary McRae [mailto:marypmcrae@gmail.com] > > > > > > > Sent: Wednesday, February 22, 2006 1:16 PM > > > > > > > To: 'Patil, Sanjay'; 'Marc Goodner'; Gilbert Pilz > > > > > > > Cc: ws-rx-editors@lists.oasis-open.org; 'Robin > > Cover'; 'James > > > > > > > Bryce Clark' > > > > > > > Subject: RE: [ws-rx-editors] RE: publish WS-RX > > CD-02 artifacts > > > > > > > > > > > > > > Please check and make sure the files are working as > > > > expected ... > > > > > > > Apparently some portion of the OASIS website header > > was copied > > > > > > > into the RDDL files; these aren't working properly. My > > > > > > suggestion would be > > > > > > > to just point to the OASIS logo from the templates location > > > > > > and omit > > > > > > > the rest of the heading. > > > > > > > > > > > > > > http://docs.oasis-open.org/templates/OASISLogo.jpg > > > > > > > > > > > > > > Thanks! > > > > > > > > > > > > > > Mary > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > From: Patil, Sanjay [mailto:sanjay.patil@sap.com] > > > > > > > > Sent: Wednesday, February 22, 2006 1:48 PM > > > > > > > > To: mary.mcrae@oasis-open.org; Marc Goodner; Gilbert Pilz > > > > > > > > Cc: ws-rx-editors@lists.oasis-open.org; Robin Cover; James > > > > > > > Bryce Clark > > > > > > > > Subject: RE: [ws-rx-editors] RE: publish WS-RX CD-02 > > > > > > > > artifacts > > > > > > > > > > > > > > > > > > > > > > > > Mary, > > > > > > > > > > > > > > > > Would it be possible to upload the WS-RX CD-02 artifacts > > > > > > today? The > > > > > > > > weekly meeting for our TC is scheduled for tomorrow and > > > > > > it would be > > > > > > > > great to have the CD-02 artifacts published and available > > > > > > > in advance > > > > > > > > of the weekly meeting. > > > > > > > > > > > > > > > > -- Sanjay > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > > From: Mary McRae [mailto:marypmcrae@gmail.com] > > > > > > > > > Sent: Wednesday, Feb 22, 2006 10:38 AM > > > > > > > > > To: 'Marc Goodner'; Patil, Sanjay; 'Gilbert Pilz' > > > > > > > > > Cc: ws-rx-editors@lists.oasis-open.org; 'Robin Cover'; > > > > > > > 'James Bryce > > > > > > > > > Clark' > > > > > > > > > Subject: RE: [ws-rx-editors] RE: publish WS-RX > > > > CD-02 artifacts > > > > > > > > > > > > > > > > > > Hi Mark, > > > > > > > > > > > > > > > > > > I was actually trying to say that OASIS does > > *not* have > > > > > > > > an explicit > > > > > > > > > policy regarding the reserved use of keywords. I don't > > > > > > > believe the > > > > > > > > > issue had ever arisen in the past; staff has submitted > > > > > > this as an > > > > > > > > > issue to the Board TC Process Committee. > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > > > > > > > > > Mary > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > > > From: Marc Goodner [mailto:mgoodner@microsoft.com] > > > > > > > > > > Sent: Wednesday, February 22, 2006 12:21 PM > > > > > > > > > > To: Patil, Sanjay; mary.mcrae@oasis-open.org; Gilbert > > > > > > > > > > Pilz > > > > > > > > > > Cc: ws-rx-editors@lists.oasis-open.org; Robin Cover; > > > > > > > > > > James > > > > > > > > > Bryce Clark > > > > > > > > > > Subject: RE: [ws-rx-editors] RE: publish WS-RX CD-02 > > > > > > > > > > artifacts > > > > > > > > > > > > > > > > > > > > Mary, you imply that OASIS does now have some > > > > > > approved accepted > > > > > > > > > > policy regarding things like keywords and products. > > > > > > > > > > I don't think that is correct. If there is an approved > > > > > > > > policy that > > > > > > > > > > covers this pleas provide a reference to it. > > > > > > > > > > > > > > > > > > > > Marc Goodner > > > > > > > > > > Technical Diplomat > > > > > > > > > > Microsoft Corporation > > > > > > > > > > Tel: (425) 703-1903 > > > > > > > > > > Blog: http://spaces.msn.com/mrgoodner/ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > > > From: Patil, Sanjay [mailto:sanjay.patil@sap.com] > > > > > > > > > > Sent: Wednesday, February 22, 2006 8:05 AM > > > > > > > > > > To: mary.mcrae@oasis-open.org; Gilbert Pilz > > > > > > > > > > Cc: ws-rx-editors@lists.oasis-open.org; Robin Cover; > > > > > > > > > > James > > > > > > > > > Bryce Clark > > > > > > > > > > Subject: RE: [ws-rx-editors] RE: publish WS-RX CD-02 > > > > > > > > > > artifacts > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Mary, > > > > > > > > > > > > > > > > > > > > The use of the date identifier in the URI is a > > > > > > > > > > deliberate > > > > > > > > > decision the > > > > > > > > > > WS-RX TC made after sweating over a lot of > > discussions. > > > > > > > > > > Please note that > > > > > > > > > > the product version identifiers are part of > > the artifact > > > > > > > > names (last > > > > > > > > > > token in the URI) in our scheme . > > > > > > > > > > > > > > > > > > > > So I must say that currently we do not much choice and > > > > > > > > > would strongly > > > > > > > > > > prefer to keep the format of the URI as suggested in > > > > > > > > Gil's original > > > > > > > > > > email. > > > > > > > > > > > > > > > > > > > > --Sanjay > > > > > > > > > > WS-RX TC Co-Chair > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > > > > From: Mary McRae [mailto:mary.mcrae@oasis-open.org] > > > > > > > > > > > Sent: Wednesday, Feb 22, 2006 7:23 AM > > > > > > > > > > > To: 'Gilbert Pilz' > > > > > > > > > > > Cc: ws-rx-editors@lists.oasis-open.org; > > 'Robin Cover' > > > > > > > > > > > Subject: [ws-rx-editors] RE: publish WS-RX > > > > CD-02 artifacts > > > > > > > > > > > > > > > > > > > > > > Hi Gilbert, > > > > > > > > > > > > > > > > > > > > > > My apologies for the delay in responding; > > I've been > > > > > > > trying to > > > > > > > > > > > research the decision regarding the WS-RX > > TC's use of > > > > > > > > > the keyword > > > > > > > > > > > WSRM. It appears that since we did not have an > > > > > > > > > > > explicit > > > > > > > > policy in > > > > > > > > > > > place reserving the keyword for use only by the WSRM > > > > > > > > TC, and since > > > > > > > > > > > the WSRM TC does not call its work product "wsrm", > > > > > > > > > > > that > > > > > > > > WS-RX is > > > > > > > > > > > being allowed to use the WSRM as a product > > designation. > > > > > > > > > > There's one > > > > > > > > > > > other problem however,and that's the use of a date > > > > > > identifier > > > > > > > > > > > rather than a version number - The OASIS Library is > > > > > > > > configured to > > > > > > > > > > > identify TC work products by version number (i.e. > > > > > > > > > > > docs.oasis-open.org/ws-rx/wsrm/v1.1/). Is it > > > > > > possible for the > > > > > > > > > > > editors to reconfigure the documents to match > > > > that scheme? > > > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > > > > > > > > > Mary > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > > > > > From: Gilbert Pilz [mailto:Gilbert.Pilz@bea.com] > > > > > > > > > > > > Sent: Wednesday, February 15, 2006 1:58 AM > > > > > > > > > > > > To: Mary McRae > > > > > > > > > > > > Cc: ws-rx-editors@lists.oasis-open.org; > > Robin Cover > > > > > > > > > > > > Subject: RE: publish WS-RX CD-02 artifacts > > > > > > > > > > > > > > > > > > > > > > > > Mary, > > > > > > > > > > > > > > > > > > > > > > > > Any word on the review of the WS-RX CD-02 > > artifacts? > > > > > > > > The rest of > > > > > > > > > > > > the TC is going to want status from me on > > Thursday > > > > > > > > > > > > so > > > > > > > > I need to > > > > > > > > > > > > know what to tell them. > > > > > > > > > > > > > > > > > > > > > > > > - gp > > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > > > > > > From: Robin Cover [mailto:robin@oasis-open.org] > > > > > > > > > > > > > Sent: Monday, February 13, 2006 2:04 PM > > > > > > > > > > > > > To: Gilbert Pilz > > > > > > > > > > > > > Cc: ws-rx-editors@lists.oasis-open.org; > > Mary McRae > > > > > > > > > > > > > Subject: Re: publish WS-RX CD-02 artifacts > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, 13 Feb 2006, Gilbert Pilz wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > Robin, > > > > > > > > > > > > > > > > > > > > > > > > > > > > Attached is a zip archive containing the > > > > > > artifacts that > > > > > > > > > > > > make up the > > > > > > > > > > > > > > WX-RX TC's Committee Draft 02. The archive > > > > > > structure is > > > > > > > > > > > > > intended for > > > > > > > > > > > > > > unpacking under > > > > > > > http://docs.oasis-open.org/ws-rx. You will > > > > > > > > > > > > > notice that > > > > > > > > > > > > > > we have included the RDDL documents > > > > > > > > > > > > > > "wsrm/200510/wsrm-1.1-rddl-cd-02.html" and > > > > > > > > > > > > > > "wsrmp/200510/wsrmp-1.1-rddl-cd-02.html". > > > > In order > > > > > > > > > > > > > > for > > > > > > > > > > > > > things to work > > > > > > > > > > > > > > as intended these files need to be the > > > > > > default page for > > > > > > > > > > > > > > > > > > "http://docs.oasis-open.org/ws-rx/wsrm/200510/"; and > > > > > > > > > > > > > > > > "http://docs.oasis-open.org/ws-rx/wsrmp/200510/"; > > > > > > > > > respectively. > > > > > > > > > > > > > > > > > > > > > > > > > > > > Please let me know if any of the above is > > > > unclear or > > > > > > > > > > there is a > > > > > > > > > > > > > > problem with organizing the web space > > in this way. > > > > > > > > > > > > > > > > > > > > > > > > > > > > Gilbert Pilz > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Gilbert, > > > > > > > > > > > > > > > > > > > > > > > > > > I'm forwarding your request to Mary McRae, > > > > > > > currently listed > > > > > > > > > > > > as one of > > > > > > > > > > > > > the OASIS Staff Contacts for the WS-RX TC, and > > > > > > responsible > > > > > > > > > > > > for the QA > > > > > > > > > > > > > work on approved specs as delegated to the > > > > > > OASIS TC Admin. > > > > > > > > > > > > > > > > > > > > > > > > > > I'm pleased that your TC has decided to use RDDL > > > > > > > documents: > > > > > > > > > > > > > it makes a lot of sense to me. > > > > > > > > > > > > > > > > > > > > > > > > > > Congratulations on TC progress > > resulting in these > > > > > > > > > > > approved CD specs. > > > > > > > > > > > > > > > > > > > > > > > > > > Robin Cover > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ______________________________________________________________ > > > > > > _________ > > > > > > Notice: This email message, together with any > > attachments, may > > > > > > contain information of BEA Systems, Inc., its > > > > subsidiaries and > > > > > > affiliated entities, that may be confidential, proprietary, > > > > > > copyrighted and/or legally privileged, and is intended > > > > solely for > > > > > > the use of the individual or entity named in this message. If > > > > > > you are not the intended recipient, and have received this > > > > > > message in error, please immediately return this by > > email and then delete it. > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > ______________________________________________________________________ > > > _ > > > Notice: This email message, together with any attachments, may > > > contain information of BEA Systems, Inc., its > > subsidiaries and > > > affiliated entities, that may be confidential, proprietary, > > > copyrighted and/or legally privileged, and is intended > > solely for the > > > use of the individual or entity named in this message. If > > you are not > > > the intended recipient, and have received this message in error, > > > please immediately return this by email and then delete it. > > > > > > > -- > > > > > > > _______________________________________________________________________ > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally privileged, and is intended solely for the use of the individual > or entity named in this message. If you are not the intended recipient, > and have received this message in error, please immediately return this > by email and then delete it. > --
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]