Stream: fhircast-github
Topic: fhircast-docs / Issue #213 May 2019 Ballot Comment:
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot opened Issue #213
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Catalog
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Chaos reigns. Events should be an extensible value set. Otherwise each implementor will define event xyz with different meaning - resulting in lack of interoperability.
Existing wording: The name of the event SHOULD succinctly and clearly describe the activity or event. Event names are unique so event creators SHOULD take care to ensure newly proposed events do not conflict with an existing event name. Event creators SHALL name their event with reverse domain notation (e.g. org.example.patient-transmogrify) if the event is specific to an organization. Reverse domain notation SHALL not be used by a standard event catalog.
Proposed wording: The name of the event SHOULD succinctly and clearly describe the activity or event. Event names are unique so event creators SHOULD take care to ensure newly proposed events do not conflict with an existing event name. Event creators SHALL name their event with reverse domain notation (e.g. org.example.patient-transmogrify) if the event is specific to an organization. Reverse domain notation SHALL not be used by a standard event catalog.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot edited Issue #213
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Catalog
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Chaos reigns. Events should be an extensible value set. Otherwise each implementor will define event xyz with different meaning - resulting in lack of interoperability.
Existing wording: The name of the event SHOULD succinctly and clearly describe the activity or event. Event names are unique so event creators SHOULD take care to ensure newly proposed events do not conflict with an existing event name. Event creators SHALL name their event with reverse domain notation (e.g. org.example.patient-transmogrify) if the event is specific to an organization. Reverse domain notation SHALL not be used by a standard event catalog.
Proposed wording: The name of the event SHOULD succinctly and clearly describe the activity or event. Event names are unique so event creators SHOULD take care to ensure newly proposed events do not conflict with an existing event name. Event creators SHALL name their event with reverse domain notation (e.g. org.example.patient-transmogrify) if the event is specific to an organization. Reverse domain notation SHALL not be used by a standard event catalog.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 05 2019 at 02:55):
isaacvetter labeled Issue #213
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Catalog
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Chaos reigns. Events should be an extensible value set. Otherwise each implementor will define event xyz with different meaning - resulting in lack of interoperability.
Existing wording: The name of the event SHOULD succinctly and clearly describe the activity or event. Event names are unique so event creators SHOULD take care to ensure newly proposed events do not conflict with an existing event name. Event creators SHALL name their event with reverse domain notation (e.g. org.example.patient-transmogrify) if the event is specific to an organization. Reverse domain notation SHALL not be used by a standard event catalog.
Proposed wording: The name of the event SHOULD succinctly and clearly describe the activity or event. Event names are unique so event creators SHOULD take care to ensure newly proposed events do not conflict with an existing event name. Event creators SHALL name their event with reverse domain notation (e.g. org.example.patient-transmogrify) if the event is specific to an organization. Reverse domain notation SHALL not be used by a standard event catalog.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 05 2019 at 02:56):
isaacvetter commented on Issue #213
Hey Anthony,
I'd like to suggest that this negative comment should be resolved by defining, in the specification, the process and documentation template for defining and maturing new events. And that each event be maturable, indepedent of the specification or unrelated events.
Isaac
Github Notifications (FHIRcast) (May 21 2019 at 13:07):
wmaethner labeled Issue #213:
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Catalog
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Chaos reigns. Events should be an extensible value set. Otherwise each implementor will define event xyz with different meaning - resulting in lack of interoperability.
Existing wording: The name of the event SHOULD succinctly and clearly describe the activity or event. Event names are unique so event creators SHOULD take care to ensure newly proposed events do not conflict with an existing event name. Event creators SHALL name their event with reverse domain notation (e.g. org.example.patient-transmogrify) if the event is specific to an organization. Reverse domain notation SHALL not be used by a standard event catalog.
Proposed wording: The name of the event SHOULD succinctly and clearly describe the activity or event. Event names are unique so event creators SHOULD take care to ensure newly proposed events do not conflict with an existing event name. Event creators SHALL name their event with reverse domain notation (e.g. org.example.patient-transmogrify) if the event is specific to an organization. Reverse domain notation SHALL not be used by a standard event catalog.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 11 2019 at 20:35):
wmaethner closed Issue #213:
May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Catalog
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Chaos reigns. Events should be an extensible value set. Otherwise each implementor will define event xyz with different meaning - resulting in lack of interoperability.
Existing wording: The name of the event SHOULD succinctly and clearly describe the activity or event. Event names are unique so event creators SHOULD take care to ensure newly proposed events do not conflict with an existing event name. Event creators SHALL name their event with reverse domain notation (e.g. org.example.patient-transmogrify) if the event is specific to an organization. Reverse domain notation SHALL not be used by a standard event catalog.
Proposed wording: The name of the event SHOULD succinctly and clearly describe the activity or event. Event names are unique so event creators SHOULD take care to ensure newly proposed events do not conflict with an existing event name. Event creators SHALL name their event with reverse domain notation (e.g. org.example.patient-transmogrify) if the event is specific to an organization. Reverse domain notation SHALL not be used by a standard event catalog.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Last updated: Apr 12 2022 at 19:14 UTC
