Specification Proposal Template

Fill out this form to request a Change to an existing specification. See the complete process in context.

New Building Block Proposal

Proposed Name _REQUIRED	[Proposed name for this Building Block]
Status	SUBMITTED / ON REVIEW / APPROVED / DECLINED ^{(For use by the GovSpec Core Team only)}
Date Submitted _REQUIRED	[YYYY-MM-DD]
Requestors _REQUIRED	[Name], [Email], [Affiliation] [Name], [Email], [Affiliation] [Name], [Email], [Affiliation]
Building Block Type _REQUIRED	[Foundational/Feature/Guidelines/Cross-Cutting]
Building Block Proposal Description _REQUIRED	[Context or justification for the creation of this building block] [Solution statement that briefly describes this building block]
Interaction with other Building Blocks _OPTIONAL	[Name of building block] - [Name of functionality with which it interacts]
Existing solutions on the market _RECOMMENDED	[Name] - [URL]
Known APIs _RECOMMENDED	[Name] - [URL]
Existing related policies _RECOMMENDED	[Name] - [URL]
Known related standards _OPTIONAL	[Name] - [URL]

Existing Building Block Change proposal

For requesting to change an existing Building Block, consider whether this change requires a Minor or Major version change. The following may be of guidance:

Minor version for the specification: Non-breaking changes to existing version by adding new features or extending existing ones.
Major version of the specifications: Breaking changes are being proposed. Below is a list of examples of breaking changes, which often go together (changes in the data model require changes in the API):
1. Semantic understanding of a BB is fundamentally changed by non-compatible Terminology
2. Key Digital Functionalities are eliminated or split into new ones,
3. The requirement levels of Cross-Cutting Requirements or Functional Requirements are changed, or new mand-atory requirements are added
4. Changes in the Data Model are needed which require the elimination or splitting of a existing resource, or the addition of a new required resource is needed.
5. The Service API model requires the release of a new version

Building Block Impacted _REQUIRED	[Name of BB] - [Version] - [URL]
Status	SUBMITTED / ON REVIEW / APPROVED / DECLINED ^{(For use by the GovSpec Core Team only)}
Date Submitted _REQUIRED	[YYYY-MM-DD]
Requestors _REQUIRED	[Name], [Email], [Affiliation] [Name], [Email], [Affiliation] [Name], [Email], [Affiliation]
Type of change proposed _REQUIRED	[Minor Version/Major Version]
Change Request details _{In case of Major or Minor version request, use this section to broadly describe your proposed changes}
Change Proposal Description _REQUIRED	[Context or justification for the change proposal] [Solution statement that briefly describes the scoped proposed]
Optional Details
Section 3. Terminology _OPTIONAL	[Rough description of changes]
Section 4. Key digital functionalities _OPTIONAL	[Rough description of changes]
Section 5. Cross-Cutting Requirements _OPTIONAL	[Rough description of changes]
Section 6. Functional Requirements _OPTIONAL	[Rough description of changes]
Section 7. Data Structures _OPTIONAL	[Rough description of changes]
Section 8. Service APIs _OPTIONAL	[Rough description of changes]
Section 9. Internal Workflows _OPTIONAL	[Rough description of changes]
Addition of section _OPTIONAL	[Description of section title and its contents]