Hi Tom,

makes sense (although this is a bit of a corner case since the value violates the constraint). I have changed

    http://datashapes.org/forms.html#TextFieldWithLangEditor

to go from 10 to 11. I also clarified that both xsd:string and rdf:langString must be allowed (sh:or) as datatypes.

Does this look better to you?

Thanks,
Holger


On 11/21/2020 7:45 PM, Tomek Pluskiewicz wrote:
Hi Holger

Yes, thank you.

I’m combing up with a follow up, having actually implemented this in our forms. Consider a shape which has `sh:datatype rdf:langString` and a value which is a plain string literal. Both single line editors will get a score = 10. This can cause an underterministic behavior where one or the other comes on top.

I think that a property which is explicitly constrained to tagged string should actually prefer the lang editor over plain text box.

Best
Tom

On 6 November 2020 at 07:35:00, Holger Knublauch (hol...@topquadrant.com <mailto:hol...@topquadrant.com>) wrote:

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 topbraid-users+unsubscr...@googlegroups.com <mailto:topbraid-users+unsubscr...@googlegroups.com>. 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 a topic in the Google Groups "TopBraid Suite Users" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/topbraid-users/HOgbOdYh8dc/unsubscribe <https://groups.google.com/d/topic/topbraid-users/HOgbOdYh8dc/unsubscribe>. To unsubscribe from this group and all its topics, send an email to topbraid-users+unsubscr...@googlegroups.com <mailto:topbraid-users+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/b1a95671-ba59-70a7-35f8-5d9943643181%40topquadrant.com <https://groups.google.com/d/msgid/topbraid-users/b1a95671-ba59-70a7-35f8-5d9943643181%40topquadrant.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 topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/fd279b31-5ff9-b7e3-e2eb-26018405f60a%40topquadrant.com.

Reply via email to