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

 


Help: OASIS Mailing Lists Help | MarkMail Help

wss message

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


Subject: Issue: Binary Token & XML Token should be abstract


I believe that both the Binary Token and the XML Token should be abstract
types.  This means that they can not be instantiated by themselves but need
to have a derived element, which, in the present wsse case, would be defined
in profiles. The existing potential derived profiles are the X.509 and
Kerberos, which would be derived from the Binary Token and the SAML, XCBF
and XrML tokens, which would be derived from the XML Token.  Additional
profiles may derive from either an abstract type or may be a top level
element.

In my previous mail I suggested that the derived token be in a substitution
group or a choice.  Subsequent conversations have convinced me that this
would be too restrictive as the intent of the TC was to have an "open"
model. Therefore, I am dropping the later and just proposing that the Binary
and XML tokens be optional, abstract types.   I believe that the proposed
inheritance gives structure and clarity to this part of the specification.

Comments please.

Don


====================
Donald Flinn
Managing Partner
Flint Security
Phone: (781) 856-7230
e-mail: flinn@alum.mit.edu
Web Page: http://dflinn.home.attbi.com



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