GithubHelp home page GithubHelp logo

Comments (7)

lanthaler avatar lanthaler commented on July 22, 2024

Feedback:

Thomas Steiner: +1 for no. 1
Personally I'm also a big friend of HTTP headers (remember the @context discussion?) to keep the actual payload clean, so I could also imagine an HTTP header like "Content-Language: en".
The overall opinion with @context was that HTTP headers are not considered the most suitable solution for a number of reasons.

Ivan Herman: +1 for no. 1

Gregg Kellog: +1 for no. 1, +0 for 1B, -1 for no 2

Markus Lanthaler: +1 for no. 1
+1 but perhaps we should move @language into the context description. The "meaning" of the document is described in the context so I think that's the place to be for the @language tag as well.

from json-ld.org.

lanthaler avatar lanthaler commented on July 22, 2024

Ivan Herman:
I would also feel it more natural if this was part of the @context. It would also make it clear/clean that children of a node would inherit the language setting, just like any other contextual settings.

Thomas Steiner:
Oh, I instinctively assumed it would be part of the @context. -1 on any proposition different from that. +1 for putting @language in the @context.

Alexandre Passant:
+1 for having it in the context.
And for also supporting separately in the headers - using Content-Language.

from json-ld.org.

gkellogg avatar gkellogg commented on July 22, 2024

+1, I had mistakenly read the example as putting it @context, this is where it should go,

Also, as with other stuff in @context, it applies through all sub-nodes, unless overridden by another definition. (@language = null might clear a setting.

from json-ld.org.

msporny avatar msporny commented on July 22, 2024

@language in @context is accepted. @langmap is rejected.

from json-ld.org.

msporny avatar msporny commented on July 22, 2024

http://json-ld.org/spec/ED/json-ld-syntax/20120122/#default-language

from json-ld.org.

niklasl avatar niklasl commented on July 22, 2024

Great. Just to be clear, although it is said that "apply a particular language code to all string values", I expect it is still the case that a @language in the context does not apply to coerced values, right?

I.e. the language should apply to all string values except those which are coerced, including coerced to xsd:string (which is needed to exclude certain expressions from improperly having a language applied).

from json-ld.org.

lanthaler avatar lanthaler commented on July 22, 2024

Niklas, I think we should discuss this in issue #64.

from json-ld.org.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.