OASIS eXtensible Access Control Markup Language (XACML) TC

Paul, > -----Original Message----- > From: Tyson, Paul H [ mailto:ptyson@bh.com ] > Sent: Tuesday, April 24, 2012 3:38 PM > To: Sinnema, Remon; xacml@lists.oasis-open.org > Subject: RE: Media types > > Following your reasoning that media types are used mainly for content > negotiation, why do we even need specialized media types for XACML? http://tools.ietf.org/html/rfc3023#page-32 There could be other XML based formats that represent the same information as application/xacml+xml. For instance, a policy could potentially also be represented by RDF-XML (application/rdf+xml). > The currently defined top-level syntactic entities--Policy, PolicySet, > Request, Response--will just be "text/xml". http://tools.ietf.org/html/rfc3023#section-3 Anything in the "text" branch is supposed to be readable for a *casual* user. That's definitely not the case for XACML, so we need a media type from the "application" branch. > If we do move forward with an "application/xacml+json" type, I don't > think the profile should include examples. The TC has not specified any > JSON representation of XACML entities, and the examples in this profile > would be misleading. The profile should state clearly that this media > type does not imply any particular mapping from XACML XML syntax to > JSON data structures. The JSON format needs to be defined somewhere, or else JSON based systems can't interoperate. So we have two options: (1) We define the JSON representation in this profile (2) We create a separate JSON profile and refer to that from here I was shooting for (1), with the examples being the "specification" of the JSON format. Unfortunately, there is no JSON equivalent of XML Schema. I think the best we can do is something like this: http://amundsen.com/media-types/collection/format/#objects Thanks, Ray

Ray, OK, thanks for the references to rfc3023. I agree with your proposed types. However, I don't think this profile is the right place to define a JSON mapping for XACML. That should be a different document. Regards, --Paul > -----Original Message----- > From: remon.sinnema@emc.com [ mailto:remon.sinnema@emc.com ] > Sent: Tuesday, 24 April, 2012 09:15 > To: Tyson, Paul H > Cc: xacml@lists.oasis-open.org > Subject: RE: Media types > > Paul, > > > > -----Original Message----- > > From: Tyson, Paul H [ mailto:ptyson@bh.com ] > > Sent: Tuesday, April 24, 2012 3:38 PM > > To: Sinnema, Remon; xacml@lists.oasis-open.org > > Subject: RE: Media types > > > > Following your reasoning that media types are used mainly for content > > negotiation, why do we even need specialized media types for XACML? > > http://tools.ietf.org/html/rfc3023#page-32 > > There could be other XML based formats that represent the same > information as application/xacml+xml. For instance, a policy could > potentially also be represented by RDF-XML (application/rdf+xml). > > > > The currently defined top-level syntactic entities--Policy, > PolicySet, > > Request, Response--will just be "text/xml". > > http://tools.ietf.org/html/rfc3023#section-3 > > Anything in the "text" branch is supposed to be readable for a *casual* > user. That's definitely not the case for XACML, so we need a media type > from the "application" branch. > > > > If we do move forward with an "application/xacml+json" type, I don't > > think the profile should include examples. The TC has not specified > any > > JSON representation of XACML entities, and the examples in this > profile > > would be misleading. The profile should state clearly that this media > > type does not imply any particular mapping from XACML XML syntax to > > JSON data structures. > > The JSON format needs to be defined somewhere, or else JSON based > systems can't interoperate. So we have two options: > (1) We define the JSON representation in this profile > (2) We create a separate JSON profile and refer to that from here > > I was shooting for (1), with the examples being the "specification" of > the JSON format. > > Unfortunately, there is no JSON equivalent of XML Schema. I think the > best we can do is something like this: > http://amundsen.com/media-types/collection/format/#objects > > > Thanks, > Ray

On Apr 24, 2012, at 7:47 AM, Tyson, Paul H wrote: > However, I don't think this profile is the right place to define a JSON mapping for XACML. That should be a different document. Agreed. If nothing else, the scope of work of the JSON mapping should not impede the progress of defining typing IMO. b

Bill, Paul, > -----Original Message----- > From: xacml@lists.oasis-open.org [ mailto:xacml@lists.oasis-open.org ] On > Behalf Of Bill Parducci > Sent: Tuesday, April 24, 2012 5:05 PM > To: Tyson, Paul H > Cc: Sinnema, Remon; xacml@lists.oasis-open.org > Subject: Re: [xacml] RE: Media types > > > On Apr 24, 2012, at 7:47 AM, Tyson, Paul H wrote: > > > However, I don't think this profile is the right place to define a > JSON mapping for XACML. That should be a different document. > > Agreed. If nothing else, the scope of work of the JSON mapping should > not impede the progress of defining typing IMO. That's fine with me. However, you can't register a MIME media type if the format is undefined, so the Media Types profile would have to wait until the JSON profile is done. The registration must contain or link to the format specification. Thanks, Ray

All Need to define the impact on the ITU submission I suggest that we do not choose a solution that delay the submission Regards Abbie -----Original Message----- From: xacml@lists.oasis-open.org [ mailto:xacml@lists.oasis-open.org ] On Behalf Of remon.sinnema@emc.com Sent: Tuesday, April 24, 2012 11:28 AM To: bill@parducci.net; ptyson@bh.com Cc: xacml@lists.oasis-open.org Subject: RE: [xacml] RE: Media types Bill, Paul, > -----Original Message----- > From: xacml@lists.oasis-open.org [ mailto:xacml@lists.oasis-open.org ] > On Behalf Of Bill Parducci > Sent: Tuesday, April 24, 2012 5:05 PM > To: Tyson, Paul H > Cc: Sinnema, Remon; xacml@lists.oasis-open.org > Subject: Re: [xacml] RE: Media types > > > On Apr 24, 2012, at 7:47 AM, Tyson, Paul H wrote: > > > However, I don't think this profile is the right place to define a > JSON mapping for XACML. That should be a different document. > > Agreed. If nothing else, the scope of work of the JSON mapping should > not impede the progress of defining typing IMO. That's fine with me. However, you can't register a MIME media type if the format is undefined, so the Media Types profile would have to wait until the JSON profile is done. The registration must contain or link to the format specification. Thanks, Ray --------------------------------------------------------------------- To unsubscribe, e-mail: xacml-unsubscribe@lists.oasis-open.org For additional commands, e-mail: xacml-help@lists.oasis-open.org ---------------------------------------------------------------------- This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.bankofamerica.com/emaildisclaimer . By messaging with Sender you consent to the foregoing.

The progress of this specification should be completely independent to moving the Core to OASIS Standard. Hal > -----Original Message----- > From: Barbir, Abbie [ mailto:abbie.barbir@bankofamerica.com ] > Sent: Tuesday, April 24, 2012 11:38 AM > To: remon.sinnema@emc.com; bill@parducci.net; ptyson@bh.com > Cc: xacml@lists.oasis-open.org; Radhakrishnan, Rakesh; Marian, Radu > Subject: RE: [xacml] RE: Media types > > All > Need to define the impact on the ITU submission I suggest that we do > not choose a solution that delay the submission > > Regards > Abbie > > > > -----Original Message----- > From: xacml@lists.oasis-open.org [ mailto:xacml@lists.oasis-open.org ] On > Behalf Of remon.sinnema@emc.com > Sent: Tuesday, April 24, 2012 11:28 AM > To: bill@parducci.net; ptyson@bh.com > Cc: xacml@lists.oasis-open.org > Subject: RE: [xacml] RE: Media types > > Bill, Paul, > > > > -----Original Message----- > > From: xacml@lists.oasis-open.org [ mailto:xacml@lists.oasis-open.org ] > > On Behalf Of Bill Parducci > > Sent: Tuesday, April 24, 2012 5:05 PM > > To: Tyson, Paul H > > Cc: Sinnema, Remon; xacml@lists.oasis-open.org > > Subject: Re: [xacml] RE: Media types > > > > > > On Apr 24, 2012, at 7:47 AM, Tyson, Paul H wrote: > > > > > However, I don't think this profile is the right place to define a > > JSON mapping for XACML. That should be a different document. > > > > Agreed. If nothing else, the scope of work of the JSON mapping should > > not impede the progress of defining typing IMO. > > That's fine with me. However, you can't register a MIME media type if > the format is undefined, so the Media Types profile would have to wait > until the JSON profile is done. The registration must contain or link > to the format specification. > > > Thanks, > Ray > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: xacml-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: xacml-help@lists.oasis-open.org > > ---------------------------------------------------------------------- > This message w/attachments (message) is intended solely for the use of > the intended recipient(s) and may contain information that is > privileged, confidential or proprietary. If you are not an intended > recipient, please notify the sender, and then please delete and destroy > all copies and attachments, and be advised that any review or > dissemination of, or the taking of any action in reliance on, the > information contained in or attached to this message is prohibited. > Unless specifically indicated, this message is not an offer to sell or > a solicitation of any investment products or other financial product or > service, an official confirmation of any transaction, or an official > statement of Sender. Subject to applicable law, Sender may intercept, > monitor, review and retain e-communications (EC) traveling through its > networks/systems and may produce any such EC to regulators, law > enforcement, in litigation and as required by law. > The laws of the country of each sender/recipient may impact the > handling of EC, and EC may be archived, supervised and produced in > countries other than the country in which you are located. This message > cannot be guaranteed to be secure or free of errors or viruses. > > References to "Sender" are references to any subsidiary of Bank of > America Corporation. Securities and Insurance Products: * Are Not FDIC > Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank > Deposit * Are Not a Condition to Any Banking Service or Activity * Are > Not Insured by Any Federal Government Agency. Attachments that are part > of this EC may have additional important disclosures and disclaimers, > which you should read. This message is subject to terms available at > the following link: > http://www.bankofamerica.com/emaildisclaimer . By messaging with Sender > you consent to the foregoing. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: xacml-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: xacml-help@lists.oasis-open.org >

Re: > The progress of this specification should be completely > independent to moving the Core to OASIS Standard. Maybe "completely independent" (?) but please note: Just a reminder (though not to contradict Hal) that there is direction from IETF/IANA (and evidence of enforcement) that if an RFC is not used to define the media/mine type(s), or maybe even if so, then the definition/description of the proposed media types must be made in a **standard** when a non-IETF SSO/SDO is making the registration request. Is the XACML TC intending to approve and publish the document "XACML Media Types Version 1.0" as an OASIS Standard? Details: ====================================================== [emph added in "**  ... **"] http://tools.ietf.org/html/rfc4288#section-4.10 4.10. Publication Requirements Proposals for media types registered in the standards tree by the IETF itself MUST be published as RFCs. RFC publication of vendor and personal media type proposals is encouraged but not required.  In all cases the IANA will retain copies of all media type proposals and "publish" them as part of the media types registration tree itself. As stated previously, standards tree registrations for **media types defined in documents produced by other standards bodies MUST be described by a formal standards specification produced by that body.** Such specifications MUST contain an appropriate media type registration template taken from Section 10.  Additionally, the copyright on the registration template MUST allow the IANA to copy it into the IANA registry. [...] Proposed registrations in the standards tree by other standards bodies should be communicated to the IESG (at iesg@ietf.org ) and to the ietf-types list (at ietf-types@iana.org ).  Prior posting as an Internet Draft is not required for these registrations, but may be helpful to the IESG and is encouraged. ====================================================== Tracking: Register XACML Media Type with IANA http://tools.oasis-open.org/issues/browse/TCADMIN-844 Compare: http://tools.oasis-open.org/issues/browse/TCADMIN-613 "Media Type Specifications and Registration Procedures" Request for Comments: 4288 http://tools.ietf.org/html/rfc4288 http://tools.ietf.org/html/rfc4288#section-10 See: http://tools.ietf.org/html/rfc4288#section-5.2 Please keep me in the loop here; Ray, I have some comments/corrections for the WD 02 revision of "XACML Media Types Version 1.0" - Robin Robin Cover OASIS, Director of Information Services Editor, Cover Pages and XML Daily Newslink Email: robin@oasis-open.org Staff bio: http://www.oasis-open.org/people/staff/robin-cover Cover Pages: http://xml.coverpages.org/ Newsletter: http://xml.coverpages.org/newsletterArchive.html Tel: +1 972-296-1783 On Thu, May 3, 2012 at 12:03 PM, Hal Lockhart < hal.lockhart@oracle.com > wrote: The progress of this specification should be completely independent to moving the Core to OASIS Standard. Hal > -----Original Message----- > From: Barbir, Abbie [mailto: abbie.barbir@bankofamerica.com ] > Sent: Tuesday, April 24, 2012 11:38 AM > To: remon.sinnema@emc.com ; bill@parducci.net ; ptyson@bh.com > Cc: xacml@lists.oasis-open.org ; Radhakrishnan, Rakesh; Marian, Radu > Subject: RE: [xacml] RE: Media types > > All > Need to define the impact on the ITU submission I suggest that we do > not choose a solution that delay the submission > > Regards > Abbie > > > > -----Original Message----- > From: xacml@lists.oasis-open.org [mailto: xacml@lists.oasis-open.org ] On > Behalf Of remon.sinnema@emc.com > Sent: Tuesday, April 24, 2012 11:28 AM > To: bill@parducci.net ; ptyson@bh.com > Cc: xacml@lists.oasis-open.org > Subject: RE: [xacml] RE: Media types > > Bill, Paul, > > > > -----Original Message----- > > From: xacml@lists.oasis-open.org [mailto: xacml@lists.oasis-open.org ] > > On Behalf Of Bill Parducci > > Sent: Tuesday, April 24, 2012 5:05 PM > > To: Tyson, Paul H > > Cc: Sinnema, Remon; xacml@lists.oasis-open.org > > Subject: Re: [xacml] RE: Media types > > > > > > On Apr 24, 2012, at 7:47 AM, Tyson, Paul H wrote: > > > > > However, I don't think this profile is the right place to define a > > JSON mapping for XACML. That should be a different document. > > > > Agreed. If nothing else, the scope of work of the JSON mapping should > > not impede the progress of defining typing IMO. > > That's fine with me. However, you can't register a MIME media type if > the format is undefined, so the Media Types profile would have to wait > until the JSON profile is done. The registration must contain or link > to the format specification. > > > Thanks, > Ray > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: xacml-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: xacml-help@lists.oasis-open.org > > ---------------------------------------------------------------------- > This message w/attachments (message) is intended solely for the use of > the intended recipient(s) and may contain information that is > privileged, confidential or proprietary. If you are not an intended > recipient, please notify the sender, and then please delete and destroy > all copies and attachments, and be advised that any review or > dissemination of, or the taking of any action in reliance on, the > information contained in or attached to this message is prohibited. > Unless specifically indicated, this message is not an offer to sell or > a solicitation of any investment products or other financial product or > service, an official confirmation of any transaction, or an official > statement of Sender. Subject to applicable law, Sender may intercept, > monitor, review and retain e-communications (EC) traveling through its > networks/systems and may produce any such EC to regulators, law > enforcement, in litigation and as required by law. > The laws of the country of each sender/recipient may impact the > handling of EC, and EC may be archived, supervised and produced in > countries other than the country in which you are located. This message > cannot be guaranteed to be secure or free of errors or viruses. > > References to "Sender" are references to any subsidiary of Bank of > America Corporation. Securities and Insurance Products: * Are Not FDIC > Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank > Deposit * Are Not a Condition to Any Banking Service or Activity * Are > Not Insured by Any Federal Government Agency. Attachments that are part > of this EC may have additional important disclosures and disclaimers, > which you should read. This message is subject to terms available at > the following link: > http://www.bankofamerica.com/emaildisclaimer . By messaging with Sender > you consent to the foregoing. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: xacml-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: xacml-help@lists.oasis-open.org > --------------------------------------------------------------------- To unsubscribe, e-mail: xacml-unsubscribe@lists.oasis-open.org For additional commands, e-mail: xacml-help@lists.oasis-open.org --

All, Since we've now decided to define the JSON format in a separate specification instead of in the Media Types profile, I propose the following course of action: (1) Let the JSON format specification contain the IANA media type registration details for application/xacml+json (2) Register the XML format (application/xacml+xml) through an IETF RFC (3) Skip the Media Types profile altogether What do you think? Thanks, Ray From: Robin Cover [ mailto:robin@oasis-open.org ] Sent: Thursday, May 03, 2012 7:32 PM To: xacml@lists.oasis-open.org; Hal Lockhart Cc: Barbir, Abbie; Sinnema, Remon; bill@parducci.net; ptyson@bh.com; Radhakrishnan, Rakesh; Marian, Radu; Robin Cover Subject: Re: [xacml] RE: Media types Re: > The progress of this specification should be completely > independent to moving the Core to OASIS Standard. Maybe "completely independent" (?) but please note: Just a reminder (though not to contradict Hal) that there is direction from IETF/IANA (and evidence of enforcement) that if an RFC is not used to define the media/mine type(s), or maybe even if so, then the definition/description of the proposed media types must be made in a **standard** when a non-IETF SSO/SDO is making the registration request. Is the XACML TC intending to approve and publish the document "XACML Media Types Version 1.0" as an OASIS Standard? Details: ====================================================== [emph added in "**  ... **"] http://tools.ietf.org/html/rfc4288#section-4.10 4.10. Publication Requirements Proposals for media types registered in the standards tree by the IETF itself MUST be published as RFCs. RFC publication of vendor and personal media type proposals is encouraged but not required.  In all cases the IANA will retain copies of all media type proposals and "publish" them as part of the media types registration tree itself. As stated previously, standards tree registrations for **media types defined in documents produced by other standards bodies MUST be described by a formal standards specification produced by that body.** Such specifications MUST contain an appropriate media type registration template taken from Section 10.  Additionally, the copyright on the registration template MUST allow the IANA to copy it into the IANA registry. [...] Proposed registrations in the standards tree by other standards bodies should be communicated to the IESG (at iesg@ietf.org) and to the ietf-types list (at ietf-types@iana.org).  Prior posting as an Internet Draft is not required for these registrations, but may be helpful to the IESG and is encouraged. ====================================================== Tracking: Register XACML Media Type with IANA http://tools.oasis-open.org/issues/browse/TCADMIN-844 Compare: http://tools.oasis-open.org/issues/browse/TCADMIN-613 "Media Type Specifications and Registration Procedures" Request for Comments: 4288 http://tools.ietf.org/html/rfc4288 http://tools.ietf.org/html/rfc4288#section-10 See: http://tools.ietf.org/html/rfc4288#section-5.2 Please keep me in the loop here; Ray, I have some comments/corrections for the WD 02 revision of "XACML Media Types Version 1.0" - Robin Robin Cover OASIS, Director of Information Services Editor, Cover Pages and XML Daily Newslink Email: robin@oasis-open.org Staff bio: http://www.oasis-open.org/people/staff/robin-cover Cover Pages: http://xml.coverpages.org/ Newsletter: http://xml.coverpages.org/newsletterArchive.html Tel: +1 972-296-1783 On Thu, May 3, 2012 at 12:03 PM, Hal Lockhart <hal.lockhart@oracle.com> wrote: The progress of this specification should be completely independent to moving the Core to OASIS Standard. Hal > -----Original Message----- > From: Barbir, Abbie [ mailto:abbie.barbir@bankofamerica.com ] > Sent: Tuesday, April 24, 2012 11:38 AM > To: remon.sinnema@emc.com; bill@parducci.net; ptyson@bh.com > Cc: xacml@lists.oasis-open.org; Radhakrishnan, Rakesh; Marian, Radu > Subject: RE: [xacml] RE: Media types > > All > Need to define the impact on the ITU submission I suggest that we do > not choose a solution that delay the submission > > Regards > Abbie > > > > -----Original Message----- > From: xacml@lists.oasis-open.org [ mailto:xacml@lists.oasis-open.org ] On > Behalf Of remon.sinnema@emc.com > Sent: Tuesday, April 24, 2012 11:28 AM > To: bill@parducci.net; ptyson@bh.com > Cc: xacml@lists.oasis-open.org > Subject: RE: [xacml] RE: Media types > > Bill, Paul, > > > > -----Original Message----- > > From: xacml@lists.oasis-open.org [ mailto:xacml@lists.oasis-open.org ] > > On Behalf Of Bill Parducci > > Sent: Tuesday, April 24, 2012 5:05 PM > > To: Tyson, Paul H > > Cc: Sinnema, Remon; xacml@lists.oasis-open.org > > Subject: Re: [xacml] RE: Media types > > > > > > On Apr 24, 2012, at 7:47 AM, Tyson, Paul H wrote: > > > > > However, I don't think this profile is the right place to define a > > JSON mapping for XACML. That should be a different document. > > > > Agreed. If nothing else, the scope of work of the JSON mapping should > > not impede the progress of defining typing IMO. > > That's fine with me. However, you can't register a MIME media type if > the format is undefined, so the Media Types profile would have to wait > until the JSON profile is done. The registration must contain or link > to the format specification. > > > Thanks, > Ray > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: xacml-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: xacml-help@lists.oasis-open.org > > ---------------------------------------------------------------------- > This message w/attachments (message) is intended solely for the use of > the intended recipient(s) and may contain information that is > privileged, confidential or proprietary. If you are not an intended > recipient, please notify the sender, and then please delete and destroy > all copies and attachments, and be advised that any review or > dissemination of, or the taking of any action in reliance on, the > information contained in or attached to this message is prohibited. > Unless specifically indicated, this message is not an offer to sell or > a solicitation of any investment products or other financial product or > service, an official confirmation of any transaction, or an official > statement of Sender. Subject to applicable law, Sender may intercept, > monitor, review and retain e-communications (EC) traveling through its > networks/systems and may produce any such EC to regulators, law > enforcement, in litigation and as required by law. > The laws of the country of each sender/recipient may impact the > handling of EC, and EC may be archived, supervised and produced in > countries other than the country in which you are located. This message > cannot be guaranteed to be secure or free of errors or viruses. > > References to "Sender" are references to any subsidiary of Bank of > America Corporation. Securities and Insurance Products: * Are Not FDIC > Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank > Deposit * Are Not a Condition to Any Banking Service or Activity * Are > Not Insured by Any Federal Government Agency. Attachments that are part > of this EC may have additional important disclosures and disclaimers, > which you should read. This message is subject to terms available at > the following link: > http://www.bankofamerica.com/emaildisclaimer . By messaging with Sender > you consent to the foregoing. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: xacml-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: xacml-help@lists.oasis-open.org > --------------------------------------------------------------------- To unsubscribe, e-mail: xacml-unsubscribe@lists.oasis-open.org For additional commands, e-mail: xacml-help@lists.oasis-open.org --

I tend to agree with Ray. It will speed things up. @Ray, are you happy for me to use the profile i had initiated to define the JSON format? Cheers, David. On Thu, May 3, 2012 at 10:45 AM, < remon.sinnema@emc.com > wrote: All, Since we've now decided to define the JSON format in a separate specification instead of in the Media Types profile, I propose the following course of action: (1) Let the JSON format specification contain the IANA media type registration details for application/xacml+json (2) Register the XML format (application/xacml+xml) through an IETF RFC (3) Skip the Media Types profile altogether What do you think? Thanks, Ray From: Robin Cover [mailto: robin@oasis-open.org ] Sent: Thursday, May 03, 2012 7:32 PM To: xacml@lists.oasis-open.org ; Hal Lockhart Cc: Barbir, Abbie; Sinnema, Remon; bill@parducci.net ; ptyson@bh.com ; Radhakrishnan, Rakesh; Marian, Radu; Robin Cover Subject: Re: [xacml] RE: Media types Re: > The progress of this specification should be completely > independent to moving the Core to OASIS Standard. Maybe "completely independent" (?) but please note: Just a reminder (though not to contradict Hal) that there is direction from IETF/IANA (and evidence of enforcement) that if an RFC is not used to define the media/mine type(s), or maybe even if so, then the definition/description of the proposed media types must be made in a **standard** when a non-IETF SSO/SDO is making the registration request. Is the XACML TC intending to approve and publish the document "XACML Media Types Version 1.0" as an OASIS Standard? Details: ====================================================== [emph added in "**  ... **"] http://tools.ietf.org/html/rfc4288#section-4.10 4.10. Publication Requirements Proposals for media types registered in the standards tree by the IETF itself MUST be published as RFCs. RFC publication of vendor and personal media type proposals is encouraged but not required.  In all cases the IANA will retain copies of all media type proposals and "publish" them as part of the media types registration tree itself. As stated previously, standards tree registrations for **media types defined in documents produced by other standards bodies MUST be described by a formal standards specification produced by that body.** Such specifications MUST contain an appropriate media type registration template taken from Section 10.  Additionally, the copyright on the registration template MUST allow the IANA to copy it into the IANA registry. [...] Proposed registrations in the standards tree by other standards bodies should be communicated to the IESG (at iesg@ietf.org ) and to the ietf-types list (at ietf-types@iana.org ).  Prior posting as an Internet Draft is not required for these registrations, but may be helpful to the IESG and is encouraged. ====================================================== Tracking: Register XACML Media Type with IANA http://tools.oasis-open.org/issues/browse/TCADMIN-844 Compare: http://tools.oasis-open.org/issues/browse/TCADMIN-613 "Media Type Specifications and Registration Procedures" Request for Comments: 4288 http://tools.ietf.org/html/rfc4288 http://tools.ietf.org/html/rfc4288#section-10 See: http://tools.ietf.org/html/rfc4288#section-5.2 Please keep me in the loop here; Ray, I have some comments/corrections for the WD 02 revision of "XACML Media Types Version 1.0" - Robin Robin Cover OASIS, Director of Information Services Editor, Cover Pages and XML Daily Newslink Email: robin@oasis-open.org Staff bio: http://www.oasis-open.org/people/staff/robin-cover Cover Pages: http://xml.coverpages.org/ Newsletter: http://xml.coverpages.org/newsletterArchive.html Tel: +1 972-296-1783 On Thu, May 3, 2012 at 12:03 PM, Hal Lockhart < hal.lockhart@oracle.com > wrote: The progress of this specification should be completely independent to moving the Core to OASIS Standard. Hal > -----Original Message----- > From: Barbir, Abbie [mailto: abbie.barbir@bankofamerica.com ] > Sent: Tuesday, April 24, 2012 11:38 AM > To: remon.sinnema@emc.com ; bill@parducci.net ; ptyson@bh.com > Cc: xacml@lists.oasis-open.org ; Radhakrishnan, Rakesh; Marian, Radu > Subject: RE: [xacml] RE: Media types > > All > Need to define the impact on the ITU submission I suggest that we do > not choose a solution that delay the submission > > Regards > Abbie > > > > -----Original Message----- > From: xacml@lists.oasis-open.org [mailto: xacml@lists.oasis-open.org ] On > Behalf Of remon.sinnema@emc.com > Sent: Tuesday, April 24, 2012 11:28 AM > To: bill@parducci.net ; ptyson@bh.com > Cc: xacml@lists.oasis-open.org > Subject: RE: [xacml] RE: Media types > > Bill, Paul, > > > > -----Original Message----- > > From: xacml@lists.oasis-open.org [mailto: xacml@lists.oasis-open.org ] > > On Behalf Of Bill Parducci > > Sent: Tuesday, April 24, 2012 5:05 PM > > To: Tyson, Paul H > > Cc: Sinnema, Remon; xacml@lists.oasis-open.org > > Subject: Re: [xacml] RE: Media types > > > > > > On Apr 24, 2012, at 7:47 AM, Tyson, Paul H wrote: > > > > > However, I don't think this profile is the right place to define a > > JSON mapping for XACML. That should be a different document. > > > > Agreed. If nothing else, the scope of work of the JSON mapping should > > not impede the progress of defining typing IMO. > > That's fine with me. However, you can't register a MIME media type if > the format is undefined, so the Media Types profile would have to wait > until the JSON profile is done. The registration must contain or link > to the format specification. > > > Thanks, > Ray > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: xacml-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: xacml-help@lists.oasis-open.org > > ---------------------------------------------------------------------- > This message w/attachments (message) is intended solely for the use of > the intended recipient(s) and may contain information that is > privileged, confidential or proprietary. If you are not an intended > recipient, please notify the sender, and then please delete and destroy > all copies and attachments, and be advised that any review or > dissemination of, or the taking of any action in reliance on, the > information contained in or attached to this message is prohibited. > Unless specifically indicated, this message is not an offer to sell or > a solicitation of any investment products or other financial product or > service, an official confirmation of any transaction, or an official > statement of Sender. Subject to applicable law, Sender may intercept, > monitor, review and retain e-communications (EC) traveling through its > networks/systems and may produce any such EC to regulators, law > enforcement, in litigation and as required by law. > The laws of the country of each sender/recipient may impact the > handling of EC, and EC may be archived, supervised and produced in > countries other than the country in which you are located. This message > cannot be guaranteed to be secure or free of errors or viruses. > > References to "Sender" are references to any subsidiary of Bank of > America Corporation. Securities and Insurance Products: * Are Not FDIC > Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank > Deposit * Are Not a Condition to Any Banking Service or Activity * Are > Not Insured by Any Federal Government Agency. Attachments that are part > of this EC may have additional important disclosures and disclaimers, > which you should read. This message is subject to terms available at > the following link: > http://www.bankofamerica.com/emaildisclaimer . By messaging with Sender > you consent to the foregoing. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: xacml-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: xacml-help@lists.oasis-open.org > --------------------------------------------------------------------- To unsubscribe, e-mail: xacml-unsubscribe@lists.oasis-open.org For additional commands, e-mail: xacml-help@lists.oasis-open.org -- --------------------------------------------------------------------- To unsubscribe, e-mail: xacml-unsubscribe@lists.oasis-open.org For additional commands, e-mail: xacml-help@lists.oasis-open.org -- David Brossard, M.Eng, SCEA, CSTP VP Product Marketing & Customer Relations +46(0)760 25 85 75 Axiomatics AB Skeppsbron 40 S-111 30 Stockholm, Sweden http://www.linkedin.com/companies/536082 http://www.axiomatics.com http://twitter.com/axiomatics

David, From: xacml@lists.oasis-open.org [ mailto:xacml@lists.oasis-open.org ] On Behalf Of David Brossard Sent: Friday, May 04, 2012 5:11 AM To: Sinnema, Remon Cc: xacml@lists.oasis-open.org; robin@oasis-open.org Subject: Re: [xacml] RE: Media types > Ray, are you happy for me to use the profile i had initiated to define the JSON format? Didn't that have "HTTP" in the title? If so, can that be changed? Thanks, Ray