Stream: fhircast-github
Topic: docs / Issue #67 Polish specification before ballot: remo...
Github Notifications (FHIRcast) (Feb 07 2019 at 19:50):
isaacvetter opened Issue #67
@bvhd analyzed our specification during the January HL7 WGM in San Antonio and provided some sigificant, detailed analysis and feedback.
Two broad themes of Bas's feedback include:
- The specification is written as a story or narrative or use-case, not as a specification.
- Better use & explanation of mandatory text
In general, it's also difficult for the reader to determine what content is informative and what content is specification.
To address these issues, I'm going to split the narrative out of the specification and add an overview page and then specifically label the specification as version 1.0 (with a notice that it's still in draft).
@bvhd - as always, would love your feedback.
Github Notifications (FHIRcast) (Feb 07 2019 at 19:50):
isaacvetter assigned Issue #67(assigned to isaacvetter)
@bvhd analyzed our specification during the January HL7 WGM in San Antonio and provided some sigificant, detailed analysis and feedback.
Two broad themes of Bas's feedback include:
- The specification is written as a story or narrative or use-case, not as a specification.
- Better use & explanation of mandatory text
In general, it's also difficult for the reader to determine what content is informative and what content is specification.
To address these issues, I'm going to split the narrative out of the specification and add an overview page and then specifically label the specification as version 1.0 (with a notice that it's still in draft).
@bvhd - as always, would love your feedback.
Github Notifications (FHIRcast) (Feb 07 2019 at 19:51):
isaacvetter labeled Issue #67(assigned to isaacvetter)
@bvhd analyzed our specification during the January HL7 WGM in San Antonio and provided some sigificant, detailed analysis and feedback.
Two broad themes of Bas's feedback include:
- The specification is written as a story or narrative or use-case, not as a specification.
- Better use & explanation of mandatory text
In general, it's also difficult for the reader to determine what content is informative and what content is specification.
To address these issues, I'm going to split the narrative out of the specification and add an overview page and then specifically label the specification as version 1.0 (with a notice that it's still in draft).
@bvhd - as always, would love your feedback.
Last updated: Apr 12 2022 at 19:14 UTC
