[Bug 5636] why prohibit rules on local decls/defs described by other specs?

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5636





--- Comment #5 from John Arwe <johnarwe@us.ibm.com>  2008-06-23 11:48:52 ---
Prong 1 change 1: REJECTED

Prong 1 change 2: Desire to define what embed means, but not as children since
we are talking about schema properties here.  
from: sch:schema elements MAY be embedded in members of the {application 
information} of the ..
to:   sch:schema elements MAY appear as items in the {application information}
of the ...

Prong 1 change 3: dup of prong 2 change 2

Prong 1 change 4 (first one):  REJECTED, otherwise it would not covers P1e

Prong 1 change 4 (second one): REJECTED as harmless & potentially confusing

Prong 1 change 5 (first one):  NO CHANGE, since covering p1e is desired

Prong 1 change 5 (second one): REJECTED, so p1e is covered

Prong 1 change 6: REJECTED, harmless but unnecessary

Prong 1 change 7: REJECTED, unnecessary due to other changes rejected above

Prong 1 change 8: REJECTED

MSM proposal: Add to 6.3.1 Mapping from schema, paragraph 3: For other schema
components, local-rules is empty.
MSM proposal is ACCEPTED.

The wg members ARE aware that the MSM proposal = prong 1 change 3 = prong 2
change 4, we simply read 2/2 incorrectly the first time around.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Monday, 23 June 2008 11:49:26 UTC