[Bug 4602] NOTATION and enumeration

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





--- Comment #3 from Dave Peterson <davep@iit.edu>  2008-12-17 03:05:58 ---
(In reply to comment #0)

> But it's not clear what "used directly in a schema" means.
> - Used as a base type in a restriction
> - Used as a member type in a union
> - Used as an item type in a list
> - Used as the declared type of an element/attribute
> - Used as xsi:type in an instance
> - Used to validate an element/attribute in an instance
> 
> My guess is that the last one is the ultimate goal. We may also have meant to
> require all but the first 1 (as base type) to avoid the last one from
> happening.

I've looked at Structures some more, and thought about this question some more.
 My current opinion is that the last one is the one we wanted to completely
prohibit.  I believe that that will automatically prohibit using it as an
xsi:type value.  All of the other possibilities leave the schema in a state
where it is possible (without avoiding an enumeration)--by xsi:type in the
instance or a later-in-the-derivation-chain restriction by enumeration--to be
in a position to validate an element or attribute in an instance.  Therefore, I
think it would be appropriate to formally require that an un-enumerated
NOTATION cannot be the final datatype against which a value can be validated,
and also add a Note to the effect that therefore such a datatype cannot be used
as an xsi:type value.

If this isn't editorial, it has to be acted on this week.  (If I understand our
schedule correctly.)


-- 
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 Wednesday, 17 December 2008 03:06:10 UTC