Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Triple Terms in Subject Position #138

Open
rat10 opened this issue Jan 17, 2025 · 1 comment
Open

Triple Terms in Subject Position #138

rat10 opened this issue Jan 17, 2025 · 1 comment
Labels
ms:CR Milestone: Candidate Recommendation spec:substantive Change in the spec affecting its normative content (class 3) –see also spec:bug, spec:new-feature

Comments

@rat10
Copy link

rat10 commented Jan 17, 2025

Should triple terms be allowed in subject and object position of triples and triple terms or only in object position.

@rat10 rat10 added the ms:CR Milestone: Candidate Recommendation label Jan 17, 2025
@rat10
Copy link
Author

rat10 commented Jan 17, 2025

The issue in question is if triple terms should be only allowed in object position or also in subject position. The Abstract Grammar as defined in the "liberal baseline" allows them in both positions. However, it is an open discussion if allowing them in subject position is harmful in practice. This discussion has so far mainly taken place in the Semantics TF, but it is of general concern, as its outcome determines if a whole class of use cases can be tackled with triple terms, or not.

The discussion is spread over several Github issues, but the most recent thread is triple terms in subject position - issues with RDF/XML?. For a tl;dr just scroll down to the last two comments to get Niklas' and my position.

Please excuse that so far this is a rather sparse description of the issue. I hope to update it with a more thorough treatment and more links after today's Semantics TF meeting.

This discussion depends on the WG's decision to adopt the "liberal baseline" semantics as suggested by the Semantics TF.

@rat10 rat10 added the spec:substantive Change in the spec affecting its normative content (class 3) –see also spec:bug, spec:new-feature label Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ms:CR Milestone: Candidate Recommendation spec:substantive Change in the spec affecting its normative content (class 3) –see also spec:bug, spec:new-feature
Projects
None yet
Development

No branches or pull requests

1 participant