docs: Removed broken links from README.md

[vaibhav45sktech]

• Removed broken GitHub source code path references from Ontology, DataParser, and Util sections
• Removed broken relative links (Build-from-Source-with-Maven, Installation, Run-from-Java-or-Scala, Run-from-a-JAR)
• Added HTML comments documenting which links were removed

solves issue #817

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates the README.md file to remove broken and outdated links, converting some bracketed namespace references to inline code formatting, and replacing non-functional links with updated resources. No functional code or public APIs are altered.

Changes

Cohort / File(s)	Summary
Documentation cleanup README.md	Removed duplicate word in Slack section; replaced broken image links with comments; converted bracketed namespace references to backtick-formatted code; updated "More tips" section with new DBpedia link and simplified phrasing; added comments noting removal of broken links throughout.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related issues

• Broken and outdated links in README.md #817: Directly addresses the same objective of removing and updating broken and outdated links in README.md documentation.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title clearly and concisely describes the main change: removing broken links from README.md, which aligns perfectly with the changeset's primary objective.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 182708c and 4c24d2f.

📒 Files selected for processing (1)

• README.md

🧰 Additional context used

🪛 LanguageTool

README.md

[uncategorized] ~7-~7: Did you mean the communication tool “Slack” (= proper noun, capitalized)?
Context: ...//dbpedia.slack.com/archives/C0L9MJFU7) slack channel within the DBpedia Slack worksp...

(ON_SKYPE)

---

[grammar] ~7-~7: Ensure spelling is correct
Context: ...a Slack workspace - the main point for [developement updates](https://github.com/dbpedia/ext...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🪛 markdownlint-cli2 (0.18.1)

README.md

130-130: Bare URL used

(MD034, no-bare-urls)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: long-running-tests
• GitHub Check: build
• GitHub Check: deploy
• GitHub Check: build
• GitHub Check: build

🔇 Additional comments (2)

README.md (2)

64-64: Documentation cleanup is appropriate.

Removing the broken Data flow image reference with an HTML comment is a clean way to document the change. This aligns well with the PR objective.

---

79-84: Well-executed link removal and documentation.

Converting the broken GitHub source code links to inline code formatting (backticks) for the namespace references and documenting the removal with HTML comments is a clear and maintainable approach. The namespace references are preserved in a readable format while broken links are cleanly removed.

[vaibhav45sktech]

It looks like the deploy job failed with a 403 Forbidden error because it's trying to upload artifacts from a forked repository. Since I don't have write access to the package registry, this step is expected to fail. @m1ci

[TallTed]

Suggested change

	**Slack**: join the [**#dev-team**](https://dbpedia.slack.com/archives/C0L9MJFU7) slack channel within the DBpedia Slack workspace - the main point for [developement updates](https://github.com/dbpedia/extraction-framework/blob/master/.github/workflows/maven.yml) and discussions <br/>
	**Slack**: join the [**#dev-team**](https://dbpedia.slack.com/archives/C0L9MJFU7) Slack channel within the DBpedia Slack workspace — the main point for [development updates](https://github.com/dbpedia/extraction-framework/blob/master/.github/workflows/maven.yml) and discussions <br/>

[TallTed]

Suggested change

	<!-- Data flow image removed - original link was broken -->
	<!-- original link to Data flow image was broken -- replaced by archive.org link -->
	

[TallTed]

Removed broken or outdated links and replaced with current resources.

This appears to be inaccurate. A more accurate statement appears to be "Removed broken or outdated links" which is far less helpful, especially when functioning links can be found or constructed. I've suggested a few already. Perhaps you can revise the other "Removed broken" changes?