Stream: hapi
Topic: Namingsystem is derived from Metadataresource.java
Patrick Werner (Apr 01 2020 at 16:34):
Just used NamingSystem.java in R4 and found a get and set Url methods, which irritated me. They are coming from the MetadataResource.java it is deriving from. This allows me to build such Namingsystems: {"resourceType":"NamingSystem","url":"test1"}
Patrick Werner (Apr 01 2020 at 16:35):
shouldn't NamingSystem treated differently from the other canonical Resources ?
Grahame Grieve (Apr 01 2020 at 19:06):
@James Agnew this is an interesting one. You can get/set Url on Naming system because of a heirarchy problem. My code ignores it when serialising but yours doesn't
Jens Villadsen (Apr 01 2020 at 20:09):
Out of pure interest: why is this a problem?
Grahame Grieve (Apr 01 2020 at 20:12):
NamingSystem doesn't have a URL when it should - and it will in R5
Jens Villadsen (Apr 01 2020 at 20:24):
arh ... right ... - thats why I couldn't find it in the doc :lol:
Patrick Werner (Apr 01 2020 at 20:29):
this was found by one of our developers. He assumed that NamingSystems have a uri, because the code told him so. Could these uri methods be overwritten in NamingSystem in R4- and throw a Exception if you use them? Just ignoring them in the serialiser isn't that obvious to catch for implementers.
Patrick Werner (Apr 02 2020 at 08:08):
Great that NamingSystem is getting a uri in R5. Just had a look at the R5 examples. The uri of a Namingsystem isn't identical with on of its uniqueId (i expected that one of the uniqueIds would be the same as the NamingSystem.uri). As NamingSystem has a canonical url now, are there plans to enable binding a identifier to a NamingSystem?
Patrick Werner (Apr 02 2020 at 16:05):
question about R5 Namingsystem also asked here: https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/Use.20of.20NamingSystem.20in.20an.20IG.3F
Last updated: Apr 12 2022 at 19:14 UTC
