complexType "sia:SimpleImageAccess"
Namespace:
http://www.ivoa.net/xml/SIA/v1.1
Content:
complex, 1 attribute, 16 elements
Defined:
globally in SIA.xsd; see XML source
Includes:
definitions of 7 elements
Used:
never
XML Representation Summary
<...
    standardID
 = 
 xs:anyURI
    >
   
Content: 
 validationLevel*, description?, interface*, imageServiceType, maxQueryRegionSize?, maxImageExtent?, maxImageSize?, maxFileSize?, maxRecords?, testQuery?
</...>
Content Model Elements (10):
description (type xs:string),
imageServiceType (type sia:ImageServiceType),
interface (type vr:Interface),
maxFileSize (type xs:positiveInteger),
maxImageExtent (type sia:SkySize),
maxImageSize (type xs:positiveInteger),
maxQueryRegionSize (type sia:SkySize),
maxRecords (type xs:positiveInteger),
testQuery (type sia:Query),
validationLevel (type vr:Validation)
Annotation
The capabilities of an SIA implementation.
Type Definition Detail
Type Derivation Tree
vr:Capability (extension)
  sia:SimpleImageAccess
XML Source (see within schema source)
<xs:complexType name="SimpleImageAccess">
<xs:annotation>
<xs:documentation>
The capabilities of an SIA implementation.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="vr:Capability">
<xs:sequence>
<xs:element name="imageServiceType" type="sia:ImageServiceType">
<xs:annotation>
<xs:documentation>
The class of image service: Cutout, Mosaic, Atlas, Pointed
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="1" minOccurs="0" name="maxQueryRegionSize" type="sia:SkySize">
<xs:annotation>
<xs:documentation>
The maximum image query region size, expressed in
decimal degrees. Not providing this element or
specifying a value of 360 degrees indicates that
there is no limit and the entire data collection
(entire sky) can be queried.
</xs:documentation>
<xs:documentation>
Not providing a value is the preferred way to indicate
that there is no limit.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="1" minOccurs="0" name="maxImageExtent" type="sia:SkySize">
<xs:annotation>
<xs:documentation>
An upper bound on a region of the sky that can
be covered by returned images. That is, no image
returned by this service will cover more than
this limit. Not providing this element or
specifying a value of 360 degrees indicates that
there is no fundamental limit to the region covered
by a returned image.
</xs:documentation>
<xs:documentation>
When the imageServiceType is &#8220;Cutout&#8221; or &#8220;Mosaic&#8221;,
this represents the largest area that can be requested.
In this case, the &#8220;no limit&#8221; value means that all-sky
images can be requested. When the type is &#8220;Atlas&#8221; or
&#8220;Pointed&#8221;, it should be a region that most closely
encloses largest images in the archive, and the &#8221;no
limit&#8221; value means that the archive contains all-sky
(or nearly so) images.
</xs:documentation>
<xs:documentation>
Not providing a value is the preferred way to indicate
that there is no limit.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="1" minOccurs="0" name="maxImageSize" type="xs:positiveInteger">
<xs:annotation>
<xs:documentation>
A measure of the largest image the service
can produce given as the maximum number of
pixels along the first or second axes.
Not providing a value indicates that there is
no effective limit to the size of the images
that can be returned.
</xs:documentation>
<xs:documentation>
This is primarily relevant when the imageServiceType
is &#8220;Cutout&#8221; or &#8220;Mosaic&#8221;, indicating the largest
image that can be created. When the imageServiceType
is &#8220;Atlas&#8221; or &#8220;Pointed&#8221;, this should be specified only
when there are static images in the archive that can
be searched for but not returned because they are
too big.
</xs:documentation>
<xs:documentation>
When a service is more fundamentally limited
by the total number of pixels in the image, this
value should be set to the square-root of that
number. This number will then represent a
lower limit on the maximum length of a side.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="1" minOccurs="0" name="maxFileSize" type="xs:positiveInteger">
<xs:annotation>
<xs:documentation>
The maximum image file size in bytes. Not providing
a value indicates that there is no effective limit
the size of files that can be returned.
</xs:documentation>
<xs:documentation>
This is primarily relevant when the imageServiceType
is &#8220;Cutout&#8221; or &#8220;Mosaic&#8221;, indicating the largest
files that can be created. When the imageServiceType
is &#8220;Atlas&#8221; or &#8220;Pointed&#8221;, this should be specified only
when there are static images in the archive that can
be searched for but not returned because they are
too big.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="1" minOccurs="0" name="maxRecords" type="xs:positiveInteger">
<xs:annotation>
<xs:documentation>
The largest number of records that the Image Query web
method will return. Not providing this value means that
there is no effective limit.
</xs:documentation>
<xs:documentation>
This does not refer to the total number of images in
the archive but rather maximum number of records the
service is capable of returning. A limit that is
greater than the number of images available in the
archive is equivalent to their being no effective
limit. (See RM, Hanisch 2007.)
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="1" minOccurs="0" name="testQuery" type="sia:Query">
<xs:annotation>
<xs:documentation>
a set of query parameters that is expected
to produce at least one matched record which
can be used to test the service.
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
Attribute Detail (all declarations; 1)
standardID
Type:
xs:anyURI
Use:
optional
Defined:
locally within vr:Capability complexType
Annotation 1 [src]:
A URI identifier for a standard service.
Annotation 2 [src]:
This provides a unique way to refer to a service specification standard, such as a Simple Image Access service. The use of an IVOA identifier here implies that a VOResource description of the standard is registered and accessible.
XML Source (see within schema source)
<xs:attribute name="standardID" type="xs:anyURI">
<xs:annotation>
<xs:documentation>
A URI identifier for a standard service.
</xs:documentation>
<xs:documentation>
This provides a unique way to refer to a service
specification standard, such as a Simple Image Access service.
The use of an IVOA identifier here implies that a
VOResource description of the standard is registered and
accessible.
</xs:documentation>
</xs:annotation>
</xs:attribute>
Content Element Detail (all declarations; 16)
description
Type:
xs:string, simple content
Defined:
locally within vr:Capability complexType
Annotation 1 [src]:
A human-readable description of what this capability provides as part of the over-all service
Annotation 2 [src]:
Use of this optional element is especially encouraged when this capability is non-standard and is one of several capabilities listed.
XML Source (see within schema source)
<xs:element minOccurs="0" name="description" type="xs:string">
<xs:annotation>
<xs:documentation>
A human-readable description of what this capability
provides as part of the over-all service
</xs:documentation>
<xs:documentation>
Use of this optional element is especially encouraged when
this capability is non-standard and is one of several
capabilities listed.
</xs:documentation>
</xs:annotation>
</xs:element>
description
Type:
xs:string, simple content
Defined:
locally within vr:Capability complexType
Annotation 1 [src]:
A human-readable description of what this capability provides as part of the over-all service
Annotation 2 [src]:
Use of this optional element is especially encouraged when this capability is non-standard and is one of several capabilities listed.
XML Source (see within schema source)
<xs:element minOccurs="0" name="description" type="xs:string">
<xs:annotation>
<xs:documentation>
A human-readable description of what this capability
provides as part of the over-all service
</xs:documentation>
<xs:documentation>
Use of this optional element is especially encouraged when
this capability is non-standard and is one of several
capabilities listed.
</xs:documentation>
</xs:annotation>
</xs:element>
description
Type:
xs:string, simple content
Defined:
locally within vr:Capability complexType
Annotation 1 [src]:
A human-readable description of what this capability provides as part of the over-all service
Annotation 2 [src]:
Use of this optional element is especially encouraged when this capability is non-standard and is one of several capabilities listed.
XML Source (see within schema source)
<xs:element minOccurs="0" name="description" type="xs:string">
<xs:annotation>
<xs:documentation>
A human-readable description of what this capability
provides as part of the over-all service
</xs:documentation>
<xs:documentation>
Use of this optional element is especially encouraged when
this capability is non-standard and is one of several
capabilities listed.
</xs:documentation>
</xs:annotation>
</xs:element>
imageServiceType
Type:
sia:ImageServiceType, simple content
Defined:
locally within (this) sia:SimpleImageAccess complexType
The class of image service: Cutout, Mosaic, Atlas, Pointed
XML Source (see within schema source)
<xs:element name="imageServiceType" type="sia:ImageServiceType">
<xs:annotation>
<xs:documentation>
The class of image service: Cutout, Mosaic, Atlas, Pointed
</xs:documentation>
</xs:annotation>
</xs:element>
interface
Type:
vr:Interface, complex content
Defined:
locally within vr:Capability complexType
Annotation 1 [src]:
a description of how to call the service to access this capability
Annotation 2 [src]:
Since the Interface type is abstract, one must describe the interface using a subclass of Interface, denoting it via xsi:type.
Annotation 3 [src]:
Multiple occurences can describe different interfaces to the logically same capability, i.e. data or functionality. That is, the inputs accepted and the output provides should be logically the same. For example, a WebBrowser interface given in addition to a WebService interface would simply provide an interactive, human-targeted interface to the underlying WebService interface.
XML Source (see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="interface" type="vr:Interface">
<xs:annotation>
<xs:documentation>
a description of how to call the service to access
this capability
</xs:documentation>
<xs:documentation>
Since the Interface type is abstract, one must describe
the interface using a subclass of Interface, denoting
it via xsi:type.
</xs:documentation>
<xs:documentation>
Multiple occurences can describe different interfaces to
the logically same capability, i.e. data or functionality.
That is, the inputs accepted and the output provides should
be logically the same. For example, a WebBrowser interface
given in addition to a WebService interface would simply
provide an interactive, human-targeted interface to the
underlying WebService interface.
</xs:documentation>
</xs:annotation>
</xs:element>
interface
Type:
vr:Interface, complex content
Defined:
locally within vr:Capability complexType
Annotation 1 [src]:
a description of how to call the service to access this capability
Annotation 2 [src]:
Since the Interface type is abstract, one must describe the interface using a subclass of Interface, denoting it via xsi:type.
Annotation 3 [src]:
Multiple occurences can describe different interfaces to the logically same capability, i.e. data or functionality. That is, the inputs accepted and the output provides should be logically the same. For example, a WebBrowser interface given in addition to a WebService interface would simply provide an interactive, human-targeted interface to the underlying WebService interface.
XML Source (see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="interface" type="vr:Interface">
<xs:annotation>
<xs:documentation>
a description of how to call the service to access
this capability
</xs:documentation>
<xs:documentation>
Since the Interface type is abstract, one must describe
the interface using a subclass of Interface, denoting
it via xsi:type.
</xs:documentation>
<xs:documentation>
Multiple occurences can describe different interfaces to
the logically same capability, i.e. data or functionality.
That is, the inputs accepted and the output provides should
be logically the same. For example, a WebBrowser interface
given in addition to a WebService interface would simply
provide an interactive, human-targeted interface to the
underlying WebService interface.
</xs:documentation>
</xs:annotation>
</xs:element>
interface
Type:
vr:Interface, complex content
Defined:
locally within vr:Capability complexType
Annotation 1 [src]:
a description of how to call the service to access this capability
Annotation 2 [src]:
Since the Interface type is abstract, one must describe the interface using a subclass of Interface, denoting it via xsi:type.
Annotation 3 [src]:
Multiple occurences can describe different interfaces to the logically same capability, i.e. data or functionality. That is, the inputs accepted and the output provides should be logically the same. For example, a WebBrowser interface given in addition to a WebService interface would simply provide an interactive, human-targeted interface to the underlying WebService interface.
XML Source (see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="interface" type="vr:Interface">
<xs:annotation>
<xs:documentation>
a description of how to call the service to access
this capability
</xs:documentation>
<xs:documentation>
Since the Interface type is abstract, one must describe
the interface using a subclass of Interface, denoting
it via xsi:type.
</xs:documentation>
<xs:documentation>
Multiple occurences can describe different interfaces to
the logically same capability, i.e. data or functionality.
That is, the inputs accepted and the output provides should
be logically the same. For example, a WebBrowser interface
given in addition to a WebService interface would simply
provide an interactive, human-targeted interface to the
underlying WebService interface.
</xs:documentation>
</xs:annotation>
</xs:element>
maxFileSize
Type:
xs:positiveInteger, simple content
Defined:
locally within (this) sia:SimpleImageAccess complexType
Annotation 1 [src]:
The maximum image file size in bytes. Not providing a value indicates that there is no effective limit the size of files that can be returned.
Annotation 2 [src]:
This is primarily relevant when the imageServiceType is “Cutout” or “Mosaic”, indicating the largest files that can be created. When the imageServiceType is “Atlas” or “Pointed”, this should be specified only when there are static images in the archive that can be searched for but not returned because they are too big.
XML Source (see within schema source)
<xs:element maxOccurs="1" minOccurs="0" name="maxFileSize" type="xs:positiveInteger">
<xs:annotation>
<xs:documentation>
The maximum image file size in bytes. Not providing
a value indicates that there is no effective limit
the size of files that can be returned.
</xs:documentation>
<xs:documentation>
This is primarily relevant when the imageServiceType
is &#8220;Cutout&#8221; or &#8220;Mosaic&#8221;, indicating the largest
files that can be created. When the imageServiceType
is &#8220;Atlas&#8221; or &#8220;Pointed&#8221;, this should be specified only
when there are static images in the archive that can
be searched for but not returned because they are
too big.
</xs:documentation>
</xs:annotation>
</xs:element>
maxImageExtent
Type:
sia:SkySize, complex content
Defined:
locally within (this) sia:SimpleImageAccess complexType
Annotation 1 [src]:
An upper bound on a region of the sky that can be covered by returned images. That is, no image returned by this service will cover more than this limit. Not providing this element or specifying a value of 360 degrees indicates that there is no fundamental limit to the region covered by a returned image.
Annotation 2 [src]:
When the imageServiceType is “Cutout” or “Mosaic”, this represents the largest area that can be requested. In this case, the “no limit” value means that all-sky images can be requested. When the type is “Atlas” or “Pointed”, it should be a region that most closely encloses largest images in the archive, and the ”no limit” value means that the archive contains all-sky (or nearly so) images.
Annotation 3 [src]:
Not providing a value is the preferred way to indicate that there is no limit.
XML Source (see within schema source)
<xs:element maxOccurs="1" minOccurs="0" name="maxImageExtent" type="sia:SkySize">
<xs:annotation>
<xs:documentation>
An upper bound on a region of the sky that can
be covered by returned images. That is, no image
returned by this service will cover more than
this limit. Not providing this element or
specifying a value of 360 degrees indicates that
there is no fundamental limit to the region covered
by a returned image.
</xs:documentation>
<xs:documentation>
When the imageServiceType is &#8220;Cutout&#8221; or &#8220;Mosaic&#8221;,
this represents the largest area that can be requested.
In this case, the &#8220;no limit&#8221; value means that all-sky
images can be requested. When the type is &#8220;Atlas&#8221; or
&#8220;Pointed&#8221;, it should be a region that most closely
encloses largest images in the archive, and the &#8221;no
limit&#8221; value means that the archive contains all-sky
(or nearly so) images.
</xs:documentation>
<xs:documentation>
Not providing a value is the preferred way to indicate
that there is no limit.
</xs:documentation>
</xs:annotation>
</xs:element>
maxImageSize
Type:
xs:positiveInteger, simple content
Defined:
locally within (this) sia:SimpleImageAccess complexType
Annotation 1 [src]:
A measure of the largest image the service can produce given as the maximum number of pixels along the first or second axes. Not providing a value indicates that there is no effective limit to the size of the images that can be returned.
Annotation 2 [src]:
This is primarily relevant when the imageServiceType is “Cutout” or “Mosaic”, indicating the largest image that can be created. When the imageServiceType is “Atlas” or “Pointed”, this should be specified only when there are static images in the archive that can be searched for but not returned because they are too big.
Annotation 3 [src]:
When a service is more fundamentally limited by the total number of pixels in the image, this value should be set to the square-root of that number. This number will then represent a lower limit on the maximum length of a side.
XML Source (see within schema source)
<xs:element maxOccurs="1" minOccurs="0" name="maxImageSize" type="xs:positiveInteger">
<xs:annotation>
<xs:documentation>
A measure of the largest image the service
can produce given as the maximum number of
pixels along the first or second axes.
Not providing a value indicates that there is
no effective limit to the size of the images
that can be returned.
</xs:documentation>
<xs:documentation>
This is primarily relevant when the imageServiceType
is &#8220;Cutout&#8221; or &#8220;Mosaic&#8221;, indicating the largest
image that can be created. When the imageServiceType
is &#8220;Atlas&#8221; or &#8220;Pointed&#8221;, this should be specified only
when there are static images in the archive that can
be searched for but not returned because they are
too big.
</xs:documentation>
<xs:documentation>
When a service is more fundamentally limited
by the total number of pixels in the image, this
value should be set to the square-root of that
number. This number will then represent a
lower limit on the maximum length of a side.
</xs:documentation>
</xs:annotation>
</xs:element>
maxQueryRegionSize
Type:
sia:SkySize, complex content
Defined:
locally within (this) sia:SimpleImageAccess complexType
Annotation 1 [src]:
The maximum image query region size, expressed in decimal degrees. Not providing this element or specifying a value of 360 degrees indicates that there is no limit and the entire data collection (entire sky) can be queried.
Annotation 2 [src]:
Not providing a value is the preferred way to indicate that there is no limit.
XML Source (see within schema source)
<xs:element maxOccurs="1" minOccurs="0" name="maxQueryRegionSize" type="sia:SkySize">
<xs:annotation>
<xs:documentation>
The maximum image query region size, expressed in
decimal degrees. Not providing this element or
specifying a value of 360 degrees indicates that
there is no limit and the entire data collection
(entire sky) can be queried.
</xs:documentation>
<xs:documentation>
Not providing a value is the preferred way to indicate
that there is no limit.
</xs:documentation>
</xs:annotation>
</xs:element>
maxRecords
Type:
xs:positiveInteger, simple content
Defined:
locally within (this) sia:SimpleImageAccess complexType
Annotation 1 [src]:
The largest number of records that the Image Query web method will return. Not providing this value means that there is no effective limit.
Annotation 2 [src]:
This does not refer to the total number of images in the archive but rather maximum number of records the service is capable of returning. A limit that is greater than the number of images available in the archive is equivalent to their being no effective limit. (See RM, Hanisch 2007.)
XML Source (see within schema source)
<xs:element maxOccurs="1" minOccurs="0" name="maxRecords" type="xs:positiveInteger">
<xs:annotation>
<xs:documentation>
The largest number of records that the Image Query web
method will return. Not providing this value means that
there is no effective limit.
</xs:documentation>
<xs:documentation>
This does not refer to the total number of images in
the archive but rather maximum number of records the
service is capable of returning. A limit that is
greater than the number of images available in the
archive is equivalent to their being no effective
limit. (See RM, Hanisch 2007.)
</xs:documentation>
</xs:annotation>
</xs:element>
testQuery
Type:
sia:Query, complex content
Defined:
locally within (this) sia:SimpleImageAccess complexType
a set of query parameters that is expected to produce at least one matched record which can be used to test the service.
XML Source (see within schema source)
<xs:element maxOccurs="1" minOccurs="0" name="testQuery" type="sia:Query">
<xs:annotation>
<xs:documentation>
a set of query parameters that is expected
to produce at least one matched record which
can be used to test the service.
</xs:documentation>
</xs:annotation>
</xs:element>
validationLevel
Type:
vr:Validation, simple content
Defined:
locally within vr:Capability complexType
Annotation 1 [src]:
A numeric grade describing the quality of the capability description and interface, when applicable, to be used to indicate the confidence an end-user can put in the resource as part of a VO application or research study.
Annotation 2 [src]:
See vr:ValidationLevel for an explanation of the allowed levels.
XML Source (see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="validationLevel" type="vr:Validation">
<xs:annotation>
<xs:documentation>
A numeric grade describing the quality of the
capability description and interface, when applicable,
to be used to indicate the confidence an end-user
can put in the resource as part of a VO application
or research study.
</xs:documentation>
<xs:documentation>
See vr:ValidationLevel for an explanation of the
allowed levels.
</xs:documentation>
</xs:annotation>
</xs:element>
validationLevel
Type:
vr:Validation, simple content
Defined:
locally within vr:Capability complexType
Annotation 1 [src]:
A numeric grade describing the quality of the capability description and interface, when applicable, to be used to indicate the confidence an end-user can put in the resource as part of a VO application or research study.
Annotation 2 [src]:
See vr:ValidationLevel for an explanation of the allowed levels.
XML Source (see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="validationLevel" type="vr:Validation">
<xs:annotation>
<xs:documentation>
A numeric grade describing the quality of the
capability description and interface, when applicable,
to be used to indicate the confidence an end-user
can put in the resource as part of a VO application
or research study.
</xs:documentation>
<xs:documentation>
See vr:ValidationLevel for an explanation of the
allowed levels.
</xs:documentation>
</xs:annotation>
</xs:element>
validationLevel
Type:
vr:Validation, simple content
Defined:
locally within vr:Capability complexType
Annotation 1 [src]:
A numeric grade describing the quality of the capability description and interface, when applicable, to be used to indicate the confidence an end-user can put in the resource as part of a VO application or research study.
Annotation 2 [src]:
See vr:ValidationLevel for an explanation of the allowed levels.
XML Source (see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="validationLevel" type="vr:Validation">
<xs:annotation>
<xs:documentation>
A numeric grade describing the quality of the
capability description and interface, when applicable,
to be used to indicate the confidence an end-user
can put in the resource as part of a VO application
or research study.
</xs:documentation>
<xs:documentation>
See vr:ValidationLevel for an explanation of the
allowed levels.
</xs:documentation>
</xs:annotation>
</xs:element>
This XML schema documentation has been generated with DocFlex/XML RE 1.8.0 using DocFlex/XML XSDDoc 2.2.0 template set.
DocFlex/XML RE is a reduced edition of DocFlex/XML, which is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually using a high quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML.
DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-end XML Schema documentation generator with simultaneous support of framed multi-file HTML, single-file HTML and RTF output formats. (More formats are planned in the future).
A commercial license for "DocFlex/XML XSDDoc" will allow you:
  • To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support more than 300 template parameters (working the same as "options" of an ordinary doc-gen), which will give you an unprecedented control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To enable/disable documenting of the initial, imported, included and redefined XML schemas selectively.
  • To document local element components both globally and locally (similar to attributes).
  • To enable/disable reproducing of namespace prefixes.
  • To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
  • To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
  • To use PlainDoc.tpl main template to generate all the XML schema documentation in the form of a single HTML file.
  • To use the same template to generate the incredible quality RTF documentation.
  • To document only selected XML schema components specified by name.
  • To remove this very advertisement text
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML SDK and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required!
But this is not all. In addition to it, a commercial license for DocFlex/XML SDK will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only. And, of course, you could develop any template applications by your own!
Please note: By purchasing a license for this software, you not only acquire a useful tool, you will also make an important investment in its future development, the result of which you could enjoy later by yourself. Every single your purchase matters and makes a difference for us!
To buy a license, please follow this link: http://www.filigris.com/shop/