Stream: cds hooks/github
Topic: docs / Issue #327 May 2018 Ballot Comment 121
Github Notifications (May 16 2018 at 23:02):
cds-hooks-bot opened Issue #327
## May 2018 Ballot Comment 121
Submitted by @kensaku-kawamoto on behalf of @euvitudo from University of Utah
Chapter: Context
Section: https://cds-hooks.org/hooks/
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:Existing Wording:
All fields defined by the hook's context MUST be defined in a table where each field is described by the following attributes:
Comment:
Recommend also providing the hook's context information in the CDS services discovery interface itself, so that users can identify how a hook is to function directly through the service rather than by looking up documentation. This would also apply to the hook's version support information.## :de: Köln May 2018 Working Group Vote
@brettmarquard moved the following disposition, seconded by @brynrhodes.
Disposition: Not Persuasive
Disposition Comment:
We don't think this change should be made as the hook definition should remain defined in the hook rather than duplicated into each CDS Service definition (and potentially changed in non-standard ways):+1: For: 20
:expressionless: Abstain: 3
:-1: Against: 0:tada: The motion passed! :tada:
_This issue was imported by @cds-hooks-bot from the consolidated CDS Hooks May 2018 ballot spreadsheet._
Github Notifications (May 16 2018 at 23:02):
cds-hooks-bot milestoned Issue #327
Github Notifications (May 16 2018 at 23:02):
cds-hooks-bot labeled Issue #327
Github Notifications (May 16 2018 at 23:02):
cds-hooks-bot edited Issue #327
## May 2018 Ballot Comment 121
Submitted by @kensaku-kawamoto on behalf of @euvitudo from University of Utah
Chapter: Context
Section: https://cds-hooks.org/hooks/
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:Existing Wording:
All fields defined by the hook's context MUST be defined in a table where each field is described by the following attributes:
Comment:
Recommend also providing the hook's context information in the CDS services discovery interface itself, so that users can identify how a hook is to function directly through the service rather than by looking up documentation. This would also apply to the hook's version support information.## :de: Köln May 2018 Working Group Vote
@brettmarquard moved the following disposition, seconded by @brynrhodes.
Disposition: Not Persuasive
Disposition Comment:
We don't think this change should be made as the hook definition should remain defined in the hook rather than duplicated into each CDS Service definition (and potentially changed in non-standard ways):+1: For: 20
:expressionless: Abstain: 3
:-1: Against: 0:tada: The motion passed! :tada:
_This issue was imported by @cds-hooks-bot from the consolidated CDS Hooks May 2018 ballot spreadsheet._
Github Notifications (May 16 2018 at 23:10):
kpshek commented on Issue #327
Closing per the _Not Persuasive_ vote at the :de: Köln May 2018 working group meeting.
Github Notifications (May 16 2018 at 23:10):
kpshek closed Issue #327
Github Notifications (Jun 14 2018 at 13:44):
cds-hooks-bot assigned Issue #327
Last updated: Apr 12 2022 at 19:14 UTC
