[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Checking BBIEs with repetition
Hello, TSC members,I'm copying this note from a discussion in PSC that may be relevant to the model work done in TSC.
Please let me know if you have any questions. . . . . . . . . . Ken
To: UBL Procurement Subcommittee <firstname.lastname@example.org> From: "G. Ken Holman" <gkholman@CraneSoftwrights.com> Subject: Checking BBIEs with repetitionWith my comments below in mind, I will add a new section of the model checker to flag those BBIE's with "0..n" or "1..n" that are not of type "Text". That will bring to focus those BIEs that might likely need to be refactored into an ASBIE/ABIE/BBIE combination to accommodate future use.I say "likely" because there should be no non-text BBIEs with "0..n" or "1..n".I agree it is unfortunate that this has come to light so late in the process, but it is something we shouldn't let fall through the cracks. I will publish the model report when I create the next draft PRD3 and we will see if we have to update the model with refactoring of BBIEs to ASBIE/ABIE/BBIE combinations before we vote on the package and make it public.I will send this to TSC as well to make them aware. . . . . . . . . Ken At 2012-12-20 10:22 -0500, I wrote:I agree that BBIEs that are not prose oriented (e.g. descriptions, notes, instructions) should be 0..1 or 1..1. If there is a requirement for more than one such BBIE, then there should be an ASBIE pointing to an ABIE with the BBIE with 0..1 or 1..1. Such an approach allows for future versions of the standard to associate other information with each of the identifiers that is not conceived of at this early stage. If we leave the BBIE as "0..n" or "1..n", then it is impossible to associate information with each individual BBIE in the future.
-- Contact us for world-wide XML consulting and instructor-led training Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal