Update:
Since the flaw was in an administrative document (namespace or RDDL document) and not in the TC's normative Work Product content, we have determined that we can go ahead and make the correction. It is in place now.
Again, many thanks to Thomas Blanchard for identifying the issue.
Paul Knight
On Fri, Sep 21, 2018 at 2:46 PM Paul Knight <> wrote:
Thomas Blanchard submitted the following comment, regarding a broken link in the RDDL document which is retrieved by dereferencing any of the three namespaces listed inÂWeb Services Federation Language (WS-Federation) Version 1.2. [1]Â
Many thanks to Thomas for providing the correct link.
This identifies an error in the RDDL document stored at:
http://docs.oasis-open.org/wsfed/federation/v1.2/os/wsfed-1.2-rddl-200706-os.html
It is the policy of OASIS TC Administration not to alter published Work Products, so this error will not be corrected in place.
TheÂOASIS Web Services Federation (WSFED) TC has completed work, and is closed. Any Technical Committee which undertakes maintenance of the WSFED specifications is urged to correct this error in future versions.
[1]Âhttp://docs.oasis-open.org/wsfed/federation/v1.2/os/ws-federation-1.2-spec-os.html
Paul Knight
On Fri, Sep 21, 2018 at 1:51 PM 'Thomas Blanchard' via TC Administration <> wrote:
Hi folks,Â
Under these 3 pages:
http://docs.oasis-open.org/wsfed/privacy/200706
http://docs.oasis-open.org/wsfed/authorization/200706
http://docs.oasis-open.org/wsfed/federation/200706
The link towards the
WS-Federation Privacy Schema (ws-privacy.xsd) is broken:
the broken link isÂhttp://docs.oasis-open.org/wsfed/authorization/v1.2/os/ws-privacy.xsd
instead of :Âhttp://docs.oasis-open.org/wsfed/privacy/v1.2/os/ws-privacy.xsd
--Â
Thomas Blanchard
LinkedIn Learning & Lynda SRE
--
Paul KnightÂÂ-ÂTel: +1 781-883-1783
OASIS - Advancing open standards for the information society -ÂDocument Process Analyst
