Description
Distinguish empty morphology values from an explicit missing marker.
Language-processing records depend on tokenization, indexing, null sentinels and text representation. A UTF-8 byte offset, UTF-16 index, dependency link or literal feature label can be handled precisely without inferring linguistic correctness or semantic equivalence.
Distinguish empty morphology values from an explicit missing marker.
When to use this tool
Use Morph Feature Empty Value Token when checking a supplied linguistic annotation, span, alignment or text-offset convention.
How to use the tool and how it works
- Enter name, value, emptyMarker. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read emptyValue, explicitlyMissing, featureKey. Inspect emptyValue, explicitlyMissing before interpreting the associated values.
Distinguish empty morphology values from an explicit missing marker. Require nonempty name/emptyMarker; emptyValue tests zero text length, explicitlyMissing tests literal marker equality, featureKey serializes name/value.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| name | Name | Required. Text; maximum UTF-16 length 8192. |
| value | Value | Required. Text; maximum UTF-16 length 8192. |
| emptyMarker | Empty Marker | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| emptyValue | Empty Value | Required. Boolean. |
| explicitlyMissing | Explicitly Missing | Required. Boolean. |
| featureKey | Feature Key | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"name": "Case",
"value": "",
"emptyMarker": "_"
},
"output": {
"emptyValue": true,
"explicitlyMissing": false,
"featureKey": "[\"Case\",\"\"]"
}
} Limitations and assumptions
- Neither condition is an inferred linguistic feature or a complete morphology-format validation.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Use the appropriate tokenizer, Unicode and annotation-format conventions and validate the complete text or tree for full linguistic processing.
References
Similar or alternative tools
- IPA Secondary Stress Position
Locate literal IPA secondary-stress markers.
- CoNLL-U Root Label Head Zero Check
Compare a CoNLL-U root label with zero head.