Should we alias @none to none (or similar)?

[jpstroop]

[from Rob]
The advantage of the language map pattern is you can do manifest.label.en to get the english labels for the manifest. We can't do that for no language without using the disliked ['@none'] pattern. Thus we should alias @none to something and discuss with JSON-LD WG if there's a best practice here

[azaroth42]

We /can/ - see json-ld playground: http://tinyurl.com/yd2v4mlu
I think we also should.

[zimeon]

If we decide to alias I would be tempted towards @azaroth42's noLanguage in the playground example in preference to none

[azaroth42]

Question - can we use scoped contexts to add the alias for @none ONLY within the properties that take a language?

Answer - Yes, and probably should: http://tinyurl.com/yd7cnfe7

[tomcrane]

👍 to "none"

[azaroth42]

Raised upstream clarification issue about the definition of @none in JSON-LD: w3c/json-ld-syntax#102

[mikeapp]

👍 to none

[zimeon]

Given (hopeful) clarification of JSON-LD description of @none to mean more than just "no language", I'm 👍 on none

[azaroth42]

So proposal from the editors is to alias @none as none using scoped contexts such that it only affects the language map properties.

[christopher-johnson]

👍 to none. This also facilitates GraphQL (it cannot query fields with @).

[zimeon]

none issues addressed by merge of #1810, the question os en-us split off into #1771. Closing