Unverified50% confidenceFactExact time
The N-PORT XML filing template imposes mandatory constraints on most identifier fields, and filers fill in sentinel values such as "N/A", "000000000" and "999999999" to satisfy format validation when there is no corresponding value, rather than leaving them blank.
1
Sources
50%
Confidence
Long-term
Relevance
10/17/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe SEC dataset documentation describes the IDENTIFIER_TICKER field only with the word "Ticker", whereas Form N-PORT Item C.1.e requires "at least one" other identifier (ISIN, Ticker (if ISIN is unavailable) or other identifier) and does not require it to be an exchange code.63% similarUnverifiedHard rules for handling signed XML include: prohibit multiple parsers from processing the same security-sensitive XML, perform C14N before signature verification and extract identity based on the canonicalized result, strictly validate namespaces, and use absolute paths in XPath.61% similarUnverifiedThe one-time nonce (Number Used Once) mechanism attaches a random string to each authorization credential; after the server consumes it, the nonce is marked as used, and any subsequent request with the same nonce is rejected outright.61% similarUnverifiedA common practice in n8n workflows is to first use email as the primary key for exact deduplication, then use name plus phone number for a secondary fuzzy verification.60% similarUnverifiedEffects with their Message-ID should be logged at the point where the effect occurs (in the provider or relay acceptance log), and execution counts should never be tracked inside n8n.58% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1053997API
curl https://kongchang.com/api/v1/knowledge/claims/1053997MCP
get_claim(id=1053997)