Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jo edits batch 1 #4

Open
wants to merge 7 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
35 changes: 16 additions & 19 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,51 +1,48 @@
# Victorian Government - API Design Standard - DRAFT FOR REVIEW
# Victorian Government API Design Standard - DRAFT FOR REVIEW

The Victorian Department of Premier and Cabinet has recently created the Digital, Design and Innovation Group as part of the Governance, Policy and Coordination Division.
The Victorian Department of Premier and Cabinet created the Digital, Design and Innovation Branch within the Governance, Policy and Coordination Group in late 2018.

A key function of this group is to provide standards for information access across government, its partners and the community, bringing governance and security, opportunities for innovative rapid development, and enhanced data consistency and discoverability.
A key function of this branch is to provide standards for information access across government, its partners and the community. These standards provide guidance on API governance and security and enhanced data consistency and discoverability.

These API standards are a starting point for collaboration across government to ensure interoperability is front of mind when creating or modifying digital services across government.
These API standards are a starting point for collaboration across government. They provide a reference point to ensure interoperability is a priority when creating or modifying digital services across government.

A working group is being formulated as part of the Victorian Government CIO Leadership Group, a forum of CIOs across government, that will assist in the ratification and update of these standards over time.
A working group is being formulated as part of the Victorian Government CIO Leadership Group, a forum of CIOs across government, that will assist in the ratification and updating of these standards over time.

This repository is being used to seek feedback from the working group, and also provide a view to the general public on the standards that are being created within government. These standards should also be applicable for entites outside of government and their use is encouraged.
We're providing this repository to seek feedback from the working group and share with the general public the standards that are being created within government. These standards should be applicable for entities outside of government; their use is encouraged.

The API Standards have been written by the API Team, lead by Jordan Walsh. Reviewers and contributors can see open issues and proposed decision points for feedback on the issues page here.
The API Standards have been written by the API Team, led by Jordan Walsh. Reviewers and contributors can see open issues and proposed decision points for feedback on the issues page.

For more information see the contact information below.

You can read the latest version of the standard [here](api-standards.md).
You can read the latest version of the standards [here](api-standards.md).


<br /><br />
<br />
______________________________________________________________________________
# Contact Information
# Contact information

API Team<br/>
Digital, Design and Innovation<br/>
Department of Premier and Cabinet<br/>
[apiteam@dpc.vic.gov.au](mailto:apiteam@dpc.vic.gov.au)


<br /><br />
<br />
______________________________________________________________________________

# Contributing to this standard

We're committed to undertaking conversations relating to the technical standards in the open. Questions or comments that participants might ask us via email or private message are likely to be questions or comments other participants have as well. Our answers will be of interest to everyone. There are likely to be experiences and lessons everybody working in this ecosystem can learn from. Having these conversations transparently helps us reduce duplication, resolve issues faster and keep everyone up to date with the conversation.
We're committed to having public conversations about the technical standards. Questions or comments that participants might ask us via email or private message are likely to be questions or comments other participants have as well - our responses will be of interest to everyone. We anticipate that there will be experiences and lessons everybody can learn from. Having these conversations publicly helps us reduce duplication, resolve issues faster and keep everyone up to date with the conversation.

We ask that all contributors to the Victorian Government API Standards repositories comply with the [GitHub Community Forum Code of Conduct](https://help.github.com/articles/github-community-forum-code-of-conduct/).

In addition, it would be appreciated if the following rules are adhered to when commenting or contributing:

- Please provide a single, considered response to each proposal covering all feedback concerning the proposal.

- For transparency, if you work at or are associated with an organisation with an interest in the standards, please indicate this in your response.
- Provide a single, considered response to each proposal covering all feedback concerning the proposal.

- Please ensure you are aware of and compliant with any social media guidelines or internal processes for response set by your organisation before providing feedback.
- For transparency, if you work at or are associated with an organisation with an interest in the standards, indicate this in your response.

- Ensure you are aware of and compliant with any social media guidelines or internal processes for response set by your organisation before providing feedback.

<br /><br />
<br />
______________________________________________________________________________
# Reference

Expand Down