Stream: mapping-framework
Topic: Support for adding metadata
Ewout Kramer (Aug 20 2019 at 16:33):
Currently, the mapping language syntax allows us to specify the canonical url and the title of a map, while the StructureMap resource has many more elements dealing with metadata (i.e. status, version, identifier etc). In GF#22110, I have suggested a method to expand the capabilities of the syntax using an approach comparable to Java and C# doccomments:
/* * This is a FHIR mapping language file which shows special 'doccomments' * below to specify the version and status of this map. */ /// version = 0.1 /// status = draft map "http://fire.ly/tests/AllFeatures" = "Map testing all features"
This works nicely for primitive metadata elements, but needs an approach for complex types (like contact or identifier). One solution would be to use inline json to do specify such complex elements. Also, it's not yet clear whether we need to support all metadata available (though that would be nice to be able to roundtrip between the syntax and the structuremap resource).
Ideas? Opinions?
Brian Kaney (Aug 20 2019 at 17:58):
JSDoc/Javadoc? It kinda has the ability to express complicated objects (e.g. @param); the idea could be expanded to support more @ keywords:
/** * @author Firstname Lastname <address @ example.com> * @version 1.6 * @status draft * * @param identifier.system http://foo.com * @param identifier.value 12345 */ map "http://fire.ly/tests/AllFeatures" = "Map testing all features"
Last updated: Apr 12 2022 at 19:14 UTC
