知识卡片
文本格式与模式校验取舍
XML用标签和模式表达丰富结构并可验证;JSON用名称值与数组减少文本冗余、贴近常见语言数据。二者都需协议语义,JSON并非没有模式,XML的验证能力也有解析与资源成本。实际大小和性能应依消息、库与约束测量,不把书内总体比较当所有负载的固定结论。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 软件接口 · 查看原书依据
Compared to XML, however, JSON is significantly less verbose, as field names occur only once. Using a name/value representation instead of start and end tags, JSON documents can be parsed as they are read.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第15章《软件接口》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch15.html)
- 结论依据:所引连续原文给出本卡机制或取舍;条件与示例结合本节已读上下文解释。
- 原始内容:Compared to XML, however, JSON is significantly less verbose, as field names occur only once. Using a name/value representation instead of start and end tags, JSON documents can be parsed as they are read.