ebXML   masters by research in Computer Science  by Sacha Schlegel
   http://www.schlegel.li/ebXML/index.html    is the homepage of this project.

 M E E T I N G
 
m e e t i n g . h e a d e r  
  
date:    July 14th, 2003
week:    29
report:    x out of y
location:    School of Computing at Curtin University
Building 314, Level 4 Meeting room Don Reid
person:    Don Reid, supervisor
Sacha Schlegel, student (2967)
 
m e e t i n g . a c t i v i t i e s  
  
  • Table of contents for thesis
  • Main points of various chapters
  • Timetable for thesis
  • PLUG presentation, August 12th, 2003 about ebXML
 
m e e t i n g . n o t e s  
Don suggested to write more about standards in general. who was behind edi who is behind ebxml.
Don thinks that some history background gives context to ebXML as such. Get a book on it ... EDI and Open Systems Interxxx (OSI), then ANSI (American National Standards Institute?). Problems of ISO lots of parties ... issues are becoming political. Specifciations almost unimplementable and very complex. ISO sells!! standards from their site where as Internet standards got given away for free and source code was floating around the net.
Does EDI have agreements (ala CPA). How do they differ to ebXML CPAs?
Think about examiners. Need at least masters (PHD prefered) qualification.
Think about audience of final thesis. Computer Science vs Business people. CS dont like business models and blah blah whereas business people dont want to dig into complicated algorithms. - Might be rather business like examiners for this project.
basic outline
Methodology/Data/Conclusion
reading spec / building model / implementing (with scope in methodology defining what is impl and what isnt) / look at output.
  • First anaylsis
    Study of the specifications
  • Algorithm
    - the implementation
    algorithm details.
    algorithm problems ( xml referencing, > 1 CPA, CPP overwriting etc)
  • After analysis
    preformance of algorithm, test cases, size of testcases, validity of output etc.
  
  
  
  
  
 
m e e t i n g . t o . d o . l i s t  
Maybe remove methodology out of introduction.
Add 2.2.2 specific standard groups. previous edi then new push by ebxml group. introduce different subgroups for different ebXML specifications???. Then in later chapters refer to the works of these subgroups.
  
  
  
  


© Sacha Schlegel@2003!