Hi Tom,
On the first topic, maybe the wording needs to be clarified, but the two
cases are different:
10 is only returned if the widget is for an *existing* value, and that
value is a rdf:langString literal
5 is returned for new "empty" values, e.g. on a yet unfilled form, and
the property does not exclude langString
On the singleLine you are right, this looks like a bug: It should say
that dash:singleLine != false. The intent is that if someone explicitly
states singleLine=false then the TextAreaWithLang should be preferred. I
have just fixed this, both in the spec and in our code and see how it
behaves.
Does this make sense to you?
Thanks
Holger
On 11/6/2020 1:48 AM, Tomasz Pluskiewicz wrote:
Hello
We've looked at the scoring and implementation of
dash:TextFieldWithLangEditor and find the rules a little inconsistent.
Particularly, it seems that *5* will never be returned because if
*rdf:langString* is permitted, the first run will always be hit and
score = 10 returned.
Also, why exclude *dash:singleLine *from this editor?
Best,
Tom
--
You received this message because you are subscribed to the Google
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/1ee443c2-bbe8-4c11-af46-624c8dd1c0d3n%40googlegroups.com
<https://groups.google.com/d/msgid/topbraid-users/1ee443c2-bbe8-4c11-af46-624c8dd1c0d3n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups "TopBraid
Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/b1a95671-ba59-70a7-35f8-5d9943643181%40topquadrant.com.
