Post #41,922
6/11/02 9:33:05 AM
6/11/02 10:37:28 AM
|
Re: XML is ... Some of the definitions
(I was hoping it wouldn't come to this)
a tag based meta-language for creating other languages. The use of a DTD or Schema
allows derived languages to be defined. The DTD or Schema is used to define the TAGs
that are permitted in the sub-language. XHTML is a classic implementation of an XML
derive language. What is so great about XHTML - it can be modified (for different
display devices) in flight, by XSL (another XML derived technology).
XML allows the creation of self describing data. Self describing data offers significant
benefit in being used to pass documents and messages among otherwise incompatible
systems.
XML Tags allow XML <ELEMENTS> to be better identified when a document is
searched for its content. This is near to impossible with EDI documents in their
transmitted form as it is with messages passed between CORBA, DCOM & RMI.
The concept (like a cargo container) is incredibly simple but its simplicity doesn't
mean the impact will not be dramatic (as was containerization). XML is the same.
What is driving 'needs' for XML. It is the need for a simple but powerful mechanisim
that can be integrated into existing systems (EAI & Legacy) but can also support
entirely new concepts like Web Services, ebXML. XML Query etc: etc: etc: etc:.
XML is human readable but XML derivative standards support the ability to handle
encryption. XML can support encryption of <ELEMENTS> and it is entirely
possible for each <ELEMENT> to use a different encryption approach. So, one
might ask, what is the big about being human readable ? - this ability opens the
pandora's box of discovery !. Discovery of content, one of the greatest inhibitors in
analysing and exploiting data in information systems. Yes, there is a price, (lack
of data compression) but already hardware vendors are developing intelligent
routers capable of compressing XML in transit without losing its 'visibility'.
XML has derivative standards that support non-repudiation. An essential
ingredient for electronic document exchange.
XML has a concept (Global DOCID) that supports a unique document ID for
each any every document that chooses to employ it. This offers significant
benefits in managing XML based documents that travel globally. And that
need to be traced to their origins.
Web Services is a concept derived from XML and thus harnesses the
significant benefits already recognised in the technology. Web Services
allows the concept of 'COLLABORATIVE COMPUTING' which is the next logical
step in the evolution of computing use. In essence it is computung that spans
computers and is technology agnostic. Web Services does this. CORBA DCOM
& RMI (as methods of linking computing) arent & can't.
Web Services can do one other extremely important trick that CORBA, DCOM &
RMI can't. Becaues of XML and WSDL, They can be bound to in real time. The
other middleware technologies have to be bound together at compile time (this
seems to be so lost on many people who criticze the Web Service concept).
This 'trick' gives Web Services its magic and like XML human readability, opens
a pandora's box of potential that proprietary & non web scalable technologies
(CORBA etc:) can never rise to.
Web Services can be said to be the forunner of a 'plug and play' solutions
capability. This is where the benefits can be passed to business. If businesses
can create solutions by real-time & dynamic binding of services using business
flow languages then the world of business & IT has move substantially forward.
IN DEFENCE of CORBA etc:
But there are applications where proprietary technologies like CORBA etc: offer
value that Web Services can't (yet).
Some today say the the next big Wave will be 'GRID' computing and for that to
make sense, Web Services need to proceed as it will, down its evolutionary path.
No doubt some people have no view whatsoever of computer evolution just as
some shippers might never have grasped the benefits of containerization.
Brings to mind the famous British story of when King Canute (11th century)
sought to teach some of his aides how not even the King of Scandanavia and
England could command the tide to turn back. Darwin taught us some
powerful principles in his oragins of the species.
XML standards are driven by the W3C (WWW Consortium)
[link|http://www.w3c.org/|W3c web site]
Its a damned shame the above web site is so academic and boring if it
wasn't them maybe many more people would read the details.
W3C has defined a \ufffdfamily\ufffd of XML related technologies ... (just a few here)
XML, XHTML, DTD, XML Schema,
XML Query, XSL, XSLT, XML Path,
XLL, etc:, etc:, etc:.
XSL is a topic in its own right.
All and more can be read at the link provided.
Cheers - Doug Marker
#1 added more detail
Edited by dmarker2
June 11, 2002, 10:21:57 AM EDT
Re: XML is ... Some of the definitions
(I was hoping it wouldn't come to this)
a tag based meta-language for creating other languages. The use of a DTD or Schema allows derived languages
to be defined. The DTD or Schema is used to define the TAGs that are permitted in the sub-language.
XML allows the creation of self describing data. Self describing data offers significant benefit in being used to pass documents and messages among otherwise incompatible systems.
XML Tags allow XML <ELEMENTS> to be better identified when a document is searched for its content. This is near to impossible with EDI documents in their transmitted form.
The concept (like a cargo container) is incredibly simple but its simplicity doesn't mean the impact will not be dramatic (as was containerization).
What is driving the 'need' for XML. It is the need for a simple but powerful mechanisim that can be integrated into existing systems)EAI & Legacy) but can also support entirely new concepts like ebXML. XML Query etc:.
XML is human readable but XML derivative standards support the ability to handle encryption. XML can support encryption of <ELEMENTS> and it is entirely possible for each <ELEMENT> to use a different encryption approach.
XML has derivative standards that support non-repudiation.
XML has a concept (Global DOCID) that supports a unique document ID for each any every document that chooses to employ it. This offers significant benefits in managing XML based documents that travel globally.
Web Services is a concept derived from XML and thus harnesses the significant benefits already recognised in the technology. Web Services allows the concept of 'COLLABORATIVE COMPUTING' which is the next logical step in the evolution of computing use.
Many today say the the next big Wave will be 'GRID' computing and for that to make sense, Web Services need to proceed as it will, down its evolutionary path. No doubt some people have no view whatsoever of computer evolution just as some shippers might never have grasped the benefits of containerization.
Brings to mind the famous British story of when King Canute (11th century) sought to teach some of his aides how not even the King of Scandanavia and England could command the tide to turn back. Darwin taught us some powerful principles in his oragins of the species.
Edited by dmarker2
June 11, 2002, 10:25:52 AM EDT
Re: XML is ... Some of the definitions
(I was hoping it wouldn't come to this)
a tag based meta-language for creating other languages. The use of a DTD or Schema allows
derived languages to be defined. The DTD or Schema is used to define the TAGs that are
permitted in the sub-language. XHTML is a classic implementation of an XML derive language.
XML allows the creation of self describing data. Self describing data offers significant benefit
in being used to pass documents and messages among otherwise incompatible systems.
XML Tags allow XML <ELEMENTS> to be better identified when a document is searched
for its content. This is near to impossible with EDI documents in their transmitted form as
it is with messages passed between CORBA, DCOM & RMI.
The concept (like a cargo container) is incredibly simple but its simplicity doesn't mean the
impact will not be dramatic (as was containerization). XML is the same.
What is driving 'needs' for XML. It is the need for a simple but powerful mechanisim
that can be integrated into existing systems (EAI & Legacy) but can also support entirely
new concepts like Web Services, ebXML. XML Query etc: etc: etc: etc:.
XML is human readable but XML derivative standards support the ability to handle encryption.
XML can support encryption of <ELEMENTS> and it is entirely possible for each
<ELEMENT> to use a different encryption approach. So, one might ask, what is the big
about being human readable ? - this ability opens the pandora's box of discovery !. Discovery
of content, one of the greatest inhibitors in analysing and exploiting data in information
systems. Yes, there is a price, (lack of data compression) but already hardware vendors
are developing intelligent routers capable of compressing XML in transit without losing
its 'visibility'.
XML has derivative standards that support non-repudiation. An essential ingredient for
electronic document exchange.
XML has a concept (Global DOCID) that supports a unique document ID for each any
every document that chooses to employ it. This offers significant benefits in managing
XML based documents that travel globally. And that need to be traced to their origins.
Web Services is a concept derived from XML and thus harnesses the significant benefits
already recognised in the technology. Web Services allows the concept of
'COLLABORATIVE COMPUTING' which is the next logical step in the evolution of
computing use. In essence it is computung that spans computers and is technology
agnostic. Web Services does this. CORBA DCOM & RMI (as methods of linking
computing) arent & can't.
Web Services can do one other extremely important trick that CORBA, DCOM &
RMI can't. Becaues of XML and WSDL, They can be bound to in real time. The
other middleware technologies have to be bound together at compile time (this
seems to be so lost on many people who criticze the Web Service concept).
This 'trick' gives Web Services its magic and like XML human readability, opens
a pandora's box of potential that proprietary & non web scalable technologies
(CORBA etc:) can never rise to.
But there are applications where proprietary technologies like CORBA etc: offer
value that Web Services can't (yet).
Some today say the the next big Wave will be 'GRID' computing and for that to
make sense, Web Services need to proceed as it will, down its evolutionary path.
No doubt some people have no view whatsoever of computer evolution just as
some shippers might never have grasped the benefits of containerization.
Brings to mind the famous British story of when King Canute (11th century)
sought to teach some of his aides how not even the King of Scandanavia and
England could command the tide to turn back. Darwin taught us some
powerful principles in his oragins of the species.
#1 added more detail
Edited by dmarker2
June 11, 2002, 10:37:28 AM EDT
Re: XML is ... Some of the definitions
(I was hoping it wouldn't come to this)
a tag based meta-language for creating other languages. The use of a DTD or Schema allows
derived languages to be defined. The DTD or Schema is used to define the TAGs that are
permitted in the sub-language. XHTML is a classic implementation of an XML derive language.
XML allows the creation of self describing data. Self describing data offers significant benefit
in being used to pass documents and messages among otherwise incompatible systems.
XML Tags allow XML <ELEMENTS> to be better identified when a document is searched
for its content. This is near to impossible with EDI documents in their transmitted form as
it is with messages passed between CORBA, DCOM & RMI.
The concept (like a cargo container) is incredibly simple but its simplicity doesn't mean the
impact will not be dramatic (as was containerization). XML is the same.
What is driving 'needs' for XML. It is the need for a simple but powerful mechanisim
that can be integrated into existing systems (EAI & Legacy) but can also support entirely
new concepts like Web Services, ebXML. XML Query etc: etc: etc: etc:.
XML is human readable but XML derivative standards support the ability to handle encryption.
XML can support encryption of <ELEMENTS> and it is entirely possible for each
<ELEMENT> to use a different encryption approach. So, one might ask, what is the big
about being human readable ? - this ability opens the pandora's box of discovery !. Discovery
of content, one of the greatest inhibitors in analysing and exploiting data in information
systems. Yes, there is a price, (lack of data compression) but already hardware vendors
are developing intelligent routers capable of compressing XML in transit without losing
its 'visibility'.
XML has derivative standards that support non-repudiation. An essential ingredient for
electronic document exchange.
XML has a concept (Global DOCID) that supports a unique document ID for each any
every document that chooses to employ it. This offers significant benefits in managing
XML based documents that travel globally. And that need to be traced to their origins.
Web Services is a concept derived from XML and thus harnesses the significant benefits
already recognised in the technology. Web Services allows the concept of
'COLLABORATIVE COMPUTING' which is the next logical step in the evolution of
computing use. In essence it is computung that spans computers and is technology
agnostic. Web Services does this. CORBA DCOM & RMI (as methods of linking
computing) arent & can't.
Web Services can do one other extremely important trick that CORBA, DCOM &
RMI can't. Becaues of XML and WSDL, They can be bound to in real time. The
other middleware technologies have to be bound together at compile time (this
seems to be so lost on many people who criticze the Web Service concept).
This 'trick' gives Web Services its magic and like XML human readability, opens
a pandora's box of potential that proprietary & non web scalable technologies
(CORBA etc:) can never rise to.
But there are applications where proprietary technologies like CORBA etc: offer
value that Web Services can't (yet).
Some today say the the next big Wave will be 'GRID' computing and for that to
make sense, Web Services need to proceed as it will, down its evolutionary path.
No doubt some people have no view whatsoever of computer evolution just as
some shippers might never have grasped the benefits of containerization.
Brings to mind the famous British story of when King Canute (11th century)
sought to teach some of his aides how not even the King of Scandanavia and
England could command the tide to turn back. Darwin taught us some
powerful principles in his oragins of the species.
XML standards are driven by the W3C (WWW Consortium)
W3c web site
Its a damned shame the above web site is so academic and boring it it
wasn't them maybe more people would read the details.
W3C has defined a family of XML related technologies ...
XML, XHTML, DTD, XML Schema,
XML Query, XSL, XSLT, XML Path,
XLL, etc:, etc:, etc:.
All and more can be read at the link provided.
Cheers - Doug Marker
#1 added more detail
|
Post #42,269
6/13/02 5:29:11 PM
6/14/02 6:11:40 PM
|
Not so analogous to containerization, then.
Doug describes XML: a tag based meta-language [...] allows the creation of self describing data. So "XML" per se doesn't mean ready-made standardized "containers" (they're in the DTD/Schema), but more of a *container-construction kit*. If y [ou l]ook at it that way, are you still so sure it will "revolutionize" IT like containerization did shipping? Do you believe shipping would have been commoditized if there had only been a standard for *how* to build containers, but no actual standard for the resulting containers themselves? (Needless to say, since you already inferred it from my tone above, I don't think so.)
[EDIT: Typo; "you look" inadvertently contracted to "yook".] Christian R. Conrad
Of course, who am I to point fingers? I'm in the "Information Technology" business, prima facia evidence that there's bats in the bell tower. -- [link|http://z.iwethey.org/forums/render/content/show?contentid=27764|Andrew Grygus]
Edited by CRConrad
June 14, 2002, 06:11:40 PM EDT
|
