2
1
0

Contact/Person used to be a RefElement in JDF1.4 and before (so allow both embedded or referenced).

Seems that this changed a Element (not RefElement in JDF1.5)

  • this is NOT marked in the 1.5 spec as a change or in the changed list
  • this is NOT backwards compatible

I remembered some discussions and there is also JDF-87 but there was no JIRA issue requesting this change and also nothing in Errata if it was by mistake. Schema validation does not complain on PersonRef.

Why was it done ? (and not marked as change?)

Personally would consider a RefElement to be the better method since it allows multiple contacts to share the same Person (making sure there is no conflict between different Contacts). So we asked our partners to use PersonRef.

    CommentAdd your comment...

    2 answers

    1.  
      1
      0
      -1

      This is clearly a bug and we want to be backwards compatible. It needs to be fixed in 1.5 and 1.6.

      Somehow the  schema fix for  subelements and resource attributes in JDF 1.5 and JDF-87 - 1.5 schema: Person, PersonRef missing? Implemented never made it to the errata and thus also not into JDF 1.6.

      Please track in JDF-411 - JDF sub-elements or resources TSC VERIFY



      1. Koen Van de Poel

        Ok, I understand now

        • it was wrong in the 1.5 spec and derived schema
        • it was NOT marked as a change in 1.5 spec so reviewers did not notice
        • schema was fixed after the bug report in 2015 and samples validated again
        • forgot to mark as errata so ended up in JDF1.6
        • because the case was from 2015 I also did not remember it when reviewing 1.6, sorry about that.
      CommentAdd your comment...
    2.  
      2
      1
      0

      please see:-

      https://confluence.cip4.org/display/PUB/questions/10879143/subelements-and-resource-attributes-in-jdf-1.5

      I raised the same point a long time ago as a bug but it got rejected. I don't agree with the strategy of stopping supporting something already in use. Thx

        CommentAdd your comment...