You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UUIDs are used in AIXM as a unique pointer to feature instances, like aerodrome (see their document on Feature identification and reference for details). They do this through the use of gml:identifier:
Starting with the IWXXM WAFS SIGWX Forecast package, gml:identifier will also be used to identify individual iwxxm:MeteorologicalFeature (e.g. a turbulence polygon). The last line of the WAFS-Example.xml shows what one can do to reference this object if this is available as an online resource.
While it is still a long way to the provision and consumption of online resources, especially our use cases cover situations where network access may or may not be available when consuming the IWXXM report, it also gives us food for thought of the future mix of information, services and systems.
Just a point to note: WMO WIS2 is built upon the Resource Oriented Architecture (ROA) whereas the foundation of SWIM is Service Oriented Architecture (SOA). It would be interesting to learn from WIS2 the experience on developing, maintaining and operating online resources before deciding how we deal with aviation meteorological information on SWIM.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
UUIDs are used in AIXM as a unique pointer to feature instances, like aerodrome (see their document on Feature identification and reference for details). They do this through the use of gml:identifier:
and referencing it in some other instances in this way, if the above record is hosted on an FAA server:
Starting with the IWXXM WAFS SIGWX Forecast package, gml:identifier will also be used to identify individual iwxxm:MeteorologicalFeature (e.g. a turbulence polygon). The last line of the WAFS-Example.xml shows what one can do to reference this object if this is available as an online resource.
While it is still a long way to the provision and consumption of online resources, especially our use cases cover situations where network access may or may not be available when consuming the IWXXM report, it also gives us food for thought of the future mix of information, services and systems.
Just a point to note: WMO WIS2 is built upon the Resource Oriented Architecture (ROA) whereas the foundation of SWIM is Service Oriented Architecture (SOA). It would be interesting to learn from WIS2 the experience on developing, maintaining and operating online resources before deciding how we deal with aviation meteorological information on SWIM.
Beta Was this translation helpful? Give feedback.
All reactions