Cart
[Home] [By Thread] [By Date] [Recent Entries]
For every feature of SGML that was taken out of XML, there was an existing application that used it. If you go down this path, you may be required to consume the parent language. XML killed SGML. ASN.2 may be required to do the same. If so, start the debate on the new name now as that debate will consume a lot of cycles later. Then you can consider the parent language the pioneering effort that secured your future just as SGML/HyTime/DSSSL secured the future of XML and other markup systems to come. There is nothing wrong with profiting twice from one technology if you are certain that profit comes of improvements and the enabling of larger markets. Pioneers secure the future; ranchers develop it; cowboys work it; dudes sell it. Pick a role. len From: John Larmouth [mailto:j.larmouth@s...] Suggestions for an ASN.2 that is a cut-down, basic, ASN.1 abound. But the problem is that for every feature you look at, there are real specicifications out there that use it!
|
