"the laughable response was that 5.5.1 was/is only a draft" - why is this laughable? If you aim to work from standards, you need to follow standards. Not drafts. It's not as if the 5.5.1 drafts are even internally consistent. I have, on several occasions, wanted to find the commentary on why certain things had changed in that draft, and I have failed, so clearly it's an incomplete draft. With that in mind, is anyone in a position to confirm that any given draft is complete? I've a suspicion, as well, that I have seen different versions of the draft.
"The very first product to support 5.5.1 before the ink was even dry was PAF 5.0". So? All that confirms is that the GEDCOM Standard and PAF were under different management. In any case, last time I looked, PAF didn't support FROM ... TO dates, so its support of 5.5.1 must be vague at best.
Having said all that, there would be be, I agree, many advantages to supporting "5.5.1". There is a Wish List request for exactly this - see
http://www.fhug.org.uk/wishlist/wldispl ... lwlref=390 - this has the score of 133, taking it into the top 1/8th of requests - just. Of course, there'd probably need to be arbitrary decisions about which version of 5.5.1 were to be supported and whether it was indeed internally consistent.
There is also, I have to say, a pig in making FH 5.5.1
optionally compliant - user defined attributes were proposed for 5.5.1 (good!) in a manner totally different from the way FH has done them (oh bother!).
So while I support the adoption of 5.5.1 (whatever it is), I don't agree that it's a simple no-brainer with no issues.