Subj : Re: DogBone
To   : Nick Andre
From : John Dovey
Date : Sun Jun 27 2021 11:30:12

Glad to see you, Nick!

 NA> On 26 Jun 21  21:20:02, John Dovey said the following to Nick Andre:
 NA> 
 NA> JD> If the RC/ZC/IC is presented with a well formatted nodelist (or segment of
 NA> JD> one) why would they care how it was generated?
 NA> 
 NA> You'd be surprised... its not "how" its generated but "by whom".
 NA> 
 NA> The current nodelist management is one of checks and balances. It has worked,
 NA> currently works, will work tomorrow... the human element just works.
 NA> 
 NA> Where is the checks and balances in your project, and what obligation does an
 NA> RC or ZC have to accept your data?
 NA> 
 NA> Nick

I think you?re confusing my intentions. I?m talking about the creation of a  tool, just one more in the toolbox of the various people who have to do the work. I have no intention of usurping the role or function of anyone. 
Why I do want to try to do is create a tool that can be used by anyone in the chain to extract the data for whatever purposes they desire. If that is to use it to send up the chain as they trust the data, then that?s on them. It?s a pull not push scenario. 
Just like there is a tool to check the validity of the data (ErrChk) and another to assemble the data (nodenl) this *could* serve as a tool to collate the data, and format it, at the sysop/RC/ZC?s discretion and then feed into the various data checks and compilations etc.
I think you think that I?m talking about it replacing the entire nodelist process. That?s possible I suppose, but if it ever happened it would be because a plurality of the various role players decided that was what they wanted, not because of anything I?d prescribed.
I hope that makes it clearer.
All the best,
JD

*** [Netmail-to-Telegram address: 474405162@2:460/256]

.... Tag, you are IT!
--- tg BBS v0.7.1
 * Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

.