[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: SV: SV: SV: [ubl] Revised discussion paper on UBL 2.0 subsets, extensions, versions, validation and interchange
To be more specific: when I say non-deterministic and wrong I mean non-deterministic schema and wrong instance. :) Whereas XSV has returned non-deterministic schema and correct instance. I don't think this is wrong for XSV to say because I don't understand the spec to mean that a non-deterministic schema MUST always mean incorrect instances, but I think almost everybody else does. And as noted before it just seems really weird to think that one could have a non-deterministic schema but a correct instance by it, frankly the idea hurts my head. Cheers, Bryan Rasmussen -----Oprindelig meddelelse----- Fra: Bryan Rasmussen Sendt: 20. juni 2006 16:05 Til: 'G. Ken Holman'; ubl@lists.oasis-open.org Emne: SV: SV: SV: [ubl] Revised discussion paper on UBL 2.0 subsets, extensions, versions, validation and interchange Hi Ken >I am willing to accept your assessment and can >withdraw the proposal based on >non-implementability (is that a word?) ... can >anyone else offer a comment on the >non-determinism? Does anyone have an opinion >regarding which processor is correct? My opinion is basically that XSV is correct on this matter, in that I would tend to trust Henry Thompson in matters of non-determinism, problems with XSV has generally not been on this stuff and it seems to me that this is one of the things the whole FSA based approach is ideally suited for. Thinking about it abstractly: It is non-deterministic because we cannot be sure if we are supposed to do strict or skip. However if it validates by strict then the non-determinism does not apply (one could argue this, but it feels really weird). In other words, the schema is non-deterministic but we can be sure that the instance is correct anyway because if it is correct by strict it is surely correct by skip as well. I think that explains the otherwise strange output of XSV. However it has been my experience that most processors would take this as non-deterministic and wrong, and IIRC XSV at one point did take it as both non-deterministic and wrong. For all these reasons I would like to avoid it, and while it might be theoretically implementable in that way I think in most real world applications it will be non-implementable. Cheers, Bryan Rasmussen
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]