-
Notifications
You must be signed in to change notification settings - Fork 20
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
Reframing Relationships #73
Labels
defer-future-version
Defer this issue until a future version of JSON-LD
Comments
This issue was discussed in a meeting.
View the transcriptReframing relationshipsRob Sanderson: #73 Rob Sanderson: There’s a graph in the first example, and they want to restructure it so that the actor created has an event. But they can not do everything they want. This looks like a new feature, so we should defer this to the next version, or wontfix. Gregg Kellogg: It begs the question: what is the purpose of framing? … You could keep adding features to lead to a complex construct language. … We should understand the boundaries of what framing is intended to do. … best practices might describe how you can do more advanced things using sparql constructs. Dave Longley: I would mark this as defer, for future discussion in a future version. We may not want to say outright that we don’t want this as a framing feature. Rob Sanderson: We would likely say no, but agreed. Proposed resolution: Defer framing #73 to future version, as new feature after the proposal window is closed (Rob Sanderson) Dave Longley: +1 Rob Sanderson: +1 Ruben Taelman: +1 Gregg Kellogg: +1 Jeff Mixter: +1 Ivan Herman: +1 David I. Lehn: +1 Pierre-Antoine Champin: +1 Resolution #5: Defer framing #73 to future version, as new feature after the proposal window is closed |
iherman
added
the
defer-future-version
Defer this issue until a future version of JSON-LD
label
Oct 18, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have the following data structure:
I would like to restructure it as:
In other words, the structure can be viewed as reifed data where:
and I need to instantiate its triple:
ex:actor-23456 -- exv:created --> ex:event-34567
Some framing issues are:
It seems wildcard matching is an all or nothing affair: match specific IRIs, everything {}, or nothing [], but not generic string matching. It would be useful for the frame matching to use regex patterns like "ex:relationship-.+". This is helpful when I don't have @type, but can create type based on the @id match.
Then, I can validate some pattern while framing. The framing could be:
to produce:
Yeah, I hate it too. It looks ugly, but I currently don't see a way around it.
The text was updated successfully, but these errors were encountered: