Initial commit of library files (#1)

* Initial commit of a Maven-based build and library code
* Created a basic data loader that is capable of detecting the type of content for the loaded file.
* Initial commit of project markdown and CI/CD resources.

.circleci/config.yml

@@ -0,0 +1,83 @@
+version: 2.1
+
+executors:
+  maven-executor:
+    docker:
+      - image: circleci/openjdk:8u171-jdk
+jobs:
+  build-and-test:
+    executor: maven-executor
+    steps:
+      - checkout
+      - restore_cache:
+          key: maven-m2-{{ checksum "pom.xml" }}
+      - configure-gpg
+      - run:
+          command: mvn -Prelease verify
+      - persist_to_workspace:
+          root: .
+          paths:
+            - .
+      - store_artifacts:
+          path: oss-build-support/target
+          destination: artifacts/oss-build-support
+      - store_artifacts:
+          path: oss-parent/target
+          destination: artifacts/oss-parent
+      - store_artifacts:
+          path: reflow-maven-skin/target
+          destination: artifacts/reflow-maven-skin
+  deploy-release:
+    executor: maven-executor
+    steps:
+      - deploy
+
+commands:
+  configure-gpg:
+    steps:
+      - run:
+          name: Configure GPG private key for signing project artifacts in OSS Sonatype
+          command: |
+            echo $SECRING_GPG_ASC_BASE64 | base64 --decode | gpg --batch --no-tty --import --yes
+  deploy:
+    steps:
+      - attach_workspace:
+          at: .
+      - restore_cache:
+          key: maven-m2-{{ checksum "pom.xml" }}
+      - configure-gpg
+      - run:
+          name: Release new version to Maven Central
+          command: |
+            mvn -s .circleci/maven-release-settings.xml -Prelease deploy
+            mvn -s .circleci/maven-release-settings.xml -Prelease nexus-staging:close -DstagingDescription="closing to release"
+      - save_cache:
+          paths:
+            - ~/.m2
+          key: maven-m2-{{ checksum "pom.xml" }}
+workflows:
+  releases:
+    jobs:
+      - build-and-test:
+          filters:
+            branches:
+              ignore: /.*/
+            # only act on version tags
+            tags:
+              only: /v[0-9]+(\.[0-9]+)*.*/
+      - deploy-release:
+          requires:
+            - build-and-test
+          filters:
+            branches:
+              ignore: /.*/
+            # only act on version tags
+            tags:
+              only: /v[0-9]+(\.[0-9]+)*.*/
+  tests:
+    jobs:
+      - build-and-test:
+          filters:
+            branches:
+              ignore: nist-pages
+

.circleci/maven-release-settings.xml

@@ -0,0 +1,25 @@
+<settings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+	xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+	xsi:schemalocation="http://maven.apache.org/SETTINGS/1.0.0
+                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
+	<servers>
+		<server>
+			<!-- Maven Central Deployment -->
+			<id>ossrh</id>
+			<username>${env.SONATYPE_USERNAME}</username>
+			<password>${env.SONATYPE_PASSWORD}</password>
+		</server>
+	</servers>
+	<profiles>
+		<profile>
+			<id>gpg</id>
+			<properties>
+				<gpg.executable>gpg</gpg.executable>
+				<gpg.passphrase>${env.GPG_PASSPHRASE}</gpg.passphrase>
+			</properties>
+		</profile>
+	</profiles>
+	<activeProfiles>
+		<activeProfile>gpg</activeProfile>
+	</activeProfiles>
+</settings>

.github/CONTENTS.md

@@ -0,0 +1,7 @@
+# GitHub Supporting Files
+
+This directory contains supporting files for the project's GitHub repository. The structure and contents of the directory are as follows:
+
+* [ISSUE_TEMPLATE](ISSUE_TEMPLATE): This directory contains several templates for creating new issues in GitHub.
+* [issue_template.md](issue_template.md): This file contains a template for creating a new issue in GitHub containing a user story.
+* [PULL_REQUEST_TEMPLATE.md](issue_template.md): This file contains a template to be filled out for each GitHub pull request by the person submitting it.

.github/ISSUE_TEMPLATE/README.md

@@ -0,0 +1,7 @@
+# OSCAL GitHub Issue Template Files
+
+This directory contains templates for creating new project issues in GitHub. The structure and contents of the directory are as follows:
+
+* [bug_report.md](bug_report.md): This file contains a template for creating a new issue in GitHub to report a bug.
+* [question.md](question.md): This file contains a template for creating a new issue in GitHub containing a general question about the project.
+* [feature_request.md](feature_request.md): This file contains a template for creating a new issue in GitHub containing a user story.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,39 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+# Describe the bug
+
+{A clear and concise description of what the bug is.}
+
+# Who is the bug affecting?
+
+# What is affected by this bug?
+
+{Describe the impact the bug is having.}
+
+# When does this occur?
+
+{Describe the conditions under which the bug is occurring.}
+
+# How do we replicate the issue?
+
+{What are the steps to reproduce the behavior?
+1. Do this...
+1. Then this...
+1. See error
+
+If applicable, add screenshots to help explain your problem.}
+
+# Expected behavior (i.e. solution)
+
+{A clear and concise description of what you expected to happen.}
+
+# Other Comments
+
+{Add any other context about the problem here.}

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,26 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: User Story, enhancement
+assignees: ''
+
+---
+
+# User Story:
+
+As a project {stakeholder}, I {provide a clear and concise description of what the problem is. Ex. I need to be able to do}
+
+## Goals:
+
+{A clear and concise description of what you want to happen. This should be outcome focused. Include concise description of any alternative solutions or features you've considered. Feel free to include screenshots or examples about the feature request here.}
+
+## Dependencies:
+
+{Describe any previous issues or related work that must be completed to start or complete this issue.}
+
+## Acceptance Criteria
+
+- [ ] All website and readme documentation affected by the changes in this issue have been updated.
+- [ ] A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
+- [ ] The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,10 @@
+---
+name: Question
+about: Ask your question
+title: ''
+labels: question
+assignees: ''
+
+---
+
+{Please enter your question.}

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,17 @@
+# Committer Notes
+
+{Please provide a brief description of what this PR accomplishes. Be sure to reference any issues addressed. If the PR is a work-in-progress submitted for early review, please include [WIP] at the beginning of the title or mark the PR as `DRAFT`.}
+
+### All Submissions:
+
+- [ ] Have you followed the guidelines in our [Contributing](https://github.com/usnistgov/oss-maven/blob/master/CONTRIBUTING.md) document?
+- [ ] Have you checked to ensure there aren't other open [Pull Requests](https://github.com/usnistgov/oss-maven/pulls) for the same update/change?
+- [ ] Have you squashed any non-relevant commits and commit messages? \[[instructions](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History)\]
+- [ ] Do all automated CI/CD checks pass?
+
+### Changes to Core Features:
+
+- [ ] Have you added an explanation of what your changes do and why you'd like us to include them?
+- [ ] Have you written new tests for your core changes, as applicable?
+- [ ] Have you included examples of how to use your new feature(s)?
+- [ ] Have you updated all website and readme documentation affected by the changes you made?

.github/issue_template.md

@@ -0,0 +1 @@
+{Please describe the nature of your issue}

.gitignore

@@ -0,0 +1,8 @@
+.classpath
+.project
+.settings
+.checkstyle
+.factorypath
+.pmd
+.pmdruleset.xml
+/target/

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making 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, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes 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
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have 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 to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at oscal@nist.gov. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/