I for one am a big believer in freedom of the press, as Mike is representing his own personal opinion rather than an official opinion of OASIS. I personally feel that Mike has done due diligence by placing the date at the bottom of each piece, and that anyone reading them should take this into account. I personally do not feel that Mike is under any obligation (not saying that anyone implied that he was) to make any changes whatsoever to his site. Kind Regards, Joe "CRAWFORD, Mark" wrote: > > This seems like apretty heavy burden to levy on Mike- tantamount to asking for an independent validation of the specs. Isn't that a function of the ebXMLIIC TC? > Mark Crawford > Research Fellow - LMI XML Lead > W3C Advisory Committee, OASIS, RosettaNet Representative > Vice Chair - OASIS UBL TC & Chair Naming and Design Rules Subcommittee > Chair - UN/CEFACT XML Syntax Working Group > Editor - UN/CEFACT Core Components > ______ > Logistics Management Institute > 2000 Corporate Ridge, McLean, VA 22102-7805 > (703) 917-7177 Fax (703) 917-7481 > Wireless (703) 655-4810 > mcrawford@lmi.org > http://www.lmi.org > "Opportunity is what you make of it" > > -----Original Message----- > From: Mike Rawlins <mcr@rawlinsecconsulting.com> > To: ebxml-dev <ebxml-dev@lists.ebxml.org> > Sent: Wed Feb 11 00:34:39 2004 > Subject: Re: ebXML Registry --- can work as distributed registries? > > At 12:01 PM 2/10/2004 -0800, Duane Nickull wrote <snipped>: > > >[DN] I also second the notion of a 3 years after update. I would like to > >suggest however that Mike write the first draft in a vacuum using only the > >official specs. This IMHO, is a good sanity check to make sure that > >someone can pick up the specs and they are complete enough to > >implement. While I also had several points of contention with Mike's > >articles at the time, I did feel that the entire process added value to > >ebXML. If he hadn't pointed out the shortcomings, it may have been longer > >before we caught them. All teams could comment on these before final > >publishing. Then it can be worded to reflect those comments. > > > >"while the author felt there was insufficient support for XX, the XX team > >expressed that it felt it was possible by doing XX. The following > >implementation experience was cited to back up this claim" > > > >Mike - you up for this task? > > Gee, thanks, Duane. Nothing like a bit of throwing down the gauntlet, eh? ;^) > > All I can promise you is that I will consider your suggestion. Those with > a long enough memory will recall that I did actively solicit comments from > various ebXML TC leads during the posting of the original series, > particularly after the "Market Impact" article was posted. So few > responded that I have doubts about the effort being worthwhile a second > time. At this point I'm more inclined to write the update based on the > specs and other publicly available materials and let the chips fall where > they may. For rebuttals and corrections this listserv has worked quite > well, but I could also offer links on my pages for them. At any rate, I'll > think about it. > > Cheers, > > --------------------------------------------------------------- > Michael C. Rawlins, Rawlins EC Consulting > www.rawlinsecconsulting.com > Using XML with Legacy Business Applications (Addison-Wesley, 2003) > www.awprofessional.com/titles/0321154940 > > The ebxml-dev list is sponsored by OASIS <http://www.oasis-open.org> The > list archives are at http://lists.ebxml.org/archives/ebxml-dev/ > To subscribe or unsubscribe from this list use the subscription manager: > <http://www.oasis-open.org/mlmanage/> > > The ebxml-dev list is sponsored by OASIS <http://www.oasis-open.org> The > list archives are at http://lists.ebxml.org/archives/ebxml-dev/ > To subscribe or unsubscribe from this list use the subscription manager: > <http://www.oasis-open.org/mlmanage/> The ebxml-dev list is sponsored by OASIS <http://www.oasis-open.org> The list archives are at http://lists.ebxml.org/archives/ebxml-dev/ To subscribe or unsubscribe from this list use the subscription manager: <http://www.oasis-open.org/mlmanage/>
<<attachment: winmail.dat>>