90C41DD21FB7C64BB94121FBBC2E72343783562587@P3PW5EX1MB01.EX1.SECURESERVER.NET"
type="cite">
The decision between an attribute or a new element is still open and
this is one reason to opt for a separate <Subject> and <SubjectSet>
elements. In a separate approach, the <SubjectSet> element can have a
'match' attribute which will only define 'beginswith' at this point.
The content of this new element will be string.
Can we close this?
I suggest we stick to an attribute of <Subject> over a new element <SubjectSet> because the only reason for a new element is to make the content of the element a string (and not a URI). But if we do that, it becomes impossible to apply a *generic* trust profile to it because it no longer plays by the same rules <Subject> does (with a URI and an obvious authority section). This means if we create a new element, we need to explicitly set the trust profile to apply only to certain values of the match attribute... not pretty.
It looks like we need to start putting deadlines on issues or they just linger for months...
So please reply by 7/30 with your comments.
EHL
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php