Subj : slightly different format
To   : Maurice Kinal
From : Carol Shenkenberger
Date : Fri Jan 01 2021 09:43:53

  Re: slightly different format
  By: Maurice Kinal to Carol Shenkenberger on Sat Dec 26 2020 09:53 pm

 > -={ Corrected DateTime for those in the know: 2020-12-26 21:53:58 +0000 }=-
 > 
 > Hey Carol!
 > 
 >  > ... Werig sceal se wiþ winde roweþ.
 >  >     Weary shall he be who rows against the wind.
 > 
 >  CS> Hehehe,
 > 
 > Truer words were never spoken even after well over 1000 years have gone by.
 > Did Anglo-Saxons have fidonet nodes?  If so then I think I give new meaning 
 > backwards compatibilty.
 > 
 >  CS> here's a little secret.  Anyone can make a proposal.  It just
 >  CS> doesn't get changed to a 'standard' unless widely in use.
 > 
 > So I've noticed.  What do you think my odds are?  So far I've only heard the
 > word 'impossible' which is probably what motivated me to take the chance.  A
 > without the election being called I thought I'd give it a shot if for no oth
 > reson than to increase the traffic here, and on that count I think I might h
 > outdone even an election here would have on this regard.
 > 
 > And on that note I believe I am a winner.  :-)
 > 
 > Life is good,
 > Maurice
 > 
 > ... Don't cry for me I have vi.

Well, from what I see it's the normal resistance, mostly because the approach
was more like 'asking them' so got the problems.  The way to do it is write it,
then leave room for a cross compatible (back compatible) mode as a 3rd party
utility.  Best to make one for that too along with it.  Open source it and has
a chance, then make proposal.

It's not for the FTSC to deny a *proposal*.  It's only for them to document
when it becomes a STANDARD.

Eventually proposals go to a backup library if not used.  The only ones that
completely went away seem to be the FAQ series, which *documented* existing
standards but was never a proposal (it was due to be written to one but was
deleted somewhere between 2006-2008 it seems).

Recently recovered a partial document that clearly was my own wording (hard for
me to not recognize my own) but had other edits in another's style added to it.
Possibly Ozzy Nixon?  Not sure.

Planning to do some work on it this weekend.

All the document does is piece together some of the variety in nodelist
'styles' into a preferred format easier for developers to base nodelist tools
on.  For ex:  Special ports go after the Connectivity tab (IBN etc.) and INA
carries no port but has the FQDN.  FQDN for a specific connection can be added
after connecitvity port if different from INA and in which case by preference,
over rides INA when using that connection protocol.

  xxcarol
--- SBBSecho 2.11-Win32
 * Origin: SHENK'S EXPRESS, shenks.synchro.net (1:275/100)

.