Next in thread →
Next in month →
RE: [xacml] status code schema for xacmlContext:Response
Well, you took some sides I guess.. ;-)) This is better then putting it into advice - and I feel that something to this effect (rather then exceptions over underlying protocol is useful..) I would be happy with this - status codes can be dealt in the combining algorithm - which may be a custom extension anyway, if I understand correctly.. Are you proposing to standartize any status codes? -----Original Message----- From: Simon Godik [mailto:] Sent: Wednesday, July 24, 2002 2:26 PM To: Subject: [xacml] status code schema for xacmlContext:Response Status code element. Currently, there is a debate on how to communicate pdp status such as missing attributes etc to the pep. Without taking sides here is <status> element, borrowed from saml protocol schema that can be included in the xacml-context:Response. <xacmlContext:Status> element should be used instead of <xacml:ContextAdvice> within <xacmlContext:Result> element. <xs:element name="Status" type="xacmlContext:StatusType"/> <xs:complexType name="StatusType"> <xs:sequence> <xs:element ref="xacmlContext:StatusCode"/> <xs:element ref="xacmlContext:StatusMessage" minOccurs="0"/> <xs:element ref="xacmlContext:StatusDetail" minOccurs="0"/> </xs:sequence> </xs:complexType> <xs:element name="StatusCode" type="xacmlContext:StatusCodeType"/> <xs:complexType name="StatusCodeType"> <xs:sequence> <xs:element ref="xacmlStatus:StatusCode" minOccurs="0"/> <xs:attribute name="Value" type="xs:QName" use="required"/> </xs:sequence> </xs:complexType> <xs:element name="StatusMessage" type="xs:string"/> <xs:element name="StatusDetail" type="xacmlContext:StatusDetailType"/> <xs:complexType name="StatusDetailType"> <xs:sequence> <xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> Simon Godik
Next in thread →
Next in month →