Whitespace management: remove excess whitespace in long quoted literals

[kouralex]

There already exists a whitespace trimming mechanism in Skosify, however, it does not take into account long quoted literals such as

""" This is an  example
of a long quoted
literal
which is     ridden    with   
   whitespace  
"""

in which the whitespace in the middle of the literal (between words and at line starts/endings) is preserved.
I would prefer the example above to be stripped into

"""This is an example
of a long quoted
literal
which is ridden with
whitespace"""

I believe that there could be an option that sets how whitespace is trimmed as sometimes whitespace may very well be intended and meaningful. At least line breaks are such a feature - I wonder what would be the best option for setting them as, for example, meaningful HTML entities. I can already think of two line breaks to be different from single one in these cases as well as in general.

Also, I wonder if long quoted literals could be switched into single quoted literals and vice versa (when applicable) based on an option, even though they yield the very same information.

Any thoughts on this, @osma ?

[osma]

PR welcome ;) Do you have any examples of a vocabulary where this is a problem?

Regarding literal quote style: there is no semantic difference between single quoted vs. triple-quoted literals in Tutle. It is up to the serializer (i.e. rdflib) to choose the appropriate quoting style. I believe the choice depends on whether the literal includes newlines or not. I don't see this as something Skosify should try to control.

[kouralex]

Heh, I might come up one, if only we can agree on behavior. :)

I am currently working on https://finto.fi/ykl/ and there exists these things I mentioned even in preferred labels - one can download the skosify'd file and search for, e.g., \s".*\ \ (won't catch long quoted triple cases, though).

And for the latter comment, I certainly know that there is no semantic difference, however, I had some use case on my mind but it probably isn't a good idea anyway (would complicate things) as you pinpointed.