OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

security-services message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: [security-services] Proposed DoNotCache Condition

Title: Proposed DoNotCache Condition

I propose to add the following text after line 438 of the core spec.


<DoNotCacheCondition> [Optional]

Indicates that the assertion SHOULD be used immediately and MUST not be retained for future use. Note: no implementation is required to perform caching, however any that do so MUST observe this Condition.


The coresponding changes to the schema would be to derive <DoNotCacheCondition> from <Condition>. I don't know if we need to derive an abstract type from <ConditionAbstractType> of just derive <DoNotCacheCondition> directly. It is hard to imagine any further extension to <DoNotCacheCondition>.

Suggestions? Opinions?


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC