OASIS eXtensible Access Control Markup Language (XACML) TC

 View Only

RE: [xacml] Re: [xacml-comment] D024

  • 1.  RE: [xacml] Re: [xacml-comment] D024

    Posted 12-03-2002 13:44
     MHonArc v2.5.2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    xacml message

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


    Subject: RE: [xacml] Re: [xacml-comment] D024


    On Tue, 3 Dec 2002, Daniel Engovatov wrote:
    
    >
    > >All arguments can be type checked in advance.
    >
    > Define "advance"?
    
    It was your term.
    
    > Yes, it is typechecked before the decision is made.  The exact sequence
    > of said operations is implementation dependent.  That's why I said we are
    > talking about different definition of time.
    >
    > My point was that the policy document MAY be tested and accepted INDEPENDENT
    > of context data type verification.
    
    Yes, but I was not referring to the context data. The actual policy was
    not type correct, and hence not well formed.
    
    -Polar
    
    > In implementation that is concerned about efficiency that may be a key
    > distinction.
    >
    > >The theory of type systems and polymorphic functions allows complete
    > >typing of every element of an expression.
    >
    > The practice of implementation of said systems cause a great deal of
    > PITA for extension API development, that being the reason of such
    > language being rather unpopular.
    >
    > D;
    >
    
    


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


    Powered by eList eXpress LLC