Stream: implementers
Topic: Type in Location
Luke Duncan (Mar 23 2017 at 13:51):
Is there a reason why type is restricted to only 1 value in Location? Our use case is mainly for buildings so one building may cover multiple types. Other resources do allow multiple types so I wanted to check to see if there was a particular reason that Location didn't. Thanks!
John Moehrke (Mar 23 2017 at 14:36):
Seems that usecase just calls for many Location resources. One for each type.
Lloyd McKenzie (Mar 23 2017 at 15:13):
How is status managed? If the state applies to all types, then it might be reasonable to do a 0..*.
Luke Duncan (Mar 23 2017 at 17:43):
So it would be appropriate to have multiple Location resources that are identical except for the type? Any reason this is different than Organizations that can have multiple types?
Luke Duncan (Mar 23 2017 at 18:05):
The status would apply to all types. Everything would be identical except for the type so 0..* would be easier. I was just wondering if there was a particular reason for limiting it here.
Carl Leitner (Mar 23 2017 at 18:13):
There may be different coding schemes in place for a classification of a single location/facility. I had thought type was the appropriate place to put this. It seems odd to me to create multiple location resources for the same physical location.
Last updated: Apr 12 2022 at 19:14 UTC
