The required claims appear as a whitespace separated list when
being set in an HTML tag. In an XHTML tag, each claim appears
as a separate element, with an attribute marking it as required or
optional.
OptionalClaims
Optional claims represent information that the site might like to
know about the user, but isn??™t requiring. The site may choose to
use optional claims if it is requesting information that may not
apply to all users. A common example would be when a site
does not require some information, such as a blog URL. The
blog URL may provide more pro?¬?le information about a user,
but is not required, because not everybody has a blog.
TokenType
Token type lets the website specify the token type they will accept.
CardSpace Personal Cards support SAML 1.0 and SAML
1.1 tokens. In this case, a token type of 'urn:oasis:names:tc:
SAML:1.0:assertion' should be speci?¬?ed. For Managed Cards,
Using CardSpace in the Browser 231
any format that the card provider would like can be used: SAML
or a token format that the provider invents. What is important is
that the website and the IP both understand the format.
CardSpace will not inspect whether the token conforms to a
speci?¬?c format For instance, we could de?¬?ne our own token
format and assign it a URI.
Pages:
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353