Re: total number of search results (prior to pagination)?
Reply #20 –
It's not critical or anything, just my perfectionism showing.
I'll explain though, schema.org offers a feature to annotate <form> elements with constraints for the expected values.
So the SearchAction's query property contains our search-term, and the query-input property contains the annotation.
Here's the annotation thus far.
<span property="schema:query-input" typeof="schema:PropertyValueSpecification">
<meta property="schema:valueName" content="search" />
<meta property="schema:valuePattern" content="/[^\s]{2,100}$/" />
<meta property="schema:valueMinLength" content="2" />
<meta property="schema:valueMaxLength" content="100" />
<link property="schema:valueRequired" href="http://schema.org/True" />
<link property="schema:multipleValues" href="http://schema.org/True" />
</span>
Note the valuePattern property, this value is a regular expression pattern for "search=term". Currently, my regex states the <input name="search" /> accepts 2-100 characters and ignores spaces. For this to be more accurate, it should state that it accepts 2-100 characters, ignores spaces but each "word" needs to be at least 2 characters long.
The corrected regex should match like so:
t - no match
th 1 match
th r 1 match 1 fail
th re 2 matches
On Second Thought
Nevermind, i was way too focused on that regex that i didn't consider the multipleValues=true accomplishes what i intended in concert with the existing regex. So i was right and thought i was wrong and now it's all nevermind.