Update 3.0.4.md to fix broken links

.github/templates/agenda.md

@@ -0,0 +1,22 @@
+**NOTE: This meeting is on Thursday at 9am - 10am PT**
+
+Zoom Meeting link: [https://zoom.us/j/975841675](https://zoom.us/j/975841675?pwd=SUh4MjRLaEFKNlI3RElpWTdhRDVVUT09). Dial-in passcode: 763054 - [Code-of-Conduct](https://github.com/OAI/OpenAPI-Specification/blob/main/CODE_OF_CONDUCT.md#code-of-conduct)
+
+In order to give some more visibility into the topics we cover in the TDC meetings here is the planned agenda for the next meeting.  Hopefully this will allow people to plan to attend meetings for topics that they have an interest in.  And for folks who cannot attend they can comment on this issue prior to the meeting.  Feel free to suggest other potential agenda topics.
+
+**Please submit comments below for topics or proposals that you wish to present in the TDC meeting**
+
+![F10B5460-B4B3-4463-9CDE-C7F782202EA9](https://user-images.githubusercontent.com/21603/121568843-0b260900-ca18-11eb-9362-69fda4162be8.jpeg)
+
+The agenda backlog is currently maintained in issue #2482
+
+| Topic | Owner | Decision/NextStep |
+|-------|---------|---------|  
+| | | |
+Reports from Special Interest Groups | TDC | |
+AOB (see below) | TDC | |
+New issues / PRs labelled [review](https://github.com/OAI/OpenAPI-Specification/labels/review) | @OAI/triage | |
+[New issues](https://github.com/search?q=repo%3Aoai%2Fopenapi-specification+is%3Aissue+comments%3A0+no%3Alabel+is%3Aopen) without response yet | @OAI/triage  | |
+
+
+/cc @OAI/tsc Please suggest items for inclusion

.github/workflows/agenda.yaml

@@ -0,0 +1,29 @@
+name: agenda
+
+# author: @MikeRalphson
+# issue: various
+
+#
+# This workflow creates the agenda issue each week. It runs on a cron every
+# Monday morning, raising an issue for the following Thursday.
+# It can also be run manually, in case GitHub Actions has a failure.
+#
+
+on:
+  schedule:
+    - cron: '0 9 * * 1'
+  workflow_dispatch: {}
+
+jobs:
+  agenda:
+    env:
+      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v1 # checkout repo content
+
+    - name: Create agenda issue
+      run: gh issue create -l Housekeeping -t "Open Community (TDC) Meeting, `date --date='next Thu' +'%A %d %B %Y'`" -F .github/templates/agenda.md
+

.github/workflows/convert-examples-to-json.yaml

@@ -0,0 +1,49 @@
+name: convert-examples-to-json
+
+# author: @MikeRalphson / @cebe
+# issue: https://github.com/OAI/OpenAPI-Specification/issues/1385
+
+#
+# This workflow updates the *.json files in the examples/v3.x directories,
+# when the corresponding *.yaml files change.
+# JSON example files are automatically generated from the YAML example files.
+# Only the YAML files should be adjusted manually.
+#
+
+# run this on push to main
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  yaml2json:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2 # checkout repo content
+
+    - name: Install dependencies
+      run: npm i
+
+    - name: convert YAML examples to JSON
+      run: find examples/v3* -type f -name "*.yaml" | xargs node scripts/yaml2json/yaml2json.js
+
+    - name: git diff
+      run: |
+        git add examples/**/*.json
+        git --no-pager -c color.diff=always diff --staged
+
+    - name: Create Pull Request
+      uses: peter-evans/create-pull-request@v3
+      with:
+        token: ${{ secrets.GITHUB_TOKEN }}
+        branch: update-json-examples
+        title: Update JSON example files
+        commit-message: Update JSON example files
+        body: |
+          This pull request is automatically triggered by GitHub action `convert-examples-to-json`.
+
+          The examples/v3.* YAML files have changed, so the JSON files are automatically being recreated.
+

.github/workflows/respec.yaml

@@ -0,0 +1,57 @@
+name: respec
+
+# author: @MikeRalphson
+# issue: https://github.com/OAI/OpenAPI-Specification/issues/1564
+
+#
+# This workflow updates the respec 'pretty' rendered versions of the spec 
+# on the gh-pages branch when the corresponding markdown files change.
+#
+
+# run this on push to main
+on:
+  push:
+    branches:
+      - main
+  workflow_dispatch: {}
+
+jobs:
+  respec:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2 # checkout main branch
+      with:
+        fetch-depth: 0
+
+    - name: Install dependencies
+      run: npm i
+
+    - uses: actions/checkout@v2 # checkout gh-pages branch
+      with:
+        ref: gh-pages
+        path: deploy
+
+    - name: run main script
+      run: scripts/md2html/build.sh
+
+    - name: Create Pull Request
+      uses: peter-evans/create-pull-request@v3
+      with:
+        token: ${{ secrets.GITHUB_TOKEN }}
+        branch: update-respec-version
+        base: gh-pages
+        delete-branch: true
+        path: deploy
+        labels: Housekeeping
+        reviewers: webron,darrelmiller
+        title: Update ReSpec versions
+        commit-message: Update ReSpec versions
+        signoff: true
+        body: |
+          This pull request is automatically triggered by GitHub action `respec`.
+
+          The versions/v*.md files have changed, so the HTML files are automatically being regenerated.
+
+

.github/workflows/schema-tests.yaml

@@ -0,0 +1,31 @@
+name: schema-test
+
+# Author: @MikeRalphson / runs @jdesrosiers tests
+# Issue: https://github.com/OAI/OpenAPI-Specification/pull/2489
+
+#
+# This workflow runs the npm test script to validate passing and failing
+# testcases for the metaschema.
+#
+
+# run this on push to any branch and creation of pull-requests
+on: 
+  push: {}
+  pull_request: {}
+  workflow_dispatch: {}
+
+jobs:
+  test:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v1 # checkout repo content
+    - uses: actions/setup-node@v1 # setup Node.js
+      with:
+        node-version: '14.x'
+    - name: Install dependencies
+      run: npm i
+    - name: Run tests
+      run: npm run test
+

.github/workflows/validate-markdown.yaml

@@ -18,10 +18,10 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v1 # checkout repo content
+    - uses: actions/checkout@v2 # checkout repo content
     - uses: actions/setup-node@v1 # setup Node.js
       with:
-        node-version: '12.x'
+        node-version: '14.x'
     - name: Validate markdown
       run: npx mdv versions/3.*.md
 

.gitignore

@@ -5,4 +5,7 @@
 target
 atlassian-ide-plugin.xml
 node_modules/
+package-lock.json
+deploy/
+history
 Gemfile.lock

CODE_OF_CONDUCT.md

@@ -0,0 +1,155 @@
+Code of Conduct
+===============
+
+OpenAPI Initiative Code of Conduct
+
+*The Linux Foundation*
+
+*Effective November 24, 2020*
+
+The OpenAPI Initiative (OAI) is an open source Linux Foundation project
+and home of the OpenAPI Specification (OAS) released under the Apache
+2.0 license. As contributors, maintainers, and participants in this
+project, we want to foster an open and welcoming environment. We pledge
+to make participation in our project and our community a harassment-free
+experience for everyone, regardless of age, body size, disability,
+ethnicity, gender identity and expression, level of experience,
+education, socio-economic status, nationality, personal appearance,
+race, religion, or sexual identity and orientation.
+
+Our Standards
+-------------
+
+Examples of behaviors that contribute to creating a positive environment
+include:
+
+-   Using welcoming and inclusive language
+
+-   Being respectful of differing viewpoints and experiences
+
+-   Gracefully accepting constructive criticism
+
+-   Focusing on what is best for the community
+
+-   Showing empathy towards other community members
+
+-   Assuming the best intent from others
+
+Examples of unacceptable behavior by participants include:
+
+-   The use of sexualized language or imagery and unwelcome sexual attention or advances
+
+-   Making unsolicited, insulting or derogatory comments, including personal (i.e., ad hominem) or political attacks to create conflict (e.g., trolling)
+
+-   Public or private harassment
+
+-   Publishing others' private information, such as a physical or electronic address, without explicit permission (e.g., doxxing)
+
+-   Threatening, offensive, harmful comments, or behavior
+
+-   Other conduct which could reasonably be considered inappropriate in a professional setting
+
+Our Responsibilities
+--------------------
+
+The Code of Conduct Committee is responsible for clarifying the
+standards of acceptable behavior and is expected to take appropriate and
+fair corrective action in response to any instances of unacceptable
+behavior.
+
+Scope
+-----
+
+This Code of Conduct applies to OAI project spaces, as well as
+interactions in public spaces. Project spaces include, but are not
+limited to, official OAI code repositories, Slack, mailing lists,
+meetings, and events. Public spaces may include venues where an
+individual is representing the project or its community. Examples of
+this include a community member's email communication, forum posts,
+social media activity, or acting as a representative at an online or
+offline event. In addition, violations of this code of conduct outside
+of these spaces may affect a person's ability to participate in them.
+
+Enforcement
+-----------
+
+To report instances of abuse, harassment, or otherwise unacceptable
+behavior, contact
+[conduct\@openapis.org](mailto:[email protected]). **We
+are committed to maintaining the confidentiality of anyone reporting an
+incident**. The Code of Conduct Committee will review and investigate
+all complaints, responding as deemed necessary and appropriate to the
+circumstances. For incidents relating to offline events, we aim to
+respond to reports within 24 hours, and for incidents relating to online
+activities, we aim to respond to reports within 7 days.
+
+The Code of Conduct Committee has the right and responsibility to
+remove, edit, or reject comments, commits, code, wiki edits, issues, and
+other contributions that are not aligned to this Code of Conduct, or
+take other appropriate action as deemed necessary for behaviors contrary
+to the standards listed above. In the case of offline or in-person
+events, if a participant engages in behavior that is not aligned to this
+Code of Conduct, the committee may take action, such as warning the
+offender, banning the offender from various online spaces (temporary or
+permanent), removing the offender from an event with no refund, or other
+options deemed appropriate.
+
+Enforcement Guidelines
+----------------------
+
+The Code of Conduct committee will follow these Enforcement Guidelines in 
+determining the consequences for any action they deem in violation of this 
+Code of Conduct:
+
+#### 1. Correction
+Community Impact: Use of inappropriate language or other behavior deemed 
+unprofessional or unwelcome in the community.
+
+Consequence: A private, written warning from the Code of Conduct committee, 
+providing clarity around the nature of the violation and an explanation of 
+why the behavior was inappropriate. A public apology may be requested.
+
+#### 2. Warning
+Community Impact: A violation through a single incident or series of 
+actions.
+
+Consequence: A warning with consequences for continued behavior. No 
+interaction with the people involved, including unsolicited interaction 
+with the Code of Conduct committee, for a specified period of time. This 
+includes avoiding interactions in community spaces as well as external 
+channels like social media. Violating these terms may lead to a temporary 
+or permanent ban.
+
+#### 3. Temporary Ban
+Community Impact: A serious violation of community standards, including 
+sustained inappropriate behavior.
+
+Consequence: A temporary ban from any sort of interaction or public 
+communication with the community for a specified period of time. No 
+public or private interaction with the people involved, including 
+unsolicited interaction with the Code of Conduct committee, is allowed 
+during this period. Violating these terms may lead to a permanent ban.
+
+#### 4. Permanent Ban
+Community Impact: Demonstrating a pattern of violation of community 
+standards, including sustained inappropriate behavior, harassment of 
+an individual, or aggression toward or disparagement of classes of 
+individuals.
+
+Consequence: A permanent ban from any sort of public interaction 
+within the community.
+
+### Events
+
+Some OpenAPI events are governed by the [Linux Foundation Code of
+Conduct](https://events.linuxfoundation.org/about/code-of-conduct/)
+(E.g. API Specifications Conference) and will be listed on the event
+page. The OAI Code of Conduct is designed to be compatible with the
+above policy and also includes more details on responding to incidents.
+
+### Attribution
+
+This code of conduct is adapted from the [Contributor Covenant, version
+1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct)
+and the [PyCon 2019 Code of
+Conduct](https://us.pycon.org/2019/about/code-of-conduct/).