| [higgins-dev] Improved i-card.owl checked in |
Paul,
I made the following changes to attached i-card.owl:
1. I-Card should be able to contain extensions (in xml form).
2. ClaimType should also have the following datatype properties : claimTypeName, claimTypeDescription.
3. supportedClaimType should be object property with ClaimType range.
4. I-Card should have supportedTokenType datatype property.
5. pinDigest should have I-Card as a range (now CardSpace supports it for both m- and p-card, we did not yet implement it for m-card).
6. cardName property missed for I-Card.
7. cardVersion property missed for I-Card.
8. masterKey property missed for I-Card.
9. langId property missed for I-Card.
10. issuer property missed for I-Card.
11. stsPrivacyPolicyVersion missed for M-Card.
12. M-Card should have tokenService object property with TokenService range.
13. TokenService should have endpointReference object property with EndpointReference range.
14. EndpointReference should have address, metadataAddress and certificate properties.
15. TokenService should have userCredential object property with UserCredential range (also, there is CredentialDescriptor class defined in i-card.owl which duplicates UserCredential).
16. UserCredential should be able to contain all forth credential type descriptors. I added them as extended classes of UserCredential, but not sure it is correct. Does CDM support polymorphism?
Also the following changes need to be done:
17. P-card needs claim values.
18. strongRecipientdentityRequired - the label contains "require aplies to", but this is not quite correct. It meaning is RP should provide a cryptographically protected identity, for example, an X.509v3 certificate. Also "I" is missed in the name of this property, moreover, in CardSpace docs it is named as RequireStrongRecipientIdentity.