<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.5726" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>From Roland> </FONT>... agree on an XML
transport layer and ...</DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Exactly my thoughts when all this came out into the
open. Most (secondary) schools have most programs they need to operate the
school's admin. If our place is anything to go by, the single biggest
inefficiency is the lack of interoperabilty between the various packages.When
the new report format was introduced and a contract awarded to produce QuickVic,
someone managed to cobble together an XML specification that allows qucik, easy
transfer of data between CASES and QuickVic (MarkBook). It seems to me that
creating an EducXML and then insisting that all vendors create import/export
functions that speak EducXML would be a heck of a lot cheaper, free up a lot of
time for users, and have a greater chance of success than inventing a whole new,
all singing, all dancing wheel.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Regards</FONT></DIV>
<DIV><FONT face=Arial size=2>Robert T-A</FONT></DIV>
<DIV><FONT face=Arial size=2>Brighton SC</FONT></DIV></BODY></HTML>