Ron, I believe you're right about that, given NIST's role as you mention below. Thanks for educating me. Joe "Schuldt, Ron L" wrote: > > Joe, > > Since the conceptual model is being developed by industry volunteers and > NIST is simply a facilitator, I don't believe it falls into the same > category as public information developed by a government organization > such as NIST - but I also might be wrong. > > The eBSC conceptual model team had a telecon yesterday (Mark Palmer of > NIST also attended) to discuss the status of the model. We all agreed > that the model needed better definitions for the various categories > (rows) of standards. We felt that the current definitions are too > ambiguous and therefore might cause various industries to improperly > indicate within their assigned column which standards they are using, > adopting or evaluating for possible adoption. > > The intent is that once the conceptual model is complete, various > industries would be able to fill-in the cells online associated with > their assigned column. By simply having this information publicly > available would provide a tremendous leverage point for the convergence > of ebusiness standards. > > Ron Schuldt > Senior Staff Systems Architect > Lockheed Martin Enterprise Information Systems > 11757 W. Ken Caryl Ave. > #F521 Mail Point DC5694 > Littleton, CO 80127 > 303-977-1414 > ron.l.schuldt@lmco.com > > > -----Original Message----- > From: Chiusano Joseph [mailto:chiusano_joseph@bah.com] > Sent: Tuesday, July 13, 2004 10:18 AM > To: Schuldt, Ron L > Cc: Kremena Gotcheva; ebxml-dev@lists.ebxml.org; dill@gefeg.com > Subject: Re: Alphabet soup, was RE: hey whilst we are all asking for > things > > Ron, > > If the conceptual model is being developed by a group that is sponsored > by a federal agency (such as NIST), I believe (but could be wrong) that > it has to be considered public information. > > Joe > > "Schuldt, Ron L" wrote: > > > > Kremena, > > > > I am not aware of a "globally recognized" list that puts the various > standards acronyms into an architectural perspective (i.e., that > describes how they are inter-related and their overlaps). However, I am > aware of at least one effort that is attempting to build a framework > (conceptual model) of various ebusiness standards. That conceptual model > is being developed by an team within the eBusiness Standards Convergence > (eBSC) Forum - see > http://www.mel.nist.gov/div826/msid/sima/ebsc/index.htm > > > > I am a member of the team that is building the conceptual model. One > of the stated purposes of the conceptual model is "To provide an > approach for standards developers to effectively communicate > eBusiness-standards-related concepts among one another promoting more > effective standards development, cross-industry standards collaboration, > and standards adoption and deployment" Since the conceptual model is > only in draft form and not ready yet for public review, I am not at > liberty to share it at this time. > > > > Ron Schuldt > > Senior Staff Systems Architect > > Lockheed Martin Enterprise Information Systems > > 11757 W. Ken Caryl Ave. > > #F521 Mail Point DC5694 > > Littleton, CO 80127 > > 303-977-1414 > > ron.l.schuldt@lmco.com > > > > -----Original Message----- > > From: Kremena Gotcheva [mailto:infom@bcci.bg] > > Sent: Tuesday, July 13, 2004 9:27 AM > > To: Schuldt, Ron L > > Cc: ebxml-dev@lists.ebxml.org; dill@gefeg.com > > Subject: Alphabet soup, was RE: hey whilst we are all asking for > things > > > > Ron, > > > > Thanks for the interesting links. One never stops learning ;-) > > > > While on the topic of implementation/adoption: you and many others on > the > > list will be familiar with the fact that part of every technology > > adoption, be it in a private or public organization, is getting > > non-technical management's approval. To do so, one must report. > > > > Can you give me some best practices on how to report the alphabet soup > - > > the difference/interrelations between UDEF, CCTS, ebXML, WSDL, UDDI, > and, > > and, and... The IT world of today is full of thriving acronyms that > are > > difficult to follow and virtually impossible to communicate in a > nutshell. > > > > Is there a globally recognized, neutral, more or less comprehensive > list > > of acronyms with a schema what technology fits where and what is it > good > > for - a kind of who's who in the acronym mess? If not, I think > creating > > one would greatly facilitate interoperability efforts since IT people > will > > make their needs clear to decisionmakers. I would be happy to work on > > setting such page up and maintaining it - maybe even as part of the > work > > on the GFP topic on Ecommerce and business [1]. > > > > Actually, in case such who's who doesn't exist, please regard this > mail as > > a call to start an open process on the topic. If enough volunteers > write > > me on or off list, I'll set up some kind of discussion forum. Please > > indicate your background, and views on the presentation of the theme. > > Also, what would be the critical mass of participants for the success > of > > such undertaking, in your opinion? > > > > Thanks in advance, > > Kremena > > > > [1] http://www.gfptt.org/topics/eCommerce > > > > 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/> > > -- > Kind Regards, > Joseph Chiusano > Associate > Booz | Allen | Hamilton -- Kind Regards, Joseph Chiusano Associate Booz | Allen | Hamilton 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>>