Re: ISSUE: xacml 2.0 schema location appears to have moved, possibly invalidating schemas

[Rich Levinson <rich.levinson@oracle.com>]

Hi Sampo,

Please see most recent email addressing this problem:

    http://lists.oasis-open.org/archives/xacml/200705/msg00028.html

We did not determine the exact cause of the problem, and there is
not enough information available at this time to determine the steps
that preceded the current state of affairs.

The TC has issue #69 to follow up on, at which time I expect whatever
happened will be determined. In any event, I believe that we are currently
in a working state. I believe that the links in the above email are a 
potential
permanent solution to the problem as it currently stands for the existing
release, and for the Interop, but, again, the TC will cover this when
issue 69 is further analyzed.

    Thanks,
    Rich

sampo@symlabs.com wrote:
> Anne Anderson - Sun Microsystems writes:
>> Rich, we can't just do that.  That is the approved XACML 2.0 OASIS 
>> Standard, like it or not.  We plan to fix it as errata, but that is 
>> not exactly a lightweight process itself.
>> The link was right when XACML 2.0 was approved - OASIS changed the 
>> structure of their directories afterwards, and that is when it broke.
>> Given that it was an OASIS process change that broke it, perhaps you 
>> can persuade the OASIS powers that be to let us change it without 
>> going through the errata approval process.  The other alternative, 
>> possibly easier, is to convince them to store a copy of it in the old 
>> location at 
>> http://docs.oasis-open.org/xacml/access_control-xacml-2.0-policy-schema-os 
>> .xsd
>
> Supporting all old normatively referenced URLs is web master 101. I'm
> surprised OASIS has changed their web site structure without being
> aware of such a basic requirement.
> Cheers,
> --Sampo
>> -Anne
>> Rich Levinson wrote:
>>> Hi Anne,
>>> That .zip file just contains the .doc, .pdf, .odt for the XACML 2.0 
>>> core spec.
>>> My main concern is that what exists now does not work. My suggestion is
>>> that we simply insert the "/2.0" in the context spec:
>>>     
>>> http://docs.oasis-open.org/xacml/2.0/access_control-xacml-2.0-context-sch 
>>> ema-os.xsd
>>> i.e replace:
>>>   <xs:import 
>>> namespace="*urn:oasis:names:tc:xacml:2.0:policy:schema:os*" 
>>> schemaLocation="*http://docs.oasis-open.org/xacml/access_control-xacml-2. 
>>> 0-policy-schema-os.xsd*" />
>>> with
>>>   <xs:import 
>>> namespace="*urn:oasis:names:tc:xacml:2.0:policy:schema:os*" 
>>> schemaLocation="*http://docs.oasis-open.org/xacml/2.0/access_control-xacm 
>>> l-2.0-policy-schema-os.xsd*" />
>>>                                                                          
>>> ^^^^
>>> in the document that is posted there now.
>>> The problem is that the first thing users find is that the path is 
>>> not correct.
>>> Ok, fixing the path in the local xml files is not a big problem and 
>>> it is
>>> something the customer can control.
>>> But then they also find if they reference the context doc that it, 
>>> itself,
>>> has a bad ref that they can't do anything about. This will be major
>>> inconvenience. *In particular, I am doing work for the Interop and
>>> don't know what to do to address this problem.*
>>> Again, my recommendation is that we put the quick fix in the context
>>> file so that people can actually use things from the web site.
>>>     Thanks,
>>>     Rich
>>>  
>>>
>>>
>>> Anne Anderson wrote:
>>>> Existing Issue#69.  I haven't checked, but it may also be fixed in 
>>>> the schema included in the XACML 2.0 Errata at 
>>>> http://www.oasis-open.org/committees/download.php/19135/access_control-x 
>>>> acml-2.0-core-spec-os-errata.zip 
>>>>
>>>> Regards,
>>>> Anne
>>>> Rich Levinson wrote:
>>>>> I have been trying to validate some messages and appear to have
>>>>> uncovered a problem with the xacml 2.0 schemas.
>>>>> On the web site the schema locations are:
>>>>>    
>>>>> http://docs.oasis-open.org/xacml/2.0/access_control-xacml-2.0-policy-sc 
>>>>> hema-os.xsd 
>>>>> and
>>>>>    
>>>>> http://docs.oasis-open.org/xacml/2.0/access_control-xacml-2.0-context-s 
>>>>> chema-os.xsd 
>>>>>
>>>>> However, the context schema has a pointer to the policy schema 
>>>>> that says:
>>>>>  <xs:import 
>>>>> namespace="*urn:oasis:names:tc:xacml:2.0:policy:schema:os*" 
>>>>> schemaLocation="*http://docs.oasis-open.org/xacml/access_control-xacml- 
>>>>> 2.0-policy-schema-os.xsd*" />
>>>>>
>>>>> Note /xacml/ is not followed by "2.0" as it is in the actual 
>>>>> locations above,
>>>>> which causes the schema file not to be found on validate.
>>>>> This also shows up in what appears to be all the sample messages.
>>>>> Please advise.
>>>>>    Thanks,
>>>>>    Rich
>>>>
>>
>> -- 
>> Anne H. Anderson             Email: Anne.Anderson@Sun.COM
>> Sun Microsystems Laboratories
>> 1 Network Drive,UBUR02-311     Tel: 781/442-0928
>> Burlington, MA 01803-0902 USA  Fax: 781/442-1692
>
>
>
> __________________________________________________________________
> Sym  | Sampo Kellomaki  ______| Identity Architect, Federated SSO
> ____ | +351-918.731.007 ______| Liberty ID-WSF DirectoryScript
> labs | skype: sampo.kellomaki | LDAP SOAP PlainDoc Crypto C Perl
>