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

_link_ should be a value function on whatever is in predicate #15

Open
rsinger opened this issue Aug 29, 2014 · 2 comments
Open

_link_ should be a value function on whatever is in predicate #15

rsinger opened this issue Aug 29, 2014 · 2 comments

Comments

@rsinger
Copy link
Member

rsinger commented Aug 29, 2014

Currently, the predicate property is required, but ignored for link fields.

For predicates that are URIs, you should be able to:

"fieldName":"fooLink",
"predicates":["foo:uri"]
"value":"_link_"

and it creates a fully qualified URI from the value of foo:uri.u (as opposed to _id.r).

There are a few questions, however:

  1. What happens if there is more than 1 value in "predicates"?
  2. What if "predicates" value is not a URI?
@scaleupcto
Copy link
Contributor

I would say:

  1. All of them get the _link_ treatment
  2. I would say just output the literal value. Although it makes little sense to apply a _link_ to a literal, I'm not sure it should be a fail condition. Especially seeing that the predicates array could be a mixed economy of resources and literals, and bad data modelling decisions could even see different values same predicate having literal and resource versions.

@rsinger
Copy link
Member Author

rsinger commented Aug 29, 2014

Yeah, both of those seem reasonable to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants