数据管道与 API 数据接入任务经常会遇到混合格式的标识符——例如现代 UUIDv7 主键、大写传统 GUID、哨兵常量,以及像 ULID 这样的非 UUID 令牌。下面是一个包含 7 行数据的具体批次示例,展示了 RFC 9562 验证器如何对每种情况进行分类与诊断。
多行候选输入示例
01941f29-7c7b-7a3c-9f4e-2b8d5c1a0e6f
550e8400-e29b-41d4-a716-446655440000
00000000-0000-0000-0000-000000000000
FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF
550e8400-e29b-91d4-a716-446655440000
550e8400-e29b-41d4-c716-446655440000
01ARZ3NDEKTSV4RRFFQ69G5FAV
逐行分类诊断报告
[
{
"line": 1,
"input": "01941f29-7c7b-7a3c-9f4e-2b8d5c1a0e6f",
"valid": true,
"classification": "UUIDv7",
"variant": "RFC 9562 (10xx)",
"normalized": "01941f29-7c7b-7a3c-9f4e-2b8d5c1a0e6f"
},
{
"line": 2,
"input": "550e8400-e29b-41d4-a716-446655440000",
"valid": true,
"classification": "UUIDv4",
"variant": "RFC 9562 (10xx)",
"normalized": "550e8400-e29b-41d4-a716-446655440000"
},
{
"line": 3,
"input": "00000000-0000-0000-0000-000000000000",
"valid": true,
"classification": "Nil UUID (RFC 9562 Section 5.9)",
"variant": "Nil (all zeros)",
"normalized": "00000000-0000-0000-0000-000000000000"
},
{
"line": 4,
"input": "FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF",
"valid": true,
"classification": "Max UUID (RFC 9562 Section 5.10)",
"variant": "Max (all ones)",
"normalized": "ffffffff-ffff-ffff-ffff-ffffffffffff"
},
{
"line": 5,
"input": "550e8400-e29b-91d4-a716-446655440000",
"valid": false,
"error": "Invalid version nibble '9' at position 15 (expected 1-8, or Nil/Max)"
},
{
"line": 6,
"input": "550e8400-e29b-41d4-c716-446655440000",
"valid": false,
"error": "Non-RFC-9562 variant nibble 'c' (110x Microsoft legacy GUID; expected 8, 9, a, or b)"
},
{
"line": 7,
"input": "01ARZ3NDEKTSV4RRFFQ69G5FAV",
"valid": false,
"error": "Invalid length (26 chars, Crockford Base32 ULID pattern; expected 36-char 8-4-4-4-12 hex)"
}
]
过滤后的规范化导出结果
导出有效行时,工具会按照 RFC 9562 第 4 节的要求,将所有大写十六进制字符统一规范化为标准小写形式:
01941f29-7c7b-7a3c-9f4e-2b8d5c1a0e6f
550e8400-e29b-41d4-a716-446655440000
00000000-0000-0000-0000-000000000000
ffffffff-ffff-ffff-ffff-ffffffffffff