OASIS eXtensible Access Control Markup Language (XACML) TC

Hi Steven, all, I was just made aware that the class diagrams in the spec are not readable. I checked the word version and it is fine. The conversion to HTML makes it lose resolution. Can we fix that? Also, I was just asked for an MDP by reference example. I just built one and pasted it down below so that we can include it as a non-normative example. Thanks, David { "Request":{ "AccessSubject":{ "Id":"s1", "Attribute":[ { "AttributeId":"com.acme.user.employeeId", "Value":"Alice" } ] }, "Resource":[ { "Id":"r1", "Attribute":[ { "AttributeId":"com.acme.object.objectType", "Value":"record" }, { "AttributeId":"com.acme.record.recordId", "Value":"126", "IncludeInResult":true } ] }, { "Id":"r2", "Attribute":[ { "AttributeId":"com.acme.object.objectType", "Value":"record" }, { "AttributeId":"com.acme.record.recordId", "Value":"125", "IncludeInResult":true } ] } ], "Action":[ { "Id":"a1", "Attribute":[ { "AttributeId":"com.acme.action.actionId", "Value":"view", "IncludeInResult":true } ] }, { "Id":"a2", "Attribute":[ { "AttributeId":"com.acme.action.actionId", "Value":"edit", "IncludeInResult":true } ] }, { "Id":"a3", "Attribute":[ { "AttributeId":"com.acme.action.actionId", "Value":"delete", "IncludeInResult":true } ] } ], "MultiRequests":{ "RequestReference":[ { "ReferenceId":[ "s1", "a1", "r1" ] }, { "ReferenceId":[ "s1", "a2", "r1" ] } ] } } } And the response { "Response":[ { "Decision":"Deny", "Status":{ "StatusCode":{ "Value":"urn:oasis:names:tc:xacml:1.0:status:ok", "StatusCode":{ "Value":"urn:oasis:names:tc:xacml:1.0:status:ok" } } }, "Category":[ { "CategoryId":"urn:oasis:names:tc:xacml:3.0:attribute-category:resource", "Attribute":{ "AttributeId":"com.acme.record.recordId", "Value":"126", "DataType":" http://www.w3.org/2001/XMLSchema#string " } }, { "CategoryId":"urn:oasis:names:tc:xacml:3.0:attribute-category:action", "Attribute":{ "AttributeId":"com.acme.action.actionId", "Value":"view", "DataType":" http://www.w3.org/2001/XMLSchema#string " } } ] }, { "Decision":"Deny", "Status":{ "StatusCode":{ "Value":"urn:oasis:names:tc:xacml:1.0:status:ok", "StatusCode":{ "Value":"urn:oasis:names:tc:xacml:1.0:status:ok" } } }, "Category":[ { "CategoryId":"urn:oasis:names:tc:xacml:3.0:attribute-category:resource", "Attribute":{ "AttributeId":"com.acme.record.recordId", "Value":"126", "DataType":" http://www.w3.org/2001/XMLSchema#string " } }, { "CategoryId":"urn:oasis:names:tc:xacml:3.0:attribute-category:action", "Attribute":{ "AttributeId":"com.acme.action.actionId", "Value":"edit", "DataType":" http://www.w3.org/2001/XMLSchema#string " } } ] } ] }

Hi David, On 18/07/2018 3:13 AM, David Brossard wrote: Hi Steven, all, I was just made aware that the class diagrams in the spec are not readable. I checked the word version and it is fine. The conversion to HTML makes it lose resolution. Can we fix that? Where did you find the HTML version? Which leads to my second question; does anyone know specifically how it was generated from the Word version? What did you use to originally compose the class diagrams? Perhaps if they are imported into the Word document in a different format that might make a difference. Also, I was just asked for an MDP by reference example. I just built one and pasted it down below so that we can include it as a non-normative example. Shall do. Regards, Steven Thanks, David { "Request":{ "AccessSubject":{ "Id":"s1", "Attribute":[ { "AttributeId":"com.acme.user.employeeId", "Value":"Alice" } ] }, "Resource":[ { "Id":"r1", "Attribute":[ { "AttributeId":"com.acme.object.objectType", "Value":"record" }, { "AttributeId":"com.acme.record.recordId", "Value":"126", "IncludeInResult":true } ] }, { "Id":"r2", "Attribute":[ { "AttributeId":"com.acme.object.objectType", "Value":"record" }, { "AttributeId":"com.acme.record.recordId", "Value":"125", "IncludeInResult":true } ] } ], "Action":[ { "Id":"a1", "Attribute":[ { "AttributeId":"com.acme.action.actionId", "Value":"view", "IncludeInResult":true } ] }, { "Id":"a2", "Attribute":[ { "AttributeId":"com.acme.action.actionId", "Value":"edit", "IncludeInResult":true } ] }, { "Id":"a3", "Attribute":[ { "AttributeId":"com.acme.action.actionId", "Value":"delete", "IncludeInResult":true } ] } ], "MultiRequests":{ "RequestReference":[ { "ReferenceId":[ "s1", "a1", "r1" ] }, { "ReferenceId":[ "s1", "a2", "r1" ] } ] } } } And the response { "Response":[ { "Decision":"Deny", "Status":{ "StatusCode":{ "Value":"urn:oasis:names:tc:xacml:1.0:status:ok", "StatusCode":{ "Value":"urn:oasis:names:tc:xacml:1.0:status:ok" } } }, "Category":[ { "CategoryId":"urn:oasis:names:tc:xacml:3.0:attribute-category:resource", "Attribute":{ "AttributeId":"com.acme.record.recordId", "Value":"126", "DataType":" http://www.w3.org/2001/XMLSchema#string" ; } }, { "CategoryId":"urn:oasis:names:tc:xacml:3.0:attribute-category:action", "Attribute":{ "AttributeId":"com.acme.action.actionId", "Value":"view", "DataType":" http://www.w3.org/2001/XMLSchema#string" ; } } ] }, { "Decision":"Deny", "Status":{ "StatusCode":{ "Value":"urn:oasis:names:tc:xacml:1.0:status:ok", "StatusCode":{ "Value":"urn:oasis:names:tc:xacml:1.0:status:ok" } } }, "Category":[ { "CategoryId":"urn:oasis:names:tc:xacml:3.0:attribute-category:resource", "Attribute":{ "AttributeId":"com.acme.record.recordId", "Value":"126", "DataType":" http://www.w3.org/2001/XMLSchema#string" ; } }, { "CategoryId":"urn:oasis:names:tc:xacml:3.0:attribute-category:action", "Attribute":{ "AttributeId":"com.acme.action.actionId", "Value":"edit", "DataType":" http://www.w3.org/2001/XMLSchema#string" ; } } ] } ] }

Where did you find the HTML version? Which leads to my second question; does anyone know specifically how it was generated from the Word version? I just googled for it. It took me to http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xacml-json-http-v1.0.html . What did you use to originally compose the class diagrams? Perhaps if they are imported into the Word document in a different format that might make a difference. Possibly. I used Inkscape and SVG. I've sent you the source. Thanks, David.