OASIS ACAL [XACML] TC

 View Only

RE: [xacml] url/uri-string-concatenate

  • 1.  RE: [xacml] url/uri-string-concatenate

    Posted 06-09-2006 17:24
     MHonArc v2.5.0b2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    xacml message

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


    Subject: RE: [xacml] url/uri-string-concatenate


    Should be URI.  Well, should really be IRI, but URI is fine.. :)
    
    -----Original Message-----
    From: Seth Proctor [mailto:Seth.Proctor@sun.com] 
    Sent: Thursday, June 08, 2006 8:47 PM
    To: Bill Parducci
    Cc: Anne.Anderson@sun.com; OASIS XACML TC
    Subject: Re: [xacml] url/uri-string-concatenate
    
    
    FYI, I dredged up my notes on this question from several months ago  
    when I tripped across it. The informal consensus was that the  
    concatenation function is _not_ supposed to handle any specific  
    properties of the URI scheme. That is, it is not responsible for  
    adding characters like '/' or ':' or '%'.
    
    In other words, the function takes a URI and a bunch of strings. The  
    URI is effectively converted to a string, simple sting concatenation  
    is done to append all the elements in order, and then the complete  
    string is converted back to a URI. This does not have to be a URL.
    
    For some reason, the consensus on the name was to use "url" instead  
    of "uri" so this is what I implemented. That said, I don't care too  
    much which name is used. Given that there's nothing URL-specific  
    about the function, using "uri" for the name seems like a good idea  
    to me.
    
    <aside>
    I've talked a little about this with Anne. I should have thought of  
    it before 2.0, but, well, hindsight and all :) Rather than all these  
    type-specific functions we introduced for regexp, concat, etc., it  
    would probably make more sense just to have type-to-string functions  
    (which are needed anyway to support XML encoding), especially since  
    these functions essentially use these semantics. Maybe in the future  
    we could consider adding this to make it easier
    </aside>
    
    
    seth
    
    ---------------------------------------------------------------------
    To unsubscribe from this mail list, you must leave the OASIS TC that
    generates this mail.  You may a link to this group and all your TCs in
    OASIS
    at:
    https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
    
    _______________________________________________________________________
    Notice:  This email message, together with any attachments, may contain
    information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
    entities,  that may be confidential,  proprietary,  copyrighted  and/or
    legally privileged, and is intended solely for the use of the individual
    or entity named in this message. If you are not the intended recipient,
    and have received this message in error, please immediately return this
    by email and then delete it.
    


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