Working towards the next version of the SWIM Supporting Material
Working towards the next version of the SWIM Supporting Material
I have a hypothetical question over the usage of terminology in the actual data payload that the consumer will ingest. Imagine I have a data service that I wrote and launched '20' years ago. In the data content there is numerical data for temperatures and times for a point in space, but there is also the text "Aerodrome".
As the service was written '20' years ago there is a strong possibility that the meaning of the word "Aerodrome" in the data payload does not exactly fit the meaning of the word "Aerodrome" as laid out according to the AIRM definition. Under what circumstances would this payload be valid - or would it be advised to re-write the payload from scratch so that the definitions are always common in both the payload and service description?
I suppose what I am asking is 'do you see more SWIM services being developed with a pre-understanding of SWIM from scratch' in favour of taking existing operational services and adding SWIM descriptions to them?
Frequently Asked Questions about the implementation of the SWIM Service Description specification. Including direct link to the supporting material when applicable.
Answers to questions from (former) implementers may help newcomers.
work in progress
The list contains the received questions. We are not yet at a stage of frequently asked questions.
Many questions have not received an answer yet.
When more questions are available, re-organisation might be needed.