Follow these steps to create and publish this repository to your GitHub account.
- Go to https://github.com/new
- Repository name:
meeting-transcript-ontology - Description: "A comprehensive SHACL 1.2 ontology for converting meeting transcriptions into structured RDF knowledge graphs"
- Choose: Public (or Private if you prefer)
- DO NOT initialize with README, .gitignore, or license (we already have these)
- Click "Create repository"
Open your terminal and navigate to the project directory, then run:
cd /path/to/meeting-transcript-ontology
# Initialize git repository
git init
# Add all files
git add .
# Create initial commit
git commit -m "Initial commit: Meeting Transcript Ontology with SHACL 1.2"
# Rename branch to main (if needed)
git branch -M mainReplace [your-username] with your actual GitHub username:
git remote add origin https://github.com/[your-username]/meeting-transcript-ontology.git
# Or if you use SSH:
git remote add origin git@github.com:[your-username]/meeting-transcript-ontology.gitgit push -u origin mainYou may be prompted for your GitHub credentials. If you have 2FA enabled, you'll need to use a Personal Access Token instead of your password.
On your GitHub repository page:
- Click the gear icon next to "About"
- Add topics:
semantic-web,rdf,shacl,knowledge-graph,ontology,meeting-intelligence,sparql,rdf-star,context-graphs,decision-tracking - Click "Save changes"
To publish documentation:
- Go to Settings → Pages
- Source: Deploy from a branch
- Branch:
main, folder:/docs - Click "Save"
Your documentation will be available at: https://[your-username].github.io/meeting-transcript-ontology/
- Go to Releases → "Create a new release"
- Tag:
v1.0.0 - Title: "Initial Release: Meeting Transcript Ontology v1.0.0"
- Description:
First stable release of the Meeting Transcript Ontology Features: - Complete SHACL 1.2 ontology for meeting transcriptions - 11 core classes with comprehensive properties - 6 SHACL rules for automated inference - RDF-Star support for rich annotations - Wikidata entity linking - Example queries and documentation See README.md for full documentation. - Click "Publish release"
meeting-transcript-ontology/
├── README.md # Main documentation
├── LICENSE # MIT License
├── .gitignore # Git ignore rules
├── ontology/
│ └── meeting-transcript-ontology.ttl
├── examples/
│ ├── meeting-transcript-rdf.ttl # Example RDF data
│ └── sample-meeting-transcript.txt # Sample transcript
└── docs/
├── original-prompt.txt # Project requirements
├── example-queries.md # SPARQL query examples
└── QUICKSTART.md # Quick start guide
After creating the repository, update the citation in README.md:
@software{meeting_transcript_ontology,
title = {Meeting Transcript Ontology: A SHACL-based Framework for Decision Tracking},
author = {Cagle, Kurt},
year = {2026},
url = {https://github.com/[your-username]/meeting-transcript-ontology}
}Replace [your-username] with your actual GitHub username.
If you get authentication errors:
- Generate a Personal Access Token: GitHub Settings → Developer settings → Personal access tokens → Tokens (classic)
- Select scopes:
repo(all) - Use the token as your password when pushing
If using SSH and getting permission denied:
- Check your SSH key is added to GitHub: Settings → SSH and GPG keys
- Test connection:
ssh -T git@github.com
If you add large files in the future (>50MB), consider using Git LFS:
git lfs install
git lfs track "*.mp4" # example for video files
git add .gitattributes- Add to your blog post - Include the GitHub link in your Context Graphs blog post
- Share on social media - Twitter/LinkedIn with hashtags: #SemanticWeb #KnowledgeGraphs #RDF
- Submit to awesome lists - Consider submitting to awesome-semantic-web lists
- Enable discussions - Settings → Features → Enable Discussions for community engagement
Remember to:
- Accept pull requests that improve the ontology
- Respond to issues in a timely manner
- Update the ontology version in releases when making changes
- Keep documentation synchronized with code changes
- Add new example queries as use cases emerge
If you encounter any issues with these instructions, feel free to:
- Check GitHub's documentation: https://docs.github.com
- Ask in GitHub Community: https://github.community
- Open an issue in your repository once it's created