[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue CORE-9: Wildcarding and Extensibility in the SAML Schemas
This issue is still open. The latest version of the relevant position paper is here: http://www.oasis-open.org/committees/download.php/5226/sstc-maler-schema-extension-02.pdf I'd like to be able to close this out by next Tuesday. I believe this is what remains to be done/decided; only the last item is potentially worth discussing, I believe: - The paper offered a few options around a "xs:anyType vs. <xs:any>" strategy. I think that, in practice, we have selected option 3 (use either one, depending on the circumstances), though we haven't fully articulated the criteria for choosing in each circumstance. I think Scott wrote up a brief proposal for the criteria, but can't seem to find it right now. I would be willing to consider this closed. - The paper proposed a recommendation around "restrained globalness", which in practice we follow, but I seem to recall that we rejected the idea of adding prose to disallow reuse of elements other than assertions etc. I would be willing to consider this closed. - The recommendation around "attribute clarity" has been superseded quite dramatically by our earlier reworking of the attribute structure. The "semantic vs. syntactic clarity" recommendation has also been superseded. Same for the "namespace terminology" recommendation. So I would be willing to consider these closed. - Finally, there's an open question posed about the "must ignore" paradigm. We have refined, somewhat, our understanding of our goals around extension usage. But do we need/want to add something explicit around "must ignore" semantics? Eve -- Eve Maler +1 781 442 3190 Sun Microsystems cell +1 781 354 9441 Web Products, Technologies, and Standards eve.maler @ sun.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]