Dear Benjamin, I found that following sections may be the proper place to restrict the 1-to-1 mapping. I think we can have restrictions in section 3.1 only or in 3.1&4.2.1&4.2.5. I've not decided which one is better and hope to have others' suggestions.
1. In section 3.1 Organization Identifier, add sentences at the end of this paragraph. A "role" attribute is used to represent the relationship that the organization has to the EPP object. Any given object MUST have at most one associated organization ID for any given role value. 2. In section 4.2.1, One or more <orgext:id> elements that contain the identifier of the organization. The "role" attribute is used to represent the relationship that the organization has to the object. Any given object MUST have at most one associated organization ID for any given role value. See Section 7.3 in [ID.draft-ietf-regext-org] for a list of values. 3. In section 4.2.5 One or more <orgext:id> elements that contain the identifier of the organization. The "role" attribute is used to represent the relationship that the organization has to the object. Any given object MUST have at most one associated organization ID for any given role value. See Section 7.3 in [ID.draft-ietf-regext-org] for a list of values. If we have the restrictions, the 1-to-multiple mapping cases are not necessary to be specified in this document. Regards, Linlin Linlin Zhou From: Benjamin Kaduk Date: 2018-10-31 20:43 To: Linlin Zhou CC: regext-chairs; Pieter Vandepitte; iesg; regext; draft-ietf-regext-org-ext Subject: Re: [regext] Benjamin Kaduk's Discuss on draft-ietf-regext-org-ext-09: (with DISCUSS and COMMENT) Dear Linlin, On Wed, Oct 31, 2018 at 02:19:45PM +0800, Linlin Zhou wrote: > Dear Benjamin, > Thanks for your input. We believe that relationship between an object and an > organization should be 1-to-1, one organization ID with just one role. > 1-to-many is an exception for the organization extension. Indeed that is our > concern, "the multiple examples may be overkill". Many thanks. I won't object to requiring the 1-to-1 mapping, as the impact of the restriction seems minor. I am not entirely sure where the best place to add some text that clarifies this restriction would be; perhaps in Section 4.2.1 where we describe the <orgext:id> elements in <create>? (I assume that the formal syntax does not provide for a maxOccurs that applies per-type.) It may also be worth a (non-normative) reminder in the <update> description that the semantics of <orgext:chg> are well-defined because there is only one entry per role value, but I'm not sure about that. Thanks, Benjamin _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
