You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 11, 2019. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
@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.
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.
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.
The text was updated successfully, but these errors were encountered: