5659 2008-04-24 06:07:56 +0000 schemaComplete default value 2008-05-22 22:30:05 +0000 1 1 1 Unclassified SML Interchange Format LC PC Windows NT RESOLVED FIXED resolved P2 normal --- 1 kumarp virginia.smith public-sml oldest_to_newest 19926 0 kumarp 2008-04-24 06:07:56 +0000 schemaComplete attribute is currently defined as use=required (no default). I believe the intention behind this decision was to require the SML-IF producer make an explicit declaration regarding the completeness of the schema set. This is a good intention, but unfortunately this results in breaking all existing SML-IF files since they do not specify the schemaComplete attribute. The WG discussed semantics of schemaComplete and decided on the following: schemaComplete=’true’ : schema set is known to be complete schemaComplete=’false’ : schema set is not known to be complete (see bug# 4774 for a discussion of the above.) Note that, only the ‘true’ value above is an explicit assertion. It asserts that schema set is known to be complete. On the other hand, the false value merely indicates the absence of an assertion. Proposal: Given the above meaning, it would be reasonable to have schemaComplete=’false’ as the default value. This has 3 advantages, 1. It applies correctly to the existing models because we do not know the schemaComplete-ness of the existing models. Having this default minimizes the impact on the current models. 2. It retains the explicit declaration requirement for the ‘true’ case where it makes most sense. 3. We do not have to change the meaning of ‘true’ or ‘false’ values. 20052 1 johnarwe 2008-05-08 13:22:50 +0000 +1 20101 2 virginia.smith 2008-05-15 15:36:26 +0000 +1 20236 3 pratul.dublish 2008-05-22 18:59:51 +0000 Resolution on 5/22 call is to mark it editorial