Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved.
Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved.
Page 64 of 131 For example, the right to use an image processing service might be restricted to “visible
light” layers. The right to use a navigation service might be restricted to road layers appropriately augmented with network connectivity associations. Some examples are
given below.
The Massachusetts Roads Maintenance Agency is given the right to modify the roads layer of a combined New England database, as long as the records modified are part of
Massachusetts road system, by the following grant form:
• Grant
o Principal = Massachusetts Roads Maintenance Agency
o Resource = Combined New England SDI
→Layer = Roads…
o Right = modify
Input
→location “is contained in” Massachusetts The Massachusetts Emergency Dispatch is given the right to use navigation services
against the roads layer of a combined New England database, as long as the records used are part sufficient for use by navigation systems, by the following grant form:
• Grant
o Principal = Massachusetts Emergency Dispatch
o Resource = Combined New England SDI
→layer = Roads
→“accepted use” = navigation
o Right = execute
Process
• → Compliance = URN:OGC:NAVIGATE
9.5.3.3.8 Implementation conditions
Implementation rights shall be used to specify which implementations of functionality may be used in using a right. If unspecified, any provably conformant implementation of
the functionality is allowed. If specific implementations are identified they may be allowed or disallowed specifically.
This may be part of the trust model of the resource owner. For example, a company may wish to assure itself of the safety of the DRM by individually testing applications for
what they consider a level of security. In this case, the company may put up an online directory of software implementations that have passed this rigid test, and the licences it
issues of its resource might explicitly reference this online resource as the authority for what is to be considered “conformant” applications. More popular should be the
restriction of a processing right to those implementations that are registered as
Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved.
Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved.
Page 65 of 131 conformant by the standards associated testing authority. Thus, one licensor may require
that his resource only be served with an OGC-compliant implementation listed in the OGC registry supported by the Open Geospatial Consortium.
The default assumption is open world that is, all conformant implementations are allowed unless specifically disallowed. If this is not the intent, the licence should specify
a NULL specification-based right, and then specifically allow other implementations. An unmodified NULL specification effectively nullifies the right.
9.5.3.3.9 Parameter Range conditions
In functional rights that pass parameters, the allowable range of any parameter may be limited. The format of the range is type specific. For parameters that do not have any
ordering or dimensional structure, the usual representation is a white space separated list of values. Values with internal white space should be quoted or the white space
escaped appropriately for the licensing encoding mechanism being used. For ordered or dimensionally structured parameters, a set of ranges or extents should be specified in
accordance to the semantics of the parameter type.
For example, to change an earlier example to only allow viewing of Boston roads, assuming the view parameters are layer, extent and style, then the following grant could
be used:
• Grant
o Principal = …
o Resource = …
o Right = view
→extent “is contained within” Boston
9.5.3.3.10 Derived Right conditions
