GDL Configurations
Collapse the table of content
Expand the table of content

GDL Configurations

GDL enables you to define dependencies in the data. The client does not need to be aware of dependencies; instead, the client specifies the configuration of interest when it requests a snapshot and the parser generates a snapshot that corresponds to that configuration.

For example, the prices that are charged for a phone call depend on the origin and destination points, the time of day and day of the week that the call is placed, the calling plan that is used, and so on. The prices for all possible outcomes can be represented by a large multidimensional array. This data can be represented by using GDL directives to define parameters to represent the various variables, like origin and destination points, time of day, calling plan, and so on. Other directives can be used to define the allowed values for these parameters. Still other directives specify how the data depends on the value of the parameters to be defined. After the data that represents the cost of the phone call (CostOfCall in the following example) has been expressed as a GDL source file, it can be parsed and any client can obtain the cost of making a phone call by simply creating a configuration that assigns the desired value to each parameter that is defined in the GDL.

For example, a client might compose a configuration that contains the following data.

OriginationPoint: Seattle
DestinationPoint: SanFrancisco
LengthOfCall: 10minutes
TimeOfDay: Night
CallingPlan: OneRate

And the snapshot that generated will contain one piece of data (out of all of the possible combinations) that might look like the following example.

CostOfCall: $0.49

A GDL snapshot can contain a complex data structure with thousands of items or just one. Each item in the snapshot can have its own set of dependencies on the configuration that the client is not aware of. The client must simply supply the configuration of interest, and the GDL parser will return the snapshot that represents the data that corresponds to that configuration.

In addition, GDL enables selected configurations to be excluded as "not allowed". For example, a printing device might not wish to allow duplex printing on transparent media. The GDL parser interface has methods to detect if the supplied configuration is allowed or disallowed; if the configuration is disallowed, the method will minimally alter the configuration so it is allowed. There are directives to define excluded configurations and directives to specify the relative importance of parameters so that a configuration can be corrected to resolve a conflict and the change can be made so it preserves the original intent as much as possible.

For more information about creating data that is configuration-dependent, see Creating GDL Configuration-Dependent Data.



Send comments about this topic to Microsoft

© 2016 Microsoft