Computable.nl
  • Thema’s
    • Carrière
    • Innovatie & Transformatie
    • Cloud & Infrastructuur
    • Data & AI
    • Governance & Privacy
    • Security & Awareness
    • Software & Development
    • Werkplek & Beheer
  • Sectoren
    • Channel
    • Financiële dienstverlening
    • Logistiek
    • Onderwijs
    • Overheid
    • Zorg
  • Awards
    • Overzicht
    • Nieuws
    • Winnaars
    • Partner worden
  • Vacatures
    • Vacatures bekijken
    • Vacatures plaatsen
  • Bedrijven
    • Profielen
    • Producten & Diensten
  • Kennisbank
  • Magazine
  • Nieuwsbrief

XML related standards (2)

09 mei 2002 - 22:004 minuten leestijdOpinieCloud & Infrastructuur
Martin Healey
Martin Healey

The core frameworks for building Web applications based on XML as represented by BizTalk and ebXML are now stable and complete enough to build new e-commerce applications on. The usual word of caution is of course still worth listening to; these are new technologies and there will be a lot of further developments over the next few years. Thus it is wise to tackle relatively straightforward applications in these early years. Because these technologies have such a high profile, there is a tendency to forget that they are so new!

The fight to control the so-called Web Services market is probably the hottest topic in the IT industry today (apart from the financial problems that is). The major players, Microsoft, IBM, BEA and Oracle have all got significant offerings, all based on XML. The earlier products used to be called Enterprise Application Integration systems, using a variety of technologies, but EAI based on XML related standards is now commonly referred to as Web Services, yet another lot of middleware in fact. While there is a lot of posturing and in- fighting, a lot of progress has been made towards compatibility, largely because there is commercial pressure for systems to work together. Thus each vendor will put forward a solution to a particular problem, invariably generating a counter proposition from one or more of the opposition, but for once in the IT industry they most times get together and compromise on a standard solution, usually in cooperation with W3C, OMG and other reputable bodies.
XML itself is one such standard, in this case a W3C standard, but the others of note in Web Services are SOAP, WSDL, UDDI and XHTML. The later is there to provide a path from HTML to XML. SOAP (Simple Object Access Protocol) is a remote procedure call, tailored to suit the message-based concepts of the Web, simpler than the CORBA standards. SOAP protocols include an envelope which describes the message and how to process it, an optional header to extend functions and the XML message in the body. The transport protocol is normally HTTP, which means that it can pass through firewalls (is this a good or a bad thing?), but it means that it will work between disparate systems.
WSDL (Web Services Definition Language) is an XML language devised for use with SOAP and UDDI to describe what Web services are available in a system.
UDDI (Universal Description, Discovery and Integration) is that part of the Web Services framework , a completely open technical one, which allows enterprises globally to locate Web services, to define how they work together and to specify how information can be shared.
One benefit of these open standards is that older EAI products can evolve and Open Source products are available to offer an option to the bigger suppliers. It is also a blessing to the software tool vendors, again resulting in a wider choice of tools.
Given that there is now considerable progress in XML languages to support the lower-level core services and the middleware mentioned above, it is equally good to note that there has been a very rapid development of industry specific higher-level, or "vertical" schemas. These have developed quickly simply because the supporting standards have matured in time. It is a good example of how cooperation on standards accelerates related developments and benefits everyone. Each sector of industry is developing their own relevant XML schemas. This has happened in the past with EDI but little else in IT. What is happening now is far more advanced than EDI, but that is still the best source of experience in defining needs.
The chemical, pharmaceutical, automotive, retail, aerospace, petroleum, and many other industries have long benefited from global standards, which they are extending into XML systems. Architecture, construction, finance, government and news media have all established committees to define relevant XML schema. Human resources is another industry in need of standards. Those industries mentioned first have a big advantage in that they have more mature and comprehensive committees in place, while others have to go through the in-fighting before a consensus will be reached. But it is happening. It is always easier if there is a dominant force involved, but this also leads to unfortunate diversification; can Ford, General Motors, Toyota, etc. agree on a common standard or will they exploit their power over their own supply chain?
Finally note that while there are probably too many vertical standards, this is not a sign of fragmentation and impending collapse, because they are based on solid lower-level standards.

Meer over

E-commerceOpensource

Deel

    Inschrijven nieuwsbrief Computable

    Door te klikken op inschrijven geef je toestemming aan Jaarbeurs B.V. om je naam en e-mailadres te verwerken voor het verzenden van een of meer mailings namens Computable. Je kunt je toestemming te allen tijde intrekken via de af­meld­func­tie in de nieuwsbrief.
    Wil je weten hoe Jaarbeurs B.V. omgaat met jouw per­soons­ge­ge­vens? Klik dan hier voor ons privacy statement.

    Whitepapers

    Computable.nl

    Kies de juiste virtualisatie-aanpak

    Vergelijk drie krachtige open source-oplossingen: Proxmox, Kubernetes en OpenStack

    Computable.nl

    Beveiliging begint bij de Server

    Is serverhardware de blinde vlek in het securitybeleid? Waarom lifecycle-denken cruciaal is voor IT-security

    Computable.nl

    Bouw de AI-organisatie niet op los zand

    Wat is de afweging tussen zelf bouwen of het benutten van cloud?

    Geef een reactie Reactie annuleren

    Je moet ingelogd zijn op om een reactie te plaatsen.

    Populaire berichten

    Meer artikelen

    Uitgelicht

    Partnerartikel
    AdvertorialSecurity & Awareness

    Cybersec Netherlands 2025 – Programma...

    Keynotes over cloud, AI en geopolitiek: het programma van Cybersec Netherlands raakt de kern van digitale weerbaarheid

    Meer persberichten

    Meer lezen

    OpinieSecurity & Awareness

    Cloudsecurity als fundament voor groei

    ActueelCloud & Infrastructuur

    Eurofiber en Bright Access versterken glasvezelnetwerk op bedrijventerreinen

    Krimp groei
    ActueelSecurity & Awareness

    Kort: Fintech snel minder populair, Centric neemt Groupcard niet over (en meer)

    Joost Smit
    AchtergrondCloud & Infrastructuur

    Op deze vier paarden zet Google Cloud in

    AchtergrondCarrière

    Willem van der Poel – Een avonturier in de techniek

    ActueelCloud & Infrastructuur

    NLnet en CWI testen eerste openbare Scion-verbinding in Nederland

    ...

    Footer

    Direct naar

    • Carrièretests
    • Kennisbank
    • Planning
    • Computable Awards
    • Magazine
    • Abonneren Magazine
    • Cybersec e-Magazine
    • Topics
    • – Phishing
    • – Ransomware

    Producten

    • Adverteren en meer…
    • Jouw Producten en Bedrijfsprofiel
    • Whitepapers & Leads
    • Vacatures & Employer Branding
    • Persberichten

    Contact

    • Colofon
    • Computable en de AVG
    • Service & contact
    • Inschrijven nieuwsbrief
    • Inlog

    Social

    • Facebook
    • X
    • LinkedIn
    • YouTube
    • Instagram
    © 2025 Jaarbeurs
    • Disclaimer
    • Gebruikersvoorwaarden
    • Privacy statement
    Computable.nl is een product van Jaarbeurs