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-schema-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-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.
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-xacml-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-schema-os.xsd
and
http://docs.oasis-open.org/xacml/2.0/access_control-xacml-2.0-context-schema-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
