Hi,
Maybe, what did you have in mind? However, it might make sense to
keep this profile as it is since these schemes stand on their own in
any case, and some of them are foundations for the multiple decision
profile, so we would be impacting that profile as well. The multiple
decision profile is one of those which I think is important to close
off since it means implementation effort in terms of code in the
PDP, so it's not nice for vendors to have it in flux.
If there are possibilities from the entities profile, it might make
sense to put those options in that profile since the entities
profile will be an implementation effort regardless.
Best regards,
Erik
On 2014-01-22 05:00, Mohammad Jafari
wrote:
Thanks
Erik.
I
am wondering if the work on Nested and Related Entities can
influence this profile. It seems to me that “hierarchies”
can be considered special cases of “related entities”.
This
might be something we can think about and discuss at the
next TC call.
Regards,
Mohammad
Jafari, Ph.D.
Security
Architect, Edmond Scientific Company
Submitter's message
Updates the hierarchical profile to the current OASIS
document template. There are no changes in the content,
except to fit the new template and:
- I added a subsection 1.1 to make it clear that the
non-normative statement only applies to it, not the rest of
section 1.
- Changed incorrect reference to RFC2396 to the correct
RFC3986
- I had forgot to specify Rich as a co-editor when I
requested the template, so I added him (I hope this does not
break any TC admin metadata tracking)
- I did a search for glossary terms and ended up marking
some which were not highlighted in the previous version.
- I fixed a few minor typos which I found.
-- Erik Rissanen
|