API Reference
Gs1ValidationOptions
Controls GS1 parsing and validation strictness.
Inheritance
- Object
- Gs1ValidationOptions
Usage
This type appears in these public API surfaces even when no hand-authored example is attached directly to the page.
Accepted by parameters
- Method Gs1.Parse
- Method Gs1.ParseDigitalLink
- Method Gs1.TryValidate
- Method Gs1.Validate
- Method Gs1.ValidateDigitalLink
- Method Gs1Validator.ToElementString
- Method Gs1Validator.TryValidate
- Method Gs1Validator.Validate
- Method Gs1DigitalLink.Build
- Method Gs1DigitalLink.BuildCanonical
- Method Gs1DigitalLink.Parse
- Method Gs1DigitalLink.TryParse
- Method Gs1DigitalLink.Validate
Constructors
public Gs1ValidationOptions() #Inherited Methods
Properties
public Boolean AllowUnknownApplicationIdentifiers { get; set; } #Gets or sets whether unassigned AIs are accepted in bracketed input as variable-length fields. Raw element strings cannot safely infer the length of an unknown AI.
public Boolean ValidateAssociations { get; set; } #Gets or sets whether mandatory and mutually-exclusive AI association rules are evaluated.
public Boolean ValidateSemanticRules { get; set; } #Gets or sets whether GS1 semantic linters such as check-digit and date validation are evaluated.
public Boolean ValidateCharacterSets { get; set; } #Gets or sets whether data characters are checked against the official N, X, Y, and Z repertoires.
public Boolean AllowEmptyVariableLengthData { get; set; } #Gets or sets whether an empty variable-length field is accepted for compatibility with legacy encoders. Standards-conformance validation should leave this disabled.
public Boolean AllowRedundantFnc1Separators { get; set; } #Gets or sets whether redundant FNC1 separators after predefined-length fields are tolerated. Standards-conformance validation should leave this disabled.