Open mvanbrab opened 2 years ago
For me it's fine to add a new warning, but I would not remove the current one because the fact that it's useless to you personally is not a valid reason to remove it.
It's useless to everybody, right?
How do you know that?
Can you explain the added value of that warning anyway? That situation doesn't lead anyone to unexpected mapping results; it's just telling you that you're over-specifying. If the new warning, signalling a situation that does lead to unexpected mapping results, is added, it will probably not be noticed, between all these other warnings.
It explains to the user that they are doing something redundant, while they might think that it's needed that they specify the datatype when they specify the language. I can understand that we put this as "info" instead of "warning".
That would be a good compromise indeed. To be effective, one would need a command line switch that can set the logging level. This is not available at this moment.
Issue type: :unicorn: Feature
Description
In my use case the YARRRML file is generated automatically, and always providing a datatype. For that purpose, my earlier feature request #160 was already implemented in v1.3.5. The new implementation gives a warning for that case:
That warning is rather useless and appears very frequently in my use case.
On the other hand, when another datatype (such as xsd:string) is specified in combination with a language tag, there is no warning. The behaviour of the parser in this case is to ignore the language tag and keep the datatype, which is OK. However, in this case, a warning like this one would be appreciated:
Summary: add second warning, remove first one.
Why it is useful
Useful when debugging missing language tags in mapper output, in the use case of automatically generated YARRRML files.
Existing features it breaks
None.
Example data
YARRRML input file:
RML output file (is OK):