Todd,

I'm not sure if you're participating in the ebXML Initiative or not.
However, I believe the concept you describe below is a key part of the
architecture and registry/repository project teams' focus, and perhaps also
part of the core components project team. If you are not involved with this
initiative, why not jump into the pool with one or all three of these
project teams and present your concepts and recommendations. The ebXML
Initiative is open for participation by any one who wants to contribute.

Rachel Foerster
ebXML Initiative
Marketing, Awareness & Education Project Team Lead

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Todd Boyle
> Sent: Thursday, February 24, 2000 6:40 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Article: Future of XML and EDI?
>
>
> Kurt Kanaskie said Thursday, February 24, 2000 2:00 PM
> [snip]
> > To address your issue regarding different DTDs, our hope is
> to use an
> > industry standard set of DTDs. Right now we are using OAG,
> but we are also
> > looking at RosettaNet. We started when RosettaNet was just
> marketing hype.
> > So in an ideal world there would be just one Purchase Order
> DTD. We both
> > know this won't happen for a long time if at all. To date
> we have not
> > addressed the issue of handling different DTDs for the same
> concept (i.e.
> > PurchaseOrder). The reason being is that we are developing
> the interfaces
> > with our partners. We have not exposed an Ecommerce portal
> to the world
> > which accepts any old XML message. ....
>
> Could I interject with some small business perspectives?
>
> SMEs will likely conduct an increasing range of business
> (buying, selling,
> paying, receiving, collaboration, payroll, etc) by logging
> into dotcoms,
> banks and other hosts on the web.
>
> They will have datasets on more than one provider.  They will
> still run
> general ledgers to maintain control totals, to produce P&L and to file
> their taxes on the combined business transactions.
>
> SMEs will leave the detail on the hosts for two reasons.  The
> hosts won't
> release it, and the SME won't have a need or a capability to
> store replicas
> of it anyway.  Leaving detail in the subsystem is best
> practice anyway.
>
> The model that will emerge is obviously a general ledger,
> with the total
> of the business from "Subledgers" posted to the master GL in
> summary entries.
>
> It will be highly beneficial if ebXML takes up the requirement for a
> general ledger schema that is usable across a broad
> horizontal spectrum
> of SMEs.  OAGIS 6.2 is very good --POST_Journal.dtd and
> associated confirmation
> and chart of accounts apparatus are very close to what's
> needed for any
> given dotcom to transmit summary general journal postings to
> the root ledger
> of the SME.
>
> It will be important to consider the wild west environment of
> small business
> dotcoms -- the SME is not connected to a trusted B2B partner,
> in a VPN or
> anything of that nature.  The incoming XML message has to be
> something that
> can be examined with tools before accepting and posting to
> the primary
> ledger --and this has to be something that doesn't require a computer
> engineer to be comfortable with.
>
> At the end of the day, the metaphor of subledgers and ledgers
> will permit
> SMEs to choose from best of breed providers of vertical market or
> horizontal services functionality.  Millions of accountants
> already understand
> subledgers and systems of control totals.  General Ledger
> schema will permit
> multi-level consolidations of arbitrary complexity.  Nobody
> is going to
> invent a better "technique" than financial consolidation-- after a few
> years of experience the DotCOms will converge around the
> subledger and the
> consolidation metaphor.
>
> A well-designed XML schema for general ledger will enable
> free competition
> in the DOtComs' services as well as the accounting software
> market.  As you
> know SMEs have generally been forced to choose among
> integrated midrange
> software packages for all their business automation and
> accounting needs,
> due to the impossibility of mixing best of breed applications.  DO you
> see how important the XML Schema for General Ledger will be?
>
> TOdd Boyle CPA Kirkland WA
>
>
> ==========================================
> XML/EDI Group members-only discussion list
> Homepage =  http://www.xmledi.com
>
> Brought to you by: Online Technologies Corporation
>                   Home of BizServe - www.bizserve.com
>
> TO UNSUBSCRIBE: Send email to <[EMAIL PROTECTED]>
>                Leave the subject blank, and
>                In the body of the message, enter ONLY: unsubscribe
>
> Questions/requests should be sent to: [EMAIL PROTECTED]
> To join the XML/EDI Group complete the form located at:
> http://www.geocities.com/WallStreet/Floor/5815/mail1.htm
>
>


==========================================
XML/EDI Group members-only discussion list
Homepage =  http://www.xmledi.com

Brought to you by: Online Technologies Corporation
                  Home of BizServe - www.bizserve.com

TO UNSUBSCRIBE: Send email to <[EMAIL PROTECTED]>
               Leave the subject blank, and
               In the body of the message, enter ONLY: unsubscribe

Questions/requests should be sent to: [EMAIL PROTECTED]
To join the XML/EDI Group complete the form located at:
http://www.geocities.com/WallStreet/Floor/5815/mail1.htm

Reply via email to