hello dudes and dudettes, i am in the throws of building a suite of ebXML services, off-the-shelf and packaged. i am thinking of throwing in the Debtors/creditors ledger and inventory system in for free. i should be ready by december 2005. i also have an ace up my sleeve that should make ebXML go POP, but i will not talk about that as a major ISP (in new zealand) and i are looking all of this and going "yummy". also, the interface is going to be for "dummies" to use. it is my opinion that people look at the specs and get scared off. sure it is a mouth full, but once you do get to that "aha" stage, its all smooth sailing. the UBL model is an imperative optional component that should be taken up, as it solves the interop problem. in 1.5 months i should be fully spec'd out, class diagrams and such, of all the ebXML services i intend building, as i have just completed the first-cut Use Case diagrams (see UML). my URL: www.archmage.org.nz i have not updated the site for a month, as my server is "under going changes" and will not be up for 1 month. so i will drop some cool Use Case Diagrams (JPEG anyone?) on the site. this ebXML thing must be turned around. do not think technology, think products. once you start down that road you start looking into marketing strategies, and thats why i have paired up with an ISP. client base already there, just scope out that discretionary income thing, figure out their propensities to buy more product from us, and you must display the added-value in your suite. technology for technology sake only makes people like us happy. anyhow, i have this thing i am chucking in free, along with the SERIOUSLY abridged ERP package i have been working on, and ebXML goes on the shelf, shrink-wrapped, and "international" ready. man, after all my student income that i have spent, i hope it works. oh yeah, just in case you are feeling poorly, and thinking "gee he seems on to it", i am older than most of you, except you alan kotok and colin adam. "all we have are questions that need answers, so dig deep for answers". cheerfully, dean hemopo auckland, new zealand -----Original Message----- From: david.lyon@computergrid.net [mailto:david.lyon@computergrid.net] Sent: Wednesday, 14 July 2004 12:06 p.m. To: ebxml-dev@lists.ebxml.org Subject: What the ? is happening to ebxml, and where the ? is it going ? I've been following ebxml for a few years now, and just reflecting the comments of others, I too am wondering where ebxml is going ? So far, most of the implementations that I've seen require somebody with a list of degrees and maybe a phd to setup, install and run. That's ok if ebxml is going to be simply an academic pursuit. But in the real business world, things are somewhat different. After the hype of dot coms, business is bustling away, and looking for good tools and new things. Companies are spending on IT again. ebxml history gives the strong impression of being just the part-time hack of some good engineers but in the end, it never worked. There is nothing wrong with that. I'm wondering if there is any 5 year plan for ebxml ? and where to next ? and what about addressing the real needs of the people, how to use it to get customers to pay money for it etc. These things seem a long way off and yet these are the things that are really important to most of the people that I know. Regards David Quoting Rick Marshall <rjm@zenucom.com>: > i haven't been able to get into ebxml yet because i don't think it has > yet really solved the problems of edi. and this is very relevant to the > soap/uddi people. > > the problem with edi is that it is a huge standard encompassing just > about every aspect of electronic trading and can cope with just about > every trading relationship. which means 90% (my guess) of it is not > needed in any particular trading instance. > > so industry trading groups sit down and agree on which parts of the > standard they will use, and how they will use them. typically the > largest purchaser in a trading group will dominate and determine how > these things will be done. > > then everyone else sits down with interpreters and tools and makes sure > they can interpret the necessary bits correctly. > > as an aside, there's a lot of redundancy in many of the message formats too. > > it also forces everyone to learn how to deal at the most complex level..... > > i have yet to see any evidence that ebxml has made this simpler, or > indeed can make it simpler. i can't see how it reduces the trade group > needs to negotiate the semantics of the messages, the specific use of > different terms. and now before you can even start to interpret messages > you need to fully describe your business model. > > i reckon the horse has become a camel, and like the camel now has it's > own evolutionary path. > > the good news is that it takes so long for multi-billion dollar trading > groups to move core technologies i'll probably retire before i have to > face the reality of this one. > > rick > > bry@itnisk.com wrote: > > > Whenever one examines one of the ebxml specs or reads an article on the > subject > > there is likely to be a reference to how edi had problems with being > accepted > >because it was too complex, but luckily ebxml, being based on xml, solves > all > >this. A very suspect class of assertion it seems like to me. I'm wondering > if > >anyone who has familiarity with these technologies can clarify exactly how > and > >in what ways ebxml reduces the complexity of edi. > > > >Basically my understanding is that ebxml just wrapped the edi model in xml, > so I > >have a hard time seeing how it could be simpler. > > > >Also am wondering about CPAs in Ebxml, it strikes me that this process > could > >actually be somewhat onerous, does anyone know of any case studies etc. on > >problems with making CPAs between two companies? > > > > > > > > > >----------------------------------------------------------------- > >The xml-dev list is sponsored by XML.org <http://www.xml.org>, an > >initiative of OASIS <http://www.oasis-open.org> > > > >The list archives are at http://lists.xml.org/archives/xml-dev/ > > > >To subscribe or unsubscribe from this list use the subscription > >manager: <http://www.oasis-open.org/mlmanage/index.php> > > > > > > > > ------------------------------------------------------- ----------------------------------------------------------------- The xml-dev list is sponsored by XML.org <http://www.xml.org>, an initiative of OASIS <http://www.oasis-open.org> The list archives are at http://lists.xml.org/archives/xml-dev/ To subscribe or unsubscribe from this list use the subscription manager: <http://www.oasis-open.org/mlmanage/index.php> ----- End forwarded message ----- ------------------------------------------------------- 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>>