Relative Content

Tag Archive for asn.1

Use of Abstract Syntax Notation (ASN.1)

The problem of Electronic Data Interchange over networks is well known and understood. Today, the most common formats for data interchange are things like XML and JSON. There are various pros and cons of using one format over the other, and certain formats lend themselves better to certain data-sets.

Use of Abstract Syntax Notation (ASN.1)

The problem of Electronic Data Interchange over networks is well known and understood. Today, the most common formats for data interchange are things like XML and JSON. There are various pros and cons of using one format over the other, and certain formats lend themselves better to certain data-sets.

Use of Abstract Syntax Notation (ASN.1)

The problem of Electronic Data Interchange over networks is well known and understood. Today, the most common formats for data interchange are things like XML and JSON. There are various pros and cons of using one format over the other, and certain formats lend themselves better to certain data-sets.

Effect of COMPONENT OF constraint on extensibility

Given the following schema, I contend that ConstrainedContentSequence is not extensible, does not allow values having more than 8 Content values, and that a value of type ConstrainedContentSequence would be encoded in PER without an extension bit. A colleague finds this surprising because the added constraint is aimed at the component type of the SEQUENCE OF, not at the SEQUENCE OF itself, and yet the extensibility on the SEQUENCE OF type is removed. Technically, however, the added constraint is a constraint on the SEQUENCE OF; it just has the effect of constraining the component values.