PeopleSearchParseQuestion
pair, tag or yesno.
The tag the question is about (NAME for the name law).
options object[]required
fix objectrequired
The user's answer to a parse question or a tap on a chip: {start, end, tag}; tag: "O" =
not a fact. start / end are code-point offsets into the NORMALIZED line (what
POST /people-search/parse read). The schema's own caps — at most 8 fixes, tag at most
16 code points, start / end at most 200 — are checked first and are a 400
(input_too_long / input_invalid). Within them, a fix is kept only when its tag is a
tagger tag ([A-Z_]{1,16}: O, NAME, LOC, …) and 0 ≤ start < end ≤ the normalized
line's length — any other is dropped, not refused (a stale fix of an edited line must not
fail the request).
Possible values: >= 0 and <= 200
Possible values: >= 0 and <= 200
Possible values: <= 16 characters
default object
The user's answer to a parse question or a tap on a chip: {start, end, tag}; tag: "O" =
not a fact. start / end are code-point offsets into the NORMALIZED line (what
POST /people-search/parse read). The schema's own caps — at most 8 fixes, tag at most
16 code points, start / end at most 200 — are checked first and are a 400
(input_too_long / input_invalid). Within them, a fix is kept only when its tag is a
tagger tag ([A-Z_]{1,16}: O, NAME, LOC, …) and 0 ≤ start < end ≤ the normalized
line's length — any other is dropped, not refused (a stale fix of an edited line must not
fail the request).
Possible values: >= 0 and <= 200
Possible values: >= 0 and <= 200
Possible values: <= 16 characters
{
"kind": "string",
"text": "string",
"start": 0,
"end": 0,
"read": "string",
"alt": "string",
"ask": "string",
"why": "string",
"p": 0,
"options": [
{
"answer": "string",
"tag": "string",
"label": "string",
"fix": {
"start": 0,
"end": 0,
"tag": "string"
}
}
],
"default": {
"start": 0,
"end": 0,
"tag": "string"
}
}