If the BOD is to be signed the signature element is included, otherwise it is not. Signature supports any digital signature that maybe used by an implementation of OAGIS. The qualifyingAgency identifies the agency that provided the format for the signature.

This element supports any digital signature specification that is available today and in the future. This is accomplished by not actually defining the content but by allowing the implementation to specify the digital signature to be used via an external XML Schema namespace declaration. The Signature element is defined to have any content from any other namespace.

This allows the user to carry a digital signature in the xml instance of a BOD. The choice of which digital signature to use is left up to the user and their integration needs.

Child Components

Qualifying Agency Id 0..1
Type Code 0..1
Scheme Identifier 0..1
Any Property 0..1

UML Class Model

The following link opens the SVG image in a separate browser tab.
You can save the file locally and use it, for example, in PowerPoint.
SVG File
@startuml Signature

class Signature {
    String [[/docs/qualifying-agency-id QualifyingAgencyId]]
    String [[/docs/type-code TypeCode]]
    String [[/docs/scheme-identifier SchemeIdentifier]]

class AnyProperty {
    [[/docs/any-property details]]→

Signature o-d- "0...1" AnyProperty

hide circle

Where Used

Following is a list of components that have Signature as a child component.


OAGi and its members welcome your feedback.

UUID: 262ce7445a3b429ba38d7facb9d38440

connectSpec (OAGIS) Version 10.11.1