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

@set in the data does not override @list in the context #548

Open
pchampin opened this issue Aug 22, 2022 · 1 comment
Open

@set in the data does not override @list in the context #548

pchampin opened this issue Aug 22, 2022 · 1 comment

Comments

@pchampin
Copy link
Contributor

I ran into this issue while trying to find an acceptable output for the code in #547. It would, IMO, look like this:

{
  "@context": {
    "prop": {
      "@id": "http://schema.org/prop",
      "@container": "@list"
    }
  },
  "prop": {"@set": [
    ["foo", "bar"],
    ["baz", "qux"]
  ]}
}

I would expect the @set on line 8 to override the @container: @list in the context, so that this expands back to the original code in #547. But instead, this expands into a @list of @lists in the JSON-LD playground, PyLD, and the Ruby distiller. The @set keyword is simply ignored.

Do others share my expectation that @set in this example should override the @list from the context?

@gkellogg
Copy link
Member

gkellogg commented Sep 1, 2022

Agreed, it might be treated as a set of lists, instead.

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

No branches or pull requests

2 participants