APPENDIX A EVENT EXTRACTION RESULTS

Size: px

Start display at page:

Download "APPENDIX A EVENT EXTRACTION RESULTS"

Roy O’Brien’
7 years ago
Views:

1 APPENDIX A EVENT EXTRACTION RESULTS Case studies from different domains were taken and event list generated by the event extraction module was compared with event list made manually by experts in order to optimize our proposed rules so that they can be applied to many domains. The statistics of experiments show that this module is able to extract almost 80% accurate events that are matching in both the lists and around 4% to 12% are not extracted by this tool completely. This may be due to different perspectives of experts while analyzing events. Such events can be left on analyst to refine them and take decision about them to be relevant events. Table A.1, gives statistics on various case studies that were solved and Figure A.1 shows the results using a bar graph. Table A.1: Result of Event Extraction on Various Case Studies S.No Related domain NE E NE T NCE T Coverage Metric(%) Coverage Accuracy Metric(%) E-Business Luggage control Software Blood-bank Library Avionics System Air Port Management System Mall Management University Management System 9. LIC Management System Fighter Plane Control System KIT Management System

2 Extraction Results Values NEE NET NCET Coverage Metric(%) Coverage Accuracy Metric(%) 20 0 E-Business Luggage control Software Blood-bank Library Avionics System Air Port Management System Mall Management University Management System Case Studies LIC Management System Fighter Plane Control System KIT Management System Online Auction System Figure A.1: Bar Chart of Results of Event Extraction 174

3 APPENDIX B XML SCHEMA FOR EVENT TEMPLATE VALIDATION Event Formalization and Validation module document each event from the final list of events using Event Templates and store the output as validated XML file. For validating the event template XML file, an XML schema is designed that reads the contents of XML file and generate a validated XML File. XML schema written to validate the generated XML file of event template is described below: <?xml version= 1.0 encoding= UTF-8?> <xsd:schema xmlns:xsd= targetnamespace= xmlns:et= <xsd:element name= eventtemplates > <xsd:sequence> <xsd:element ref= event minoccurs= 1 maxoccurs= unbounded /> </xsd:sequence> <xsd:element name= event <xsd:attribute name= eventid use= required type= xsd:id /> <xsd:unique name= uniqueeventkey > <xsd:selector xpath= et:event /> <xsd:field /> </xsd:unique> <xsd:key name= eventkey > <xsd:selector xpath= et:event /> <xsd:field /> </xsd:key> <xsd:sequence> <xsd:element name= eventname type= xsd:string /> 175

4 <xsd:element name= description type= xsd:string /> <xsd:element name= timestamp type= xsd:time minoccurs= 0 /> //Causative events have already occurred in the system. It will be a string containing // //compound event expression involving operators. One can process string to extract Id s. <xsd:element name= causative_events type= xsd:string /> <xsd:keyref name= eventref ref= eventkey > <xsd:selector xpath= et:causative_event /> <xsd:field /> </xsd:keyref> <xsd:element name= initiator minoccurs= 0 maxoccurs= unbounded > <xsd:attribute name= iname use= required type= string /> <xsd:attribute name= icount use= required type= integer /> <xsd:element name= facilitator minoccurs= 0 maxoccurs= unbounded > <xsd:attribute name= fname use= required type= string /> <xsd:attribute name= fcount use= required type= integer /> <xsd:element name= affector minoccurs= 0 maxoccurs= unbounded > <xsd:attribute name= aname use= required type= string /> <xsd:attribute name= acount use= required type= integer /> // It is a set to events that have to occur after the current event. Multiple lines are taken as //input each corresponding to an event description. For each new event an id is generated //automatically by the system. <xsd:element name= triggervector minoccurs= 0 maxoccurs= unbounded > <xsd:attribute name= teventdescription use= required type= string /> <xsd:keyref name= teventref ref= eventkey > 176

5 <xsd:selector xpath= et:triggervector /> <xsd:field /> </xsd:keyref> <xsd:element name= input minoccurs= 1 maxoccurs= unbounded > <xsd:attribute name= source use= required type= string /> <xsd:attribute name= name use= required type= string /> <xsd:attribute name= value use= required type= integer /> <xsd:element name= changes minoccurs= 1 maxoccurs= unbounded > <xsd:attribute name= mname use= required type= string /> <xsd:attribute name= mtype use= required type= string /> <xsd:attribute name= definedin use= required type= string /> <xs:element name="change "> <xs:complextype> <xs:sequence> <xs:element name="ctype" type="xs:string"/> <xs:element name="inputs" type="xs:string"/> </xs:sequence> </xs:complextype> </xs:element> <xs:element name="change-event " type= change minoccurs= 0 maxoccurs= unbounded /> </xsd:sequence> </xsd:complectype> 177

+ <xs:element name="productsubtype" type="xs:string" minoccurs="0"/>

+ <xs:element name=productsubtype type=xs:string minoccurs=0/> otcd.ntf.001.01.auctiondetail.. otcd.ntf.001.01.auctionresult - + otcd.ntf.001.01.automaticterminationsummary