IEEE 1849-2016 en eXtensible Event Stream (XES) for Achieving Interoperability in Event Logs and Event Streams.pdf

《IEEE 1849-2016 en eXtensible Event Stream (XES) for Achieving Interoperability in Event Logs and Event Streams.pdf》由会员分享，可在线阅读，更多相关《IEEE 1849-2016 en eXtensible Event Stream (XES) for Achieving Interoperability in Event Logs and Event Streams.pdf（50页珍藏版）》请在麦多课文档分享上搜索。

1、IEEE Standard for eXtensible Event Stream (XES) for Achieving Interoperability in Event Logs and Event StreamsIEEE Std 1849-2016IEEE Computational Intelligence SocietySponsored by the Standards CommitteeIEEE3 Park AvenueNew York, NY 10016-5997USAIEEE Std 1849-2016IEEE Standard for eXtensible Event S

2、tream (XES) for Achieving Interoperability in Event Logs and Event StreamsSponsor Standards Committee of the IEEE Computational Intelligence SocietyApproved 22 September 2016IEEE-SA Standards BoardAbstract: A grammar for a tag-based language whose aim is to provide designers of information systems w

3、ith a unified and extensible methodology for capturing systems behaviors by means of event logs and event streams is defined in the XES standard. An “XML Schema” describing the structure of an XES event log/stream and a “XML Schema” describing the structure of an extension of such a log/stream are i

4、ncluded in this standard. Moreover, a basic collection of so-called “XES extension” prototypes that provide semantics to certain attributes as recorded in the event log/stream is included in this standard.Keywords: event log, event stream, extensions, IEEE 1849, system behavior , XMLThe Institute of

5、 Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USACopyright 2016 by The Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 11 November 2016. Printed in the United States of America.IEEE is a registered trademark in the U.S. Pate

6、nt fitness for a particular purpose; non-infringement; and quality, accuracy, effectiveness, currency, or completeness of material. In addition, IEEE disclaims any and all conditions relating to: results; and workmanlike effort. IEEE standards documents are supplied “AS IS” and “WITH ALL FAULTS.”Use

7、 of an IEEE standard is wholly voluntary. The existence of an IEEE standard does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to the scope of the IEEE standard. Furthermore, the viewpoint expressed at the time a stand

8、ard is approved and issued is subject to change brought about through developments in the state of the art and comments received from users of the standard.In publishing and making its standards available, IEEE is not suggesting or rendering professional or other services for, or on behalf of, any p

9、erson or entity nor is IEEE undertaking to perform any duty owed by any other person or entity to another. Any person utilizing any IEEE Standards document, should rely upon his or her own independent judgment in the exercise of reasonable care in any given circumstances or, as appropri-ate, seek th

10、e advice of a competent professional in determining the appropriateness of a given IEEE standard.IN NO EVENT SHALL IEEE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO: PROCURE-MENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF U

11、SE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CON-TRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE PUBLICATION, USE OF, OR RELIANCE UPON ANY STANDARD, EVEN IF ADVISED OF THE POSSIBILITY OF S

12、UCH DAMAGE AND REGARDLESS OF WHETHER SUCH DAMAGE WAS FORESEEABLE.4Copyright 2016 IEEE. All rights reserved.TranslationsThe IEEE consensus development process involves the review of documents in English only. In the event that an IEEE standard is translated, only the English version published by IEEE

13、 should be considered the approved IEEE standard.Official statementsA statement, written or oral, that is not processed in accordance with the IEEE-SA Standards Board Operations Manual shall not be considered or inferred to be the official position of IEEE or any of its committees and shall not be c

14、onsidered to be, or be relied upon as, a formal position of IEEE. At lectures, symposia, seminars, or educational courses, an individual presenting information on IEEE standards shall make it clear that his or her views should be considered the personal views of that individual rather than the forma

15、l position of IEEE.Comments on standardsComments for revision of IEEE Standards documents are welcome from any interested party, regardless of membership affiliation with IEEE. However, IEEE does not provide consulting information or advice pertain-ing to IEEE Standards documents. Suggestions for ch

16、anges in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Since IEEE standards represent a consensus of concerned interests, it is important that any responses to comments and questions also receive the concur-rence of a balance of interest

17、s. For this reason, IEEE and the members of its societies and Standards Coordi-nating Committees are not able to provide an instant response to comments or questions except in those cases where the matter has previously been addressed. For the same reason, IEEE does not respond to interpretation req

18、uests. Any person who would like to participate in revisions to an IEEE standard is welcome to join the relevant IEEE working group.Comments on standards should be submitted to the following address:Secretary, IEEE-SA Standards Board445 Hoes LanePiscataway, NJ 08854 USALaws and regulationsUsers of I

19、EEE Standards documents should consult all applicable laws and regulations. Compliance with the provisions of any IEEE Standards document does not imply compliance to any applicable regulatory require-ments. Implementers of the standard are responsible for observing or referring to the applicable re

20、gulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in compliance with applicable laws, and these documents may not be construed as doing so.CopyrightsIEEE draft and approved standards are copyrighted by IEEE under US and international copyrig

21、ht laws. They are made available by IEEE and are adopted for a wide variety of both public and private uses. These include both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the pro-motion of engineering practices and methods. By making these do

22、cuments available for use and adoption by public authorities and private users, IEEE does not waive any rights in copyright to the documents.5Copyright 2016 IEEE. All rights reserved.PhotocopiesSubject to payment of the appropriate fee, IEEE will grant users a limited, non-exclusive license to photo

23、copy portions of any individual standard for company or organizational internal use or individual, non-commercial use only. To arrange for payment of licensing fees, please contact Copyright Clearance Center, Customer Ser-vice, 222 Rosewood Drive, Danvers, MA 01923 USA; +1 978 750 8400. Permission t

24、o photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center.Updating of IEEE Standards documentsUsers of IEEE Standards documents should be aware that these documents may be superseded at any time by the issuance of new ed

25、itions or may be amended from time to time through the issuance of amendments, corri-genda, or errata. An offi cial IEEE document at any point in time consists of the current edition of the document together with any amendments, corrigenda, or errata then in effect.Every IEEE standard is subjected t

26、o review at least every 10 years. When a document is more than 10 years old and has not undergone a revision process, it is reasonable to conclude that its contents, although still of some value, do not wholly refl ect the present state of the art. Users are cautioned to check to determine that they

27、 have the latest edition of any IEEE standard.In order to determine whether a given document is the current edition and whether it has been amended through the issuance of amendments, corrigenda, or errata, visit IEEE Xplore at http:/ieeexplore.ieee.org or contact IEEE at the address listed previous

28、ly. For more information about the IEEE SA or IEEEs standards develop-ment process, visit the IEEE-SA Website at http:/standards.ieee.org.ErrataErrata, if any, for all IEEE standards can be accessed on the IEEE-SA Website at the following URL: http:/standards.ieee.org/fi ndstds/errata/index.html. Us

29、ers are encouraged to check this URL for errata periodically.PatentsAttention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard, no position is taken by the IEEE with respect to the existence

30、or validity of any patent rights in connection therewith. If a patent holder or patent applicant has fi led a statement of assurance via an Accepted Letter of Assurance, then the statement is listed on the IEEE-SA Website at http:/standards.ieee.org/about/sasb/patcom/patents.html. Letters of Assuran

31、ce may indicate whether the Submitter is willing or unwilling to grant licenses under patent rights without compensation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair discrim-ination to applicants desiring to obtain such licenses.Essential P

32、atent Claims may exist for which a Letter of Assurance has not been received. The IEEE is not re-sponsible for identifying Essential Patent Claims for which a license may be required, for conducting inquiries into the legal validity or scope of Patents Claims, or determining whether any licensing te

33、rms or conditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that determination of the valid-ity of any patent rights, and the risk of infringement of such

34、rights, is entirely their own responsibility. Further information may be obtained from the IEEE Standards Association.6Copyright 2016 IEEE. All rights reserved.ParticipantsAt the time this IEEE standard was completed, the XES Working Group had the following membership:Wil van der Aalst, ChairChristi

35、an Gnther, Vice ChairJC BoseJosep CarmonaMarlon DumasFrank van GeffenSukriti GoelAntonella GuzzoRania KhalafRudolf KuhnTeemu LehtoFelix MannhardtMarco MontaliMichael zur MuehlenZbigniew PaszkiewiczHajo ReijersAlexander RinkeMichal RosikAnne RozinatPnina SofferMinseok SongKeith SwensonWalter Vanherle

36、Eric VerbeekLijie WenMoe WynnThe following members of the individual balloting committee voted on this standard. Balloters may have voted for approval, disapproval, or abstention.Giovanni AcamporaMichael BauerJC BoseKeith ChowRandall GrovesChristian GntherAntonella GuzzoWerner HlzlNoriyuki IkeuchiPi

37、otr KarockiAkhil KumarEdward McCallBjrn MolitorTakahide NogayamaZbigniew PaszkiewiczMichal RosikChristopher TurnerWil van der AalstEric VerbeekLijie WenOren YuenWhen the IEEE-SA Standards Board approved this standard on 22 September 2016, it had the following membership:Jean-Philippe Faure, ChairTed

38、 Burse, Vice ChairJohn D. Kulick, Past ChairKonstantinos Karachalios, SecretaryChuck AdamsMasayuki AriyoshiStephen DukesJianbin FanJ. Travis Griffi thGary HoffmanRonald W. HotchkissMichael JanezicJoseph L. Koepfi nger*Hung LingKevin LuAnnette D. ReillyGary RobinsonMehmet UlemaYingli WenHoward Wolfma

39、nDon WrightYu YuanDaidi Zhong*Member Emeritus7Copyright 2016 IEEE. All rights reserved.IntroductionThis introduction is not part of IEEE Std 1849-2016, IEEE Standard for eXtensible Event Stream (XES) for Achieving Interoperability in Event Logs and Event Streams.Event logs contain information on how

40、 processes have evolved in running systems. As more and more systems capture such information, there is a need to be able to transfer this information from these running systems to a site where the information can be analyzed, either automatically by software from the computational intelli-gence fie

41、ld, or manually (at least in part) using such software.This standard addresses this need by defining an eXtensible Event Stream (XES) structure for such event logs.Furthermore, this standard defines the World Wide Web Consortium (W3C) Extensible Markup Language (XML) structure and constraints on the

42、 contents of XML 1.1 documents that can be used to represent XES instances, and a likewise structure (called XESEXT) that can be used to represent so-called extensions to this structure.The purpose of this standard is to allow the generation and analysis of event logs using XML. This standard uses t

43、he W3C XML Schema definition language as the encoding, which allows for interoperability and the exchange of XES XML instances between various systems.8Copyright 2016 IEEE. All rights reserved.Contents1. Overview . 101.1 Scope 101.2 Purpose . 102. Normative references 113. Definitions, abbreviations

44、, and acronyms . 113.1 Definitions 113.2 Abbreviations and acronyms 114. XES metadata structure . 124.1 Hierarchical components 124.2 Attribute component . 124.3 Global attributes . 134.4 Classifiers . 144.5 Extensions 155. XES XML serialization . 155.1 Log element 155.2 Trace element . 185.3 Event

45、element . 185.4 Attribute element 195.5 Extension element 195.6 Global element . 205.7 Classifier element . 206. XESEXT XML Serialization . 216.1 XES Extension element 216.2 Log element 216.3 Trace element . 236.4 Event element . 236.5 Meta element 236.6 Attribute element 246.7 Alias 247. XES standa

46、rd extensions . 247.1 Concept extension 257.2 Lifecycle extension. 257.3 Organizational extension 287.4 Time extension . 297.5 Semantic extension . 297.6 ID extension . 307.7 Cost extension 308. XES Conformance 318.1 Strictly conforming XES instances . 318.2 Conforming XES instances 319. XESEXT Conf

47、ormance . 329.1 Strictly conforming XESEXT instances . 329.2 Conforming XESEXT instances . 32Annex A (informative) History of XES 339Copyright 2016 IEEE. All rights reserved.Annex B (informative) Current status of XES 34Annex C (informative) XES support 35Annex D (normative) XES Schema definition (X

48、SD) 39Annex E (normative) XESEXT Schema definition (XSD) . 43Annex F (informative) XESEXT Example . 45Annex G (informative) Bibliography . 4710Copyright 2016 IEEE. All rights reserved.1. Overview1.1 ScopeThis standard defines World Wide Web Consortium (W3C) Extensible Markup Language (XML) structure

49、 and constraints on the contents of XML 1.1 documents that can be used to represent extensible event stream (XES) instances.1A XES instance corresponds to a file-based event log or a formatted event stream that can be used to transfer event-driven data in a unified and extensible manner from a first site to a second site. Typically, the first site will be the site generating this event-driven data (for example, workflow systems, case handling systems, procurement systems, devices like wafer steppers and X-ray machines, and hospitals) while the sec-ond site will be