Language definition (what language the model, or it's individual parts is/are in. Multi-lingual model #169
FactEngineCommunity
started this conversation in
Ideas
Replies: 1 comment
-
|
Agreed! XML has had language specifiers for decades. RDF is using it extensively. If this is to be impactful for international organisations, we absolutely need this. And if not for business jargon, than at least to support the technical term (another language domain) ánd the business domain. If 'semantic' is to be taken serious, this needs to be able to get out of the single language use-case. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
If a Dataset, 'StockedItem', represents "Part is in Bin in Warehouse", and has a description, "A Stocked Item is where a Part is in a Bin within a Warehouse"...those are written in English.
Similarly, where a "Session" represents "Cinema is showing Film at DateTime" (for a Cinema Bookings model), that is the Name, one of its Fact Type Readings (e.g. "Film is showing at Cinema at DateTime" another) and those, again, in English.
At what level/s within the model will we say which language the model and its parts are in?
If the model is mono-Lingual, the language of interpretation can be listed at the Model level, an an AI or person might be able to deduce the language of the model and its parts, however for a multi-Lingual/Language model (and its parts) this may be more difficult.
So this discussion is about including the language of interpretation within the model itself, and where there seems to be an assumption at this stage of one-language-per-model (and where the examples, to this point seem to all be in English).
Beta Was this translation helpful? Give feedback.
All reactions