Skip to content
This repository has been archived by the owner on Nov 11, 2019. It is now read-only.

Textual property value does not use language of the element #61

Closed
gkellogg opened this issue Jun 28, 2017 · 4 comments
Closed

Textual property value does not use language of the element #61

gkellogg opened this issue Jun 28, 2017 · 4 comments

Comments

@gkellogg
Copy link
Member

The Values section does not make use of the language of the element (as established using @lang or @xml:lang on an ancestor or self).

This could certainly pertain to the textContent of an element and potentially the value of the @content attribute. RDFa uses the current language when creating a literal from @content, but it could be argued either way.

Of course, the JSON expression cannot make use of the language, but it is useful to have in an abstract model for the purposes of generating RDF or JSON-LD.

@chaals
Copy link
Collaborator

chaals commented Jun 29, 2017

It makes sense, if we put in how to generate RDFa/JSON-LD, to collect the language info there...

@chaals
Copy link
Collaborator

chaals commented Jun 29, 2017

Is this a duplicate of #21?

@gkellogg
Copy link
Member Author

@chaals I interpreted you discussion in #21 to be about more than @lang, more about the use of XMLLiteral (or HTML) in RDFa. So, the issues may require a somewhat different resolution.

@chaals
Copy link
Collaborator

chaals commented Jun 30, 2017

OK. I think these are duplicates - my point regarding XMLLiteral etc is that while Microdata is weak for internationalisation, there is a solution based on shifting the microdata to RDFa...

Closing this as a duplicate, I'll take the discussion back to #21 in particular so the i18n people can follow it more easily.

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

No branches or pull requests

2 participants