Implement oekg predicates

[madbkr]

Summary of the discussion

As discussed in #2013 we need some more predicates to use in the OEKG. Some of those are implemented here as discussed in the issue.

Type of change (CHANGELOG.md)

Add

• has iri, has study descriptor tag, has uuid, has scenario type, has publication date, has report title, has doi, has reference, based on sector division

Workflow checklist

Automation

Closes #

PR-Assignee

• [ x] 🐙 Follow the Pull Request Workflow
• [x ] 📝 Update the CHANGELOG.md
• [x ] 📙 Add #'s to term tracker annotation

Reviewer

• 🐙 Follow the Reviewer Guide
• 🐙 Provided feedback and show sufficient appreciation for the work done

[stap-m]

My remarks on has number and object property vs data property seem to apply to more than has iri.

[stap-m]

Suggested change

	OEO_00140178 some rdfs:Literal
	OEO_00140178 some rdfs:Literal

why has number? A literal can also be a string... https://www.w3.org/TR/rdf-schema/#ch_literal

I have the impression that has iri should be a data property itself. Like this, the range could be rdfs:literal directly.

[stap-m]

Maybe we need a new data property for that. Has literal value?