<div dir="ltr">I support.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Dec 18, 2019 at 11:51 AM Darrell Budic <<a href="mailto:darrell@unitedix.net">darrell@unitedix.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;">Works for me, I support. <div><br></div><div> -Darrell<br><div><br><blockquote type="cite"><div>On Dec 18, 2019, at 10:45 AM, Chris Caputo <<a href="mailto:ccaputo@alt.net" target="_blank">ccaputo@alt.net</a>> wrote:</div><br><div><span style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">On Wed, 18 Dec 2019, Arnold Nipper wrote:</span><br style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><blockquote type="cite" style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">On 18.12.2019 16:51, Chris Caputo wrote:<br><blockquote type="cite">On Wed, 18 Dec 2019, Arnold Nipper wrote:<br><blockquote type="cite">All<br><br>On 18.12.2019 16:09, Chris Caputo wrote:<br><blockquote type="cite">On Wed, 18 Dec 2019, Arnold Nipper wrote:<br><br><blockquote type="cite">On 18.12.2019 00:54, Filiz Yilmaz wrote:<br><br><blockquote type="cite">It is mainly changing:<br><br>“This Policy Document will include a clear description of each object,<br>sub-object, and associated data, respectively, as well as*which type of<br>user (network, IXP, etc.) *should be allowed to create and update them. “<br><br>To: <br>“This Policy Document will include a clear description of each object,<br>sub-object, and associated data, respectively, as well as well as *who*<br>should be allowed to create and update them.”<br><br>If you have any objections to this, you can raise them until 24 Dec on<br>the mailing list. <br>After that I will get the Scope on the website changed too. <br><br></blockquote>for me it's unclear what is meant by "sub-object" and "associated data".<br>For me there are only objects (i.e. fac, ix, ixfac, ixlan, ixpfx, net,<br>netfac, netixlan and poc. And as-set which imho shouldn't be there) and<br>relations between these objects expressed by ids. E.g. in netixlan we<br>find net_id and ix_id (and ixlan_id, but this id in turn is pointed to<br>by the the very same ix_id).<br></blockquote>Arnold, as I understand it, the Scope is meant to be broad and not address<span> </span><br>specific present-day PeeringDB object types.<br><br></blockquote><br>so what is "each object" then referring to?<br></blockquote><br>It is referring to PeeringDB objects. I just meant they aren't addressed<span> </span><br>specificially in the Scope.<br><br><blockquote type="cite">I'm not a native speaker, but would rephrase this to<br></blockquote><br>I think you write English quite well, actually.<br><br><blockquote type="cite">“This Policy Document will include a clear description of each object<br>and the relation between each other, as well as well as the user<br>permission system to create, update, and delete objects".<br></blockquote><br>In the most recent conference call we tried to address your comment in the<span> </span><br>Policy Document:<br><br> - "which type of user (network, IXP, etc.)"<br> - There is no distinction between users regarding their network, IXP etc<br><br>by getting away from "user" with a change to "who" since we are talking<span> </span><br>about the type of user (ie., their perspective on a given object), not the<span> </span><br>PeeringDB "user" object specifically. Thus if "user permission system" is<span> </span><br>replaced with "who should be allowed" in your verbage, ala:<br><br> “This Policy Document will include a clear description of each object<br> and the relation between each other, as well as well as who should be<span> </span><br> allowed to create, update, and delete objects".<br><br>Would you be comfortable with that?<br><br></blockquote><br>Fine by me. Now you only have to deal with Job's suggestion which imho<br>is a fine one as well.<br></blockquote><br style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><span style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">:-)</span><br style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><br style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><span style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">On Wed, 18 Dec 2019, Job Snijders wrote:</span><br style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><blockquote type="cite" style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">We should replace "object" with "data element"<br></blockquote><br style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><span style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">So that gives:</span><br style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><br style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><span style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline"> - “This Policy Document will include a clear description of each data<span> </span></span><br style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><span style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline"> element and the relation between each other, as well as who should be<span> </span></span><br style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><span style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline"> allowed to create, update, and delete them".</span><br style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><br style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><span style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">Anyone else support this as the change to make to the Scope? (I do too.)</span><br style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><br style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><span style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">Chris--<span> </span></span><br style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><span style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">DataOwnership-TF mailing list</span><br style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><a href="mailto:DataOwnership-TF@lists.peeringdb.com" style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">DataOwnership-TF@lists.peeringdb.com</a><br style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><a href="https://lists.peeringdb.com/cgi-bin/mailman/listinfo/dataownership-tf" style="font-family:FantasqueSansMono-Regular;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">https://lists.peeringdb.com/cgi-bin/mailman/listinfo/dataownership-tf</a></div></blockquote></div><br></div></div>-- <br>
DataOwnership-TF mailing list<br>
<a href="mailto:DataOwnership-TF@lists.peeringdb.com" target="_blank">DataOwnership-TF@lists.peeringdb.com</a><br>
<a href="https://lists.peeringdb.com/cgi-bin/mailman/listinfo/dataownership-tf" rel="noreferrer" target="_blank">https://lists.peeringdb.com/cgi-bin/mailman/listinfo/dataownership-tf</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><b>Bill Marantz</b><br>Principal Network Engineer</div><div dir="ltr">Backbone Engineering<br>Mobile: 848-404-4613<div>email: <a href="mailto:ihamilton@salesforce.com" style="color:rgb(17,85,204)" target="_blank">wmarantz@salesforce.com</a><br></div></div></div></div></div></div><br></div></div></div></div></div>