initialize develop branch for github repo

initialize develop branch for github repo, first commit on this branch is ahead of D3FEND release 0.10.0-BETA-2 which is tagged in our private repository.

Author: netfl0

Diff for: .gitignore

@@ -0,0 +1,7 @@
+.vscode/settings.json
+bin
+build
+reports
+dist
+.DS_Store
+

Diff for: .gitlab-ci.yml

@@ -0,0 +1,35 @@
+# This file is a template, and might need editing before it works on your project.
+# To contribute improvements to CI/CD templates, please follow the Development guide at:
+# https://docs.gitlab.com/ee/development/cicd/templates.html
+# This specific template is located at:
+# https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Getting-Started.gitlab-ci.yml
+
+# This is a sample GitLab CI/CD configuration file that should run without any modifications.
+# It demonstrates a basic 3 stage CI/CD pipeline. Instead of real tests or scripts,
+# it uses echo commands to simulate the pipeline execution.
+#
+# A pipeline is composed of independent jobs that run scripts, grouped into stages.
+# Stages run in sequential order, but jobs within stages run in parallel.
+#
+# For more information, see: https://docs.gitlab.com/ee/ci/yaml/index.html#stages
+
+stages:          # List of stages for jobs, and their order of execution
+  - build
+  - test
+
+build:       # This job runs in the build stage, which runs first.
+  stage: build
+  script:
+    #- yum install make -y 
+    - make install-deps
+    - make clean
+    - make all
+
+test:       # This job runs in the test stage
+  stage: test
+  script:
+    - make install-deps
+    - make reports
+  artifacts:
+    paths:
+      - reports/

Diff for: CONTRIBUTING.md

@@ -0,0 +1,40 @@
+# Contributing to D3FEND
+
+Thank you for your interest in contributing to D3FEND! This document briefly details the guidelines for contributing to the project. Please [reach out to us](mailto:[email protected]) if you have any questions or need clarification.
+
+## Contribution Guidelines
+
+**Before spending lots of time on something, ask for feedback on your idea first!**
+
+Please search [issues](../../issues/) and [pull requests](../../pulls/) before adding something new! This helps avoid duplicating efforts and conversations.
+
+### Contribution Types
+
+Please determine what type of contribution you are submitting and then follow any specified instructions. If you are not comfortable with a pull request please feel free to send us an email with your contribution.
+
+- **Technique**: submitting or recommending a new defensive technique.
+    > Process: please email submission with this [mailto template](mailto:[email protected]?subject=New%20D3FEND%20Technique%20Submission&body=Definition%3A%0D%0A-%0D%0A%0D%0APublic%20Reference%20Links%3A%0D%0A-%0D%0A-).
+- **Correction**: grammar, typos, broken links.
+    > Process: [Create issue](#create-issue) -> [Submit pull request](#pull-request).
+- **Reference**: adding a reference to the ontology.
+    > Process: [Create issue](#create-issue) -> [Submit pull request](#pull-request).
+- **Ontology**: adding a digital artifact or creating a new artifact relationship. New classes, individuals, or properties.
+    > Process: [Create issue](#create-issue) -> [Submit pull request](#pull-request).
+
+## Processes
+
+### Pull Request
+
+Please create an issue before you send a pull request. Also please read about our [conventions](CONVENTIONS.md) (they are still a work in progress).
+
+### Create Issue
+
+1. Identify which [type of contribution](#contribution-types) you are making.
+1. Create a Github issue.
+1. Title the issue with a prefix of the type of contribution, e.g.:
+    1. `[Reference] Add new reference for File Content Rules`
+    1. `[Correction] Typo in File Content Rules KB article`
+
+## Code of Conduct
+
+All contributors are expected to conduct themselves in a professional manner.

Diff for: CONVENTIONS.md

@@ -0,0 +1,6 @@
+# D3FEND Ontology Conventions
+
+1. Defensive Techniques are punned as instances of their parent classes.
+1. CamelCase  [IRIs](https://en.wikipedia.org/wiki/Internationalized_Resource_Identifier), capitalize all words in the IRI fragment.
+1. Do not use bracket characters in IRIs.
+1. Do not use unicode characters in IRIs.

Diff for: DESIGN.md

@@ -0,0 +1,9 @@
+# Design Details for the D3FEND Ontology
+
+## IRI naming approach
+The the ontology iri was selected to satisfy two key requirements:
+1. The ontology prefix shall be a resolvable file.
+2. A full IRI shall result in a resolvable file.
+
+### Constraints
+1. Must be compatible with standard static web file server

Diff for: LICENSE.md

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2022 The MITRE Corporation
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+