[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xacml] ISSUE: xacml 2.0 schema location appears to have moved,possibly invalidating schemas
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:
<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-xacml-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.
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-xacml-2.0-core-spec-os-errata.zip