Update rdf-terminology.md from semi-transparent to semi-opaque #71
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
2 reasons to use semi-opaque instead of semi-transparent:
the term semi-opaque is shorter than semi-transparent and therefore more economical to utter. If there is no other reason for which variant to chose then this should make the difference.
more seriously, the fact that some terms are treated as opaque is what differentiates the semi-transparent/opaque semantics from the standard RDF semantics (which is fully transparent). IMHO emphasizing what is different instead of what is the same improves understanding.