Proposal to improve AIXM Temporality

Find the latest AIXM Temporality document on the AIXM website: http://www.aixm.aero/gallery/content/public/AIXM51/AIXM%20Temporality%201.0.pdf

Clarify omitted correction numbers for non-SNAPSHOT time slices

Related AIXM CCB Issue: https://aixmccb.atlassian.net/browse/AIXM-153?jql=project%20%3D%20AIXM

The "AIXM Temporality 1.0" is not very clear about correction numbers. It assumes that every non-SNAPSHOT time slice has a sequenceNumber and correctionNumber, but in the examples, the correctionNumber is often obmitted. There may be an implicit convention that a missing correctionNumber means "correctionNumber=0", but this is nowhere explicitly stated.

So this convention correctionNumber=0 should be stated explicitly.

In addition, we propose to add a business rule ("best practice") which requires an explicit correctionNumber for all non-SNAPSHOT time slices. If there is an agreement, this "best practice" should also be stated in the AIXM Temporality document. In that case, the following XSLT script should be run over the Donlon test data:
<xsl:stylesheet xmlns:aixm="http://www.aixm.aero/schema/5.1" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
  <xsl:output method="xml"/>
  <xsl:template match="aixm:sequenceNumber[../aixm:interpretation!='SNAPSHOT' and not(../aixm:correctionNumber)]">
    <xsl:copy-of select="."/>
    <xsl:text>&#xa;&#9;&#9;&#9;&#9;&#9;</xsl:text>
    <aixm:correctionNumber>0</aixm:correctionNumber>
  </xsl:template>
  <xsl:template match="@*|node()">
    <xsl:copy>
      <xsl:apply-templates select="@*|node()"/>
    </xsl:copy>
  </xsl:template>
</xsl:stylesheet>

Clarify featureLifeTime property for SNAPSHOTs

The document doesn't clearly say whether a SNAPSHOT contains the featureLifeTime property or not. Assuming it does contain the featureLifeTime: How is it defined? Applying the same rules as for other properties, this would be the featureLifeTime at this point in time. On the other hand, it would make a lot of sense if the featureLifeTime was the full featureLifeTime (if it is known).

This is an important detail for implementing the WFS Temporality Extension.

For example, consider a feature with 3 BASELINEs and a lifespan over 3 months:
  • interpretation = BASELINE, validTime = [2014-01-01,2014-02-01), featureLifeTime = [2014-01-01,indeterminate)
  • interpretation = BASELINE, validTime = [2014-02-01,2014-03-01), featureLifeTime = [2014-01-01,indeterminate)
  • interpretation = BASELINE, validTime = [2014-03-01,2014-04-01), featureLifeTime = [2014-01-01,2014-04-01)

(sequenceNumber and correctionNumber omitted for brevity, no TEMPDELTAs)

How would the SNAPSHOT for 2014-02-15 look like?
  • A: interpretation = BASELINE, validTime = [2014-02-15], no featureLifeTime
  • B: interpretation = BASELINE, validTime = [2014-02-15], featureLifeTime = [2014-01-01,indeterminate)
  • C: interpretation = BASELINE, validTime = [2014-02-15], featureLifeTime = [2014-01-01,2014-04-01)

For every version there are good arguments: A means that the featureLifeTime is out of scope for SNAPSHOTs. B means that featureLifeTime is handled like any other property. C means that since we know the total featureLifeTime, we should also state it in the SNAPSHOT.
Edit | Attach | Print version | History: r8 | r7 < r6 < r5 < r4 | Backlinks | View wiki text | Edit WikiText | More topic actions...
Topic revision: r6 - 10 Sep 2014, MatthiasPohl
 

This site is powered by FoswikiThe information you supply is used for OGC purposes only. We will never pass your contact details to any third party without your prior consent.
If you enter content here you are agreeing to the OGC privacy policy.

Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding OGC Public Wiki? Send feedback