Stream: fmg
Topic: QA - GF#13066
Grahame Grieve (Mar 15 2017 at 22:57):
GF#13066 - mark Location.mode as not a modifier
Grahame Grieve (Mar 15 2017 at 22:57):
+1
Lloyd McKenzie (Mar 15 2017 at 23:07):
This fundamentally changes the meaning of location - is it a place or a type of place. That's a modifier to me
Lloyd McKenzie (Mar 15 2017 at 23:07):
It's the sort of thing we might actually create two distinct resources for
Grahame Grieve (Mar 15 2017 at 23:10):
modifies it how? it's still a location. When would it be unsafe to ignore the difference?
Lloyd McKenzie (Mar 15 2017 at 23:18):
No, it's not a location. It's either an actual location or it's a type of location
Lloyd McKenzie (Mar 15 2017 at 23:18):
Those are very different things
Grahame Grieve (Mar 15 2017 at 23:19):
they're different. When does the difference matter?
Lloyd McKenzie (Mar 15 2017 at 23:21):
The attribute is essentially a way of conveying two different resources using the same structure. It changes what kinds of elements make sense - or at least how you'd interpret them. For example, an address on a non-instance location would be weird, as would contact information
Lloyd McKenzie (Mar 15 2017 at 23:22):
It's the same reason the various Requst.intent attributes are considered modifiers - plan vs. proposal vs. order vs. option matter
Lloyd McKenzie (Mar 15 2017 at 23:22):
i.e. they change the fundamental nature of the instance
Grahame Grieve (Mar 15 2017 at 23:37):
that's not the definition of the element. I don't know what you'd put for "why it is a modifier"
Lloyd McKenzie (Mar 15 2017 at 23:38):
"This element changes the fundamental nature of the resource between describing a real place and describing a type of place."
Brian Postlethwaite (Mar 16 2017 at 01:00):
contact details on a location that is a kind would still make sense.
Mobile clinics for an organization
Lloyd McKenzie (Mar 16 2017 at 01:01):
A mobile location is still an instance, not a kind.
Brian Postlethwaite (Mar 16 2017 at 01:02):
Not if you are referring to the generally within the organization.
They have 12 ambulances, and have no intention of creating 12 instances of type ambulance.
As far as referencing the resource, makes no difference to all the other places here.
Lloyd McKenzie (Mar 16 2017 at 01:06):
Not really true. Definitions can point to types, but generally not to instances.
Grahame Grieve (Mar 16 2017 at 01:07):
acion item for MnM for R4: get better consensus about what makes an item a modifier. Clearly we don't have consensus, and some committees are randomly flagging 'must-support' things as 'ismodifier'
Grahame Grieve (Mar 16 2017 at 01:07):
definitions frequently refer to instances. particularly when you only have one of a type
Grahame Grieve (Mar 16 2017 at 01:07):
but in other circumstances too
John Moehrke (Mar 16 2017 at 01:08):
I looked at all the examples. Instances look very different than modes. Sure seems diffeent
John Moehrke (Mar 16 2017 at 01:09):
That said, that there are clear differences in what gets populated. I don't see elements taking on a different meaning. It just looks like two profiles overlayed with an element declaring which profile was used.
John Moehrke (Mar 16 2017 at 01:10):
therefore... I am not finding a good reason to make it a modifier, or to not make it a modifier. Guess I need to hear more arguing
Brian Postlethwaite (Mar 16 2017 at 01:16):
+1
Last updated: Apr 12 2022 at 19:14 UTC
