| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | human-readable nodelist format |
ac>>> I don't think you can, because FTS-5001 has made it ac>>> a standard. And you can't change standards, only add ac>>> to them. >> What about FTS-5000? >> I'm trying to have both standards replaced with something >> slightly more sensible and less crufty. ac> You can only extend the standard or obsolete it. That is, ac> unless the ZCs decide FTS-5000 isn't really a standard after ac> all, because it's "expired", which is unfair to all the ac> developers who wrote software in accordance with that spec ac> between the time it became a standard and the time it expired. ac> (In other words, having standards documents expire is a ac> really bad idea!) the reason the present/last FTSC decided to put in expiration dates was to force them to revisit the expiring standard and to update it or whatever was needed before it expired... this was supposed to keep the FTSC alive and also to ensure that we had current and up to date standards to work from... )\/(ark* Origin: (1:3634/12) SEEN-BY: 106/2000 120/544 123/500 132/500 400/300 490/33 633/104 260 262 270 SEEN-BY: 633/285 634/383 640/954 690/682 712/848 771/4020 774/605 2432/200 SEEN-BY: 3634/12 @PATH: 3634/12 106/2000 123/500 774/605 633/260 285 267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.