So we need to agree on an "architecture" and decide where the "sweet spots" are to define standards
-
i.e. you do not agree on standards but do try to agree (or guess) what entities will have standards defined for them in the future
|
So assume that we are building education portals in terms of "Distributed Educational Objects" -- this is not really an assumption but a statement as to "language used"
|
Then standards define interfaces to objects (methods and properties)
|
XML is useful as a flexible way of specifying object interfaces in a convenient user readable way supported by growing number of tools
-
Internet Explorer 5 renders XML
-
Many Java libraries for processing XML
|