GitHub issues vs. mailing list

Dear Fahad, dear all,

we had this discussion before, what to discuss where. Personally, I think
that "real" discussions are better placed on the mailing list, but that
summary or consensus should also go into a GitHub issue -- if that exists
--, so they are more findable. We could also do it the other way around,
but with summaries on GitHub, past issue discussions will be much more
concise, and much more digestible for future OntoLex contributors and users.

For the case at hand: Maybe let's wait for another week for people to make
up their mind, and if we arrive at a tentative consensus by then, we can
reply to the issue and summarize which possibility is preferred by the
community (and what we mean by "preferred by the community").

All the best,
Christian

Am Sa., 10. Juni 2023 um 19:24 Uhr schrieb Fahad Khan <fahad.khan@ilc.cnr.it
>:

> Dear all,
> I don't know if we're supposed to respond here or on github but I
> definitely agree with Christian's least invasive proposal of using
> dct:language (with the intention of resolving the dct:language,
> lime:language ambiguity of the whole document in later versions). In
> addition one of the examples which uses dct:language in the report (the
> bank example in Section 3.3) has a slight error, it uses the namespace odct
> instead of dct.
> Cheers
> Fahad
>
> Il giorno sab 10 giu 2023 alle ore 02:41 Christian Chiarcos <
> christian.chiarcos@gmail.com> ha scritto:
>
>> Dear OntoLex community,
>>
>> in a discussion with Manuel Fiorelli, we recently spotted an issue with
>> the core diagram, in that it seems to suggest a property "ontolex:language"
>> where the text uses "dct:language" (core section) and
>> "lime:language"/"dct:language" (lime section), instead.
>>
>> Details under https://github.com/ontolex/ontolex/issues/37.
>>
>> The least invasive fix is to replace "language" in the diagram with the
>> correct properties. My preference on that is to use "dct:language" (as in
>> the examples in core section). Alternatively, we might give both
>> "dct:language" and "lime:language" (I'd find that confusing for a
>> first-time user) or "lime:language" only (this contradicts examples in core
>> ... unless these are fixed).
>>
>> As there are three options, people in the community might want to
>> discuss. My preference is to use `dct:language` here, only, because it
>> doesn't require other changes in the text and doesn't confuse first-time
>> users.
>>
>> Best,
>> Christian
>>
>