Cart
[Home] [By Thread] [By Date] [Recent Entries]
Claude L Bullard wrote: > If you decide to subset ASN.1, you will need a > considerable amount of fortitude. You may even > have to give away the credit. Be sure to keep > ALL the documentation to fight the patent predators. Why would we subset ASN.1? The worst "excesses" in its definition were removed almost a decade ago when macros were trashed. What is there in ASN.1 that you would take out today? As it stands, everything that is in there is being used by someone and given that ASN.1 is used to drive our cell phone system, much of the security world (certificates), LDAP, SNMP, etc. it is unlikely that you'll find bits that can be removed without causing extreme pain in some very sensitive place. If you take things out, you'll just be bifurcating the world again. You'll have ASN.1 people fighting to get features put back into ASN.2 and you'll have people enhancing ASN.2 to include things already handled well by ASN.1. Not good. You haven't made it clear what would be gained by subsetting ASN.1. What does ASN.1 have that ASN.2 shouldn't have? In order to have enough richness of expression to permit the broad range of XML to be described, ASN.1 needs a fairly large percentage of its current expressiveness... bob wyman
|
