To prevent spam users, you can only post on this forum after registration, which is by invitation. If you want to post on the forum, please send me a mail (h DOT m DOT w DOT verbeek AT tue DOT nl) and I'll send you an invitation in return for an account.

Validation of XES sample log fails.

pcoderpcoder Posts: 49
edited November 2011 in ProM 6
Dear all,

I am finding this wierd problem. 

When I try to validate the sample XES file (running-example.xes) from the Process Mining book by van der Aalst, located at  http://www.processmining.org/_media/processminingbook/chapter_1.zip, against the xes schema located at http://code.deckfour.org/xes/xes.xsd, I get the following schema validation error:

Cannot find the declaration of element 'log'.

I try to validate the schema using the online tool http://tools.decisionsoft.com/schemaValidate/

Am I doing something wrong?



Post edited by pcoder on
-- Thank you, PCoder

Comments

  • JBuijsJBuijs Posts: 912
    Hi PCoder,

    Thank you for pointing this out, it is indeed strange that it does not validate.
    I will ask around if this needs to be fixed.
    Joos Buijs

    Senior Data Scientist and process mining expert at APG (Dutch pension fund executor).
    Previously Assistant Professor in Process Mining at Eindhoven University of Technology
  • pcoderpcoder Posts: 49
    Thanks Joos, I thought I was the only one with this problem :)
    -- Thank you, PCoder
  • pcoderpcoder Posts: 49
    edited November 2011
    It happened that the answer to the question was very simple and within the schema definition itself http://code.deckfour.org/xes/xes.xsd

    The schema specifies that the element log needs three required attributes: xes.version, openxes.version, and xes.features and the xml namespace should be http://code.fluxicon.com/xes rather than http://code.deckfour.org/xes. Also, it doesn't need the xes.creator attribute.

    I wonder if the schema was modified after the book was written.

    The log element should look something like the attached image to comply to the schema.
    Post edited by pcoder on
    -- Thank you, PCoder
  • JBuijsJBuijs Posts: 912
    Hi PCoder,

    Thanks for investigating this further!!!
    There were some changes to the XES standard in the last year so that might indeed be the cause for the mismatch.
    I'll see if I can update the example log file to match the schema.
    Joos Buijs

    Senior Data Scientist and process mining expert at APG (Dutch pension fund executor).
    Previously Assistant Professor in Process Mining at Eindhoven University of Technology
  • lcalca Posts: 22
    Any news on this issue? It does not seem to be solved.
Sign In or Register to comment.