For the initial support of DDMS 5.0 TSPI shapes, the DDMSence component will only return the raw XML of a shape. The TSPI specification is incredibly complex and multi-layered, and it is unclear how much value full-fledged classes would have. As use cases refine and more organizations adopt DDMS 5.0, the components can be revisited to provide more value-add.
{@table.header History}None. {@table.footer}{@table.header Nested Elements}None. {@table.footer}{@table.header Attributes}{@child.info gml:id|1|00001}{@child.info <srsAttributes>|0..*|00001}{@table.footer}{@table.header Validation Rules}{@ddms.rule Component must not be used before the DDMS version in which it was introduced.|Error|11111}{@ddms.rule The qualified name of this element must be correct.|Error|11111}{@ddms.rule The srsName must exist.|Error|11111}{@ddms.rule The gml:id must exist, and must be a valid NCName.|Error|11111}{@ddms.rule If the gml:pos has an srsName, it must match the srsName of this Point.|Error|11111}{@ddms.rule Warnings from any SRS attributes are claimed by this component.|Warning|11111}No additional validation is done on the TSPI shape at this time.
{@table.footer} @author Brian Uri! @since 2.2.0
|
|
|
|