diff --git a/diagrams-and-tables/annotations/cn_diagram_01.json b/diagrams-and-tables/annotations/cn_diagram_01.json new file mode 100644 index 0000000000000000000000000000000000000000..a21dccedb4b7d325592bd6aef46b6f3d5cf35768 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_01.json @@ -0,0 +1,107 @@ +[ + { + "type": "title", + "text": "2.2.3 英特尔® Geti™ 平台" + }, + { + "type": "title", + "text": "intel GeTi" + }, + { + "type": "text", + "text": "英特尔® Geti™ 平台使企业团队能够快速构建计算机视觉 AI 模型。通过直观的图形界面，用户可以添加图像或视频数据、进行标注、训练、重新训练、导出以及优化 AI 模型以便部署。配备了最先进的技术，如主动学习、任务链和智能标注，英特尔® Geti™ 平台减少了劳动密集型任务，实现了协作模型开发，并加快了模型创建的速度。\n\n英特尔® Geti™ 平台提供的功能包括：\n\n• 定制化的计算机视觉任务：英特尔® Geti™ 平台加速了 AI 任务的模型创建，如分类、对象检测、语义分割或异常检测。\n• 直观的用户界面：英特尔® Geti™ 平台提供了便捷的图形用户界面和交互功能，如标注助手，允许几乎没有 AI 经验的团队成员协助计算机视觉模型训练。\n• 任务链：使用英特尔® Geti™ 平台，用户可以通过链接两个或更多任务来训练模型，而无需编写额外的代码，从而使用多步骤的智能应用程序。\n• 智能标注：英特尔® Geti™ 平台提供了使用铅笔、多边形工具和 OpenCV GrabCut 等绘图功能加速数据标注和图像分割，提高用户体验。\n• 超参数优化：英特尔® Geti™ 平台内置的优化方法使数据科学家的工作变得更加轻松，通过精炼对模型学习过程至关重要的超参数。\n• 生产就绪的模型：英特尔® Geti™ 平台输出的深度学习模型可以是 TensorFlow* 或 PyTorch* 格式。该平台还可以输出为 OpenVINO™ 工具包优化的模型，以便在英特尔® 架构的 CPU、GPU 和 VPU 上运行。" + }, + { + "type": "title", + "text": "英特尔® Geti™ 平台的优势" + }, + { + "type": "text", + "text": "• 节省时间：英特尔® Geti™ 平台通过提供一个无需编码的直观平台，帮助缩短开发 AI 应用计算机视觉模型所需的时间。这加快了通常需要长时间训练计划的自定义 AI 模型创建的工作流程。\n• 节省成本：英特尔® Geti™ 平台有助于消除进入 AI 领域的障碍（如培训或支付专业服务费用），使计算机视觉 AI 建模对各种组织更加容易和经济高效，特别是对于较小的公司来说。降低与人员培训相关的成本进一步增加了整体价值。\n• 灵活部署：英特尔® Geti™ 平台可以在本地部署或通过云虚拟机部署，为那些使用这两种基础设施之一或两者的组织提供灵活性。" + }, + { + "type": "title", + "text": "英特尔® Geti™ 平台的使用流程示例" + }, + { + "type": "diagram_caption", + "text": "图：使用英特尔® Geti™ 平台训练 AI 模型的流程示意图" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "1 数据收集" + }, + { + "id": "B", + "text": "2 主动集" + }, + { + "id": "C", + "text": "3 标注" + }, + { + "id": "D", + "text": "4 训练" + }, + { + "id": "E", + "text": "5 优化" + }, + { + "id": "F", + "text": "6 导出" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D", + "label": "主动学习" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "D", + "label": "预测" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "G", + "target": "C" + }, + { + "source": "H", + "target": "B" + } + ] + }, + { + "type": "text", + "text": "02 英特尔® 技术方案" + }, + { + "type": "page_number", + "text": "35" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_02.json b/diagrams-and-tables/annotations/cn_diagram_02.json new file mode 100644 index 0000000000000000000000000000000000000000..8170a43e8583e80603c02519b2cd925b1fe7dc2e --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_02.json @@ -0,0 +1,101 @@ +[ + { + "type": "text", + "text": "机器学习模型部署在英特尔® 私有云中的高性能计算服务器上，使用英特尔® 至强® 可扩展处理器进行训练。模型在数十万张晶圆图像上训练之后，部署到生产线的边缘位置。边缘上的模型推理工作负载（在摄像头控制器上）可以卸载到英特尔® ARC A770 独立 GPU 上，以加速图像分析。英特尔® 至强® 可扩展处理器提供强大的计算能力来处理繁重的工作负载，加快训练过程。根据我们的经验，模型训练的速度比使用其他处理器快达 50%，现阶段每季度进行一次完整迭代训练流程（如下图）。" + }, + { + "type": "diagram_caption", + "text": "Figure. Our solution spans the entire machine-learning lifecycle, from raw data acquisition and labeling to training and validation to deployment." + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Machine-Learning Lifecycle" + }, + { + "id": "B", + "text": "Acquire Image" + }, + { + "id": "C", + "text": "Label Data" + }, + { + "id": "D", + "text": "Machine-Learning Model Training" + }, + { + "id": "E", + "text": "Validation" + }, + { + "id": "F", + "text": "Deployment" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "E", + "target": "F" + } + ] + }, + { + "type": "text", + "text": "收集的图像由包含 50 个底层核心算法的混合机器学习模型分析，包括各种如基于 ResNet50 的检查、语义剪辑分割（以实现像素级的缺陷识别）以及识别和测量（自动识别图像中的边缘类型和自动测量距离）等功能。模型经英特尔® OpenVINO™ 工具包优化，提高在英特尔® 硬件平台上的效率。工业视觉控制软件支持图像审查和模拟，所有功能以模块形式集成，便于扩展应用，支持低代码操作和流程向导。" + }, + { + "type": "title", + "text": "方案优势" + }, + { + "type": "text", + "text": "标准化设计实现了快速部署和易于扩展到新的用例。该解决方案能够准确识别晶圆研磨过程中的多种类型缺陷，包括凹痕、各种大小的划痕、研磨痕迹、污点、裂纹、气泡、晶圆偏移和安装偏移。与离线检查相比，使用在线检查可以更早地检测到多达 50% 的晶圆研磨问题。当警报响起时，可以对晶圆进行返工，这避免了下游过程中的整片晶圆分层。更重要的是，该解决方案超越了离线计量所能实现的：在问题发生时检测偏差，检测过程缺陷并迅速关闭工具，实现了检查框架清洁度和内环的新能力。\n\n帮助工厂实现业务效益：\n• 避免废品，每年为工厂节省高达 200 万美元。\n• 降低了业务风险。\n• 更高的产品质量。\n• 使工程师免于繁琐的手动离线检查。" + }, + { + "type": "text", + "text": "03 成功案例" + }, + { + "type": "footer", + "text": "intel." + }, + { + "type": "page_number", + "text": "48" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_03.json b/diagrams-and-tables/annotations/cn_diagram_03.json new file mode 100644 index 0000000000000000000000000000000000000000..bd5b05931e9e200ac5445ba05717a427afe3ce49 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_03.json @@ -0,0 +1,244 @@ +[ + { + "type": "title", + "text": "4.2.3 工业电脑优选项目申请流程与节点安排" + }, + { + "type": "title", + "text": "项目时间线" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "申请意向确认 提交申请材料" + }, + { + "id": "B", + "text": "测试及验证申请" + }, + { + "id": "C", + "text": "签发及相关测试函 市场推广活动" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "C" + } + ] + }, + { + "type": "title", + "text": "项目流程" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "提交线上报名申请" + }, + { + "id": "B", + "text": "发送申请材料(产品规格信息、报名表、第三方机构测试报告等)" + }, + { + "id": "C", + "text": "英特尔项目团队初审" + }, + { + "id": "D", + "text": "材料齐全?" + }, + { + "id": "E", + "text": "客户使用软件调优测试工具测试并将寄送样机至英特尔复测" + }, + { + "id": "F", + "text": "技术工程对接及验证" + }, + { + "id": "G", + "text": "是否通过测试?" + }, + { + "id": "H", + "text": "签发测试函" + }, + { + "id": "I", + "text": "签收测试函" + }, + { + "id": "J", + "text": "申请" + }, + { + "id": "K", + "text": "验证" + }, + { + "id": "L", + "text": "签发" + }, + { + "id": "M", + "text": "客户" + }, + { + "id": "N", + "text": "英特尔" + }, + { + "id": "O", + "text": "20天" + }, + { + "id": "P", + "text": "30天" + }, + { + "id": "Q", + "text": "20天" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "J" + }, + { + "source": "A", + "target": "M" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D", + "label": "否" + }, + { + "source": "B", + "target": "J" + }, + { + "source": "B", + "target": "M" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "J" + }, + { + "source": "C", + "target": "N" + }, + { + "source": "D", + "target": "F", + "label": "是" + }, + { + "source": "D", + "target": "J" + }, + { + "source": "D", + "target": "N" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "E", + "target": "G", + "label": "否" + }, + { + "source": "E", + "target": "K" + }, + { + "source": "E", + "target": "M" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "F", + "target": "K" + }, + { + "source": "F", + "target": "N" + }, + { + "source": "G", + "target": "H", + "label": "是" + }, + { + "source": "G", + "target": "K" + }, + { + "source": "G", + "target": "N" + }, + { + "source": "H", + "target": "I" + }, + { + "source": "H", + "target": "L" + }, + { + "source": "H", + "target": "N" + }, + { + "source": "I", + "target": "L" + }, + { + "source": "I", + "target": "M" + } + ] + }, + { + "type": "text", + "text": "04 合作伙伴加速项目和产品推荐" + }, + { + "type": "footer", + "text": "* 每家客户每个应用 x 等级最多只能申请一台机器\n** 每批次开放时间与名额有限，请您与英特尔客户经理联系锁定意向\n*** 锁定报名意向后，英特尔将向您发送线上报名链接，届时正式启动项目参与\n**** 流程中的天数为自然天天数" + }, + { + "type": "page_number", + "text": "67" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_04.json b/diagrams-and-tables/annotations/cn_diagram_04.json new file mode 100644 index 0000000000000000000000000000000000000000..65741d5e93830ebbb204c01c709c8329832ea563 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_04.json @@ -0,0 +1,89 @@ +[ + { + "type": "title", + "text": "4.3.5 养老信托" + }, + { + "type": "text", + "text": "在信托行业回归本源的监管导向和社会养老需求增加的背景下，资产服务信托和公益慈善信托是目前养老信托的主要布局方向。\n养老信托不同于其他以获取投资收益为主要目标的金融产品，是指委托人（个人、家庭或法人）以养老资金管理、养老生活保障或养老慈善事业为核心目的，将财产委托给受托人（信托公司），信托公司根据合同约定向受益人（通常为委托人本人、家庭成员、公司员工、符合慈善信托标准的群体或组织等）提供财产保值增值、定期分配、养老规划及养老资源对接等信托业务安排。" + }, + { + "type": "diagram_caption", + "text": "图表4-36 信托基本结构示意图" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "受托人" + }, + { + "id": "B", + "text": "委托人" + }, + { + "id": "C", + "text": "信托" + }, + { + "id": "D", + "text": "受益人" + }, + { + "id": "E", + "text": "财产保管" + }, + { + "id": "F", + "text": "资产配置" + }, + { + "id": "G", + "text": "运作服务" + }, + { + "id": "H", + "text": "......" + } + ], + "relationships": [ + { + "source": "A", + "target": "C" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "C", + "target": "F" + }, + { + "source": "C", + "target": "G" + }, + { + "source": "C", + "target": "H" + } + ] + }, + { + "type": "text", + "text": "● 发挥制度优势，“金融+非金融”服务属性凸显\n根据法律规定，信托财产独立保管、运作，且与委托人其他财产相隔离，能够有效保障信托财产的安全。\n信托能够横跨货币、资本、商品等多元市场投资，可构建广泛、动态、灵活的投资组合。\n信托灵活的架构下，委托人能够根据个性化养老需求，灵活设置信托财产的分配机制，有效应对多元化养老场景要求。\n● 业务模式多元，满足不同客群差异化养老需求\n资产服务信托模式：定制化的综合养老金融服务方案\n资产服务信托项下的财富管理服务信托成为信托赋能养老事业发展的主要载体，信托计划的委托人主要分为自然人或家庭/家族成员、法人或非法人组织两类。其中自然人或家庭/家族成员主要通过家族信托、家庭服务信托和保险金信托来实现养老目的；法人则主要通过法人及非法人组织财富管理信托，以达到为员工提供补充养老、补充医疗资金、关爱特定困难员工等福利的效果。" + }, + { + "type": "page", + "page": 55 + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_05.json b/diagrams-and-tables/annotations/cn_diagram_05.json new file mode 100644 index 0000000000000000000000000000000000000000..12423468dee738c44d89be6b315cdc07670077e7 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_05.json @@ -0,0 +1,109 @@ +[ + { + "type": "title", + "text": "家族信托：为高净值人群提供一站式综合养老保障" + }, + { + "type": "text", + "text": "● 家族信托以1000万元设立门槛，通过跨代际资产配置与定制化条款设计，覆盖养老、医疗、传承等多元场景。\n● 委托人将财产委托信托公司，设定受益人及分配规则（如定期领取养老金、医疗专项支付），依托受托人投研能力实现资产增值，并进行家族成员日常养老支出、高端康养服务采购及财富传承安排。\n● 受托人发挥资源整合优势，对接优质养老机构居住权益等非金融增值服务，形成“财富管理+养老服务”双轨闭环，系统性满足品质养老需求。" + }, + { + "type": "diagram_caption", + "text": "图表4-37 养老主题家族信托架构示意" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "委托人" + }, + { + "id": "B", + "text": "受托人" + }, + { + "id": "C", + "text": "养老服务咨询机构" + }, + { + "id": "D", + "text": "养老主题家族信托" + }, + { + "id": "E", + "text": "资产管理产品" + }, + { + "id": "F", + "text": "投资顾问（或有）" + }, + { + "id": "G", + "text": "受益人" + } + ], + "relationships": [ + { + "source": "A", + "target": "B", + "label": "签订信托合同" + }, + { + "source": "A", + "target": "D", + "label": "财产委托" + }, + { + "source": "B", + "target": "D", + "label": "管理信托财产" + }, + { + "source": "C", + "target": "D", + "label": "付费（或有）" + }, + { + "source": "C", + "target": "G", + "label": "付费 提供养老服务" + }, + { + "source": "D", + "target": "E", + "label": "获取收益" + }, + { + "source": "D", + "target": "F", + "label": "投资指令" + }, + { + "source": "D", + "target": "G", + "label": "信托利益分配" + } + ] + }, + { + "type": "title", + "text": "家庭服务信托：综合财富管理服务的普惠化实践" + }, + { + "type": "text", + "text": "● 家庭服务信托是信托三分类新规后的创新型业务，也是家族信托模式的“普惠型”实践，设立门槛为100万元，相较家族信托大幅降低，让更多大众富裕家庭有机会运用信托工具实现家庭财富保护和养老规划等多样化目的。\n● 家庭服务信托与家族信托的业务架构较为相似，但明确了不低于5年的信托期限和标准化的配置范围，提供更符合大众家庭的资产配置服务。" + }, + { + "type": "title", + "text": "保险金信托：融合保险保障与养老规划双重优势" + }, + { + "type": "text", + "text": "● 保险金信托是指信托公司接受单一自然人委托，或者接受单一自然人及其家庭成员共同委托，以人身保险合同的相关权利和对应利益以及后续支付保费所需资金作为信托财产设立信托。\n● 当保险合同约定的给付条件发生时，保险公司按照保险约定将对应资金划付至对应信托专户，由信托公司按照信托文件管理。" + }, + { + "type": "page", + "page": 56 + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_06.json b/diagrams-and-tables/annotations/cn_diagram_06.json new file mode 100644 index 0000000000000000000000000000000000000000..498883a3635363d1cf66985c64877dce1cb0ad76 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_06.json @@ -0,0 +1,150 @@ +[ + { + "type": "title", + "text": "法人及非法人组织财富管理信托：企业为员工提供补充养老福利的重要途径" + }, + { + "type": "text", + "text": "● 法人及非法人组织财富管理信托以1000万元为设立门槛，能够借助信托的功能实现多元目的。其中，以薪酬福利管理为信托目的、公司员工作为受益人的信托架构，能够为员工提供补充养老资金等各类福利。" + }, + { + "type": "diagram_caption", + "text": "图表4-38 养老主题法人及非法人组织财富管理信托部分框架" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "委托人（企业）" + }, + { + "id": "B", + "text": "受托人" + }, + { + "id": "C", + "text": "企业补充养老信托" + }, + { + "id": "D", + "text": "资产管理产品" + }, + { + "id": "E", + "text": "受益人员工1" + }, + { + "id": "F", + "text": "受益人员工2" + }, + { + "id": "G", + "text": "受益人员工3" + }, + { + "id": "H", + "text": "......" + } + ], + "relationships": [ + { + "source": "A", + "label": "签订信托合同" + }, + { + "source": "A", + "target": "C", + "label": "财产 委托" + }, + { + "source": "B", + "target": "C", + "label": "管理信托财产" + }, + { + "source": "C", + "target": "D", + "label": "获取收益" + }, + { + "source": "C", + "target": "E", + "label": "信托利益分配" + }, + { + "source": "C", + "target": "F", + "label": "信托利益分配" + }, + { + "source": "C", + "target": "G", + "label": "信托利益分配" + }, + { + "source": "C", + "target": "H", + "label": "信托利益分配" + } + ] + }, + { + "type": "text", + "text": "● 此外，委托人还可借助该信托架构实现员工股权激励、薪酬递延支付等效果。同时，也可以通过其他行政服务管理信托的模式，实现对特定困难员工的关怀，包括对其养老生活的额外支持。" + }, + { + "type": "title", + "text": "● 公益慈善信托模式：助力养老公益事业“向上向善”" + }, + { + "type": "text", + "text": "● 在政策引导和社会需求下，养老慈善信托已经成为推动养老慈善事业发展的有力工具，数量持续扩容。在2024年全年新设的慈善信托中，信托目的涵盖扶老助老的慈善信托共155单，占比28.8%。履行了金融服务实体经济和社会民生的天职，实现了金融服务与社会公益的双赢。\n● 养老慈善信托通过信托架构，一方面帮助企业和高净值人群灵活、高效、可持续地管理慈善财产、实现慈善意愿；另一方面通过支持社会养老福利事业、资助养老慈善项目，使得广大老年群体、尤其是处于困境中的老年群体受益，是多层次养老保障体系的重要组成部分。\n● 养老慈善信托支持的慈善项目范畴广泛，包括：机构及社区养老设施及服务建设、特困老人救助、老年健康关怀、老年文化活动、养老慈善行业发展及人才培训等多个维度，以多元化的方式助力养老事业发展。" + }, + { + "type": "diagram_caption", + "text": "图表4-39 养老慈善信托架构示意" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "委托人" + }, + { + "id": "B", + "text": "养老慈善信托" + }, + { + "id": "C", + "text": "养老相关慈善组织" + }, + { + "id": "D", + "text": "老年群体" + } + ], + "relationships": [ + { + "source": "A", + "target": "B", + "label": "委托设立" + }, + { + "source": "B", + "target": "C", + "label": "委托执行" + }, + { + "source": "C", + "target": "D", + "label": "开展慈善活动" + } + ] + }, + { + "type": "page", + "page": 57 + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_07.json b/diagrams-and-tables/annotations/cn_diagram_07.json new file mode 100644 index 0000000000000000000000000000000000000000..00cc5f8e41fcb36fe327b620fa2d55e43749b1e5 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_07.json @@ -0,0 +1,109 @@ +[ + { + "type": "title", + "text": "第一章 AI PC 的历史使命：\nAI 普惠首选终端" + }, + { + "type": "text", + "text": "人工智能的需求正在爆发，大模型开启了普惠于人的路程。用户不仅需要公共的大模型服务，更需要的是专属自己的个人大模型。个人大模型将依托混合人工智能的方式，逐步实现普惠。我们看到，个人大模型的普惠要求和 PC 的承载优势完美契合，显示着 PC 将再一次承载技术普惠的历史使命，成为 AI 普惠的首选终端。" + }, + { + "type": "diagram_caption", + "text": "图 1 PC 与 AI 大模型的天然匹配" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "能进行多模态自然语言交互" + }, + { + "id": "B", + "text": "压缩后依然具备通用场景服务能力" + }, + { + "id": "C", + "text": "需要强 AI 算力进行推理" + }, + { + "id": "D", + "text": "需要基于个人数据和隐私信息进行微调和个性化服务" + }, + { + "id": "E", + "text": "个人大模型" + }, + { + "id": "F", + "text": "PC" + }, + { + "id": "G", + "text": "具备全模态人机自然交互条件" + }, + { + "id": "H", + "text": "承载最多场景的个人通用设备" + }, + { + "id": "I", + "text": "最强的个人计算平台" + }, + { + "id": "J", + "text": "存储容量最大、最受信赖的安全终端" + } + ], + "relationships": [ + { + "source": "A", + "target": "E" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "F", + "target": "H" + }, + { + "source": "F", + "target": "I" + }, + { + "source": "F", + "target": "J" + } + ] + }, + { + "type": "text", + "text": "来源: IDC, 2023" + }, + { + "type": "footer", + "text": "IDC | Lenovo 联想" + }, + { + "type": "page_number", + "text": "4" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_08.json b/diagrams-and-tables/annotations/cn_diagram_08.json new file mode 100644 index 0000000000000000000000000000000000000000..02e0cdd5c1d604fc8b17b8700a53de5c74ea7463 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_08.json @@ -0,0 +1,118 @@ +[ + { + "type": "header", + "text": "AI PC 产业 (中国) 白皮书" + }, + { + "type": "diagram_caption", + "text": "图 5 个人智能体提升 AI PC 的自主性与易用性" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "用户图标" + }, + { + "id": "B", + "text": "自然语言交互 UI" + }, + { + "id": "C", + "text": "意图理解 & 多任务分发平台 (基于个人本地大模型)" + }, + { + "id": "D", + "text": "个性化本地知识库" + }, + { + "id": "E", + "text": "个人智能体" + }, + { + "id": "F", + "text": "本地模型" + }, + { + "id": "G", + "text": "云端模型" + }, + { + "id": "H", + "text": "应用" + }, + { + "id": "I", + "text": "设备" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "C", + "target": "D", + "label": "查询知识库\n反馈新的 prompt" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "E", + "target": "F", + "label": "模型调用\n反馈结果" + }, + { + "source": "E", + "target": "G", + "label": "模型调用\n反馈结果" + }, + { + "source": "E", + "target": "H", + "label": "应用 API 调用\n反馈结果" + }, + { + "source": "E", + "target": "I", + "label": "操作设备功能\n返回操作结果" + } + ] + }, + { + "type": "text", + "text": "来源: IDC, 2023" + }, + { + "type": "title", + "text": "终端内嵌个人大模型" + }, + { + "type": "title", + "text": "本地为主，边缘与云为辅的大模型方案" + }, + { + "type": "text", + "text": "随着用户对 AI 能力和大模型的调用变得像使用办公软件一样频繁，仅依赖云端提供相应的能力就变得昂贵、复杂且不够安全。因此，以模型的本地化推理为主，以边缘和云端推理为辅的混合大模型架构成为 AI PC 解决这一问题的关键。\n\n用户的大部分任务将能够依托 AI PC 本地模型完成。例如，用户能够在离线的情况下依靠本地大模型完成通过文字描述生成文档和 PPT 的任务。同时，本地模型还将承担意图理解和任务分配的功能，是个人智能体的底座。" + }, + { + "type": "footer", + "text": "IDC | Lenovo 联想" + }, + { + "type": "page_number", + "text": "17" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_09.json b/diagrams-and-tables/annotations/cn_diagram_09.json new file mode 100644 index 0000000000000000000000000000000000000000..c688d9ac55602c253bf18229caab6e49fda5aed0 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_09.json @@ -0,0 +1,190 @@ +[ + { + "type": "title", + "text": "第三章 AI PC 的产业生态：\n以人为本、终端主导、AI 原生" + }, + { + "type": "text", + "text": "在 AI PC 的推动下，PC 产业生态将从应用为本转向以人为本，从应用驱动转变为意图驱动。传统 PC 产业生态以操作系统为基础，用户在系统界面中直接进行操作，并管理和应用各式各样的应用程序。AI PC 产业生态中，个人智能体将成为第一入口，在大模型与应用生态的支持下，准确理解用户指令，给出恰当的反馈，跨应用进行调度，进而完成相对复杂的任务。模型、应用、算力厂商都需要围绕 AI PC（终端）形态下新的以人为本的需求做出改变，在研发工作中对 AI 的高效运行予以充分的考量，以适应 AI PC 新时代。" + }, + { + "type": "diagram_caption", + "text": "图 7 PC 产业生态变革图" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "传统 PC 产业生态" + }, + { + "id": "B", + "text": "用户" + }, + { + "id": "C", + "text": "应用" + }, + { + "id": "D", + "text": "功能" + }, + { + "id": "E", + "text": "数据" + }, + { + "id": "F", + "text": "操作系统" + }, + { + "id": "G", + "text": "通用计算 / 芯片" + }, + { + "id": "H", + "text": "AI PC 产业生态" + }, + { + "id": "I", + "text": "用户" + }, + { + "id": "J", + "text": "个人智能体" + }, + { + "id": "K", + "text": "应用" + }, + { + "id": "L", + "text": "模型" + }, + { + "id": "M", + "text": "混合算力 / 芯片" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "A", + "target": "G" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "F" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "C", + "target": "F" + }, + { + "source": "D", + "target": "G" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "E", + "target": "G" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "H", + "target": "I" + }, + { + "source": "H", + "target": "J" + }, + { + "source": "H", + "target": "K" + }, + { + "source": "H", + "target": "L" + }, + { + "source": "H", + "target": "M" + }, + { + "source": "I", + "target": "J" + }, + { + "source": "J", + "target": "K" + }, + { + "source": "J", + "target": "L" + }, + { + "source": "K", + "target": "M" + }, + { + "source": "L", + "target": "M" + }, + { + "source": "A", + "target": "H", + "label": "变革" + } + ] + }, + { + "type": "text", + "text": "来源: IDC, 2023" + }, + { + "type": "footer", + "text": "IDC | Lenovo 联想" + }, + { + "type": "page_number", + "text": "23" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_10.json b/diagrams-and-tables/annotations/cn_diagram_10.json new file mode 100644 index 0000000000000000000000000000000000000000..7c9f5166569b065e779597e7e4ff011ea38b5ceb --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_10.json @@ -0,0 +1,177 @@ +[ + { + "type": "text", + "text": "随着 AI 技术的不断进步，越来越多的企业加入 AI PC 的开放生态，形成用户、终端厂商、模型、应用、算力多层开放的繁荣生态。用户视野将发生变化，模型与应用的新关系将改变用户需求的底层逻辑。用户的需求是推动整个生态发展的关键要素，而终端厂商以场景需求为基础面向用户整合产业资源，提供软硬件一体的混合交付体验。模型厂商、芯片厂商也将与终端厂商产生更加紧密地联结。" + }, + { + "type": "diagram_caption", + "text": "图 8 产业内供给关系变化" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "现在" + }, + { + "id": "B", + "text": "用户" + }, + { + "id": "C", + "text": "应用" + }, + { + "id": "D", + "text": "终端厂商" + }, + { + "id": "E", + "text": "模型" + }, + { + "id": "F", + "text": "芯片" + }, + { + "id": "G", + "text": "未来" + }, + { + "id": "H", + "text": "用户" + }, + { + "id": "I", + "text": "应用 / 插件" + }, + { + "id": "J", + "text": "终端厂商" + }, + { + "id": "K", + "text": "大模型" + }, + { + "id": "L", + "text": "芯片" + }, + { + "id": "M", + "text": "具备 AI 环境" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "D", + "target": "F" + }, + { + "source": "A", + "target": "G" + }, + { + "source": "G", + "target": "H" + }, + { + "source": "G", + "target": "I" + }, + { + "source": "G", + "target": "J" + }, + { + "source": "G", + "target": "K" + }, + { + "source": "G", + "target": "L" + }, + { + "source": "H", + "target": "J" + }, + { + "source": "I", + "target": "J" + }, + { + "source": "I", + "target": "K" + }, + { + "source": "J", + "target": "K" + }, + { + "source": "J", + "target": "L" + } + ] + }, + { + "type": "text", + "text": "来源: IDC, 2023" + }, + { + "type": "title", + "text": "3.1 用户：生态话语权显著提升" + }, + { + "type": "title", + "text": "用户成为行业生态创新的驱动者和创造者" + }, + { + "type": "text", + "text": "PC 行业的前几次产业变革主要由终端、OS 或是芯片厂商推动，用户被动接纳新的技术和产品，调整和适应自己的使用工具的习惯、提升使用工具的熟练度。" + }, + { + "type": "footer", + "text": "IDC | Lenovo 联想" + }, + { + "type": "page_number", + "text": "24" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_11.json b/diagrams-and-tables/annotations/cn_diagram_11.json new file mode 100644 index 0000000000000000000000000000000000000000..6fcfd7a36c398bdc9e51987284528e897f13f84a --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_11.json @@ -0,0 +1,361 @@ +[ + { + "type": "header", + "text": "工业设备网联化技术与实践白皮书\n工业设备网联化现状及趋势" + }, + { + "type": "text", + "text": "不确定性的随机网络，难以胜任高速实时性数据通信。为此，世界上的各大公司纷纷开发出自己的实时工业以太网，例如：PROFINET、EtherCAT等。而TSN(Time Sensitive Network)-时间敏感型网络的出现，解决了用单一网络连接不同工业以太协议的问题，并与OPC-UA结合实现了IT与OT的融合通信。" + }, + { + "type": "diagram_caption", + "text": "图2-3 大部分工业实时以太协议舍弃TCP/IP层" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "L2标准以太+标准IP" + }, + { + "id": "B", + "text": "Category A" + }, + { + "id": "C", + "text": "IT / RT Services " + }, + { + "id": "D", + "text": "TCP/UDP" + }, + { + "id": "E", + "text": "IP" + }, + { + "id": "F", + "text": "Standard" + }, + { + "id": "G", + "text": "Standard Ethernet TCP/IP, EtherNet/IP, Modbus/TCP" + }, + { + "id": "H", + "text": "标准以太+标准IP/定制协议" + }, + { + "id": "I", + "text": "Category B" + }, + { + "id": "J", + "text": "IT Services " + }, + { + "id": "K", + "text": "RT Services " + }, + { + "id": "L", + "text": "TCP/UDP" + }, + { + "id": "M", + "text": "Special Process Data Protocol" + }, + { + "id": "N", + "text": "IP" + }, + { + "id": "O", + "text": "Standard" + }, + { + "id": "P", + "text": "Powerlink, Sercos-III, Profinet v2" + }, + { + "id": "Q", + "text": "标准以太/定制硬件+标准IP/定制协议" + }, + { + "id": "R", + "text": "Category C" + }, + { + "id": "S", + "text": "IT Services" + }, + { + "id": "T", + "text": "RT Services" + }, + { + "id": "U", + "text": "TCP/UDP" + }, + { + "id": "V", + "text": "Special Process Data Protocol" + }, + { + "id": "W", + "text": "IP" + }, + { + "id": "X", + "text": "Special RT" + }, + { + "id": "Y", + "text": "EtherCAT, Profinet v3" + }, + { + "id": "Z", + "text": "支持 IEEE1588" + }, + { + "id": "AA", + "text": "物理相同" + }, + { + "id": "AB", + "text": "Ethernet/MAC" + }, + { + "id": "AC", + "text": "Ethernet/MAC" + }, + { + "id": "AD", + "text": "Ethernet/MAC" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "A", + "target": "G" + }, + { + "source": "A", + "target": "AB" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "F", + "target": "AB" + }, + { + "source": "H", + "target": "I" + }, + { + "source": "H", + "target": "J" + }, + { + "source": "H", + "target": "K" + }, + { + "source": "H", + "target": "L" + }, + { + "source": "H", + "target": "M" + }, + { + "source": "H", + "target": "N" + }, + { + "source": "H", + "target": "O" + }, + { + "source": "H", + "target": "P" + }, + { + "source": "H", + "target": "Z" + }, + { + "source": "H", + "target": "AC" + }, + { + "source": "J", + "target": "K" + }, + { + "source": "J", + "target": "L" + }, + { + "source": "K", + "target": "M" + }, + { + "source": "L", + "target": "N" + }, + { + "source": "L", + "target": "M" + }, + { + "source": "M", + "target": "N" + }, + { + "source": "M", + "target": "O" + }, + { + "source": "N", + "target": "O" + }, + { + "source": "O", + "target": "AC" + }, + { + "source": "Q", + "target": "R" + }, + { + "source": "Q", + "target": "S" + }, + { + "source": "Q", + "target": "T" + }, + { + "source": "Q", + "target": "U" + }, + { + "source": "Q", + "target": "V" + }, + { + "source": "Q", + "target": "W" + }, + { + "source": "Q", + "target": "X" + }, + { + "source": "Q", + "target": "Y" + }, + { + "source": "Q", + "target": "Z" + }, + { + "source": "Q", + "target": "AD" + }, + { + "source": "S", + "target": "U" + }, + { + "source": "S", + "target": "T" + }, + { + "source": "T", + "target": "V" + }, + { + "source": "U", + "target": "V" + }, + { + "source": "U", + "target": "W" + }, + { + "source": "V", + "target": "W" + }, + { + "source": "V", + "target": "X" + }, + { + "source": "W", + "target": "X" + }, + { + "source": "X", + "target": "AD" + }, + { + "source": "AA", + "target": "AB" + }, + { + "source": "AA", + "target": "AC" + }, + { + "source": "AA", + "target": "AD" + } + ] + }, + { + "type": "text", + "text": "广域IP化：大部分的工业以太在实时处理过程中舍弃了TCP/IP层，因此从本质上讲是工业以太总线。进入工业智能时代，工业互联网正在推动企业生产系统走向现场少人化、无人化，控制系统加速走向远程集中控制模式，让操作人员可以在更安全、更舒适的集中控制室完成生产任务，也让大型企业得以在更大范围内实现总部、多基地之间的生产要素调度和优化，为此，工业控制系统需要走向广域云化。工控系统的IP化是实现整个网络端到端统一语言都说“普通话”、IT与OT网络融合的基础。当然，要实现远程的云化实时控制，一张确定性的广域网络必不可少。" + }, + { + "type": "page_number", + "text": "05" + }, + { + "type": "footer", + "text": "打造先进工业网络 加速工业互联网创新发展" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_12.json b/diagrams-and-tables/annotations/cn_diagram_12.json new file mode 100644 index 0000000000000000000000000000000000000000..8a8578361ed826a6ee76d84d93659d2e7c5b2e34 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_12.json @@ -0,0 +1,261 @@ +[ + { + "type": "header", + "text": "HarmonyOS NEXT 安全技术白皮书" + }, + { + "type": "header", + "text": "2 HarmonyOS 概述" + }, + { + "type": "text", + "text": "分布式软总线是手机、智能穿戴、平板、智慧屏、车机等多种终端设备的统一基座，为设备之间的互联互通提供了统一的分布式通信能力，能够快速发现并连接设备，高效地分发任务和传输数据。" + }, + { + "type": "diagram_caption", + "text": "图2-1 分布式软总线示意图" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "终端设备" + }, + { + "id": "B", + "text": "设备A" + }, + { + "id": "C", + "text": "设备B" + }, + { + "id": "D", + "text": "设备C" + }, + { + "id": "E", + "text": "设备D" + }, + { + "id": "F", + "text": "......" + }, + { + "id": "G", + "text": "分布式软总线" + }, + { + "id": "H", + "text": "数据与计算中心" + }, + { + "id": "I", + "text": "决策中心" + }, + { + "id": "J", + "text": "总线中枢" + }, + { + "id": "K", + "text": "互联管理中心" + }, + { + "id": "L", + "text": "组网&拓扑管理" + }, + { + "id": "M", + "text": "发现" + }, + { + "id": "N", + "text": "连接" + }, + { + "id": "O", + "text": "任务&数据总线（消息、字节、文件、流）" + }, + { + "id": "P", + "text": "安全" + }, + { + "id": "Q", + "text": "设备Profile" + }, + { + "id": "R", + "text": "基础通信" + }, + { + "id": "S", + "text": "协议栈" + }, + { + "id": "T", + "text": "软硬协同" + }, + { + "id": "U", + "text": "WLAN" + }, + { + "id": "V", + "text": "Bluetooth" + }, + { + "id": "W", + "text": "BLE" + }, + { + "id": "X", + "text": "NFC" + }, + { + "id": "Y", + "text": "红外" + }, + { + "id": "Z", + "text": "USB" + }, + { + "id": "AA", + "text": "Ethernet" + }, + { + "id": "AB", + "text": "Modem (2/3/4/5G)" + }, + { + "id": "AC", + "text": "......" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "G", + "target": "J" + }, + { + "source": "G", + "target": "O" + }, + { + "source": "G", + "target": "P" + }, + { + "source": "G", + "target": "Q" + }, + { + "source": "H", + "target": "J" + }, + { + "source": "I", + "target": "J" + }, + { + "source": "J", + "target": "K" + }, + { + "source": "K", + "target": "L" + }, + { + "source": "K", + "target": "M" + }, + { + "source": "K", + "target": "N" + }, + { + "source": "R", + "target": "S" + }, + { + "source": "R", + "target": "T" + }, + { + "source": "R", + "target": "U" + }, + { + "source": "R", + "target": "V" + }, + { + "source": "R", + "target": "W" + }, + { + "source": "R", + "target": "X" + }, + { + "source": "R", + "target": "Y" + }, + { + "source": "R", + "target": "Z" + }, + { + "source": "R", + "target": "AA" + }, + { + "source": "R", + "target": "AB" + }, + { + "source": "R", + "target": "AC" + } + ] + }, + { + "type": "title", + "text": "分布式设备虚拟化" + }, + { + "type": "text", + "text": "分布式设备虚拟化平台可以实现不同设备的资源融合、设备管理、数据处理，多种设备共同形成一个超级虚拟终端。针对不同类型的任务，为用户匹配并选择能力合适的执行硬件，让业务连续地在不同设备间流转，充分发挥不同设备的资源优势。" + }, + { + "type": "footer", + "text": "文档版本 V1.0 (2024-08-13) 版权所有 © 华为技术有限公司" + }, + { + "type": "page_number", + "text": "5" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_13.json b/diagrams-and-tables/annotations/cn_diagram_13.json new file mode 100644 index 0000000000000000000000000000000000000000..d462e6744759d2cbe99a4a02e31225861268118f --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_13.json @@ -0,0 +1,318 @@ +[ + { + "type": "header", + "text": "HarmonyOS NEXT 安全技术白皮书 2 HarmonyOS 概述" + }, + { + "type": "diagram_caption", + "text": "图2-2 分布式设备虚拟化示意图" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "设备A" + }, + { + "id": "B", + "text": "直播类应用" + }, + { + "id": "C", + "text": "通话类应用" + }, + { + "id": "D", + "text": "健身类应用" + }, + { + "id": "E", + "text": "多设备虚拟化Kit" + }, + { + "id": "F", + "text": "多设备虚拟化平台" + }, + { + "id": "G", + "text": "设备管理与安全" + }, + { + "id": "H", + "text": "数据处理与增强" + }, + { + "id": "I", + "text": "设备虚拟与接入" + }, + { + "id": "J", + "text": "OS" + }, + { + "id": "K", + "text": "设备B" + }, + { + "id": "L", + "text": "智慧屏、智能穿戴、车机等设备" + }, + { + "id": "M", + "text": "多设备虚拟化SDK" + }, + { + "id": "N", + "text": "设备管理" + }, + { + "id": "O", + "text": "设备虚拟化" + }, + { + "id": "P", + "text": "数据处理" + }, + { + "id": "Q", + "text": "OS适配" + }, + { + "id": "R", + "text": "OS" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "F", + "target": "H" + }, + { + "source": "F", + "target": "I" + }, + { + "source": "A", + "target": "J" + }, + { + "source": "A", + "target": "K" + }, + { + "source": "K", + "target": "L" + }, + { + "source": "K", + "target": "M" + }, + { + "source": "M", + "target": "N" + }, + { + "source": "M", + "target": "O" + }, + { + "source": "M", + "target": "P" + }, + { + "source": "M", + "target": "Q" + }, + { + "source": "K", + "target": "R" + } + ] + }, + { + "type": "title", + "text": "分布式数据管理" + }, + { + "type": "text", + "text": "分布式数据管理基于分布式软总线的能力，实现应用程序数据和用户数据的分布式管理。用户数据不再与单一物理设备绑定，业务逻辑与数据存储分离，应用跨设备运行时数据无缝衔接，为打造一致、流畅的用户体验创造了基础条件。" + }, + { + "type": "diagram_caption", + "text": "图2-3 分布式数据管理示意图" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "设备A：应用程序数据&用户数据" + }, + { + "id": "B", + "text": "设备/用户/应用Profile" + }, + { + "id": "C", + "text": "状态事件/位置" + }, + { + "id": "D", + "text": "文本数据" + }, + { + "id": "E", + "text": "媒体数据" + }, + { + "id": "F", + "text": "......" + }, + { + "id": "G", + "text": "设备B：应用程序数据&用户数据" + }, + { + "id": "H", + "text": "设备/用户/应用Profile" + }, + { + "id": "I", + "text": "状态事件/位置" + }, + { + "id": "J", + "text": "文本数据" + }, + { + "id": "K", + "text": "超级虚拟终端：应用程序数据&用户数据" + }, + { + "id": "L", + "text": "设备/用户/应用Profile" + }, + { + "id": "M", + "text": "状态事件/位置" + }, + { + "id": "N", + "text": "文本数据" + }, + { + "id": "O", + "text": "媒体数据" + }, + { + "id": "P", + "text": "......" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "A", + "target": "K", + "label": "数据同步管理" + }, + { + "source": "G", + "target": "H" + }, + { + "source": "G", + "target": "I" + }, + { + "source": "G", + "target": "J" + }, + { + "source": "G", + "target": "K", + "label": "数据同步管理" + }, + { + "source": "K", + "target": "L" + }, + { + "source": "K", + "target": "M" + }, + { + "source": "K", + "target": "N" + }, + { + "source": "K", + "target": "O" + }, + { + "source": "K", + "target": "P" + } + ] + }, + { + "type": "title", + "text": "分布式任务调度" + }, + { + "type": "text", + "text": "分布式任务调度基于分布式软总线、分布式数据管理等技术特性，构建统一的分布式服务管理（发现、同步、注册、调用）机制，支持对跨设备的应用进行远程启动、远程调用、远程连接以及迁移等操作，能够根据不同设备的能力、位置、业务运行状态、资源使用情况，以及用户的习惯和意图，选择合适的设备运行分布式任务。" + }, + { + "type": "footer", + "text": "文档版本 V1.0 (2024-08-13) 版权所有 © 华为技术有限公司" + }, + { + "type": "page_number", + "text": "6" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_14.json b/diagrams-and-tables/annotations/cn_diagram_14.json new file mode 100644 index 0000000000000000000000000000000000000000..4c9f6f2f4e1d32d1201725ca1cc261aef00b1369 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_14.json @@ -0,0 +1,165 @@ +[ + { + "type": "header", + "text": "HarmonyOS NEXT 安全技术白皮书 5 HarmonyOS “正确的设备”系统安全架构" + }, + { + "type": "diagram_caption", + "text": "图5-1 HarmonyOS 系统安全架构" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "云服务、应用市场" + }, + { + "id": "B", + "text": "上架检测、代码唯一分发途径（签名）、OTA升级、设备查找、华为账号等" + }, + { + "id": "C", + "text": "底座安全机制" + }, + { + "id": "D", + "text": "加密和数据保护：文件加密、密钥管理" + }, + { + "id": "E", + "text": "完整性保护：安全启动链、启动链加固、代码强制签名、XPM、JIT Fort" + }, + { + "id": "F", + "text": "隔离和访问控制：AccessTOKEN、SE-Harmony、SECCOMP、应用沙盒等" + }, + { + "id": "G", + "text": "漏洞防利用：PAN/PXN、PAC CFI、PAC DFI、HKIP、XOM、uPPL、坚盾守护模式等" + }, + { + "id": "H", + "text": "HarmonyOS内核&系统框架" + }, + { + "id": "I", + "text": "芯片" + }, + { + "id": "J", + "text": "计算可信根" + }, + { + "id": "K", + "text": "内存安全：PAC保护" + }, + { + "id": "L", + "text": "安全隔离：SE、Trustzone" + }, + { + "id": "M", + "text": "启动可信根" + }, + { + "id": "N", + "text": "安全启动：一机一授权" + }, + { + "id": "O", + "text": "启动链：PAC CFI、DICE启动" + }, + { + "id": "P", + "text": "存储可信根" + }, + { + "id": "Q", + "text": "数据加密：inline加密引擎、硬件加密引擎等" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "C", + "target": "F" + }, + { + "source": "C", + "target": "G" + }, + { + "source": "C", + "target": "H" + }, + { + "source": "I", + "target": "J" + }, + { + "source": "J", + "target": "K" + }, + { + "source": "J", + "target": "L" + }, + { + "source": "I", + "target": "M" + }, + { + "source": "M", + "target": "N" + }, + { + "source": "M", + "target": "O" + }, + { + "source": "I", + "target": "P" + }, + { + "source": "P", + "target": "Q" + } + ] + }, + { + "type": "text", + "text": "遵循可信计算理论，HarmonyOS 的安全设计整体根植于信任根，根据不同的保护对象和资产选择合适的信任根，如芯片、服务器等。" + }, + { + "type": "title", + "text": "完整性保护" + }, + { + "type": "text", + "text": "是系统安全的根基，确保系统软件和应用程序全生命周期的完整合法，未被非法篡改，是支撑安全策略正确实施的前提。" + }, + { + "type": "title", + "text": "隔离及访问控制" + }, + { + "type": "footer", + "text": "文档版本 V1.0 (2024-08-13) 版权所有 © 华为技术有限公司" + }, + { + "type": "page_number", + "text": "23" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_15.json b/diagrams-and-tables/annotations/cn_diagram_15.json new file mode 100644 index 0000000000000000000000000000000000000000..393d878c09c0f41329fa5b508cc3691fa58c56a0 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_15.json @@ -0,0 +1,101 @@ +[ + { + "type": "header", + "text": "HarmonyOS NEXT 安全技术白皮书 6 HarmonyOS “正确的访问数据” 分级访问控制架构" + }, + { + "type": "diagram_caption", + "text": "发送方生成的加密数据格式" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "加密数据格式" + }, + { + "id": "B", + "text": "数据密文（数据加密密钥加密）" + }, + { + "id": "C", + "text": "数据明文" + }, + { + "id": "D", + "text": "数据权限文件密文（数据所有者私钥签名，接收方公钥加密）" + }, + { + "id": "E", + "text": "数据加密密钥（AES-GCM密钥）" + }, + { + "id": "F", + "text": "数据访问控制信息" + }, + { + "id": "G", + "text": "数据执行权限（是否允许打印、截屏等）" + }, + { + "id": "H", + "text": "授权访问用户信息（可访问该文件的账号信息）" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "D", + "target": "F" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "F", + "target": "H" + } + ] + }, + { + "type": "text", + "text": "数据的接收方如果想要访问数据明文，必须先获取数据加密密钥（AES-GCM 密钥）。根据当前的加密数据格式，数据加密密钥作为数据权限文件的一部分，被数据所有者指定的接收方数据保护凭据公钥加密。授权用户设备上的系统数据加密分享服务，会使用本地管理的数据保护凭据私钥进行解密，并验证数据权限文件的完整性（使用数据所有者的数据保护凭据公钥验签）；解密后会获得数据执行权限和数据加密密钥，后者会进一步用于解密数据密文获得明文数据。" + }, + { + "type": "text", + "text": "系统数据加密分享服务定义了绑定访问控制策略的加密数据格式，保证了用户对数据设置的访问控制权限不可剥离、不可篡改；任意非授权的用户都无法解密数据权限文件。" + }, + { + "type": "title", + "text": "基于动态沙箱的数据权限管控" + }, + { + "type": "text", + "text": "为实现数据在接收方的延伸控制，用户选定应用访问数据时，系统数据加密分享服务会将数据执行权限为 HarmonyOS 上的应用权限，并安装对应权限的应用沙箱；该沙箱对于底层系统服务（包括文件系统、以及屏幕控制、打印服务等）的访问控制权限，全部由系统数据加密分享服务定义。当该应用沙箱访问数据时，对底层系统服务的访问行为均受到系统控制，从而保证发送方设置的数据执行权限在接收方得到管控。" + }, + { + "type": "footer", + "text": "文档版本 V1.0 (2024-08-13) 版权所有 © 华为技术有限公司" + }, + { + "type": "page_number", + "text": "42" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_16.json b/diagrams-and-tables/annotations/cn_diagram_16.json new file mode 100644 index 0000000000000000000000000000000000000000..abe496ea594eb296ac3441ed5345b4c2957c795c --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_16.json @@ -0,0 +1,301 @@ +[ + { + "type": "header", + "text": "HarmonyOS NEXT 安全技术白皮书 7 HarmonyOS 应用生态治理架构" + }, + { + "type": "diagram_caption", + "text": "图7-2 HarmonyOS 应用程序生命周期关键技术和措施" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "开发阶段（开发工具）" + }, + { + "id": "B", + "text": "开发" + }, + { + "id": "C", + "text": "开发者实名认证" + }, + { + "id": "D", + "text": "安全编码编译" + }, + { + "id": "E", + "text": "安全调试模式" + }, + { + "id": "F", + "text": "代码混淆" + }, + { + "id": "G", + "text": "安全检测" + }, + { + "id": "H", + "text": "上架" + }, + { + "id": "I", + "text": "发布profile申请" + }, + { + "id": "J", + "text": "开发者证书签名" + }, + { + "id": "K", + "text": "发布阶段（应用市场）" + }, + { + "id": "L", + "text": "审核和检测" + }, + { + "id": "M", + "text": "开发者、应用合法性" + }, + { + "id": "N", + "text": "安全隐私漏洞检测" + }, + { + "id": "O", + "text": "应用行为检测" + }, + { + "id": "P", + "text": "发布" + }, + { + "id": "Q", + "text": "应用加密" + }, + { + "id": "R", + "text": "代码签名" + }, + { + "id": "S", + "text": "下架" + }, + { + "id": "T", + "text": "违规应用下架" + }, + { + "id": "U", + "text": "吊销开发者证书" + }, + { + "id": "V", + "text": "运行阶段（操作系统）" + }, + { + "id": "W", + "text": "安装" + }, + { + "id": "X", + "text": "来源管控" + }, + { + "id": "Y", + "text": "企业应用" + }, + { + "id": "Z", + "text": "运行" + }, + { + "id": "AA", + "text": "应用沙箱隔离" + }, + { + "id": "AB", + "text": "隐私权限保护" + }, + { + "id": "AC", + "text": "安全控件/picker" + }, + { + "id": "AD", + "text": "应用风险行为管控" + }, + { + "id": "AE", + "text": "更新" + }, + { + "id": "AF", + "text": "禁止未经检测的热更新" + } + ], + "relationships": [ + { + "source": "A", + "target": "K" + }, + { + "source": "K", + "target": "V" + }, + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "B", + "target": "F" + }, + { + "source": "B", + "target": "G" + }, + { + "source": "A", + "target": "H" + }, + { + "source": "H", + "target": "I" + }, + { + "source": "H", + "target": "J" + }, + { + "source": "K", + "target": "L" + }, + { + "source": "L", + "target": "M" + }, + { + "source": "L", + "target": "N" + }, + { + "source": "L", + "target": "O" + }, + { + "source": "K", + "target": "P" + }, + { + "source": "P", + "target": "Q" + }, + { + "source": "P", + "target": "R" + }, + { + "source": "K", + "target": "S" + }, + { + "source": "S", + "target": "T" + }, + { + "source": "S", + "target": "U" + }, + { + "source": "V", + "target": "W" + }, + { + "source": "W", + "target": "X" + }, + { + "source": "W", + "target": "Y" + }, + { + "source": "V", + "target": "Z" + }, + { + "source": "Z", + "target": "AA" + }, + { + "source": "Z", + "target": "AB" + }, + { + "source": "Z", + "target": "AC" + }, + { + "source": "Z", + "target": "AD" + }, + { + "source": "V", + "target": "AE" + }, + { + "source": "AE", + "target": "AF" + } + ] + }, + { + "type": "text", + "text": "如图 7-2 所示，我们在应用全生命周期的不同阶段，分别提供不同的关键技术和措施，来解决生态构建的重大挑战问题。" + }, + { + "type": "title", + "text": "7.2 HarmonyOS 应用程序 “纯净” 开发" + }, + { + "type": "text", + "text": "对于 HarmonyOS 开发者，提供开发者注册、账号管理、实名认证，并进行开发者证书管理，开发者的应用开发以及调测提供配套管理能力。" + }, + { + "type": "text", + "text": "开发工具提供安全能力，帮助开发者进行代码级以及二进制相关的安全与隐私检查，确保开发者能够快速开发出高质量 HarmonyOS 程序。" + }, + { + "type": "text", + "text": "同时，DevEco Studio 为开发者提供应用来源管控和完整性保护的安全能力，例如：DevEco Studio 能够自动化帮助开发者进行秘钥的生成和管理，自动化的签名管理、自动化的调试证书管理和自动化的调测设备管理，方便开发者开发的应用或服务能够快速上架。" + }, + { + "type": "text", + "text": "实名认证要求：依据国家互联网信息办公室 2016 年 6 月 28 日发布的《移动互联网应用程序信息服务管理规定》，同时为了促进生态健康有序发展，保护开发者、用户的合法权益，申请成为一个 HarmonyOS 开发者需要注册账号，注册账号时可以同步进行实名认证，实名认证包括个人开发者实名认证和企业开发者实名认证；确保应用的开发者是可以被追溯的。在应用上架发布环节仍需要实名认证，建议注册时立即实名认证。" + }, + { + "type": "footer", + "text": "文档版本 V1.0 (2024-08-13) 版权所有 © 华为技术有限公司" + }, + { + "type": "page_number", + "text": "45" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_17.json b/diagrams-and-tables/annotations/cn_diagram_17.json new file mode 100644 index 0000000000000000000000000000000000000000..15419f58f39142c00e034ada4169b3825e5570c4 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_17.json @@ -0,0 +1,83 @@ +[ + { + "type": "header", + "text": "HarmonyOS NEXT 安全技术白皮书 11 HarmonyOS 安全能力开放使能生态" + }, + { + "type": "text", + "text": "意 URL 检测能力向三方开发者提供了集成简单、免运营、可信赖的安全服务，降低安全浏览服务的实现成本。" + }, + { + "type": "title", + "text": "应用设备状态检测 (Device Verify)" + }, + { + "type": "text", + "text": "应用设备状态检测向开发者提供了管理应用在某设备上使用状态的能力，该服务基于设备证书对设备身份进行认证并签发 DeviceToken，应用的服务器使用 DeviceToken 到 Device Security 服务器查询和管理应用在该设备的使用状态。" + }, + { + "type": "text", + "text": "应用场景：对应用在某台设备上的使用状态进行管理和检测，包括判断应用是否在该设备上首次安装，或在该设备上用户是否已获取了优惠券等的状态检测，以支撑业务进行新用户营销活动。" + }, + { + "type": "title", + "text": "可信服务证明" + }, + { + "type": "text", + "text": "位置信息的安全风险：在一些对安全性较高的场景下，应用在终端侧会获取设备的位置信息，应用服务器把位置信息当做因子一起参与业务逻辑判断或风控检测。但由于应用在 REE 侧获取的位置信息存在被篡改和仿冒的风险，带来以下风险：\n1) 营销活动薅羊毛：电商、银行类应用经常会在指定城市开展营销活动。如果位置信息被篡改，可以快速切换到目标城市，获得参与营销活动资格；\n2) 逃避风控检测：诈骗集团通过前期的诈骗资料收集以及植入木马（盗取验证码和密码）等，交易时通过返回被篡改的地理位置逃避风险的检测；\n3) 游戏外挂：对一些依赖地理位置信息的应用实施攻击行为，通过篡改地理位置，可以瞬间移动到 NPC，破坏游戏平衡。\n人脸图像存在与位置信息同样的安全风险：在金融类应用中，一些业务需要人脸识别通过后才能完成，当前应用的流程一般是先采集人脸数据、再上传到应用服务器完成人脸识别。但如果在设备采集的人脸被篡改，服务器人脸识别通过，带来安全风险、甚至财产损失。\nHarmonyOS 系统向应用提供安全摄像头和安全地理位置能力，如下图所示：" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "业务APP云侧服务" + }, + { + "id": "B", + "text": "业务APP" + }, + { + "id": "C", + "text": "Kit" + }, + { + "id": "D", + "text": "安全摄像头" + }, + { + "id": "E", + "text": "安全地理位置" + } + ], + "relationships": [ + { + "source": "A", + "target": "B", + "label": "上传结果到云服务，完成验证" + }, + { + "source": "B", + "target": "C", + "label": "调用安全摄像头接口或安全地理位置接口" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "E" + } + ] + }, + { + "type": "footer", + "text": "文档版本 V1.0 (2024-08-13) 版权所有 © 华为技术有限公司" + }, + { + "type": "page_number", + "text": "64" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_18.json b/diagrams-and-tables/annotations/cn_diagram_18.json new file mode 100644 index 0000000000000000000000000000000000000000..cd441b682fb26c9c509289b667d556fc7f9743d6 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_18.json @@ -0,0 +1,177 @@ +[ + { + "type": "text", + "text": "\"BMC 启动至 CPU 上电\"之间长达数百毫秒的安全盲区，防止攻击者利用预启动阶段进行恶意植入或篡改。图 5 展示了鲲鹏 TPCM 的整体实现架构。" + }, + { + "type": "diagram_caption", + "text": "图 5 鲲鹏 TPCM 整体架构" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "可信管理中心" + }, + { + "id": "B", + "text": "计算部件" + }, + { + "id": "C", + "text": "操作系统" + }, + { + "id": "D", + "text": "应用" + }, + { + "id": "E", + "text": "应用" + }, + { + "id": "F", + "text": "度量代理" + }, + { + "id": "G", + "text": "OS Loader(Grub)" + }, + { + "id": "H", + "text": "OS度量控制" + }, + { + "id": "I", + "text": "BIOS" + }, + { + "id": "J", + "text": "华为自研Grub度量控制" + }, + { + "id": "K", + "text": "鲲鹏主板" + }, + { + "id": "L", + "text": "防护部件" + }, + { + "id": "M", + "text": "iBMC" + }, + { + "id": "N", + "text": "应用" + }, + { + "id": "O", + "text": "TSB软件基" + }, + { + "id": "P", + "text": "华为自研TPCM固件" + }, + { + "id": "Q", + "text": "带外管理面硬件" + }, + { + "id": "R", + "text": "TCM" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "L" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "C", + "target": "F" + }, + { + "source": "B", + "target": "G" + }, + { + "source": "G", + "target": "H" + }, + { + "source": "B", + "target": "I" + }, + { + "source": "I", + "target": "J" + }, + { + "source": "B", + "target": "K" + }, + { + "source": "L", + "target": "M" + }, + { + "source": "M", + "target": "N" + }, + { + "source": "M", + "target": "O" + }, + { + "source": "L", + "target": "P" + }, + { + "source": "L", + "target": "Q" + }, + { + "source": "Q", + "target": "R" + } + ] + }, + { + "type": "text", + "text": "TPCM 技术的实现依托可信计算 3.0 架构，强调“计算组件”与“防护组件”的物理与逻辑隔离。系统中的 BMC 作为防护部件，运行可信软件基 (Trusted Software Base, TSB)，在 BMC 核与独立的 TCM 核之间建立加密通信信道，并通过度量策略引擎和策略匹配模块对 BIOS、引导程序、操作系统核心、驱动模块乃至关键应用程序进行主动度量与比对。与此同时，运行在主机操作系统层的 TSB Agent 负责收集系统运行状态与动态完整性信息，并上报至 BMC 侧的度量控制模块。一旦系统中存在未授权的组件加载、程序行为超出策略范围，或白名单匹配失败，TPCM 系统可即时采取控制措施，例如中断异常进程、关闭被感染的 CPU 核心、冻结可疑模块加载，乃至强制重启服务器，从而形成一个完整的“发现—判断—控制”防御系统。" + }, + { + "type": "title", + "text": "3.2 计算昇腾算力基础设施安全" + }, + { + "type": "text", + "text": "华为昇腾处理器作为面向 AI 计算场景的自研 NPU，凭借高带宽内存、高吞吐率 AI Core 架构以及完整的软件栈支持，在云端和数据中心已得到广泛部署。随着大模型应用对数据隐私和模型保护需求愈发强烈，构建具备可信保护能力的 AI 执行环境成为 NPU 系统设计的重要课题。尤其在多租户、混合信任的云环境中，如何保障模型和数据在 AI 加速器上运行时不被泄露或篡改，已成为可信 AI 基础设施构建的核心问题。" + }, + { + "type": "footer", + "text": "文档版本 V1.0 版权所有 © 华为技术有限公司" + }, + { + "type": "page_number", + "text": "10" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_19.json b/diagrams-and-tables/annotations/cn_diagram_19.json new file mode 100644 index 0000000000000000000000000000000000000000..d31335ebbe024f3b0f6f4dc3230c1c8b7ecb1790 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_19.json @@ -0,0 +1,153 @@ +[ + { + "type": "title", + "text": "NPU 可信计算" + }, + { + "type": "text", + "text": "华为自研昇腾 NPU 芯片和 BMC 芯片均提供了内置硬件可信根，可提供安全启动、DICE 等安全能力，作为系统信任的“起点”，确保系统启动、运行过程中的关键操作（如固件验证、密钥生成）可被信任。抵御物理攻击（如芯片篡改）和逻辑攻击（如恶意代码注入），为上层安全机制提供“可信基础”。关键引导固件 BSBC、BaseBIOS、高安运行固件 HSM、iBMC 软件均通过 CC EAL4/5+ 高等级安全认证，为客户提供坚实算力安全底座。此外，华为昇腾服务器兼容支持标准 TPM，可为客户业务提供基于 TPM 的可信启动能力。昇腾平台还提供 NPU 应用度量与远程证明服务，能够对关键文件、强制访问控制策略及 NPU 运行状态进行持续度量，从而有效防范 NPU 关键软件组件的非授权修改，保障 NPU 软件栈的完整性与应用安全。" + }, + { + "type": "title", + "text": "NPU 机密计算" + }, + { + "type": "text", + "text": "为应对现实场景中复杂的信任格局，昇腾平台提出了以 NPU 为根、从硬件到运行时的全栈机密计算体系，命名为昇盾（NPU TEE），这一安全体系“以 NPU 为信任边界”，处于非可信域的主机系统，包括主机侧操作系统、驱动、AI 运行时框架和外设通信接口，无法访问 NPU TEE 内的敏感用户数据，最终实现数据在 NPU 侧的隔离与完整性校验。图 6 展示了昇腾机密计算的实现架构。" + }, + { + "type": "diagram_caption", + "text": "图 6 昇腾 NPU TEE 实现架构" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "可信互联协议" + }, + { + "id": "B", + "text": "昇腾 NPU TEE" + }, + { + "id": "C", + "text": "NPU 0" + }, + { + "id": "D", + "text": "TEE 扩展组件" + }, + { + "id": "E", + "text": "NPU 私有内存" + }, + { + "id": "F", + "text": "达芬奇计算单元" + }, + { + "id": "G", + "text": "可信启动" + }, + { + "id": "H", + "text": "远程证明" + }, + { + "id": "I", + "text": "NPU N" + }, + { + "id": "J", + "text": "TEE 扩展组件" + }, + { + "id": "K", + "text": "NPU 私有内存" + }, + { + "id": "L", + "text": "达芬奇计算单元" + }, + { + "id": "M", + "text": "可信启动" + }, + { + "id": "N", + "text": "远程证明" + } + ], + "relationships": [ + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "I" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "C", + "target": "F" + }, + { + "source": "C", + "target": "G" + }, + { + "source": "C", + "target": "H" + }, + { + "source": "B", + "target": "I" + }, + { + "source": "I", + "target": "J" + }, + { + "source": "I", + "target": "K" + }, + { + "source": "I", + "target": "L" + }, + { + "source": "I", + "target": "M" + }, + { + "source": "I", + "target": "N" + } + ] + }, + { + "type": "text", + "text": "昇腾平台设计了 TEE 扩展组件来实现 NPU 的信任边界，该组件对接 NPU 设备到可信互联协议上，NPU 上内存被 TEE 扩展组件隔离，使得 REE 侧恶意程序甚至管理员无法读取 NPU TEE 侧私有内存的模型和用户推理数据。在推理过程中，每个任务所使用的用户输入、中间计算结果、模型参数与 KV 缓存、甚至算子工作空间都在 NPU 私有内存上，并通过 TEE 扩展组件隔绝 REE 的访问。当 NPU 计算完当前用户任务并切换到其它用户的计算任务时，内存内容会被清除后释放，防止在共享计算资源场景下出现信息残留或交叉泄露。这一点在大模型推理中尤为关键，比如在处理 KV 缓存、注意" + }, + { + "type": "footer", + "text": "文档版本 V1.0 版权所有 © 华为技术有限公司" + }, + { + "type": "page_number", + "text": "11" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_20.json b/diagrams-and-tables/annotations/cn_diagram_20.json new file mode 100644 index 0000000000000000000000000000000000000000..5364e8b51823bf46975f2a227c30acfb34343bf0 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_20.json @@ -0,0 +1,218 @@ +[ + { + "type": "text", + "text": "与 TDISP 等方案不同，CoDA 在当前硬件形态下即具备部署能力，且不依赖于异构设备进行安全认证与通道加解密，从而大幅降低部署门槛与复杂度。" + }, + { + "type": "diagram_caption", + "text": "图 8 基于 PCIPC 模块的机密设备直通" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Normal world" + }, + { + "id": "B", + "text": "Host OS" + }, + { + "id": "C", + "text": "VFIO driver" + }, + { + "id": "D", + "text": "PCI driver" + }, + { + "id": "E", + "text": "SMMU driver" + }, + { + "id": "F", + "text": "Secure world" + }, + { + "id": "G", + "text": "cVM0" + }, + { + "id": "H", + "text": "Dev Driver" + }, + { + "id": "I", + "text": "DMA" + }, + { + "id": "J", + "text": "MMIO" + }, + { + "id": "K", + "text": "cVM0" + }, + { + "id": "L", + "text": "Dev Driver" + }, + { + "id": "M", + "text": "DMA" + }, + { + "id": "N", + "text": "MMIO" + }, + { + "id": "O", + "text": "tmm" + }, + { + "id": "P", + "text": "DA Module" + }, + { + "id": "Q", + "text": "SMMU" + }, + { + "id": "R", + "text": "PCIE Root Complex (PCIPC)" + }, + { + "id": "S", + "text": "PCI Device" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "C", + "target": "P", + "label": "Forward vfio_pci_rw" + }, + { + "source": "D", + "target": "P", + "label": "Forward msi" + }, + { + "source": "E", + "target": "P", + "label": "Forward SMMU confia" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "F", + "target": "K" + }, + { + "source": "F", + "target": "O" + }, + { + "source": "F", + "target": "Q" + }, + { + "source": "F", + "target": "R" + }, + { + "source": "F", + "target": "S" + }, + { + "source": "G", + "target": "H" + }, + { + "source": "G", + "target": "I" + }, + { + "source": "G", + "target": "J" + }, + { + "source": "K", + "target": "L" + }, + { + "source": "K", + "target": "M" + }, + { + "source": "K", + "target": "N" + }, + { + "source": "M", + "target": "Q", + "label": "S-EL2" + }, + { + "source": "N", + "target": "S", + "label": "S-EL2" + }, + { + "source": "O", + "target": "P" + }, + { + "source": "P", + "target": "Q" + }, + { + "source": "P", + "target": "R" + }, + { + "source": "Q", + "target": "R" + }, + { + "source": "R", + "target": "S" + } + ] + }, + { + "type": "text", + "text": "在软件栈方面，CoDA 方案高度复用了 Linux 社区成熟的 VFIO、SMMU 与 PCIe 设备驱动能力。只要设备支持 VFIO 半虚拟化机制，即可无差别地接入 cVM。这意味着 GPU、NPU、NVMe SSD、智能网卡 (SmartNIC) 等 PCIe 设备，均可被透明、安全地直通到机密虚拟机中，无需更改驱动或框架层代码。在推理框架、数据服务、边缘推送等应用中，原有业务可无缝迁移至机密环境，带来极大便利性与性能优势。从性能角度看，CoDA 已在多类设备上完成测试与验证。以 NVMe 存储设备为例，测试结果显示 cVM 在直通模式下的顺序与随机访问性能与普通虚拟机持平，而相较于 virtio 等半虚拟化方案，性能提升超过 2 倍。" + }, + { + "type": "text", + "text": "早期 PCIPC 设计以 Root Port 为隔离单位，无法区分同一设备下虚拟功能 (VF) 与物理功能 (PF) 的访问边界，考虑到实际应用中要求 SRIOV 设备也支持机密虚拟机直通，来实现多租户且高性能的云计算要求，升级后的 CoDA 方案采用“驱动结合转发”机制，使能了 SRIOV 特性。当 SRIOV 设备被切入安全世界的时候，非安全世界主机侧设备驱动依然能够通过 PF 配置 VF，PF 的 DMA 使用的是" + }, + { + "type": "footer", + "text": "文档版本 V1.0 版权所有 © 华为技术有限公司" + }, + { + "type": "page_number", + "text": "15" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_21.json b/diagrams-and-tables/annotations/cn_diagram_21.json new file mode 100644 index 0000000000000000000000000000000000000000..71a4c0462c5005018dfd2f6a50562c73f0fa9a9a --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_21.json @@ -0,0 +1,178 @@ +[ + { + "type": "text", + "text": "但是随着存算分离与智能存储的深入应用，数据已不再局限于传统存储设备内部，而是频繁在计算节点、存储节点与网络之间流动，这显著扩大了潜在攻击面，传统以计算为核心的安全模型难以完全适用，如图 9 所示，潜在攻击面主要体现在以下几个方面：" + }, + { + "type": "text", + "text": "• 数据传输安全：在存算分离架构下，数据需要跨节点、跨网络进行频繁传输，传输链路因此成为潜在攻击通道，容易遭受窃听、篡改或中间人攻击，给数据完整性与保密性带来威胁；" + }, + { + "type": "text", + "text": "• 存储计算引擎可信性：随着计算功能下沉至存储节点，存储计算引擎可能成为攻击目标，若缺乏有效的可信执行与验证机制，计算过程透明性与结果可靠性将无法保障，存在被篡改或伪造的风险；" + }, + { + "type": "text", + "text": "• 多租户隔离风险：在云化与共享资源环境中，不同租户的存算资源可能存在隔离不足，尤其在身份认证与授权机制薄弱时，可能导致租户间数据泄漏、越权访问甚至横向攻击，直接冲击系统的安全边界。" + }, + { + "type": "diagram_caption", + "text": "图 10 「存储—计算」机密域框架" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Confidential Computing" + }, + { + "id": "B", + "text": "GPU" + }, + { + "id": "C", + "text": "NPU" + }, + { + "id": "D", + "text": "Accelerator Card" + }, + { + "id": "E", + "text": "PCIPC" + }, + { + "id": "F", + "text": "Confidential Storage" + }, + { + "id": "G", + "text": "1. Hardware Identity" + }, + { + "id": "H", + "text": "Measurement" + }, + { + "id": "I", + "text": "Attestation" + }, + { + "id": "J", + "text": "Hardware Root of Trust" + }, + { + "id": "K", + "text": "3. Multi-layer Authentication" + }, + { + "id": "L", + "text": "Entity Authentication" + }, + { + "id": "M", + "text": "Access Policy Control" + }, + { + "id": "N", + "text": "Confidential LUN" + }, + { + "id": "O", + "text": "Confidential FS" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "E", + "target": "F", + "label": "2. I/O Encryption\n4. Confidential Device Assignment" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "F", + "target": "N" + }, + { + "source": "F", + "target": "O" + }, + { + "source": "G", + "target": "H" + }, + { + "source": "G", + "target": "I" + }, + { + "source": "G", + "target": "J" + }, + { + "source": "H", + "target": "J" + }, + { + "source": "I", + "target": "J" + }, + { + "source": "F", + "target": "K" + }, + { + "source": "K", + "target": "L" + }, + { + "source": "K", + "target": "M" + }, + { + "source": "L", + "target": "M" + } + ] + }, + { + "type": "footer", + "text": "文档版本 V1.0 版权所有 © 华为技术有限公司" + }, + { + "type": "page_number", + "text": "18" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_22.json b/diagrams-and-tables/annotations/cn_diagram_22.json new file mode 100644 index 0000000000000000000000000000000000000000..db19b279a743b306722e3d2c822a79d0d7ae908d --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_22.json @@ -0,0 +1,262 @@ +[ + { + "type": "text", + "text": "为了实现上述目标，擎天机密计算设计在两个维度上提供安全隔离（如图 13 所示）：" + }, + { + "type": "diagram_caption", + "text": "图 13 擎天隔离方案" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "CSP-controlled System" + }, + { + "id": "B", + "text": "Control Plane" + }, + { + "id": "C", + "text": "ECS/VPC/EVS" + }, + { + "id": "D", + "text": "QingTian Cards" + }, + { + "id": "E", + "text": "QingTian Controller 云系统" + }, + { + "id": "F", + "text": "Customer-controlled Instance" + }, + { + "id": "G", + "text": "VM" + }, + { + "id": "H", + "text": "Guest App" + }, + { + "id": "I", + "text": "Guest OS" + }, + { + "id": "J", + "text": "Enclave" + }, + { + "id": "K", + "text": "Enclave App" + }, + { + "id": "L", + "text": "TEE OS" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "F", + "label": "隔离 1" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "F", + "target": "J" + }, + { + "source": "G", + "target": "H" + }, + { + "source": "G", + "target": "I" + }, + { + "source": "G", + "target": "J", + "label": "隔离 2" + }, + { + "source": "J", + "target": "K" + }, + { + "source": "J", + "target": "L" + } + ] + }, + { + "type": "text", + "text": "• 隔离维度 1：将『客户代码和数据』与『云厂商内部人员和云系统软件』隔离，抵御 CSP 内部人员攻击；" + }, + { + "type": "text", + "text": "• 隔离维度 2：将『客户代码和数据』与『客户内部人员和低可信 Guest OS』隔离，抵御客户内部人员攻击。" + }, + { + "type": "title", + "text": "隔离维度 1：假设 CSP 不可信" + }, + { + "type": "text", + "text": "此隔离维度是基于 CSP 不可信的假设，其安全设计目标是将 ECS 实例中的『客户代码和数据』与『云厂商内部人员和云系统软件』进行隔离。" + }, + { + "type": "diagram_caption", + "text": "图 14 擎天计算节点抵御 CSP 内部人员攻击" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "服务器（前端）" + }, + { + "id": "B", + "text": "ECS VM1" + }, + { + "id": "C", + "text": "Untrusted Guest OS (Rich OS)" + }, + { + "id": "D", + "text": "Trusted Enclave" + }, + { + "id": "E", + "text": "ECS VM2" + }, + { + "id": "F", + "text": "Trusted Guest OS" + }, + { + "id": "G", + "text": "QingTian Hypervisor" + }, + { + "id": "H", + "text": "擎天卡（后端）" + }, + { + "id": "I", + "text": "受限的管控 VM" + }, + { + "id": "J", + "text": "网络" + }, + { + "id": "K", + "text": "存储" + }, + { + "id": "L", + "text": "安全" + }, + { + "id": "M", + "text": "SDI NanoOS" + }, + { + "id": "N", + "text": "硬件" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "G" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "A", + "target": "H" + }, + { + "source": "H", + "target": "I" + }, + { + "source": "H", + "target": "J" + }, + { + "source": "H", + "target": "K" + }, + { + "source": "H", + "target": "L" + }, + { + "source": "H", + "target": "M" + }, + { + "source": "H", + "target": "N" + } + ] + }, + { + "type": "footer", + "text": "文档版本 V1.0 版权所有 © 华为技术有限公司" + }, + { + "type": "page_number", + "text": "26" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_23.json b/diagrams-and-tables/annotations/cn_diagram_23.json new file mode 100644 index 0000000000000000000000000000000000000000..45f91502abe33395fa5316146843d72dec5d5ef7 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_23.json @@ -0,0 +1,146 @@ +[ + { + "type": "title", + "text": "度量启动与远程证明" + }, + { + "type": "text", + "text": "擎天 Enclave 提供完整的度量启动与远程证明能力，通过标准可信度量运算得到哈希值并保存在 QTSM 的 PCR 中，使得应用程序可获取当前环境的可信证明文档（Attestation Document），从而与外部实体运行密钥协商和端到端加密等安全协议。其远程证明 PKI 基于多级 CA 层级设计，遵循最大化瞬态安全原则，支持小时级证书轮转，且华为云每个部署均拥有独立的擎天 Attestation CA 以确保隔离性与安全性。华为云 KMS 和 IAM 服务已内置对该证明协议的支持，租户可通过设置 IAM 条件策略实现细粒度控制（如仅允许特定 Enclave 调用特定 KMS API）。典型应用流程中（如图 15 所示），Enclave 生成 RSA 密钥对并获取含公钥的证明文档，随后向 KMS 提交文档与密文请求解密；KMS 验证文档有效性并通过 IAM 策略检查后，使用该公钥对解密结果加密返回，最终由 Enclave 应用本地解封装获得明文。" + }, + { + "type": "diagram_caption", + "text": "图 15 Enclave 应用与 KMS 服务配合进行安全解密的参考流程" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "QingTian Attestation PKI" + }, + { + "id": "B", + "text": "QingTian Root Certificate" + }, + { + "id": "C", + "text": "ECS Instance" + }, + { + "id": "D", + "text": "Enclave" + }, + { + "id": "E", + "text": "Enclave Application" + }, + { + "id": "F", + "text": "Parent VM" + }, + { + "id": "G", + "text": "Network Proxy" + }, + { + "id": "H", + "text": "Relying Party (e.g., KMS)" + }, + { + "id": "I", + "text": "Access Policy (reference measurements as access control conditions)" + }, + { + "id": "J", + "text": "QTSM (Attestation Key)" + }, + { + "id": "K", + "text": "Verifier" + }, + { + "id": "L", + "text": "IAM PDP" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "J", + "label": "Attestation Key Certification" + }, + { + "source": "A", + "target": "K" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "F" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "E", + "target": "G" + }, + { + "source": "E", + "target": "J", + "label": "1\n2" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "G", + "target": "H", + "label": "3\n6" + }, + { + "source": "H", + "target": "K", + "label": "4" + }, + { + "source": "H", + "target": "L", + "label": "5" + }, + { + "source": "I", + "target": "L" + } + ] + }, + { + "type": "text", + "text": "每个 ECS 实例均拥有一个由服务生成的实例身份文档，提供实例的元数据信息，并在实例启动、停止或重启时更新。应用程序可通过实例元数据服务（IMDS）获取该文档及其数字签名，用于向远程依赖方验证实例属性，具备抗重放攻击能力。此“默认出生证”为实例提供初始身份证明，基于可传递信任原则安全获取应用访问凭证，从而避免在代码或配置中硬编码静态凭证。用户也可在创建 ECS 实例时配置 IAM 委托，该虚拟身份由 IAM 管理员创建，代表实例身份且无需静态凭证，有效降低长期凭证泄露风险。应用程序通过 IMDS 获取由 STS 签发的临时安全令牌，据此代表委托身份访问被授权的云服务资源。实例 IAM 委托作为实例的“机器身份”，使应用程序无需硬编码 AK/SK 等静态凭据即可安全调用云服务 API。" + }, + { + "type": "title", + "text": "5.4 华为云擎天异构架构展望" + }, + { + "type": "text", + "text": "在 AI 机密计算需求的推动下，算力需求的增长正驱动组合式 TEE 的快速演进。单个运行在 CPU 上的擎天 Enclave，正在扩展为可与多个加速器 TEE 互联的安全算力群组，从而形成更强大的安全算力。" + }, + { + "type": "footer", + "text": "文档版本 V1.0 版权所有 © 华为技术有限公司" + }, + { + "type": "page_number", + "text": "29" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_24.json b/diagrams-and-tables/annotations/cn_diagram_24.json new file mode 100644 index 0000000000000000000000000000000000000000..81a3400dc4ef1759f4b5b664481bdc2cedbb973e --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_24.json @@ -0,0 +1,252 @@ +[ + { + "type": "header", + "text": "6. AI 平台安全关键技术" + }, + { + "type": "title", + "text": "6.1 A+K 异构机密计算加速平台" + }, + { + "type": "text", + "text": "在面向 AI 的算力安全体系中，单一计算节点的可信保障已无法满足日益复杂的人工智能场景需求。尤其是在大模型推理、高性能训练、多端协同等任务中，CPU 与 NPU 等异构计算单元协同执行的需求持续上升，同时也带来了计算边界扩展、数据跨域流转所引发的安全挑战。为此，在 CPU 通用机密计算平台与 NPU 机密计算平台的基础上，HCIST 还提供异构协同的新型安全架构：A+K 机密计算加速平台（如图 16 所示）。该平台通过可信互联协议，建立跨设备信任传递与统一内存安全映射方案，实现了“双硬件信任根、端到端运行时隔离、任务级零信任验证”三位一体安全架构，从而在保障数据机密性的同时，充分释放计算资源的协同效能。" + }, + { + "type": "diagram_caption", + "text": "图 16 华为 A+K 异构机密计算框架" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "鲲鹏 CPU" + }, + { + "id": "B", + "text": "CPU REE环境" + }, + { + "id": "C", + "text": "系统管理服务" + }, + { + "id": "D", + "text": "Host OS" + }, + { + "id": "E", + "text": "REE 共享内存" + }, + { + "id": "F", + "text": "CPU TEE环境" + }, + { + "id": "G", + "text": "AI训练/推理框架" + }, + { + "id": "H", + "text": "CANN" + }, + { + "id": "I", + "text": "可信启动与远程证明" + }, + { + "id": "J", + "text": "Guest OS" + }, + { + "id": "K", + "text": "TEE 私有内存" + }, + { + "id": "L", + "text": "可信互联协议" + }, + { + "id": "M", + "text": "昇腾 NPU" + }, + { + "id": "N", + "text": "NPU 0" + }, + { + "id": "O", + "text": "TEE扩展组件" + }, + { + "id": "P", + "text": "NPU私有内存" + }, + { + "id": "Q", + "text": "达芬奇计算单元" + }, + { + "id": "R", + "text": "可信启动" + }, + { + "id": "S", + "text": "远程证明" + }, + { + "id": "T", + "text": "NPU N" + }, + { + "id": "U", + "text": "TEE扩展组件" + }, + { + "id": "V", + "text": "NPU私有内存" + }, + { + "id": "W", + "text": "达芬奇计算单元" + }, + { + "id": "X", + "text": "可信启动" + }, + { + "id": "Y", + "text": "远程证明" + }, + { + "id": "Z", + "text": "非信任实体" + }, + { + "id": "AA", + "text": "可信实体" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "B", + "target": "F", + "label": "×" + }, + { + "source": "B", + "target": "L", + "label": "×" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "F", + "target": "H" + }, + { + "source": "F", + "target": "I" + }, + { + "source": "F", + "target": "J" + }, + { + "source": "F", + "target": "K" + }, + { + "source": "F", + "target": "L", + "label": "只有CPU TEE有访问NPU TEE内存的权限" + }, + { + "source": "L", + "target": "N" + }, + { + "source": "L", + "target": "T" + }, + { + "source": "M", + "target": "N" + }, + { + "source": "N", + "target": "O" + }, + { + "source": "N", + "target": "P" + }, + { + "source": "N", + "target": "Q" + }, + { + "source": "N", + "target": "R" + }, + { + "source": "N", + "target": "S" + }, + { + "source": "M", + "target": "T" + }, + { + "source": "T", + "target": "U" + }, + { + "source": "T", + "target": "V" + }, + { + "source": "T", + "target": "W" + }, + { + "source": "T", + "target": "X" + }, + { + "source": "T", + "target": "Y" + } + ] + }, + { + "type": "footer", + "text": "文档版本 V1.0 版权所有 © 华为技术有限公司" + }, + { + "type": "page_number", + "text": "31" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_25.json b/diagrams-and-tables/annotations/cn_diagram_25.json new file mode 100644 index 0000000000000000000000000000000000000000..37f267b4c40a541c6935681082b9403518104337 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_25.json @@ -0,0 +1,268 @@ +[ + { + "type": "diagram_caption", + "text": "图18 Kuasar安全容器框架" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "kubernetes" + }, + { + "id": "B", + "text": "containerd" + }, + { + "id": "C", + "text": "CRI-O" + }, + { + "id": "D", + "text": "docker" + }, + { + "id": "E", + "text": "iSulad" + }, + { + "id": "F", + "text": "sandboxer plugin" + }, + { + "id": "G", + "text": "rust-sandboxer (lib)" + }, + { + "id": "H", + "text": "vmm-sandboxer" + }, + { + "id": "I", + "text": "wasm-sandboxer" + }, + { + "id": "J", + "text": "quark-sandboxer" + }, + { + "id": "K", + "text": "runc-sandboxer" + }, + { + "id": "L", + "text": "microVM Sandbox" + }, + { + "id": "M", + "text": "vmm-task" + }, + { + "id": "N", + "text": "container" + }, + { + "id": "O", + "text": "WASM Sandbox" + }, + { + "id": "P", + "text": "wasm-task" + }, + { + "id": "Q", + "text": "container" + }, + { + "id": "R", + "text": "App Kernel Sandbox" + }, + { + "id": "S", + "text": "quark-task" + }, + { + "id": "T", + "text": "container" + }, + { + "id": "U", + "text": "Runc Sandbox" + }, + { + "id": "V", + "text": "runc-task" + }, + { + "id": "W", + "text": "container" + }, + { + "id": "X", + "text": "Kuasar" + }, + { + "id": "Y", + "text": "Sandbox API framework" + } + ], + "relationships": [ + { + "source": "A", + "target": "F", + "label": "CRI" + }, + { + "source": "B", + "target": "F" + }, + { + "source": "C", + "target": "F" + }, + { + "source": "D", + "target": "F" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "F", + "target": "G", + "label": "Sandbox API" + }, + { + "source": "F", + "target": "P", + "label": "Task API" + }, + { + "source": "G", + "target": "H" + }, + { + "source": "G", + "target": "I" + }, + { + "source": "G", + "target": "J" + }, + { + "source": "G", + "target": "K" + }, + { + "source": "H", + "target": "L" + }, + { + "source": "I", + "target": "O" + }, + { + "source": "J", + "target": "R" + }, + { + "source": "K", + "target": "U" + }, + { + "source": "L", + "target": "M" + }, + { + "source": "L", + "target": "N" + }, + { + "source": "O", + "target": "P" + }, + { + "source": "O", + "target": "Q" + }, + { + "source": "R", + "target": "S" + }, + { + "source": "R", + "target": "T" + }, + { + "source": "U", + "target": "V" + }, + { + "source": "U", + "target": "W" + }, + { + "source": "X", + "target": "H" + }, + { + "source": "X", + "target": "I" + }, + { + "source": "X", + "target": "J" + }, + { + "source": "X", + "target": "K" + }, + { + "source": "X", + "target": "M" + }, + { + "source": "X", + "target": "P" + }, + { + "source": "X", + "target": "S" + }, + { + "source": "X", + "target": "V" + }, + { + "source": "Y", + "target": "F" + }, + { + "source": "Y", + "target": "G" + } + ] + }, + { + "type": "text", + "text": "在当前容器运行时的 Shim v2 模型中，containerd 每创建一个 Pod，就要创建一个对应的 Shim 进程用于 Pod 的管理，Shim 进程再去创建虚拟机和容器，在这种场景下，管理面 Shim 进程和 Pod 的数量关系为 1:1。但在 Kuasar 中，只需要运行一个 Kuasar-Sandboxer 进程，containerd 对 Pod 的管理都是调用 Sandboxer 对外暴露的接口，不再需要为每个 Pod 都拉起一个管理进程，因此，管理面 Sandboxer 进程和 Pod 的数量关系为 1:N。这种模型可以大大减少常驻进程的数量，降低容器管理面底噪，整个架构也因此变得更清晰简洁。" + }, + { + "type": "text", + "text": "基于 Kuasar 安全容器和 TEE 融合，实现 Kuasar 机密容器，保护容器镜像、工作负载及所运行虚机环境的机密性和完整性，防止非授权实体的非法访问，同时兼容云原生应用生态，提高机密计算的易用性。" + }, + { + "type": "text", + "text": "图 19 展示了基于 Kuasar 和 secGear 的机密容器方案。这里 Kuasar 主要对接 QEMU 实现机密虚机生命周期管理，向上屏蔽不同类型的机密虚机，如鲲鹏 virtCCA/CCA 等。iSulad 是将拉取容器镜像动作卸载到机密容器内的 Kuasar-task，在机密容器内部拉取并解密容器镜像，保护容器镜像的机密性和完整性。而 secGear 用来屏蔽 TEE 硬件差异，提供统一的远程证明和镜像加解密密钥获取流程。" + }, + { + "type": "footer", + "text": "文档版本 V1.0 版权所有 © 华为技术有限公司" + }, + { + "type": "page_number", + "text": "35" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_26.json b/diagrams-and-tables/annotations/cn_diagram_26.json new file mode 100644 index 0000000000000000000000000000000000000000..cf4a1035ac38b75a7041e1fbaffa52d4e3be48d7 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_26.json @@ -0,0 +1,211 @@ +[ + { + "type": "diagram_caption", + "text": "图 20 网络设备三层密钥管理组件" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "APP" + }, + { + "id": "B", + "text": "Storage data encryption" + }, + { + "id": "C", + "text": "passwords" + }, + { + "id": "D", + "text": "certificates" + }, + { + "id": "E", + "text": "files" + }, + { + "id": "F", + "text": "Transport data encryption" + }, + { + "id": "G", + "text": "MacSec" + }, + { + "id": "H", + "text": "SSH" + }, + { + "id": "I", + "text": "TLS" + }, + { + "id": "J", + "text": "" + }, + { + "id": "K", + "text": "Cipher algorithm libs" + }, + { + "id": "L", + "text": "对称加密算法" + }, + { + "id": "M", + "text": "公钥加密算法" + }, + { + "id": "N", + "text": "消息认证码" + }, + { + "id": "O", + "text": "哈希算法" + }, + { + "id": "P", + "text": "三层密钥管理" + }, + { + "id": "Q", + "text": "工作密钥1" + }, + { + "id": "R", + "text": "工作密钥n" + }, + { + "id": "S", + "text": "主密钥" + }, + { + "id": "T", + "text": "Hardware" + }, + { + "id": "U", + "text": "Root key" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "F", + "target": "H" + }, + { + "source": "F", + "target": "I" + }, + { + "source": "A", + "target": "J", + "label": "Encryption" + }, + { + "source": "J", + "target": "K" + }, + { + "source": "J", + "target": "P" + }, + { + "source": "K", + "target": "L" + }, + { + "source": "K", + "target": "M" + }, + { + "source": "K", + "target": "N" + }, + { + "source": "K", + "target": "O" + }, + { + "source": "P", + "target": "Q" + }, + { + "source": "P", + "target": "R" + }, + { + "source": "P", + "target": "S" + }, + { + "source": "S", + "target": "Q" + }, + { + "source": "S", + "target": "R" + }, + { + "source": "T", + "target": "U" + }, + { + "source": "S", + "target": "U", + "label": "Encryption protection" + } + ] + }, + { + "type": "text", + "text": "通过在设备生命周期各环节贯穿可验证的信任机制，HCIST 构建了面向未来的自主可信网络设备体系。该体系使设备能够在复杂、异构、跨域的算力环境中持续维持可信状态，不仅为管道安全提供了坚实的硬件基础，也为实现高性能通信安全与跨域算力协同提供了关键保障。" + }, + { + "type": "title", + "text": "7.3 Scale Up 及 Scale Out 通信安全" + }, + { + "type": "text", + "text": "随着大模型、生成式 AI 和多方数据协作的快速发展，算力需求呈指数级增长，单一计算节点已无法满足复杂任务的性能要求。越来越多的计算需要依托 Scale Up（单节点多芯片协同）和 Scale Out（跨节点、跨集群协作）来完成，从而实现更高吞吐和更低时延的数据传输。然而，这种高度互联的算力架构意味着模型权重、企业数据、RAG 索引、用户隐私等敏感信息将在不同计算芯片、节点、集群甚至数据中心之间高频流动，带来了比传统网络更复杂的安全挑战。" + }, + { + "type": "text", + "text": "在算力集群内部和跨集群协作过程中，安全威胁呈现多维度特征：在 Scale Up 场景下，多租户共享硬件资源，恶意程序可通过固件漏洞、隐蔽信道或配置篡改发起攻击；在 Scale Out 场景中，跨框、跨地域的高带宽传输更容易面临线路嗅探、数据篡改与源地址伪造等威胁。同时，大模型训练和推理对性能的要求极为苛刻：部分场景下需实现纳秒级时延与 Tbps 级带宽，而传统基于软件加密的安全通信协议往往无法在性能和安全之间取得平衡。如何在保持高性能的同时保障安全，成为 HCIST 管道安全体系中的关键挑战之一。" + }, + { + "type": "footer", + "text": "文档版本 V1.0 版权所有 © 华为技术有限公司 39" + }, + { + "type": "page_number", + "text": "39" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_27.json b/diagrams-and-tables/annotations/cn_diagram_27.json new file mode 100644 index 0000000000000000000000000000000000000000..62983038427a2819a9621e43a147483dcf50361d --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_27.json @@ -0,0 +1,345 @@ +[ + { + "type": "title", + "text": "8. 典型应用场景" + }, + { + "type": "text", + "text": "HCIST 通过端管云协同的隐私保护架构与纵向全栈安全能力的有机整合，为各行业敏感数据处理场景提供安全可靠的算力支撑。整个架构既可以全栈式部署，发挥端管云协同优势，最大限度提升算力安全基础设施的安全特性，也可以对接不同厂商的算力底座，实现灵活的安全防御策略，适配不同的业务场景和软硬件设施。本章会从端云协同、数据安全、大模型保护、云原生安全特性等维度介绍 HCIST 在这些典型高价值场景中展现出的显著优势，虽然在案例介绍中以华为全栈设备为算力基础设施，但是在实际应用时也可以充分整合和对接不同厂商的算力设备及其安全特性，实现方案的灵活部署。" + }, + { + "type": "title", + "text": "8.1 端云协同大模型推理" + }, + { + "type": "text", + "text": "在 HCIST 算力基础设施安全技术能力的支撑下，HarmonyOS 的小艺个人隐私助理围绕“端云协同、端云安全等同、全栈安全”的核心理念，构建了一种以用户为中心的隐私保护体系（如图 23 所示）。该体系的关键特征并非简单地在端侧加密或云侧隔离，而是在端与云之间建立一套动态、可验证、基于信任链的协同机制，使用户数据在全链路中始终可控。无论数据是在设备本地生成，还是在云端被用于 AI 计算，所有传输、处理与存储路径都依托端云间强耦合的加密与策略管理实现精细化保护。通过端云协同安全框架，释放云上安全算力，达到保障业务体验的目的。" + }, + { + "type": "diagram_caption", + "text": "图23 小艺场景端云协同大模型隐私机密推理" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "以用户为中心的隐私计算体系" + }, + { + "id": "B", + "text": "端侧性能增强" + }, + { + "id": "C", + "text": "端云等同 全栈安全" + }, + { + "id": "D", + "text": "严密保护隐私" + }, + { + "id": "E", + "text": "数据不存储" + }, + { + "id": "F", + "text": "数据不泄露" + }, + { + "id": "G", + "text": "数据不滥用" + }, + { + "id": "H", + "text": "隐私安全新架构" + }, + { + "id": "I", + "text": "端：芯片级硬件安全计算" + }, + { + "id": "J", + "text": "端机密计算区" + }, + { + "id": "K", + "text": "安全证明" + }, + { + "id": "L", + "text": "安全系统" + }, + { + "id": "M", + "text": "安全硬件" + }, + { + "id": "N", + "text": "链路：安全会话通信" + }, + { + "id": "O", + "text": "安全节点" + }, + { + "id": "P", + "text": "安全盲化" + }, + { + "id": "Q", + "text": "云：无状态计算不存储" + }, + { + "id": "R", + "text": "云机密计算区" + }, + { + "id": "S", + "text": "安全计算环境" + }, + { + "id": "T", + "text": "安全可信" + }, + { + "id": "U", + "text": "身份远程证明" + }, + { + "id": "V", + "text": "节点直连端端加密" + }, + { + "id": "W", + "text": "匿名身份管理" + }, + { + "id": "X", + "text": "TEE可信环境" + }, + { + "id": "Y", + "text": "安全芯片" + }, + { + "id": "Z", + "text": "3rd Relay隔离两端信息" + }, + { + "id": "AA", + "text": "身份匿名化不可追溯" + }, + { + "id": "AB", + "text": "数据使用安全" + }, + { + "id": "AC", + "text": "最小化运行时" + }, + { + "id": "AD", + "text": "可证明机密分区" + }, + { + "id": "AE", + "text": "全栈软件完整性" + }, + { + "id": "AF", + "text": "TEE秘钥保护" + }, + { + "id": "AG", + "text": "iTrustee安全OS" + }, + { + "id": "AH", + "text": "安全研究人员独立审计机构" + }, + { + "id": "AI", + "text": "AI可信治理" + } + ], + "relationships": [ + { + "source": "A", + "target": "C" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "H" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "D", + "target": "F" + }, + { + "source": "D", + "target": "G" + }, + { + "source": "H", + "target": "I" + }, + { + "source": "H", + "target": "N" + }, + { + "source": "H", + "target": "Q" + }, + { + "source": "I", + "target": "J" + }, + { + "source": "J", + "target": "U" + }, + { + "source": "J", + "target": "V" + }, + { + "source": "J", + "target": "W" + }, + { + "source": "J", + "target": "X" + }, + { + "source": "J", + "target": "Y" + }, + { + "source": "K", + "target": "U" + }, + { + "source": "K", + "target": "V" + }, + { + "source": "K", + "target": "W" + }, + { + "source": "L", + "target": "X" + }, + { + "source": "M", + "target": "Y" + }, + { + "source": "N", + "target": "O" + }, + { + "source": "N", + "target": "P" + }, + { + "source": "O", + "target": "Z" + }, + { + "source": "Q", + "target": "R" + }, + { + "source": "R", + "target": "AB" + }, + { + "source": "R", + "target": "AC" + }, + { + "source": "R", + "target": "AD" + }, + { + "source": "R", + "target": "AE" + }, + { + "source": "R", + "target": "AF" + }, + { + "source": "R", + "target": "AG" + }, + { + "source": "R", + "target": "AH" + }, + { + "source": "R", + "target": "AI" + }, + { + "source": "S", + "target": "AB" + }, + { + "source": "S", + "target": "AC" + }, + { + "source": "S", + "target": "AD" + }, + { + "source": "S", + "target": "AE" + }, + { + "source": "S", + "target": "AF" + }, + { + "source": "S", + "target": "AG" + }, + { + "source": "T", + "target": "AH" + }, + { + "source": "P", + "target": "AA" + }, + { + "source": "T", + "target": "AI" + } + ] + }, + { + "type": "footer", + "text": "文档版本 V1.0 版权所有 © 华为技术有限公司 39" + }, + { + "type": "page_number", + "text": "43" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_28.json b/diagrams-and-tables/annotations/cn_diagram_28.json new file mode 100644 index 0000000000000000000000000000000000000000..dd17fd0431c77f027b516f2c92626df63f49bd6b --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_28.json @@ -0,0 +1,265 @@ +[ + { + "type": "header", + "text": "NXP" + }, + { + "type": "header", + "text": "oT)要变为现实，还缺什么" + }, + { + "type": "text", + "text": "目前可使用的技术有很多，也有许多仍在开发中，这些新技术允许车辆相互通信、并与中央控制单元进行通信。这些智能汽车还可以感知道路、交通标志和道路标志，并使用GPS和通信链路，避免经过即将拥堵的道路，并避免在转弯处出现事故，或与中央控制单元配合，避免经过处于倒塌边缘的高危桥梁。" + }, + { + "type": "text", + "text": "远程监控患者是另一个与使用有关的示例。例如，设想一下一个跟踪生物特征的植入式传感节点，向一个老年患者发出一个异常的读数信号。如果患者没有反响服用药，那么节点会拨打紧急电话联系名单的联系人，如果无人接听，节点会呼叫下一个联系人，最后如果仍无人接听，节点便会联系监控诊所或快速提供其他紧急援助。另一个示例是持续监控慢性疾病，帮助医生确定最佳的治疗方式，只需最少的人力干预。" + }, + { + "type": "text", + "text": "所有以上用例的通用要求包括：\n1) 传感和数据采集功能(传感节点)\n2) 本地嵌入式处理功能层(本地嵌入式处理节点)\n3) 有线和/或无线通信功能(连接节点)\n4) 自动化任务并支持新的服务类别的软件\n5) 远程网络/基于云的嵌入式处理功能(远程嵌入式处理节点)\n6) 跨信号路径的完整安全性能" + }, + { + "type": "diagram_caption", + "text": "物联网技术功能视图" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "传感和/或智能设备" + }, + { + "id": "B", + "text": "连接节点" + }, + { + "id": "C", + "text": "嵌入式处理节点层" + }, + { + "id": "D", + "text": "连接节点" + }, + { + "id": "E", + "text": "远程基于云的处理" + }, + { + "id": "F", + "text": "应用/操作" + }, + { + "id": "G", + "text": "通过带屏幕的设备由用户驱动或基于数据参数自动操作" + }, + { + "id": "H", + "text": "洞察/大数据" + }, + { + "id": "I", + "text": "商业智能数据分析" + }, + { + "id": "J", + "text": "在所有节点上的软件" + }, + { + "id": "K", + "text": "S" + }, + { + "id": "L", + "text": "S" + }, + { + "id": "M", + "text": "S" + }, + { + "id": "N", + "text": "P" + }, + { + "id": "O", + "text": "P" + }, + { + "id": "P", + "text": "P" + }, + { + "id": "Q", + "text": "C" + }, + { + "id": "R", + "text": "C" + }, + { + "id": "S", + "text": "C" + }, + { + "id": "T", + "text": "P" + }, + { + "id": "U", + "text": "C" + }, + { + "id": "V", + "text": "P" + }, + { + "id": "W", + "text": "S:传感" + }, + { + "id": "X", + "text": "P:嵌入式处理" + }, + { + "id": "Y", + "text": "C:通讯" + } + ], + "relationships": [ + { + "source": "A", + "target": "J" + }, + { + "source": "A", + "target": "K" + }, + { + "source": "A", + "target": "L" + }, + { + "source": "A", + "target": "M" + }, + { + "source": "A", + "target": "N" + }, + { + "source": "A", + "target": "O" + }, + { + "source": "A", + "target": "P" + }, + { + "source": "B", + "target": "J" + }, + { + "source": "B", + "target": "Q" + }, + { + "source": "B", + "target": "R" + }, + { + "source": "B", + "target": "S" + }, + { + "source": "C", + "target": "J" + }, + { + "source": "C", + "target": "T" + }, + { + "source": "D", + "target": "J" + }, + { + "source": "D", + "target": "U" + }, + { + "source": "E", + "target": "J" + }, + { + "source": "E", + "target": "V" + }, + { + "source": "F", + "target": "V" + }, + { + "source": "H", + "target": "V" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "H", + "target": "I" + }, + { + "source": "K", + "target": "L" + }, + { + "source": "L", + "target": "M" + }, + { + "source": "O", + "target": "P" + }, + { + "source": "O", + "target": "R" + }, + { + "source": "N", + "target": "Q" + }, + { + "source": "P", + "target": "S" + }, + { + "source": "R", + "target": "T" + }, + { + "source": "T", + "target": "U" + }, + { + "source": "U", + "target": "V" + } + ] + }, + { + "type": "footer", + "text": "白皮书" + }, + { + "type": "page_number", + "text": "7" + }, + { + "type": "footer", + "text": "arm.com / freescale.com" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_29.json b/diagrams-and-tables/annotations/cn_diagram_29.json new file mode 100644 index 0000000000000000000000000000000000000000..e5c5293cd7fc6d09ce88905a2606ff7f8d683034 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_29.json @@ -0,0 +1,335 @@ +[ + { + "type": "header", + "text": "工业数字化/智能化2030" + }, + { + "type": "title", + "text": "3)技术支撑" + }, + { + "type": "text", + "text": "要实现上述的新理念、新模式，工业软件的上云是大势所趋。工业软件应把握云计算变革的机会窗口，以云、AI、大数据作为关键底层技术支撑，走向全新的、云化的工业软件体系。（图4-30: 云化工业软件的关键底层技术）\n具体而言，新一代工业软件需要基于云计算的架构，依托云的技术特点，实现易集成、易开发、易协同、易扩展四大特点。\n易集成，主要指场景化SaaS。以基于模型为核心理念，工业界伙伴共同打造面向不同工业场景的工具链，形成可集成的场景化SaaS服务。\n易开发，主要指aPaaS。工业界伙伴将工业知识、经验、数据、工具沉淀在云平台，共建共享共用工业根服务，大幅降低工业软件开发门槛。\n易协同，主要指工业软件开发运营中心。工业界伙伴通过共同开发工具组件、按需调用API接口，不仅实现service乃至service on service的敏捷开发，也满足工业企业灵活按需使用、按使用量计费的需求。\n易扩展，主要指gPaaS、IaaS。基于云基础设施，工业企业基于场景需求，面向近期可以灵活调用云端算力、存储资源，实现资源配置的动态优化；面向远期也可以弹性满足业务升级扩容需求，大幅减少硬件置换和运维成本。（图4-31: 基于云计算架构的工业软件体系示意）" + }, + { + "type": "diagram_caption", + "text": "图4-30: 云化工业软件的关键底层技术" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "基于云的计算框架" + }, + { + "id": "B", + "text": "过去" + }, + { + "id": "C", + "text": "未来" + }, + { + "id": "D", + "text": "单机计算框架" + }, + { + "id": "E", + "text": "云计算框架" + }, + { + "id": "F", + "text": "本地开发部署" + }, + { + "id": "G", + "text": "虚拟机" + }, + { + "id": "H", + "text": "传统集中式数据库" + }, + { + "id": "I", + "text": "本地固定资源" + }, + { + "id": "J", + "text": "云端开发部署" + }, + { + "id": "K", + "text": "容器集群" + }, + { + "id": "L", + "text": "分布式云数据库" + }, + { + "id": "M", + "text": "资源动态配置" + }, + { + "id": "N", + "text": "AI" + }, + { + "id": "O", + "text": "驱动工业应用提质增效、进一步少人化" + }, + { + "id": "P", + "text": "大数据" + }, + { + "id": "Q", + "text": "驱动精准分析、决策与创新应用" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "N", + "label": "+" + }, + { + "source": "A", + "target": "P", + "label": "+" + }, + { + "source": "B", + "target": "C", + "label": "变革" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "D", + "target": "F" + }, + { + "source": "D", + "target": "G" + }, + { + "source": "D", + "target": "H" + }, + { + "source": "D", + "target": "I" + }, + { + "source": "E", + "target": "J" + }, + { + "source": "E", + "target": "K" + }, + { + "source": "E", + "target": "L" + }, + { + "source": "E", + "target": "M" + }, + { + "source": "N", + "target": "O" + }, + { + "source": "P", + "target": "Q" + } + ] + }, + { + "type": "diagram_caption", + "text": "图4-31: 基于云计算架构的工业软件体系示意" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "场景化 SaaS( 基于模型 )" + }, + { + "id": "B", + "text": "MBSE" + }, + { + "id": "C", + "text": "MBDx" + }, + { + "id": "D", + "text": "MBM" + }, + { + "id": "E", + "text": "系统设计仿真云服务" + }, + { + "id": "F", + "text": "板级 EDA 云服务" + }, + { + "id": "G", + "text": "工业仿真云服务" + }, + { + "id": "H", + "text": "设计制造融合云服务" + }, + { + "id": "I", + "text": "aPaaS ( 工业根服务 )" + }, + { + "id": "J", + "text": "工业经验的根(工业基础资源库)" + }, + { + "id": "K", + "text": "工业数据的根(工业数据管理平台)" + }, + { + "id": "L", + "text": "工业软件的根(工业软件内核引擎)" + }, + { + "id": "M", + "text": "工业智能的根(工业智能组件)" + }, + { + "id": "N", + "text": "gPaaS" + }, + { + "id": "O", + "text": "云" + }, + { + "id": "P", + "text": "大数据" + }, + { + "id": "Q", + "text": "AI" + }, + { + "id": "R", + "text": "IaaS" + }, + { + "id": "S", + "text": "工业软件开发运营中心" + }, + { + "id": "T", + "text": "工业 SaaS 服务中心" + }, + { + "id": "U", + "text": "工业软件 DevOps 工具链" + }, + { + "id": "V", + "text": "工业云商店" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "C", + "target": "F" + }, + { + "source": "C", + "target": "G" + }, + { + "source": "D", + "target": "H" + }, + { + "source": "I", + "target": "J" + }, + { + "source": "I", + "target": "K" + }, + { + "source": "I", + "target": "L" + }, + { + "source": "I", + "target": "M" + }, + { + "source": "N", + "target": "O" + }, + { + "source": "N", + "target": "P" + }, + { + "source": "N", + "target": "Q" + }, + { + "source": "S", + "target": "T" + }, + { + "source": "S", + "target": "U" + }, + { + "source": "S", + "target": "V" + } + ] + }, + { + "type": "page_number", + "text": "58" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_30.json b/diagrams-and-tables/annotations/cn_diagram_30.json new file mode 100644 index 0000000000000000000000000000000000000000..457435c01b3774612af1ae304ee0e41cefe387e2 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_30.json @@ -0,0 +1,149 @@ +[ + { + "type": "header", + "text": "人工智能就绪度白皮书" + }, + { + "type": "diagram_caption", + "text": "AI Ready硬实力变革分析框架" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "业务应用层" + }, + { + "id": "B", + "text": "模型服务与编排层" + }, + { + "id": "C", + "text": "基础设施层" + }, + { + "id": "D", + "text": "服务治理层" + }, + { + "id": "E", + "text": "产品与服务创新" + }, + { + "id": "F", + "text": "交互式客户体验" + }, + { + "id": "G", + "text": "智能洞察与决策" + }, + { + "id": "H", + "text": "..." + }, + { + "id": "I", + "text": "模型管理与服务化" + }, + { + "id": "J", + "text": "智能体与应用编排" + }, + { + "id": "K", + "text": "计算" + }, + { + "id": "L", + "text": "网络" + }, + { + "id": "M", + "text": "存储" + }, + { + "id": "N", + "text": "数据" + }, + { + "id": "O", + "text": "安全可信AI" + }, + { + "id": "P", + "text": "AI全栈治理" + } + ], + "relationships": [ + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "A", + "target": "G" + }, + { + "source": "A", + "target": "H" + }, + { + "source": "B", + "target": "I" + }, + { + "source": "B", + "target": "J" + }, + { + "source": "C", + "target": "K" + }, + { + "source": "C", + "target": "L" + }, + { + "source": "C", + "target": "M" + }, + { + "source": "C", + "target": "N" + }, + { + "source": "D", + "target": "O" + }, + { + "source": "D", + "target": "P" + } + ] + }, + { + "type": "text", + "text": "基础设施层是企业AI技术落地的物理与虚拟资源支撑体系，是承载AI模型训练、推理与部署的高可用性底座。它包含计算资源、网络架构、存储系统及数据语料等核心要素，为上层AI应用提供稳定、高效、可拓展的运行环境。" + }, + { + "type": "text", + "text": "AI模型服务与编排层（AI Model Service and Orchestration Layer）是企业AI能力体系的中枢，扮演着承上启下的关键角色。它下接坚实的AI基础设施层（算力、网络、存储、数据），负责将底层资源与AI模型能力进行封装、管理与优化；上承多样化的业务应用场景，提供标准、高效、灵活的AI能力调用接口与智能编排服务。该层核心目标是屏蔽底层基础设施的复杂性，赋能上层应用的敏捷创新，确保企业能够高效、安全、可扩展地利用各类AI模型（包括基础大模型、行业模型、自研模型等）驱动业务价值。其关键要素包括多模型管理与服务化、智能体（Agent）与应用编排以及模型通信协议与集成。" + }, + { + "type": "text", + "text": "服务治理层是保障企业AI系统合规、安全、可持续运行的安全防护和治理体系，涵盖安全可信AI和AI全栈治理两大支柱，旨在推动企业AI安全及治理从原则规范走向工程化落地。" + }, + { + "type": "footer", + "text": "© 2025 毕马威华振会计师事务所（特殊普通合伙） — 中国合伙制会计师事务所，毕马威企业咨询（中国）有限公司 — 中国有限责任公司，毕马威会计师事务所 — 澳门特别行政区合伙制事务所，及毕马威会计师事务所 — 香港特别行政区合伙制事务所，均是与毕马威国际有限公司（英国私营担保有限公司）相关联的独立成员所全球组织中的成员。版权所有，不得转载。在中国印刷。" + }, + { + "type": "page_number", + "text": "48" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_31.json b/diagrams-and-tables/annotations/cn_diagram_31.json new file mode 100644 index 0000000000000000000000000000000000000000..cade7201eda7485b364b3cf19877897045fed814 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_31.json @@ -0,0 +1,133 @@ +[ + { + "type": "header", + "text": "毕马威银行业客户体验白皮书" + }, + { + "type": "title", + "text": "任重道远\n客户体验已被赋予新的内涵，但调研发现银行体验现状仍存提升空间\n分析框架简介" + }, + { + "type": "text", + "text": "我们的调研主要通过问卷的方式，并得到了京东科技的技术支持，在初步整理和分析问卷反馈结果后，我们发现，各类型银行的客户群体在银行各条线、渠道和场景的服务体验存在差异，不同类型银行客户的体验期望也不尽相同。客户体验管理在银行已经被赋予新的内涵，不仅仅是作为售后客户满意度的调查，而是延伸到售前、售中和售后等客户旅程的各个环节，作为产品设计、渠道建设、客户服务能力提升、系统优化等方面的重要输入，本次分析将目标银行按照不同类型（国有银行、股份制银行以及区域性银行）进行区分分别进行客户体验分析。本次调研主要分析银行的零售业务，包含厅堂服务、电子渠道、财富管理、信贷业务以及信用卡业务等业务条线和渠道维度的客户体验现状。除此之外，我们对以上调研项目将调研结果按照性别、银行客户粘性进行区分，在本文中，若客户在该银行的资产占家庭资产的 50% 以上，我们将该银行定义为客户的主办银行，具有较强的客户粘性，下文简称为主办行客户。若客户在该银行的资产占家庭资产的 50% 以下，我们将该银行定义为客户的使用银行，下文简称为使用行客户。" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "银行业客户体验" + }, + { + "id": "B", + "text": "国有银行" + }, + { + "id": "C", + "text": "股份制银行" + }, + { + "id": "D", + "text": "区域性银行" + }, + { + "id": "E", + "text": "业务种类" + }, + { + "id": "F", + "text": "厅堂服务" + }, + { + "id": "G", + "text": "电子渠道" + }, + { + "id": "H", + "text": "财富管理" + }, + { + "id": "I", + "text": "信贷业务" + }, + { + "id": "J", + "text": "信用卡业务" + }, + { + "id": "K", + "text": "•银行客户性别评估：评估各大银行种类客户中，男女性客户体验的异同。" + }, + { + "id": "L", + "text": "•银行客户粘性评估：评估各大银行种类客户中，忠实客户与普通客户体验的异同。" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "E", + "target": "G" + }, + { + "source": "E", + "target": "H" + }, + { + "source": "E", + "target": "I" + }, + { + "source": "E", + "target": "J" + } + ] + }, + { + "type": "text", + "text": "我们从调研中总结出影响国有银行、股份制银行与区域性银行客户体验的重要因素，并对可能的原因进行了分析。" + }, + { + "type": "title", + "text": "1、影响银行业整体客户体验关键因素摘要" + }, + { + "type": "text", + "text": "本次调研中，为洞悉影响银行整体客户体验的主要影响因素，我们主要从银行产品（产品好、选择范围广、到期收益高）、银行服务（服务好、业务专业、过程体验佳）、银行提供的权益（权益好、提供其" + }, + { + "type": "page_number", + "text": "19" + }, + { + "type": "footer", + "text": "© 2023 毕马威企业咨询（中国）有限公司 — 中国有限责任公司，是与英国私营担保有限公司 — 毕马威国际有限公司相关联的独立成员所全球性组织中的成员。版权所有，不得转载。在中国印刷。毕马威的名称和标识均为毕马威全球性组织中的独立成员所经许可后使用的商标。" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_32.json b/diagrams-and-tables/annotations/cn_diagram_32.json new file mode 100644 index 0000000000000000000000000000000000000000..60d103b72f4fa6fdfa6d539578f82688653049b8 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_32.json @@ -0,0 +1,89 @@ +[ + { + "type": "header", + "text": "毕马威银行业客户体验白皮书" + }, + { + "type": "text", + "text": "开始对网点进行全面的智能化改造，5 年时间，网点内部完成两次升级改造，网点内部布局领先与同行业其他银行。但股份制银行的网点劣势在于数量相对较少，相较国有银行的网点密集度，股份制银行网点布局稀疏，且大量集中于城区，客户前往银行的网点不便。虽然股份制银行利用数字化、科技化手段拓宽了银行业务办理渠道，增加了网点的辐射半径，但在中国消费者客户意识中，网点仍然是银行品牌的主要显性载体，网点仍然是银行开展业务的主战场。因此，股份制银行需考虑在现有网点数量下，如何优化网点布局，让客户体验网点方便快捷的服务。\n\n国有银行网点数量多，且银行数字化时间较早，网点内部智能设备多，相较其他两类银行，网点布局与环境较为均衡，客户认为网点不是国有银行最优先需要提升的维度，我们也观察到国有银行处于网点整体保持稳定、局部地区数量进行优化的阶段。" + }, + { + "type": "title", + "text": "2.3 手机银行作为影响整体客户体验最重要的渠道，客户期望甚高" + }, + { + "type": "text", + "text": "根据调研，手机银行的体验是影响客户对银行服务整体体验最重要的因素，完善手机银行功能，提升移动端用户体验是银行需要在未来需要持续重点投入以提升的方向。19% 的客户认为银行手机银行仍然需要继续优化，其中，27.7% 的国有银行客户认为银行需要优化手机银行界面设计、提升使用便利度，但对于将国有银行作为主办行的客户而言，他们倾向于依赖物理网点办理业务和进行咨询，反而对手机银行的重视程度不如其他银行的客户。在区域性银行客户中，男性客户更希望银行能够提升手机银行的功能和体验，说明男性客户更看中办理业务时的方便与快捷。和主办行客户相比，区域性银行的使用行客户更关注手机银行的体验，手机银行的体验是提升使用行客户体验的重要抓手。而对于股份制银行而言，手机银行功能更新速度快，相较其他类型的银行，界面、功能与使用体验均有优势，因此较少的客户认为股份制银行需要提升手机银行。" + }, + { + "type": "title", + "text": "3、客户体验——厅堂服务篇" + }, + { + "type": "title", + "text": "3.1 网点工作人员的服务态度是银行厅堂服务最重要的影响因素" + }, + { + "type": "diagram_caption", + "text": "图 9：厅堂服务客户体验的影响因素" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "银行厅堂服务体验的影响因素" + }, + { + "id": "B", + "text": "工作人员的服务态度和流程" + }, + { + "id": "C", + "text": "厅堂内智能设备功能" + }, + { + "id": "D", + "text": "网点提供的客户权益" + }, + { + "id": "E", + "text": "厅堂环境和布置" + }, + { + "id": "F", + "text": "厅堂内的人流和排队情况" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "F" + } + ] + }, + { + "type": "page_number", + "text": "26" + }, + { + "type": "footer", + "text": "© 2023 毕马威企业咨询（中国）有限公司 — 中国有限责任公司，是与英国私营担保有限公司 — 毕马威国际有限公司相关联的独立成员所全球性组织中的成员。版权所有，不得转载。在中国印刷。毕马威的名称和标识均为毕马威全球性组织中的独立成员所经许可后使用的商标。" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_33.json b/diagrams-and-tables/annotations/cn_diagram_33.json new file mode 100644 index 0000000000000000000000000000000000000000..73a40b630456673ceb620f4d39f212e0d8189d6b --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_33.json @@ -0,0 +1,193 @@ +[ + { + "type": "header", + "text": "毕马威银行业客户体验白皮书" + }, + { + "type": "text", + "text": "随着我国经济的高速发展，我国居民个人资产水平逐渐提高。其中，金融类资产的配置需求也不断增强，潜在的财富管理市场发展空间巨大。而对于银行而言，财富管理是轻资本业务，符合当下银行商业模式转型的方向，越来越多的银行将财富管理作为战略转型的重要板块。因此财富管理的客户体验逐渐受到各家银行的重视。本次调研数据显示，客户经理的专业程度、产品种类与产品收益率是财富管理板块影响客户体验的三大主要因素。其中，国有银行的客户更重视客户经理的专业程度，有 26.1% 的客户认为专业的客户经理是他们选择该行进行投资的重要原因。而对于股份制银行于区域性银行而言，产品的收益率是客户首要关注的因素，也是两类银行吸引客户的重要抓手。将各类银行深入分析后，各类客户的表现也不尽相同。\n\n虽然国有银行总体客户以客户经理的专业程度作为最重要的影响因素，但对于男性客户而言，产品的收益率情况是这些客户的第一关注点，占比达到 26.67%。由此可知，国有银行在对男性客户进行产品营销时，应以产品的收益率以及收益的保障情况入手，让客户迅速建立起对银行的信任。对于股份制银行的主办行客户而言，客户经理的专业程度反而是这类客户最关注的因素，客户占比达到了 39.24%。因股份制银行的主办行客户通常在过往的投资理财过程中，对该银行的产品收益与风险情况较为满意，产品已符合客户预期，因此客户经理能否为客户做好资产的合理配置，即成为了首要关注的因素。区域性银行的客户偏好基本与股份制银行一致，唯一不同的一点在于，部分客户认为客户经理的职业操守是影响财富管理体验的重要因素。相比国有银行和股份制银行，区域性银行的部分理财经理合规意识较弱，部分行为对客户的利益造成了损害，造成了区域性银行客户对银行信任度降低。" + }, + { + "type": "title", + "text": "5.2 产品介绍的清晰度是线上理财体验最关键的影响因素之一，而理财经理的专业程度是影响线下网点理财体验的重要风向标" + }, + { + "type": "diagram_caption", + "text": "图 19：银行 APP 与网点财富管理客户体验影响因素" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "APP 理财客户影响因素" + }, + { + "id": "B", + "text": "能够及时通知投资状态" + }, + { + "id": "C", + "text": "风险评估时给予建议和指引" + }, + { + "id": "D", + "text": "产品信息条款介绍清晰易懂" + }, + { + "id": "E", + "text": "产品挑选过程便捷" + }, + { + "id": "F", + "text": "产品赎回很方便" + }, + { + "id": "G", + "text": "功能齐全" + }, + { + "id": "H", + "text": "交易扣款方便" + }, + { + "id": "I", + "text": "收益查询和试算很方便" + }, + { + "id": "J", + "text": "个性化推荐理财产品" + }, + { + "id": "K", + "text": "风险测评方便快捷" + }, + { + "id": "L", + "text": "推送理财知识" + }, + { + "id": "M", + "text": "网点理财客户影响因素" + }, + { + "id": "N", + "text": "专员投资理财指引简单易懂" + }, + { + "id": "O", + "text": "专员耐心教导使用 APP" + }, + { + "id": "P", + "text": "专员产品风险提示到位" + }, + { + "id": "Q", + "text": "专员业务能力强很专业" + }, + { + "id": "R", + "text": "专员推荐产品符合理财需求" + }, + { + "id": "S", + "text": "专员解释产品简单明了" + }, + { + "id": "T", + "text": "专员在风险评估时给予建议和指引" + }, + { + "id": "U", + "text": "业务流程短填写资料少" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "A", + "target": "G" + }, + { + "source": "A", + "target": "H" + }, + { + "source": "A", + "target": "I" + }, + { + "source": "A", + "target": "J" + }, + { + "source": "A", + "target": "K" + }, + { + "source": "A", + "target": "L" + }, + { + "source": "M", + "target": "N" + }, + { + "source": "M", + "target": "O" + }, + { + "source": "M", + "target": "P" + }, + { + "source": "M", + "target": "Q" + }, + { + "source": "M", + "target": "R" + }, + { + "source": "M", + "target": "S" + }, + { + "source": "M", + "target": "T" + }, + { + "source": "M", + "target": "U" + } + ] + }, + { + "type": "page_number", + "text": "36" + }, + { + "type": "footer", + "text": "© 2023 毕马威企业咨询（中国）有限公司 — 中国有限责任公司，是与英国私营担保有限公司 — 毕马威国际有限公司相关联的独立成员所全球性组织中的成员。版权所有，不得转载。在中国印刷。毕马威的名称和标识均为毕马威全球性组织中的独立成员所经许可后使用的商标。" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_34.json b/diagrams-and-tables/annotations/cn_diagram_34.json new file mode 100644 index 0000000000000000000000000000000000000000..0821b5275a833b1b9280a6739cb4693d089a54be --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_34.json @@ -0,0 +1,81 @@ +[ + { + "type": "header", + "text": "毕马威银行业客户体验白皮书" + }, + { + "type": "text", + "text": "APP 理财的关键因素包括能够及时通知投资状态、风险评估时给予建议和指引、产品信息、条款介绍清晰易懂、产品挑选过程便捷、产品赎回很方便、功能齐全、交易扣款方便、收益查询和试算很方便、风险测评方便快捷、个性化推荐理财产品、推送理财知识等因素。\n\n网点理财体验的关键因素包括专员投资理财指引简单易懂、专员耐心教导使用 APP，专员产品风险提示到位，专员业务能力强、很专业，专员推荐产品符合理财需求，专员解释产品简单明了，专员在风险评估时给予建议和指引，业务流程短、填写资料少。\n\n本次调研中，我们对在 APP 上与网点内购买理财的客户体验影响因素进行了调研分析。数据显示，在 APP 上购买理财的客户更关注产品条款的清晰程度。26.1% 国有银行客户与 27.5% 股份制银行客户认为，产品信息与条款介绍是否清晰易懂，是影响他们选择 APP 进行理财的关键因素，而选择该选项的区域性银行客户的比例更高，达到 59.5%。因客户在线上挑选理财产品时，无法即时与专业的理财经理沟通产品信息，因此对产品收益与风险清晰说明，是客户获得信息的最重要渠道。另外，客户还希望在 APP 购买理财时，银行能够提供便捷的产品挑选流程。20.3% 的国有银行客户与 31.25% 的股份制银行客户选择产品挑选过程的便捷性是决定他们使用 APP 理财的关键因素，使用线上渠道购买理财时，客户已需要处理大量的、复杂的产品信息，繁琐的 APP 操作无疑会消耗客户仅存的耐心，极大的降低客户体验。同时，线上理财的状态通知的及时性，也是客户关注的重要因素，23.2% 的国有银行客户与 38.13% 的股份制银行客户，期望银行能够及时更新通知投资状态。在缺少银行工作人员的情形下，部分客户会滋生缺乏安全感的情绪，对投资状态通知的及时性，会减轻客户担忧的情绪，增加客户对银行的信任感。\n\n影响客户在网点购买理财最关键的因素是理财经理的专业程度。调研发现，47.8% 的国有银行客户、26.9% 的股份制银行客户以及 73% 的区域性银行客户均认为理财经理的业务能力是影响他们在网点理财体验的关键因素。相较于线上，网点理财的最大优势即是理财经理能够与客户面对面进行服务。通过与客户的当面交谈，理财经理能够更深入的了解客户的基本情况与需求，为客户进行专业、个性化的资产配置建议，赢得客户的信任。" + }, + { + "type": "title", + "text": "5.3 随着产品同质化水平越来越高，提升财富客户满意度的难度日益增加，银行需要从产品到服务等多方面发力" + }, + { + "type": "text", + "text": "基于影响财富客户体验的重要影响因素，从硬性的产品竞争力，到软性的银行服务以及业务办理流程，我们归纳了五条银行财富管理业务的发展路径，并对客户进行调研，对发展路径的重要性进行识别。" + }, + { + "type": "diagram_caption", + "text": "图 20：银行财富管理客户体验提升方向" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "财富管理提升方向" + }, + { + "id": "B", + "text": "产品竞争力" + }, + { + "id": "C", + "text": "对客户诚信度" + }, + { + "id": "D", + "text": "产品赎回便利度" + }, + { + "id": "E", + "text": "办理渠道多样化" + }, + { + "id": "F", + "text": "客户理财服务体验" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "F" + } + ] + }, + { + "type": "page_number", + "text": "37" + }, + { + "type": "footer", + "text": "© 2023 毕马威企业咨询（中国）有限公司 — 中国有限责任公司，是与英国私营担保有限公司 — 毕马威国际有限公司相关联的独立成员所全球性组织中的成员。版权所有，不得转载。在中国印刷。毕马威的名称和标识均为毕马威全球性组织中的独立成员所经许可后使用的商标。" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_35.json b/diagrams-and-tables/annotations/cn_diagram_35.json new file mode 100644 index 0000000000000000000000000000000000000000..b484fed3f783aadb3f0f277bcd52e8fde5eff604 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_35.json @@ -0,0 +1,141 @@ +[ + { + "type": "title", + "text": "1. 现制茶饮的发展与消费现状分析" + }, + { + "type": "text", + "text": "现制茶饮由商家在店铺内依据消费者个性化需求现场制作、调配并销售，以“现做现卖，即产即饮”为突出特点，工艺简单，生产快捷，可以较大限度的保留食材营养成分，减少食品生产添加剂的使用。最初期的现制茶饮产品多以奶精等勾兑为主，多在档口或街边小店销售，随后逐渐历经了品类的丰富和品牌的打造，形成了如今产品种类细分、食材原料丰富、品牌定位明晰和产品知名度提升的发展新阶段。" + }, + { + "type": "diagram_caption", + "text": "图 1-1 现制茶饮的发展历程$^{[1]}$" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "茶饮品类" + }, + { + "id": "B", + "text": "1.0时代" + }, + { + "id": "C", + "text": "2.0时代" + }, + { + "id": "D", + "text": "3.0时代" + }, + { + "id": "E", + "text": "4.0时代" + }, + { + "id": "F", + "text": "粉末阶段\n（1995年以前）" + }, + { + "id": "G", + "text": "➢ 产品以奶精勾兑的珍珠奶茶为主\n➢ 以街边小店或者档口店为主，品牌意识较低" + }, + { + "id": "H", + "text": "街头阶段\n（1995—2015年）" + }, + { + "id": "I", + "text": "➢ 产品以牛奶和茶叶冲泡的奶茶为主，部分品牌推出水果茶和气泡茶\n➢ 品牌开始公司化运作。门店以街边店为主，商场、写字楼等选址开始受到关注" + }, + { + "id": "J", + "text": "新式茶饮阶段\n（2016—2023年）" + }, + { + "id": "K", + "text": "➢ 产品种类丰富，有鲜果茶、乳茶、纯茶等\n➢ 品牌注重IP打造，产品研发能力、品牌知名度、门店标准化程度大幅提升" + }, + { + "id": "L", + "text": "健康原叶鲜奶阶段\n（2023年至今）" + }, + { + "id": "M", + "text": "➢ 产品种类更细分，食材原料更丰富，并强调真奶、真茶的健康属性\n➢ 品牌注重私域运营和数字化建设，并通过开放加盟、拓展海外市场等方式进一步攻占市场" + } + ], + "relationships": [ + { + "source": "A", + "target": "F" + }, + { + "source": "A", + "target": "H" + }, + { + "source": "A", + "target": "J" + }, + { + "source": "A", + "target": "L" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "F" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "H" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "D", + "target": "J" + }, + { + "source": "E", + "target": "L" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "H", + "target": "I" + }, + { + "source": "J", + "target": "K" + }, + { + "source": "L", + "target": "M" + } + ] + }, + { + "type": "text", + "text": "目前，现制茶饮和现磨咖啡是我国现制饮品市场的主要细分品类，其中以终端零售额计，现制茶饮是现制饮品市场中最大的细分品类，2023 年占现制饮品市场规模的约 50%，由 2018 年的 1085 亿元增加至 2023 年的 2585 亿元（人民币），预计到 2028 年将按照 17.3%的复合年增长率进一步增加至 5732 亿元。数据显示，截至 2023 年底，我国现制茶饮店总数已达约 46.4 万家，连锁现制茶饮店品牌数已达 2600 个。据测算 2024 年全国茶饮门店总数超过 66 万家$^{[1]}$，国民人均现制茶饮的年消费量预计从 2023 年的约 11 杯提升至 2028 年的约 26 杯，成为日常消费中重要的构成元素。" + }, + { + "type": "page_number", + "text": "1" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_36.json b/diagrams-and-tables/annotations/cn_diagram_36.json new file mode 100644 index 0000000000000000000000000000000000000000..5e0c56c223027580eb8f18ef8af362f074305fff --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_36.json @@ -0,0 +1,169 @@ +[ + { + "type": "header", + "text": "第一章 工业网络的愿景" + }, + { + "type": "title", + "text": "（一）工业网络的定义与范围" + }, + { + "type": "text", + "text": "工业网络指工业企业生产经营活动中所使用的网络，是构建工业环境人、机、物全面互联的基础设施。通过满足企业生产、办公、安防、数据中心和云平台等设备连接和数据互通的功能需求，工业网络可以实现工业研发、设计、生产、销售、管理、服务等要素的互联，促进各种工业数据的充分流动和无缝集成。" + }, + { + "type": "text", + "text": "工业网络由网络互联和数据互通两个层次组成$^{1}$。网络互联可实现要素间的泛在互联及数据传输；数据互通则通过数据和信息在各要素间、各系统间的无缝传递，使得异构系统在数据层面能相互“理解”，实现应用层面的互操作与信息集成。（图1-2：工业网络的范围）" + }, + { + "type": "diagram_caption", + "text": "图1-2：工业网络的范围" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "数据互通" + }, + { + "id": "B", + "text": "网络互联" + }, + { + "id": "C", + "text": "信息模型" + }, + { + "id": "D", + "text": "语义互操作" + }, + { + "id": "E", + "text": "应用层通信" + }, + { + "id": "F", + "text": "工厂外网" + }, + { + "id": "G", + "text": "工厂内网" + }, + { + "id": "H", + "text": "公网" + }, + { + "id": "I", + "text": "专网（物理隔离/虚拟）" + }, + { + "id": "J", + "text": "生产网络" + }, + { + "id": "K", + "text": "办公网络" + }, + { + "id": "L", + "text": "安防网络" + }, + { + "id": "M", + "text": "IT网" + }, + { + "id": "N", + "text": "OT网" + }, + { + "id": "O", + "text": "工厂级" + }, + { + "id": "P", + "text": "车间级" + }, + { + "id": "Q", + "text": "现场级" + } + ], + "relationships": [ + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "B", + "target": "F" + }, + { + "source": "B", + "target": "G" + }, + { + "source": "F", + "target": "H" + }, + { + "source": "F", + "target": "I" + }, + { + "source": "G", + "target": "J" + }, + { + "source": "G", + "target": "K" + }, + { + "source": "G", + "target": "L" + }, + { + "source": "J", + "target": "M" + }, + { + "source": "J", + "target": "N" + }, + { + "source": "M", + "target": "O" + }, + { + "source": "N", + "target": "P" + }, + { + "source": "N", + "target": "Q" + } + ] + }, + { + "type": "text", + "text": "网络互联方面，工业网络分为工厂内网和工厂外网，两者逻辑上相互隔离，通过网关、防火墙、网闸等方式连通。\n• 工厂内网包含生产网络、办公网络和安防网络等，用于生产要素互联以及企业IT管理系统间连接。其中，生产网络作为内网的核心构成部分，呈现出IT网络 (Information Technology, 信息技术) 和OT网络 (Operation Technology, 操作技术) 分层，工厂级、车间级和现场级分段的“两层三级”架构：IT网络主要由 IP 网络构成，服务于工厂级的通信；OT网络主要用于连接生产现场的控制器以及传感器、伺服器、监测设备等，服务于车间级、现场级的通信，对可靠性和确定性具有更高要求。\n• 工厂外网包含公网和专网，是以支撑工业企业全生命周期各项活动为目的，用于连接企业上下游、企业总部与分支机构、企业与云业务、企业与智能产品、企业与用户之间的网络$^{2}$。工厂外网通过各种形式的公网或专网实现互联，承担供应链上下游信息流动，数据跨园区、跨系统流动等功能。" + }, + { + "type": "footer", + "text": "1 根据工业互联网产业联盟《工业互联网网络连接白皮书（2.0版）》，工业互联网功能架构主要由网络互联、数据互通、标识解析三大模块组成。标识解析不属于本报告研究范畴\n2 工厂内网和工厂外网定义参考工业互联网产业联盟2018年9月发布的《工业互联网网络连接白皮书》和2021年9月发布的《工业互联网网络连接白皮书（2.0版）》" + }, + { + "type": "page_number", + "text": "15" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_37.json b/diagrams-and-tables/annotations/cn_diagram_37.json new file mode 100644 index 0000000000000000000000000000000000000000..a34aaadf131cd7ec4f268af77dde8758f57c7bed --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_37.json @@ -0,0 +1,149 @@ +[ + { + "type": "header", + "text": "迈向智能世界：工业网络全连接" + }, + { + "type": "text", + "text": "吞吐能力，让10Gbps 无处不在。SPE将从基于IEEE802.3cg的先进物理层技术APL演进到增强型EPL（Enhanced Physical Layer）。" + }, + { + "type": "title", + "text": "（三）发展建议" + }, + { + "type": "text", + "text": "固本强基，网络先行。在此，我们倡议广大工业企业从实际业务需求出发，以适度超前、经济适配作为大原则，在建网、用网、管网和护网的全生命周期环节进行积极应对和响应。" + }, + { + "type": "text", + "text": "• 适度超前：切忌短视、急于求成、过于追求短期回报，而是应该将网络作为面向长期的基础设施，为未来5-10年制造升级预留一定冗余空间；\n• 经济适配：无需盲目追求最佳性能参数，而是针对性选取最合适、经济好用的网络技术，实现投资回报最优。（图4-6：对工业企业的发展建议）" + }, + { + "type": "text", + "text": "建网方面，工业企业应站在全局视角，从顶层制定与业务活动相适配的网络规划，统筹考量IT与OT网，统一网络建设规范，打造面向未来、适度超前、IT与OT融合的“一体化”网络架构。" + }, + { + "type": "text", + "text": "• 确立IT与OT融合发展观念：夯实工业网络作为基础设施的地位，改变IT与OT割裂、“数字化是IT的事”等错误认知，建立IT和OT融合的全局观，凝练共识、拉齐行动，把握工业网络发展主动权；\n• 探索建立IT与OT融合团队：传统工业企业中，IT系统和OT系统由不同团队建设管理，IT部门只关注IT、业务部门只关注OT，导致系统间数据传递与价值挖掘的不顺畅。工业企业要坚定决心打通IT和OT间的“墙”，考虑成立IT-OT融合团队，建立扁平、灵活化的协同工作机制，凝聚共识、共同推动IT与OT融合的落地实践$^{[46]}$；" + }, + { + "type": "diagram_caption", + "text": "图4-6：对工业企业的发展建议" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "大原则" + }, + { + "id": "B", + "text": "关键行动方向" + }, + { + "id": "C", + "text": "适度超前" + }, + { + "id": "D", + "text": "经济适配" + }, + { + "id": "E", + "text": "建网" + }, + { + "id": "F", + "text": "联网" + }, + { + "id": "G", + "text": "用网" + }, + { + "id": "H", + "text": "护网" + }, + { + "id": "I", + "text": "建立IT和OT融合的全局观念，探索建立IT与OT的融合团队，凝练共识、拉齐行动
基于融合化的网络架构，探索一网多能、一网多用，推动多业务的共网融合承载，并以开放态度拥抱新技术" + }, + { + "id": "J", + "text": "存量工厂依据业务场景和约束条件，积极开展“哑设备”的联网化
改造新建工厂可考虑IP到终端（IP到底）的一步到位，优先使用开放、兼容的应用层协议，让设备统一语言，都说“普通话”" + }, + { + "id": "K", + "text": "观念上，明确“没有最好的技术，只有最合适的技术”，立足于场景需求，权衡技术性能和成本投入，追求最佳性价比
选配上，积极拥抱无线化趋势，探索极简灵活的网络，实现“化繁为简”" + }, + { + "id": "L", + "text": "探索网络数字孪生、网络数字地图等技术，实现网络的智能、自主，为网络的日常配置、调试、运维减负
构建“非侵入式”安全架构，将网络和安全视为互为依存的整体，构筑韧性保障" + } + ], + "relationships": [ + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "B", + "target": "I" + }, + { + "source": "B", + "target": "J" + }, + { + "source": "B", + "target": "K" + }, + { + "source": "B", + "target": "L" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "E", + "target": "I" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "F", + "target": "J" + }, + { + "source": "G", + "target": "H" + }, + { + "source": "G", + "target": "K" + }, + { + "source": "H", + "target": "L" + } + ] + }, + { + "type": "footer", + "text": "46 中国信通院在《5G 全连接工厂建设白皮书（2022 年）》中就曾提出“建议改变原有工厂内 IT-OT 系统应用建设运营方式，组织 IT-OT 融合团队，对 IT-OT 进行一体化部署......形成 IT-OT 应用的统筹建设、统一运维、统一管理，并促进形成工厂内同时要加快推进云网融合，实现网络资源、计算资源、平台资源等横向打通，提升工厂生产运营管理效率”；OPC基金会在《Extending OPC UA to the field: OPC UA for Field eXchange ( FX ) 》提出“IT/OT organizational convergence where the boundary between organizations blurs and management of IT and OT groups operate to common strategies and processes.”" + }, + { + "type": "page_number", + "text": "86" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_38.json b/diagrams-and-tables/annotations/cn_diagram_38.json new file mode 100644 index 0000000000000000000000000000000000000000..e384fc02cfb2fb11f1bc7ab8a3a0557ea0247a8a --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_38.json @@ -0,0 +1,105 @@ +[ + { + "type": "header", + "text": "openEuler 技术白皮书" + }, + { + "type": "title", + "text": "openEuler 覆盖全场景的创新平台" + }, + { + "type": "diagram_caption", + "text": "openEuler 场景拓展示意图" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "服务器" + }, + { + "id": "B", + "text": "服务器" + }, + { + "id": "C", + "text": "云计算" + }, + { + "id": "D", + "text": "边缘" + }, + { + "id": "E", + "text": "嵌入式" + }, + { + "id": "F", + "text": "基础公共服务" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "B", + "target": "F" + }, + { + "source": "C", + "target": "F" + }, + { + "source": "D", + "target": "F" + }, + { + "source": "E", + "target": "F" + } + ] + }, + { + "type": "text", + "text": "openEuler 已支持 X86、ARM、SW64、RISC-V、LoongArch 多处理器架构及 PowerPC 芯片架构，持续完善多样性算力生态体验。\nopenEuler 社区面向场景化的 SIG 不断组建，推动 openEuler 应用边界从最初的服务器场景，逐步拓展到云计算、边缘计算、嵌入式等更多场景。openEuler 正成为覆盖数字基础设施全场景的操作系统，新增发布面向边缘计算的版本 openEuler Edge、面向嵌入式的版本 openEuler Embedded。\nopenEuler 希望与广大生态伙伴、用户、开发者一起，通过联合创新、社区共建，不断增强场景化能力，最终实现统一操作系统支持多设备，应用一次开发覆盖全场景。" + }, + { + "type": "title", + "text": "openEuler 开放透明的开源软件供应链管理" + }, + { + "type": "text", + "text": "开源操作系统的构建过程，也是供应链聚合优化的过程。拥有可靠开源软件供应链，是大规模商用操作系统的基础。openEuler 从用户场景出发，回溯梳理相应的软件依赖关系，理清所有软件包的上游社区地址、源码和上游对应验证。完成构建验证、分发、实现生命周期管理。开源软件的构建、运行依赖关系、上游社区，三者之前形成闭环且完整透明的软件供应链管理。" + }, + { + "type": "title", + "text": "2. 平台架构" + }, + { + "type": "title", + "text": "系统框架" + }, + { + "type": "text", + "text": "openEuler 是覆盖全场景的创新平台，在引领内核创新，夯实云化基座的基础上，面向计算架构互联总线、存储介质发展新趋势，创新分布式、实时加速引擎和基础服务，结合边缘、嵌入式领域竞争力探索，打造全场景协同的面向数字基础设施的开源操作系统。" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_39.json b/diagrams-and-tables/annotations/cn_diagram_39.json new file mode 100644 index 0000000000000000000000000000000000000000..f3f239a190694757ca2aeb7283f6f9f6a3d1211f --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_39.json @@ -0,0 +1,229 @@ +[ + { + "type": "header", + "text": "openEuler 技术白皮书" + }, + { + "type": "title", + "text": "智能诊断" + }, + { + "type": "title", + "text": "功能描述" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "用户输入" + }, + { + "id": "B", + "text": "巡检本节点当前时间的健康状况" + }, + { + "id": "C", + "text": "异常事件1/异常事件2" + }, + { + "id": "D", + "text": "check.1/check.2/check.3" + }, + { + "id": "E", + "text": "EulerCopilot框架" + }, + { + "id": "F", + "text": "意图理解 -> 巡检" + }, + { + "id": "G", + "text": "异常事件列表" + }, + { + "id": "H", + "text": "意图理解 -> 定界" + }, + { + "id": "I", + "text": "异常事件根因指标TOP3" + }, + { + "id": "J", + "text": "意图理解 -> 定位" + }, + { + "id": "K", + "text": "Profiling定位结果报告" + }, + { + "id": "L", + "text": "巡检 Agent" + }, + { + "id": "M", + "text": "● 1、自动进行异常事件检测\n● 2、输出异常事件列表" + }, + { + "id": "N", + "text": "定界 Agent" + }, + { + "id": "O", + "text": "● 1、自动进行异常事件定界\n● 2、输出定界结果TOP3根因指标" + }, + { + "id": "P", + "text": "定位 Agent" + }, + { + "id": "Q", + "text": "● 1、自动进行profiling定位分析\n● 2、输出profiling结果" + }, + { + "id": "R", + "text": "智能体框架" + }, + { + "id": "S", + "text": "Agents" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "R" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "F" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "G" + }, + { + "source": "C", + "target": "H" + }, + { + "source": "D", + "target": "I" + }, + { + "source": "D", + "target": "J" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "E", + "target": "G" + }, + { + "source": "E", + "target": "H" + }, + { + "source": "E", + "target": "I" + }, + { + "source": "E", + "target": "J" + }, + { + "source": "E", + "target": "K" + }, + { + "source": "E", + "target": "R" + }, + { + "source": "F", + "target": "M" + }, + { + "source": "G", + "target": "M" + }, + { + "source": "H", + "target": "O" + }, + { + "source": "I", + "target": "O" + }, + { + "source": "J", + "target": "Q" + }, + { + "source": "K", + "target": "Q" + }, + { + "source": "L", + "target": "M" + }, + { + "source": "L", + "target": "S" + }, + { + "source": "N", + "target": "O" + }, + { + "source": "N", + "target": "S" + }, + { + "source": "P", + "target": "Q" + }, + { + "source": "P", + "target": "S" + } + ] + }, + { + "type": "text", + "text": "1. 巡检：调用 Inspection Agent，对指定 IP 进行异常事件检测，为用户提供包含异常容器 ID 以及异常指标（cpu、memory 等）的异常事件列表\n2. 定界：调用 Demarcation Agent，对巡检结果中指定异常事件进行定界分析，输出导致该异常事件的根因指标 TOP3\n3. 定位：调用 Detection Agent，对定界结果中指定根因指标进行 Profiling 定位分析，为用户提供该根因指标异常的热点堆栈、热点系统时间、热点性能指标等信息" + }, + { + "type": "title", + "text": "应用场景" + }, + { + "type": "text", + "text": "智能诊断接口在本次 openEuler 24.03 LTS SP1 版本的功能范围是：具备单机异常事件检测 + 定界 + profiling 定位的能力。" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_40.json b/diagrams-and-tables/annotations/cn_diagram_40.json new file mode 100644 index 0000000000000000000000000000000000000000..a32acb9ef8935ee6ac5f91136aa5cd3f07820a31 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_40.json @@ -0,0 +1,132 @@ +[ + { + "type": "header", + "text": "openEuler 技术白皮书" + }, + { + "type": "title", + "text": "应用场景" + }, + { + "type": "text", + "text": "主版本场景：正常编译使用系统默认的 gcc-12.3.1。\n副版本场景：需要使用 GCC 14 高版本特性构建相关应用，使用 SCL 工具将构建环境切换为 gcc-toolset-14 编译工具链的编译环境。" + }, + { + "type": "diagram_caption", + "text": "GCC 主副版本切换示意图" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "用户" + }, + { + "id": "B", + "text": "默认使用" + }, + { + "id": "C", + "text": "系统默认GCC" + }, + { + "id": "D", + "text": "副版本GCC调用" + }, + { + "id": "E", + "text": "使用脚本切换副版本GCC" + }, + { + "id": "F", + "text": "设置环境变量" + }, + { + "id": "G", + "text": "副版本GCC" + }, + { + "id": "H", + "text": "使用scl工具切换GCC并激活运行环境" + }, + { + "id": "I", + "text": "新建bash shell并使能副版本路径" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "H" + }, + { + "source": "B", + "target": "C", + "label": "/usr/bin/gcc" + }, + { + "source": "C", + "target": "G" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "D", + "target": "F" + }, + { + "source": "D", + "target": "G" + }, + { + "source": "D", + "target": "H" + }, + { + "source": "D", + "target": "I" + }, + { + "source": "E", + "target": "F", + "label": "/opt/openEuler/gcc-toolset-X/root/usr/bin" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "G", + "target": "I" + }, + { + "source": "H", + "target": "I", + "label": "scl enable gcc-toolset-X bash" + } + ] + }, + { + "type": "title", + "text": "5. 内核创新" + }, + { + "type": "title", + "text": "openEuler 内核中的新特性" + }, + { + "type": "text", + "text": "openEuler 24.03 LTS SP1 基于 Linux Kernel 6.6 内核构建，在此基础上，同时吸收了社区高版本的有益特性及社区创新特性。\n● 内存管理 folio 特性：Linux 内存管理基于 page（页）转换到由 folio（拉丁语 folio，对开本）进行管理，相比 page，folio 可以由一个或多个 page 组成，采用 struct folio 参数的函数声明它将对整个（1 个或者多个）页面进行操作，而不仅仅是 PAGE_SIZE 字节，从而移除不必要复合页转换，降低误用 tail page 问题；从内存管理效率上采用 folio 减少 LRU 链表数量，提升内存回收效率。另一方，一次分配更多连续内存减少 page fault 次数，一定程度降低内存碎片化；而在 IO 方面，可以加速大 IO 的读写效率，提升吞吐。全量支持匿名页、文件页的 large folio，提供系统级别的开关控制，业务可以按需使用。对于 ARM64 架构，基于硬件 contiguous bit 技术（16 个连续 PTE 只占一个 TLB entry），可以进一步降低系统 TLB miss，从而提升整体系统性能。24.03 LTS SP1 版本新增支持 anonymous shmem 分配 mTHP 与支持 mTHP 的 lazyfree，进一步增加内存" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_41.json b/diagrams-and-tables/annotations/cn_diagram_41.json new file mode 100644 index 0000000000000000000000000000000000000000..06b2a40cadcc2778a328b97f8774e954b9686828 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_41.json @@ -0,0 +1,82 @@ +[ + { + "type": "header", + "text": "openEuler 技术白皮书" + }, + { + "type": "text", + "text": "因此本特性旨在对现有 IMA 机制进行增强，有效提升对解释器类应用程序的完整性保护能力。" + }, + { + "type": "title", + "text": "功能描述" + }, + { + "type": "text", + "text": "本需求的核心功能是，对OS现有权限机制进行扩展，保证通过exec运行的程序（如./test.sh）和通过解释器间接运行的程序（bash ./test.sh）具备相同的权限检查流程。具体方案如下：\n➢ openEuler 24.03 LTS SP1版本针对execveat系统调用新增AT_CHECK参数的支持，实现对文件进行可执行权限检查并返回结果，而不真正地执行该文件；\n➢ 针对bash、jdk等组件进行功能扩展，调用execveat+CHECK对待运行的脚本文件或java文件进行可执行权限检查，只有当检查成功后，才可继续运行程序。\n该特性与IMA机制相结合，即可实现如下图所示的解释器类应用程序完整性保护方案。由解释器调用execveat触发对脚本程序的可执行权限检查，并间接触发IMA的exec检查策略，在有效实现脚本程序完整性保护的同时，避免开启IMA read检查策略导致的保护范围扩大化风险。" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "脚本文件" + }, + { + "id": "B", + "text": "IMA摘要列表" + }, + { + "id": "C", + "text": "解释器\n(bash/python/java/...)" + }, + { + "id": "D", + "text": "openEuler IMA子系统" + }, + { + "id": "E", + "text": "进程 (脚本程序)" + } + ], + "relationships": [ + { + "source": "A", + "target": "B", + "label": "预先生成" + }, + { + "source": "A", + "target": "C", + "label": "① 打开文件" + }, + { + "source": "B", + "target": "D", + "label": "部署阶段导入" + }, + { + "source": "C", + "target": "D", + "label": "② 查询完整性\n③ 返回校验结果" + }, + { + "source": "C", + "target": "E", + "label": "④ 解释执行" + } + ] + }, + { + "type": "text", + "text": "同时其他社区开发人员或用户可基于该特性，自行扩展其他解释器或类似机制的支持。" + }, + { + "type": "title", + "text": "应用场景" + }, + { + "type": "text", + "text": "在高安全要求的场景，用户可基于该特性实现“应用程序白名单”功能，即只允许通过 IMA 度量或校验的二进制程序或脚本程序才可在系统中运行。" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_42.json b/diagrams-and-tables/annotations/cn_diagram_42.json new file mode 100644 index 0000000000000000000000000000000000000000..195e4c224b6c9940ff6b6977dedb31504d410ec5 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_42.json @@ -0,0 +1,95 @@ +[ + { + "type": "header", + "text": "openEuler 技术白皮书" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "IMA" + }, + { + "id": "B", + "text": "DIM" + }, + { + "id": "C", + "text": "..." + }, + { + "id": "D", + "text": "可信根框架" + }, + { + "id": "E", + "text": "TPM" + }, + { + "id": "F", + "text": "virtCCA" + }, + { + "id": "G", + "text": "..." + } + ], + "relationships": [ + { + "source": "A", + "target": "D", + "label": "统一度量接口" + }, + { + "source": "B", + "target": "D", + "label": "统一度量接口" + }, + { + "source": "C", + "target": "D", + "label": "统一度量接口" + }, + { + "source": "D", + "target": "E", + "label": "各类驱动程序" + }, + { + "source": "D", + "target": "F", + "label": "各类驱动程序" + }, + { + "source": "D", + "target": "G", + "label": "各类驱动程序" + } + ] + }, + { + "type": "title", + "text": "应用场景" + }, + { + "type": "text", + "text": "当前该框架已实现对于 TPM 和 virtCCA 可信根的支持，用户可在支持 TPM 和 virtCCA 的环境中使能 IMA 特性，并通过可信根证明 IMA 度量结果的完整性。同时其他社区开发人员或硬件厂商可基于该特性，自行扩展完整性度量特性和硬件的支持。" + }, + { + "type": "title", + "text": "secGear 特性增强" + }, + { + "type": "text", + "text": "secGear 远程证明统一框架是机密计算远程证明相关的关键组件，屏蔽不同 TEE 远程证明差异，提供 Attestation Agent 和 Attestation Service 两个组件，Agent 供用户集成获取证明报告，对接证明服务；Service 可独立部署，支持 iTrustee、virtCCA 远程证明报告的验证。" + }, + { + "type": "title", + "text": "功能描述" + }, + { + "type": "text", + "text": "远程证明统一框架聚焦机密计算相关功能，部署服务时需要的服务运维等相关能力由服务部署第三方提供。远程证明统一框架的关键技术如下：" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_43.json b/diagrams-and-tables/annotations/cn_diagram_43.json new file mode 100644 index 0000000000000000000000000000000000000000..28bcd9d085ad610045a01b41836aeb5b78d68ef1 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_43.json @@ -0,0 +1,121 @@ +[ + { + "type": "header", + "text": "openEuler 技术白皮书" + }, + { + "type": "title", + "text": "功能描述" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "authHub" + }, + { + "id": "B", + "text": "用户管理" + }, + { + "id": "C", + "text": "应用注册" + }, + { + "id": "D", + "text": "应用属性设置" + }, + { + "id": "E", + "text": "用户鉴权" + }, + { + "id": "F", + "text": "单点登录登出" + }, + { + "id": "G", + "text": "用户管理" + }, + { + "id": "H", + "text": "功能应用" + }, + { + "id": "I", + "text": "主机服务" + }, + { + "id": "J", + "text": "漏洞巡检" + }, + { + "id": "K", + "text": "配置溯源" + }, + { + "id": "L", + "text": "第三方集成应用" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "H" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "E", + "target": "G" + }, + { + "source": "H", + "target": "I" + }, + { + "source": "H", + "target": "J" + }, + { + "source": "H", + "target": "K" + }, + { + "source": "H", + "target": "L" + } + ] + }, + { + "type": "text", + "text": "authHub 基于 oauth2 协议，实现统一用户鉴权中心，用户鉴权中心功能包括：\n● 应用管理：应用部署后需要在 authHub 应用管理界面进行注册和配置，用户可以使用注册的应用的功能。\n● 用户鉴权：在 authHub 管理的应用中，用户可以实现单点登录和单点登出。" + }, + { + "type": "title", + "text": "应用场景" + }, + { + "type": "text", + "text": "Aops 适配 authHub 统一用户鉴权，支持第三方应用现有的鉴权对接 authHub，提升应用的可拓展性；不同应用间的鉴权通过 authHub 统一管理，管理服务的访问权限。" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_44.json b/diagrams-and-tables/annotations/cn_diagram_44.json new file mode 100644 index 0000000000000000000000000000000000000000..67dadfb112d36e9152765c4783d9aab53558343e --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_44.json @@ -0,0 +1,269 @@ +[ + { + "type": "header", + "text": "openEuler 技术白皮书" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Normal World" + }, + { + "id": "B", + "text": "Host OS" + }, + { + "id": "C", + "text": "libvirt" + }, + { + "id": "D", + "text": "qemu" + }, + { + "id": "E", + "text": "SMMU driver" + }, + { + "id": "F", + "text": "KVM" + }, + { + "id": "G", + "text": "开源修改组件" + }, + { + "id": "H", + "text": "底层固件" + }, + { + "id": "I", + "text": "virtCCA组件" + }, + { + "id": "J", + "text": "Secure World" + }, + { + "id": "K", + "text": "cVM0" + }, + { + "id": "L", + "text": "用户态" + }, + { + "id": "M", + "text": "OpenSSL" + }, + { + "id": "N", + "text": "KAE引擎" + }, + { + "id": "O", + "text": "UADK" + }, + { + "id": "P", + "text": "内核态" + }, + { + "id": "Q", + "text": "uacce" + }, + { + "id": "R", + "text": "ACC VF驱动" + }, + { + "id": "S", + "text": "cVM1" + }, + { + "id": "T", + "text": "用户态" + }, + { + "id": "U", + "text": "OpenSSL" + }, + { + "id": "V", + "text": "KAE引擎" + }, + { + "id": "W", + "text": "UADK" + }, + { + "id": "X", + "text": "内核态" + }, + { + "id": "Y", + "text": "uacce" + }, + { + "id": "Z", + "text": "ACC VF驱动" + }, + { + "id": "AA", + "text": "DA Module" + }, + { + "id": "AB", + "text": "tmm" + }, + { + "id": "AC", + "text": "ACC PF驱动" + }, + { + "id": "AD", + "text": "S-EL2" + }, + { + "id": "AE", + "text": "KAE Device(SEC/HPRE)" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "G" + }, + { + "source": "A", + "target": "H" + }, + { + "source": "A", + "target": "I" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "B", + "target": "F" + }, + { + "source": "J", + "target": "K" + }, + { + "source": "J", + "target": "S" + }, + { + "source": "J", + "target": "AB" + }, + { + "source": "J", + "target": "AE" + }, + { + "source": "K", + "target": "L" + }, + { + "source": "K", + "target": "P" + }, + { + "source": "L", + "target": "M" + }, + { + "source": "L", + "target": "N" + }, + { + "source": "L", + "target": "O" + }, + { + "source": "P", + "target": "Q" + }, + { + "source": "P", + "target": "R" + }, + { + "source": "S", + "target": "T" + }, + { + "source": "S", + "target": "X" + }, + { + "source": "T", + "target": "U" + }, + { + "source": "T", + "target": "V" + }, + { + "source": "T", + "target": "W" + }, + { + "source": "X", + "target": "Y" + }, + { + "source": "X", + "target": "Z" + }, + { + "source": "AA", + "target": "AB" + }, + { + "source": "AB", + "target": "AC" + }, + { + "source": "AB", + "target": "AD" + } + ] + }, + { + "type": "title", + "text": "应用场景" + }, + { + "type": "text", + "text": "面向密态数据库、安全云主机、机密多方计算、数据可信流通以及 AI 模型数据保护。" + }, + { + "type": "title", + "text": "海光 CSV3 支持" + }, + { + "type": "text", + "text": "海光第三代安全虚拟化技术(CSV3)在前二代技术的基础上继续增强，在CPU内部实现了虚拟机数据的安全隔离，禁止主机操作系统读写CSV3虚拟机内存，禁止主机操作系统读写虚拟机嵌套页表，保证了虚拟机数据的完整性，实现了CSV3虚拟机数据机密性和完整性的双重安全。" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_45.json b/diagrams-and-tables/annotations/cn_diagram_45.json new file mode 100644 index 0000000000000000000000000000000000000000..d5bd4828e11b3f0d2158ab785cb6a3d5e4ea7e34 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_45.json @@ -0,0 +1,301 @@ +[ + { + "type": "header", + "text": "openEuler 技术白皮书" + }, + { + "type": "text", + "text": "在政府机构、AI、医疗、金融、多方计算等异构加速场景中，为数据安全保驾护航。" + }, + { + "type": "title", + "text": "密码套件 openHiTLS" + }, + { + "type": "text", + "text": "openHiTLS 旨在通过提供轻量化、可裁剪的软件技术架构及丰富的国际主流及中国商用密码算法、协议，满足云计算、大数据、AI、金融等多样化行业的安全需求。它具备算法先进、性能卓越、安全可靠、开放架构及多语言平滑兼容等特点，为开发者提供了一套安全、可扩展的密码解决方案。通过社区共建与生态建设，openHiTLS 推动密码安全标准在各行各业的加速落地，同时构建以 openEuler 为核心的安全开源生态，为用户带来更加安全、可靠的数字环境。" + }, + { + "type": "diagram_caption", + "text": "openHiTLS 架构图" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "算法、协议、证书命令行工具" + }, + { + "id": "B", + "text": "统一接口层" + }, + { + "id": "C", + "text": "openHiTLS原生接口" + }, + { + "id": "D", + "text": "基础安全协议" + }, + { + "id": "E", + "text": "TLS1.X" + }, + { + "id": "F", + "text": "DTLS" + }, + { + "id": "G", + "text": "TLCP" + }, + { + "id": "H", + "text": "RFC8998" + }, + { + "id": "I", + "text": "......" + }, + { + "id": "J", + "text": "数字证书基础" + }, + { + "id": "K", + "text": "ASN.1" + }, + { + "id": "L", + "text": "PKCS10/12" + }, + { + "id": "M", + "text": "X509" + }, + { + "id": "N", + "text": "......" + }, + { + "id": "O", + "text": "密码算法" + }, + { + "id": "P", + "text": "国际算法" + }, + { + "id": "Q", + "text": "AES" + }, + { + "id": "R", + "text": "CHACHA20" + }, + { + "id": "S", + "text": "DSA" + }, + { + "id": "T", + "text": "SHA3" + }, + { + "id": "U", + "text": "SHA2" + }, + { + "id": "V", + "text": "(EC) DH" + }, + { + "id": "W", + "text": "RSA" + }, + { + "id": "X", + "text": "ECC" + }, + { + "id": "Y", + "text": "ECDSA" + }, + { + "id": "Z", + "text": "Curve25519" + }, + { + "id": "AA", + "text": "PBKDF2" + }, + { + "id": "AB", + "text": "......" + }, + { + "id": "AC", + "text": "国密算法" + }, + { + "id": "AD", + "text": "SM2" + }, + { + "id": "AE", + "text": "SM3" + }, + { + "id": "AF", + "text": "SM4" + }, + { + "id": "AG", + "text": "..." + }, + { + "id": "AH", + "text": "随机数发生器" + }, + { + "id": "AI", + "text": "DRBG-CTR/HASH/HMAC" + } + ], + "relationships": [ + { + "source": "B", + "target": "C" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "D", + "target": "F" + }, + { + "source": "D", + "target": "G" + }, + { + "source": "D", + "target": "H" + }, + { + "source": "D", + "target": "I" + }, + { + "source": "J", + "target": "K" + }, + { + "source": "J", + "target": "L" + }, + { + "source": "J", + "target": "M" + }, + { + "source": "J", + "target": "N" + }, + { + "source": "O", + "target": "P" + }, + { + "source": "O", + "target": "AC" + }, + { + "source": "O", + "target": "AH" + }, + { + "source": "P", + "target": "Q" + }, + { + "source": "P", + "target": "R" + }, + { + "source": "P", + "target": "S" + }, + { + "source": "P", + "target": "T" + }, + { + "source": "P", + "target": "U" + }, + { + "source": "P", + "target": "V" + }, + { + "source": "P", + "target": "W" + }, + { + "source": "P", + "target": "X" + }, + { + "source": "P", + "target": "Y" + }, + { + "source": "P", + "target": "Z" + }, + { + "source": "P", + "target": "AA" + }, + { + "source": "P", + "target": "AB" + }, + { + "source": "AC", + "target": "AD" + }, + { + "source": "AC", + "target": "AE" + }, + { + "source": "AC", + "target": "AF" + }, + { + "source": "AC", + "target": "AG" + }, + { + "source": "AH", + "target": "AI" + } + ] + }, + { + "type": "title", + "text": "功能描述" + }, + { + "type": "title", + "text": "支持主流的密码协议和算法" + }, + { + "type": "text", + "text": "支持国际主流及中国商用密码算法和协议，可根据场景需求选择合适的密码算法和协议。" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_46.json b/diagrams-and-tables/annotations/cn_diagram_46.json new file mode 100644 index 0000000000000000000000000000000000000000..dac47cdd36cfcb9f6be37bd724365ff84356fa9d --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_46.json @@ -0,0 +1,105 @@ +[ + { + "type": "header", + "text": "openEuler 技术白皮书" + }, + { + "type": "text", + "text": "AI4C 的自动调优基于 OpenTuner (2015 Ansel et al.) 开发，通过插件驱动编译器采集优化特性相关参数信息，通过搜索算法调整关键决策参数（例如循环展开系数），通过插件注入编译过程修改决策，运行编译输出二进制获得反馈因子，迭代自动调优。" + }, + { + "type": "text", + "text": "● 已集成一系列搜索算法，动态选择算法并共享搜索进；\n● 支持用户配置 yaml 自定义搜索空间和扩展底层搜索算法；\n● 支持细粒度代码块调优与粗粒度编译选项自动调优；\n● 在 cormark、dhrystone、Cbench 等 benchmark 上获得 3%~5% 不等的收益。" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Source Code" + }, + { + "id": "B", + "text": "Compiler" + }, + { + "id": "C", + "text": "Applying Tuning Config" + }, + { + "id": "D", + "text": "Recording Tuning Opportunity" + }, + { + "id": "E", + "text": "Auto-Tuner" + }, + { + "id": "F", + "text": "Search Driver" + }, + { + "id": "G", + "text": "Profiler" + }, + { + "id": "H", + "text": "Tuning Opportunities" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "B", + "target": "E", + "label": "yaml" + }, + { + "source": "B", + "target": "G", + "label": "Binary" + }, + { + "source": "C", + "target": "H" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "F", + "target": "G", + "label": "feedback" + }, + { + "source": "F", + "target": "H", + "label": "yaml" + } + ] + }, + { + "type": "title", + "text": "● AI 辅助编译优化（ACPO）" + }, + { + "type": "text", + "text": "ACPO 提供全面的工具、库、算法，为编译器工程师提供简单易用的接口使用 AI 模型能力，替代或增强编译器中启发式优化决策算法。在编译器优化过程中，使用插件提取优化遍的输入结构化数据作为模型输入特征，getAdvice 运行预训练模型获得决策系数，编译器使用模型决策结果替代部分启发式决策，获得更好的性能。" + }, + { + "type": "text", + "text": "■ 解耦编译器与 AI 模型和推理引擎，帮助算法开发者专注 AI 算法模型开发，简化模型应用成本，同时兼容多个编译器、模型、AI 推理框架等主流产品，提供 AI 模型的热更新能力；\n■ 实践落地 IPA Function Inline、RTL Loop Unroll 等不同优化阶段和优化过程，获得相对显著的收益。" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_47.json b/diagrams-and-tables/annotations/cn_diagram_47.json new file mode 100644 index 0000000000000000000000000000000000000000..e15c04a23dfb09ce9c13bb7dd7b72fd5b7f398e7 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_47.json @@ -0,0 +1,204 @@ +[ + { + "type": "header", + "text": "openEuler 技术白皮书" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Program" + }, + { + "id": "B", + "text": "Opt Passes" + }, + { + "id": "C", + "text": "InlinerPass" + }, + { + "id": "D", + "text": "FIModel::clearCache()" + }, + { + "id": "E", + "text": "CollectFeatures\nclearFunctionLevel()" + }, + { + "id": "F", + "text": "ModelDataFICollector\n(load ModelFile)" + }, + { + "id": "G", + "text": "getAdvice" + }, + { + "id": "H", + "text": "FIModel::invalidateCache()" + }, + { + "id": "I", + "text": "Opt Passes" + }, + { + "id": "J", + "text": "Executable" + }, + { + "id": "K", + "text": "getAdvice" + }, + { + "id": "L", + "text": "MDC->collectFeatures" + }, + { + "id": "M", + "text": "FI->setMLCustomFeatures" + }, + { + "id": "N", + "text": "FI->getAdvice" + }, + { + "id": "O", + "text": "ShouldInline" + }, + { + "id": "P", + "text": "trained ML model" + }, + { + "id": "Q", + "text": "TF AOT Model" + }, + { + "id": "R", + "text": "AOTModelRunner" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "C", + "target": "F" + }, + { + "source": "C", + "target": "G" + }, + { + "source": "C", + "target": "H" + }, + { + "source": "C", + "target": "I" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "G", + "target": "K", + "label": "Plugin" + }, + { + "source": "H", + "target": "O", + "label": "Plugin" + }, + { + "source": "I", + "target": "J" + }, + { + "source": "K", + "target": "L" + }, + { + "source": "K", + "target": "M" + }, + { + "source": "K", + "target": "N" + }, + { + "source": "K", + "target": "O" + }, + { + "source": "L", + "target": "M" + }, + { + "source": "M", + "target": "N" + }, + { + "source": "N", + "target": "O" + }, + { + "source": "N", + "target": "R" + }, + { + "source": "P", + "target": "Q", + "label": "aot_compile_tf_model.py" + }, + { + "source": "Q", + "target": "R" + } + ] + }, + { + "type": "title", + "text": "应用场景" + }, + { + "type": "text", + "text": "AI4C 提供优化模型和调优插件实现不同应用的编译优化，支持开发者根据不同应用的性能瓶颈开发相应的优化模型，使用 AI4C 框架能力注入编译过程，实现性能提升，当前 AI4C 主要应用于数据库等互联网后端领域。" + }, + { + "type": "text", + "text": "● RocksDB\n● MySQL\n● Doris\n● Nginx\n● Python\n● ..." + }, + { + "type": "title", + "text": "RPM 国密签名支持" + }, + { + "type": "text", + "text": "根据国内相关安全技术标准，在某些应用场景中需要采用国密算法实现对重要可执行程序来源的真实性和完整性保护。openEuler 当前采用 RPM 格式的软件包管理，软件包签名算法基于 openPGP 签名规范。openEuler 24.03 LTS SP1 版本基于 RPM 包管理机制扩展对于 SM2 签名算法和 SM3 摘要算法的支持。" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_48.json b/diagrams-and-tables/annotations/cn_diagram_48.json new file mode 100644 index 0000000000000000000000000000000000000000..51913e57100bab167b2248f6b3745cdf6723e10b --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_48.json @@ -0,0 +1,111 @@ +[ + { + "type": "header", + "text": "openEuler 技术白皮书" + }, + { + "type": "title", + "text": "功能描述" + }, + { + "type": "text", + "text": "本特性主要基于 RPM 组件以及其调用的 GnuPG2 签名工具，在现有 openPGP 签名体系的基础上，进行国密算法使能。特性涉及的软件包如下：" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "RPM" + }, + { + "id": "B", + "text": "rpmsign" + }, + { + "id": "C", + "text": "rpmkeys" + }, + { + "id": "D", + "text": "rpm" + }, + { + "id": "E", + "text": "GnuPG" + }, + { + "id": "F", + "text": "gpg" + }, + { + "id": "G", + "text": "openSSL" + }, + { + "id": "H", + "text": "libcrypto" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E", + "label": "签名生成" + }, + { + "source": "A", + "target": "G", + "label": "签名验证" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "G", + "target": "H" + } + ] + }, + { + "type": "text", + "text": "在 RPM 软件包签名场景，用户可调用 gpg 命令生成 SM2 签名私钥和证书，并调用 rpmsign 命令为指定的 RPM 包添加基于 SM2+SM3 算法的数字签名。\n在 RPM 软件包验签场景，用户可调用 rpm 命令导入验签证书，并通过校验 RPM 包的数字签名信息从而验证软件包的真实性和完整性。" + }, + { + "type": "title", + "text": "应用场景" + }, + { + "type": "text", + "text": "用户可基于本特性提供的软件包国密签名/验签技术，构建基于国密算法的软件包验证能力，满足国内部分合规场景中的密码应用安全要求。" + }, + { + "type": "title", + "text": "oneAPI 框架支持" + }, + { + "type": "text", + "text": "Unified Acceleration Foundation (UXL) 正在推动构建开放的异构加速软件框架的标准化。其中oneAPI作为初始项目的目标是提供一种跨行业、开放、基于标准的统一编程模型，并为异构加速器（如 CPU、GPU、FPGA 和专用加速器）提供统一的开发体验。oneAPI 规范扩展了现有的开发者编程模型，通过并行编程语言 (Data Parallel C++) 或者一组加速软件库以及底层的硬件抽象接口 (Level Zero) 来支持跨架构的编程，从而支持多种加速硬件和处理器平台。为了提供兼容性并提高开发效率，oneAPI 规范基于行业标准，提供了多种开放的、跨平台和易用的开发者软件套件。" + }, + { + "type": "title", + "text": "功能描述" + }, + { + "type": "text", + "text": "为了在 openEuler 上完整的支持 oneAPI，我们从 openEuler 24.03 LTS 开始分别集成了" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_49.json b/diagrams-and-tables/annotations/cn_diagram_49.json new file mode 100644 index 0000000000000000000000000000000000000000..6dc169789ec1180226d076bd3793f81194b3f191 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_49.json @@ -0,0 +1,69 @@ +[ + { + "type": "text", + "text": "因此，从移动智能终端安全实践来看，MCP、A2A、ANP 协议在身份认证设计、身份认证协议在终端场景下的适配、及授权机制三个维度仍有一定的完善空间。这些协议短板将直接影响移动智能终端场景下的 Agent 业务的安全程度，形成潜在的安全风险，例如：" + }, + { + "type": "text", + "text": "○ 在终端内 Agent 协作场景下，身份认证适配不足可能引发身份仿冒风险、恶意 Agent 参与数据传输可能造成敏感数据篡改或数据泄露；" + }, + { + "type": "text", + "text": "○ 当 Agent 调用终端工具与资源时，因缺乏针对性的身份认证方案，理论上存在非法 Agent 伪装系统组件的可能，进而威胁用户数据安全与设备稳定运行。" + }, + { + "type": "text", + "text": "综上，为了加强移动智能终端上的 Agent 业务安全，需要从 Agent 身份校验和数据保护的思路出发，建设 Agent 可信身份基础设施。结合手机终端业务需求，可从三方面进行考虑，如图 5 所示。" + }, + { + "type": "diagram_caption", + "text": "图 5 Agent 可信身份基础设施建设角度" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Agent可信身份基础设施" + }, + { + "id": "B", + "text": "身份防仿冒" + }, + { + "id": "C", + "text": "数据防泄露" + }, + { + "id": "D", + "text": "数据防篡改" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + } + ] + }, + { + "type": "text", + "text": "如图 6 所示，在 Agent 可信身份基础设施的身份防仿冒环节，核心是依托合规有效的数字证书对 Agent 可信身份进行全流程的注册与校验：注册阶段需将 Agent 的唯一身份标识、属性信息与数字证书进行绑定，确保身份信息的真实性与合规性；校验阶段则通过验证证书的有效期、颁发机构合法性、证书签名完整性等信息，核对 Agent 当前提交的身份信息与注册时绑定的身份信息是否一致，最终确认 Agent 身份的可信性，为后续的数据交互环节筑牢身份信任基础。" + }, + { + "type": "text", + "text": "而针对数据防泄露与数据防篡改需求，其实施前提是 Agent 已通过前述的身份认证流程 —— 在确认 Agent 身份可信后，将采用安全强度符合行业规范与业务需求的密码算法套件（如包含对称加密算法、非对称加密算法、哈希算法的完整套件），对 Agent 与 Agent 之间、Agent 与工具或功能模块之间的全链路传输数据进行双重安全处理：一方面通过数据加密操作，将敏感传输数据转化为不可直接解读的密文，防止数据在传输过程中被未授权主体窃取、窥探，保障数据的机密性；另一方面通过数据签名操作，利用 Agent 的专属密钥" + }, + { + "type": "page_number", + "text": "18" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_diagram_50.json b/diagrams-and-tables/annotations/cn_diagram_50.json new file mode 100644 index 0000000000000000000000000000000000000000..75d580ac2ac1dd01ccdab584fcdf76c135478c4b --- /dev/null +++ b/diagrams-and-tables/annotations/cn_diagram_50.json @@ -0,0 +1,85 @@ +[ + { + "type": "header", + "text": "移动 Agent 安全技术白皮书" + }, + { + "type": "text", + "text": "对传输数据的哈希值进行签名，接收方通过验签可确认数据在传输过程中是否被篡改、替换或破坏，从而保障敏感数据的完整性，确保数据从发送端到接收端的一致性与可靠性。" + }, + { + "type": "diagram_caption", + "text": "图 6 Agent 可信身份基础设施思路和措施" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "身份防仿冒" + }, + { + "id": "B", + "text": "基于证书的Agent身份校验" + }, + { + "id": "C", + "text": "数据防泄露" + }, + { + "id": "D", + "text": "身份认证前提下的数据加密" + }, + { + "id": "E", + "text": "数据防篡改" + }, + { + "id": "F", + "text": "身份认证前提下的数据签名" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "E", + "target": "F" + } + ] + }, + { + "type": "text", + "text": "通过上述优化思路的落地，搭建可靠的 Agent 可信身份基础设施，既能广泛兼容多种异构智能体通信协议，又依托灵活架构具备协议扩展能力，破除不同类型终端 Agent 间的通信适配壁垒，为多场景交互奠定基础；在筑牢通信基础的同时，还会为终端智能体分配唯一身份标识，并搭配端到端全链路加密机制，实现从身份确认到数据传输的全链路可信，进一步强化现有协议在终端场景下的身份鉴权能力。在此过程中，基础设施严格遵循最小化信息披露原则，仅采集、传输业务必需信息，避免冗余数据暴露，切实保障用户隐私与数据安全；同时通过跨域的身份流转和数据全生命周期保护，实现 Agent 行为的透明可追溯。最终，这一系列作用将形成从身份验证到权限管控的完整安全链条，为终端 Agent 生态的健康发展提供有力支撑。" + }, + { + "type": "title", + "text": "3.4 Agent 细粒度权限管理" + }, + { + "type": "title", + "text": "3.4.1 Agent 行为分级" + }, + { + "type": "text", + "text": "随着大模型智能体（AI Agent）技术的快速迭代，其在终端侧承担的任务能力越来越复杂，涉及跨应用操作、系统功能控制等多种行为。这种高度自动化、可组合、可自主规划的能力极大提升了智能体的可用性，但同时也让能力边界与行为安全变得愈发模糊。" + }, + { + "type": "title", + "text": "3.4.1.1 Agent 行为能力分类" + }, + { + "type": "text", + "text": "○ 感知能力：指 Agent 对系统状态（如 UI 结构、网络情况、传感器状态）的感知能力，为后续行为提供上下文支撑。\n○ 决策能力：指 Agent 根据感知输入、用户目标以及对话历史进行自主规划和多轮推理，决定下一步行动的能力。\n○ 记忆能力：指 Agent 在任务执行或对话中对用户信息、操作上下文等进行短期或长" + }, + { + "type": "page_number", + "text": "19" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_01.json b/diagrams-and-tables/annotations/cn_nested_table_01.json new file mode 100644 index 0000000000000000000000000000000000000000..db2013243b6c6976b8c7cda2efa955b1cb90fa8c --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_01.json @@ -0,0 +1,26 @@ +[ + { + "type": "title", + "text": "第三章 定标信息" + }, + { + "type": "text", + "text": "定标方法：综合评分法" + }, + { + "type": "text", + "text": "综合评分法，是指投标文件满足招标文件全部实质性要求，且按照评审因素的量化指标评审得分最高的投标单位为中标候选人的评标方法。" + }, + { + "type": "text", + "text": "价格分计算方法：采用低价优先法计算，即满足招标文件要求且投标价格最低的投标报价为评标基准价，其价格分为满分。其他投标单位的价格分统一按照下列公式计算：\n投标报价得分=(评标基准价 / 投标报价) × 100\n评标总得分=F1×A1+F2×A2+……+Fn×An\nF1、F2……Fn 分别为各项评审因素的得分；\nA1、A2、……An 分别为各项评审因素所占的权重(A1+A2+……+An=1)。\n评标过程中，不得去掉报价中的最高报价和最低报价。" + }, + { + "type": "table", + "html": "
序号评分项权重
1价格20
采用低价优先法计算，即满足招标文件要求且投标价格最低的投标报价（综合单价）为评标基准价，其价格分为满分。其他投标人的价格分统一按照下列公式计算：
投标报价（综合单价）得分=(评标基准价 / 投标报价) × 权重
2技术32
行号内容权重评分准则
1服务方案10
序号详情
1考察投标人的工作措施，包含工作依据、开展审图工作的领导机制、针对审图方面的工作团队、审图责任分工、审图情况考核办法
2考察投标人的工作方法，包括工作目标、审图重点、审图流程、审图问题上报机制、审图问题后续跟踪整改机制
3考察投标人的工作手段，包括分析审图经验、提高消防设计审查人员培训积极度的
" + }, + { + "type": "page_number", + "text": "1" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_02.json b/diagrams-and-tables/annotations/cn_nested_table_02.json new file mode 100644 index 0000000000000000000000000000000000000000..847428679141b983c9f9f8e421329835b82d5951 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_02.json @@ -0,0 +1,10 @@ +[ + { + "type": "table", + "html": "
的合理化建议较普通、完整性、规范性一般，思路不够清晰，内容合理性一般。
差评分标准：项目重点难点分析、应对措施及相关的合理化建议不完整、不规范，思路不清晰，内容合理性较差或未提供。
评价为优得 30 分；评价为良得 20 分；评价为中得 10 分；评价为差不得分。
3质量（完成时间、安全、环保）保障措施及方案81. 考察投标人的保密审图工作的细则，包括审图各环节的控制、时间安排、人员安排、审图人员的资格、个人能力、审图发现问题要求整改的措施、监督管理措施；
2. 考察投标人的消防设计审图场地情况，包括对自有或已租赁的固定消防设计审图场地、场地设施情况（提供相关场地证明文件及相片）。
评分依据：
提供以上 2 点内容得 50 分；提供以上 1 点内容得 20 分；未提供不得分。
在此基础上，专家根据内容的合理性进行评分：
优评分标准：质量（完成时间）保障措施及方案符合实际、完整、规范、思路清晰，内容合理性强。
良评分标准：质量（完成时间）保障措施及方案较符合实际、较完整规范、思路较清晰，内容合理性较强。
中评分标准：质量（完成时间）保障措施及方案较普通、完整性、规范性一般，思路不够清晰，内容合理性一般。
差评分标准：质量（完成时间）保障措施及方案不完整、不规范，思路不清晰，内容合理性较差或未提供。
评价为优得 50 分；评价为良得 30 分；评价为中得 10 分；评价为差不得分。
4项目完成（服务期满）后的服务承诺3考察投标人对项目的服务承诺，包含：
序号详情
1对签订合同的履约承诺
2对消防设计审图材料的保密承诺
3对消防设计审图过程中相关文件归档方案
" + }, + { + "type": "page_number", + "text": "3" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_03.json b/diagrams-and-tables/annotations/cn_nested_table_03.json new file mode 100644 index 0000000000000000000000000000000000000000..5443de006fdda723af593e0a0944e08c68944d76 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_03.json @@ -0,0 +1,10 @@ +[ + { + "type": "table", + "html": "
5服务应急预案及违约承诺3考察投标人违约承诺，包括违约赔偿、违约处罚、终止合同等追究相关责任。
（1）违约承诺全面、具体，针对性强、科学合理、可操作性强，得 100%分；
（2）违约承诺全面、具体，针对性较强、科学合理、可操作性较强，得 80%分；
（3）违约承诺一般、针对性一般、科学合理一般、可操作性一般，得 60%分；
（4）违约承诺差、针对性差、科学合理差、可操作性差或未提供的，不得分。
3商务部分48
序号评分因素权重评分准则
6企业认证情况51. 投标人在社会消防技术服务信息系统备案（信息录入）得 40 分；
2. 具有以下四个有效体系认证证书的，每项得 15 分：
序号详情
1环境管理体系认证证书
2信息安全管理体系认证证书
3职业健康安全管理体系认证证书
4质量管理体系认证证书

本项满分 100 分。
备案信息提供网站截屏，证书提供扫描件，原件备查。
7同类业绩情况181. 近三年内有承接过消防技术服务类政府市级、区级部门采购项目，得 50 分；
2. 近三年内为下列房建工程提供消防技术服务的：
（1）具有总建筑面积 50 万平方米以上且有单体建筑高度 200 米以上的公共建筑类项目得 20 分；
" + }, + { + "type": "page_number", + "text": "4" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_04.json b/diagrams-and-tables/annotations/cn_nested_table_04.json new file mode 100644 index 0000000000000000000000000000000000000000..0f58ced9353c7cf6a5be14b0e7f9052554d7062a --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_04.json @@ -0,0 +1,14 @@ +[ + { + "type": "title", + "text": "第二章 投标人须知" + }, + { + "type": "title", + "text": "一、投标人须知前附表" + }, + { + "type": "table", + "html": "
序号条款名称内 容
1.招标人名 称：麻城市能源投资开发有限公司
联系人：王先生 电话：0713-2960266
2.招标代理服务费及场租信息费名 称：湖北名达工程咨询有限责任公司
地 址：麻城市金桥大道 52 号（人行四楼）
联系人：刘女士 电话：0713-2116111
1. 招标代理服务费：根据国家发展与改革委员会发改价格299 号文的规定，经与招标人协商，由中标人以中标总价为基数，按差额定率累进法支付招标代理服务费，具体标准参照国家计委计价格1980 号文件货物类标准执行。招标代理服务费由中标人在领取中标通知书时，向代理机构支付。
2. 信息服务费依据鄂价工服规29 号和鄂价工服函34 号收取：由中标人在领取中标通知书前到麻城市公共资源交易中心付清。
3.项目名称麻城能投铁门岗乡 70MWp 农光互补光伏扶贫发电项目设计采购施工总承包（EPC）
4.项目编号MCCG-2016- 246-1
5.资金预算49000 万元
6.投标人应具备的基本条件投标人必须符合《政府采购法》第二十二条规定的条件, 且：
1、资格要求：投标人须具有独立的法人资格，且工商营业执照、税务登记证、组织机构代码证（已办理三证合一的只需提供营业执照副本）、安全生产许可证证照齐全，合格有效。
2、资质要求：投标人应同时具备设计和施工资质条件。
（a）设计资质为以下任一项
序号详细内容
1工程设计电力行业乙级及以上资质
2太阳能光电建筑一体化及光伏电站设计专项乙级及以上资质
3电力行业（新能源发电）专业乙级及以上资质
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_05.json b/diagrams-and-tables/annotations/cn_nested_table_05.json new file mode 100644 index 0000000000000000000000000000000000000000..1b0340a8b6c02cec5e51a20ce7de1d8c9dc859cb --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_05.json @@ -0,0 +1,14 @@ +[ + { + "type": "table", + "html": "
(二)投标人获奖情况1. 评分内容：
投标人承担的研究课题，获得市级及以上级别的奖励，或作为市级及以上级别政策文件进行公开发布的，每提供 1 个得 20%，最高得分不超过 100%。
2. 评分依据：
(1) 要求提供相关证明文件。
(2) 以上资料均要求提供扫描件(或官方网站截图)，原件备查。评分中出现无证明资料或专家无法凭所提供资料判断是否得分的情况，一律作不得分处理。		1515
(三)拟安排的项目负责人情况(仅限一人)1. 评分内容：
(1) 项目负责人具有中高级职称或博士学位，得 25%，否则不得分。
(2) 项目负责人主持或参与过相关领域市级以上政府课题的，每提供 1 个得 25%，最高得分不超过 75%。
2. 评分依据：
(1) 要求提供通过投标人购买的项目负责人近三个月社保，学位或职称文件，业绩合同关键页或其他证明文件(需要体现人员信息，若无人员信息，须提供工作单位出具的证明材料)。
(2) 以上资料均要求提供扫描件(或官方网站截图)，原件备查。评分中出现无证明资料或专家无法凭所提供资料判断是否得分的情况，一律作不得分处理。		1010
(四)拟安排的项目主要团队成员(主要技术人员)情况(项目负责人除外)1. 评分内容：
项目团队中每提供 1 位有中高级职称或博士学位人员得 50%，每提供 1 位有硕士学位人员得 25%，最高得分不超过 100%。
2. 评分依据：
(1) 要求提供通过投标人购买的团队成员近三个月社保，学位或职称文件等。
(2) 以上资料均要求提供扫描件(或官方网站截图)，原件备查。评分中出现无证明资料或专家无法凭所提供资料判断是否得分的情况，一律作不得分处理。		55
三价格部分(合计 15 分)
(一)投标报价价格分应当采用低价优先法计算，即满足招标文件要求且投标价格最低的投标报价为评标基准价，其价格分为满分。其他投标人的价格分统一按照下列公式计算：
投标报价得分=(评标基准价 / 投标报价)×100×权重
备注：		1515
" + }, + { + "type": "page_number", + "text": "2" + }, + { + "type": "footer", + "text": "第 2 页" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_06.json b/diagrams-and-tables/annotations/cn_nested_table_06.json new file mode 100644 index 0000000000000000000000000000000000000000..24a04d8b74ff39e2822358fad2940b0e9a2e6352 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_06.json @@ -0,0 +1,10 @@ +[ + { + "type": "table", + "html": "
提供的证明材料不符合要求的或或评审专家无法凭所提供资料判断是否得分的，该项参数视为负偏离。技术参数未要求提供证明材料的，则无需提供材料证明，以《技术要求偏离表》响应的为准。
3项目实施方案5(一) 评分内容：
投标人提供项目实施方案，内容包括以下内容：
①实施步骤；
②交货安排；
③设备调试；
④质量保证；
⑤应急预案。
(二) 评分依据：
1、每提供上述任意一项内容得 12 分，本小项累计最高得 60 分；
2、在此基础上，专家根据各供应商的具体响应内容按照量化的评审因素指标进一步评审：
方案整体科学合理、针对性强、可操作性强，评审为优的加 40 分
方案较合理、有一定针对性、一定可操作性，评审为良的加 25 分
方案不尽合理、针对性一般、可操作性一般，评审为中的加 10 分
方案不合理、无针对性、无可操作性，评审为差的加 0 分
3商务部分10
序号评分因素权重(%)评分准则
1免费保修期时长5（一）评分内容：
在满足提供主机及配件免费保修期要求的情况下，提供主机及配件免费保修期每增加 1 年得 50 分，最高得 100 分。
（二）评分依据：
投标人提供承诺函（格式自拟），未提供证明材料或者提供的证明材料不符合要求或评审专家无法凭所提供资料判断是否得分的，一律做不得分处理。
2同类业绩5（一）评分内容：
自 2022 年 1 月 1 日至本项目投标截止日前（以合同签订日期为准），投标人或产品
" + }, + { + "type": "footer", + "text": "- 2 -" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_07.json b/diagrams-and-tables/annotations/cn_nested_table_07.json new file mode 100644 index 0000000000000000000000000000000000000000..a3567a119c0635e11a3aaa70180350602f474557 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_07.json @@ -0,0 +1,46 @@ +[ + { + "type": "title", + "text": "湖北名达工程咨询有限责任公司招标文件" + }, + { + "type": "table", + "html": "
14.评标委员会的组成评标委员会成员由 7 人组成，其中招标人代表 1 人，评审专家 6 人，评标专家 6 人从省中心专家库中随机抽取。
15.履约保证金履约担保的形式：采用以支票、汇票、本票或者金融机构、担保机构出具的保函形式提交。
履约担保的金额：按中标价的 10%提交。
16.质量要求详见“技术规范”
17.投标文件递交截止时间2017 年 2 月 14 日 9 时 30 分
18.投标文件递交地点麻城市公共资源交易中心五楼开标大厅
19.投标文件递交要求本项目递交投标文件及开标现场，应由投标单位法定代表人或其授权代表持身份证原件参与，否则招标代理机构可拒收其投标文件。
20.开标时间2017 年 2 月 14 日 9 时 30 分
21.开标地点麻城市公共资源交易中心五楼开标大厅
22.评标方法及标准详见招标文件第四章 评标方法、步骤及标准
23.投标人提出问题的截止时间以邮件方式提交至邮箱地址，邮件发送后请及时致电告知招标代理机构，投标人提出问题的截止时间之后，提出的问题将不予受理。
邮件地址24874166@qq.com
截止时间2016 年 1 月 29 日 17:00 时
24.其他要求升压站、通信调度、继电保护、智能管理系统等，直至最终并网售电，以供电部门批准的接入方案为准。
" + }, + { + "type": "title", + "text": "二、说 明" + }, + { + "type": "text", + "text": "1. 适用范围" + }, + { + "type": "text", + "text": "1.1 本招标文件适用于麻城能投铁门岗乡 70MWp 农光互补光伏扶贫发电项目设计采购施工总承包（EPC）的采购。" + }, + { + "type": "text", + "text": "2. 定义" + }, + { + "type": "text", + "text": "2.1 “招标人”是指：麻城市能源投资开发有限公司。" + }, + { + "type": "text", + "text": "2.2 “监管部门”是指：麻城市财政局。" + }, + { + "type": "text", + "text": "2.3 “综合监管部门”是指：麻城市公共资源交易监督管理局。" + }, + { + "type": "text", + "text": "2.4 “代理机构”是指：湖北名达工程咨询有限责任公司。" + }, + { + "type": "page_number", + "text": "4" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_08.json b/diagrams-and-tables/annotations/cn_nested_table_08.json new file mode 100644 index 0000000000000000000000000000000000000000..df01b3f2f55a6cccf291c8a4829c58ebfe108593 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_08.json @@ -0,0 +1,10 @@ +[ + { + "type": "header", + "text": "招 标 编 号 ： 2012 [72]\n北京大学实验室与设备管理部" + }, + { + "type": "table", + "html": "
设备名称设备要求单位数量
自助复印打印系统如上描述（可扩展）套1
自助打印复印触摸柜1、机柜：进口金属漆/含电源开关/音响/熔断器/散热风机/RJ45 网络接口/刷卡口/丝网印刷
2、显示器：液晶显示器/响应时间：8ms/对比度：500：1/亮度 300CD/M2/
3、触摸屏：高级红外线触摸屏
4、工控机：主板 EMB-9459T、工业级固态硬盘 16G、内存金士顿 DDR2/1G、电源适配器 AVC
5、信号转换器：信号转换器、连接线		台4
彩色复印机
一般规格
复印速度黑白（A4）：≥45 页/分 彩色（A4）：≥45 页/分
首页复印时间黑白 ≤3.6 秒/彩色≤5.7 秒
分辨率≥600dpi
内存容量≥2GB
预热时间≤19 秒
硬盘容量≥190GB（标配）
纸张容量标准：≥1,200 页 最大：≥4,400 页
纸张尺寸A6-A3
纸张重量标配纸盘：52-256g/m$^{2}$ 手送纸盘：52-300g/m$^{2}$
选购纸盘：52-256g/m$^{2}$ 双面器：52-169g/m$^{2}$
连续复印张数（张）1-999 页
缩放比例标准：预设 5 种放大/7 种缩小
预设放大倍率 ：400,200,141,122,115% 预设缩小倍率 ：93,82,75,71,65,50,25%
变焦比率25-400%
重量小于 110kg （仅主机）
电源220-240V,50-60Hz
最大功耗≤1.7kw
打印功能
打印速度黑白（A4）：≥45 页/分 彩色（A4）：≥45 页/分
台3
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_09.json b/diagrams-and-tables/annotations/cn_nested_table_09.json new file mode 100644 index 0000000000000000000000000000000000000000..470a7a947788f919c5caf537ae428063e54650b0 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_09.json @@ -0,0 +1,6 @@ +[ + { + "type": "table", + "html": "
打印语言标准：PCL5c, PCL6 选购：Adobe PostScript3, IPDS
分辨率≥1,200X1,200dpi
界面标准：以太网（10Base-TX/100Base-TX）、USB2.0 type A、USB2.0 type B，前置 USB/SD 卡插槽
选购：以太网（1000Base-T）、IEEE1284
网络协议TCP/IP（IPV4, IV6）
操作系统Windows XP/Vista/7/Server 2003/Server 2008/Server 2008R2
Netware 6.5（选购）
Unix; Sun Solaris, HP-UX, SCO OpenServer, RedHat Linux, IBM AIX
Mac OS X v.10.2 or later
SAP R/3, NDPS Gateway
IBM iSeries/ AS/400-using OS/400
Host Print Transform
扫描功能
扫描速度黑白（A4/200dpi）：≥67 页/分
彩色（A4/200dpi）：≥67 页/分
分辨率≥1,200dpi
扫描文件格式PDF, TIFF, JPEG, PDF-A, 高压缩 PDF
绑定软件网络 TWAIN 扫描
最大原稿尺寸A3
扫描到电子邮件协议SMTP, POP3
最多可发送目标地址≥500 个
最多可存储目标地址≥2,000 个
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_10.json b/diagrams-and-tables/annotations/cn_nested_table_10.json new file mode 100644 index 0000000000000000000000000000000000000000..c6162a65224cc60f2cf3a06406286bd120b201f1 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_10.json @@ -0,0 +1,18 @@ +[ + { + "type": "title", + "text": "第一章 投标人须知" + }, + { + "type": "title", + "text": "投标人须知前附表" + }, + { + "type": "table", + "html": "
项号条款号条款名称编列内容
11.1招标人和招标代理机构
招标人
地址
联系人
电话
招标代理机构
地址
联系人
电话
21.2招标项目名称
31.3资金来源和落实情况资金来源：□国有资金 □非国有资金
出资比例：国有资金_____% 其中，财政资金_____% 资金核定表编号：________ 非国有资金：____%
资金落实情况：
41.4建设地点
51.5建设规模A. 房屋建筑工程：建筑面积：
工程造价 (工程费用限额)：
B. 市政基础设施：
(1) 道路：长度： 宽度：
(2) 桥梁：跨径：
(3) 排水：管径：
(4) 工程造价：
C. 风景园林工程：景观绿化面积：
工程造价 (工程费用限额)：
61.6招标类型A. 房屋建筑工程：□概念性方案设计招标；□实施性方案设计招标；□施工图设计招标；□组合方案设计、施工图设计招标
B. 市政基础设施工程：□综合工程招标；□单独桥梁工程招标；□单独排水工程招标；
C. 风景园林工程：□方案设计招标；□施工图设计招标；□组合方案设计、施工图设计招标；
D. 建筑装饰工程：□建筑装饰工程设计招标；
E. 岩土工程勘察：□可行性研究勘察招标；□初步勘察招标；□详细勘察招标；□施工勘察招标；
F. 岩土工程设计：□岩土工程设计招标；
G. 岩土工程监测：□岩土工程监测招标。
" + }, + { + "type": "page_number", + "text": "第 8 页" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_11.json b/diagrams-and-tables/annotations/cn_nested_table_11.json new file mode 100644 index 0000000000000000000000000000000000000000..1cb325f47394547865c6d162ad106348b222d001 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_11.json @@ -0,0 +1,6 @@ +[ + { + "type": "table", + "html": "
操作系统Windows XP/Vista/Server 2003/Server 2008/Server 2008 R2/7,
Netware: 6.5 及以上版本(选购)
Unix: Sun Solaris, HP-UX, SCO OpenServer, Red Hat Linux, IBM AIX
Mac: OS X 10.2 及以上版本,
SAP R/3,
NDPS Gateway,
IBM iSeries/AS/400-using OS/400
Host Print Transform
扫描
扫描速度黑白: ≥ 61 页/分钟
彩色: ≥ 31 页/分钟
分辨率≥ 600*600 dpi
最大原稿尺寸A3
输出格式TIFF; 单页 JPEG; PDF; 高压缩 PDF; PDF/A
绑定软件网络 TWAIN 扫描
扫描到电子邮件协议TCP/IP; SMTP; POP3
最多可发送目标地址≥ 500 个
最多可存储目标地址≥ 2,000 个
扫描到文件夹协议SMB, FTP; NCP
软件
Web Image Monitor(网页图像管理器)
Smart Device Monitor(智网管理程序)
DeskTop Binder V5 Lite(文档桌面管理器 V5 简化版)
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_12.json b/diagrams-and-tables/annotations/cn_nested_table_12.json new file mode 100644 index 0000000000000000000000000000000000000000..058a0e0f61beb3903e5bbcc58d2640bdd33ec34a --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_12.json @@ -0,0 +1,10 @@ +[ + { + "type": "title", + "text": "包二：一卡通系统" + }, + { + "type": "table", + "html": "
序号设备名称技术规格单位数量
1智能通道管理软件1、系统须完全兼容现有的一卡通管理平台，不须进行多次人员信息维护和发卡；
2、系统授权管理可进行分时段、分级别管理，可按照设定规则对某一类别人员进行自动授权；
3、可通过软件平台对人员出入进行实时监控，实时显示刷卡人姓名、班级等信息；
4、远程控制功能，可能远程操作控制通道设备的启用有敞开；
5、记录查询和报表打印功能；		套1
2智能通道机根据现场确定，要求知名品牌，包含辅助设备等暂估计 4 万。中标后要实际测试所选设备，由招标方确认。台1
3智能通道机读卡器1、支持卡类型：符合 ISO14443（TypeA）协议的 13.56MHz 卡，兼容读写北京市中小学生卡(包括 M1 S70 卡，和 CPU 卡)，支持对现有的北大附中学生卡信息的读写操作；
2、读卡范围： 0-5cm；
3、通讯接口： 维根 34；
4、读卡频率： 13.56M；
5、工作环境： 温度：-20°C~50°C 湿度：25%-95%；		台2
4智能通道机控制器
电源：AC220V
功耗：<10W
温度范围：-10℃～+50℃
通讯接口：TCP/IP
在线升级：支持
处理器：ARM 处理器
存储容量：不小于 32Mbit
记录容量：不小于 8 万
名单容量：不小于每通道 2 万
台1
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_13.json b/diagrams-and-tables/annotations/cn_nested_table_13.json new file mode 100644 index 0000000000000000000000000000000000000000..fa3586d31adc4fd4d6ded2ad6cc044fd9507c22d --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_13.json @@ -0,0 +1,10 @@ +[ + { + "type": "table", + "html": "
71.7招标范围和内容招标范围：__________（建筑安装工程、室外工程、岩土工程（勘察、设计、监测）等）；
其中包括__________（建筑装饰、建筑智能化、幕墙、钢结构、消防设施和环境工程等）专业工程施工图设计；
招标内容：__________（方案设计、初步设计、施工图设计；可行性研究勘察、初步勘察、详细勘察、施工勘察现场指导与监督，岩土工程设计、岩土工程监测；其他：__________）。
81.8计划开工日期和建设周期本工程计划于____年____月开工，工程建设周期____月
91.9勘察设计周期
工程时间
方案设计__________日历日
初步设计__________日历日
施工图设计__________日历日
岩土勘察__________日历日
岩土设计__________日历日
岩土监测__________日历日
102.1资格审查方式资格预审：收到招标人发出资格预审合格通知书的投标申请人
115.1踏勘现场和标前会时间地点
128.1招标文件的澄清投标人提交要求澄清文件的方式：____________________
要求澄清招标文件的截止时间：____年____月____日____时____分（北京时间）之前。
招标人对招标文件澄清、修改时间：____年____月____日____时至投标截止时间 15 天前
招标人发送澄清的方式：______________________________
投标人领取文本文件的时间和地点：____________________
1311.2是否要求提交电子文档、演示盘和模型计算机文件：__________（□要求、□不要求）提交
演示盘：__________（□要求、□不要求）提交
模型：__________（□要求、□不要求）提交
1413.3勘察设计费金额参照原《工程勘察设计收费标准》（计价格〔2002〕10 号），确定工程勘察设计计费基价及上下浮动幅度。招标人公布的勘察设计招标范围和内容的勘察设计费金额为______万元，浮动幅度为______%。
费用组成：方案设计费______万元，初步设计费______万元，施工图设计费______万元；岩土工程（勘察、设计、监测）费______万元。
投标人应参照《工程勘察设计收费标准》，结合本项目情况进行投标报价，不得超过浮动幅度报价竞标。
工程估算金额与经批准的标底造价金额不一致的，则以后者金额为计费基数，按实调整，但中标的勘察设计费浮动幅度不变。
1515.1投标有效期本招标项目的投标有效期为投标截止期后____日历天。
1616.1投标保证金投标保证金的金额：______万元人民币。投标保证金有效期截止到投标有效期结束。
" + }, + { + "type": "page_number", + "text": "第 9 页" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_14.json b/diagrams-and-tables/annotations/cn_nested_table_14.json new file mode 100644 index 0000000000000000000000000000000000000000..81a62cf5cee7231efab5ac5e8e9f8c1c76c4691c --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_14.json @@ -0,0 +1,6 @@ +[ + { + "type": "table", + "html": "
20无线网络控制器不小于 64 个 AP（含相应授权）；与校园原无线控制器兼容、并能形成 n+1 冗余模式；必须能针对单一用户进行带宽控制；必须支持 IPv4/IPv6 防火墙功能，并提供 ICSA 认证报告
支持 IGMP 代理/移动控制器智能转发
支持多信道部署，支持频谱负载均衡
支持动态组播优化（DMO），并支持 IP 组播的服务质量 QoS
具有 VLAN Pool 功能，可以动态给用户分配 VLAN。
支持 DHCP 动态分配 IPv4/IPv6 地址。支持强制要求只有通过 DHCP 拿到地址的用户才能正常上网，支持防止假冒 DHCP 服务器。
自动对笔记本、iPad、iPhone、Android 等终端设备进行识别和区分，并针对不同设备作相应的安全控制策略
AP 能够识别 WIFI 和非 WIFI 干扰源（如微波炉，无绳电话等），并自动对干扰进行分析，避开干扰。支持自动探测和识别所有 WIFI 和非 WIFI 干扰源，实时进行射频频谱分析。通过无线控制器的管理界面，实时查看 FFT 图、占空比图、干扰设备列表、信道占用率列表、干扰功率列表、信道质量列表等。
（1）支持基于 MAC 地址的认证方式；
（2）支持基于 Web 的用户名/密码的认证方式；
（4）支持基于 802.1X 的用户认证方式，并支持 802.1X 加速；
（3）支持对用户 IP 地址、端口号等方面的接入控制列表（ACL）功能。
（4）限制存取：在使用者未完成身份帐号登录认证时，无线控制器将限制并杜绝使用者存取网络上未经允许的网络服务，在使用者认证成功后，方使其网络正常运作。
（5）支持利用同一个 SSID 接入不同身份的终端用户，同时可以把不同身份的终端用户分配到不同的 VLAN
（6）支持同一 VLAN 中不同的无线终端之间的访		台2
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_15.json b/diagrams-and-tables/annotations/cn_nested_table_15.json new file mode 100644 index 0000000000000000000000000000000000000000..ea3843d6e76b58c6807bc43798c7a9bc59b95d44 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_15.json @@ -0,0 +1,10 @@ +[ + { + "type": "table", + "html": "
条款号条目内容
5.2.5标的所属行业本项目采购标的对应的中小企业划分标准所属行业：
包号标的名称中小企业划分标准所属行业
01全国司法加密网专线传输信息传输业。从业人员2000人以下或营业收入100000万元以下的为中小微型企业。其中，从业人员100人及以上，且营业收入1000万元及以上的为中型企业；从业人员10人及以上，且营业收入100万元及以上的为小型企业；从业人员10人以下或营业收入100万元以下的为微型企业。
5.7.1商品包装、快递包装本项目是否涉及商品包装、快递包装：
■否
□是，具体要求如下：
（1）包装要求：详见第五章《采购需求》；
（2）合同中履约验收要求：详见第六章《拟签订的合同文本》。
11.2投标报价投标报价的特殊规定：
■无
□有，具体情形：____。
12.1投标保证金投标保证金金额：
01 包：60000 元。
投标保证金收受人信息：
开户人名称：中钢招标有限责任公司
开户银行：中国民生银行股份有限公司北京大兴新城支行
人民币账号：【对应标包的投标保证金账号】
购标成功后，在平台内点击“我参与的标包”——“缴纳保证金”——“下一步”——“导出账号信息”，获取对应标包的投标保证金账号，请从供应商单位银行账户以电汇形式向此投标保证金账号缴纳投标保证金，应在投标文件提交截止时间前到账。
注意事项：（1）上述投标保证金账号，为本项目标包专属一次性虚拟账号，对于同一供应商、同一项目的不同标包，投标保证金虚拟账号各不相同。对应的投标保证金虚拟账号只接受本供应商本项目对应标包的投标保证金，其他项目、标包的投标保证金请勿电汇至本标包的账号。请勿泄露或从他人处获取账号信息。保证金账号获取相关问题可咨询（010-86397110）。（2）在采购活动结束后，投标保证金将按照供应商单位交款账户原路退还。
" + }, + { + "type": "page_number", + "text": "2" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_16.json b/diagrams-and-tables/annotations/cn_nested_table_16.json new file mode 100644 index 0000000000000000000000000000000000000000..531a849c940f653826bae863c66856730c68bd9a --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_16.json @@ -0,0 +1,14 @@ +[ + { + "type": "text", + "text": "北京大学深圳研究生院设备采购招标文件" + }, + { + "type": "table", + "html": "
2.2.1评委会根据招标文件商务及技术不可偏离项的内容和标准，对通过符合性检查的投标进行不可偏离项检查。
2.2.2评委会将对照招标文件中的商务、技术需求中的不可偏离条款和投标文件中的商务、技术条款响应进行评议。
2.2.3不可偏离项检查的结果是“合格”或“不合格”，只有逐条通过不可偏离项检查的投标方能进入下一阶段的评标，否则将导致其投标被废标。
2.3商务及技术评议
2.3.1评委会对通过不可偏离项检查的投标进行商务评议和技术评议。评委会将对照招标文件中的商务、技术需求条款和投标文件中的商务、技术条款响应进行打分。
2.3.2评标委员会将对照招标文件中的商务、技术需求条款和投标文件中的商务、技术条款响应进行评议。评标委员会成员将按照“评比因素《商务及技术评议指标表》”确定的权重比例独立对每个投标的商务及技术部分以打分的方式进行评议。
2.3.3评标委员会将以算术平均的方式对所有评标委员会成员的独立评分进行汇总，计算出每个投标人的商务及技术得分，商务及技术得分的满分为 70 分。
2.4价格评议
2.4.1价格得分满分为 30 分，计算方法如下：
满足招标文件要求且投标价格最低的投标报价为评标基准价，其价格分为满分。其他投标人的价格分统一按照下列公式计算：
投标报价得分=(评标基准价 / 投标报价)×价格分权重×100
2.4. 2投标人的最终评标得分=商务评议和技术评议得分 + 价格得分。
2.5评比因素：评委会在评标时，应按照以下量化的评审因素，对各投标文件进行分析和比较：
2.5.1符合性检查
序号评议内容评议结果
1法定代表人证明书/法人授权委托证明书有/无
2投标书有/无
3资格证明文件有/无
4技术文件有/无
5投标分项报价表有/无
6是否超过财政控制金额是/否
7结论合格/不合格
" + }, + { + "type": "page_number", + "text": "11" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_17.json b/diagrams-and-tables/annotations/cn_nested_table_17.json new file mode 100644 index 0000000000000000000000000000000000000000..3efcccca1990db08b605aa37f0a9642304b5d976 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_17.json @@ -0,0 +1,10 @@ +[ + { + "type": "table", + "html": "
条款号条目内容
27代理费收费对象：
□采购人
■中标人
收费标准：
以每个包中标人的投标报价为计算基数，按“国家计委关于印发《招标代理服务收费管理暂行办法》的通知”（计价格[2002]1980 号）规定的收费标准（见下表），采用差额定率累进计费方式计算，下浮 5%后乘以三年。
序号金额 M（万元）费率
货物服务工程
1M≤1001.50%1.50%1.00%
21001.10%0.80%0.70%
35000.80%0.45%0.55%
410000.50%0.25%0.35%
550000.25%0.10%0.20%
6100000.05%0.05%0.05%
71000000.01%0.01%0.01%
缴纳时间：
在领取中标通知书前向采购代理机构一次性缴纳。
接收招标代理服务费的银行账号：
同投标保证金账号。
28违法行为的处理如在招标各环节中出现供应商提供虚假材料谋取中标等违法行为，相关情形将被上报财政部门，并按政府采购相关规定处理。
《中华人民共和国政府采购法》第七十七条，供应商有下列情形之一的，处以采购金额千分之五以上千分之十以下的罚款，列入不良行为记录名单，在一至三年内禁止参加政府采购活动，有违法所得的，并处没收违法所得，情节严重的，由工商行政管理机关吊销营业执照；构成犯罪的，依法追究刑事责任：
（一）提供虚假材料谋取中标、成交的；
（二）采取不正当手段诋毁、排挤其他供应商的；
（三）与采购人、其他供应商或者采购代理机构恶意串通的；
（四）向采购人、采购代理机构行贿或者提供其他不正当利益的；
（五）在招标采购过程中与采购人进行协商谈判的；
（六）拒绝有关部门监督检查或者提供虚假情况的。
供应商有前款第（一）至（五）项情形之一的，中标、成交无效。
29增补条款本次采购的服务周期为 3 年，合同按年分别签订。采购人有权根据上年度服务考核结果和当年预算批复情况决定是否续签合同。供应商报价须充分考虑上述风险。
" + }, + { + "type": "page_number", + "text": "5" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_18.json b/diagrams-and-tables/annotations/cn_nested_table_18.json new file mode 100644 index 0000000000000000000000000000000000000000..d898102001711f2f123505585b4ca4b32598e133 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_18.json @@ -0,0 +1,34 @@ +[ + { + "type": "title", + "text": "一、资格审查程序" + }, + { + "type": "text", + "text": "1 开标结束后，采购人或采购代理机构将根据《资格审查要求》中的规定，对投标人进行资格审查，并形成资格审查结果。" + }, + { + "type": "text", + "text": "2 《资格审查要求》中对格式有要求的，除招标文件另有规定外，均为“实质性格式”文件。" + }, + { + "type": "text", + "text": "3 投标人《资格证明文件》有任何一项不符合《资格审查要求》的，资格审查不合格，其投标无效。" + }, + { + "type": "text", + "text": "4 资格审查合格的投标人不足 3 家的，不进行评标。" + }, + { + "type": "title", + "text": "二、资格审查要求" + }, + { + "type": "table", + "html": "
序号审查因素审查内容格式要求
1满足《中华人民共和国政府采购法》第二十二条规定及法律法规的其他规定具体规定见第一章《投标邀请》
1-1营业执照等证明文件）的，应提供有效的“营业执照”；
投标人为事业单位的，应提供有效的“事业单位法人证书”；
投标人是非企业机构的，应提供有效的“执业许可证”、“登记证书”等证明文件；
投标人是个体工商户的，应提供有效的“个体工商户营业执照”；
投标人是自然人的，应提供有效的自然人身份证明。
投标人提供资料
企业（包括合伙企业）“营业执照”
事业单位“事业单位法人证书”
非企业机构“执业许可证”、“登记证书”等证明文件
个体工商户“个体工商户营业执照”
自然人自然人身份证明

若本项目允许分支机构参加投标，则分支机构参加投标的，此处可提供该分支机构或其所属法人或其他组织的相应证明文件。		提供证明文件的复印件
" + }, + { + "type": "page_number", + "text": "6" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_19.json b/diagrams-and-tables/annotations/cn_nested_table_19.json new file mode 100644 index 0000000000000000000000000000000000000000..4402b534ddf462c1bf5b3f5438133c54a93ecaf6 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_19.json @@ -0,0 +1,10 @@ +[ + { + "type": "table", + "html": "
13国家有关部门对投标人的投标产品有强制性规定或要求的国家有关部门对投标人的投标产品有强制性规定或要求的（如相应技术、安全、节能和环保等），投标人的投标产品应符合相应规定或要求，并提供证明文件复印件：
1）采购的产品若属于《节能产品政府采购品目清单》范围中政府强制采购产品，则投标人所报产品必须获得国家确定的认证机构出具的、处于有效期之内的节能产品认证证书；
2）投标产品如涉及计算机信息系统安全专用产品的，须提供公安部颁发的计算机信息系统安全专用产品销售许可证；
3）投标产品如有属于开展国家信息安全产品认证产品范围的，须提供由中国网络安全审查技术与认证中心（原中国信息安全认证中心）按国家标准认证颁发的有效认证证书等；
4）国家有特殊信息安全要求的项目，采购产品涉及无线局域网产品和含有无线局域网功能的计算机、通信设备、打印机、复印机、投影仪等产品的，投标产品须为符合国家无线局域网安全标准（GB 15629.11/1102）并通过国家产品认证的产品；
5）项目中涉及涂料、胶黏剂、油墨、清洗剂等挥发性有机物产品，且属于强制性标准的，供应商应执行符合本市和国家的 VOCs 含量限制标准。
14公平竞争投标人遵循公平竞争的原则，不存在恶意串通，妨碍其他投标人的竞争行为，不存在损害采购人或者其他投标人的合法权益情形的；
15串通投标不存在《政府采购货物和服务招标投标管理办法》视为投标人串通投标的情形：
序号
一不同投标人的投标文件由同一单位或者个人编制
二不同投标人委托同一单位或者个人办理投标事宜
三不同投标人的投标文件载明的项目管理成员或者联系人员为同一人
四不同投标人的投标文件异常一致或者投标报价呈规律 性差异
五不同投标人的投标文件相互混装
六不同投标人的投标保证金从同一单位或者个人的账户转出
16附加条件投标文件未含有采购人不能接受的附加条件的；
" + }, + { + "type": "page_number", + "text": "12" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_20.json b/diagrams-and-tables/annotations/cn_nested_table_20.json new file mode 100644 index 0000000000000000000000000000000000000000..4616a8bdd8d99fc33cb3cf4c6a7f7d748b5f1f1a --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_20.json @@ -0,0 +1,18 @@ +[ + { + "type": "text", + "text": "(1) 技术评分标准(30 分)" + }, + { + "type": "table", + "html": "
评分项目评审内容分值(分)评分标准得分(分)
技术措施(10 分)缩短工期措施5根据投标人所提出的保证设计质量、缩短建设工期的措施的科学性、可行性及满足招标文件要求的程度分别进行评分。
控制造价经济性措施5根据投标人所提出的控制造价经济性进行评分。
技术方案(20 分)根据已确定的设计方案，明确节能、结构、给排水、电气、暖通等专业的技术方案20
标准得分
保温节能的先进工艺的应用4
结构、设备与建筑方案的符合性4
结构专业技术方案的科学性4
给排水专业技术方案的科学性2
电气专业技术方案的科学性2
暖通专业技术方案的科学性2
低碳、环保等新技术的应用2
得分合计
评委日期
" + }, + { + "type": "text", + "text": "(2) 总得分\n商务分和技术分之和为投标人的总得分。" + }, + { + "type": "page_number", + "text": "第 15 页" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_21.json b/diagrams-and-tables/annotations/cn_nested_table_21.json new file mode 100644 index 0000000000000000000000000000000000000000..c372f09f2b70f93e641e5a096a36c390c79e1d9c --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_21.json @@ -0,0 +1,10 @@ +[ + { + "type": "table", + "html": "
4方案针对性高的，得4分；方案具有一定的针对性的，得2分；方案针对性欠佳的，得1分；方案针对性存在重大缺陷或未提供方案的，得0分。
8售后服务方案4方案内容完整、描述具体详实的，得4分；方案内容完整、但描述不够具体详实的，得2分；方案内容不够完整、描述不够具体详实的，得1分；方案存在重大缺陷或未提供方案的，得0分。
4
方案可实施性高的得4分
方案具有一定的可实施性的得2分
方案可实施性欠佳的得1分
方案可实施性存在重大缺陷或未提供方案的得0分
4方案针对性高的，得4分；方案具有一定的针对性的，得2分；方案针对性欠佳的，得1分；方案针对性存在重大缺陷或未提供方案的，得0分。
9保密措施解决方案3方案内容完整、描述翔实具体、考虑周全合理可行、贴近项目实际针对性强，得3分；方案通用、简单，考虑不够周全或针对性欠佳，得2分；方案内容不全或存在明显欠缺，得1分；未提供方案得0分。
10投标报价15满足招标文件要求且投标价格最低的投标报价为评标基准价，其价格分为满分。其他投标人的价格分统一按照下列公式计算：
投标报价得分=（评标基准价/投标报价）×分值。		此处投标报价指经过报价修正，及因落实政府采购政策进行价格调整后的报价，详见第四章《评标程序、评标方法和评标标准》2.4 及 2.5。
合计100
" + }, + { + "type": "page_number", + "text": "15" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_22.json b/diagrams-and-tables/annotations/cn_nested_table_22.json new file mode 100644 index 0000000000000000000000000000000000000000..d415934de8f12f8b5963ee05ab1a21c1d52c7ee1 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_22.json @@ -0,0 +1,18 @@ +[ + { + "type": "title", + "text": "一、供应商须知" + }, + { + "type": "title", + "text": "（一）须知前附表" + }, + { + "type": "table", + "html": "
序号内容说明与要求
1采购人六安市社会福利院
2采购代理机构
名称六安市瑞新项目管理有限公司
地址安徽省六安市金安区皖西路健康苑小区 10 幢 203 商铺
3谈判有效期投标截止日后 30 天
4项目类型服务类
5项目名称六安市社会福利院康复服务项目
6项目编号LARX-20241108
7付款方式付款方式：按季度支付。
（供应商提交的响应文件中如有关于付款条件的表述与谈判文件规定不符，将被视为实质性不响应，将导致响应无效）
8中标服务费招标代理服务费和评标评审专家劳务费由成交供应商支付。招标代理服务费收费标准依据国家计委计价格〔2002〕1980 号、发改价格〔2011〕534 号和皖价服[2007]86 号文件规定标准计取。评标评审专家劳务费按实计取（无票）。以上费用包含在投标报价的单价、合价与总价中，不单独报价。
9履约保证金成交供应商在签订合同时应向采购人提交合同总价 /% 的履约保证金。
成交供应商可以通过转账、网银支付、汇票、支票、保证保险、银行履约保函等方式提交履约保证金。
10勘察现场请各供应商联系采购单位自行勘踏。
11质疑与答疑供应商如果对采购文件内容有相关疑问，向采购人或采购代理机构以书面形式提出（联系方式见谈判公告）。采购人对谈判文件进行的澄清、更正或更改，将在网站上及时发布，该公告内容为谈判文件的组成部分，对投标人具有同样约束力效力。投标人应
" + }, + { + "type": "page_number", + "text": "1" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_23.json b/diagrams-and-tables/annotations/cn_nested_table_23.json new file mode 100644 index 0000000000000000000000000000000000000000..1f7e0bf3eccebd8b5c101de42bf710642be04685 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_23.json @@ -0,0 +1,10 @@ +[ + { + "type": "table", + "html": "
主动上网查询，投标人须自行承担因未及时关注相关信息而引发的相关责任。
12响应文件份数及要求1、一式五份，正本一份，副本四份，标书封面注明“正本”、“副本”字样。
2、供应商的响应文件须胶装成册，否则响应文件无效
13响应文件的密封和标记1、密封：响应文件装入密封袋内，密封袋封口处加盖供应商单位章。供应商未按上述要求密封的，其响应文件无效。
2、标记：密封袋上注明：
供应商名称
项目名称（同时还需标明正本、副本）
采购人名称

在 年 月 日时分前不得开启
供应商未按上述要求密封和标记，其响应文件无效
14响应文件的签署谈判文件中明确要求加盖供应商公章、签字的，响应文件中必须加盖供应商公章、签字，否则将导致响应文件无效。
15递交投标文件注意事项1、供应商代表（法人或者授权代表）应在响应文件递交截止时间前签到并递交纸质响应文件；
2、法人参加磋商会议的须在响应文件中提供身份证明复印件，授权代表参加磋商会议的须在响应文件中提供授权书及身份证明复印件（见响应文件格式附件三）；
16备注一1、存在以下不良信用记录情形之一的，不得推荐为成交候选供应商：
（1）供应商被人民法院列入失信被执行人的；
（2）供应商被市场监督管理部门列入企业经营异常名录的；
（3）供应商被税务部门列入重大税收违法案件当事人名单的；
（4）供应商被政府采购监管部门列入政府采购严重违法失信行为记录名单的。
2、联合体供应商，联合体任何一方存在上述不良信用记录的，视同联合体存在不良信用记录。
" + }, + { + "type": "page_number", + "text": "2" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_24.json b/diagrams-and-tables/annotations/cn_nested_table_24.json new file mode 100644 index 0000000000000000000000000000000000000000..881c0df509b98609d0ba0e8509420419ae9b43f0 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_24.json @@ -0,0 +1,10 @@ +[ + { + "type": "table", + "html": "
3、不良信用记录查询渠道如下：
失信被执行人：信用中国官网（www.creditchina.gov.cn）
企业经营异常名录：信用中国官网（www.creditchina.gov.cn）
重大税收违法案件当事人名单：信用中国官网（www.creditchina.gov.cn）
政府采购严重违法失信行为记录名单中国政府采购官网（www.ccgp.gov.cn）
4、投标时，供应商应当查询上述记录后，如实提供无不良信用记录声明并加盖供应商签章。如有虚假，采购人将取消其成交资格并上报六安市公共资源交易监督管理局按有关规定处理。
17备注二特别提醒：供应商参与政府采购，应当诚信守法、公平竞争。如有以提供虚假材料（包括但不限于虚假技术参数响应、虚假业绩、虚假证书、虚假检测报告等）、串通投标、隐瞒失信信息等谋取中标的行为，一经发现，将报监管部门严肃查处。
" + }, + { + "type": "page_number", + "text": "3" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_nested_table_25.json b/diagrams-and-tables/annotations/cn_nested_table_25.json new file mode 100644 index 0000000000000000000000000000000000000000..d7260742df076d9322d528459b656f66630d28fb --- /dev/null +++ b/diagrams-and-tables/annotations/cn_nested_table_25.json @@ -0,0 +1,10 @@ +[ + { + "type": "table", + "html": "
出应对措施和建议、提供的延伸服务情况、针对本项目服务承诺情况），横向比较，分档评分：根据内容准确完善，方案科学合理可操作性强的评价为优的得100%；内容准确完善，方案合理的评价为良的得85%；内容基本完善的评价为中的得70%；内容不全有严重缺漏项的评价为差的不得分。专家按照百分制打分。
3项目完成（服务期满）后的服务承诺8根据各投标人投标文件的响应内容（进度安排是否合理，能否满足项目要求，能否提供相应的保障措施）：内容准确完善，措施科学合理可操作性强的评价为优的得 100%；内容准确完善，措施合理的评价为良的得 85%；内容基本完善的评价为中的得 70%；内容不全有严重缺漏项的评价为差的不得分。专家按照百分制打分。
4违约承诺5根据招标文件的需求和投标文件响应情况进行横向比较。评分标准：
序号要求
1违约承诺内容全面
2违约承诺内容具体，表达清晰、完整、严谨
3违约承诺内容根据性强
4违约承诺内容先进，科学合理
5违约承诺内容可操作性强

优得 100%，良得 85%，中得 70%，差不得分，不提供或无法分辨的不得分。以提供供应商承诺函为准，格式自拟。
3综合实力28
序号评分因素权重 (%)评分准则
1拟安排的项目负责人10评审内容：1.项目负责人为专职律师，若具有本科学历的，得 20%；若具有硕士及以上学位的，得 40%。（需提供学历、学位证明材料扫描件）2.项目负责人的执业年限为 10 年（含）以上的，得 20%；5 年（含）至 9 年的，得 10%；5 年以下的不得分。3.项目负责人获得市级及以上荣誉证书的（法律服务方面），得 40%。（需提供荣誉证书复印件）评分依据：1.要求提供投标人相关证明资料作为得分依据。2.以上资料均要求提供扫描件（或官方网站截图），原件备查。评分中出现无证明资料或专家无法凭所提供资料判断是否得分的情况，一律作不得分处理。3.如涉及考察人员工作经验，要求提供项目合同关键信息作为得分依据，通过合同关键信息无法判断是否得分的，还须同时提供合同甲方出具的证明文件。
" + }, + { + "type": "page_number", + "text": "- 3 -" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_01.json b/diagrams-and-tables/annotations/cn_simple_table_01.json new file mode 100644 index 0000000000000000000000000000000000000000..db0a24f87f338608b62bc4b999b85ef59d1e36d6 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_01.json @@ -0,0 +1,10 @@ +[ + { + "type": "table", + "html": "
（二）投标人获奖情况1. 评分内容：
投标人承担的研究课题，获得市级及以上级别的奖励，或作为市级及以上级别政策文件进行公开发布的，每提供 1 个得 20%，最高得分不超过 100%。
2. 评分依据：
（1）要求提供相关证明文件。
（2）以上资料均要求提供扫描件（或官方网站截图），原件备查。评分中出现无证明资料或专家无法凭所提供资料判断是否得分的情况，一律作不得分处理。		1515
（三）拟安排的项目负责人情况（仅限一人）1. 评分内容：
项目负责人具有中高级职称或博士学位得 25%，否则不得分
项目负责人主持或参与过相关领域市级以上政府课题的每提供 1 个得 25%，最高得分不超过 75%
2. 评分依据：
（1）要求提供通过投标人购买的项目负责人近三个月社保，学位或职称文件，业绩合同关键页或其他证明文件（需要体现人员信息，若无人员信息，须提供工作单位出具的证明材料）。
（2）以上资料均要求提供扫描件（或官方网站截图），原件备查。评分中出现无证明资料或专家无法凭所提供资料判断是否得分的情况，一律作不得分处理。		1010
（四）拟安排的项目主要团队成员（主要技术人员）情况（项目负责人除外）1. 评分内容：
项目团队中每提供 1 位有中高级职称或博士学位人员得 50%，每提供 1 位有硕士学位人员得 25%，最高得分不超过 100%。
2. 评分依据：
（1）要求提供通过投标人购买的团队成员近三个月社保，学位或职称文件等。
（2）以上资料均要求提供扫描件（或官方网站截图），原件备查。评分中出现无证明资料或专家无法凭所提供资料判断是否得分的情况，一律作不得分处理。		55
三价格部分（合计 15 分）
（一）投标报价价格分应当采用低价优先法计算，即满足招标文件要求且投标价格最低的投标报价为评标基准价，其价格分为满分。其他投标人的价格分统一按照下列公式计算：
投标报价得分=(评标基准价 / 投标报价)×100×权重
备注：		1515
" + }, + { + "type": "footer", + "text": "第 2 页" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_02.json b/diagrams-and-tables/annotations/cn_simple_table_02.json new file mode 100644 index 0000000000000000000000000000000000000000..46054a4042be03de78d57a53b1cd0dfe7d00a244 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_02.json @@ -0,0 +1,14 @@ +[ + { + "type": "title", + "text": "评标信息" + }, + { + "type": "text", + "text": "评标方法：综合评分法\n综合评分法，是指投标文件满足招标文件全部实质性要求，且按照评审因素的量化指标评审得分排名前列的投标人为中标候选人的评标方法。\n价格分计算方法：\n采用低价优先法计算，即满足招标文件要求且投标价格最低的投标报价为评标基准价，其价格分为满分。其他投标人的价格分统一按照下列公式计算：\n投标报价得分=(评标基准价 / 投标报价)×100\n评标总得分=F1×A1+F2×A2+......+Fn×An\nF1、F2......Fn 分别为各项评审因素的得分；\nA1、A2、......An 分别为各项评审因素所占的权重(A1+A2+......+An=1)。\n评标过程中，不得去掉报价中的最高报价和最低报价。\n因落实政府采购政策进行价格调整的，以调整后的价格计算评标基准价和投标报价。" + }, + { + "type": "table", + "html": "
序号评分项权重(%)
1价格30
2技术部分55
序号评分因素权重(%)评分准则
1所投产品一般参数响应情况评价35（一）评分内容：
投标人根据“第三章 用户需求书”“技术要求”如实填写《技术要求偏离表》，评审委员会根据投标人的一般参数响应情况进行评价，所投产品参数（非“★”“▲”指标项技术参数）全部满足得 100 分；有负偏离的，每负偏离一项扣 8.34 分，扣完为止。
（二）评分依据：
提供《技术要求偏离表》。投标人未按具体的技术参数要求提供相关证明材料或者提供的证明材料不符合要求的或评审专家无法凭所提供资料判断是否得分的，该项参数视为负偏离。技术参数未要求提供证明材料的，则无需提供材料证明，以《技术要求偏离表》响应的为准。
2所投产品重要参数响应情况评价15（一）评分内容：
投标人根据“第三章 用户需求书”“技术要求”如实填写《技术要求偏离表》，评审委员会根据投标人的一般参数响应情况进行评价，所投产品重要参数（“▲”指标项技术参数）全部满足得 100 分；有负偏离的，每负偏离一项扣 100 分，扣完为止。
（二）评分依据：
提供《技术要求偏离表》。投标人未按具体的技术参数要求提供相关证明材料或者
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_03.json b/diagrams-and-tables/annotations/cn_simple_table_03.json new file mode 100644 index 0000000000000000000000000000000000000000..f4037113589fcc1c99af040ce6f93830eb9c9c81 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_03.json @@ -0,0 +1,10 @@ +[ + { + "type": "table", + "html": "
制造商具有本项目所投核心产品的销售业绩，且履约评价为合格或满意或同等最高评价，每提供 1 份得 50 分，本项累计最高得 100 分。
（二）评分依据：
投标人同时提供以下证明文件：
1. 提供销售合同关键页（包括但不限于合同（项目）名称、合同采购内容、签订日期、合同双方签字盖章页）
2. 履约评价为合格或满意或同等最高评价的履约评价文件或验收合格的验收报告（需加盖甲方公章或业务章）。
3. 以上证明文件原件备查，未提供证明材料或者提供的证明材料不符合要求或评审专家无法凭所提供资料判断是否得分的，一律做不得分处理。
4诚信情况5
序号评分因素权重(%)评分准则
1诚信情况5投标人存在《深圳市财政局政府采购供应商信用信息管理办法》（深财规〔2023〕3 号）列明的一般行政处罚信息、一般违法失信记录信息的，本项不得分，不存在上述情形的本项得 100 分。投标人无需提供任何证明材料，评标过程中由工作人员向评审委员会提供有关供应商诚信查询结果。
查询渠道：通过“信用中国”（www.creditchina.gov.cn，下载信用信息报告）、“中国政府采购网”（www.ccgp.gov.cn）“深圳市政府采购监管网”（http://zfcg.sz.gov.cn）、以及“深圳政府采购智慧平台信用库”查询供应商信用信息，信用信息以开标当日的查询结果为准。
" + }, + { + "type": "page_number", + "text": "- 3 -" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_04.json b/diagrams-and-tables/annotations/cn_simple_table_04.json new file mode 100644 index 0000000000000000000000000000000000000000..6019833f0b5a12244a5945e7f76d9932815b7681 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_04.json @@ -0,0 +1,6 @@ +[ + { + "type": "table", + "html": "
1维修服务和优惠价格1.1 由生产厂家提供售后服务，4 小时内响应，24 小时维修到位。消耗品和零配件供应及时，特殊情况下可提供备用机。
1.2 终身维修，保修期满后，生产厂家对用户进行的售后服务只收更换部件的成本费，提供维修零配件、消耗品优惠价格。中标人负责设备的终身维修并应继续提供优质的服务，储备足够的零配件备库并保证十年以上维修配件、耗材的正常供应。十年内免费提供软件升级服务。
1.3 采购人可与投标人就优惠价进行谈判，但优惠价不得高于投标人在投标文件中承诺的消耗品、零配件报价。
1.4 生产厂家维修的货物经采购人验收合格，且厂家提供维修发票后，采购人支付维修费用。
1.5 投标人及生产厂家不得以任何理由不按时进行维修，不得要求采购人购买所谓“保修服务”（即：不论设备有无故障，先买保修服务），不得在设备中嵌设任何不利于采购人使用与维修设备的障碍。
1.6 信息化系统：含设备接入医院信息系统（包括但不限于 HIS、PACS、LIS 等）端口开发、调试及对接费用，确保设备数据能实时、准确上传至医院指定系统，投标供应商须配合医院信息科及科室完成系统对接测试。在保修期内，应免费将软件更新、维护并免费提供更新所需的硬件，免费开放软件端口，无偿派人配合与医院信息系统（包括但不限于 HIS、PACS、LIS 等系统）的连接工作，直至该设备与医院信息系统可进行完整的数据交换；当医院信息系统变更或其他情形需要与该设备连接时，无偿派人配合，直至该设备与医院信息系统可进行完整的数据交换，确保数据安全，无外泄。
（三）其他商务要求
1交货要求★1. 投标人在签订合同之日起 30 天（日历日）内交货。
2. 交货地点：采购人指定地点
3. 投标人应提供货物的技术文件，包括但不限于设备配置清单、产品说明书、图纸、操作手册、维护手册（含维修密码及接口数据）、质量证明文件（含生产厂家出具的出厂合格证）、服务指南等，所有外文资料须提供中文译本。文件应随货物一并交付至采购人指定地点。
4. 提供的货物须为全新、经检验合格的产品。产品如需要计量检定的应提供相关计量检定部门出具的合法检定报告。其中，进口设备必须提供相关进口资料。
2报价要求投标总价是完成该项目的一切费用总和，包括完成采购项目所需的一切费用，即：设备费、软件费、税费、运输费、装卸费、安装费、调试费、培训费、计量及技术服务费和一切不可预见等费用，项目结算时不做任何单价或费用的调整（因数量变更除外）。
3质量要求★投标人保证所提供的产品必须是生产日期在半年内未使用过的原厂全新产品（包括零部件），符合国家或省级行业质量标准。确保产品投入使用前，按照国家规定办理好产品所有启用所需的资质证件。
4付款方式1. 预付款支付
合同签订后，中标人需向采购人提供全额发票，采购人在收到发票且财政资金到位后，向中标人支付合同总金额 50%的货物预付款。
2. 进度款（尾款）支付
中标人将货物运至指定地点、完成安装调试、设备运行合格并通过性能验收后，采购人根据财政拨款时间支付剩余 50%货款。具体规则如下：
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_05.json b/diagrams-and-tables/annotations/cn_simple_table_05.json new file mode 100644 index 0000000000000000000000000000000000000000..565b47c6e902a5cb34501d8c6c39fbeeccf325e9 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_05.json @@ -0,0 +1,6 @@ +[ + { + "type": "table", + "html": "
2.1 若财政资金足额到位且设备验收合格，采购人按照财务审批流程支付剩余 50%货款；
2.2 若财政资金不足以支付尾款，采购人可据实支付部分款项，待剩余资金到位后结清余款；
2.3 若采购人 2025 年资金预算不足，付款顺延至 2026 年。
5运输、安装和验收1. 投标人负责将货物安全无损运抵采购人指定地点，并承担设备的包装、运输、保险、装卸、安装调试、培训、商检及计量检测、关税、增值税和进口代理等费用。
2. 货物安装前厂家需派专业工程师到现场确认场地及安装环境是否符合该设备安装要求，在用户单位、中标人双方在场情况下开箱检验。在安装过程中若造成机器损坏，应由中标人负责修复，安装后保证产品质量。
3. 采购人有权检验或测试货物，以确认货物是否符合合同规格的要求，并且不承担额外的费用。如果发现所交货物与投标文件中所承诺的不符或存在质量、技术缺陷等，采购人可以拒绝接收该货物，投标人应在 30 天（日历日）内采取补足、更换或退货等措施，以满足规格的要求，由此发生的一切损失和费用由投标人承担。
4. 供货时须确保产品外观清洁，标记编号以及盘面显示等字体清晰、明确，能够准确无误地表示产品的型号、规格、制造商等，并保证所提供的产品的可追溯性。
5. 投标人负责货物的现场安装和调试，提供货物安装、调试和维修所需的专用工具和辅助材料。投标人应在货物运至指定地点后一周内开始安装调试，并在 15 天（日历日）内完成安装调试工作。
★6. 当满足以下条件时，采购人才向中标人签发货物验收报告：
（1）设备全新，外观无伤痕变形或明显修饰痕迹。
（2）如有国标，需符合有关规定；如无国标，则按照行业标准；如无国标及行业标准，则按双方约定执行。投标文件提供的技术数据经实测证实是真实的。检验及免费保修期内达到的性能指标与要求一致，达到或优于相应标准。
（3）技术文件资料、备件等已按规定数量移交完毕。
（4）按照招标文件要求及投标文件提供的技术要求验收合格。
（5）投标人提供的各种文件载明的内容应保证真实，其技术数据采购人有权要求投标人提供采购人认可的第三方按照双方同意的试验方法进行检测。检测结果需证明投标人提供的技术数据是真实的，否则视为不合格。
（6）货物具备产品合格证。
（7）在货物安装调试合格后，所有技术指标达到技术规范书要求，经验收合格后，双方共同签署验收报告。
6履约保证金1. 履约保证金提交要求
1.1 中标人需向采购人提供合同总额 5%的履约保证金，由中标人自主选择以支票、汇票、本票、保函等非现金方式提交。
1.2 提交时间：合同签订后 10 日内提交。
1.3 如涉及相关费用的，均由中标人自行承担。
2. 保证金退还：中标人完成供货且经过采购人验收合格后，采购人在 30 日内不计利息退还。
3. 违约处理：中标人发生违约行为，如设备出现质量问题，或中标人未按采购人要求维修或替换，则采购人有权扣除已收取的履约保证金，无需经过中标人同意，由此造成的一切损失由中标人承担。
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_06.json b/diagrams-and-tables/annotations/cn_simple_table_06.json new file mode 100644 index 0000000000000000000000000000000000000000..03729f636a67b660262e34dfbdcaec914b3ad54b --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_06.json @@ -0,0 +1,6 @@ +[ + { + "type": "table", + "html": "
7培训中标人应派专业技术人员免费对采购单位制定人员进行定期培训及指导，直至其完全掌握设备的基本故障处理技术，其中第一次培训应在设备验收后一周内有专业人员对采购人临床操作人员进行专业的培训。
8违约条款1. 中标人提供的设备品种、型号、规格、质量、数量不符合招标文件或经采购人验收不合格的，采购人有权解除合同，中标人应向采购人支付合同总价 30%的违约金，如采购人已支付货款的中标人还应立即退还，若违约金不足以弥补采购人损失的，中标人还应按实际损失对采购人予以赔偿。
2. 中标人无正当理由不能交付设备的，采购人有权解除合同，中标人应向采购人支付合同总价 30%的违约金，如违约金不足以弥补采购人损失的，中标人还应按实际损失对采购人予以赔偿。
3. 中标人未按合同约定履行保修维修服务的，中标人向采购人每日给付违约金为合同总价的 1%，逾期提供服务超过 30 天的，采购人有权解除合同，中标人应向采购人支付合同总价 30%的违约金，如采购人已支付货款的中标人还应立即退还，若违约金不足以弥补采购人损失的，中标人还应按实际损失对采购人予以赔偿。
4. 中标人承诺所使用软件的合法性，因中标人使用的软件引起纠纷给采购人造成损失的，应按合同总价的 30%向采购人承担违约责任，违约金不足以弥补损失的，还应赔偿相应损失。
5. 由于中标人的原因，未能按时供货或配合验收的，每迟一天应给付采购人的违约金为合同总额的 1%，总额不超过合同总价的 30%；如超过供货期 30 日，采购人有权解除合同，如采购人已支付货款的中标人还应立即退还，违约金不足以弥补损失的，应赔偿相应损失。
6. 由于中标人的原因，在货到一周内未进行安装调试，或安装调试时间超过正常要求（30 日），每超过一天应给付采购人的违约金为合同总额的 1%。违约金不足以弥补采购人损失的，中标人应承担相应损失。情节严重者，采购人将依法律程序要求中标人进行索赔。
7. 中标人提供的设备经调试验收合格后，在保修期内连续三个月内频繁（平均每月 1 次或 1 次以上）出现设备不能正常使用的情况，采购人有权要求中标人免费更新机或者退货。
8. 中标人违约或给采购人造成损失的，应承担采购人的维权费用（包括但不限于诉讼费，财产保全担保费，律师费，调查取证费，鉴定费，交通费，差旅费等）。在合同履行过程中，如双方发生分歧或纠纷，应首先通过友好协商方式解决，协商未果，任何一方均可向采购人所在地有管辖权的人民法院提起诉讼。
9知识产权1. 投标人应保证采购人在使用该货物或其任何一部分时，免受第三方提出的侵犯其专利权、商标权、著作权或其他知识产权的起诉。投标人保证所提供软件的合法性，所发生的任何知识产权纠纷与采购人无关。
2. 采购人购买产品后，有权对该产品与其他设备进行配套、整合或适当改进，而免受侵犯专利权的起诉。
10其他要求1. 投标人应按其投标文件中的承诺，进行其他售后服务工作。
★2. 投标人所投产品（台式彩色 B 超机（含工作站）），必须提供医疗器械注册证书（或者备案凭证）扫描件，原件备查。开标时，该证应在有效期内，若不在有效期内，则需提供该证和所投产品在该证有效期内生产的药监局出具的证明文件。
★3.投标人提供本项目的投标授权代表（提供投标截止日前缴纳的近 1 个月（由于社保部门原因最近一个月的社保证明无法提供的可往前顺延一个月）的社保证明；如投标授权代表与本项目其他投标授权代
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_07.json b/diagrams-and-tables/annotations/cn_simple_table_07.json new file mode 100644 index 0000000000000000000000000000000000000000..f818b191607266fb75e330823530cf8b192e710b --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_07.json @@ -0,0 +1,30 @@ +[ + { + "type": "text", + "text": "（1）开标仪式由招标人主持，在投标邀请函中规定的地点和时间开标。\n（2）开标时当众查验投标文件密封情况，确认无误后拆封。" + }, + { + "type": "title", + "text": "1. 评标" + }, + { + "type": "text", + "text": "（1）评标委员会：招标人将依照《中华人民共和国招标投标法》、国家计委等七部委制定的《评标委员会和评标方法暂行规定》、《北京大学招标采购管理办法》等法律法规的有关规定组建评标委员会；评标委员会成员由专家、用户代表等五人以上单数组成。\n（2）评标原则：评标委员会按照有关法律、法规规定和招标文件要求，遵循公平、公正、科学、择优的原则，采用相同的程序和标准，不受外界任何因素干扰和影响独立对投标文件进行评审。\n（3）评标主要内容：对投标文件的初审、质疑、综合评审、择优定标。具体内容：技术方案、综合商务、售后服务及投标报价。\n（4）评标办法：本次招标采用综合评分法，是指在最大限度地满足招标文件实质性要求前提下，按照招标文件中规定的各项因素进行综合评审后，以评标总得分最高的投标人作为中标候选供应商。\n（5）评分因素（总分 100 分）：\n分为 4 个部分：投标报价 30 分、综合商务 15 分、技术方案 50 分、售后服务 5 分。\n1）投标报价部分（30 分）的评分细则如下：" + }, + { + "type": "table", + "html": "
评分说明
报价高出本项目预算的投标书为废标。
鉴于本项目软件开发的难度和进度要求，为确保投标人能够派出综合能力最强的开发团队来确保本项目的开发进度和开发质量，避免恶意低价投标，因此，最低投标报价的报价分不一定是最低。
有效报价指的是不高于预算 100%也不低于预算 65%的投标价。
基准价指的是有效报价的算术平均值。若没有有效报价，则基准价为预算的 80%。
基准分为 30 分。基准价对应的报价分值为基准分。投标价每低于或高于基准价 1%，其报价分值为基准分减 1 分。
价格分最低为 0 分，最高分为 30 分。报价分保留 2 位小数。
" + }, + { + "type": "text", + "text": "2）综合商务部分（15 分）的评分细则如下：" + }, + { + "type": "table", + "html": "
评分指标评分说明最高分值
1、注册资本（2）公司注册资本在 3000 万以上的得 2 分，在 500-3000 万的得 1 分，其余得 0 分2
2、公司资质（2）具有 ISO9000 质量体系管理认证或 CMM3 以上认证资格1
同时具有高新技术企业证书和软件企业认定证书1
3、标书完整性（2）提供的各种资格/证明文件没有缺漏项，齐全有效1
投标书内容（包括应答书在内）没有缺漏项，齐全有效1
" + }, + { + "type": "page_number", + "text": "1" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_08.json b/diagrams-and-tables/annotations/cn_simple_table_08.json new file mode 100644 index 0000000000000000000000000000000000000000..f3fe8009c5cc49516669a8242f62dfb250870c51 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_08.json @@ -0,0 +1,22 @@ +[ + { + "type": "header", + "text": "招标编号：2011[46]\t北京大学实验室与设备管理部" + }, + { + "type": "table", + "html": "
4、投标人业绩（4）投标人员绩以提供的合同复印件为准：（1）每提供一个图书馆/博物馆相关行业的应用软件技术开发服务合同案例加 1 分；（2）每提供一个其他行业的但合同额不低于 200 万元的应用软件开发合同案例加 1 分，该类合同案例累计最多加 2 分；（3）其他合同不加分。累计加分超过 4 分时按 4 分计。4
5、项目人员资质（5）项目经理具有项目管理（PMP）证书或者国家认可的高级技术职称证书的、并拥有 2 个以上软件开发项目成功案例的、具有 8 年以上开发与管理经验的得 2 分，否则不得分；2
从为本项目配备的开发人员数、开发人员从业资质和能力、开发过类似项目的经验、相关技术积累等方面对项目开发团队的综合能力进行考察：团队综合能力优秀的得 3 分，综合能力很强的得 2 分，综合能力次之的得 1-0 分。3
" + }, + { + "type": "text", + "text": "3）技术方案部分（50 分）的评分细则如下：" + }, + { + "type": "table", + "html": "
评分指标评分说明最高分值
1、需求分析完整性和合理性（10）需求理解完整、清晰、准确2
系统功能性需求分析及用例需求完整、正确4
非功能性需求完整、正确2
需求分析创新程度（对招标技术要求增加了合理和必要的需求）2
2、系统设计完整性和合理性（18）系统总体设计完整、正确，采用分层设计，各层次调用清晰，不跨层调用5
系统详细功能设计完整、正确6
数据库设计、关键数据结构与配置文件设计的完整、正确5
设计方案创新性（对招标技术要求增加了合理和必要的功能）2
3、系统关键性设计（3）系统所用开发框架、数据库、搜索引擎等全部来自开源项目而没有采用投标人私有软件平台1
系统采用插件式结构设计并具有自动升级和扩展能力1
系统采用 Hudson 进行持续集成1
4、系统集成性（4）应用系统集成方案的全面、合理和正确2
系统提供完整的接口，支持多种客户端2
5、系统安全性（2）从系统物理安全、信息安全、数据安全以及系统安全管理等各个方面阐述了系统的安全性2
6、系统测试（4）采用 Junit 进行单元测试1
完整的集成测试管理流程1
完整的测试验收标准2
7、项目管理与实施方案（6）项目开发和测试的项目管理、质量管理和实施方案的完整性、合理性2
能提供各个阶段的系统原型，以供用户提出评审2
给出了详细的项目实施进度计划，非常合理，能确保按时完成2
8、整体技术方案可行性（3）具有很高的可操作性，能够有效保证项目能够如期完成3
" + }, + { + "type": "page_number", + "text": "2" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_09.json b/diagrams-and-tables/annotations/cn_simple_table_09.json new file mode 100644 index 0000000000000000000000000000000000000000..70d1229865a31e64a53708302782863cd2e43daa --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_09.json @@ -0,0 +1,30 @@ +[ + { + "type": "header", + "text": "招标编号：2011[46]\t北京大学实验室与设备管理部" + }, + { + "type": "title", + "text": "2.1. 系统接口和相关标准规范" + }, + { + "type": "text", + "text": "教参系统共享版向 calis 其它系统提供的接口：" + }, + { + "type": "table", + "html": "
接口类型说明
统一检索服务接口包含提交查询请求、获取检索结果列表等方法，支持统一认证
个性化服务接口与个人空间相关的接口，供 CALIS 个性化门户系统中的 gadget 组件进行调用，支持统一认证
教学参考信息提供接口向教参中心系统、移动客户端（支持 IOS 或 android 的移动终端）提供教学参考信息和教学参考书信息以及相关链接。
适配器同步数据处理接口与 calis Nserver 的接口，具体参见 calis 适配器同步数据处理接口规范
开馆接口与 calis Nserver 的接口，具体参见 calis 开馆接口规范
RSS 接口向其他子系统或用户提供资源更新的信息。
FETCH 接口通过此接口获取全文电子书在共享域或租用馆本地电子书管理系统中的 URL 链接地址
数据导出接口按 CALIS 统一数据交换系统要求，导出教参数据。
E-learning 接口由 E-learning 系统调用该接口，获取相关资源信息，包括相关教材/教参书信息（含全文 URL 链接地址）、国内相关课程信息（含课程 URL 链接地址）、国外相关课程信息（含课程 URL 链接地址）等。
elearning 请求接口由 E-learning 系统向本系统提交相关电子资源链接请求；
其他接口等
" + }, + { + "type": "text", + "text": "教参系统共享版用到的由其它系统提供的接口：" + }, + { + "type": "table", + "html": "
接口类型说明提供方
统一认证系统接口通过 CALIS 统一认证共享版对用户进行身份认证和授权验证。CALIS 统一认证共享版
馆际互借系统接口向 CALIS 其它子系统提供资源馆际互借请求接口CALIS 馆际互借共享版
" + }, + { + "type": "page_number", + "text": "4" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_10.json b/diagrams-and-tables/annotations/cn_simple_table_10.json new file mode 100644 index 0000000000000000000000000000000000000000..c6a0b8b9f322139126c5ddda659c8c94927b1d84 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_10.json @@ -0,0 +1,14 @@ +[ + { + "type": "table", + "html": "
与资源调度系统的接口通过资源调度系统提供查看 CALIS 联机编目收藏情况、查看租用馆本地馆藏、查看电子书全文以及发送馆际互借请求的服务。CALIS 资源调度系统
CVRS 接口通过该接口可以发送咨询请求到租用馆咨询台或 CVRS 中心虚拟参考咨询台。CALIS 参考咨询系统共享版
FETCH 接口通过此接口获取全文电子书在教参中心系统电子书管理系统中的 URL 链接地址CALIS 教参中心系统
第三方电子书系统
国外课程信息接口和国外教参书信息接口通过此接口，引导用户查看教参中心系统的相关信息CALIS 教参中心系统
OPAC 接口获取租用馆的本地动态馆藏租用馆本地 OPAC
E-learning 接口通过此接口，教参系统共享版能获得 E-learning 系统中的课程信息E-learning 系统
其他接口等
" + }, + { + "type": "text", + "text": "教参系统共享版应支持的标准规范：\nCALIS ODL-MAP 协议规范\nCALIS 数字对象唯一标识符本地解析规范\nOpenURL 标准\nCALIS 资源名称规范表\nCALIS 日志设计统计系统参考\nCALIS_OAI 记录格式与发布规范\nCALIS_METS 包结构规范\nCALIS 常规资源 METS 包结构规范\nCALIS 数字对象唯一标识符本地解析规范\nCALIS 数字对象唯一标识符参考实现方案\nCALIS 统一交换平台交换格式说明_教参格式\nCALIS 统一认证接口规范" + }, + { + "type": "page_number", + "text": "5" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_11.json b/diagrams-and-tables/annotations/cn_simple_table_11.json new file mode 100644 index 0000000000000000000000000000000000000000..3a6f0a1a2da6178408d96c90ee02f1b5fe69f140 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_11.json @@ -0,0 +1,34 @@ +[ + { + "type": "header", + "text": "招标编号：2011[46]" + }, + { + "type": "header", + "text": "北京大学实验室与设备管理部" + }, + { + "type": "text", + "text": "基础数据维护：为了保证系统运行完整性、解决馆员重复录入、规范录入取值，馆员可在此进行基础数据的维护。包括：系统提示信息维护、基础数据维护等。\n服务管理：通过该模块，馆员对各个服务内容相关数据进行管理和维护。包括资源收藏标签管理、读者反馈信息管理、FAQ 管理、RSS 订阅管理、公共信息管理。\n接口管理：馆员可以设置各个接口的状态（是否开放）、接口开放条件（IP 限制）、以及必要的接口参数维护。\n系统参数：如豆瓣书评服务链接、Google 图书链接等，设置按需出版社联系方式，可以设置网页的布局，如每页显示的最大记录数，显示字段（元素）的长度等。\n系统预置标准的学科分类、中图分类法等公用信息。与教参系统共享版中的公用信息一致。" + }, + { + "type": "title", + "text": "3.1. 系统接口和相关标准规范" + }, + { + "type": "text", + "text": "CALIS 教参中心系统向 calis 其它系统提供的接口：" + }, + { + "type": "table", + "html": "
接口类型说明
统一检索服务接口包含提交查询请求、获取检索结果列表等方法，支持统一认证
个性化服务接口与个人空间相关的接口，供 CALIS 个性化门户系统中的 gadget 组件进行调用，支持统一认证
教学参考信息提供接口向移动客户端（支持 IOS 或 android 的移动终端）提供教学参考信息和教学参考书信息。
适配器同步数据处理接口与 calis Nserver 的接口，具体参见 calis 适配器同步数据处理接口规范
RSS 接口向其他子系统或用户提供资源更新的信息。
FETCH 接口通过此接口获取全文电子书在教参中心系统电子书管理系统中的 URL 链接地址
数据导入、导出接口按 CALIS 统一数据交换系统要求，导入和导出教参数据。
其他接口等
" + }, + { + "type": "text", + "text": "CALIS 教参中心系统用到的由其它系统提供的接口：" + }, + { + "type": "page_number", + "text": "6" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_12.json b/diagrams-and-tables/annotations/cn_simple_table_12.json new file mode 100644 index 0000000000000000000000000000000000000000..b6a6dc8e311d500d5c5c6b1b2eb2f67ecf701f55 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_12.json @@ -0,0 +1,22 @@ +[ + { + "type": "header", + "text": "招标编号：2011[46]" + }, + { + "type": "header", + "text": "北京大学实验室与设备管理部" + }, + { + "type": "table", + "html": "
接口类型说明接口提供方
统一认证接口过 CALIS 认证中心对该用户进行身份认证和授权验证。统一认证中心系统
资源调度接口通过资源调度系统提供查看 CALIS 联机编目收藏情况、查看租用馆本地馆藏、查看电子书全文以及发送馆际互借请求的服务。CALIS 资源调度系统
CVRS 接口通过该接口可以发送咨询请求到租用馆咨询台或 CVRS 中心虚拟参考咨询台。CALIS 参考咨询系统共享版
馆际互借接口通过此接口推送馆际互借请求到用户的所属馆馆际互借系统CALIS 馆际互借共享版
FETCH 接口通过此接口获取全文电子书在共享域或租用馆本地电子书管理系统中的 URL 链接地址教参系统共享版 第三方电子书系统
国外教参书网站的电子书访问接口通过此接口，下载“国外教参书网站“中的电子书国外教参书网站
国外课程信息访问接口通过此接口，下载国外课程信息国外课程网站
其他接口等
" + }, + { + "type": "text", + "text": "CALIS 教参中心系统应支持的标准规范：\nCALIS ODL-MAP 协议规范\nCALIS 数字对象唯一标识符本地解析规范\nOpenURL 标准\nCALIS 资源名称规范表\nCALIS 日志设计统计系统参考\nCALIS_OAI 记录格式与发布规范\nCALIS_METS 包结构规范" + }, + { + "type": "page_number", + "text": "7" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_13.json b/diagrams-and-tables/annotations/cn_simple_table_13.json new file mode 100644 index 0000000000000000000000000000000000000000..2990067bb1218494807a7e77e1b6bc654fc2d152 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_13.json @@ -0,0 +1,22 @@ +[ + { + "type": "header", + "text": "招标编号：2011[46]\t北京大学实验室与设备管理部" + }, + { + "type": "text", + "text": "✧ 可以自动为上传的高精度图片生成多种不同精度的用于网上浏览的图像。\n用于网上浏览的图像对象分为 3 级：" + }, + { + "type": "table", + "html": "
精细浏览级在本文件中用字母 L 表示。供普通读者网上访问，可下载和打印。屏 显尺寸相对较大，长边像素 2000 左右。以 JPEG/JFIF/PNG 格式保存， 中度压缩。文件在 250K 以下。
普通浏览级在本文件中用字母 M 表示。供一般读者网上访问，可任意下载，打印。 通常以屏幕显示尺寸为度（宽<=1024； 高<=768）以 JPEG/JFIF/PNG 格 式保存，高度压缩。文件在 100K 以下。
袖珍浏览级在本文件中用字母 S 表示。缩略图。72 DPI（宽<=120； 高<=90）以 256 色的 GIF 或高度压缩的 JPEG 格式保存。文件在 20K 以下。
" + }, + { + "type": "text", + "text": "元数据审校：元数据编辑后可以“提交审校”，由审校人员对提交审校的元数据进行审校。审校通过可以提交入正式库。入正式库要进行数据查重。\n对毕业生在线提交的论文，则需单独进行审核，审核过程中，还能同时修改和完善已有的元数据内容，审核通过后再进行论文格式的转换和前 N 页的抽取，分配唯一标识符等。\n对回溯学位论文论文和纸本图书的加工，则按正常的纸本资源加工流程进行处理。\n数字对象有效性的检查：系统支持 MD5 校验，可以为每一个存储其中的文件产生一 个 MD5 校验和，利用这个校验和来验证一个文件的完整性。对于本地存储的文件将生成 MD5 校验和，而对于远程存储只是对文件名进行 MD5 校验。\n数字对象批量挂接：系统根据馆员指定的一组数字对象存在位置，依据元数据 ID 与数字对象名称对照表，对数字对象进行批量挂接。挂接过程中可以进行数字对象的有效性检查与数字对象加工。\n当馆员针对某条元数据进行编辑或审校，系统会自动给该条元数据标记锁定，防止其它人再对其操作。故会存在死锁状态。当馆员登录系统后，如果存在上次操作时存留的未释放锁定元数据，系统将自动弹出提醒窗口。\n资源加工环节总体要求：\n✧ 要求遵循 CALIS 对资源的元数据标准及著录规则\n✧ 一条元数据可以对应多个数字对象\n✧ 支持多种元数据格式批量导入\n✧ 数字对象批量挂接" + }, + { + "type": "page_number", + "text": "8" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_14.json b/diagrams-and-tables/annotations/cn_simple_table_14.json new file mode 100644 index 0000000000000000000000000000000000000000..1f26e5ac4d839f35c44a6dbfde7984ee7effc4cd --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_14.json @@ -0,0 +1,14 @@ +[ + { + "type": "header", + "text": "招标编号：2011[46] 北京大学实验室与设备管理部" + }, + { + "type": "table", + "html": "
02_CALIS 数字对象唯一标识符命名规范.doc
03_CALIS 信息资源名称规范列表.doc
04_CALIS_OAI 记录格式与发布规范.doc
05_CALIS_METS 结构规范.doc
06_CALIS 常规资源 METS 包结构规范.doc
07_CALIS 数字对象唯一标识符本地解析规范.doc
08_CALIS 数字对象唯一标识符参考实现方案.doc
09_CALIS_OAI 数据供应服务器参考实现方案.doc
10_CALIS_OAI 数据供应服务器记录查询接口规范.doc
11_CALIS_OAI 与 METS 数据导出规范.doc
12_CALIS 特色库元数据著录规则概览.doc
13_CALIS 特色库私有元数据格式向核心扩展集格式的映射规则.doc
14_CALIS 特色库仓储部署指导要求.doc
15_CALIS 特色库与学位论文本地系统数据质量检查模块模式一功能规范.doc
16_CALIS 特色库与学位论文本地系统数据质量检查模块模式二功能规范.doc
17_CALIS 特色库与学位论文本地系统数据质量检查模块错误代码列表.doc
18_CALIS 特色库与学位论文本地系统数据发布模式比较.doc
19_CALIS 学位论文元数据著录规则概览.doc
20_CALIS 统一交换平台交换格式说明_特色库本地格式_v0.1.doc
21_CALIS 统一认证接口规范.htm
22_CALIS 应用系统与统一认证系统集成规范.htm
2CALIS 应用系统集成改造规范CALIS 应用系统 SaaS 化改造规范_V1.30.htm
CALIS 应用系统 SaaS 化改造评审表_V1.30.doc
CALIS 应用系统统一接口服务规范_V1.0.doc
CALIS 统一认证系统集成改造规范_V1.2.htm
3CALIS 元数据规范CDLS-S05-013 古籍元数据规范.pdf
CDLS-S05-014 古籍著录规则.pdf
CDLS-S05-015 家谱元数据规范.pdf
CDLS-S05-016 家谱著录规则.pdf
CDLS-S05-017 拓片元数据规范.pdf
CDLS-S05-018 拓片著录规则.pdf
CDLS-S05-019 舆图元数据规范.pdf
CDLS-S05-020 舆图著录规则.pdf
CDLS-S05-021 地方志元数据规范.pdf
CDLS-S05-022 地方志著录规则.pdf
CDLS-S05-023 期刊论文元数据规范.pdf
CDLS-S05-024 期刊论文元数据著录规则.pdf
CDLS-S05-025 会议论文元数据规范.pdf
" + }, + { + "type": "page_number", + "text": "10" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_15.json b/diagrams-and-tables/annotations/cn_simple_table_15.json new file mode 100644 index 0000000000000000000000000000000000000000..b8a2ddbc72023a3fc908fea270dbbf6e904e6577 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_15.json @@ -0,0 +1,22 @@ +[ + { + "type": "header", + "text": "招标编号：2011[46] 北京大学实验室与设备管理部" + }, + { + "type": "table", + "html": "
CDLS-S05-026 会议论文著录规则.pdf
CDLS-S05-027 学位论文元数据规范.pdf
CDLS-S05-028 学位论文著录规则.pdf
CDLS-S05-029 电子图书元数据规范.pdf
CDLS-S05-030 电子图书著录规则.pdf
CDLS-S05-031 音频资料元数据规范.pdf
CDLS-S05-032 音频资料著录规则.pdf
CDLS-S05-033 网络资源元数据规范.pdf
CDLS-S05-034 网络资源著录规则.pdf
4相关元数据 schema含有各类元数据 schema 的参考文件
5其他方正德赛数据加工系统 4.1 数据格式参考.docx
方正德赛数据加工系统接口说明.docx
" + }, + { + "type": "title", + "text": "2. 性能需求" + }, + { + "type": "text", + "text": "对性能的总体要求：可靠、响应迅速、高效、可扩展、健壮。
可靠是指特色库系统共享版的服务在任何时间或者几乎所有时间都可以被利用，该服务应该是安全的，即使在磁盘发生故障或安全被破坏时也不会丢失资料；响应迅速则指终端用户和管理人员都可迅速地浏览、搜索和维护；高效的服务可以最大化地利用可得的硬件和网络资源；可扩展是指可以很好地解决用户数量的增长、数据库规模的扩大和服务项目的增加问题；健壮是指系统运行稳定。
特色库系统共享版应满足以下要求：
1、时间特性要求：数据记录达到 500 万条、web 并发用户达到 100 个时，web 服务器的数据检索响应时间应小于 3 秒。数据的转换、元数据的收割、文件传送及上下载要求响应迅速。
2、灵活性/稳定性：软件要具有较好的灵活性，强调在数据处理及多用户浏览过程中的稳定性。
3、数据管理能力要求：一套系统应能容纳不少于 500 个租用馆，每个馆的资源库数量不少于 100 个，所有资源库的数据总量不低于 1000 万条资源记录，要求全文检索引擎支持上述数据容量，要求在数据库达到最大数据量时系统仍可保证速度、正常运行。为此，系统应提供多机负载均衡的部署能力。
4、故障处理要求：具有数据备份和恢复功能，故障后能迅速恢复系统运行。
系统其他指标：
1、易于使用：Web 界面要求美观，富有人性化。支持主流的浏览器如 IE、Firefox" + }, + { + "type": "page_number", + "text": "11" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_16.json b/diagrams-and-tables/annotations/cn_simple_table_16.json new file mode 100644 index 0000000000000000000000000000000000000000..d9dfd636ff4a3549a23607560880594141e28a22 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_16.json @@ -0,0 +1,6 @@ +[ + { + "type": "table", + "html": "
9电子寄存柜软件必须支持校园内一卡一箱，不能一卡多箱，支持随存随取及固定箱位两种模式。1. 自助寄存柜为电脑联网型：即能够通过自身的以太网接口与系统的电脑通过 TCP/IP 协议进行数据交换，能够与校一卡通相结合，学生通过校园卡完成自助存取包过程。
2、一卡通要求：能与校一卡通系统相结合，并根据校一卡通系统需求开发相关软件接口，自助寄存柜能够与校一卡通数据库相结合，并通过计算机进行控制，与寄存柜使用信息进行实时交互并检测使用的合法性，达到对电子寄存柜系统的安全、合理、便捷而高效的管理。
3、联网系统软件能对存、取行为进行实时监控、记录，并提供完备的数据库以实现对历史、当前存取行为、存取箱号和存取时间等数据进行复合查询和统计等功能。
4、联网软件有存取记录统计功能，报表统计功能，能够对存取记录进行查询（如学生姓名、班级、存取时间等），并且能够导出 EXCEL 打印；
5、有挂失功能，能对丢失智能卡进行挂失，通过挂失后该卡不能再进行存取。支持一卡通基础平台挂失，一卡通基础平台挂失后，寄存柜软件将对挂失卡进行自动挂失
6、联网软件图形界面能够清晰地显示箱门的使用状态、如：空闲、使用、非法存物、超时、故障。
7、B/S 远程记录查询功能：支持分布式计算机查询系统，可以在同一网络环境下，通过 IE 浏览器，对寄存柜存取记录进行查询。		套1
10电子寄存柜柜体1、柜体选用 δ=1mm 冷轧板经冷加工成形后，用氩弧焊接装配而成，表面经除锈除油磷化处理后喷塑，塑面的颜色可由用户选定；底板=1.50mm 冷轧钢板；
2、每组 24 门柜，每箱格尺寸 324.5×335×643.3（宽×深×高），2900×335×2030（宽×深×高）		组50
11电子寄存柜电气控制器1、24 门寄存柜专用控制器
2、通讯方式支持 RS485、TCP/IP、无线 WIFI
3、网络采用主从控制方式，系统主机有故障后，各单元柜仍可对已授权存物的校园卡进行取物工作，单元柜中某箱出故障后，不影响其他箱的使用。
4、电源电压：AC220V		台50
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_17.json b/diagrams-and-tables/annotations/cn_simple_table_17.json new file mode 100644 index 0000000000000000000000000000000000000000..a213f6ffb9d9d6bbb88f52dcfc298a95480666ed --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_17.json @@ -0,0 +1,18 @@ +[ + { + "type": "table", + "html": "
21室内双频 AP支持 IEEE 802.11a/n 和 b/g/n (同时开启)
2.400 - 2.4835 GHz，5.725 - 5.850 GHz
支持 IPv4/IPv6 双栈协议，支持在纯 IPv6 网络中部署
1x10/100/1000BASE-T Ethernet (RJ-45)
集成内置天线
支持 PoE 供电
包含安装附件 (也可单报)		个110
226 类非屏蔽双绞线国内外知名品牌，如康普、安普等箱50
2324 口 POE 交换机24 口，知名品牌，支持本项目 AP台6
2448 口 POE 交换机48 口，知名品牌，支持本项目 AP台3
25六类配线架国内外知名品牌个10
26六类非屏蔽模块国内外知名品牌个110
27六类跳线国内外知名品牌根220
28单模光纤跳线国内外知名品牌条10
29配套光纤模块国内外知名品牌个12
30服务器机架
>=双核，2.2GHz
DDR3,32G
>=6 硬盘、RAID5,
容量>=4t		台2
31一卡通工作站一体机，双核,4G,22',1t台6
32调试笔记本14 寸，4G,500GB,>=I3台6
" + }, + { + "type": "title", + "text": "包三：软件系统" + }, + { + "type": "table", + "html": "
北京大学附属中学数字化校园建设序号系统名称数量
1基础数据库与管理平台1 套
2学校协同办公系统1 套
3个人信息门户1 套
注：拥有证书的，须提供软件著作权登记证书复印件加盖公章。
" + }, + { + "type": "table", + "html": "
主模块子模块描述
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_18.json b/diagrams-and-tables/annotations/cn_simple_table_18.json new file mode 100644 index 0000000000000000000000000000000000000000..b547b50f5b593b0ca4d4848e55592f86d4ba1ba5 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_18.json @@ -0,0 +1,18 @@ +[ + { + "type": "header", + "text": "中钢招标有限责任公司" + }, + { + "type": "title", + "text": "投标人须知资料表" + }, + { + "type": "text", + "text": "本表是对投标人须知的具体补充和修改，如有矛盾，均以本资料表为准。标记“■”的选项意为适用于本项目，标记“□”的选项意为不适用于本项目。" + }, + { + "type": "table", + "html": "
条款号条目内容
1.3联合体为了便于采购活动开展，如本项目接受联合体，建议以联合体形式参与采购活动的供应商，在联合体确定后，尽早通知代理机构。
2.2项目属性项目属性：
■服务
□货物
2.3科研仪器设备是否属于科研仪器设备采购项目：
□是
■否
2.4核心产品■关于核心产品本项目不适用。
□本项目_包为单一产品采购项目。
□本项目_包为非单一产品采购项目，核心产品为：____。
3.1现场考察■不组织
□组织，考察时间：__年_月_日_点_分（招标文件提供期限截止后）
考察地点：____________。
开标前答疑会■不召开
□召开，召开时间：__年_月_日_点_分
召开地点：____________。
3.3演示视频演示视频：
■无需递交
□递交，投标人可以用【U盘/光盘】形式随投标文件一并递交不超过【____】分钟的演示视频（演示视频具体内容详见本招标文件【《第四章 评标程序、评标方法和评标标准》】/《第五章 采购需求》】相关规定），供代理机构在评标时向评标委员会播放。播放格式为avi、mp4、rmvb、wmv其中一种格式，视频应配有讲解音频。如果演示视频超过招标文件规定时间则超出部分不再播放。如因投标人所递交的视频文件出现错误，导致评标委员会无法对此部分顺利进行评审，造成的后果由投标人自行承担，且对应评分项不得分。
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_19.json b/diagrams-and-tables/annotations/cn_simple_table_19.json new file mode 100644 index 0000000000000000000000000000000000000000..a9d5c5204dbe614080793bbab68d0ad51ffb4526 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_19.json @@ -0,0 +1,10 @@ +[ + { + "type": "table", + "html": "
条款号条目内容
22.2最多中标包数量的限制如投标人对本项目的多个包同时进行投标，则投标人在本项目中最多中标包的数量：
■不限制；
□限制。具体规定如下：
25.5分包本项目的非主体、非关键性工作是否允许分包：
□不适用
■不允许
□允许，具体要求：
（1）可以分包履行的具体内容：____；
（2）允许分包的金额或者比例：____；
（3）其他要求：
1）分包承担主体应具备的资质条件：无。（如有特殊资质要求据实填写）
2）若项目或相关采购包要求通过分包措施预留部分采购份额面向中小企业采购、且投标人因落实政府采购政策拟进行分包的，须按本招标文件第七章《投标文件格式》一、资格证明文件格式第 2-2 项及其附件提交投标文件相应内容；非因以上原因而允许分包、且投标人拟进行分包的，须按本招标文件第七章《投标文件格式》二、商务技术文件格式第 8 项提交投标文件相应内容。
3）依据《政府采购促进中小企业发展管理办法》（财库（2020）46 号）文件规定享受扶持政策获得政府采购合同的，小微企业不得将合同分包给大中型企业，中型企业不得将合同分包给大型企业。
4）分包承担主体不得再次分包。
26.1.1询问询问送达形式：书面形式。
26.3联系方式接收询问和质疑的联系方式：
同第一章《投标邀请》中“项目问询”联系方式。
" + }, + { + "type": "page_number", + "text": "4" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_20.json b/diagrams-and-tables/annotations/cn_simple_table_20.json new file mode 100644 index 0000000000000000000000000000000000000000..3b984a0c0472aefc465e97a1cf562d8e04098492 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_20.json @@ -0,0 +1,30 @@ +[ + { + "type": "title", + "text": "一、评标方法" + }, + { + "type": "text", + "text": "1 投标文件的符合性审查" + }, + { + "type": "text", + "text": "1.1 评标委员会对资格审查合格的投标人的投标文件进行符合性审查，以确定其是否满足招标文件的实质性要求。" + }, + { + "type": "text", + "text": "1.2 评标委员会根据《符合性审查要求》中规定的审查因素和审查内容，对投标人的投标文件是否实质上响应招标文件进行符合性审查，并形成符合性审查评审结果。投标人《商务技术文件》有任何一项不符合《符合性审查要求》要求的，投标无效。" + }, + { + "type": "title", + "text": "符合性审查要求" + }, + { + "type": "table", + "html": "
序号审查因素审查内容
1授权委托书按招标文件要求提供授权委托书；
2投标完整性未将一个采购包中的内容拆开投标；
3投标报价投标报价未超过招标文件中规定的项目/采购包预算金额或者项目/采购包最高限价；
4报价唯一性投标文件未出现可选择性或可调整的报价（招标文件另有规定的除外）；
5投标有效期投标文件中承诺的投标有效期满足招标文件中载明的投标有效期的；
6实质性格式标记为“实质性格式”的文件均按招标文件要求提供且签署、盖章的；
7★号条款响应投标文件满足招标文件第五章《采购需求》中★号条款要求的；
8拟分包情况说明（如有）如本项目（包）非因“落实政府采购政策”亦允许分包，且供应商拟进行分包时，必须提供；否则无须提供；
9分包承担主体资质（如有）分包承担主体具备《投标人须知资料表》载明的资质条件且提供了资质证书复印件（如有）；
10报价的修正（如有）不涉及报价修正，或投标文件报价出现前后不一致时，投标人对修正后的报价予以确认；（如有）
11报价合理性报价合理，或投标人的报价明显低于其他通过符合性审查投标人的报价，有可能影响产品质量或者不能诚信履约的，能够应评标委员会要求在规定时间内证明其报价合理性的；
12进口产品（如有）招标文件不接受进口产品投标的内容时，投标人所投产品非进口产品的；
" + }, + { + "type": "page_number", + "text": "11" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_21.json b/diagrams-and-tables/annotations/cn_simple_table_21.json new file mode 100644 index 0000000000000000000000000000000000000000..f6f9566eff64bda274246b894001d5460c6d8cb7 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_21.json @@ -0,0 +1,10 @@ +[ + { + "type": "table", + "html": "
护手段，具备双向不同物理路由及自动切换功能。已具备条件得4分；不具备得0分。
4平滑迁移方案4有详细的迁移方案，能够在不影响现有网络、系统稳定运行的基础上，将网络平滑迁移。迁移期间，网络中断时长不大于2小时。满足的得4分；不满足得0分。
5技术指标响应性16投标文件对招标文件第五章采购需求中“电路安全可靠性要求、采用的接入设备要求、基于SDH的以太网专线性能指标要求、扩展性要求、网管要求、过渡期要求、项目实施要求、运行服务要求”8大项内容进行响应，每有一项负偏离，本项扣2分。全部无负偏离得16分。
6项目实施方案4方案内容完整、描述具体详实的，得4分；方案内容完整、但描述不够具体详实的，得2分；方案内容不够完整、描述不够具体详实的，得1分；方案存在重大缺陷或未提供方案的，得0分。
4方案可实施性高的，得4分；方案具有一定的可实施性的，得2分；方案可实施性欠佳的，得1分；方案可实施性存在重大缺陷或未提供方案的，得0分。
4方案针对性高的，得4分；方案具有一定的针对性的，得2分；方案针对性欠佳的，得1分；方案针对性存在重大缺陷或未提供方案的，得0分。
7运行服务方案4方案内容完整、描述具体详实的，得4分；方案内容完整、但描述不够具体详实的，得2分；方案内容不够完整、描述不够具体详实的，得1分；方案存在重大缺陷或未提供方案的，得0分。
4方案可实施性高的，得4分；方案具有一定的可实施性的，得2分；方案可实施性欠佳的，得1分；方案可实施性存在重大缺陷或未提供方案的，得0分。
" + }, + { + "type": "page_number", + "text": "14" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_22.json b/diagrams-and-tables/annotations/cn_simple_table_22.json new file mode 100644 index 0000000000000000000000000000000000000000..d807c58627b91e34f3462812132f933387b0ae12 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_22.json @@ -0,0 +1,30 @@ +[ + { + "type": "header", + "text": "项目名称：《中华医学杂志》社有限责任公司知识服务和运营服务平台建设\n招标编号：CMAYB-2019010" + }, + { + "type": "title", + "text": "第五部分 评分标准" + }, + { + "type": "title", + "text": "1. 总则" + }, + { + "type": "text", + "text": "评标委员会将仅对在实质上响应招标文件要求的投标文件进行评价和比较。投标文件的评价采用综合评分法，评分按商务、技术和价格三部分分别打分的方式进行。其中商务和技术分满分为 80 分，价格分满分为 20 分。投标人的投标综合评分为两项得分之和，满分为 100 分。" + }, + { + "type": "title", + "text": "2. 评分细则" + }, + { + "type": "table", + "html": "
内容评分因素分项评分标准分值
商务部分（40 分）投标文件编制投标文件制作规范，应答清晰，印制清楚，装订整齐，得 5 分，否则得 0 分。5
投标人认证证书1. 投标人具有软件企业认证证书，需提供证书复印件并加盖投标人公章，满足得 1 分，否则得 0 分。
2. 投标人具有市级或省级（含）以上单位颁发的高新技术企业证书，需提供证书复印件并加盖投标人公章，满足得 1 分，否则得 0 分。
3. 投标人具有 ISO9001 质量管理体系认证证书复印件并加盖投标人公章，满足得 1 分，否则得 0 分。
4. 投标人具有 ISO27001 信息安全管理体系认证证书复印件并加盖投标人公章，满足得 1 分，否则得 0 分。
5. 投标人具有 ITSS 信息技术服务标准认定证书的得 1 分，没有得 0 分。
6. 投标人具有类似行业的数据库建设相关功能模块的软件著作权登记证书或专利的，每提供一个得 1 分，最高得 4 分。		9
" + }, + { + "type": "page_number", + "text": "25" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_23.json b/diagrams-and-tables/annotations/cn_simple_table_23.json new file mode 100644 index 0000000000000000000000000000000000000000..af20ba210e4885736b54e8fdcd8112d03ce3a9b8 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_23.json @@ -0,0 +1,14 @@ +[ + { + "type": "header", + "text": "项目名称：《中华医学杂志》社有限责任公司知识服务和运营服务平台建设\n招标编号：CMAYB-2019010" + }, + { + "type": "table", + "html": "
业绩案例投标人业绩：2016 年 1 月 1 日（含）以来具有类似行业的数据库建设合同业绩，合同金额达到 100 万元（含）以上，每提供一个满足要求的案例得 2 分，合同金额达到 1000 万元（含）以上的案例额外加 2 分，最高得 16 分（案例不重复计算）。
注：提供案例合同首页、金额页、显示项目名称页、显示项目内容页和签署页的复印件（加盖投标人公章）、项目内容简介（加盖投标人公章）。如果上述材料不能证明为所要求的开发案例，则需要由用户单位出具案例证明材料（包括合同金额及项目内容简介，加盖用户单位章）。		16
数据库对接服务有否与以下数据库或服务有过数据对接或定向研发的经验，每项得 1 分，最高 10 分：
CSCD、PubMed、SinoMed、WOS、万方数据库、中国知网、超星发现、维普数据、百度学术、谷歌学术、altmetrics、trendMD、OICID。
注：提供取得对接的项目名称或案例截图，被动数据收割不属于数据对接范围。		10
技术部分40 分项目需求理解评价根据投标人各类业务功能需求的实质性响应程度，是否全面理解业务需求进行评价。其中理解全面，实质性响应程度好得 5 分；理解较好、响应程度较好得 3 分；理解和响应程度与需求有一定差距得 1 分；未提供得 0 分。5
" + }, + { + "type": "page_number", + "text": "26" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_24.json b/diagrams-and-tables/annotations/cn_simple_table_24.json new file mode 100644 index 0000000000000000000000000000000000000000..06ebcd1d37ce59ebebdd6eda3744dea860fe8ce7 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_24.json @@ -0,0 +1,14 @@ +[ + { + "type": "header", + "text": "项目名称：《中华医学杂志》社有限责任公司知识服务和运营服务平台建设\n招标编号：CMAYB-2019010" + }, + { + "type": "table", + "html": "
总体技术方案响应总体评价对投标人总体技术方案及软件设计架构的合理性、先进性、完整性进行评价。其中技术方案先进、合理、完整，思路清晰，符合国家相关标准和规范；软件设计合理、架构完整先进、设计思路清晰，对需求分析详细、理解准确，充分满足需求的得 10 分；技术方案基本合理，符合国家相关标准和规范；软件结构层次较合理，思路较清晰，基本满足需求的得 6 分；技术方案欠缺、思路不够清晰、软件结构层次欠合理，无法满足需求的得 2 分；未提供 0 分。注：投标人需要详细提供研发团队技术框架的详细阐述说明，如无，本项不得分。10
项目实施方案投标人将实施进度分解到位，并对每一个步骤设立时间节点及进度保障措施，相关内容合理可行并优于招标文件要求的得 4 分，满足招标文件要求得 2 分，否则不得分。4
技术人员要求投标人提供完整的开发团队的名单及其分工职责，并提供团队成员投标截止前 3 个月内的社保缴纳凭证（复印件加盖投标人公章）得 3 分，部分的提供得 1 分。3
投标人开发团队的人数 10 人（含）以上的得 2 分，其中中高级工程师 5 人（含）以上的得 3 分。须提供相应职称证明复印件及工作内容介绍并加盖投标人公章，否则评审时不予认可。5
投标人项目经理、技术负责人 2016 年至今具有至少 2 项（含）科技期刊数字出版的项目研发经验的得 3 分。须提供项目业绩合同及相应人员在团队任职的证明文件复印件及工作内容介绍并加盖投标人公章，否则评审时不予认可。项目经理具有有效的高级项目经理证书或高级项目管理师证书或 PMP 证书，技术负责人具有高级系统分析师证书。（提供相关人员简历，相关资格证书复印件，否则不得分）3
" + }, + { + "type": "page_number", + "text": "27" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/cn_simple_table_25.json b/diagrams-and-tables/annotations/cn_simple_table_25.json new file mode 100644 index 0000000000000000000000000000000000000000..ba9b91f9e7a54958997b3195a4cff4055f009f35 --- /dev/null +++ b/diagrams-and-tables/annotations/cn_simple_table_25.json @@ -0,0 +1,14 @@ +[ + { + "type": "header", + "text": "项目名称：《中华医学杂志》社有限责任公司知识服务和运营服务平台建设\n招标编号：CMAYB-2019010" + }, + { + "type": "table", + "html": "
开发团队组成须包括有基于云服务研发经验的网络工程师。
提供 2 名（含）以上的具有云服务研发经验的网络工程师，须提供项目业绩合同及相应人员在团队任职的证明文件复印件、工作内容介绍及相关的资格证书加盖投标人公章，否则评审时不予认可。		3
投标人提供承诺，需求设计、系统设计、项目上线期间团队成员驻场开发。
提供承诺加盖投标人公章的得 3 分。		3
技术支持和售后服务投标人技术支持和售后服务方案满足第三部分技术需求书 5.6 售后服务需求，包括保修期，维保期内的服务内容、服务标准及培训的应答符合要求得 4 分，否则得 0 分。4
价格部分20 分投标报价满足招标文件要求且投标价格最低的投标报价为评标分项基准价，其价格为满分。
投标报价得分=（评标基准价/投标报价）×20×100%
注：价格分数保留两位小数。		20
" + }, + { + "type": "page_number", + "text": "28" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_01.json b/diagrams-and-tables/annotations/en_diagram_01.json new file mode 100644 index 0000000000000000000000000000000000000000..3f42babf1c260632b049c38b9f9d89c6bb3a83f4 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_01.json @@ -0,0 +1,149 @@ +[ + { + "type": "title", + "text": "Development Cooperation Charter and Japan's Development Cooperation" + }, + { + "type": "text", + "text": "Japan's development cooperation is founded on the Development Cooperation Charter 1 (revised by Cabinet decision on June 9, 2023). The Charter defines the objectives of Japan's development cooperation as follows: to work together with developing countries to address their development challenges and global issues common to all humankind through equal partnerships and contribute proactively to the creation of a peaceful, stable, and prosperous international community under a free and open international order based on the rule of law; and to contribute to the pursuit of Japan's national interests, such as the maintenance of peace and security for the country and its people and the achievement of further prosperity through economic growth, while developing a favorable international environment for Japan and the world, as well as preserving and strengthening foreign relations based on trust. The Official Development Assistance (ODA) is expected to serve ever more strategically and effectively as one of the most important foreign policy tools (see Part I, Section 1 on page 2 for the revision of the Development Cooperation Charter)." + }, + { + "type": "title", + "text": "1. Basic policies of the Development Cooperation Charter" + }, + { + "type": "text", + "text": "To achieve these objectives, the Development Cooperation Charter sets out the following four basic policies in development cooperation: \"contribution to peace and prosperity,\" \"human security in the new era,\" \"co-creation of social values through dialogue and collaboration with developing countries,\" and \"leadership in the dissemination and implementation of international rules and guidelines based on inclusiveness, transparency, and fairness.\"" + }, + { + "type": "title", + "text": "2. Priority issues of the Development Cooperation Charter" + }, + { + "type": "text", + "text": "In line with these basic policies, Japan pursues the following three policy priorities: \"'quality growth' in the new era and poverty eradication through such growth,\" \"the realization of a peaceful, secure, and stable society, and the maintenance and development of a free and open international order based on the rule of law,\" and \"leadership in international efforts to tackle increasingly complex and aggravated global issues.\"" + }, + { + "type": "diagram_caption", + "text": "Japan's ODA" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Bilateral Aid (including assistance through international organizations)" + }, + { + "id": "B", + "text": "Grants" + }, + { + "id": "C", + "text": "Government Loans, etc. (loan aid)" + }, + { + "id": "D", + "text": "Grant Aid" + }, + { + "id": "E", + "text": "Technical Cooperation" + }, + { + "id": "F", + "text": "ODA Loans" + }, + { + "id": "G", + "text": "Private-Sector Investment Finance (for the private sector)" + }, + { + "id": "H", + "text": "Multilateral Aid (contributions and subscriptions to international organizations, etc.)" + }, + { + "id": "I", + "text": "Grants" + }, + { + "id": "J", + "text": "Government Loans, etc. (loan aid)" + }, + { + "id": "K", + "text": "ODA" + } + ], + "relationships": [ + { + "source": "A", + "target": "K" + }, + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "C", + "target": "F" + }, + { + "source": "C", + "target": "G" + }, + { + "source": "H", + "target": "K" + }, + { + "source": "H", + "target": "I" + }, + { + "source": "H", + "target": "J" + } + ] + }, + { + "type": "title", + "text": "● What is ODA?" + }, + { + "type": "text", + "text": "Development cooperation refers to \"international cooperation activities that are conducted by the government and its affiliated agencies for the main purpose of development in developing regions\" (the Development Cooperation Charter), and ODA is the public funding for those activities. The government or its implementing agencies provide financial and technical assistance to developing regions, international organizations, or the private sector through ODA for \"development,\" including peacebuilding, governance, promotion of basic human rights, and humanitarian assistance.\nThe ODA recipients are presented in the list (see Chart II-10 on page 22) compiled by the Development Assistance Committee (DAC) of the Organisation for Economic Co-operation and Development (OECD)." + }, + { + "type": "title", + "text": "● What types of ODA exist?" + }, + { + "type": "text", + "text": "ODA can be categorized into grants and government loans, etc. (loan aid). ODA can also be grouped into bilateral aid, which directly assists developing regions, and multilateral aid, which concerns contributions and investments to international organizations, etc.\nGrants in bilateral aid are assistance provided to developing regions without repayment obligation. The grant scheme implemented by Japan is comprised of grant aid, which gives financial resources needed for the socio-economic development of developing regions without repayment obligation, and technical cooperation, which develops human resources that will be responsible for the socio-economic development of developing regions through the transfer of Japanese expertise, technology, and experience. Among contributions and investments to international organizations, contributions earmarked for specific countries and projects are accounted for as bilateral aid in statistics (see Chart II-1 on page 13).\nAdditionally, Japan's government loans, etc. (loan aid) in bilateral aid include ODA loans that lend the funds needed by developing regions on concessional terms, such as low interest rates and long repayment periods, and private-sector investment finance, which offers loans and investment to corporations and other private entities responsible for implementing projects in developing regions.\nMultilateral aid includes contributions and investments to the UN organizations, such as the United Nations Development Programme (UNDP) and the United Nations Children's Fund (UNICEF), international organizations, as well as multilateral financial institutions including the World Bank. Most of the contributions are provided as grants, but in recent years, government loans, etc. (loan aid) have also been used for multilateral financial institutions.\nVarious kinds of information about ODA are available on the Ministry of Foreign Affairs website. 2" + }, + { + "type": "footer", + "text": "1 Development Cooperation Charter https://www.mofa.go.jp/files/100514705.pdf. It can also be accessed via the 2D code on page vii.\n2 Various information on ODA https://www.mofa.go.jp/policy/oda/index.html. It can also be accessed via the 2D code on page vii." + }, + { + "type": "page_number", + "text": "vi" + }, + { + "type": "footer", + "text": "White Paper on Development Cooperation 2023" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_02.json b/diagrams-and-tables/annotations/en_diagram_02.json new file mode 100644 index 0000000000000000000000000000000000000000..abbbd805c34e5e71fe94c4dfed7c147898e4df85 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_02.json @@ -0,0 +1,161 @@ +[ + { + "type": "diagram_caption", + "text": "Figure 3: The three basic types of process mining explained in terms of input and output: (a) discovery, (b) conformance checking, and (c) enhancement." + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "(a)" + }, + { + "id": "B", + "text": "(b)" + }, + { + "id": "C", + "text": "(c)" + }, + { + "id": "D", + "text": "event log" + }, + { + "id": "E", + "text": "discovery" + }, + { + "id": "F", + "text": "model" + }, + { + "id": "G", + "text": "event log" + }, + { + "id": "H", + "text": "model" + }, + { + "id": "I", + "text": "conformance checking" + }, + { + "id": "J", + "text": "diagnostics" + }, + { + "id": "K", + "text": "event log" + }, + { + "id": "L", + "text": "model" + }, + { + "id": "M", + "text": "enhancement" + }, + { + "id": "N", + "text": "new model" + } + ], + "relationships": [ + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "B", + "target": "G" + }, + { + "source": "B", + "target": "H" + }, + { + "source": "B", + "target": "I" + }, + { + "source": "B", + "target": "J" + }, + { + "source": "G", + "target": "I" + }, + { + "source": "H", + "target": "I" + }, + { + "source": "I", + "target": "J" + }, + { + "source": "C", + "target": "K" + }, + { + "source": "C", + "target": "L" + }, + { + "source": "C", + "target": "M" + }, + { + "source": "C", + "target": "N" + }, + { + "source": "K", + "target": "M" + }, + { + "source": "L", + "target": "M" + }, + { + "source": "M", + "target": "N" + } + ] + }, + { + "type": "title", + "text": "Process Mining Characteristics:" + }, + { + "type": "text", + "text": "1. Process mining is not limited to control-flow discovery. The discovery of process models from event logs fuels the imagination of both practitioners and academics. Therefore, control-flow discovery is often seen as the most exciting part of process mining. However, process mining is not limited to control-flow discovery. On the one hand, discovery is just one of the three basic forms of process mining (discovery, conformance, and enhancement). On the other hand, the scope is not limited to control-flow; the organizational, case and time perspectives also play an important role.\n\n2. Process mining is not just a specific type of data mining. Process mining can be seen as the \"missing link\" between data mining and traditional model-driven BPM. Most data mining techniques are not process-centric at all. Process models potentially exhibiting concurrency are incomparable to simple data mining structures such as decision trees and association rules. Therefore, completely new types of representations and algorithms are needed.\n\n3. Process mining is not limited to offline analysis. Process mining techniques extract knowledge from historical event data. Although \"post mortem\" data is used, the results can be applied to running cases. For example, the completion time of a partially handled customer order can be predicted using a discovered process model." + }, + { + "type": "text", + "text": "produces a model without using any a-priori information. Process discovery is the most prominent process mining technique. For many organizations it is surprising to see that existing techniques are indeed able to discover real processes merely based on example executions in event logs. The second type of process mining is conformance. Here, an existing process model is compared with an event log of the same process. Conformance checking can be used to check if reality, as recorded in the log, conforms to the model and vice versa. Note that different types of models can be considered: conformance checking can be applied to procedural models, organizational models, declarative process models, business rules/policies, laws, etc. The third type of process mining is enhancement. Here, the idea is to extend or improve an existing process model using information about the actual process recorded in some event log. Whereas conformance checking measures the alignment between model and reality, this third type of process mining aims at changing or extending the a-priori model. For instance, by using timestamps in the event log one can extend the model to show bottlenecks, service levels, throughput times, and frequencies.\n\nFigure 3 describes the three types of process mining in terms of input and output. Techniques for discovery take an event log and produce a model. The discovered model is typically a process model (e.g., a Petri net, BPMN, EPC, or UML activity diagram), however, the model may also describe other perspectives (e.g., a social network). Conformance checking techniques need an event log and a model as input. The output consists of diagnostic information showing differences and commonalities between model and log. Techniques for model enhancement (repair or extension) also need an event log and a model as input. The output is an improved or extended model.\n\nProcess mining may cover different perspectives. The control-flow perspective focuses on the control-flow, i.e., the ordering of activities. The goal of mining this perspective is to find a good characterization of all possible paths. The result is typically expressed in terms of a Petri net or some other process notation (e.g., EPCs, BPMN, or UML activity diagrams). The organizational perspective focuses on information about resources hidden in the log, i.e., which actors (e.g., people, systems, roles, or departments) are involved and how are they related. The goal is to either structure the organization by classifying people in terms of roles and organizational units or to show the social network. The case perspective focuses on properties of cases. Obviously, a case can be characterized by its path in the process or by the actors working on it. However, cases can also be characterized by the values of the corresponding data elements. For example, if a case represents a" + }, + { + "type": "page_number", + "text": "4" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_03.json b/diagrams-and-tables/annotations/en_diagram_03.json new file mode 100644 index 0000000000000000000000000000000000000000..9667a126140b2cef904143fb541d5650d01ca629 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_03.json @@ -0,0 +1,65 @@ +[ + { + "type": "header", + "text": "Executive Summary" + }, + { + "type": "title", + "text": "The following recommendations are offered as guidance for future work to ensure the reliability and security of the BPS:" + }, + { + "type": "text", + "text": "Recommendation 1: The NERC LLTF should identify existing processes and standards that do not fully address the risks of emerging large loads, as planned for the LLTF's second work item—White Paper: Assessment of Gaps in Existing Practices, Requirements, and Reliability Standards for Emerging Large Loads.\nRecommendation 2: The LLTF should identify potential mitigations to risks posed by emerging large loads through improvements to existing planning and operation processes and interconnection procedures for large loads as planned for the LLTF's third work item—Reliability Guideline: Risk Mitigation for Emerging Large Loads.\nRecommendation 3: The LLTF should clearly define each of the identified characteristics of emerging large loads and develop a framework for classifying large loads.\nRecommendation 4: The NERC Load Modeling Working Group should create and approve load models that can show the characteristics and risks of each category of emerging large loads in simulations.\nRecommendation 5: The NERC System Protection and Control Working Group should assess possible protection system impacts to the BPS from emerging large loads.\nRecommendation 6: The NERC Energy Reliability Assessment Working Group and Probabilistic Assessments Working Group should investigate methods for grid operators and planners to assess the risks potentially posed by emerging large loads to resource adequacy." + }, + { + "type": "title", + "text": "Next Steps" + }, + { + "type": "text", + "text": "To address the near- and long-term risks associated with large loads, NERC is identifying gaps in integrating these large loads onto the grid, enabling a coordinated approach to address this issue effectively. This white paper is expected to be published in Q4 2025." + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "High Priority Risks" + }, + { + "id": "B", + "text": "LONG-TERM PLANNING\n• Resource Adequacy" + }, + { + "id": "C", + "text": "OPERATIONS/BALANCING\n• Balancing and Reserves" + }, + { + "id": "D", + "text": "STABILITY\n• Ride-through\n• Voltage Stability\n• Angular Stability\n• Oscillations" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + } + ] + }, + { + "type": "footer", + "text": "NERC | Characterization and Risks of Emerging Large Loads | July 2025" + }, + { + "type": "page_number", + "text": "vii" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_04.json b/diagrams-and-tables/annotations/en_diagram_04.json new file mode 100644 index 0000000000000000000000000000000000000000..d3cc61426242a200d26fe44a7a53729ce50b6361 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_04.json @@ -0,0 +1,185 @@ +[ + { + "type": "header", + "text": "Chapter 3: Risks to the Bulk Power System" + }, + { + "type": "diagram_caption", + "text": "Figure 3.3: Taxonomy of Power System Stability" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Power system stability" + }, + { + "id": "B", + "text": "Resonance stability" + }, + { + "id": "C", + "text": "Converter-driven stability" + }, + { + "id": "D", + "text": "Rotor angle stability" + }, + { + "id": "E", + "text": "Voltage stability" + }, + { + "id": "F", + "text": "Frequency stability" + }, + { + "id": "G", + "text": "Electrical" + }, + { + "id": "H", + "text": "Torsional" + }, + { + "id": "I", + "text": "Fast interaction" + }, + { + "id": "J", + "text": "Slow interaction" + }, + { + "id": "K", + "text": "Transient" + }, + { + "id": "L", + "text": "Small-disturbance" + }, + { + "id": "M", + "text": "Large-disturbance" + }, + { + "id": "N", + "text": "Small-disturbance" + }, + { + "id": "O", + "text": "Short term" + }, + { + "id": "P", + "text": "Long term" + }, + { + "id": "Q", + "text": "Short term" + }, + { + "id": "R", + "text": "Long term" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "B", + "target": "G" + }, + { + "source": "B", + "target": "H" + }, + { + "source": "C", + "target": "I" + }, + { + "source": "C", + "target": "J" + }, + { + "source": "D", + "target": "K" + }, + { + "source": "D", + "target": "L" + }, + { + "source": "E", + "target": "M" + }, + { + "source": "E", + "target": "N" + }, + { + "source": "F", + "target": "Q" + }, + { + "source": "F", + "target": "R" + }, + { + "source": "M", + "target": "O" + }, + { + "source": "M", + "target": "P" + }, + { + "source": "N", + "target": "P" + } + ] + }, + { + "type": "text", + "text": "To keep stability problems from adversely affecting BPS reliability, it is generally necessary to identify them proactively and put mitigations in place to ensure conditions conducive to instability are avoided. Power system stability studies are the primary means by which this is accomplished. Thus, many of the stability-related risks associated with large loads arise from the concern that the loads have not been accurately represented in power system stability studies. This is one reason why the widespread tripping of large loads has attracted significant attention—this widespread tripping was not anticipated in power system studies and could indicate unforeseen (and therefore unmitigated) stability problems. In the next white paper, gaps in current practices (e.g., modeling practices) contributing to this concern will be discussed in detail. This white paper, however, is dedicated to identifying ways in which large loads might contribute adversely to stability problems." + }, + { + "type": "title", + "text": "Ride-Through" + }, + { + "type": "text", + "text": "The voltage and frequency ride-through behavior of large loads during disturbances plays a significant role in how they may contribute to instability. Ride-through behavior is primarily defined in terms of how long the load remains connected during a given voltage and/or frequency disturbance. However, changes in the load's real or reactive power consumption during or after the disturbance are important as well (e.g., how much time passes before a disconnected load reconnects, and how quickly does it return to its original consumption). Currently, much attention is directed toward the tendency of many large loads to disconnect during disturbances. Some large loads have internal protection and control systems that will disconnect from the grid during disturbances. For example, some data centers may switch to backup power systems after three transient voltage disturbances within one minute as observed at certain data centers in the EI load transfer event.$^{1}$ The intent behind such systems is usually to ensure the reliability of the large load's process (e.g., serving internet traffic) or protect equipment from damage by switching to a local backup power source.\n\nBPS equipment is designed and operated to meet certain ride-through requirements (e.g., Reliability Standard PRC-024) so that it remains on-line during disturbances and supports the system.$^{31}$ These requirements are necessary because disconnecting BPS equipment during a disturbance can worsen the disturbance's effects and, if enough equipment disconnects, lead to cascading power outages. At a sufficient scale, the disconnection of load introduces similar concerns. The tendency of some loads to disconnect during disturbances is not new. However, the scale of recent load loss events was unexpected and had measurable effects on the BPS. This called into question existing modeling practices and expectations for loads." + }, + { + "type": "text", + "text": "31 Standard PRC-024-3" + }, + { + "type": "footer", + "text": "NERC | Characterization and Risks of Emerging Large Loads | July 2025" + }, + { + "type": "page_number", + "text": "22" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_05.json b/diagrams-and-tables/annotations/en_diagram_05.json new file mode 100644 index 0000000000000000000000000000000000000000..f0eed0c100b516c338aaa63594c8429a9e1514b3 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_05.json @@ -0,0 +1,101 @@ +[ + { + "type": "header", + "text": "BEYOND INDUSTRIAL POLICY: EMERGING ISSUES AND NEW TRENDS" + }, + { + "type": "diagram_caption", + "text": "Figure 3. A typology of industrial policies by policy orientation" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Industrial Policy" + }, + { + "id": "B", + "text": "Horizontal" + }, + { + "id": "C", + "text": "Selective" + }, + { + "id": "D", + "text": "Framework conditions" + }, + { + "id": "E", + "text": "Strategic" + }, + { + "id": "F", + "text": "Defensive/Reactive" + }, + { + "id": "G", + "text": "\"Tasks\"" + }, + { + "id": "H", + "text": "Sectors" + }, + { + "id": "I", + "text": "Technology" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "C", + "target": "F" + }, + { + "source": "C", + "target": "G" + }, + { + "source": "C", + "target": "H" + }, + { + "source": "C", + "target": "I" + } + ] + }, + { + "type": "text", + "text": "Arguably, policies designed to tide industry over a period of temporary disruption, arising for example from disruption to global value chains or to the flow of credit, may be less distorting and therefore easier to justify than those designed to attempt to slow the pace of structural change. However, in practice, it may be difficult to distinguish between the two ex ante, and therefore defensive polices need to be carefully designed and subject to close monitoring and evaluation. Ideally, they should be accompanied by conditionality that encourages structural reform in return for temporary funding, as happened with some of the support provided to the car industry. Similarly, defensive/reactive industrial policies that address the problems of longer term structural change should aim to promote orderly adjustment, through facilitating the transfer of resources from declining industries to new industries, or upgrading production into higher value added activities, rather than seeking to immunise sectors from the effects of change altogether.\n\nWithin the sphere of strategic industrial policy, the literature makes two important and relevant distinctions - between catch-up and frontier industrial policies and between comparative advantage-following and comparative advantage-defying policies. The orientation of strategic industrial policy for a country that is far from the technology frontier is likely to be different from what it might be for a country that is at or close to the frontier. Within the development literature, which focuses on the position of countries in catch-up mode, there has been an active debate on whether industrial policy should follow comparative advantage or defy it (Lin and Chang, 2009). On one side of the debate are those, such as Justin Lin, who argue that role of industrial policy in developing countries should be to make possible the effective exploitation of the country's comparative advantage at each stage of development. On the other side of the debate are those, typified by Ha-Joon Chang, whose view is that development requires the acquisition of industry-specific technological capabilities through the experience of production and that it is by definition necessary to defy, or at least develop, comparative advantage if a country is going to enter new industries and upgrade its industrial structure.$^{14}$ These two approaches may imply different orientations for strategic industrial policy in a catch-up context." + }, + { + "type": "footer", + "text": "OECD SCIENCE, TECHNOLOGY AND INDUSTRY POLICY PAPERS" + }, + { + "type": "page_number", + "text": "29" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_06.json b/diagrams-and-tables/annotations/en_diagram_06.json new file mode 100644 index 0000000000000000000000000000000000000000..9b9778fd1b41e5b94436d28bd4e7efff3ff34608 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_06.json @@ -0,0 +1,101 @@ +[ + { + "type": "header", + "text": "Office of the Principal Scientific Adviser to the Government of India" + }, + { + "type": "diagram_caption", + "text": "Figure 2: An indicative diagram for techno-legal governance mechanism" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Law (Enables innovation with necessary continuous technical safeguards across lifecycle)" + }, + { + "id": "B", + "text": "Rule (Provides direction on technical safeguards mandatory for scenarios & exemptions)" + }, + { + "id": "C", + "text": "Regulatory Mechanism (Provides guidance, acts on grievances from public and pronounces decision)" + }, + { + "id": "D", + "text": "Regulator" + }, + { + "id": "E", + "text": "Board of Directors of an Organization (Ethical obligation to protect the rights of its customers and their safety)" + }, + { + "id": "F", + "text": "Techno-Legal Governance Team (Defines policy, ensures technical controls are in place to understand & mitigate risk)" + }, + { + "id": "G", + "text": "Technical & Policy Teams (Implements policies and technical controls for automated & continuous compliance)" + }, + { + "id": "H", + "text": "Organization" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "E", + "target": "H" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "F", + "target": "H" + }, + { + "source": "G", + "target": "H" + } + ] + }, + { + "type": "text", + "text": "At the execution level, techno-legal framework may evolve from a law to rules to guidance to standards to protocols to various frameworks based on organizations and various levels of associated risks. Regulators and/or Courts (if applicable) could provide guidance on various attributes of Responsible AI and its mitigation depending upon the level of maturity of existing laws and obligations for each attribute.\n\nIn a nutshell, a techno-legal approach supplements the traditional regulatory mechanisms with modern governance tools and digital processes that embed compliance into technology. Instead of enforcing rules only after deployment, this approach encodes legal obligations directly into technical artefacts and system-level controls (such as consent-based access control, privacy-enhancing technologies, privacy-preserving machine learning, data poisoning detection, data and AI threat modelling, data and AI impact assessment, LLM and agentic guardrails [7][8]) directly at the design and development stage, allowing system controls to support compliance on an ongoing basis. This reduces the risk of gaps, misuse, and regulatory breaches during operation. When combined with human oversight, these measures enable compliance to occur at the point of data collection, model training, and deployment." + }, + { + "type": "page_number", + "text": "7" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_07.json b/diagrams-and-tables/annotations/en_diagram_07.json new file mode 100644 index 0000000000000000000000000000000000000000..e1006df3cac585699379ebd29269554f85eb3bc0 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_07.json @@ -0,0 +1,189 @@ +[ + { + "type": "header", + "text": "Office of the Principal Scientific Adviser to the Government of India" + }, + { + "type": "diagram_caption", + "text": "Figure 3: An indicative diagram of lifecycle journey of AI use-case" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Business Use Case" + }, + { + "id": "B", + "text": "Requirement, Value & Utility" + }, + { + "id": "C", + "text": "Risk & Mitigation Strategy" + }, + { + "id": "D", + "text": "AI Lifecycle Journey" + }, + { + "id": "E", + "text": "Collect Data" + }, + { + "id": "F", + "text": "Data Collection" + }, + { + "id": "G", + "text": "Quantify & Govern risk" + }, + { + "id": "H", + "text": "Validate Utility" + }, + { + "id": "I", + "text": "Data in Use Protection" + }, + { + "id": "J", + "text": "Mitigate Risk" + }, + { + "id": "K", + "text": "Continuous Training" + }, + { + "id": "L", + "text": "Model Training & Assessment" + }, + { + "id": "M", + "text": "Model Assessment" + }, + { + "id": "N", + "text": "Accelerated Adoption" + }, + { + "id": "O", + "text": "Safe AI Inference" + }, + { + "id": "P", + "text": "Inference Safety" + }, + { + "id": "Q", + "text": "Agentic Usage" + }, + { + "id": "R", + "text": "Trusted Agents" + }, + { + "id": "S", + "text": "Agentic Controls" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "D", + "target": "F" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "F", + "target": "I" + }, + { + "source": "H", + "target": "I" + }, + { + "source": "I", + "target": "J" + }, + { + "source": "I", + "target": "L" + }, + { + "source": "K", + "target": "L" + }, + { + "source": "L", + "target": "M" + }, + { + "source": "L", + "target": "O" + }, + { + "source": "N", + "target": "O" + }, + { + "source": "O", + "target": "P" + }, + { + "source": "O", + "target": "R" + }, + { + "source": "Q", + "target": "R" + }, + { + "source": "R", + "target": "S" + } + ] + }, + { + "type": "title", + "text": "(a) Data Collection Stage" + }, + { + "type": "text", + "text": "Risk: The data collection stage is foundational to building compliant, safe, and trustworthy AI systems. This follows the conception stage where an organization has clearly identified an AI opportunity or an AI use case, which can unlock value for the organization and its users. This also covers all types of data. Risks at this stage arise when data is collected without a clear understanding of its privacy, safety, intellectual property, security, and fairness implications.\n\n• Privacy risk: Collection of personal, sensitive, or re-identifiable information without proper consent, lawful basis, or purpose limitation can lead to personal data breaches and regulatory noncompliance.\n\n• Safety risk: Inclusion of malicious, harmful, deepfake, or inappropriate content in datasets can result in unsafe or harmful AI behaviors.\n\n• Intellectual property risk: Inclusion of proprietary data, covered by intellectual property laws, can result in ambiguity regarding its use to build an AI system.\n\n• Security risk: Poorly governed data sources may introduce risks such as data poisoning, credential leakage, or exposure of proprietary data through shared or third-party datasets.\n\n• Fairness risk: Skewed, incomplete, or unrepresentative data collection can embed bias, resulting in discriminatory or unfair AI outcomes." + }, + { + "type": "title", + "text": "Potential Impact of Negligence:" + }, + { + "type": "text", + "text": "• Non-compliance with data protection and AI regulations\n\n• Increased likelihood of biased, unsafe, or untrustworthy AI systems\n\n• Downstream risks that are difficult or costly to remediate" + }, + { + "type": "page_number", + "text": "10" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_08.json b/diagrams-and-tables/annotations/en_diagram_08.json new file mode 100644 index 0000000000000000000000000000000000000000..17a773650f19c9ccf95402d28f0f15303ac9562a --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_08.json @@ -0,0 +1,141 @@ +[ + { + "type": "header", + "text": "Manufacturing and Subsector Competitiveness" + }, + { + "type": "text", + "text": "knockdown assembly → domestic manufacturing of parts → development of a fully Korean-made model → realization of export industry" + }, + { + "type": "text", + "text": "During this sequential process, the development of an independent model generally occurs when independently developed technology and market conditions mature. In addition, the bodies that led such a unique, man-made development were a venturous entrepreneur, positive visions, the Korean government's momentum and passionate engineers. The success of the development mechanism of the Korean automotive industry was possible via virtuous circles among these factors. In addition, diverse and well-balanced policy measures by the government were linked with each other organically and thus contributed a pivotal role in promoting the industry. These policies covered (1) heavy chemical industrialization and the promotion of the Korean automotive industry, (2) domestic automobile market protection policies, (3) internal competition policy, and (4) automotive parts localization policy along with stable labour management relationships based on the government's strong vision." + }, + { + "type": "diagram_caption", + "text": "Figure 7.13 Development mechanism of the Korean automotive industry" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Government Policy" + }, + { + "id": "B", + "text": "Economic Development" + }, + { + "id": "C", + "text": "Type Of Korean Automotive Enterprises Multinationals Minimizing the Participation of Capital" + }, + { + "id": "D", + "text": "Entrepreneurship Independent management" + }, + { + "id": "E", + "text": "Business Strategy" + }, + { + "id": "F", + "text": "5th Production Country in the World" + }, + { + "id": "G", + "text": "Internal Capability" + }, + { + "id": "H", + "text": "Development of Relevant Industries" + }, + { + "id": "I", + "text": "Increasing the Domestically Manufactured Automotive Parts Developing People's Car Limiting Import of Foreign Vehicles Specialization/Integration" + }, + { + "id": "J", + "text": "Expansion of Domestic Demand" + }, + { + "id": "K", + "text": "Developing Fully Korean-made Vehicle Strategy for the Realization of Technological Independence Strategy for the Realization of Export Industry" + }, + { + "id": "L", + "text": "Technology Absorption Absorption Capability" + }, + { + "id": "M", + "text": "Automotive Parts Industry Steel industry Electric industry" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "I" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "B", + "target": "J" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "D", + "target": "G" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "E", + "target": "H" + }, + { + "source": "E", + "target": "K" + }, + { + "source": "G", + "target": "L" + }, + { + "source": "H", + "target": "M" + } + ] + }, + { + "type": "text", + "text": "Source: Hyun Youngsu, \"Speed Management of Hyundai Motor\", Korea Lean Management Research Institute, 2013" + }, + { + "type": "text", + "text": "In line with technology independence, the Republic of Korea has pursued strategies to promote ca pacity development. These strategies were not only staged through timeline, but also segmented and diversified throughout various key parts." + }, + { + "type": "page_number", + "text": "147" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_09.json b/diagrams-and-tables/annotations/en_diagram_09.json new file mode 100644 index 0000000000000000000000000000000000000000..d754a4a385f76c97037a583dd66803bc308f6c60 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_09.json @@ -0,0 +1,101 @@ +[ + { + "type": "title", + "text": "Parallel processes" + }, + { + "type": "text", + "text": "These are really important and often are the cause of delays for patients and frustration for staff. Mapping, analysing and improving parallel processes will often deliver great benefits. Parallel processes include:\n• processes involved in generating a referral letter and in getting the appointment details to the patient\n• processes involved in dealing with pathology specimens: from the time the specimen is taken to the point when the requesting clinician receives the test results\n• processes involved in imaging reporting: from the image being requested to the image and the report being received by the referring clinician\n• processes involved in medical records: from getting the notes to returning them to \"file\"\n• processes involved in communicating by letter: from deciding the need for a letter to the letter being received by the designated person" + }, + { + "type": "diagram_caption", + "text": "A parallel administration process" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Patient process" + }, + { + "id": "B", + "text": "GP tells patient that they need a hospital appointment" + }, + { + "id": "C", + "text": "GP dictates referral letter" + }, + { + "id": "D", + "text": "Patient waits" + }, + { + "id": "E", + "text": "Hospital appointments clerk posts letter to patient" + }, + { + "id": "F", + "text": "Patient receives appointment" + }, + { + "id": "G", + "text": "Parallel process" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "C", + "target": "G" + }, + { + "source": "D", + "target": "F" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "E", + "target": "G" + }, + { + "source": "F", + "target": "G" + } + ] + }, + { + "type": "text", + "text": "Tip\nRemember process mapping is only one method open to you. Use it in conjunction with other relevant tools." + }, + { + "type": "page_number", + "text": "20" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_10.json b/diagrams-and-tables/annotations/en_diagram_10.json new file mode 100644 index 0000000000000000000000000000000000000000..bdb6681a15f0c949bceb8b96d25c8f53664d3b88 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_10.json @@ -0,0 +1,93 @@ +[ + { + "type": "title", + "text": "5 Package of measures to enhance liquidity" + }, + { + "type": "text", + "text": "LME position\n• The LME believes a combination of measures, delivered together, will be the most effective way to enhance liquidity in the central electronic market\n• A liquidity provider programme focusing on key spreads at the front of the curve will provide liquidity for those looking to trade directly on the central venue\n• Block trade thresholds will ensure small orders go through the central venue and are exposed to maximum competition\n• New functionality in the trading platform such as tick size differentiation, self-execution prevention and more implied pricing will further support electronic liquidity provision\n• Ensuring all risk transfer trades are published on the core market data feeds will maximise transparency and avoid information asymmetry that can act as a barrier to entry\n• Where possible, all initiatives should ensure a level playing field between on-exchange trading and OTC – especially in terms of transparency, to avoid any further fragmentation of liquidity" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "1 Liquidity provider programme (for 3M-3W spreads at the front of the curve)" + }, + { + "id": "B", + "text": "2 Block rules and thresholds (inc pre-arranged trading rules and crossing)" + }, + { + "id": "C", + "text": "3 LMEselect V10 functionality (GTCs, Self execution prevention, tick calibration, implieds)" + }, + { + "id": "D", + "text": "Increase price competition" + }, + { + "id": "E", + "text": "4 Market data transparency (Client trades on core feed, LIS deferral)" + }, + { + "id": "F", + "text": "Enhance transparency" + }, + { + "id": "G", + "text": "5 Protecting the physical market (Cash and daily dates excluded from block requirements)" + }, + { + "id": "H", + "text": "Support the physical market" + }, + { + "id": "I", + "text": "6 OTC market considerations (Rules for OTC look-a-likes)" + }, + { + "id": "J", + "text": "7 Other considerations (Order to trade ratio)" + }, + { + "id": "K", + "text": "Ensure fairness" + } + ], + "relationships": [ + { + "source": "A", + "target": "D" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "G", + "target": "H" + }, + { + "source": "I", + "target": "K" + }, + { + "source": "J", + "target": "K" + } + ] + }, + { + "type": "page_number", + "text": "Page 9" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_11.json b/diagrams-and-tables/annotations/en_diagram_11.json new file mode 100644 index 0000000000000000000000000000000000000000..f3c4e28e110cd32f3e6a9c3c4f6082d6de104c7f --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_11.json @@ -0,0 +1,56 @@ +[ + { + "type": "header", + "text": "Process Model for Operations" + }, + { + "type": "page_number", + "text": "43" + }, + { + "type": "text", + "text": "The key activities within SLM include:\n\n• Creating a service catalog\n• Identifying service level requirements\n• Negotiating service level agreements, including the needs of the following foundational SMFs:\n• Service continuity management\n• Availability management\n• Capacity management\n• Workforce management\n• Ensuring that service level requirements are met within financial budgets\n• Setting accounting policies\n• Monitoring and reviewing support services\n• Conducting the SLA review\n\nFinally, the SLA is essentially a contract between the customer and the IT service delivery group. The agreements between internal IT groups are referred to as operational level agreements (OLAs), and agreements with external suppliers and partners are referred to as underpinning contracts. The following diagram depicts this hierarchy of agreements." + }, + { + "type": "diagram_caption", + "text": "Figure 10. Agreements and contracts" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Internal-External Customers" + }, + { + "id": "B", + "text": "IT Service Service Level Mgmt." + }, + { + "id": "C", + "text": "Internal Suppliers and Maintenance Personnel" + }, + { + "id": "D", + "text": "External Suppliers and Maintenance Personnel" + } + ], + "relationships": [ + { + "source": "A", + "target": "B", + "label": "Service Level Agreements" + }, + { + "source": "B", + "target": "C", + "label": "Operational Level Agreements" + }, + { + "source": "B", + "target": "D", + "label": "Underpinning Contracts" + } + ] + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_12.json b/diagrams-and-tables/annotations/en_diagram_12.json new file mode 100644 index 0000000000000000000000000000000000000000..03363170330076bbdd129d89d0a0196832653494 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_12.json @@ -0,0 +1,173 @@ +[ + { + "type": "header", + "text": "WHITE PAPER: STREAMLINING THE ROLLING STOCK APPROVAL PROCESSES." + }, + { + "type": "header", + "text": "RMAus" + }, + { + "type": "title", + "text": "5. ROLLING STOCK APPROVAL PROCESS REQUIREMENTS" + }, + { + "type": "text", + "text": "At the highest level the process to achieve rolling stock approvals follows on from agreements, approvals and acceptances on each RIMs network.\n\nCertification precedes registration. Certification of each class (or type) of vehicle is design and construction assurance to nominated standards that may include Australian Standards but also International Standards. Certification documentation may be used to demonstrate how risks related to rolling stock are being managed by the RSO and RIM under the accreditation requirements of ONRSR.\n\nUnlike certification, registration is about meeting the interface requirements and populating an operating procedure used to run the railways safely and efficiently. A vehicle, or vehicle type, must appear on the approved register, usually within a route operating standard, for the train to be given a train path by the RIM. As an exception, some operators may provide a waiver system." + }, + { + "type": "title", + "text": "5.1 Rolling stock compliance certification" + }, + { + "type": "text", + "text": "AS 7501:2019 Rolling stock compliance certification, is a generic process standard for assessing rolling stock compliance with the referenced standards that has as its objectives:\n1. A standard method for certifying rolling stock compliance to referenced standards.\n2. Facilitating network registration of rolling stock." + }, + { + "type": "text", + "text": "Operation of rolling stock regarding network safe working rules and route standards is not covered by AS 7501. That is the standard does not address the network approval of trains process used by RIMs.\n\nThe standard covers the design, construction and testing of rolling stock. Certification of individual units of rolling stock or those which are coupled to operate is included, but not trains.\n\nAS 7501 applies to new rolling stock, modified rolling stock and existing rolling stock being proposed for operation on a Network on which the class of rolling stock has not previously operated. It also applies to existing rolling stock that is to be or has been modified and has previously operated on the network.\n\nThe standard incorporates both mandatory requirements and non-mandatory preferred recommendations. Where a recommended control is not applied it may be incumbent on the adopter of the standard to demonstrate their actual method of controlling the risk. Similarly, it could also be incumbent on an adopter of the standard to demonstrate their method of controlling the risk to contracting entities, or interfacing organisations where the risk may be shared.\n\nCertification documentation produced by the process includes:\n1. Design compliance certificate.\n2. Construction conformance certificate.\n3. Acceptance for on-track testing certificate.\n4. Certificate of Standards compliance." + }, + { + "type": "diagram_caption", + "text": "Figure 5: AS 7501 as applied to certification of vehicles." + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "New Rolling Stock" + }, + { + "id": "B", + "text": "New Class?" + }, + { + "id": "C", + "text": "Design Safety Assurance Verification & Validation" + }, + { + "id": "D", + "text": "Construction & Testing Safety Assurance" + }, + { + "id": "E", + "text": "Inspection & Testing Safety Assurance" + }, + { + "id": "F", + "text": "Existing Rolling Stock" + }, + { + "id": "G", + "text": "New Application?" + }, + { + "id": "H", + "text": "RSO SMS Change Management process assess change in compliance status." + }, + { + "id": "I", + "text": "Modified Rolling Stock" + }, + { + "id": "J", + "text": "Altered compliance status?" + }, + { + "id": "K", + "text": "RSO SMS Change Management process assess change in compliance status." + }, + { + "id": "L", + "text": "Conditions?" + }, + { + "id": "M", + "text": "Vehicle Registered on Network" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "C", + "label": "YES" + }, + { + "source": "B", + "target": "D", + "label": "YES" + }, + { + "source": "B", + "target": "E", + "label": "YES" + }, + { + "source": "B", + "target": "L", + "label": "NO" + }, + { + "source": "C", + "target": "L" + }, + { + "source": "D", + "target": "L" + }, + { + "source": "E", + "target": "L" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "G", + "target": "H", + "label": "YES" + }, + { + "source": "G", + "target": "L", + "label": "NO" + }, + { + "source": "H", + "target": "L" + }, + { + "source": "I", + "target": "J" + }, + { + "source": "J", + "target": "K", + "label": "YES" + }, + { + "source": "J", + "target": "L", + "label": "NO" + }, + { + "source": "K", + "target": "L" + }, + { + "source": "L", + "target": "M" + } + ] + }, + { + "type": "page_number", + "text": "19" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_13.json b/diagrams-and-tables/annotations/en_diagram_13.json new file mode 100644 index 0000000000000000000000000000000000000000..53ad292fffb36ed4cb6ba807b6f0292c267ba038 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_13.json @@ -0,0 +1,125 @@ +[ + { + "type": "header", + "text": "RAIL INDUSTRY SAFETY AND STANDARDS BOARD" + }, + { + "type": "text", + "text": "This will not only benefit the operators in terms of reduced delays and costs but also enhance the overall safety and reliability of the rail network.\n\nThe way to proceed to address the concerns is at least twofold:\n\n1. The forms and processes can be digitised to reduce the duplication of effort. The NRSR project with further funding is the best way to deal with this in the short term.\n2. The harmonised data fields can be provided to each RIM through the NRSR system, while allowing acknowledged differences in RIM interface requirements to be identified.\n\nThe RIM Registration depends upon the management of interface hazards as highlighted in Figure 6. The next few options listed below were consulted widely but may need further development to arrive at an approach that can be easily adoptable:\n\n3. Reduce the certification requirements with RIMs to the interface static and dynamic performance requirements. In effect the design and construction requirements become self-certification processes by RSOs consistent with the co-regulation model and subject to ONRSR scrutiny.\n4. Infrastructure and Operations common interface standards for registration are incorporated into an Australian Standard to compliment AS 7501" + }, + { + "type": "text", + "text": "for certification.\n\n5. Network specific differences are then managed on a safety risk basis that identifies the further controls the RIM requires to demonstrate a SFAIRP outcome.\n6. Regulate the use of and the mutual recognition of the Certification and Registration standards to provide impetus for change.\n\nThe substantive industry business cost is the reduced utilisation and missed opportunity costs of delayed deployment of expensive capital equipment. An assessment of this can be expected to provide a strong business case for an expanded centralised, standardised and online NRSR project taking into account certification.\n\nThe NRSR project could be expanded as a program of projects, not just a database, with clearly stated industry outcomes. As detailed elsewhere in this paper this encompasses essentially 4 main topics:\n\n• Governance over the functions and data security.\n• Standardisation of certification standards adopting AS 7501 as a regulation if required.\n• Standardisation of registration standards.\n• A risk assessment from the RIM to support why they require more than the above information." + }, + { + "type": "diagram_caption", + "text": "Figure 6: RIM Registration depends upon the management of interface hazards." + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Engineering Assurance process for the design, construction & performance" + }, + { + "id": "B", + "text": "Network Specific Interface D&C, performance standards." + }, + { + "id": "C", + "text": "D&C Common Standards" + }, + { + "id": "D", + "text": "Certification of Rail Vehicles" + }, + { + "id": "E", + "text": "Safety Assurance process for the interface with Infrastructure." + }, + { + "id": "F", + "text": "Network Specific infrastructure & operations standards." + }, + { + "id": "G", + "text": "Infrastructure & Operations Common Standards" + }, + { + "id": "H", + "text": "Registration of Rail Vehicles" + }, + { + "id": "I", + "text": "Safety & Efficiency Assurance process for the interface with Infrastructure & Network Operations" + }, + { + "id": "J", + "text": "Network Specific infrastructure & operations standards." + }, + { + "id": "K", + "text": "Infrastructure & Operations Common Standards" + }, + { + "id": "L", + "text": "Network Approval of a Train" + } + ], + "relationships": [ + { + "source": "A", + "target": "D" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "D", + "target": "H" + }, + { + "source": "E", + "target": "H" + }, + { + "source": "F", + "target": "H" + }, + { + "source": "G", + "target": "H" + }, + { + "source": "H", + "target": "L" + }, + { + "source": "I", + "target": "L" + }, + { + "source": "J", + "target": "L" + }, + { + "source": "K", + "target": "L" + } + ] + }, + { + "type": "footer", + "text": "© RMAus 2024" + }, + { + "type": "page_number", + "text": "30" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_14.json b/diagrams-and-tables/annotations/en_diagram_14.json new file mode 100644 index 0000000000000000000000000000000000000000..ef5de3c9fa71a745545457c900952099b9aab9c5 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_14.json @@ -0,0 +1,109 @@ +[ + { + "type": "text", + "text": "A Merkle tree is used to represent the set of transactions within a block. This enhances transaction searches and the verification of the chain of blocks, since each block may contain many transactions. Please refer to technical note (I) for further details." + }, + { + "type": "diagram_caption", + "text": "A simplified \"chain of blocks\" construction" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": null + }, + { + "id": "B", + "text": "Genesis block" + }, + { + "id": "C", + "text": "Transactions" + }, + { + "id": "D", + "text": null + }, + { + "id": "E", + "text": "Block 2" + }, + { + "id": "F", + "text": "Transactions" + }, + { + "id": "G", + "text": null + }, + { + "id": "H", + "text": "Block 3" + }, + { + "id": "I", + "text": "Transactions" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "D", + "target": "F" + }, + { + "source": "D", + "target": "G" + }, + { + "source": "G", + "target": "H" + }, + { + "source": "G", + "target": "I" + } + ] + }, + { + "type": "title", + "text": "The \"blocks\" of information: creation and addition" + }, + { + "type": "text", + "text": "A key role of the miners, or the validating nodes, is to collect information about new transactions, put this information into a new \"transaction block\", and append it to the ledger.\n\nAn important feature of DLT is that this process of adding new transactions to the ledger needs to go through a consensus and validation mechanism, which helps prevent malicious parties from adding falsified transactions and blocks.\n\nLet us look into how this is done in unpermissioned networks and permissioned networks respectively." + }, + { + "type": "title", + "text": "1. Unpermissioned networks" + }, + { + "type": "text", + "text": "In an unpermissioned network, the miner must solve a mathematically difficult problem on the new block before being able to add the block to the ledger. The miner's solution is then forwarded to other miners and is verified by them before being accepted into their own copies of the ledger.\n\nThe mechanism for solving the difficult problem is known as \"proof-of-work\". A large amount of computational resources are needed to find the solution. Such resources may be understood in terms of power consumption or hardware resources, such as size of physical memory or special hardware logic. The first miner to succeed in solving the problem receives a reward in return for the efforts he or she has made. This behaviour, carried out in the expectation of receiving a reward, may be the reason why the process has come to be called \"mining\" and the parties involved \"miners\".\n\nIf more than one miner solves the mathematical problem for the same block, or generates a block with a different content, the differences are resolved through a consensus protocol, which is a set of rules allowing the parties involved to reach an agreement. Once the process of reaching an agreement is complete, only the block agreed upon is added to the ledger, after which all the replicated copies of ledgers in the network are identical again." + }, + { + "type": "page_number", + "text": "20" + }, + { + "type": "footer", + "text": "Whitepaper on Distributed Ledger Technology" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_15.json b/diagrams-and-tables/annotations/en_diagram_15.json new file mode 100644 index 0000000000000000000000000000000000000000..a1cad109903945fb2bd069d7fbe8bc60a0f30a33 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_15.json @@ -0,0 +1,82 @@ +[ + { + "type": "text", + "text": "As the hash operation reduces an arbitrarily large piece of data to a unique fixed-size short data string, it is often used as a unique identifier of the data itself. At the same time, it keeps the content of the data undisclosed. Not only is the unique ID quite useful for representing the data itself, it can also be used for other purposes. One example is for the proof-of-existence used in some DLT applications. A person who has a digital document containing confidential information can pass the document's hash value to a third party as a reference to the document and as a proof of its existence. When the third party is later provided with a copy of the digital document, that party can verify the genuineness of the digital document by verifying the hash value.\n\nBesides being useful for summarising data and detecting data alteration, the hash function has been innovatively applied by DLT for other purposes. Unpermissioned DLT networks use it to perform proof-of-work mining. When creating a new block containing a set of transactions, a miner runs an indefinite number of iterations of the hash operation. In each iteration, the miner selects a unique number called nonce, combines it with the block's content, and runs the hash operation on the combination. The miner then checks to see whether or not the resulting hash value matches the bit pattern specified by the DLT network. If it does not match, that means the miner has not found a suitable nonce and so has to start another round of the hash operation using a new nonce. When a suitable nonce is finally found, the miner can then legitimately declare that a new block has successfully been created and the nonce can also be presented as proof.\n\nMining is a computationally intensive process because the process requires very significant hash efforts for a miner to find a nonce that will produce a matching hash value pattern. Miners in an unpermissioned DLT compete with each other to be the first one to find the right nonce. The first one to do so normally receives a reward in the DLT system. Technical readers should refer to Technical Note (II) for a detailed illustration." + }, + { + "type": "title", + "text": "Symmetric Key Encryption" + }, + { + "type": "text", + "text": "In symmetric key cryptography, a single key is used to encrypt and to decrypt data. This allows a person to encrypt his or her data and prevent others from learning its content. As long as that person does not reveal the key to others, no one else can decrypt the data." + }, + { + "type": "diagram_caption", + "text": "Illustration: Alice uses a symmetric key to encrypt and decrypt data" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Alice" + }, + { + "id": "B", + "text": "Symmetric key" + }, + { + "id": "C", + "text": "Plain text" + }, + { + "id": "D", + "text": "Encryption" + }, + { + "id": "E", + "text": "Decryption" + }, + { + "id": "F", + "text": "Plain text" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "D", + "target": "E", + "label": "Ciphertext\nInternet" + }, + { + "source": "E", + "target": "F" + } + ] + }, + { + "type": "page_number", + "text": "24" + }, + { + "type": "footer", + "text": "Whitepaper on Distributed Ledger Technology" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_16.json b/diagrams-and-tables/annotations/en_diagram_16.json new file mode 100644 index 0000000000000000000000000000000000000000..81be882a7b7c918c018fb25361993d098ec1b5e0 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_16.json @@ -0,0 +1,94 @@ +[ + { + "type": "text", + "text": "In the diagram above, a symmetric key is used to encrypt a plain text into ciphertext. The ciphertext can then be securely sent through a public channel such as the Internet. The receiving side uses the same key to decrypt the ciphertext back to plain text.\n\nA popular example of symmetric key cryptography is Advanced Encryption Standard (AES). One common usage of AES is for on-line transactions and communications, where it protects the confidentiality of data exchanged over a public network. There are different AES key sizes, with longer key lengths for better protection. A longer key length also makes it harder for outsiders to guess. Currently, many secure online banking transactions are protected by AES cryptography. During each online banking session, a new AES key is established to encrypt subsequent network communications after the bank web server and the client have authenticated each other using asymmetric key cryptography." + }, + { + "type": "title", + "text": "Asymmetric Key Encryption" + }, + { + "type": "text", + "text": "An asymmetric key is also commonly used for data encryption. It allows two parties who may not want to share a symmetric key to send ciphertext to each other.\n\nUnlike symmetric key cryptography, where the same key is used for encryption and decryption, asymmetric key cryptography uses a pair of keys: a public key and a private key. The public key is used to encrypt the data, while the private key is used to decrypt the data. For example, if a person wants to use asymmetric key cryptography to protect the data exchange between himself and other parties, a pair of keys (i.e. the public and private keys) is created for this purpose. The public key is then sent to the other parties, while the private key is kept by the person in question. When a third party wants to send data to this person, the third party makes use of the public key to encrypt the data. As the recipient possesses the private key, he is the only person capable of decrypting the encrypted data sent by the third party (see the illustration in the diagram below).\n\nThe power of asymmetric key cryptography is that it allows two strangers to exchange confidential data on the public network without worrying about data security, and without sharing a single key." + }, + { + "type": "diagram_caption", + "text": "Illustration: Alice passes encrypted data to Bob using Bob's public key" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Alice" + }, + { + "id": "B", + "text": "Bob's public key" + }, + { + "id": "C", + "text": "Bob's private key" + }, + { + "id": "D", + "text": "Bob" + }, + { + "id": "E", + "text": "Plain text" + }, + { + "id": "F", + "text": "Encryption" + }, + { + "id": "G", + "text": "Decryption" + }, + { + "id": "H", + "text": "Plain text" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "F" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "G" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "F", + "target": "G", + "label": "Ciphertext\nInternet" + }, + { + "source": "G", + "target": "H" + } + ] + }, + { + "type": "page_number", + "text": "25" + }, + { + "type": "footer", + "text": "Whitepaper on Distributed Ledger Technology" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_17.json b/diagrams-and-tables/annotations/en_diagram_17.json new file mode 100644 index 0000000000000000000000000000000000000000..e28a52f7a79d3faad8d92be036850f265ca7630c --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_17.json @@ -0,0 +1,104 @@ +[ + { + "type": "title", + "text": "Interoperability between DLT networks and non-DLT systems" + }, + { + "type": "text", + "text": "As an emerging technology, DLT has begun to be applied significantly across many areas of activity. However, interoperability will be important for DLT to be able to integrate or interface with the existing range of applications.\n\nThe complex financial world, for example, already has a comprehensive set of multifaceted financial transactions systems, which work together to perform many different kinds of financial transactions. While some of these may gradually migrate to a DLT base, that process is likely to be gradual. This means there will be a mixture of legacy financial systems and newly emerging DLT systems working together at the same time, creating the need for an interfacing mechanism between legacy systems and DLT systems.\n\nThis interoperability must cover both control paths and data paths. Different interface methods may be needed to suit different non-DLT systems. In receiving data from a non-DLT system, for example, the interface design will need to decide whether the data is to be pulled onto the DLT platform by the validating nodes, or pushed onto it by the non-DLT system." + }, + { + "type": "diagram_caption", + "text": "a) A simplified block diagram of a legacy payment system" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Credit system" + }, + { + "id": "B", + "text": "Debit system" + }, + { + "id": "C", + "text": "Payment system" + }, + { + "id": "D", + "text": "Clearing house" + }, + { + "id": "E", + "text": "Delivery system" + } + ], + "relationships": [ + { + "source": "A", + "target": "C" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "D", + "target": "E" + } + ] + }, + { + "type": "diagram_caption", + "text": "b) A simplified block diagram of a hybrid DLT and legacy payment system" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Credit system" + }, + { + "id": "B", + "text": "Debit system" + }, + { + "id": "C", + "text": "DLT based payment system" + }, + { + "id": "D", + "text": "Delivery system" + } + ], + "relationships": [ + { + "source": "A", + "target": "C" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "C", + "target": "D" + } + ] + }, + { + "type": "page_number", + "text": "32" + }, + { + "type": "footer", + "text": "Whitepaper on Distributed Ledger Technology" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_18.json b/diagrams-and-tables/annotations/en_diagram_18.json new file mode 100644 index 0000000000000000000000000000000000000000..72bb9c72cdd8902736e3c800daa6ce9541b4f6f9 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_18.json @@ -0,0 +1,100 @@ +[ + { + "type": "title", + "text": "Borrower submits documents" + }, + { + "type": "title", + "text": "Lender retrieves borrower document hash & full details" + }, + { + "type": "diagram_caption", + "text": "Illustration showing the storing of document hash in a DLT ledger" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Borrower's documents" + }, + { + "id": "B", + "text": "Borrower's computer" + }, + { + "id": "C", + "text": "A DLT ledger" + }, + { + "id": "D", + "text": "Bank" + }, + { + "id": "E", + "text": "Secure database" + }, + { + "id": "F", + "text": "Access authenticator & gateway" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "C", + "label": "Document hash" + }, + { + "source": "B", + "target": "C", + "label": "Full document details" + }, + { + "source": "C", + "target": "D", + "label": "Public channel" + }, + { + "source": "D", + "target": "F" + }, + { + "source": "E", + "target": "F" + } + ] + }, + { + "type": "text", + "text": "Although only registered members can participate in a permissioned DLT network, members' identities are not necessarily revealed in the transactions. To keep a member's activity history private, a DLT platform may assign each member a transaction certificate when a new transaction is conducted. This means that different transactions initiated by a member may bear different transaction credentials. As a result, other members can only relate a transaction to a particular credential, and cannot infer the identity of the member from it. Some permissioned DLT networks utilise this approach to protect the privacy of members and their activity history by issuing pseudonymous member credentials in the form of transaction certificates.$^{18}$ Only authorised auditors are granted permission to access membership information and are able to relate transaction certificates to members' identities." + }, + { + "type": "title", + "text": "9.3 Challenges" + }, + { + "type": "title", + "text": "Unpermissioned DLT Networks" + }, + { + "type": "title", + "text": "Potential Attacks by a Dishonest Majority" + }, + { + "type": "text", + "text": "The integrity of an unpermissioned DLT network relies on the assumption that the majority of miners, who possess most of the mining capability, are honest in mining and in maintaining the network. If there is a chance that the majority of the miners are colluding together, or that a few dishonest miners possess most of the mining capability, these miners would be capable of compromising the integrity of the unpermissioned DLT network." + }, + { + "type": "footer", + "text": "Whitepaper on Distributed Ledger Technology" + }, + { + "type": "page_number", + "text": "49" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_19.json b/diagrams-and-tables/annotations/en_diagram_19.json new file mode 100644 index 0000000000000000000000000000000000000000..2b68231c2d84d632014b39c16f848b95cf809580 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_19.json @@ -0,0 +1,117 @@ +[ + { + "type": "diagram_caption", + "text": "An example of the workflow of a smart contract" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Buyer" + }, + { + "id": "B", + "text": "Seller" + }, + { + "id": "C", + "text": "Purchase Order" + }, + { + "id": "D", + "text": "Confirm" + }, + { + "id": "E", + "text": "Import financing when payment is due" + }, + { + "id": "F", + "text": "Post-shipment financing when invoice is verified" + }, + { + "id": "G", + "text": "Import bank" + }, + { + "id": "H", + "text": "Export bank" + } + ], + "relationships": [ + { + "source": "A", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "C", + "target": "D", + "label": "Smart contract" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "D", + "target": "F", + "label": "elnvoice" + }, + { + "source": "E", + "target": "F", + "label": "Payment settlement\nFinance status" + }, + { + "source": "E", + "target": "G" + }, + { + "source": "F", + "target": "E", + "label": "Finance status" + }, + { + "source": "F", + "target": "H" + } + ] + }, + { + "type": "title", + "text": "Current process inefficiencies:" + }, + { + "type": "text", + "text": "• No standardised structure of a PO\n• No way to verify the latest version of a PO\n• Low visibility of contract terms and amendments to banks\n• High error rate due to manual mistakes\n• Inefficient and costly due to:\n o Handling of paper-based documents\n o Difficulty in authentication by banks\n• Risk of fraud" + }, + { + "type": "title", + "text": "Improvements achieved by applying DLT:" + }, + { + "type": "text", + "text": "• Digitised and standardised PO\n• Deployment of smart contract automates trade execution\n• Facilitate cross-border trade finance by collaboration with overseas DLT projects\n• Financing to customer is faster and enable stage financing along the supply chain\n• Lower risk of financing and avoid double financing" + }, + { + "type": "title", + "text": "11.2.2 Tracking the status of trade transactions: flows of Goods & Funds" + }, + { + "type": "text", + "text": "Tracking the status of a trade transaction and the flow of goods is yet another challenge for open account financing, as the presentation of third-party documentation (such as transport documents) to the bank is not mandated, unlike with documentary credit.\n\nThe DLT solution proposed by the Trade Finance Working Group is to store and share key trade documents on the DLT network, so they are accessible by all stakeholders in the transaction. Moreover, a number of data feeds from the logistics service providers will be collected at key touch points to reveal the most current status of the flow of goods. The key information to be stored on the DLT network includes the goods delivery status reported by the seller, shipping information from logistics service providers, and the funding status from banks. This information will also be used for tracking the status of goods and funds. As a result, the visibility of the goods and the flow of funds in a transaction will be greatly enhanced, and the risk of fraudulent transactions or financing lowered." + }, + { + "type": "page_number", + "text": "80" + }, + { + "type": "footer", + "text": "Whitepaper on Distributed Ledger Technology" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_20.json b/diagrams-and-tables/annotations/en_diagram_20.json new file mode 100644 index 0000000000000000000000000000000000000000..fdd9380f5f7364c5b5f5497a9cc9e8ba4d755a4a --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_20.json @@ -0,0 +1,73 @@ +[ + { + "type": "title", + "text": "4. Trade Finance Marketplace" + }, + { + "type": "text", + "text": "In the age of Internet and eCommerce, the buyers and sellers meet and negotiate online. In international trade, the buyers and sellers in different countries may have not met each other. The banks, therefore, mitigate the risk between unknown parties. The banks, however, have to setup channels and alliances with other banks in foreign geographies to mitigate risk and enable international trade. It is not cost-efficient for even big banks to have a leading presence in every market. Setting up such channels and alliances globally with other banks operating under different laws and ensuring regulatory compliance in local country is complex and cost intensive. The result is the banks form alliances and partnerships with only few leading/large banks in each geography. The smaller banks and financial institutions, therefore, have to route their trade financing through its correspondent bank which further submits the transaction to the leading bank in the geography to complete the end-to-end transaction. As the number of such intermediate banks increase, the overall transaction cost also increase for the importer and the exporter.\n\nBlockchain technology can be employed to create a global trade finance marketplace and reduce the transaction cost by dynamically discovering the most cost-effective trust path between importer's bank and exporter's bank with least number of intermediaries. The blockchain-based marketplace allows banks and financial institutions of all sizes to join the global trade finance marketplace and offer its services. These entities connect with other entities on the network that they trust, thus defining a trust link between them. For each global trade, the blockchain discovers the most optimal trust path between the importer's bank and exporter's bank, thus eliminating the requirement for banks to form direct alliances and agreements with multiple banks in each geography. Each entity on the network publishes its terms of contract and fee. The blockchain protocol picks those entities in the trust path whose terms and conditions match with the other and also with the terms and conditions specified by the importer and exporter, while ensuring to keep the overall transaction cost to minimum. The entities, providing trust and liquidity for trade finance, act as market makers on global trade finance blockchain network." + }, + { + "type": "diagram_caption", + "text": "Figure 3. Trade Finance Marketplace on Blockchain Network" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Importer" + }, + { + "id": "B", + "text": "Importer Bank" + }, + { + "id": "C", + "text": "Financial Institution [Market Marker]" + }, + { + "id": "D", + "text": "Exporter Bank" + }, + { + "id": "E", + "text": "Exporter" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "D", + "target": "E" + } + ] + }, + { + "type": "title", + "text": "5. IBM Blockchain Technology and Solutions" + }, + { + "type": "text", + "text": "Driven by business requirements and use cases, IBM and partners are implementing an enterprise-grade programmable, secure, permissioned and auditable blockchain fabric, which allows customized and extensible solutions on blockchain. The blockchain fabric - Hyperledger (https://www.hyperledger.org/), is an open source project under the Linux Foundation and is open for all. IBM also offers hosted Hyperledger nodes on secure SoftLayer cloud." + }, + { + "type": "page_number", + "text": "89" + }, + { + "type": "footer", + "text": "Whitepaper on Distributed Ledger Technology" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_21.json b/diagrams-and-tables/annotations/en_diagram_21.json new file mode 100644 index 0000000000000000000000000000000000000000..6c79debd97e12aad1e6d2744fa1a8c24fe45641c --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_21.json @@ -0,0 +1,89 @@ +[ + { + "type": "title", + "text": "Technical note (I) - the Merkle tree" + }, + { + "type": "text", + "text": "The Merkle tree is named after Ralph Merkle, who patented the concept of the hash tree. The tree is a binary tree of hashes. It provides an efficient way of summarising a set of leaf nodes. Each non-leaf node is labelled with the hash of its child nodes.\nIn DLT, a Merkle tree is used to summarise the transactions within a block. Each transaction is represented by a hash value. Transaction hashes are attached to the bottom of the Merkle tree as leaf nodes. The Merkle tree is then built upward from the leaf nodes until it reaches the top of the tree, where there is only one node known as a Merkle root. When using the SHA256 hash, the hashes of all nodes and of the Merkle root are 32 bytes long.\nTo prove the existence of a transaction within a block, one does not need to know the hashes of all the transactions within that block. To prove its existence within a block of N transactions, all that is required is the log2(N) number of hash values and the performing of an equal number of hash operations: one hash operation at each level, with the step repeated at the next level up until it reaches the root (as illustrated in the diagram below). If the calculated root hash value is the same as the known root value, then the existence of the transaction is proven. This significantly enhances the speed of verifying transactions while at the same time reducing the amount of block information needed to prove the existence of a particular transaction within the block (see diagram below)." + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Merkle root" + }, + { + "id": "B", + "text": "HASH$_{1234}$\nHash (Hash12 , Hash34)" + }, + { + "id": "C", + "text": "HASH$_{12}$\nHash (Hash1 , Hash2)" + }, + { + "id": "D", + "text": "HASH$_{34}$\nHash (Hash3 , Hash4)" + }, + { + "id": "E", + "text": "HASH$_{1}$\nTransaction 1" + }, + { + "id": "F", + "text": "HASH$_{2}$\nTransaction 2" + }, + { + "id": "G", + "text": "HASH$_{3}$\nTransaction 3" + }, + { + "id": "H", + "text": "HASH$_{4}$\nTransaction 4" + }, + { + "id": "I", + "text": "Transactions" + } + ], + "relationships": [ + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "C", + "target": "F" + }, + { + "source": "D", + "target": "G" + }, + { + "source": "D", + "target": "H" + } + ] + }, + { + "type": "text", + "text": "A Merkle tree of four transactions. Leaf nodes at the bottom are hash values of each transaction. Each pair of these hash values are then hashed again. The process is repeated until a single hash is obtained which is called the Merkle Root. To prove the existence of transaction 4 in the block having a Merkle Root value of HASH$_{1234}$, one only needs to be provided with hash values of HASH$_{3}$ and HASH$_{12}$." + }, + { + "type": "page_number", + "text": "90" + }, + { + "type": "footer", + "text": "Whitepaper on Distributed Ledger Technology" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_22.json b/diagrams-and-tables/annotations/en_diagram_22.json new file mode 100644 index 0000000000000000000000000000000000000000..37984c367924a8eb0cd26fb696d1da8aae53e764 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_22.json @@ -0,0 +1,93 @@ +[ + { + "type": "title", + "text": "Manager pattern" + }, + { + "type": "text", + "text": "The manager pattern empowers a central LLM—the \"manager\"—to orchestrate a network of specialized agents seamlessly through tool calls. Instead of losing context or control, the manager intelligently delegates tasks to the right agent at the right time, effortlessly synthesizing the results into a cohesive interaction. This ensures a smooth, unified user experience, with specialized capabilities always available on-demand.\nThis pattern is ideal for workflows where you only want one agent to control workflow execution and have access to the user." + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Translate 'hello' to Spanish, French and Italian for me!" + }, + { + "id": "B", + "text": "..." + }, + { + "id": "C", + "text": "Manager" + }, + { + "id": "D", + "text": "Task" + }, + { + "id": "E", + "text": "Task" + }, + { + "id": "F", + "text": "Task" + }, + { + "id": "G", + "text": "Spanish agent" + }, + { + "id": "H", + "text": "French agent" + }, + { + "id": "I", + "text": "Italian agent" + } + ], + "relationships": [ + { + "source": "A", + "target": "C" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "C", + "target": "F" + }, + { + "source": "D", + "target": "G" + }, + { + "source": "E", + "target": "H" + }, + { + "source": "F", + "target": "I" + } + ] + }, + { + "type": "header", + "text": "A practical guide to building agents" + }, + { + "type": "page_number", + "text": "18" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_23.json b/diagrams-and-tables/annotations/en_diagram_23.json new file mode 100644 index 0000000000000000000000000000000000000000..9216fdf1b8eb5c5614125a8eba290ddf86916084 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_23.json @@ -0,0 +1,69 @@ +[ + { + "type": "title", + "text": "Decentralized pattern" + }, + { + "type": "text", + "text": "In a decentralized pattern, agents can 'handoff' workflow execution to one another. Handoffs are a one way transfer that allow an agent to delegate to another agent. In the Agents SDK, a handoff is a type of tool, or function. If an agent calls a handoff function, we immediately start execution on that new agent that was handed off to while also transferring the latest conversation state.\nThis pattern involves using many agents on equal footing, where one agent can directly hand off control of the workflow to another agent. This is optimal when you don't need a single agent maintaining central control or synthesis—instead allowing each agent to take over execution and interact with the user as needed." + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Where is my order?" + }, + { + "id": "B", + "text": "Triage" + }, + { + "id": "C", + "text": "On its way!" + }, + { + "id": "D", + "text": "Issues and Repairs" + }, + { + "id": "E", + "text": "Sales" + }, + { + "id": "F", + "text": "Orders" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "B", + "target": "F" + }, + { + "source": "C", + "target": "F" + } + ] + }, + { + "type": "header", + "text": "A practical guide to building agents" + }, + { + "type": "page_number", + "text": "21" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_24.json b/diagrams-and-tables/annotations/en_diagram_24.json new file mode 100644 index 0000000000000000000000000000000000000000..c55d2e302857d2488ec60035b85149cbe71201e7 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_24.json @@ -0,0 +1,93 @@ +[ + { + "type": "title", + "text": "Mac computers with Apple silicon" + }, + { + "type": "title", + "text": "Boot process for a Mac with Apple silicon" + }, + { + "type": "text", + "text": "When a Mac with Apple silicon is turned on, it performs a boot process much like that of iPad and iPhone." + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Boot ROM validates LLB signature" + }, + { + "id": "B", + "text": "LLB validates system-paired firmware signatures" + }, + { + "id": "C", + "text": "Secure Enclave signed LocalPolicy" + }, + { + "id": "D", + "text": "LLB validates LocalPolicy signature" + }, + { + "id": "E", + "text": "Secure Enclave Boot ROM fetches LocalPolicy nonces from Secure Storage Component" + }, + { + "id": "F", + "text": "LLB evaluates iBoot stage 2 signature according to LocalPolicy" + }, + { + "id": "G", + "text": "iBoot stage 2 validates macOS-paired firmware, Boot Kernel Collection, Auxiliary Kernel Collection (if applicable), system trust cache, and signed system volume signatures, according to LocalPolicy" + }, + { + "id": "H", + "text": "macOS" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "D", + "target": "F" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "G", + "target": "H" + } + ] + }, + { + "type": "text", + "text": "The chip executes code from the Boot ROM in the first step in the chain of trust. macOS secure boot on a Mac with Apple silicon verifies not only the operating system code itself, but also the security policies and even kexts (supported, though not recommended) configured by authorized users.\nWhen the Low-Level Bootloader (LLB) is launched, it verifies the signatures and loads system-paired firmware for intra-SoC cores such as the storage, display, system management, and Thunderbolt controllers. LLB is also responsible for loading the LocalPolicy, which is a file signed by the Secure Enclave Processor. The LocalPolicy file describes the configuration that the user has chosen for the system boot and runtime security policies. The LocalPolicy has the same data structure format as all other boot objects, but it's signed locally by a private key that's available only within a particular computer's Secure Enclave instead of being signed by a central Apple server (like software updates).\nTo help prevent replay of any previous LocalPolicy, LLB must look up an anti-replay value from the Secure Enclave-attached Secure Storage Component. To do this, it uses the Secure Enclave Boot ROM and makes sure the anti-replay value in the LocalPolicy matches the anti-replay value in the Secure Storage Component. This helps prevent an old LocalPolicy—which could have been configured for lower security—from being reapplied to the system after security has been upgraded. The result is that secure boot on a Mac with Apple silicon helps protect not only against rollback of operating system versions but also against security policy downgrades." + }, + { + "type": "footer", + "text": "Apple Platform Security" + }, + { + "type": "page_number", + "text": "32" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_25.json b/diagrams-and-tables/annotations/en_diagram_25.json new file mode 100644 index 0000000000000000000000000000000000000000..bfba705159db3c7305a98e47deee035ed87aa690 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_25.json @@ -0,0 +1,133 @@ +[ + { + "type": "title", + "text": "System Integrity Protection (sip3)" + }, + { + "type": "text", + "text": "• Type: Boolean\n• Mutable environments: 1TR\n• Description: If sip3 is present and true, iBoot won't enforce its built-in allow list for the boot-args NVRAM variable, which would otherwise filter the options passed to the kernel. Users can change this field using csrutil or bputil from 1TR." + }, + { + "type": "title", + "text": "Certificates and RemotePolicy" + }, + { + "type": "text", + "text": "As described in LocalPolicy signing-key creation and management, the LocalPolicy Image4 also contains the Owner Identity Certificate (OIC) and the embedded RemotePolicy." + }, + { + "type": "title", + "text": "Intel-based Mac computers" + }, + { + "type": "title", + "text": "Boot process for an Intel-based Mac" + }, + { + "type": "title", + "text": "Intel-based Mac with an Apple T2 Security Chip" + }, + { + "type": "text", + "text": "When an Intel-based Mac computer with the Apple T2 Security Chip is turned on, the chip performs a secure boot from its Boot ROM in the same fashion as iPad, iPhone, and a Mac with Apple silicon. This verifies the iBoot bootloader and is the first step in the chain of trust. iBoot checks the kernel and kernel extension code on the T2 chip, which then checks the Unified Extensible Firmware Interface (UEFI) firmware. The UEFI firmware and the associated signature are initially available only to the T2 chip." + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Boot ROM evaluates iBoot signature" + }, + { + "id": "B", + "text": "iBoot evaluates T2 kernel cache signature" + }, + { + "id": "C", + "text": "T2 kernel cache evaluates UEFI firmware signature" + }, + { + "id": "D", + "text": "UEFI firmware" + }, + { + "id": "E", + "text": "UEFI firmware evaluates boot.efi signature" + }, + { + "id": "F", + "text": "boot.efi evaluates macOS immutable kernel signature" + }, + { + "id": "G", + "text": "macOS" + }, + { + "id": "H", + "text": "eSPI T2 chip" + }, + { + "id": "I", + "text": "Intel CPU" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "H" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "H" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "H" + }, + { + "source": "D", + "target": "H" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "E", + "target": "I" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "F", + "target": "I" + }, + { + "source": "G", + "target": "I" + } + ] + }, + { + "type": "footer", + "text": "Apple Platform Security" + }, + { + "type": "page_number", + "text": "47" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_26.json b/diagrams-and-tables/annotations/en_diagram_26.json new file mode 100644 index 0000000000000000000000000000000000000000..476b01248b09935d46d4ddd0d79a4e7e798778c8 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_26.json @@ -0,0 +1,149 @@ +[ + { + "type": "text", + "text": "Although Automatic Restart enhances security, it can inadvertently cause devices to lose their Wi-Fi connection upon restart. This loss of connectivity may disrupt device management service operations, especially in environments where persistent network access is critical." + }, + { + "type": "title", + "text": "Sealed Key Protection (SKP)" + }, + { + "type": "text", + "text": "On Apple devices that support Data Protection, the key encryption key (KEK) is protected (or sealed) with measurements of the software on the system, as well as being tied to the UID available only from the Secure Enclave. On a Mac with Apple silicon, the protection of the KEK is further strengthened by incorporating information about security policy on the system, because macOS supports critical security policy changes (for example, turning off secure boot or SIP) that are unsupported on other platforms. On a Mac with Apple silicon, this protection encompass FileVault keys, because FileVault is implemented using Data Protection (Class C).\nThe key that results from entangling the user password, long-term SKP key, and Hardware key 1 (the UID from Secure Enclave) is called the password-derived key. This key is used to protect the user keybag (on all supported platforms) and KEK (in macOS only), and then enable biometric unlock or auto unlock with other devices such as Apple Watch." + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Hardware measurement of sepOS" + }, + { + "id": "B", + "text": "User password" + }, + { + "id": "C", + "text": "xART key" + }, + { + "id": "D", + "text": "Hardware measurement of LLB Image4 manifest" + }, + { + "id": "E", + "text": "Lockable hardware registers" + }, + { + "id": "F", + "text": "Crypto-hardware resident derived key" + }, + { + "id": "G", + "text": "Long term SKP system key" + }, + { + "id": "H", + "text": "+" + }, + { + "id": "I", + "text": "Key encryption key" + }, + { + "id": "J", + "text": "+" + }, + { + "id": "K", + "text": "Volume encryption key" + }, + { + "id": "L", + "text": "Volume data" + }, + { + "id": "M", + "text": "LLB measurement of LocalPolicy" + }, + { + "id": "N", + "text": "Hardware key 1" + }, + { + "id": "O", + "text": "Hardware key 2" + } + ], + "relationships": [ + { + "source": "A", + "target": "E" + }, + { + "source": "B", + "target": "H" + }, + { + "source": "C", + "target": "J" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "G", + "target": "H" + }, + { + "source": "H", + "target": "I" + }, + { + "source": "I", + "target": "J" + }, + { + "source": "J", + "target": "K" + }, + { + "source": "K", + "target": "L" + }, + { + "source": "M", + "target": "E" + }, + { + "source": "N", + "target": "H" + }, + { + "source": "O", + "target": "J" + } + ] + }, + { + "type": "text", + "text": "The Secure Enclave Boot Monitor captures the measurement of the Secure Enclave OS that's loaded. When the Application Processor Boot ROM measures the Image4 manifest attached to LLB, that manifest contains a measurement of all other system-paired firmware that's loaded as well. The LocalPolicy contains the core security configurations for the macOS which are loaded. The LocalPolicy also contains the nsih field which is a hash of the macOS Image4 manifest. The macOS Image4 manifest contains measurements of all of the macOS-paired firmware and core macOS boot objects such as the Boot Kernel Collection or signed system volume (SSV) root hash.\nIf an attacker can unexpectedly change any of the above measured firmware, software, or security configuration components, it modifies the measurements stored in the hardware registers. The modification of the measurements causes the crypto-hardware-derived system measurement root key (SMRK) to derive to a different value, effectively breaking the seal on the key hierarchy. That causes the system measurement device key (SMDK) to be inaccessible, which in turn causes the KEK, and the data, to be inaccessible." + }, + { + "type": "footer", + "text": "Apple Platform Security" + }, + { + "type": "page_number", + "text": "99" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_27.json b/diagrams-and-tables/annotations/en_diagram_27.json new file mode 100644 index 0000000000000000000000000000000000000000..5a2632bdfa58c5f2f50d4aa17c029221ff54e411 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_27.json @@ -0,0 +1,148 @@ +[ + { + "type": "text", + "text": "• Require the user's password for decryption\n• Protect the system from a brute-force attack directly against storage media removed from Mac\n• Provide a swift and secure method for wiping content via deletion of necessary cryptographic material\n• Enable users to change their password (and in turn the cryptographic keys used to protect their files) without requiring reencryption of the entire volume" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "xART key" + }, + { + "id": "B", + "text": "Hardware key" + }, + { + "id": "C", + "text": "User password" + }, + { + "id": "D", + "text": "Hardware key" + }, + { + "id": "E", + "text": "+" + }, + { + "id": "F", + "text": "Key encryption key" + }, + { + "id": "G", + "text": "+" + }, + { + "id": "H", + "text": "Volume encryption key" + }, + { + "id": "I", + "text": "Volume data" + } + ], + "relationships": [ + { + "source": "A", + "target": "G" + }, + { + "source": "B", + "target": "G" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "G", + "target": "H" + }, + { + "source": "H", + "target": "I" + } + ] + }, + { + "type": "text", + "text": "On a Mac with Apple silicon and those with the T2 chip, all FileVault key handling occurs in the Secure Enclave; encryption keys are never directly exposed to the CPU. All APFS volumes are created with a volume encryption key by default. Volume and metadata contents are encrypted with this volume encryption key, which is wrapped with a key encryption key (KEK). The KEK is protected by a combination of the user's password and hardware UID when FileVault is turned on." + }, + { + "type": "title", + "text": "Internal storage with FileVault turned off" + }, + { + "type": "text", + "text": "If FileVault isn't turned on in a Mac with Apple silicon or a Mac with the T2 chip during the initial Setup Assistant process, the volume is still encrypted but the volume encryption key is protected only by the hardware UID in the Secure Enclave." + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "xART key" + }, + { + "id": "B", + "text": "Hardware key" + }, + { + "id": "C", + "text": "+" + }, + { + "id": "D", + "text": "Volume encryption key" + }, + { + "id": "E", + "text": "Volume data" + } + ], + "relationships": [ + { + "source": "A", + "target": "C" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "D", + "target": "E" + } + ] + }, + { + "type": "text", + "text": "If FileVault is turned on later—a process that's immediate because the data has already been encrypted—an anti-replay mechanism helps prevent the old key (based on hardware UID only) from being used to decrypt the volume. The volume is then protected by a combination of the user password with the hardware UID as previously described." + }, + { + "type": "footer", + "text": "Apple Platform Security" + }, + { + "type": "page_number", + "text": "105" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_28.json b/diagrams-and-tables/annotations/en_diagram_28.json new file mode 100644 index 0000000000000000000000000000000000000000..3d74fd07655ad6739fda8cb419d731c2c1b48c3b --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_28.json @@ -0,0 +1,197 @@ +[ + { + "type": "text", + "text": "In the next stage, spanning 2030-2055, the company plans to retire 49 GW of capacity from coal-fired power plants.$^{264}$ However, the country would need international support and concessional capital to accelerate planned retirements by 5 to 10 years and clear the path to replace retired coal capacity with RES (Exhibit 55)." + }, + { + "type": "diagram_caption", + "text": "Exhibit 55: PLN roadmap for early retirement of coal-fired power plant$^{265}$" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "2021" + }, + { + "id": "B", + "text": "2025" + }, + { + "id": "C", + "text": "2030" + }, + { + "id": "D", + "text": "2035" + }, + { + "id": "E", + "text": "2040" + }, + { + "id": "F", + "text": "2045" + }, + { + "id": "G", + "text": "2050" + }, + { + "id": "H", + "text": "2055" + }, + { + "id": "I", + "text": "2060" + }, + { + "id": "J", + "text": "Replace diesel power plants with RE power plants which have 1.1 GW BASELOAD" + }, + { + "id": "K", + "text": "Retirement CFPP Subcritical Plants stage I (1 GW)" + }, + { + "id": "L", + "text": "Retirement CFPP Subcritical Plants stage I (9 GW)" + }, + { + "id": "M", + "text": "Retirement CFPP Subcritical Plants (10 GW)" + }, + { + "id": "N", + "text": "Retirement CFPP Subcritical Plants stage I (24 GW)" + }, + { + "id": "O", + "text": "Retirement CFPP Subcritical Plants (5 GW)" + }, + { + "id": "P", + "text": "24 years (existing economic lifetime)" + }, + { + "id": "Q", + "text": "Early retirement" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "J" + }, + { + "source": "B", + "target": "P" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "K" + }, + { + "source": "C", + "target": "P" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "D", + "target": "L" + }, + { + "source": "D", + "target": "P" + }, + { + "source": "D", + "target": "Q" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "E", + "target": "M" + }, + { + "source": "E", + "target": "P" + }, + { + "source": "E", + "target": "Q" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "F", + "target": "N" + }, + { + "source": "F", + "target": "P" + }, + { + "source": "F", + "target": "Q" + }, + { + "source": "G", + "target": "H" + }, + { + "source": "H", + "target": "I" + }, + { + "source": "H", + "target": "O" + } + ] + }, + { + "type": "text", + "text": "Outside PLN, MPOs are being explored with IPPs. In 2022, an MOU between ADB and Cirebon Electric Power was signed to explore the early retirement of the Cirebon coal plants in West Java.$^{266}$ The ADB, CIF, and the Energy Transition Mechanism Partnership Trust Fund were listed as prospective sources of concessional capital." + }, + { + "type": "title", + "text": "3.4.10.2. Challenges and potential solutions\n\nSignificant investment required, with lack of mechanisms to generate returns [commercial feasibility - project economics]" + }, + { + "type": "text", + "text": "The most significant challenges to MPOs in Indonesia and elsewhere are the amount of capital required and the low returns. Foregone cash flows can reach hundreds of millions of dollars in a MPO, not counting the substantial amount of capital expenses that PLN and IPPs have invested into coal generation over the past decades. On top of this, there are cases where the investment of IPPs gets tied into PPAs with PLN under long-term contract conditions (up to 30 years), inflexible take-or-pay amounts, or fuel-cost transfer that would require restructuring for MPOs to be feasible.$^{267}$ Other binding factors associated with a coal asset also include fuel supply contracts and revenue-dependent interest rates set by financiers. These various forms of binding conditions pose hurdles to MPO not only from an asset-by-asset basis, but to grid planning, which lack the certainty or visibility of the phase out to ensure sufficient replacement power supply.\n\nNotwithstanding these factors, PLN has been evaluating the feasibility and commercial viability of candidate coal assets for MPO. In 2022, PLN shortlisted nine coal assets with a total book value of USD 5.6 billion as potential candidates to be considered for decommissioning before 2030.$^{268}$ In 2023, this list is further expanded to cover 16 coal fired power plants to be early retired conditionally before 2030.$^{269}$ Among this list, PLN and ADB further show that three plants – Suralya U1, Suralya U2, and Paiton U9 – can be the most suited for decommissioning and will be prioritized for retirement in the near-term." + }, + { + "type": "footer", + "text": "264 \"Intersessional Meeting of the CTF Trust Fund Committee,\" Climate Investment Fund, October 2022; \"CIF Accelerating Coal Transition (ACT): Indonesia Country Investment Plan (IP),\" Ministry of Finance, Government of Indonesia, October 3, 2022.\n265 \"Intersessional Meeting of the CTF Trust Fund Committee,\" Climate Investment Fund, October 2022, Link.\n266 \"ADB and Indonesia Partners Sign Landmark MOU on Early Retirement Plan for First Coal Power Plant Under Energy Transition Mechanism\", ADB, November 14, 2022, Link.\n267 \"Accelerating Just Energy Transition in Indonesia 2023,\" JETP, November 2023, Link.\n268 \"CIF Accelerating Coal Transition (ACT): Indonesia Country Investment Plan (IP),\" Government of Indonesia, October 3, 2022.\n269 \"Enhanced Sustainable Financing for Investment in Renewable Energy and Infrastructure Development,\" PLN, 2022." + }, + { + "type": "footer", + "text": "MUFG Asia Transition White Paper 2023" + }, + { + "type": "page_number", + "text": "86" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_29.json b/diagrams-and-tables/annotations/en_diagram_29.json new file mode 100644 index 0000000000000000000000000000000000000000..59af7147105f9de33ca8c02af27cb5cf6c02f275 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_29.json @@ -0,0 +1,304 @@ +[ + { + "type": "text", + "text": "New transaction broadcasts do not necessarily need to reach all nodes. As long as they reach many nodes, they will get into a block before long. Block broadcasts are also tolerant of dropped messages. If a node does not receive a block, it will request it when it receives the next block and realizes it missed one." + }, + { + "type": "title", + "text": "6. Incentive" + }, + { + "type": "text", + "text": "By convention, the first transaction in a block is a special transaction that starts a new coin owned by the creator of the block. This adds an incentive for nodes to support the network, and provides a way to initially distribute coins into circulation, since there is no central authority to issue them. The steady addition of a constant of amount of new coins is analogous to gold miners expending resources to add gold to circulation. In our case, it is CPU time and electricity that is expended.\nThe incentive can also be funded with transaction fees. If the output value of a transaction is less than its input value, the difference is a transaction fee that is added to the incentive value of the block containing the transaction. Once a predetermined number of coins have entered circulation, the incentive can transition entirely to transaction fees and be completely inflation free.\nThe incentive may help encourage nodes to stay honest. If a greedy attacker is able to assemble more CPU power than all the honest nodes, he would have to choose between using it to defraud people by stealing back his payments, or using it to generate new coins. He ought to find it more profitable to play by the rules, such rules that favour him with more new coins than everyone else combined, than to undermine the system and the validity of his own wealth." + }, + { + "type": "title", + "text": "7. Reclaiming Disk Space" + }, + { + "type": "text", + "text": "Once the latest transaction in a coin is buried under enough blocks, the spent transactions before it can be discarded to save disk space. To facilitate this without breaking the block's hash, transactions are hashed in a Merkle Tree [7][2][5], with only the root included in the block's hash. Old blocks can then be compacted by stubbing off branches of the tree. The interior hashes do not need to be stored." + }, + { + "type": "diagram_caption", + "text": "Transactions Hashed in a Merkle Tree" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Block" + }, + { + "id": "B", + "text": "Block Header (Block Hash)" + }, + { + "id": "C", + "text": "Prev Hash" + }, + { + "id": "D", + "text": "Nonce" + }, + { + "id": "E", + "text": "Root Hash" + }, + { + "id": "F", + "text": "Hash01" + }, + { + "id": "G", + "text": "Hash23" + }, + { + "id": "H", + "text": "Hash0" + }, + { + "id": "I", + "text": "Hash1" + }, + { + "id": "J", + "text": "Hash2" + }, + { + "id": "K", + "text": "Hash3" + }, + { + "id": "L", + "text": "Tx0" + }, + { + "id": "M", + "text": "Tx1" + }, + { + "id": "N", + "text": "Tx2" + }, + { + "id": "O", + "text": "Tx3" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "A", + "target": "G" + }, + { + "source": "A", + "target": "H" + }, + { + "source": "A", + "target": "I" + }, + { + "source": "A", + "target": "J" + }, + { + "source": "A", + "target": "K" + }, + { + "source": "A", + "target": "L" + }, + { + "source": "A", + "target": "M" + }, + { + "source": "A", + "target": "N" + }, + { + "source": "A", + "target": "O" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "E", + "target": "G" + }, + { + "source": "F", + "target": "H" + }, + { + "source": "F", + "target": "I" + }, + { + "source": "G", + "target": "J" + }, + { + "source": "G", + "target": "K" + }, + { + "source": "H", + "target": "L" + }, + { + "source": "I", + "target": "M" + }, + { + "source": "J", + "target": "N" + }, + { + "source": "K", + "target": "O" + } + ] + }, + { + "type": "diagram_caption", + "text": "After Pruning Tx0-2 from the Block" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Block" + }, + { + "id": "B", + "text": "Block Header (Block Hash)" + }, + { + "id": "C", + "text": "Prev Hash" + }, + { + "id": "D", + "text": "Nonce" + }, + { + "id": "E", + "text": "Root Hash" + }, + { + "id": "F", + "text": "Hash01" + }, + { + "id": "G", + "text": "Hash23" + }, + { + "id": "H", + "text": "Hash2" + }, + { + "id": "I", + "text": "Hash3" + }, + { + "id": "J", + "text": "Tx3" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "A", + "target": "G" + }, + { + "source": "A", + "target": "H" + }, + { + "source": "A", + "target": "I" + }, + { + "source": "A", + "target": "J" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "E", + "target": "G" + }, + { + "source": "G", + "target": "H" + }, + { + "source": "G", + "target": "I" + }, + { + "source": "I", + "target": "J" + } + ] + }, + { + "type": "text", + "text": "A block header with no transactions would be about 80 bytes. If we suppose blocks are generated every 10 minutes, 80 bytes * 6 * 24 * 365 = 4.2MB per year. With computer systems typically selling with 2GB of RAM as of 2008, and Moore's Law predicting current growth of 1.2GB per year, storage should not be a problem even if the block headers must be kept in memory." + }, + { + "type": "page_number", + "text": "4" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_30.json b/diagrams-and-tables/annotations/en_diagram_30.json new file mode 100644 index 0000000000000000000000000000000000000000..ab5e848eafd547d84c50c6a5ec23be754dcdc4b2 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_30.json @@ -0,0 +1,229 @@ +[ + { + "type": "title", + "text": "8. Simplified Payment Verification" + }, + { + "type": "text", + "text": "It is possible to verify payments without running a full network node. A user only needs to keep a copy of the block headers of the longest proof-of-work chain, which he can get by querying network nodes until he's convinced he has the longest chain, and obtain the Merkle branch linking the transaction to the block it's timestamped in. He can't check the transaction for himself, but by linking it to a place in the chain, he can see that a network node has accepted it, and blocks added after it further confirm the network has accepted it." + }, + { + "type": "diagram_caption", + "text": "Longest Proof-of-Work Chain" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Block Header" + }, + { + "id": "B", + "text": "Prev Hash" + }, + { + "id": "C", + "text": "Nonce" + }, + { + "id": "D", + "text": "Merkle Root" + }, + { + "id": "E", + "text": "Block Header" + }, + { + "id": "F", + "text": "Prev Hash" + }, + { + "id": "G", + "text": "Nonce" + }, + { + "id": "H", + "text": "Merkle Root" + }, + { + "id": "I", + "text": "Block Header" + }, + { + "id": "J", + "text": "Prev Hash" + }, + { + "id": "K", + "text": "Nonce" + }, + { + "id": "L", + "text": "Merkle Root" + }, + { + "id": "M", + "text": "Hash01" + }, + { + "id": "N", + "text": "Hash23" + }, + { + "id": "O", + "text": "Hash2" + }, + { + "id": "P", + "text": "Hash3" + }, + { + "id": "Q", + "text": "Tx3" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "E", + "target": "G" + }, + { + "source": "E", + "target": "H" + }, + { + "source": "I", + "target": "J" + }, + { + "source": "I", + "target": "K" + }, + { + "source": "I", + "target": "L" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "E", + "target": "J" + }, + { + "source": "H", + "target": "M" + }, + { + "source": "H", + "target": "N" + }, + { + "source": "N", + "target": "O" + }, + { + "source": "N", + "target": "P", + "label": "Merkle Branch for Tx3" + }, + { + "source": "P", + "target": "Q" + } + ] + }, + { + "type": "text", + "text": "As such, the verification is reliable as long as honest nodes control the network, but is more vulnerable if the network is overpowered by an attacker. While network nodes can verify transactions for themselves, the simplified method can be fooled by an attacker's fabricated transactions for as long as the attacker can continue to overpower the network. One strategy to protect against this would be to accept alerts from network nodes when they detect an invalid block, prompting the user's software to download the full block and alerted transactions to confirm the inconsistency. Businesses that receive frequent payments will probably still want to run their own nodes for more independent security and quicker verification." + }, + { + "type": "title", + "text": "9. Combining and Splitting Value" + }, + { + "type": "text", + "text": "Although it would be possible to handle coins individually, it would be unwieldy to make a separate transaction for every cent in a transfer. To allow value to be split and combined, transactions contain multiple inputs and outputs. Normally there will be either a single input from a larger previous transaction or multiple inputs combining smaller amounts, and at most two outputs: one for the payment, and one returning the change, if any, back to the sender." + }, + { + "type": "diagram_caption", + "text": "Transaction" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Transaction" + }, + { + "id": "B", + "text": "In" + }, + { + "id": "C", + "text": "In" + }, + { + "id": "D", + "text": "..." + }, + { + "id": "E", + "text": "Out" + }, + { + "id": "F", + "text": "..." + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "F" + } + ] + }, + { + "type": "text", + "text": "It should be noted that fan-out, where a transaction depends on several transactions, and those transactions depend on many more, is not a problem here. There is never the need to extract a complete standalone copy of a transaction's history." + }, + { + "type": "page_number", + "text": "5" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_31.json b/diagrams-and-tables/annotations/en_diagram_31.json new file mode 100644 index 0000000000000000000000000000000000000000..da5ebc30d6842a53436954f245ca1738f915dcd4 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_31.json @@ -0,0 +1,85 @@ +[ + { + "type": "title", + "text": "ii. Engaging Impacted Stakeholders" + }, + { + "type": "text", + "text": "The primary stakeholders potentially impacted by a QMM rating program comprise the \"6 Ps\" of the pharmaceutical supply chain: pharmaceutical manufacturers, purchasers, payors, pharmacies, providers, and patients (Figure 3). Stakeholder engagement has been a critical element in developing a CDER QMM program. In February 2020, CDER sponsored and participated in a workshop held by the Duke-Margolis Center for Health Policy at Duke University on Understanding How the Public Perceives and Values Pharmaceutical Quality. Stakeholders represented at this workshop included patients, healthcare providers, purchasers, pharmacies, and payors. These stakeholders identified three key areas for future work and collaboration across the stakeholder community: (i) assessing perceptions surrounding quality to improve communication, (ii) improving transparency, and (iii) developing quality ratings (22)." + }, + { + "type": "diagram_caption", + "text": "Figure 3. Stakeholders in the Pharmaceutical Supply Chain: The 6 Ps" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Pharmaceutical Manufacturers" + }, + { + "id": "B", + "text": "Purchasers" + }, + { + "id": "C", + "text": "Pharmacies" + }, + { + "id": "D", + "text": "Patients" + }, + { + "id": "E", + "text": "Payors" + }, + { + "id": "F", + "text": "Providers" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "C", + "target": "F" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "D", + "target": "F" + } + ] + }, + { + "type": "text", + "text": "Stakeholders at the Duke-Margolis workshop largely agreed that the need to develop and implement quality ratings for the industry is driven by the desire to differentiate products by an attribute other than price and provide a means for purchasers to consider factors other than price. The workshop discussion concluded with the idea that quality ratings may be an ideal topic on which Group Purchasing Organizations (GPOs) and FDA could work together. CDER suggested that, in particular, knowing more about the existing supply chain ratings used by GPOs might help in the development of a rating program. A key stakeholder group, GPOs account for over $100 billion of the drugs purchased in this country in a given year." + }, + { + "type": "footer", + "text": "Quality Management Maturity: Essential for Stable U.S. Supply Chains of Quality Pharmaceuticals" + }, + { + "type": "page_number", + "text": "9" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_32.json b/diagrams-and-tables/annotations/en_diagram_32.json new file mode 100644 index 0000000000000000000000000000000000000000..dec7179baa13892561ec32e79e53f08ffa3d64c1 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_32.json @@ -0,0 +1,225 @@ +[ + { + "type": "header", + "text": "Chapter 4 Outlook and Recommendations" + }, + { + "type": "text", + "text": "Figure 4-4 summarizes the expected future uses of F5G-A in the industrial field." + }, + { + "type": "title", + "text": "F5G-A: 100 billion connections, 10 Gbps experience, harmonized communication and sensing" + }, + { + "type": "diagram_caption", + "text": "Figure 4-4: Future uses of F5G-A in the industrial field" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "10 Gbps Everywhere" + }, + { + "id": "B", + "text": "eFBB Enhanced Fixed Broadband" + }, + { + "id": "C", + "text": "RRL Realtime Resilient Link" + }, + { + "id": "D", + "text": "GRE Guaranteed Reliable Experience" + }, + { + "id": "E", + "text": "OSV Optical Sensing and Visualization" + }, + { + "id": "F", + "text": "FFC Full-Fiber Connection" + }, + { + "id": "G", + "text": "GAO Green Agile Optical Network" + }, + { + "id": "H", + "text": "Enhance 3 traditional scenarios to drive generational upgrades" + }, + { + "id": "I", + "text": "Explore 3 new scenarios to unlock more possibilities" + }, + { + "id": "J", + "text": "eFBB: 10x bandwidth" + }, + { + "id": "K", + "text": "FFC: 10x connections" + }, + { + "id": "L", + "text": "GRE: Autonomous driving L3 -> L4" + }, + { + "id": "M", + "text": "GAO: 10x energy efficiency" + }, + { + "id": "N", + "text": "RRL: μs latency & 99.9999% reliability" + }, + { + "id": "O", + "text": "OSV: 1 m precision positioning with 99% accuracy" + }, + { + "id": "P", + "text": "• 10 Gbps campus,50G PON + Wi-Fi 7" + }, + { + "id": "Q", + "text": "• All-optical campus: Fiber-in copper-out, deterministic connections, multi-purpose networks" + }, + { + "id": "R", + "text": "• Premium private line/computing network: Service provisioning in seconds, management of millions of NEs, transmission capacity map, and service awareness" + }, + { + "id": "S", + "text": "• Green optical base: FMEC target network, E2E OXC, Alps-WDM\n• Premium transmission network: All-optical transmission with 1-5-20 ms latency circles, agile setup and release, enabling on-demand computing services" + }, + { + "id": "T", + "text": "• Industrial optical network: Carrier-grade industrical-grade, industrial production network upgrade, OSU hard pipe, multi-purpose network, and μs-level latency\n• Industrial field optical network Industrial optical bus, < 20 μs latency and 20 ns jitter, 99.9999% reliability" + }, + { + "id": "U", + "text": "Optical cable digitalization: Dumb resource management, digital ODN, and minute-level fault diagnosis" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "A", + "target": "G" + }, + { + "source": "B", + "target": "J" + }, + { + "source": "C", + "target": "N" + }, + { + "source": "D", + "target": "L" + }, + { + "source": "E", + "target": "O" + }, + { + "source": "F", + "target": "K" + }, + { + "source": "G", + "target": "M" + }, + { + "source": "H", + "target": "J" + }, + { + "source": "H", + "target": "K" + }, + { + "source": "H", + "target": "L" + }, + { + "source": "I", + "target": "M" + }, + { + "source": "I", + "target": "N" + }, + { + "source": "I", + "target": "O" + }, + { + "source": "J", + "target": "P" + }, + { + "source": "K", + "target": "Q" + }, + { + "source": "L", + "target": "R" + }, + { + "source": "M", + "target": "S" + }, + { + "source": "N", + "target": "T" + }, + { + "source": "O", + "target": "U" + } + ] + }, + { + "type": "text", + "text": "With ongoing digital upgrades in industries such as manufacturing, electric power, and ports, industrial production will require a 10 Gbps all-optical production network. The network must deliver over 10 Gbps of bandwidth and latency below 1 ms to support ultra-HD AOI quality checks and production line PLCs.$^{40}$ The China Telecom Research Institute recently worked with Huawei to complete the world's first 50G PON-based industrial Internet pilot. Huawei's 50G PON provides 10 Gbps bandwidth for campuses, offers reliable and flexible access for industrial AOI, and achieves ten times higher inspection efficiency, serving as a compelling example for intelligent manufacturing. Huawei is verifying its innovative 50G PON solution together with over 30 partners around the world.$^{41}$" + }, + { + "type": "title", + "text": "4.2.3 Net5.5G in the Industrial Sector" + }, + { + "type": "text", + "text": "Looking toward future industrial scenarios, Net5.5G will deliver more intelligent and secure networks with lower latency, increased bandwidth, and higher density capabilities. Net5.5G enables agile connections through end-to-end SRv6 multi-cloud networking and IPv6 Enhanced network slicing. Additionally, the synergy between the cloud, network, and device facilitates cloud-network-security integration. In terms of deterministic performance, Net5.5G ensures end-to-end millisecond-level latency. Regarding bandwidth, Wi-Fi 7 reaches peak speeds of 30 Gbps and delivers 500 Mbps anywhere. Finally, IoT and multiple Wi-Fi technologies are integrated to deliver unified IoT networking. For example, SPE supports speeds of up to 10 Mbps @ 1 kilometer or 100 Mbps @ 500 meters, enabling plug-and-play terminal devices, centralized management, and seamless, trusted access.\nWe anticipate that industrial wireless production, digital and intelligent production, and smart instruments will flourish with Net5.5G. Let's look at wireless production as an example. Devices" + }, + { + "type": "footer", + "text": "$^{40}$ See \"From Giga to 10Giga, Building an F5.5G All-Optical 10Giga City in 5 Scenarios\" on Huawei's official website.\n$^{41}$ See \"Huawei Launches Four Intelligent OptiX Innovative Practices of F5.5G, Accelerating 10Gbps Take-off\" on Huawei's official website." + }, + { + "type": "page_number", + "text": "98" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_33.json b/diagrams-and-tables/annotations/en_diagram_33.json new file mode 100644 index 0000000000000000000000000000000000000000..42e25fdb6dd8f7fd7d45b341bdd2d45c0736e951 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_33.json @@ -0,0 +1,99 @@ +[ + { + "type": "header", + "text": "GHTF Study Group 3 - Quality Management Systems\nProcess Validation Guidance – January 2004" + }, + { + "type": "page_number", + "text": "Page 6" + }, + { + "type": "text", + "text": "The interrelationship of design control and process development may, for some technologies, be very closely related. For others the relationship may be remote. The product should be designed robustly enough to withstand variations in the manufacturing process and the manufacturing process should be capable and stable to assure continued safe products that perform adequately. Often this results in a very interactive product development and process development activity." + }, + { + "type": "text", + "text": "Daily measuring and monitoring activities are conducted as specified by the process control plan which is often largely developed during process validation." + }, + { + "type": "text", + "text": "Corrective actions often identify inadequate processes/process validations. Each corrective action applied to a manufacturing process should include the consideration for conducting process validation/revalidation." + }, + { + "type": "title", + "text": "3.1 Process validation decision" + }, + { + "type": "text", + "text": "The following model may be useful in determining whether or not a process should be validated:" + }, + { + "type": "diagram_caption", + "text": "Figure 1: Process validation decision tree" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "A\nIs Process Output Verifiable" + }, + { + "id": "B", + "text": "B\nIs Verification Sufficient & Cost Effective" + }, + { + "id": "C", + "text": "C\nVerify & Control the Process" + }, + { + "id": "D", + "text": "D\nValidate" + }, + { + "id": "E", + "text": "E\nRedesign Product and/or Process" + } + ], + "relationships": [ + { + "source": "A", + "target": "B", + "label": "Yes" + }, + { + "source": "A", + "target": "D", + "label": "No" + }, + { + "source": "A", + "target": "E", + "label": "No" + }, + { + "source": "B", + "target": "C", + "label": "Yes" + }, + { + "source": "B", + "target": "D", + "label": "No" + }, + { + "source": "B", + "target": "E", + "label": "No" + }, + { + "source": "E", + "target": "A" + } + ] + }, + { + "type": "text", + "text": "The model shown describes a decision tree that a manufacturer can follow when deciding on whether a process needs to be validated. The process under consideration in this model is the simplest possible - many processes may be large and/or a complex set of sub-processes." + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_34.json b/diagrams-and-tables/annotations/en_diagram_34.json new file mode 100644 index 0000000000000000000000000000000000000000..2ec387917b979ec7e262cb39b2f2c42c5cbd6d29 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_34.json @@ -0,0 +1,116 @@ +[ + { + "type": "header", + "text": "Digital main blocks" + }, + { + "type": "header", + "text": "LIS3DSH" + }, + { + "type": "title", + "text": "4 Digital main blocks" + }, + { + "type": "title", + "text": "4.1 State machine" + }, + { + "type": "text", + "text": "The LIS3DSH embeds two state machines able to run a user-defined program.\nThe program is made up of a set of instructions that define the transition to successive states. Conditional branches are possible.\nFrom each state (n) it is possible to have a transition to the next state (n+1) or to a reset state. The transition to the reset point happens when \"RESET condition\" is true; The transition to the next step happens when \"NEXT condition\" is true.\nAn interrupt is triggered when the output/stop/continue state is reached.\nEach state machine allows implementing gesture recognition in a flexible way, free-fall, wake-up, 4D/6D orientation, pulse counter and step recognition, click/double-click, shake/double-shake, face-up/face-down, turn/double-turn:\n• Code and parameters are loaded by the host into dedicated memory areas for the state program\n• State program with timing based on ODR or decimated time\n• Possibility of conditional branches" + }, + { + "type": "diagram_caption", + "text": "Figure 6. LIS3DSH state machines: sequence of state to execute an algorithm" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "START" + }, + { + "id": "B", + "text": "State 1" + }, + { + "id": "C", + "text": "State 2" + }, + { + "id": "D", + "text": "State 3" + }, + { + "id": "E", + "text": "State n" + }, + { + "id": "F", + "text": "OUTPUT/STOP/CONTINUE" + }, + { + "id": "G", + "text": "INT set" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "C", + "label": "next" + }, + { + "source": "B", + "target": "B", + "label": "reset" + }, + { + "source": "C", + "target": "D", + "label": "next" + }, + { + "source": "C", + "target": "B", + "label": "reset" + }, + { + "source": "D", + "target": "E", + "label": "next" + }, + { + "source": "D", + "target": "B", + "label": "reset" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "E", + "target": "B", + "label": "reset" + }, + { + "source": "F", + "target": "G" + } + ] + }, + { + "type": "footer", + "text": "DocID022405 Rev 3" + }, + { + "type": "page_number", + "text": "20/58" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_35.json b/diagrams-and-tables/annotations/en_diagram_35.json new file mode 100644 index 0000000000000000000000000000000000000000..b61faabc575eb804faa844da7b03fb65646043fe --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_35.json @@ -0,0 +1,102 @@ +[ + { + "type": "header", + "text": "GDSN Operations Manual Release 3.1" + }, + { + "type": "title", + "text": "4 Use of XML in GS1 and GDSN" + }, + { + "type": "title", + "text": "4.1 GS1 XML Standards" + }, + { + "type": "text", + "text": "GS1 XML Standards are developed within the Global Standard Management Process (GSMP) by the GS1 user companies, GS1 Member Organisations and the GS1 Global Office.\n\nThe standards provide a flexible and extensible approach for transacting business-to-business communication. They have multi-sector and global applicability. GS1 XML Standards are based on the World Wide Web Consortium (W3C) XML specifications." + }, + { + "type": "title", + "text": "4.2 GS1 XML Architecture for GDSN Major Release 3" + }, + { + "type": "diagram_caption", + "text": "Figure 4-1 Schema relationships in Major Release 3" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "CatalogueItemNotification.xsd" + }, + { + "id": "B", + "text": "PackagingMarkingModule.xsd" + }, + { + "id": "C", + "text": "Message Schema" + }, + { + "id": "D", + "text": "Module Schema" + }, + { + "id": "E", + "text": "Domain Common Schema" + }, + { + "id": "F", + "text": "Shared Common Schema" + } + ], + "relationships": [ + { + "source": "A", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "C", + "target": "E", + "label": "imports\nGdsnCommon.xsd" + }, + { + "source": "D", + "target": "E", + "label": "imports\nGdsnCommon.xsd" + }, + { + "source": "C", + "target": "F", + "label": "imports" + }, + { + "source": "D", + "target": "G", + "label": "imports" + }, + { + "source": "E", + "target": "F", + "label": "imports\nSharedCommon.xsd" + } + ] + }, + { + "type": "text", + "text": "In the GS1 XML release 3 the business message components are defined in the XML schemas of three levels:\nShared Common schema - contains all the components that can be re-used across domains, e.g. EDI and GDSN, such as GS1 Identification Keys, Party Identification, etc.\nDomain Common – contains all the components that can be re-used within one domain, e.g. GDSN, such as PartyInRole, Certification, etc. The domain specific components are defined using the shared components when available. Thus, the GdsnCommon.xsd needs to import the SharedCommon.xsd\nMessage and Module schema – defines the structure of the actual message and the business document, as well as the content of the potential modules. The document and module specific components are defined using the shared and domain specific components when available. Thus, the BusinessMessage.xsd (e.g. CatalogueItemNotification.xsd, CatalogueItemSubscription.xsd) needs to import the SharedCommon.xsd and GdsnCommon.xsd\nMessage schema architecture includes layered structure introduced in release 2, with some changes." + }, + { + "type": "footer", + "text": "GDSN Release 3.1, Issue 7 Issue, Apr 2017 © 2018 GS1 AISBL" + }, + { + "type": "page_number", + "text": "Page 21 of 52" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_36.json b/diagrams-and-tables/annotations/en_diagram_36.json new file mode 100644 index 0000000000000000000000000000000000000000..c21c46fbe174a448b06a157645e0ef4e41b913ca --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_36.json @@ -0,0 +1,117 @@ +[ + { + "type": "header", + "text": "CDL HOSPITALITY TRUSTS" + }, + { + "type": "title", + "text": "SUSTAINABILITY REPORT" + }, + { + "type": "text", + "text": "OVERVIEW AND FINANCIAL REVIEW" + }, + { + "type": "text", + "text": "MARKET REVIEW" + }, + { + "type": "text", + "text": "LEADERSHIP STRUCYURE" + }, + { + "type": "text", + "text": "PROPERTY PORTFOLIO" + }, + { + "type": "text", + "text": "REPORTS" + }, + { + "type": "text", + "text": "This Report references the following topic-specific disclosures:\n• Disclosure 102-8 from GRI 102: General Disclosure 2016\n• Disclosure 302-1 and 302-3 from GRI 302: Energy 2016\n• Disclosure 303-5 from GRI 303: Water and Effluents 2018\n• Disclosure 401-1 from GRI 401: Employment 2016\n• Disclosure 403-9 from GRI 403: Occupational Health and Safety 2018\n• Disclosure 404-1 from GRI 404: Training and Education 2016\n• Disclosure 405-1 from GRI 405: Diversity and Equal Opportunity 2016\n• Disclosure 416-2 from GRI 416: Customer Health and Safety 2016\n• Disclosure 419-1 from GRI 419: Socioeconomic Compliance 2016\nCDLHT takes pride in continuously refining our sustainability strategy and practices. We welcome any feedback and comments regarding our Sustainability Report, which can be directed to Mr. Paul Kitamura (Head of Asset Management)." + }, + { + "type": "title", + "text": "SUSTAINABILITY GOVERNANCE" + }, + { + "type": "diagram_caption", + "text": "Sustainability Governance Structure" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "BOARD" + }, + { + "id": "B", + "text": "AUDIT & RISK COMMITTEE" + }, + { + "id": "C", + "text": "INTERNAL AUDIT" + }, + { + "id": "D", + "text": "CEO" + }, + { + "id": "E", + "text": "SUSTAINABILITY WORKING COMMITTEE (SWC)" + }, + { + "id": "F", + "text": "SUSTAINABILITY OFFICER" + }, + { + "id": "G", + "text": "OPERATIONS/FUNCTIONS" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "E", + "target": "G" + }, + { + "source": "F", + "target": "G" + } + ] + }, + { + "type": "text", + "text": "At CDLHT, the Managers' Boards are responsible for overseeing the seamless integration of sustainability into CDLHT's business goals and strategies. The Managers' Boards also play a role in managing and monitoring the material ESG factors and their performance. As CDLHT strives to achieve continuous sustainable growth, we have the Audit and Risk Committee (\"ARC\") acting as the strategic advisor for the Managers' Boards regarding sustainability strategies. The ARC convenes annually to review and challenge CDLHT's sustainability efforts and performance.\nCDLHT also has a Sustainability Working Committee (\"SWC\") comprising key personnel from various business functions and led by the CEO of the Managers, Mr. Vincent Yeo Wee Eng. The SWC, which manages and monitors CDLHT's overall sustainability performance, leads the development of strategies that incorporate material ESG factors into daily operations and is overseen by the ARC. From FY 2020 onwards, the SWC also has plans to provide periodic reports to the ARC and Managers' Boards on CDLHT's sustainability performance." + }, + { + "type": "page_number", + "text": "115" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_37.json b/diagrams-and-tables/annotations/en_diagram_37.json new file mode 100644 index 0000000000000000000000000000000000000000..70eff1114e4e1c5213bb02eab8ea5baf298c70ac --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_37.json @@ -0,0 +1,101 @@ +[ + { + "type": "header", + "text": "RA6W1 Datasheet" + }, + { + "type": "text", + "text": "• DMA\n• Wi-Fi subsystem\n• SDIO\n• Low-power retention mode to minimize power consumption\n• Can be selectively retained during Sleep modes\n• Store data or code." + }, + { + "type": "title", + "text": "8.2.4 Retention RAM" + }, + { + "type": "text", + "text": "Retention RAM is a 64 kB block of memory which is used during low-power Sleep modes to maintain the Wi-Fi operating state.\nWhen operating in DPM mode, a small application is also stored in retention memory that is executed directly upon a wake-up event to check if there are any pending Wi-Fi requests. This minimizes wake-up time and reduces the need to power up the full device if there is no activity." + }, + { + "type": "title", + "text": "Features" + }, + { + "type": "text", + "text": "• Low latency access\n• Low-power retention mode to minimize power consumption\n• Retained during Sleep modes\n• Store data or code." + }, + { + "type": "title", + "text": "8.2.5 OTP" + }, + { + "type": "text", + "text": "The OTP memory is used to store and protect important information essential for mass production and the management of end products, such as boot information, MAC addresses, and serial numbers. It is also used for storing secret information that is used by the advanced security functions like secure boot, secure debug, and secure asset storage. This secret information is programmed during a secure manufacturing process and then locked so that it cannot be accessed directly by CPU read or write operations therefore protecting it from external access.\nThe OTP memory array supports write accesses of 1 bit and read accesses of 32 bits by executing read/write commands through the OTP controllers register interface." + }, + { + "type": "diagram_caption", + "text": "Figure 6. OTP block diagram" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "AHB-CPU" + }, + { + "id": "B", + "text": "AHB Slave" + }, + { + "id": "C", + "text": "OTP IF" + }, + { + "id": "D", + "text": "OTP Controller" + }, + { + "id": "E", + "text": "OTP Memory" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "B", + "target": "C" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "D", + "target": "E" + } + ] + }, + { + "type": "text", + "text": "The OTP is a 2 kB one-time programmable memory which provides storage for permanent information." + }, + { + "type": "title", + "text": "Features" + }, + { + "type": "text", + "text": "• Storage for device secrets to provide high level of security" + }, + { + "type": "footer", + "text": "R19DS0136EK0100 Rev. 1.00 Nov 26, 2025 RENESAS CFR0011-120-00" + }, + { + "type": "page_number", + "text": "Page 59" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_38.json b/diagrams-and-tables/annotations/en_diagram_38.json new file mode 100644 index 0000000000000000000000000000000000000000..6fa28ad881827054529b9b49d437aa60a72c73f5 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_38.json @@ -0,0 +1,100 @@ +[ + { + "type": "header", + "text": "GDSN Operations Manual Release 3.1" + }, + { + "type": "diagram_caption", + "text": "Figure 2-3 UML Model of the Registry Catalogue Item Message" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "«abstract» Document" + }, + { + "id": "B", + "text": "EntityIdentification" + }, + { + "id": "C", + "text": "«root» RegistryCatalogueItem" + }, + { + "id": "D", + "text": "« » CatalogueItemReference" + }, + { + "id": "E", + "text": "« » CatalogueItemDates" + }, + { + "id": "F", + "text": "+ gpcCategoryCode: string [1..*] = {\\d{8}}\n+ sourceDataPool: GLN\n+ registryCatalogueItemStateCode: RegistryCatalogueItemStateEnumeration" + }, + { + "id": "G", + "text": "+ cancelDateTime : dateTime [0..1]\n+ deletionDateTime : dateTime [0..1]\n+ discontinuedDateTime : dateTime [0..1]\n+ lastChangedDateTime : dateTime [0..1]\n+ registrationDateTime : dateTime [0..1]" + } + ], + "relationships": [ + { + "source": "A", + "target": "C" + }, + { + "source": "B", + "target": "C", + "label": "1 +registryCatalogueItemIdentification" + }, + { + "source": "C", + "target": "D", + "label": "1" + }, + { + "source": "C", + "target": "F" + }, + { + "source": "C", + "target": "E", + "label": "0..1" + }, + { + "source": "D", + "target": "G" + } + ] + }, + { + "type": "title", + "text": "2.2.4 Communication Transfer Protocol" + }, + { + "type": "text", + "text": "All messages communicated 'in network' between the Data Pools themselves or between the Data Pool and the Global Registry are sent over the internet using the EDIINT AS2 communication protocol. This protocol is used for the exchange of information in a decentralised, distributed environment and was designed and codified by the Internet Engineering Task Force (IETF). AS2 uses the Hyper Text Transfer Protocol (HTTP) to build a tunnel to the recipient address, establish the connection, and then send the information in a secured environment assuring the sender of the receipt. The use of digital certificates is also implemented in the GDSN, so that the only entities that can communicate with the Global Registry are the GDSN-Certified Data Pools." + }, + { + "type": "title", + "text": "2.3 Catalogue Item Synchronisation and Global Registry Functionality" + }, + { + "type": "title", + "text": "2.3.1 Registry Catalogue Item (RCI) Registration" + }, + { + "type": "text", + "text": "The Registry Catalogue Item is the business message used to register trade item information from a data pool to the Global Registry within the GDSN Network. The process for this is shown in Figure 2-4." + }, + { + "type": "footer", + "text": "GDSN Release 3.1, Issue 7 Issue, Apr 2017 © 2018 GS1 AISBL" + }, + { + "type": "page_number", + "text": "Page 13 of 52" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_39.json b/diagrams-and-tables/annotations/en_diagram_39.json new file mode 100644 index 0000000000000000000000000000000000000000..6dd3399b8577e966c0fc90e84b78755a789d624d --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_39.json @@ -0,0 +1,121 @@ +[ + { + "type": "header", + "text": "GDSN Operations Manual Release 3.1" + }, + { + "type": "title", + "text": "2.3.1.1 Validation Rules" + }, + { + "type": "text", + "text": "Validation Rules are used in the GDSN to enforce business rules associated with Parties, Items, and Prices. They allow some validations that are likely to change occur outside of the schemas. Thanks to that, validations can be modified without having to implement a whole new set of schemas for each change.\nThe latest version of Validation Rules can be accessed here: http://www.gs1.org/gdsn/gdsn-validation-rules/3-1.\nThe validation rules performed on a CIN are driven by the product context of an item. Please refer to contexts in the GDSN Validation Rules BMS to see the context associated with your item and the relevant validation rules. Please note that validations for an item include both the list for All Contexts and the specific context of the trade item (based on GPC Brick)." + }, + { + "type": "title", + "text": "2.3.1.2 Context and the Population of Attributes" + }, + { + "type": "text", + "text": "Release 3.1 introduces the concept of context which allows for specific validations to be run based on the Process Context currently limited to Distributing Product Information (DPI) and Product Context (a grouping of similar products, for example Food, Beverage, Tobacco and Pet Food). While the CIN has attributes used to populate context for a trade item (contextIdentification) this attribute is not populated by the Data Source. Instead, the context for a trade item will be populated by the Source Data Pool based on the brick sent in the gpcCategoryCode attribute within the CIN. The GPC to Context Mapping document is used to map the GPC brick to the correct context. Population of the contextIdentification attribute for this release is informational only. The context is then used to determine the correct validations to be run for a trade item. Some validations relate to all contexts while other validations relate to specific contexts only. The validations run for a CIN will be the ones that apply to all contexts and the ones that apply to the specific context related to the GPC brick for the trade item. GS1 provides a mapping of modules per context (Modules by Context) but this document is not normative. Instead, the modules that need to be populated are driven by the validation rules that apply to the trade item. The process for determining the attributes that need to be sent for an item and thus the modules that need to be sent is summarized in the following figure:" + }, + { + "type": "diagram_caption", + "text": "Figure summarizing the process for determining attributes and modules" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Catalogue Item Notification Message" + }, + { + "id": "B", + "text": "GPC to Context Mapping Document" + }, + { + "id": "C", + "text": "BMS GDSN Validations" + }, + { + "id": "D", + "text": "Start" + }, + { + "id": "E", + "text": "Review GPC brick sent in CIN message" + }, + { + "id": "F", + "text": "Use GPC brick to determine context based on brick assignment to context" + }, + { + "id": "G", + "text": "Review validations based on context (rules for specific context and marked for all contexts)" + }, + { + "id": "H", + "text": "Populate attributes based on validations that apply to all contexts and 'brick' context" + }, + { + "id": "I", + "text": "End" + } + ], + "relationships": [ + { + "source": "A", + "target": "E" + }, + { + "source": "B", + "target": "F" + }, + { + "source": "C", + "target": "G" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "G", + "target": "H" + }, + { + "source": "H", + "target": "I" + } + ] + }, + { + "type": "text", + "text": "Please note that contextIdentification also exists at the component level. It is currently assumed that context will not be populated at the component level (ComponentInformation/contextIdentification)." + }, + { + "type": "title", + "text": "2.3.2 Catalogue Item Subscription (CIS) Registration" + }, + { + "type": "text", + "text": "The Catalogue Item Subscription is the business message used to communicate a request made by a Data Recipient for Trade Item information, with the intention of synchronising this data with the Data Source. The process for this is shown in Figure 2-5." + }, + { + "type": "footer", + "text": "GDSN Release 3.1, Issue 7 Issue, Apr 2017 © 2018 GS1 AISBL" + }, + { + "type": "page_number", + "text": "Page 15 of 52" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_40.json b/diagrams-and-tables/annotations/en_diagram_40.json new file mode 100644 index 0000000000000000000000000000000000000000..505f64d4eb1b0d90617753e4f31b47b3b53b81df --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_40.json @@ -0,0 +1,201 @@ +[ + { + "type": "header", + "text": "Version 1.1" + }, + { + "type": "header", + "text": "Introduction\n> Bank Supervision Organizational Structure, Roles, and Responsibilities" + }, + { + "type": "diagram_caption", + "text": "Figure 1: The OCC's Organizational Structure for Supervision" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Senior Deputy Comptroller and Chief Operating Officer" + }, + { + "id": "B", + "text": "Senior Deputy Comptroller for Midsize and Community Bank Supervision" + }, + { + "id": "C", + "text": "Senior Deputy Comptroller for Large Bank Supervision" + }, + { + "id": "D", + "text": "Community Bank Deputy Comptrollers" + }, + { + "id": "E", + "text": "Midsize Bank Deputy Comptrollers" + }, + { + "id": "F", + "text": "Deputy Comptroller for Thrift and Special Supervision" + }, + { + "id": "G", + "text": "Large Bank Deputy Comptrollers" + }, + { + "id": "H", + "text": "Associate Deputy Comptrollers" + }, + { + "id": "I", + "text": "Associate Deputy Comptrollers" + }, + { + "id": "J", + "text": "Examiners-in-Charge" + }, + { + "id": "K", + "text": "Assistant Deputy Comptrollers" + }, + { + "id": "L", + "text": "Assistant Deputy Comptrollers" + }, + { + "id": "M", + "text": "Director(s) for Special Supervision" + }, + { + "id": "N", + "text": "Senior Advisor for Thrift Supervision" + }, + { + "id": "O", + "text": "Team Leaders" + }, + { + "id": "P", + "text": "International Banking Supervision Directors" + }, + { + "id": "Q", + "text": "Examiners (including Portfolio Managers and Examiners-in-Charge)" + }, + { + "id": "R", + "text": "Examiners-in-Charge" + }, + { + "id": "S", + "text": "Problem Bank Specialists" + }, + { + "id": "T", + "text": "Examiners" + }, + { + "id": "U", + "text": "Examiners (including Portfolio Managers and Examiners-in-Charge)" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "B", + "target": "F" + }, + { + "source": "C", + "target": "G" + }, + { + "source": "D", + "target": "H" + }, + { + "source": "E", + "target": "I" + }, + { + "source": "G", + "target": "J" + }, + { + "source": "G", + "target": "P" + }, + { + "source": "H", + "target": "K" + }, + { + "source": "I", + "target": "L" + }, + { + "source": "F", + "target": "M" + }, + { + "source": "F", + "target": "N" + }, + { + "source": "J", + "target": "O" + }, + { + "source": "K", + "target": "Q" + }, + { + "source": "L", + "target": "R" + }, + { + "source": "M", + "target": "S" + }, + { + "source": "O", + "target": "T" + }, + { + "source": "P", + "target": "U" + } + ] + }, + { + "type": "text", + "text": "The Senior Deputy Comptrollers for Midsize and Community Bank Supervision (MCBS) and Large Bank Supervision (LBS) report to the COO. The OCC's Bank Supervision Policy Department, Economics Department, and Office of Innovation also report to the COO.\n\nMidsize and community banks are supervised under the Senior Deputy Comptroller for MCBS. The midsize deputy comptrollers are each supported by one or more associate deputy comptrollers (AsDC). The community bank deputy comptrollers include one for each district. There is also a Deputy Comptroller for Thrift Supervision and Special Supervision. Each district deputy comptroller is supported by one or more AsDCs. The Deputy Comptroller for Thrift Supervision and Special Supervision is supported by one or more directors for special supervision and a Senior Advisor for Thrift Supervision. Each of the MCBS deputy" + }, + { + "type": "footer", + "text": "Comptroller's Handbook" + }, + { + "type": "page_number", + "text": "6" + }, + { + "type": "footer", + "text": "Bank Supervision Process" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_41.json b/diagrams-and-tables/annotations/en_diagram_41.json new file mode 100644 index 0000000000000000000000000000000000000000..fb9561a4d7dc103755c66ddcf66cb8f9a4a89268 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_41.json @@ -0,0 +1,104 @@ +[ + { + "type": "header", + "text": "CDL HOSPITALITY TRUSTS" + }, + { + "type": "text", + "text": "OVERVIEW AND FINANCIAL REVIEW" + }, + { + "type": "text", + "text": "MARKET REVIEW" + }, + { + "type": "text", + "text": "LEADERSHIP STRUCTURE" + }, + { + "type": "text", + "text": "PROPERTY PORTFOLIO" + }, + { + "type": "text", + "text": "REPORTS" + }, + { + "type": "table", + "html": "
BOARD OF THE H-REIT MANAGER AND HBT TRUSTEE-MANAGER
CHAN SOON HEE, ERIC
Chairman and Non-Executive Director		RONALD SEAH LIM SIANG
Independent Non-Executive Director
VINCENT YEO WEE ENG
Chief Executive Officer and Executive Director		KENNY KIM
Independent Non-Executive Director
FOO SAY MUI (BILL)
Lead Independent Director		CHEAH SUI LING
Independent Non-Executive Director
" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "AUDIT AND RISK COMMITTEE OF THE H-REIT MANAGER AND HBT TRUSTEE-MANAGER" + }, + { + "id": "B", + "text": "FOO SAY MUI (BILL) Chairman" + }, + { + "id": "C", + "text": "RONALD SEAH LIM SIANG Member" + }, + { + "id": "D", + "text": "KENNY KIM Member" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + } + ] + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "NOMINATING AND REMUNERATION COMMITTEE OF THE H-REIT MANAGER AND HBT TRUSTEE-MANAGER" + }, + { + "id": "B", + "text": "RONALD SEAH LIM SIANG Chairman" + }, + { + "id": "C", + "text": "FOO SAY MUI (BILL) Member" + }, + { + "id": "D", + "text": "CHEAH SUI LING Member" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + } + ] + }, + { + "type": "page_number", + "text": "49" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_42.json b/diagrams-and-tables/annotations/en_diagram_42.json new file mode 100644 index 0000000000000000000000000000000000000000..c5227be066eba32472334c739d8ed3849a604098 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_42.json @@ -0,0 +1,93 @@ +[ + { + "type": "diagram_caption", + "text": "Figure 2: Nesting structure for models G through J" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "" + }, + { + "id": "B", + "text": "Public" + }, + { + "id": "C", + "text": "(Car)" + }, + { + "id": "D", + "text": "(Air)" + }, + { + "id": "E", + "text": "Train" + }, + { + "id": "F", + "text": "Bus" + }, + { + "id": "G", + "text": "Car" + }, + { + "id": "H", + "text": "Air" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "B", + "target": "F" + }, + { + "source": "C", + "target": "G" + }, + { + "source": "D", + "target": "H" + } + ] + }, + { + "type": "table_caption", + "text": "Table 3: Degenerate Nests" + }, + { + "type": "table", + "html": "
Model(G)
RUMNL		(H)
NNNL		(I)
RUMNL		(J)
NNNL
Coef.zCoef.zCoef.zCoef.z
const ×air-1.140-1.973.1583.413.6133.833.6133.83
train2.2315.5813.2313.142.6044.3513.2313.14
bus2.0665.1411.0782.792.1803.6911.0782.79
hinc ×air0.0010.100.0111.090.0131.090.0131.09
train-0.049-4.79-0.236-2.74-0.046-4.25-0.236-2.74
bus-0.044-4.20-0.167-2.19-0.033-2.94-0.167-2.19
time-0.003-3.79-0.039-4.66
time ×public-0.008-6.17-0.039-4.66
air-0.044-6.73-0.044-6.73
car-0.007-6.11-0.007-6.11
τ public0.0732.960.1973.780.1973.780.1973.78
τ air——*1.1443.86——*1—**
τ car——*0.1863.74——*1—**
Log likelihood-212.45-182.57-182.57-182.57
" + }, + { + "type": "text", + "text": "*: Parameter does not exist." + }, + { + "type": "text", + "text": "**: Parameter normalized to 1." + }, + { + "type": "page_number", + "text": "18" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_43.json b/diagrams-and-tables/annotations/en_diagram_43.json new file mode 100644 index 0000000000000000000000000000000000000000..5923c8b9bb27899b16e453134d489cd806ffff1c --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_43.json @@ -0,0 +1,133 @@ +[ + { + "type": "title", + "text": "Process vs procedures: What does this mean?" + }, + { + "type": "title", + "text": "The concept of process management was first introduced to the ISO 9001 series in the 2000 version of the international standard." + }, + { + "type": "text", + "text": "Whilst recognized by the experts on the standards committee as a key component of an effective management system, it caused many organizations problems with its introduction. Even now, with many organizations having certificates to confirm they meet the requirements of the standard, their approach to process can often be described as 'immature'.\n\nISO is not alone in recognizing the significance of process management. It is also at the heart of the EFQM Excellence Model and Baldridge Award schemes and reducing process variation is the focus of Six Sigma initiatives. Process management is also equally applicable to service and manufacturing organizations.\n\nIt can be argued that the achievement of an organization's objectives is critically affected by the performance of its people and its processes, and that successful organizations manage both effectively.\n\nTo begin to explain the approach, it may be useful to take a step backwards and reflect on the difference between policies, processes and procedures, which is often a source of confusion." + }, + { + "type": "title", + "text": "Policies" + }, + { + "type": "text", + "text": "These are the guidelines that drive the organization and its processes and procedures. They may be supported or influenced by defined standards or regulations.\n\nProcesses are a high level view of the organization's activities. The key tasks within the overall process are identified. Process descriptions usually refer to several individuals or teams as processes tend to flow across the organization. ISO defines a process as a set of interrelated or interacting activities which transforms inputs into outputs. So every process will have a clearly identified input and output, and depending on whether these are internal or external, there will also be a customer or set of customers.\n\nProcedures are the detailed steps that describe how a process step will be performed." + }, + { + "type": "title", + "text": "Understanding the process approach" + }, + { + "type": "text", + "text": "This guide provides an understanding of the concepts, intent and the application of the “process approach”. It also may be used to apply the process approach to any management system regardless of the type or the size of the organization. This includes, but is not limited to, management systems for:\n\n• Environment (ISO 14000 family)\n• Occupational Health and Safety\n• Business Risk\n• Social Responsibility\n\nA process approach is a powerful way of organizing and managing activities to create value for the customer and other interested parties.\n\nOrganizations are often structured into a hierarchy of functional units and usually managed vertically, with responsibility for the intended outputs being divided among the functional units.\n\nThe end customer is not always visible to all involved. Consequently, problems that occur at the interface boundaries between functions and teams are often given less priority than the short-term goals of the units. The process approach introduces horizontal management, crossing the barriers between different functional units and unifying their focus to the main goals of the organization.\n\nShown below is a typical process used in many organizations to bring a new product to market. It typically involves several functions and teams, all who are critical to achieving an effective process.\n\nA successful new product launch requires each of the departments to operate collaboratively with a common view of what success looks like. The reality is that often individual departmental goals and priorities take precedent. That is why managing the process and giving ownership can achieve the focus required to make the process successful." + }, + { + "type": "diagram_caption", + "text": "Typical process: Bringing new products to market" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Research market" + }, + { + "id": "B", + "text": "Marketing" + }, + { + "id": "C", + "text": "Create specification" + }, + { + "id": "D", + "text": "Development and marketing" + }, + { + "id": "E", + "text": "Develop solution" + }, + { + "id": "F", + "text": "Development" + }, + { + "id": "G", + "text": "Test with market" + }, + { + "id": "H", + "text": "Marketing" + }, + { + "id": "I", + "text": "Manufacture" + }, + { + "id": "J", + "text": "Operations" + }, + { + "id": "K", + "text": "Market and sell" + }, + { + "id": "L", + "text": "Sales and marketing" + } + ], + "relationships": [ + { + "source": "A", + "target": "C" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "E", + "target": "G" + }, + { + "source": "G", + "target": "I" + }, + { + "source": "I", + "target": "K" + }, + { + "source": "A", + "target": "B" + }, + { + "source": "C", + "target": "D" + }, + { + "source": "E", + "target": "F" + }, + { + "source": "G", + "target": "H" + }, + { + "source": "I", + "target": "J" + }, + { + "source": "K", + "target": "L" + } + ] + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_44.json b/diagrams-and-tables/annotations/en_diagram_44.json new file mode 100644 index 0000000000000000000000000000000000000000..cb87ef963f930702475d5fb4ddece16e624a6a7f --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_44.json @@ -0,0 +1,99 @@ +[ + { + "type": "title", + "text": "How will this affect organizations?" + }, + { + "type": "title", + "text": "5.1 Leadership and commitment" + }, + { + "type": "text", + "text": "Top management shall demonstrate leadership and commitment with respect to the XXX management system by:\n• Ensuring the XXX policy and XXX objectives are established and are compatible with the strategic direction of the organization\n• Ensuring the integration of the XXX management system requirements into the organization's business processes" + }, + { + "type": "title", + "text": "8.1 Operational planning and control" + }, + { + "type": "text", + "text": "The organization shall plan, implement and control the processes needed to meet requirements, and to implement the actions determined in 6.1, by:\n• Establishing criteria for the processes\n• Implementing control of the processes in accordance with the criteria\n• Keeping documented information, to the extent necessary, to have confidence that the processes have been carried out as planned\nThe organization also needs to ensure that outsourced processes are controlled.\nAll organizations are now required to determine the risks associated with each process. This is the clause that effectively replaces PREVENTIVE action which in itself caused many questions. So whilst existing techniques are still relevant, the organization now needs to demonstrate it has applied these to all processes within the scope of the management system." + }, + { + "type": "text", + "text": "There is now a requirement to establish measures for each process to determine their effectiveness. So whilst this may just be process output measures, effective systems will also have established measures for supply inputs, in process measures, as well as outputs and customer satisfaction measures (every process, even those that are only internal, has a customer for the output).\nIt requires that leadership establishes responsibilities and authorities for the processes, in other words ownership needs to be clear. This may cause some cultural problems where the defined business processes cross functional and departmental boundaries.\nManagement have to demonstrate that they are monitoring the impact of any process changes." + }, + { + "type": "text", + "text": "And in 7.2, it requires that competences have to be established for those involved with each process." + }, + { + "type": "title", + "text": "What does a process-based system look like?" + }, + { + "type": "text", + "text": "A process-based system normally consists of a high level, on page, description of the business process model. This is supported by each of the processes being defined at the next level of detail.\nProcedures and or work instructions are then used to define how certain tasks are carried out at each stage in the process (see the example below).\nTo help document and manage systems that follow this style of approach, there are many software products available and you may wish to have a look at BSI Entropy." + }, + { + "type": "diagram_caption", + "text": "Typical structure" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Holistic view" + }, + { + "id": "B", + "text": "Owner- Managing Director\nMeasure business performance\nFinance, customer, process, innovation" + }, + { + "id": "C", + "text": "A process" + }, + { + "id": "D", + "text": "A process" + }, + { + "id": "E", + "text": "Owner- Process Owner\nMeasure efficiency and effectiveness\nBasis for activity-based costing" + }, + { + "id": "F", + "text": "A procedure" + } + ], + "relationships": [ + { + "source": "A", + "target": "C", + "label": "'the what'" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "C", + "target": "F", + "label": "'the how'" + }, + { + "source": "A", + "target": "B" + }, + { + "source": "D", + "target": "E" + }, + { + "source": "G", + "target": "F" + } + ] + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_45.json b/diagrams-and-tables/annotations/en_diagram_45.json new file mode 100644 index 0000000000000000000000000000000000000000..a22a351723ba48dd2f6e490d498b8f3c2e6ee37f --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_45.json @@ -0,0 +1,155 @@ +[ + { + "type": "diagram_caption", + "text": "Figure 10: Architecture of the Internal Industrial Data Space Connector" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Office Floor" + }, + { + "id": "B", + "text": "Shop Floor" + }, + { + "id": "C", + "text": "System Connector Modules" + }, + { + "id": "D", + "text": "System Connector Modules" + }, + { + "id": "E", + "text": "System Connector Modules" + }, + { + "id": "F", + "text": "System Connector Modules" + }, + { + "id": "G", + "text": "DATA AND CONTROL FLOW ENGINE" + }, + { + "id": "H", + "text": "Data App" + }, + { + "id": "I", + "text": "Data App" + }, + { + "id": "J", + "text": "Data App" + }, + { + "id": "K", + "text": "Data App" + }, + { + "id": "L", + "text": "SECURITY LAYER" + }, + { + "id": "M", + "text": "APPLICATION CONTAINER LAYER" + }, + { + "id": "N", + "text": "IDS AppStore" + }, + { + "id": "O", + "text": "External IDS Connector" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "C", + "target": "G", + "label": "get" + }, + { + "source": "D", + "target": "G" + }, + { + "source": "E", + "target": "G" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "G", + "target": "H", + "label": "get / put" + }, + { + "source": "G", + "target": "I" + }, + { + "source": "G", + "target": "J" + }, + { + "source": "G", + "target": "K" + }, + { + "source": "H", + "target": "N" + }, + { + "source": "K", + "target": "O" + } + ] + }, + { + "type": "title", + "text": "3.3.2 Internal Industrial Data Space Connector" + }, + { + "type": "text", + "text": "In terms of structure and functionality, the Internal Industrial Data Space Connector (INIC) is very similar to the EXIC. How-ever, an INIC is typically operated within a protected enterprise network. INICs have access to internal data sources and make data from there available to EXICs (see Figure 10). \nThe connector architecture basically uses technologies for application container management, in order to ensure a safe execution environment for the connector functionality. \nFor reasons of performance and to simplify communication, data intensive evaluation and analysis operations should take place as closely to the respective data source as possible. \nDue to safety requirements or limitation of resources, it may be necessary to execute certain data operations on other EXIC instances (a cloud provider, for example). Therefore the Industrial Data Space must allow for flexible distribution of data operations on various INIC and EXIC instances." + }, + { + "type": "title", + "text": "3.3.3 Industrial Data Space Broker and Industrial Data Space AppStore" + }, + { + "type": "text", + "text": "The software components of the Industrial Data Space Broker bring together data offers and data requests, execute clearing functions, and create reports on the use of data sources. \nThe Industrial Data Space AppStore provides data services and supports the joint creation and maintenance of vocabularies." + }, + { + "type": "page_number", + "text": "23" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_46.json b/diagrams-and-tables/annotations/en_diagram_46.json new file mode 100644 index 0000000000000000000000000000000000000000..1f5d7bbd442bd36ab62a100469cd3432ac752adf --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_46.json @@ -0,0 +1,65 @@ +[ + { + "type": "title", + "text": "2 Architecture Overview" + }, + { + "type": "text", + "text": "Blockchain technologies have evolved in distinct waves. Bitcoin$^{[1]}$ introduced the first decentralized ledger. The Ethereum network$^{[2]}$ transformed this concept into a general-purpose computing platform, unlocking new asset types like non-fungible tokens. When faced with significant scalability challenges, blockchains such as Solana$^{[3]}$ emerged to address these limitations. However, while focusing on the Scalability Trilemma — the trade-off between decentralization, scalability, and security — the applicability and usability of blockchains was overlooked, creating a barrier to mainstream adoption. This demands the rise of a new type of blockchain: purpose-built blockchains designed to address real-world challenges, creating programmable markets for new and complex asset types.\n\nStory is a purpose-built decentralized blockchain supercharged by a multi-core execution environment. It comprises a main execution core alongside multiple highly customized cores. The main core provides EVM equivalence, enabling rapid adoption of existing applications from the ecosystem. The Intellectual Property (IP) core, one of the specialized cores, efficiently handles intellectual property registration as a native asset class while optimizing operations across complex IP relationship graphs. This core transforms intelligence into programmable IP assets. Although Story focuses primarily on intellectual property, its flexible architecture enables the adoption of future cores that can expand far beyond IP-related applications." + }, + { + "type": "diagram_caption", + "text": "Figure 1: Story's Protocol Layers" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Applications" + }, + { + "id": "B", + "text": "Protocol Layers" + }, + { + "id": "C", + "text": "The Execution Layer" + }, + { + "id": "D", + "text": "The Storage Layer" + }, + { + "id": "E", + "text": "The Consensus Layer" + }, + { + "id": "F", + "text": "The Networking Layer" + } + ], + "relationships": [ + { + "source": "B", + "target": "C" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "B", + "target": "E" + } + ] + }, + { + "type": "text", + "text": "Story runs on a decentralized set of nodes (or validators) connected through a peer-to-peer network layer. These nodes work together to maintain consensus, process transactions, and protect the integrity of the chain, creating a secure decentralized network open to all participants who follow the rules of the protocol. Following the principle of separation of concerns, the protocol is divided into three layers: an execution layer, a storage layer, and a consensus layer." + }, + { + "type": "page_number", + "text": "2" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_47.json b/diagrams-and-tables/annotations/en_diagram_47.json new file mode 100644 index 0000000000000000000000000000000000000000..ea5a5a928c7b33109d1d173e8fb3adfffdb28384 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_47.json @@ -0,0 +1,97 @@ +[ + { + "type": "header", + "text": "2.1 The Execution Layer" + }, + { + "type": "text", + "text": "The Execution Layer serves as the computational foundation of the network, handling the execution of all transactions and smart contracts. It is powered by a main core and several specialized cores working in harmony. This layer is designed to deliver maximum flexibility and computational power to each core while preserving network integrity and liveness." + }, + { + "type": "diagram_caption", + "text": "Figure 2: The multi-core design of the execution layer" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "The Execution Layer" + }, + { + "id": "B", + "text": "The Intellectual Property Core (IP Core)" + }, + { + "id": "C", + "text": "The Off-Chain Synchronization Core (Oracle Core)" + }, + { + "id": "D", + "text": "The Cross-Chain Communication Core (Bridge Core)" + }, + { + "id": "E", + "text": "The Main Execution Core" + }, + { + "id": "F", + "text": "The Artificial Intelligence Core (AI Core)" + }, + { + "id": "G", + "text": "The Zero-Knowledge Verification Core (ZK Core)" + }, + { + "id": "H", + "text": "Other Future Cores" + }, + { + "id": "I", + "text": "The Storage Layer" + }, + { + "id": "J", + "text": "The Consensus Layer" + } + ], + "relationships": [ + { + "source": "A", + "target": "B" + }, + { + "source": "A", + "target": "C" + }, + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "E" + }, + { + "source": "A", + "target": "F" + }, + { + "source": "A", + "target": "G" + }, + { + "source": "A", + "target": "H" + } + ] + }, + { + "type": "text", + "text": "The main core functions as the default execution environment, providing complete EVM compatibility. The main core processes all transactions and activates specialized cores whenever a transaction calls contracts within those cores. Each specialized core is an optimized execution environment that prioritizes specific requirements such as speed, scalability, safety, or privacy. For instance, the way in which data is modeled, stored and processed in certain applications can directly impact its scalability and even its feasibility. The complexity of the multi-core design is invisible to users, since each specialized core exposes its functionality through smart contracts that automatically engage when users interact with their associated contracts. All cores must comply with the following requirements:\n\n• Determinism: The outcome of the execution of any method call must be deterministic. For example, while a core might use GPUs for fast floating-point operations internally, the final result must always be consistent. Nondeterministic behavior jeopardizes the network's integrity and liveness.\n\n• Bounded and measurable resource consumption: Each core must accurately calculate the expected resource consumption (gas costs) in advance and in constant time for all contract calls based on their input parameters. Improper metering compromises network liveness and fair usage.\n\n• Storage: Each stateful core can store data as key/value pairs in its namespace within the storage layer, where data commitments are constructed for consensus. All key/value pair updates must follow a canonical format, and their order must remain deterministic." + }, + { + "type": "page_number", + "text": "3" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_48.json b/diagrams-and-tables/annotations/en_diagram_48.json new file mode 100644 index 0000000000000000000000000000000000000000..f25795d84169783d5cf9ccf540148cf820870015 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_48.json @@ -0,0 +1,125 @@ +[ + { + "type": "text", + "text": "The first release of Story deploys three specialized cores alongside the main core to address distinct needs: One core handles storage and operations for IP as a native asset class, another connects the onchain execution environment to the offchain world, and a cross-chain communication core enables IP asset usage across the broader blockchain ecosystem." + }, + { + "type": "title", + "text": "The Intellectual Property Core" + }, + { + "type": "text", + "text": "Intellectual property assets are represented on Story as multifaceted graphs in which various types of nodes (IP assets, licenses, etc) are connected through edges representing economic and legal relationships. These IP graphs track rights, licensing, and monetization across both original and derivative assets." + }, + { + "type": "diagram_caption", + "text": "Figure 3: An example graph of IP assets" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "IP" + }, + { + "id": "B", + "text": "IP" + }, + { + "id": "C", + "text": "IP" + }, + { + "id": "D", + "text": "IP" + }, + { + "id": "E", + "text": "Derivative IP" + }, + { + "id": "F", + "text": "Derivative IP" + }, + { + "id": "G", + "text": "Derivative IP" + }, + { + "id": "H", + "text": "License" + }, + { + "id": "I", + "text": "License" + }, + { + "id": "J", + "text": "License" + }, + { + "id": "K", + "text": "User" + } + ], + "relationships": [ + { + "source": "A", + "target": "E" + }, + { + "source": "B", + "target": "E" + }, + { + "source": "C", + "target": "F" + }, + { + "source": "C", + "target": "H" + }, + { + "source": "D", + "target": "G" + }, + { + "source": "E", + "target": "G" + }, + { + "source": "F", + "target": "G" + }, + { + "source": "F", + "target": "I" + }, + { + "source": "G", + "target": "J" + }, + { + "source": "H", + "target": "K" + }, + { + "source": "I", + "target": "K" + }, + { + "source": "J", + "target": "K" + } + ] + }, + { + "type": "text", + "text": "Deployed on the IP core, the Proof of Creativity (PoC) protocol is a natively enshrined protocol that provides both an open IP repository and a set of modules to interact with those IPs in a frictionless way. PoC is at once a standardized, universal ledger for IP assets across Story and a way to create digital markets around those assets as well as their rights. PoC traces the genealogy of IPs as they are used, expanded, and monetized across applications. Just as Git enabled the tracking of code through branching and versioning, this open repository makes Story the provenance and exchange layer for IP.\nIP owners can register their intellectual property and use PoC modules to define usage terms and royalty structure. Each intellectual property can be registered onchain as an IP-Asset (ERC-721) with an optional associated IP Account (a modified ERC-6551). Off-chain entities monitor registrations, validate IP holders' identities, provide attestations for registered IPs and their licenses, and can initiate a decentralized dispute process if infringement occurs. See Appendix A for more details on the PoC protocol.\nThe IP core supports PoC by providing native, efficient storage for IP-related assets, licenses, and attestations through optimized data models for intellectual property relationship graphs. The IP core also offers efficient native implementations for complex graph operations like traversals, which would otherwise be time-consuming and computationally expensive. For" + }, + { + "type": "page_number", + "text": "4" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_49.json b/diagrams-and-tables/annotations/en_diagram_49.json new file mode 100644 index 0000000000000000000000000000000000000000..809be09ac71e71fc2e0bacb56e10d013b20895e3 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_49.json @@ -0,0 +1,65 @@ +[ + { + "type": "title", + "text": "2.3 The Consensus Layer" + }, + { + "type": "text", + "text": "The consensus layer ensures network integrity, security, and stability by orchestrating block formation among all network participants. Recent years have witnessed remarkable advances and research breakthroughs in blockchain consensus mechanisms. This layer is designed to remain adaptable, allowing it to incorporate new consensus mechanisms as they emerge." + }, + { + "type": "diagram_caption", + "text": "Figure 7: Tendermint's block formation cycle (the happy path)" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Block Proposal" + }, + { + "id": "B", + "text": "Block Pre-Vote" + }, + { + "id": "C", + "text": "Block Pre-Commit" + }, + { + "id": "D", + "text": "Block Commit" + } + ], + "relationships": [ + { + "source": "A", + "target": "B", + "label": "If proposal valid" + }, + { + "source": "A", + "target": "D", + "label": "If commit successful" + }, + { + "source": "B", + "target": "C", + "label": "If reached pre-vote majority in time" + }, + { + "source": "C", + "target": "D", + "label": "If reached pre-commit majority in time" + } + ] + }, + { + "type": "text", + "text": "The initial release of Story uses a modern, performant implementation of Tendermint called CometBFT$^{[10]}$. Tendermint$^{[11]}$ is a Byzantine Fault Tolerant consensus engine that offers well-defined properties and customization options that align with our design needs:\n\n• Fault Tolerance: maintaining security even when 33% of validators are malicious or offline. The system ensures all honest nodes reach consensus on committed blocks and uses cryptographic proofs to identify and penalize bad actors.\n• Liveness Guarantees: The network continues to progress when more than two-thirds of validators (measured by voting power) remain active and participating.\n• Instant Finality: Transactions achieve finality quickly after being included in a block. This immediate finality ensures reliability for applications needing immutability - a key factor in user experience.\n• Modular Design: The Application Blockchain Interface (ABCI) decouples consensus from execution, enabling future consensus upgrades without impacting execution.\n\nThe consensus layer of Story uses a Proof-of-Stake (PoS) mechanism, with validators playing a crucial role in maintaining blockchain security and integrity. This creates a direct economic incentive for an honest and efficient operation, as malicious behavior results in penalties, including loss of staked tokens. The layer manages all operations related to staking, lockup requirements, and reward distribution." + }, + { + "type": "page_number", + "text": "8" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_diagram_50.json b/diagrams-and-tables/annotations/en_diagram_50.json new file mode 100644 index 0000000000000000000000000000000000000000..125416f1542116343da691a7fafb5bd636086eb8 --- /dev/null +++ b/diagrams-and-tables/annotations/en_diagram_50.json @@ -0,0 +1,129 @@ +[ + { + "type": "title", + "text": "Chain of Intelligence" + }, + { + "type": "text", + "text": "In the AI field, intellectual property assets encompass various forms of IP — from datasets and foundation ML models to fine-tuned models and model tuning packages." + }, + { + "type": "diagram_caption", + "text": "Figure 8: An example graph of AI-related IP assets" + }, + { + "type": "diagram", + "nodes": [ + { + "id": "A", + "text": "Fine-Tuned Model 4" + }, + { + "id": "B", + "text": "Fine-Tuned Model 3" + }, + { + "id": "C", + "text": "Reinforcement Fine-Tuned Model 2" + }, + { + "id": "D", + "text": "Model Fine-Tuning Package" + }, + { + "id": "E", + "text": "Fine-Tuned Model 1" + }, + { + "id": "F", + "text": "Dataset 6" + }, + { + "id": "G", + "text": "Dataset 1" + }, + { + "id": "H", + "text": "Baseline Model 2" + }, + { + "id": "I", + "text": "Dataset 4" + }, + { + "id": "J", + "text": "Dataset 5" + }, + { + "id": "K", + "text": "Dataset 2" + }, + { + "id": "L", + "text": "Dataset 3" + } + ], + "relationships": [ + { + "source": "A", + "target": "D" + }, + { + "source": "A", + "target": "H" + }, + { + "source": "B", + "target": "D" + }, + { + "source": "B", + "target": "H" + }, + { + "source": "C", + "target": "E" + }, + { + "source": "C", + "target": "F" + }, + { + "source": "D", + "target": "G" + }, + { + "source": "D", + "target": "H" + }, + { + "source": "E", + "target": "H" + }, + { + "source": "E", + "target": "I" + }, + { + "source": "E", + "target": "J" + }, + { + "source": "H", + "target": "K" + }, + { + "source": "H", + "target": "L" + } + ] + }, + { + "type": "text", + "text": "Figure 8 illustrates how IP assets form a chain of intelligence. A machine learning model (Model 2) may originate from a fine-tuned deep model (Model 1) that was enhanced through reinforcement learning using another dataset (Dataset 6). The fine-tuned deep model itself could be derived from a base model trained on multiple datasets. These training datasets may also be combinations of other datasets. Furthermore, there has been active research recently in developing standalone model fine-tuning packages. A model fine-tuning package contains all the necessary data for parameter-efficient model fine-tuning, which reduces trainable parameters while maintaining performance close to full fine-tuning. Since full model fine-tuning requires significant computational resources and memory, these packages offer an efficient alternative (i.e. Huggingface Adapters). State-of-the-art model fingerprinting techniques, such as OML, developed by the Sentient Protocol$^{[12]}$, can be used to capture the unique characteristics and essential attributes of a model when registering it as an IP asset on-chain.\nRegistering the entire chain of intelligence on Story enables for a genealogy of economic value that distributes revenue across the entire graph when it is generated at any single node. Story forms the basis for a market of high-quality datasets and model fine-tuning packages that leads to more performant ML models. This incentive structure encourages data providers to contribute high-quality datasets by guaranteeing fair compensation, which creates a flywheel for rapid AI progress. With transparent economic incentives and automated revenue distribution, Story becomes the negotiation, collaboration and settlement layer for a sustainable ecosystem where data providers, model developers, and end users work together seamlessly — all while maintaining proper attribution." + }, + { + "type": "page_number", + "text": "10" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_01.json b/diagrams-and-tables/annotations/en_nested_table_01.json new file mode 100644 index 0000000000000000000000000000000000000000..b165fb07415244ded2da096f0b0113c51623cf01 --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_01.json @@ -0,0 +1,34 @@ +[ + { + "type": "title", + "text": "1.1.1 Common Characteristics for a Business Signals" + }, + { + "type": "title", + "text": "Across All or Specific Usages of a Particular Type" + }, + { + "type": "text", + "text": "This profile item applies for Business Signals within or outside of the standard allowed set, if common characteristics apply. Specify in common profile table for a particular Business Transaction pattern type such as for all Commercial Transactions for a Receipt Acknowledgement or more generally for all Receipt Acknowledgements." + }, + { + "type": "table", + "html": "
Specification FeatureCommonality between different Business Signals
For all usages?
For a particular Business Transaction pattern and BT?
For all signals?

See: Set of concrete BT patterns, operational matrices and extensibility pattern (Data Exchange) derived from these.
Specification ReferenceSection 3.4.9, Spec
ProfilingWhere applicable, this profile item involves common characteristics across all or some of the usages of a Business Signal of a particular type (Receipt Acknowledgement, General Exception etc).
AlignmentSee Operational profile where applicable in Section 4.
Common characteristicsWhich operational semantics apply as defined in the BT patterns or user defined matrices? Specify in detail such as quality, non-repudiation, etc.
Test ReferencesSection 3.4.9.1, Spec
" + }, + { + "type": "footer", + "text": "ebXML_DPT-v1.1-ebBP20x-template-pr-01" + }, + { + "type": "footer", + "text": "04 December 2006" + }, + { + "type": "footer", + "text": "Copyright © OASIS Open 2005. All Rights Reserved." + }, + { + "type": "page_number", + "text": "Page 1 of 2" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_02.json b/diagrams-and-tables/annotations/en_nested_table_02.json new file mode 100644 index 0000000000000000000000000000000000000000..47c3caf5488419d5a00cf11817619f07b5775f06 --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_02.json @@ -0,0 +1,10 @@ +[ + { + "type": "table", + "html": "
7No further instructions.
8.1Subcontracting is not allowed.
8.2Not applicable.
9.1The SOCIAL SECURITY SYSTEM will hold a pre-bid conference for this Project as indicated in the Advertisement.
10.1The Procuring Entity's address is:

The Chairperson
BIDS AND AWARDS COMMITTEE
2nd Floor, SSS Main Building
East Avenue, Diliman, Quezon City
Tel No: (632)8922-1070, 8920-6401 loc. 5492 or 6382
E-mail: bac@sss.gov.ph
Website: http://www.sss.gov.ph
12.1(a)First Envelope:

(i) PhilGEPS Certificate of Registration and membership in accordance with Section 8.5.2 of the Revised IRR of RA 9184. For procurement to be performed overseas, it shall be subject to the Guidelines to be issued by the GPPB.

(ii) Statement of all its ongoing government and private contracts including contracts awarded but not yet started, if any, whether similar or not similar in nature and complexity to the contract to be bid (Form No. 4). The statement shall include, for each contract, the following:
(ii.1) name of the contract;
(ii.2) date of the contract;
(ii.3) contract duration;
(ii.4) owner's name, address, contact number and email address;
(ii.5) kinds of Goods;
(ii.6) amount of contract and value of outstanding contracts;
(ii.7) date of delivery; and
(ii.8) end user's acceptance or official receipt(s) or sales invoice issued for the contract, if completed, which shall be attached to the statements.

(iii) Statement of Single Largest Completed Contract similar to the project to be bid within the period of five (5) years prior to the date of submission and receipt of bids and equivalent to at least fifty percent (50%) of the ABC per lot. (Form No. 4)

Lot No.ReferenceABC Per Year
1SSS MAIN, POEA and EDSA LOT₱ 37,161,439.96
2SSS NCR PROPERTIES₱ 29,428,376.00

(iv) NFCC computation in accordance with ITB Clause 5.5 or a committed Line of Credit from a universal or commercial bank; (Form No. 5)
" + }, + { + "type": "page_number", + "text": "29" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_03.json b/diagrams-and-tables/annotations/en_nested_table_03.json new file mode 100644 index 0000000000000000000000000000000000000000..b422d6e2a2ec735d7629cf4be61392bd484332ba --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_03.json @@ -0,0 +1,14 @@ +[ + { + "type": "title", + "text": "Section V. Special Conditions of Contract" + }, + { + "type": "table", + "html": "
GCC Clause
1.1(g)The Procuring Entity is SOCIAL SECURITY SYSTEM.
1.1(i)The Supplier is [to be inserted at the time of contract award].
1.1(j)The Funding Source is
The Government of the Philippines (GOP) through the SSS Corporate Operating Budget for Maintenance/Repairs – Building – Security Services and Investment Income in the amount of as provided below:
Lot No.ReferenceABC Per Year
1SSS MAIN, POEA and EDSA LOT₱ 37,161,439.96
2SSS NCR PROPERTIES₱ 29,428,376.00
1.1(k)The Project sites are defined in Section VI. Schedule of Requirements and Annex “G”.
2.1No further instructions.
5.1The SOCIAL SECURITY SYSTEM's address for Notices is:
THE CHAIRPERSON
BIDS AND AWARDS COMMITTEE
2nd Floor, SSS Main Building
East Avenue, Diliman, Quezon City
Tel. No. (632) 8922-1070; 8920-6401 local 5492 & 6382
Email: bac@sss.gov.ph
Website: http://www.sss.gov.ph
The Supplier's address for Notices refers to winning bidder.
6.21. The WINNING BIDDER shall provide the Security Package and Protective Services as follows:
(a) To protect and safeguard the SSS's premises, equipment, assets, and other properties.
(b) To secure and protect the SSS's buildings and offices, including:
(i) those properties located elsewhere which the SSS may at any time request the WINNING BIDDER to guard and protect,
(ii) those properties for which the SSS is accountable, and;
" + }, + { + "type": "page_number", + "text": "48" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_04.json b/diagrams-and-tables/annotations/en_nested_table_04.json new file mode 100644 index 0000000000000000000000000000000000000000..358a2802438a3e88c91d9814b0707097ae94840b --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_04.json @@ -0,0 +1,10 @@ +[ + { + "type": "table", + "html": "
21.1The WINNING BIDDER shall be penalized by the concerned Division/SSS Security Department for violations committed in the Contract Implementation under the following Schedule of Offenses:
WINNING BIDDER’S VIOLATIONPENALTY
a) WINNING BIDDER has issued ammunition short of the requirement as per Contract or defective “dud” bullets.Deduction from the billing of P20.00 per bullet per day
b) WINNING BIDDER has not issued any magazine/holders for extra ammunition.Deduction from the billing of P200.00 per incident per day
c) WINNING BIDDER has not issued radio equipment or short of the number as per Agreement or issued item is unserviceable.Deduction from the billing of P200.00 per lacking, unserviceable, defective or unusable equipment (per equipment per day)
d) WINNING BIDDER has not issued the required equipment as per Agreement, such as but not limited to metal detectors, watchman clock, licensed handheld radio transceivers, licensed radio base with repeater and other accessories, bullhorns, flashlights, night stick, etc. or has issued one but unserviceable and/ or defective/ unusable.Deduction from the billing of P200.00 per lacking, unserviceable, defective or unusable equipment (per equipment per day)
e) WINNING BIDDER has not provided the service vehicle as per Agreement, or service vehicle is unserviceable.Deduction from the billing of P1,000.00 per incident per day
f) WINNING BIDDER has an unmanned security post as required per Agreement.Deduction from the billing of P200.00 per hour per incident.
g) WINNING BIDDER has not provided the required number of security guard and reliever as per Agreement.Deduction from the billing of P200.00 per lacking per day.
h) Security personnel not having twenty-four (24) hour rest day per cut-off period.Deduction from the billing of P200.00 per incident per day.
i) Straight duty of more than twelve (12) hours.Deduction from the billing of P200.00 per incident per day.

The SSS Security Department shall, likewise, impose on the WINNING BIDDER penalties for offenses or violations committed by its service personnel/guard, without prejudice to penalties as may be imposed by PNP-SOSIA, as follows:
" + }, + { + "type": "page_number", + "text": "57" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_05.json b/diagrams-and-tables/annotations/en_nested_table_05.json new file mode 100644 index 0000000000000000000000000000000000000000..4e46585722154f0df6568cf871f70e466abd5969 --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_05.json @@ -0,0 +1,10 @@ +[ + { + "type": "page_number", + "text": "1" + }, + { + "type": "table", + "html": "
Section I. Instructions to Bidders
A.General
1. Scope of Bid1.1 The Purchaser indicated in the Bidding Data Sheet (BDS), issues these Bidding Documents for the supply of Goods and Related Services incidental thereto as specified in Section VI, Schedule of Requirements. The name and identification number of this International Competitive Bidding (ICB) procurement are specified in the BDS. The name, identification, and number of lots of are provided in the BDS.
1.2 Throughout these Bidding Documents:
No.Details
athe term \"in writing\" means communicated in written form (e.g. by mail, e-mail, fax, telex) with proof of receipt
bif the context so requires, \"singular\" means \"plural\" and vice versa
c\"day\" means calendar day
2. Source of Funds2.1 The Borrower or Recipient (hereinafter called \"Borrower\") specified in the BDS has applied for or received financing (hereinafter called \"funds\") from the International Bank for Reconstruction and Development or the International Development Association (hereinafter called \"the Bank\") toward the cost of the project named in the BDS. The Borrower intends to apply a portion of the funds to eligible payments under the contract for which these Bidding Documents are issued.
2.2 Payments by the Bank will be made only at the request of the Borrower and upon approval by the Bank in accordance with the terms and conditions of the financing agreement between the Borrower and the Bank (hereinafter called the Loan Agreement), and will be subject in all respects to the terms and conditions of that Loan Agreement. The Loan Agreement prohibits a withdrawal from the loan account for the purpose of any payment to persons or entities, or for any import of goods, if such payment or import, to the knowledge of the Bank, is prohibited by decision of the United Nations Security Council taken under Chapter VII of the Charter of the United Nations. No party other than the Borrower shall derive any rights from the Loan Agreement or have any claim to the funds.
3. Fraud and(a) The Bank requires that Borrowers (including beneficiaries
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_06.json b/diagrams-and-tables/annotations/en_nested_table_06.json new file mode 100644 index 0000000000000000000000000000000000000000..321075f14582d47fbac5b1b6047db0490cf0f95f --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_06.json @@ -0,0 +1,14 @@ +[ + { + "type": "header", + "text": "Section I Instructions to Bidders" + }, + { + "type": "table", + "html": "
(iii) are not a dependent agency of the Purchaser.
4.5 Bidders shall provide such evidence of their continued eligibility satisfactory to the Purchaser, as the Purchaser shall reasonably request.
5. Eligible Goods and Related Services5.1 All the Goods and Related Services to be supplied under the Contract and financed by the Bank may have their origin in any country in accordance with Section V, Eligible Countries.
5.2 For purposes of this Clause, the term \"goods\" includes commodities, raw material, machinery, equipment, and industrial plants; and \"related services\" includes services such as insurance, installation, training, and initial maintenance.
5.3 The term \"origin\" means the country where the goods have been mined, grown, cultivated, produced, manufactured or processed; or, through manufacture, processing, or assembly, another commercially recognized article results that differs substantially in its basic characteristics from its components.
B. Contents of Bidding Documents
6. Sections of Bidding Documents6.1 The Bidding Documents consist of Parts 1, 2, and 3, which include all the Sections indicated below, and should be read in conjunction with any Addendum issued in accordance with ITB Clause 8.
PART 1 Bidding Procedures
SectionDetails
IInstructions to Bidders (ITB)
IIBidding Data Sheet (BDS)
IIIEvaluation and Qualification Criteria
IVBidding Forms
VEligible Countries
PART 2 Supply Requirements
Section VI. Schedule of Requirements
PART 3 Contract
Section VII. General Conditions of Contract (GCC)
" + }, + { + "type": "page_number", + "text": "3" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_07.json b/diagrams-and-tables/annotations/en_nested_table_07.json new file mode 100644 index 0000000000000000000000000000000000000000..68b47a4c4962013fd10a72e68e13023ab0154301 --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_07.json @@ -0,0 +1,14 @@ +[ + { + "type": "header", + "text": "Section I Instructions to Bidders" + }, + { + "type": "table", + "html": "
(a) be issued by a reputable institution selected by the bidder and located in any eligible country. If the institution issuing the bond is located outside the Purchaser's Country, it shall have a correspondent financial institution located in the Purchaser's Country to make it enforceable.
(b) be substantially in accordance with one of the forms of Bid Security included in Section IV, Bidding Forms, or other form approved by the Purchaser prior to bid submission;
(c) be payable promptly upon written demand by the Purchaser in case the conditions listed in ITB Clause 21.5 are invoked;
(d) be submitted in its original form; copies will not be accepted;
(e) remain valid for a period of 28 days beyond the validity period of the bids, as extended, if applicable, in accordance with ITB Clause 20.2;
21.3 If a Bid Security or a Bid- Securing Declaration is required in accordance with ITB Sub-Clause 21.1, any bid not accompanied by a substantially responsive Bid Security or Bid Securing Declaration in accordance with ITB Sub-Clause 21.1, shall be rejected by the Purchaser as non-responsive.
21.4 The Bid Security of unsuccessful Bidders shall be returned as promptly as possible upon the successful Bidder's furnishing of the Performance Security pursuant to ITB Clause 44.
21.5 The Bid Security may be forfeited or the Bid Securing Declaration executed:
(a) if a Bidder withdraws its bid during the period of bid validity specified by the Bidder on the Bid Submission Form, except as provided in ITB Sub-Clause 20.2; or
(b) if the successful Bidder fails to:
No.Details
isign the Contract in accordance with ITB Clause 43
iifurnish a Performance Security in accordance with ITB Clause 44

21.6 The Bid Security or Bid- Securing Declaration of a JV must be in the name of the JV that submits the bid. If the JV has not been legally constituted at the time of bidding, the Bid Security or
" + }, + { + "type": "page_number", + "text": "11" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_08.json b/diagrams-and-tables/annotations/en_nested_table_08.json new file mode 100644 index 0000000000000000000000000000000000000000..d6ff3d858cc1ce94e2370502b5dcf61f6e4ce50f --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_08.json @@ -0,0 +1,14 @@ +[ + { + "type": "header", + "text": "Section II Bid Data Sheet" + }, + { + "type": "page_number", + "text": "23" + }, + { + "type": "table", + "html": "
ITB 14.6 (a) (iii);(b)(ii) and (c)(v)\"Final destination (Project Site)\": [insert name of location where the Goods are to be actually used]
ITB 14.6 (b) (iii)In addition to the CIP price specified in ITB 14.6 (b)(i), the price of the Goods manufactured outside the Purchaser's Country shall be quoted: [insert appropriate Incoterm, other than CIP]
ITB 14.7The prices quoted by the Bidder [insert \"shall \"or \"shall not\"] be adjustable. If prices shall be adjustable, the methodology is specified in Section III Evaluation and Qualification Criteria.
ITB 14.8Prices quoted for each lot shall correspond at least to [insert figure] % of the items specified for each lot.
Prices quoted for each item of a lot shall correspond at least to [insert figure] percent of the quantities specified for this item of a lot.
ITB 15.1The Bidder [insert \"is\" or \"is not\"] required to quote in the currency of the Purchaser's Country the portion of the bid price that corresponds to expenditures incurred in that currency.
ITB 18.3Period of time the Goods are expected to be functioning (for the purpose of spare parts): [insert duration ]
ITB 19.1 (a)Manufacturer's authorization is: [insert \"required\" or \"not required\"]
ITB 19.1 (b)After sales service is: [insert \"required\" or \"not required\"]
ITB 20.1The bid validity period shall be [insert number] days.
ITB 21.1[insert one of the following options:
NoDetails
aNo Bid Security is required
bBid shall include a Bid Security (issued by bank or surety) included in Section IV Bidding Forms
cBid shall include \"Bid Securing Declaration\" using the form included in Section IV Bidding Forms
ITB 21.2The amount of the Bid Security shall be: [insert amount]
ITB 22.1In addition to the original of the bid, the number of copies is: [insert
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_09.json b/diagrams-and-tables/annotations/en_nested_table_09.json new file mode 100644 index 0000000000000000000000000000000000000000..ac443e927f6824a204dacb1c186289f95cd24c69 --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_09.json @@ -0,0 +1,14 @@ +[ + { + "type": "header", + "text": "Section II Bid Data Sheet" + }, + { + "type": "page_number", + "text": "25" + }, + { + "type": "table", + "html": "
Time: [insert time, and identify if a.m. or p.m. i.e. 10:30 a.m.]
ITB 27.1If electronic bid submission is permitted in accordance with ITB sub-clause 23.1, the specific bid opening procedures shall be: [insert description of the procedures]
E. Evaluation and Comparison of Bids
ITB 34.1Bid prices expressed in different currencies shall be converted in: [insert the name of the currency]

The source of exchange rate shall be: [insert the name of the source]

The date for the exchange rate shall be [insert day, month and year]
ITB 35.1Domestic preference [insert \"shall\" or \"shall not\"] be a bid evaluation factor.

[If domestic preference shall be a bid-evaluation factor, the methodology for calculating the margin of preference and the criteria for its application shall be as specified in Section III, Evaluation and Qualification Criteria.]
ITB 36.3(d)The adjustments shall be determined using the following criteria, from amongst those set out in Section III, Evaluation and Qualification Criteria: [refer to Schedule III, Evaluation and Qualification Criteria; insert complementary details if necessary]
No.Details.
aDeviation in Delivery schedule: [insert Yes or No. If yes insert the adjustment factor]
bthe cost of major replacement components, mandatory spare parts, and service: [insert Yes or No. If yes, insert the Methodology and criteria]
cthe availability in the Purchaser's Country of spare parts and after-sales services for the equipment offered in the bid [insert Yes or No, If yes, insert the Methodology and criteria]
dthe projected operating and maintenance costs during the life of the equipment [insert Yes or No, If yes, insert the Methodology and criteria]
ethe performance and productivity of the equipment offered; [Insert Yes or No. If yes, insert the Methodology and criteria]
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_10.json b/diagrams-and-tables/annotations/en_nested_table_10.json new file mode 100644 index 0000000000000000000000000000000000000000..1732070871c43fa5b768713bbefd16b4a064967b --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_10.json @@ -0,0 +1,14 @@ +[ + { + "type": "header", + "text": "Section IX Contract Forms" + }, + { + "type": "page_number", + "text": "31" + }, + { + "type": "table", + "html": "
characteristics from its components.
8. Notices8.1 Any notice given by one party to the other pursuant to the Contract shall be in writing to the address specified in the SCC. The term \"in writing\" means communicated in written form with proof of receipt.

8.2 A notice shall be effective when delivered or on the notice's effective date, whichever is later.
9. Governing Law9.1 The Contract shall be governed by and interpreted in accordance with the laws of the Purchaser's Country, unless otherwise specified in the SCC.
10. Settlement of Disputes10.1 The Purchaser and the Supplier shall make every effort to resolve amicably by direct informal negotiation any disagreement or dispute arising between them under or in connection with the Contract.

10.2 If, after twenty-eight (28) days, the parties have failed to resolve their dispute or difference by such mutual consultation, then either the Purchaser or the Supplier may give notice to the other party of its intention to commence arbitration, as hereinafter provided, as to the matter in dispute, and no arbitration in respect of this matter may be commenced unless such notice is given. Any dispute or difference in respect of which a notice of intention to commence arbitration has been given in accordance with this Clause shall be finally settled by arbitration. Arbitration may be commenced prior to or after delivery of the Goods under the Contract. Arbitration proceedings shall be conducted in accordance with the rules of procedure specified in the SCC.
No.Details.
athe parties shall continue to perform their respective obligations under the Contract unless they otherwise agree
bthe Purchaser shall pay the Supplier any monies due the Supplier

10.3 Notwithstanding any reference to arbitration herein,
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_11.json b/diagrams-and-tables/annotations/en_nested_table_11.json new file mode 100644 index 0000000000000000000000000000000000000000..1c371ca47b3d9fa31cb594c18008600f0e775c19 --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_11.json @@ -0,0 +1,14 @@ +[ + { + "type": "table", + "html": "
F. Tender Opening and Evaluation
24. Tender Opening24.1 Tenders shall be opened immediately after the deadline for submission of Tenders at the place as specified in the TDS but not later than ONE HOUR after expiry of the submission date line.
25. Evaluation process25.1 Tender Evaluation Committee (TEC) may consider a Tender as responsive in the Evaluation, only if it is submitted in compliance with the mandatory requirements set out in the Tender Document. The evaluation process should begin immediately after Tender opening following four steps:
(a) Preliminary Examination;
(b) Technical Examinations and Responsiveness;
(c) Financial evaluation and price comparison;
(d) Post-qualification of the lowest evaluated responsive Tenders.
26. Preliminary Examination26.1 The Procuring Entity shall examine the Tenders to confirm that all documentation requested in ITT Clause 4 has been provided, to determine the completeness of each document submitted.
26.2 TEC shall confirm that the following documents and information have been provided in the tender. If any of these documents or information is missing, the Tender shall be rejected:
No.Details
aTender Submission Letter
bPrice Schedule
cValid Tender Security
26.3 In the event, this Tender is invited under LTM; the following shall be applicable:
(a) Letter of Enlistment by the specified Procuring Entity;
(b) No Tender Security.
27. Technical Examinations & Responsiveness27.1 If a Tender is not responsive to the mandatory requirements set out in the Tender Document, shall not subsequently be made responsive by the Tenderer by correction of the material deviation, reservation, or omission.
27.2 There shall be no requirement as to the minimum number of responsive Tenders.
" + }, + { + "type": "footer", + "text": "Procurement of Microsoft Exchange and Office Hybrid Email Solution" + }, + { + "type": "page_number", + "text": "8" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_12.json b/diagrams-and-tables/annotations/en_nested_table_12.json new file mode 100644 index 0000000000000000000000000000000000000000..64950d63798092a3ff5e06738198bbc155d508b9 --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_12.json @@ -0,0 +1,14 @@ +[ + { + "type": "table", + "html": "
30.2 To evaluate a Tender, TEC will consider the following:
(a) Tender price for Item(s) or Lot
(b) adjustment for correction of arithmetical errors as stated under ITT Sub Clause 29;
(c) adjustment for application of the methodology for determining the equivalent lot value, as stated under ITT Sub Clause 15.6, as applicable.
30.3 Variations, deviations and other factors which are in excess of the requirements of the Tender Document or otherwise result in unsolicited benefits for the Procuring Entity will not be taken into account in Tender evaluation.
30.4 To determine the lowest-evaluated lot or combination of lots, the TEC will take into account:
the lowest-evaluated Tender for each item(s) or lot, as applicable
the resources sufficient to meet the qualifying criteria for the individual lot or aggregate of the qualifying criteria for the multiple lots
30.5 If the winning lot is missing some item(s), as stated under ITT Sub Clause 23.8, comprising twenty (20) percent or less number of items in the lot, the Procuring Entity may procure those missing item(s) from the other responsive Tenderer(s) quoting the lowest price for the missing item(s).
31. Price Comparison31.1 TEC will compare all responsive Tenders to determine the lowest-evaluated Tender, in accordance with ITT Clause 30.
31.2 The successful Tenderer as stated under ITT Sub Clauses 31.1 shall not be selected through lottery under any circumstances
32. Negotiation32.1 No negotiations shall be held during the Tender evaluation or award with the lowest or any other Tenderer.
33. Post-qualification33.1 The determination on Post-qualification shall be based upon an examination of the documentary evidence of the Tenderer's eligibility and qualifications submitted by the Tenderer as stated under ITT Clause 17, clarifications as stated under ITT Clause 28 and the qualification criteria as stated under ITT Clause 7,8 and 9. Factors not included therein shall not be used in the evaluation of the Tenderer's qualification.
34. Procuring Entity's Right to Accept any or to Reject Any or All Tenders34.1 The Procuring Entity reserves the right to accept any Tender or to reject any or all the Tenders any time prior to contract award and , to annul the Procurement proceedings with prior approval of the Head of the Procuring Entity, any
" + }, + { + "type": "footer", + "text": "Procurement of Microsoft Exchange and Office Hybrid Email Solution" + }, + { + "type": "page_number", + "text": "10" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_13.json b/diagrams-and-tables/annotations/en_nested_table_13.json new file mode 100644 index 0000000000000000000000000000000000000000..c4964d619350c2bbd7efc8d9741ee40d04429d3c --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_13.json @@ -0,0 +1,22 @@ +[ + { + "type": "table", + "html": "
40. Right to Complain40.1 Tenderer has the right to complain in accordance with the Public Procurement Act 2006 and the Public Procurement Rules, 2008.
" + }, + { + "type": "title", + "text": "Section 2. Tender Data Sheet" + }, + { + "type": "table", + "html": "
Instructions for completing the Tender Data Sheet are provided, as needed, in the notes in italics and under lined mentioned for the relevant ITT Clauses.
ITT ClauseAmendments of, and Supplements to, Clauses in the Instruction to Tenderers
A. General
ITT 1.1The Procuring Entity is Teletalk Bangladesh Limited
The Name of the Tender is: Procurement of
Tender Ref:
Lot No(s): single
ITT 3.1All potential Tenderers of Bangladesh are eligible to participate in the Procurement process.
B. Tender Document
ITT 6.1For clarification of Tender Document purposes only, the Procuring Entity's address is:
Attention:Additional General Manager, Procurement
Address:Teletalk Bangladesh Limited 11$^{th}$ Floor, Rajuk Commercial Complex 3/A, 5/A, 7/A, Road 17, Gulshan 1 Dhaka-1212 Bangladesh
Telephone:8801550155044
Fax No.:
e-mail address:md.shariful@teletalk.com.bd

and Contact the Procuring Entity within the period mentioned in the IFT.
" + }, + { + "type": "footer", + "text": "Procurement of Microsoft Exchange and Office Hybrid Email Solution" + }, + { + "type": "page_number", + "text": "13" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_14.json b/diagrams-and-tables/annotations/en_nested_table_14.json new file mode 100644 index 0000000000000000000000000000000000000000..c084bd832d5fc9713f6666ee77412fe02f93d3f8 --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_14.json @@ -0,0 +1,14 @@ +[ + { + "type": "table", + "html": "
C. Qualification Criteria
ITT 9.1(a)The minimum number of years of general experience of the Tenderer in the supply of Goods as Supplier shall be 5 (Five) years.
ITT 9.1(b)The minimum specific experience as Supplier in supply of Goods of at least one (1) contract successfully completed within the last 3 (Three) years, with a value of at least Tk. 15 (Fifteen) Lac.
ITT 10.1The minimum amount of liquid assets i.e working capital or credit line(s) of the Tenderer shall be Tk 20 (Twenty) Lac.
D. Preparation of Tender
ITT 15.3Tenders being invited for a single lot.
ITT 19.1The Tender Validity period shall be 60 days.
ITT 20.1The amount of the Tender Security shall be Tk. 50,000 (Fifty Thousand) in favour of Teletalk Bangladesh Limited.
E. Submission of Tender
ITT 22.1For Tender submission purposes only, the Procuring Entity's address is:
Attention:Additional General Manager
Address:Teletalk Bangladesh Limited
11$^{th}$ Floor, Rajuk Commercial
Complex 3/A, 5/A, 7/A, Road 17,
Gulshan 1 Dhaka-1212
Bangladesh
Telephone:8801550155044
Fax No.:
e-mail address:md.shariful@teletalk.com.bd

The deadline for submission of Tenders is mentioned in Invitation for Tender (IFT)
F. Opening and Evaluation of Tenders
ITT 24.1The Tender opening shall take place at :
Address: Department of
Procurement, Teletalk
Bangladesh Limited
11$^{th}$ Floor, Rajuk Commercial
Complex 3/A, 5/A, 7/A, Road 17,
" + }, + { + "type": "footer", + "text": "Procurement of Microsoft Exchange and Office Hybrid Email Solution" + }, + { + "type": "page_number", + "text": "14" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_15.json b/diagrams-and-tables/annotations/en_nested_table_15.json new file mode 100644 index 0000000000000000000000000000000000000000..1f604cd7d957ae3bd38411095430248872d4ec6b --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_15.json @@ -0,0 +1,26 @@ +[ + { + "type": "table", + "html": "
Gulshan 1 Dhaka-1212
Bangladesh
The deadline for opening of Tenders is mentioned in Invitation for Tender (IFT)
G. Contract Award
ITT 37.1The amount of Performance Security shall be 10 (Ten) percent of the Contract Price and, no Retention Money shall be deducted from the successful Tenderer's payable invoices during Contract implementation, if awarded the Contract.
" + }, + { + "type": "title", + "text": "Section 3 .General Conditions of Contract" + }, + { + "type": "title", + "text": "Section 4. Particular Conditions of Contract" + }, + { + "type": "table", + "html": "
Instructions for completing the Particular Conditions of Contract are provided, as needed, in the notes in italics mentioned for the relevant GCC Clauses
GCC ClauseAmendments of, and Supplements to, Clauses in the General Conditions of Contract
GCC 1.1 (i)The Procuring Entity is Teletalk Bangladesh Limited
GCC 5.1The documents to be furnished by the Supplier shall be as follows:
Supplier's invoice showing Goods' description, quantity, unit rates, total amount etc
Supplier's Warranty Certificate (if any)
GCC 8.1The Contract price is Tk.
GCC 13.1The Warranty Period shall be : 36 Months from the issuance of Acceptance Certificate.
" + }, + { + "type": "footer", + "text": "Procurement of Microsoft Exchange and Office Hybrid Email Solution" + }, + { + "type": "page_number", + "text": "15" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_16.json b/diagrams-and-tables/annotations/en_nested_table_16.json new file mode 100644 index 0000000000000000000000000000000000000000..5ac5decf223314801d07fa307a6b2b01f0409cb1 --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_16.json @@ -0,0 +1,18 @@ +[ + { + "type": "table", + "html": "
party. For example, a Supplier may only respond to a Purchase Order Request, after he has an indicator from a Distributor that a product component is available. The Supplier-Distributor relationship is specified elsewhere, such as in another Business Transaction outside of this definition.A ComplexBTA allows for nested BTAs to happen in a recursive sequential way and does not affect Business Transaction atomicity. The ComplexBTA provides a mechanism to implement / communicate dependencies between an actual business process (semantic process) and systems implementation of business processes (service choreography). A ComplexBTA is not a multi-party collaboration.
[ComplexBusinessTransactionActivity] element
CompositionUsage[How is this Business Transaction Activity to be composed?]
In its own Business Collaboration
In a Business Collaboration with other BTA
By a user community or domain
Is a ComplexBusinessTransactionActivity (Note: This is specific to element above not to XInclude or design composability)
Other (specify)

Note: When composition occurs in a domain or community, the transitions and condition expressions may differ. Therefore, they may be added later. This flexibility adds to the declarative power of ebBP. If the same Business Transaction Activity is defined for modular use and also within a Business Collaboration with other BTA, two profile items may be required to distinguish given the compositional characteristics may differ.
As needed, add other criteria in the Operational profile. Map into the Business Collaboration profile item in upcoming section.
Test ReferencesSpec (Spec package, ebBP v2.0.x)

Note: Valid for all reference unless specified.
" + }, + { + "type": "footer", + "text": "ebXML_DPT-v1.1-ebBP20x-template-pr-01\nCopyright © OASIS Open 2005. All Rights Reserved." + }, + { + "type": "footer", + "text": "04 December 2006" + }, + { + "type": "page_number", + "text": "Page 3 of 5" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_17.json b/diagrams-and-tables/annotations/en_nested_table_17.json new file mode 100644 index 0000000000000000000000000000000000000000..d1dd49674ff91121fc48f7a783b86fde61f67113 --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_17.json @@ -0,0 +1,22 @@ +[ + { + "type": "header", + "text": "Protocol N°: SBP-9330-101\nAltasciences Project Number: CNO-P5-319" + }, + { + "type": "header", + "text": "camino\nPHARMA" + }, + { + "type": "table", + "html": "
• Questionnaire on Smoking Urges – Brief version (QSU-Brief) responses
Test Product, Dose, and Mode of Administration (proposed):SBP-9330 75-mg, 150-mg and 300-mg capsules
Manufacturer: PACE Laboratory (previously Velesco Pharmaceutical Services, Inc.)
Small batches of 75-mg dose strength capsules will also be prepared by the Altasciences pharmacy using a Sponsor-supplied procedure.
Mode of administration: Oral
Placebo, Dose, and Mode of Administration:Placebo (visually matching SBP-9330 75-mg, 150-mg and 300-mg capsules)
Manufacturer: PACE Laboratory (previously Velesco Pharmaceutical Services, Inc.)
Mode of administration: Oral
Study Design:This is a single-center, first-in-human, randomized, double-blind, placebo-controlled, SAD/MAD study incorporating a food-effect cohort.
The study will include 3 parts:
• Part A: SAD phase with a nested food-effect cohort
• Part B: MAD phase
• Part C: Smoker phase
Part A - SAD Phase with Nested Food-Effect Cohort
Healthy adult nonsmoker subjects will be randomized to receive a single oral dose of either SBP-9330 or placebo in each of 5 planned SAD cohorts. Each cohort will consist of 8 subjects in 3:1 (SBP-9330:placebo) ratio to have a total of 6 subjects receiving SBP-9330 and 2 subjects receiving placebo.
The proposed SAD design and planned escalation are as follows:
CohortN(active:placebo)DoseDrug administration
A16:2
(1:1 [sentinel group] and 5:1 [remaining subjects])		150 mgSingle oral SBP-9330 or placebo administration
A26:2
(1:1 [sentinel group] and 5:1 [remaining subjects])		300 mgSingle oral SBP-9330 or placebo administration
A36:2
(1:1 [sentinel group] and 5:1 [remaining subjects] for Period 1 only)		600 mgSingle oral SBP-9330 or placebo administration under fasted and fed conditions in 2-period food-effect cohort with 7- to 14-day washout
A46:2
(1:1 [sentinel group] and 5:1 [remaining subjects])		1200 mgSingle oral SBP-9330 or placebo administration
A56:2
(1:1 [sentinel group] and 5:1 [remaining subjects])		2400 mgSingle oral SBP-9330 or placebo administration
" + }, + { + "type": "footer", + "text": "Version 4.0 (Amendment 3) - 2022/09/14" + }, + { + "type": "page_number", + "text": "Page 8 of 104" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_18.json b/diagrams-and-tables/annotations/en_nested_table_18.json new file mode 100644 index 0000000000000000000000000000000000000000..4b5a947a771563a2e957004a61ca173935210e93 --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_18.json @@ -0,0 +1,18 @@ +[ + { + "type": "header", + "text": "Protocol N°: SBP-9330-101\nAltasciences Project Number: CNO-P5-319" + }, + { + "type": "table", + "html": "
For Cohorts A1, A2, A4, and A5, each subject will receive the assigned treatment (SBP-9330 or placebo) under fasting conditions.
For Cohort A3 (2-period food-effect cohort), each subject will receive the randomly assigned treatment (SBP-9330 or placebo) under fasting conditions in Period 1. After a 7- to 14-day washout period, subjects will receive the same single dose of SBP-9330 or placebo in a fed state in Period 2, 30 minutes after the start of an FDA High-Fat and High-Calorie Breakfast. Escalation to Cohort A4 will be based only on the fasting period safety and PK and may proceed in parallel to the A3 fed period.
All cohorts in the fasting state will be dosed according to a sentinel dosing design to ensure optimal safety. Initially, 2 subjects will be dosed; 1 subject will be dosed with SBP-9330 and 1 subject with placebo. If the safety and tolerability results of the first 24 hours following dosing for the initial subjects are acceptable to the Investigator, the other 6 subjects (5 active and 1 placebo) may be dosed approximately 24 hours after dosing of the sentinel group.
Escalation to the next higher dose will only proceed if none of the stopping criteria have been reached and when the safety and tolerability and available plasma PK analysis of the previous dose, including delayed significant AEs in earlier cohorts, are acceptable to the Investigator, Sponsor and Data and Safety Monitoring Board (DSMB).
The SAD Phase will have a maximum of 5 cohorts. The number of cohorts may be changed at the discretion of the Sponsor depending on the emerging safety and plasma PK data from the previous cohorts. The dose levels proposed for SAD cohorts may be adjusted during the course of the study based on preliminary safety and plasma PK data but escalation will not be more than 3-fold the previous dose.
Part B - MAD Phase
Healthy adult nonsmoker subjects will be randomized to receive either SBP-9330 or placebo orally in each of the 3 planned MAD cohorts. Each cohort will consist of 10 subjects in 4:1 (SBP-9330:placebo) ratio to have a total of 8 subjects receiving SBP-9330 and 2 subjects receiving placebo. An additional MAD cohort (Cohort B4) may be added at the discretion of the Sponsor depending on emerging safety and plasma PK data from previous cohorts.
The proposed MAD design and planned escalation are as follows:
CohortN (active:placebo)DoseDrug administrations
B18:2adaptiveOnce daily oral administrations for 14 consecutive days
B28:2adaptiveOnce daily oral administrations for 14 consecutive days
B38:2adaptiveOnce daily oral administrations for 14 consecutive days
Additional B48:2adaptiveOnce daily oral administrations for 14 consecutive days
Each subject will receive once daily oral administration of the assigned treatment under fasting conditions (SBP-9330 or placebo) for 14 consecutive days.
" + }, + { + "type": "footer", + "text": "Version 4.0 (Amendment 3) - 2022/09/14 Page 9 of 104" + }, + { + "type": "page_number", + "text": "Page 9 of 104" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_19.json b/diagrams-and-tables/annotations/en_nested_table_19.json new file mode 100644 index 0000000000000000000000000000000000000000..a5136fe0fd6b68402df714fe6ec40723346ca0c1 --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_19.json @@ -0,0 +1,18 @@ +[ + { + "type": "header", + "text": "Protocol N°: SBP-9330-101\nAltasciences Project Number: CNO-P5-319" + }, + { + "type": "table", + "html": "
The MAD phase of the study may commence in parallel to the SAD or thereafter. The decision on how early the MAD phase of the study may be started and the doses to be administered will be determined by the Sponsor after consultation with the DSMB based on emerging safety and PK data. The first MAD daily dose will be less than or equal to an already well-tolerated SAD dose for which complete safety and PK data are available.
All relevant safety and plasma PK data will be reviewed by the DSMB before any dose escalation. The dose levels proposed for MAD cohorts may be adjusted during the course of the study based on preliminary safety and PK data. The dosing frequency may also be changed from once daily to twice daily, without changing the total daily dose outlined in the protocol.
The MAD phase will have a maximum of 4 cohorts. The number of cohorts may be decreased at the discretion of the Sponsor depending on the emerging safety and PK data from the proceeding cohorts. The increase from one dose level to the next dose level will not be more than 3-fold. A MAD daily dose level cannot be higher than the highest dose level administered in the SAD phase.
All subjects who complete the study and those terminating early will be required to complete the End of study/Follow-up procedures.
Part C – Smoker Phase
Healthy adult smokers will be randomized to receive either SBP-9330 or placebo orally in each of the 2 planned smoker cohorts. Each cohort will consist of 10 subjects randomly assigned in a 4:1 (SBP-9330:placebo) ratio, for a total of 8 subjects receiving SBP-9330 and 2 subjects receiving placebo.
The proposed Smoker phase design and planned escalation are as follows:
CohortN (active:placebo)DoseDrug administrations
C18:2adaptiveOnce daily oral administrations for 14 consecutive days
C28:2adaptiveOnce daily oral administrations for 14 consecutive days
Additional C38:2adaptiveOnce daily oral administrations for 14 consecutive days
Each subject will receive once daily oral administration of the assigned treatment (SBP-9330 or placebo) under fasting conditions for 14 consecutive days.
The Smoker phase of the study may commence after completion of dosing in the MAD phase of the study. The Smoker cohort daily dose will be less than or equal to the highest MAD dose for which complete safety and PK data are available.
All relevant safety and PK data will be reviewed by the DSMB before any dose escalation. The DSMB will be provided the randomization code to aide in the review. The dose levels proposed for Smoker cohorts may be adjusted during the course of the study based on preliminary safety and PK data.
The Smoker phase will have a maximum of 3 cohorts. There are 2 planned cohorts and an additional cohort may be added depending on the emerging PK
" + }, + { + "type": "footer", + "text": "Version 4.0 (Amendment 3) - 2022/09/14 Page 10 of 104" + }, + { + "type": "page_number", + "text": "Page 10 of 104" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_20.json b/diagrams-and-tables/annotations/en_nested_table_20.json new file mode 100644 index 0000000000000000000000000000000000000000..f3ed3776a62daab6165931f21a8c47660200997d --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_20.json @@ -0,0 +1,18 @@ +[ + { + "type": "header", + "text": "Audit ID: QA-2026-X99 | Generation Date: 2026-02-02" + }, + { + "type": "title", + "text": "Quality Assurance Compliance & Technical Specification Matrix" + }, + { + "type": "text", + "text": "This technical annex provides a deep-dive analysis into the manufacturing tolerances and material integrity standards for the Aerospace-Grade Titanium fasteners. The data contained within the nested tables reflects real-time sensor telemetry and destructive testing results conducted at our Tier-1 facilities. Compliance with the ISO-9100 framework is mandatory for all sub-components listed herein. Discrepancies between the predicted structural fatigue and the observed results must be logged in the Non-Conformance Report (NCR) system. This technical annex provides a deep-dive analysis into the manufacturing tolerances and material integrity standards for the Aerospace-Grade Titanium fasteners. The data contained within the nested tables reflects real-time sensor telemetry and destructive testing results conducted at our Tier-1 facilities. Compliance with the ISO-9100 framework is mandatory for all sub-components listed herein. Discrepancies between the predicted structural fatigue and the observed results must be logged in the Non-Conformance Report (NCR) system." + }, + { + "type": "table", + "html": "
Standard RefTechnical Breakdown and Multi-Parameter Evaluation
AS-9100 Rev DThe following sub-matrix defines the stress-test parameters for the structural integrity of the airframe connectors. Each test cycle consists of 500,000 simulated flight hours under varying atmospheric pressures:
Test IDMetric PathThresholdVariance
STR-01Tensile Strength (MPa)1200 - 1350+/- 2.5%
STR-02Yield Strength (MPa)> 1100Nominal
FAT-09Fatigue Cycle Limit1.2 x 10^7Critical
COR-05Corrosion ResistanceGrade A+99.9%
THR-12Thermal Expansion8.6 μm/m·KHigh
HRD-02Rockwell HardnessC36 - C40+/- 1.0
ELG-04Elongation at Break> 10%Standard
DEN-01Material Density4.43 g/cm$^{3}$Exact
CON-08Electrical Cond.1.2% IACSMin
MAG-03Magnetic Perm.< 1.01 μStable
SUR-04Surface RoughnessRa 0.4 μmPassed

Note: Post-test inspection reveals that all structural components maintained their physical properties within the 95% confidence interval. Detailed spectroscopy images are attached in Appendix G for further review.
Audit Log 2This section has been verified by the chief auditor. All calibration certs are valid through December 2026. Maintenance logs are consistent with digital signatures.
Audit Log 3This section has been verified by the chief auditor. All calibration certs are valid through December 2026. Maintenance logs are consistent with digital signatures.
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_21.json b/diagrams-and-tables/annotations/en_nested_table_21.json new file mode 100644 index 0000000000000000000000000000000000000000..176a7774f9d2055861ff2027b7466e94ef84b079 --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_21.json @@ -0,0 +1,18 @@ +[ + { + "type": "header", + "text": "Regulatory Compliance Framework v2026.01 | Document ID: 8890-X" + }, + { + "type": "title", + "text": "Operational Risk Assessment & Mitigation Matrix" + }, + { + "type": "text", + "text": "The subsequent risk assessment matrix integrates multi-layered operational data points to ensure comprehensive oversight of critical infrastructure. All quantitative thresholds defined in the nested technical tables are derived from the ISO-31000 risk management framework. Analysts must prioritize the sub-components labeled 'Critical' and cross-reference them with the quarterly audit logs. This document remains the property of the compliance department and requires dual-factor authentication for digital access and revision control." + }, + { + "type": "table", + "html": "
Control DomainSub-process Evaluation & Performance Metrics
Data Integrity & Cloud SecurityFor cloud-native deployments, the integrity of the data pipeline is paramount. The following validation sub-matrix details the redundant encryption layers applied to at-rest and in-transit data packets across the primary zones:
LayerProtocolLatencyCompliance
APITLS 1.3<12msPassed
ComputeAES-256-GCM<5msPassed
StorageLUKS / KMIP<45msReview
BackupRSA-4096N/APassed
EdgeQUIC / UDP<8msPassed
AuthOIDC / SAML<150msCritical
LoggingSHA-3 Sign<3msPassed

Note: Any latency spikes exceeding the 50ms threshold in the 'Storage' layer must trigger an automated alert to the DevOps lead and the security operations center (SOC). Root cause analysis is mandatory for all 'Review' status items within 48 hours.
Audit Trace #1Verification of historical logs confirms that all previous anomalies have been addressed. The audit team performed a deep-dive analysis on the telemetry data and found no persistent vulnerabilities within the scope of this review.
Audit Trace #2Verification of historical logs confirms that all previous anomalies have been addressed. The audit team performed a deep-dive analysis on the telemetry data and found no persistent vulnerabilities within the scope of this review.
Audit Trace #3Verification of historical logs confirms that all previous anomalies have been addressed. The audit team performed a deep-dive analysis on the telemetry data and found no persistent vulnerabilities within the scope of this review.
Audit Trace #4Verification of historical logs confirms that all previous anomalies have been addressed. The audit team performed a deep-dive analysis on the telemetry data and found no persistent vulnerabilities within the scope of this review.
Audit Trace #5Verification of historical logs confirms that all previous anomalies have been addressed. The audit team performed a deep-dive analysis on the telemetry data and found no persistent vulnerabilities within the scope of this review.
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_22.json b/diagrams-and-tables/annotations/en_nested_table_22.json new file mode 100644 index 0000000000000000000000000000000000000000..1a6304521919cd22951a7426e506cf72bfaa7bf4 --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_22.json @@ -0,0 +1,22 @@ +[ + { + "type": "table", + "html": "
Security properties[List the message parts and associated security requirements – non-repudiation parameters.]
Message Part 1[non-repudiation settings]
Message Part 2[non-repudiation settings]
(others?)
Process operational semanticsIs non-repudiation of receipt required?
Certificates elements[List the certificates info and ID.]
Certificate 1
Certificate 2
(others?)
Communication medium[What transport may/must be used for this signal?]
If this maps to a web service abstract operation (name), what are the:
Interface name
Operation name
Operation step

[SignalMap] element
[map] attribute group
Business TransactionBusiness Transaction Activity[Specify what Business Transaction Activity of which these signals are integrated.]
What role is associated with this signal?
[businessTransactionActivityRef] attribute
[roleRef] attribute
Exception SignalException Signal DetailsIf an exception signal is used, are there allowed reasons associated with such signals relative to the expectations of the involved parties?
Note: Are these used for auditing or tracking purposes? For example, a Negative Acceptance Acknowledgement is related to Business or Performance reasons.
Catastrophic Condition (Exception Signal)Exception Signals Details[Are general exceptions related to catastrophic conditions to be used? ]
Note: These are outside of the choreography and Business Transactions themselves.
[GeneralExceptionType] element
" + }, + { + "type": "footer", + "text": "ebXML_DPT-v1.1-ebBP20x-template-pr-01" + }, + { + "type": "footer", + "text": "04 December 2006" + }, + { + "type": "footer", + "text": "Copyright © OASIS Open 2005. All Rights Reserved." + }, + { + "type": "page_number", + "text": "Page 4 of 5" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_23.json b/diagrams-and-tables/annotations/en_nested_table_23.json new file mode 100644 index 0000000000000000000000000000000000000000..a3af16a38e824c2a3ba92a104a53679e99653275 --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_23.json @@ -0,0 +1,22 @@ +[ + { + "type": "header", + "text": "EXECUTION VERSION // REF: ISDA-2026-X9 // SUBJECT TO MARGIN REQUIREMENTS" + }, + { + "type": "title", + "text": "Annex I: Collateral Management & Haircut Valuation Schedule" + }, + { + "type": "text", + "text": "The following schedule outlines the technical parameters for the daily valuation of eligible collateral. Pursuant to Section 13(b) of the Master Agreement, the Valuation Agent shall determine the Mid-Market value of each security asset class. The nested valuation matrix provided in Section 2.1 integrates credit default swap (CDS) spreads and liquidity discounts based on a 10-day Value-at-Risk (VaR) model at a 99% confidence interval. Any discrepancy in the calculated margin call must be disputed within two (2) Business Days following the delivery of the Margin Notice." + }, + { + "type": "table", + "html": "
Asset Class IDTechnical Valuation Methodology & Nested Risk Parameters
G10-GOVT-BOND2.1.1 Methodology Statement: The valuation of G10 Government Bonds involves a recursive discount factor analysis. The adjustment for 'Haircut' percentages is localized per maturity bucket, as detailed in the technical sub-matrix:
TenorHaircut %Liquidity AdjMin Spread
O/N0.50%0.021.5bps
1W0.75%0.051.8bps
1M1.20%0.102.2bps
3M1.50%0.152.5bps
6M2.00%0.183.0bps
1Y2.50%0.223.5bps
2Y3.20%0.304.2bps
5Y4.50%0.455.8bps
10Y6.00%0.657.5bps
20Y8.50%0.8510.2bps
30Y12.0%1.2515.0bps

The Agent reserves the right to modify the 'Min Spread' values in the event of extraordinary market volatility (Sigma > 3.5). The aforementioned parameters are cross-referenced with the Bloomberg Terminal API pricing source.
CORP-CREDITEvaluation for investment-grade corporate credit follows the same recursive model with an added multiplier of 1.45x for sector-specific risks.
" + }, + { + "type": "footer", + "text": "PAGE 1 OF 1 // MASTER VALUATION SCHEDULE // © 2026 GLOBAL FINANCE" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_24.json b/diagrams-and-tables/annotations/en_nested_table_24.json new file mode 100644 index 0000000000000000000000000000000000000000..d6c94b477b792cd6356d406eba1a60a9d677b124 --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_24.json @@ -0,0 +1,22 @@ +[ + { + "type": "header", + "text": "CLASSIFICATION: UNCLASSIFIED // PROJECT: DEEP-OCEAN-2026 // NODE: MARIANAS-X" + }, + { + "type": "title", + "text": "Technical Specification for Autonomous Deep-Sea Monitoring Arrays" + }, + { + "type": "text", + "text": "This specification dictates the operational parameters for modular sensor deployment at depths exceeding 6,000 meters. The integration of hydrothermal vent telemetry, acoustic backscatter analysis, and benthic sediment profiling requires a robust data-handling architecture. The matrices nested within Section 4.4 define the physical and chemical thresholds mandated by the International Seabed Authority (ISA). Deviations must be cross-referenced with the ISO-2026 environmental integrity standards to ensure long-term stability of the monitoring infrastructure." + }, + { + "type": "table", + "html": "
Monitoring DomainComplex Analytical Matrix (Sub-Tier Data & Protocols)
PHY-CHEM-BIO-014.4.1 Pre-Deployment Calibration Sequence:
[-] Calibrate piezoelectric transducers
[-] Verify salinity-conductivity parity
[-] Reset inertial navigation
The acoustic signature of the autonomous vehicle must be isolated from the ambient noise floor. Spectral density levels (expressed in dB re 1 μPa$^{2}$/Hz) are recorded across three primary bands. The nested technical matrix below isolates the specific harmonics observed during the trial phase:
Freq (Hz)Gain (dB)ThresholdPhase ΔResult
5013.5< 0.050.1πNOMINAL
10014.5< 0.050.2πNOMINAL
15015.5< 0.050.30000000
000000004
π		NOMINAL
20016.5< 0.050.4πNOMINAL
25017.5< 0.050.5πNOMINAL
30018.5< 0.050.60000000
00000001π		NOMINAL
35019.5< 0.050.70000000
00000001π		NOMINAL
40020.5< 0.050.8πNOMINAL
45021.5< 0.050.9πNOMINAL

Note: Gain values are adjusted for seawater attenuation coefficients (α) based on the Thorpe model. Future updates will incorporate the latest benthic pressure compensation algorithms.
Data IntegritySHA256_VERIFICATION_HASH_8F9B2C1A8F9B2C1A8F9B2C1A8F9B2C1A8F9B2C1A8F9B2C1A8F9B2C1A8F9B2C1A8F9B2C1A8F9B2C1A8F9B2C1A8F9B2C1A8F9B2C1A8F9B2C1A8F9B2C1A8F9B2C1A8F9B2C1A8F9B2C1A8F9B2C1A8F9B2C1A
" + }, + { + "type": "footer", + "text": "PAGE 1 | RESTRICTED ACCESS | © 2026 GLOBAL DEEP-SEA ALLIANCE" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_nested_table_25.json b/diagrams-and-tables/annotations/en_nested_table_25.json new file mode 100644 index 0000000000000000000000000000000000000000..b9e74e9aa51616aca4f1c600887cfbd849ae36ad --- /dev/null +++ b/diagrams-and-tables/annotations/en_nested_table_25.json @@ -0,0 +1,34 @@ +[ + { + "type": "title", + "text": "1.1.2 Common Characteristics for Business Documents" + }, + { + "type": "title", + "text": "Across All or Specific Usages of a Particular Type" + }, + { + "type": "text", + "text": "Any profiling info that is common to all Business Documents parts or Attachments may be moved up to the general Business Document / Attachments profile table. This profile item applies for Business Documents and/or Attachments, if common characteristics apply. Specify in common profile table for a class or type of business document such as all purchase orders." + }, + { + "type": "table", + "html": "
Specification FeatureCommonality between different Business Documents
For all usages?
For a particular Business Transaction pattern and BT?
Under specific conditions (condition expressions)?

See: Set of concrete BT patterns, operational matrices and extensibility pattern (Data Exchange) derived from these.
Specification ReferenceSection 3.4.9, Spec
Profiling[Where applicable, this profile item involves common characteristics across all or some of the usages of a logical Business Document of a particular type (all purchase orders for example), e.g. any reference to a particular vocabulary, external XML schemas, core components – UBL or UBL subset, OAG, etc.]
AlignmentBesides conformance to a document structure, any semantic constraint on content, format of fields, rules of composition. If some external methodology is used, what are the usage rules?
See Operational profile where applicable in Section 4.
Common characteristicsWhich operational semantics apply as defined in the BT patterns or user defined matrices? Specify in detail such as quality, non-repudiation of use and content, etc.
[isNonRepudiationRequired]
[documentSecurity] attribute group
Test Referencesany reference to content validation artifact – semantic rules, Schematron file, etc.
" + }, + { + "type": "footer", + "text": "ebXML_DPT-v1.1-ebBP20x-template-pr-01" + }, + { + "type": "footer", + "text": "04 December 2006" + }, + { + "type": "footer", + "text": "Copyright © OASIS Open 2005. All Rights Reserved." + }, + { + "type": "page_number", + "text": "Page 2 of 2" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_01.json b/diagrams-and-tables/annotations/en_simple_table_01.json new file mode 100644 index 0000000000000000000000000000000000000000..dd621d99776457b27bf33f3a2990ac8065ef704e --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_01.json @@ -0,0 +1,50 @@ +[ + { + "type": "title", + "text": "14) Bid Currencies" + }, + { + "type": "text", + "text": "14.1 All bid prices shall be quoted in Philippine Peso unless otherwise provided in the BDS. However, for purposes of bid evaluation, bids denominated in foreign currencies shall be converted to Philippine currency based on the exchange rate as published in the BSP Daily Reference Exchange Rate Bulletin on the day of the bid opening.$^{4}$" + }, + { + "type": "text", + "text": "14.2 If so allowed in accordance with ITB Clause 14.1, the Procuring Entity, for purposes of bid evaluation and comparing the bid prices, will convert the currencies in which the bid price is expressed to Philippine Peso at the foreign exchange rates." + }, + { + "type": "text", + "text": "14.3 Unless otherwise specified in the BDS, payment of the contract price shall be made in Philippine Peso." + }, + { + "type": "title", + "text": "15) Bid Validity" + }, + { + "type": "text", + "text": "15.1 Bids shall remain valid for the period specified in the BDS which shall not exceed one hundred twenty (120) calendar days from the date of the opening of bids." + }, + { + "type": "text", + "text": "15.2 Should it become necessary to extend the validity of the bids and the bid securities beyond one hundred twenty (120) calendar days, the Procuring Entity concerned shall request in writing all those who submitted bids for such extension before the expiration date therefor. Bidders, however, shall have the right to refuse to grant such extension without forfeiting their Bid Security." + }, + { + "type": "title", + "text": "16) Bid Security" + }, + { + "type": "text", + "text": "16.1 The Bidder, at its option, shall submit a Bid Security in the form and amount as stated in the BDS, which may include the following:" + }, + { + "type": "table", + "html": "
Form of Bid SecurityAmount of Bid Security (Not less than the required Percentage of the ABC)
(a) Cash or cashier's/manager's check issued by a bank.
For biddings conducted by LGUs, the Cashier's or Manager's check may be issued by other banks certified by the BSP as authorized to issue such financial instrument.		Two percent (2%)
(b) Bank draft/guarantee or irrevocable Letter of Credit issued by a bank; Provided, however, that it shall be confirmed or authenticated by aFive percent (5%)
" + }, + { + "type": "footer", + "text": "$^{4}$ RA No. 8183 or \"An Act to Assure Uniform Value to Philippine Coin and Currency.\"" + }, + { + "type": "page_number", + "text": "29" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_02.json b/diagrams-and-tables/annotations/en_simple_table_02.json new file mode 100644 index 0000000000000000000000000000000000000000..0374fdb2537cf4f43e40b0c025fe4940ca8eadb5 --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_02.json @@ -0,0 +1,38 @@ +[ + { + "type": "table", + "html": "
local bank, if issued by a foreign bank.
For biddings conducted by LGUs, the Bank Draft/ Guarantee, or irrevocable letter of credit may be issued by other banks certified by the BSP as authorized to issue such financial instrument.
(c) Surety bond callable upon demand issued by a surety or insurance company duly certified by the Insurance on as authorized to issue such security.Five percent (5%)
(d) Bid Securing DeclarationNot Applicable
" + }, + { + "type": "text", + "text": "The Bid Security shall be denominated in Philippine Peso and posted in favor of the Procuring Entity." + }, + { + "type": "text", + "text": "16.2 The Bid Security should be valid for the period specified in the BDS. Any bid not accompanied by an acceptable Bid Security shall be considered as non-responsive and rejected by the Procuring Entity." + }, + { + "type": "text", + "text": "16.3 In no case shall the Bid Security be returned later than the expiration of the bid validity period indicated in the Bidding Documents, unless it has been extended in accordance with Section 57.2 of the IRR. In case the bidder is required to extend its bid validity, the bidder may, at its discretion, substitute a Bid Securing Declaration for the extended period as a replacement of its Bid Security; Provided, that the option to substitute is indicated in the BDS." + }, + { + "type": "text", + "text": "16.4 Upon signing and execution of the contract, pursuant to ITB Clause 29, and the posting of the performance security pursuant to ITB Clause 30, the Bid Security of the successful Bidder's Bid Security will be discharged, but in no case later than its validity period as indicated in ITB Clause 15." + }, + { + "type": "text", + "text": "16.5 The Bid Security may be forfeited based on any of the following grounds, as provided under Rule VIII, X, XI, and XXI of the IRR:" + }, + { + "type": "text", + "text": "a) If a Bidder:" + }, + { + "type": "text", + "text": "i) With the Lowest Calculated Responsive Bid (LCRB), Most Economically Advantageous Responsive Bid (MEARB), Most Advantageous Responsive Bid (MARB), Single Calculated and Responsive Bid (SCRB), Single Economically Advantageous Responsive Bid (SEARB), or Single Advantageous Responsive Bid (SARB) withdraws, fails, refuses or is unable to: (i) submit the documents required under Section 66.5 of the IRR; (ii) enter into contract with the Procuring Entity; or (iii) post the required performance security within the period stipulated in the IRR and in accordance with ITB Clause 30;" + }, + { + "type": "page_number", + "text": "30" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_03.json b/diagrams-and-tables/annotations/en_simple_table_03.json new file mode 100644 index 0000000000000000000000000000000000000000..b3e2045f2dbfd1ab6cb33b8baa426b163303b1bc --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_03.json @@ -0,0 +1,30 @@ +[ + { + "type": "table", + "html": "
Form of Performance SecurityAmount of Performance Security (Not less than the Percentage of the Total Contract Price)
a) Cash or Cashier's or Manager's check issued by a bank.
For biddings conducted by LGUs, the cashier's or manager's check may be issued by other banks certified by the BSP as authorized to issue such financial instrument.		Ten percent (10%)
b) Bank draft or guarantee or irrevocable Letter of Credit issued by a local bank. If issued by a foreign bank, it shall be confirmed or authenticated by a local bank.
c) Surety bond callable upon demand issued by a surety or insurance company duly certified by the IC as authorized to issue such security.Thirty Percent (30%)
" + }, + { + "type": "text", + "text": "30.4 The performance security shall be denominated in Philippine Peso and posted in favor of the Procuring Entity, which shall be forfeited in the event it is established that the winning bidder is in default in any of its obligations under the contract." + }, + { + "type": "title", + "text": "31) Notice to Proceed" + }, + { + "type": "text", + "text": "The Procuring Entity shall issue the Notice to Proceed to the winning Bidder not later than three (3) calendar days from the date of approval of the contract by the appropriate signatories. All notices called for by the terms of the contract shall be effective only at the time of receipt thereof by the successful Bidder." + }, + { + "type": "title", + "text": "32) Protest Mechanism" + }, + { + "type": "text", + "text": "Decisions of the BAC in all stages of procurement may be protested to the HoPE in accordance with Section 83 of the IRR." + }, + { + "type": "page_number", + "text": "43" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_04.json b/diagrams-and-tables/annotations/en_simple_table_04.json new file mode 100644 index 0000000000000000000000000000000000000000..5b2e6d1246363f2ab8196af8b7f9ca692e1cabe5 --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_04.json @@ -0,0 +1,26 @@ +[ + { + "type": "text", + "text": "e) Users - In cases where Structural Defects or Failures are due to abuse or misuse by the End-User or Implementing Unit of the constructed facility and/or non-compliance by a user with the technical design limits and/or intended purpose of the same, then the user concerned shall be held liable." + }, + { + "type": "text", + "text": "15.5 The warranty against Structural Defects or Failures, except those occasioned by force majeure, shall cover the period specified in the SCC reckoned from the date of issuance of the Certificate of Final Acceptance by the Procuring Entity. On the other hand, such warranty shall likewise be applied against non-structural defects for instances that pertain to faults or deficiencies in non-load bearing components or finishes of the Project, such as minor cracks, leaks, or defects in workmanship or materials, which do not affect the stability or safety of the structure but may impact its appearance, functionality, or usability." + }, + { + "type": "text", + "text": "15.6 To guarantee that the Contractor shall perform its responsibilities, it shall be required to post a warranty security, which shall be stated in Philippine Peso, in the form chosen by the Procuring Entity in accordance with the following schedule:" + }, + { + "type": "table", + "html": "
Form of WarrantyAmount of Warranty Security Not less than the Percentage (%) of Total Contract Price
(a) Cash or letter of credit issued by bank; Provided, however, that the letter of credit shall be confirmed or authenticated by a local bank, if issued by a foreign bank.
For biddings conducted by LGUs, the Letter of Credit may be issued by other banks certified by the BSP as authorized to issue such financial instrument.		Five Percent (5%)
(b) Bank guarantee confirmed by bank.
For biddings conducted by LGUs, the bank draft/guarantee may be issued by other banks certified by the BSP as authorized to issue such financial instrument.		Ten Percent (10%)
(c) Surety bond callable upon demand issued by GSIS or any surety or insurance company duly certified by the Insurance CommissionThirty Percent (30%)
" + }, + { + "type": "text", + "text": "15.7 The warranty security shall be stated in Philippine Peso and shall remain effective within one (1) year from the date of issuance of the Certificate of Final Acceptance by the Procuring Entity, and returned only after the lapse of the said one (1) year period. This one (1) year period shall cover both structural and non-structural defects or failures; Provided, That in cases of structural defects or failures, warranties beyond the one (1) year period shall be subject to applicable laws, rules, and regulations such as the New Civil Code of the Philippines." + }, + { + "type": "page_number", + "text": "64" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_05.json b/diagrams-and-tables/annotations/en_simple_table_05.json new file mode 100644 index 0000000000000000000000000000000000000000..68efef5d58b1f76ffd7090e7aff102fe931149eb --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_05.json @@ -0,0 +1,18 @@ +[ + { + "type": "title", + "text": "Section 1. Instructions to Tenderers" + }, + { + "type": "table", + "html": "
A. General
1. Scope of Tender1.1 The Procuring Entity, as indicated in the Tender Data Sheet (TDS) issues this Tender Document for the supply of Goods, and related services incidental thereto, as specified in the TDS and as detailed in Section 6: Schedule of Requirements.
2. Corrupt, Fraudulent, Collusive or Coercive Practices2.1 The Government requires that the Procuring Entity as well as the Tenderers shall, observe the highest standard of ethics during implementation of the Procurement proceedings and the execution of Contracts under public funds.
2.2 If corrupt, fraudulent, collusive or coercive practices of any kind determined by the Procuring Entity against any Tenderer or Supplier in competing for, or in executing, a contract under public fund, Procuring Entity shall -
(a) exclude the concerned Tenderer from further participation in the particular Procurement proceeding; or
(b) reject any recommendation for award that had been proposed for that concerned Tenderer or;
(c) declare, at its discretion, the concerned Tenderer to be ineligible to participate in further Procurement proceedings, either indefinitely or for a specific period of time.
3. Eligible Tenderers3.1 This Invitation for Tenders is open/limited to Tenderers as specified in the TDS.
3.2 Tenderers shall have the legal capacity to enter into the Contract under the Applicable Law.
3.3 Tenderers shall be enrolled in the relevant professional or trade organisations registered in Bangladesh.
3.4 Tenderers shall have fulfilled its obligations to pay taxes under the provisions of laws and regulations of Bangladesh.
3.5 Tenderers and all parties constituting the Tenderer shall not have a conflict of interest.
3.6 Tenderers in its own name or its other names or also in the case of its Persons in different names, shall not be under a declaration of ineligibility for corrupt, fraudulent, collusive or coercive practices as stated under ITT Clause 2.
" + }, + { + "type": "footer", + "text": "Procurement of Microsoft Exchange and Office Hybrid Email Solution" + }, + { + "type": "page_number", + "text": "1" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_06.json b/diagrams-and-tables/annotations/en_simple_table_06.json new file mode 100644 index 0000000000000000000000000000000000000000..5027e8e5130261b9e1d9dd4471d94ff6b73fb1dc --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_06.json @@ -0,0 +1,14 @@ +[ + { + "type": "table", + "html": "
7.3 To qualify for multiple number of contracts/lots in a package made up of this and other individual contracts/lots for which Tenders are invited in the Invitation for Tenders, the Tenderer shall demonstrate having resources sufficient to meet the aggregate of the qualifying criteria for the individual contracts except for general experience as stated under ITT Sub Clause 8.1(a) and specific experience, unless otherwise of different nature, as stated under ITT Sub Clause 8.1(b).
8. Experience Criteria8.1 Tenderers shall have the following minimum level of supply experience to qualify for supplying the Goods and related Services under the contract:
(a) a minimum number of years of general experience in the supply of Goods and related services as specified in the TDS;
(b) specific experience of satisfactory completion of supply of Goods similar to the proposed goods in at least one contract with a minimum value, over the period, as specified in TDS.
9. Financial Criteria9.1 Tenderers shall have the availability of minimum liquid assets, net of other contractual commitments, of the amount as specified in the TDS.
10. Subcontractor(s)10.1 The successful Tenderer shall under no circumstances assign the supply of Goods or any part of it to the Subcontractor(s).
D. Tender Preparation
11. Only One Tender11.1 Tender being invited for one or more items on an\"item-by-item\" basis, each such item shall constitute a Tender. Tenderers shall submit only one (1) Tender for one or more items of each lot or single lot of a package. Tenderer who submits more than one (1) Tender in one or more item (s) of one (1) lot will cause all the Tenders of that particular Tenderer to be rejected.
11.2 Tender being invited for a single lot/package, the single lot/package shall constitute a Tender. Tenderers shall submit only one (1) Tender for the lot/package. Tenderer who submits more than one (1) Tender in the lot/package will cause all the Tenders of that particular Tenderer to be rejected.
11.3 Tender being invited for a number of lots on a \"lot-by-lot\" basis, each such lot shall constitute a Tender. Tenderers shall submit only one (1) Tender for each lot. Tenderer who submits more than one (1) Tender in one (1) lot of the package will cause all the Tenders of that particular Tenderer to be rejected.
12. Issuance, Sale and Language of Tender Document12.1 The Procuring Entity shall make Tender Documents available immediately to the potential Tenderers without any pre-
" + }, + { + "type": "footer", + "text": "Procurement of Microsoft Exchange and Office Hybrid Email Solution" + }, + { + "type": "page_number", + "text": "3" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_07.json b/diagrams-and-tables/annotations/en_simple_table_07.json new file mode 100644 index 0000000000000000000000000000000000000000..9400a62983355daa29b5016b8f520b69ebcf32e0 --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_07.json @@ -0,0 +1,14 @@ +[ + { + "type": "table", + "html": "
14.2 If in preparing its Tender, the Tenderer has made errors in the unit rate or the total price, and wishes to correct such errors prior to submission of its Tender, it may do so, but shall ensure that each correction is initialled by the Tenderer.
15. Tender Prices15.1 Tenderers shall fill in unit rates for the items of the Goods both in figures and in words as described in the Price Schedule.
15.2 All items or lots in Section 6: Schedule of Requirements must be listed and priced separately on the Price Schedule following the Form PG2-2.
15.3 Tenders being invited either for one or more items on an 'item-by-item' basis or for a single lot/package or. for a number of lots on 'lot-by-lot' basis, as specified in the TDS, the price quoted for an item shall correspond to full quantity under that particular item; otherwise the Tenders shall be considered non-responsive.
15.4 Tenders being invited for a single lot/package, price quoted shall correspond to all the items of the lot/package and, shall further correspond to full quantity under each item of the lot/package as stated under ITT Sub Clause 15.3; otherwise the Tenders shall be considered non-responsive.
15.5 Tenders being invited for a number of lots on \"lot-by-lot\" basis, the lot not quoting at least eighty (80) percent of the total number of items under that lot, determined in the methodology as stated under ITT Sub Clause 15.6, shall be considered non-responsive.
15.6 Tenderers quoting in the least eighty (80) percent of the total number of items in a lot, taking into consideration the fractions after the decimal to the nearer digit, for Tenders invited on \"lot-by-lot\" basis, the methodology for determining the equivalent lot value as stated under ITT Sub Clause 15.5, shall be to simulate the total price of the lot by adding up the average of the prices quoted by the other responsive Tenderers for the missing items to that lot value, to establish its responsiveness and, will be used for price comparison, as stated under ITT Sub Clause 31.1.
15.7 All applicable taxes, custom duties, VAT and other levies payable by the Contractor under the Contract shall be included in the unit rates and the Total price submitted by the Tenderers.
16. Tender Currency16.1 Tenderers shall quote all prices in the Tender Submission Letter and in the Price Schedule in Bangladesh Taka (BDT) currency.
" + }, + { + "type": "footer", + "text": "Procurement of Microsoft Exchange and Office Hybrid Email Solution" + }, + { + "type": "page_number", + "text": "5" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_08.json b/diagrams-and-tables/annotations/en_simple_table_08.json new file mode 100644 index 0000000000000000000000000000000000000000..29bffeb2e1ed1fff3c204856d9e9abf256413c40 --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_08.json @@ -0,0 +1,14 @@ +[ + { + "type": "table", + "html": "
20.2 The Tender Security shall be at the Tenderer's option, be either in the form of Bank Draft or Pay Order or irrevocable unconditional Bank Guarantee issued by any scheduled Bank of Bangladesh, in the format (Form PG2-4), without any alteration, furnished in Section 5: Tender and Contract Forms; remaining valid for at least twenty eight (28) days beyond the expiry date of the Tender Validity.
20.3 The authenticity of the Tender Security submitted by a Tenderer may be examined and verified by the Procuring Entity at its discretion in writing from the Bank issuing the security. A Tender not accompanied by a valid Tender Security shall be considered as non-responsive.
20.4 No Tender Security shall be returned to the Tenderers before contract signing.
20.5 The Tender Security may be forfeited if a Tenderer:
(a) modifies, substitutes or withdraws its Tender after submission as stated under ITT Sub Clause 23.1;
(b) refuses to accept a Notification of Award, as stated under ITT Sub Clause 36 ; or
(c) fails to furnish Performance Security, as stated under ITT Sub Clause 37 ; or
(d) refuses to sign the Contract, as stated under ITT Sub Clause 38 ;
(e) does not accept the correction of the Tender price following the correction of arithmetic errors, as stated under ITT SubClause 29.
20.6 In the event, this Tender is invited under LTM; the ITT Clause 20 shall not be applicable, as indicated in the TDS.
E. Tender Submission
21. Sealing & Marking of Tender21.1 Tenderers shall prepare one (1) original of the documents comprising the Tender as described in ITT Clause 4 and clearly mark it \"ORIGINAL\" with all particulars of the Procuring Entity, the Tenderer and the Tender.
22. Deadline for Submission of Tenders22.1 Tenders shall be delivered to the Procuring Entity at the address specified in the TDS and not later than the date and time specified in the TDS. Any Tender received by the Procuring Entity after the deadline for submission of Tenders shall be declared LATE and returned unopened to the Tenderer.
23. Modification, Substitution or Withdrawal of Tender23.1 Tenderers may not modify, substitute or withdraw its Tender after it has been submitted. Tenders modified, substituted or withdrawn shall be rejected.
" + }, + { + "type": "footer", + "text": "Procurement of Microsoft Exchange and Office Hybrid Email Solution" + }, + { + "type": "page_number", + "text": "7" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_09.json b/diagrams-and-tables/annotations/en_simple_table_09.json new file mode 100644 index 0000000000000000000000000000000000000000..a4e540ced2a978fe88c60c6771d14fe9195808d1 --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_09.json @@ -0,0 +1,14 @@ +[ + { + "type": "table", + "html": "
any liability to Tenderers, or any obligations to inform the Tenderers of the grounds for the Procuring Entity's action.
G. Contract Award
35. Award Criteria35.1 The Procuring Entity shall award the Contract to the Tenderer whose Tender is responsive to all the requirements of the Tender Document and that has been determined to be the successful lowest evaluated Tender, provided further that the Tenderer is determined to be Post-qualified as stated under ITT Clause 33.
36. Notification of Award36.1 Prior to the expiry of the Tender Validity period and within one (1) week of receipt of the approval of the award by the Approving Authority, the Procuring Entity shall issue the Notification of Award (NOA) to the successful Tenderer.
36.2 The NOA, attaching the contract as per the sample (Form PG2-6 to be signed, shall state:
(a) the acceptance of the Tender by the Procuring Entity;
(b) the price at which the contract is awarded;
(c) the amount of the Performance Security and its format;
(d) the date and time within which the Performance Security shall be furnished; and
(e) the date and time within which the contract shall be signed.
36.3 The NOA shall be accepted in writing by the successful Tenderer within seven (7) working days from the date of its issuance.
36.4 In the event, this Tender is invited for one (1) or more items on an \"item-by-item\" basis, contract(s) will comprise the corresponding item(s) awarded to the successful Tenderer(s) and, Contract(s) will be signed per each of the successful Tenderer(s),covering the corresponding item(s).
36.5 In the event, this Tender is invited for a single lot, contract will comprise the corresponding items in the lot awarded to the successful Tenderer and, Contract will be signed with the successful Tenderer of the lot, covering the item(s).
36.6 In the event, this Tender is invited for a number of lots on a \"lot-by-lot\" basis, contracts will comprise the corresponding items in a lot awarded to the successful Tenderer(s) and, Contract(s) will be signed per each of the successful Tenderer(s) per lot, covering the corresponding item(s).
" + }, + { + "type": "footer", + "text": "Procurement of Microsoft Exchange and Office Hybrid Email Solution" + }, + { + "type": "page_number", + "text": "11" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_10.json b/diagrams-and-tables/annotations/en_simple_table_10.json new file mode 100644 index 0000000000000000000000000000000000000000..d82d6bc39184cec3fa2cc8fc3f490f3951a79ff4 --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_10.json @@ -0,0 +1,34 @@ +[ + { + "type": "header", + "text": "The University of Akron\nNotes to the Financial Statements\nJune 30, 2018 and 2017" + }, + { + "type": "title", + "text": "6. Long-term Liabilities - continued" + }, + { + "type": "text", + "text": "The University has defeased certain debt by placing the proceeds of new bonds in an irrevocable trust to provide for all future debt service payments on the old debt. Accordingly, the trust account assets and the liabilities for the defeased debt are not included in The University's financial statements. The defeased debt is as follows:" + }, + { + "type": "table", + "html": "
Amount
Defeased		Amount
Outstanding at
June 30, 2018		Amount
Outstanding at
June 30, 2017
General Receipts Rental Note:
Series 2003A$ 33,412,270$ 22,171,926$ 23,242,435
General Receipts Bonds:
Refunded in 2015
Series 2008A48,765,000-48,765,000
Series 2008B51,370,000-51,370,000
Remainder Refunded in 2016
Series 2008A28,320,000-25,770,000
Series 2008B51,825,000-49,715,000
Lease Revenue Bonds:
Series 201118,555,00017,275,00017,925,000
Totals$ 232,247,270$ 39,446,926$ 216,787,435
" + }, + { + "type": "text", + "text": "The aggregate annual principal maturities for the debt agreements for fiscal years subsequent to June 30, 2018 are as follows:" + }, + { + "type": "table", + "html": "
Fiscal Year:PrincipalInterestTotal
2019$ 21,334,623$ 16,670,381$ 38,005,004
202022,018,09715,882,36537,900,462
202122,768,76515,113,21037,881,975
202223,396,68114,314,46137,711,142
202323,156,90113,410,67036,567,571
2024-2028120,305,21152,329,976172,635,187
2029-2033100,940,24826,148,081127,088,329
2034-203867,312,1469,336,90676,649,052
2039-204211,182,090555,31311,737,403
Totals$ 412,414,762$ 163,761,363$ 576,176,125
" + }, + { + "type": "text", + "text": "In September 2013, The University finalized an agreement with Akron Public Schools (APS) to transfer a decommissioned high school to The University in return for the equivalent in-kind services to the district in accordance with state law. The fair market value of the high school, known as Central Hower High School, was determined to be $13.5 million. The University agreed to fund annual, renewable APS Innovation Generation Scholarships to qualified current and future APS students up to the fair market value of Central Hower. The remaining scholarship balance as of June 30, 2018 and 2017 was $10,982,508 and $11,550,303, respectively." + }, + { + "type": "page_number", + "text": "31" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_11.json b/diagrams-and-tables/annotations/en_simple_table_11.json new file mode 100644 index 0000000000000000000000000000000000000000..f996a0fcf6a45fa34dab61f83b3ef76e4a6a5f7f --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_11.json @@ -0,0 +1,46 @@ +[ + { + "type": "header", + "text": "The University of Akron\nNotes to the Financial Statements\nJune 30, 2018 and 2017" + }, + { + "type": "title", + "text": "8. Employee Benefit Plans - continued" + }, + { + "type": "title", + "text": "Contributions" + }, + { + "type": "text", + "text": "State retirement law requires contributions by covered employees and their employers, and Chapter 3307 of the Ohio Revised Code (ORC) limits the maximum rate of contributions. The retirement boards of the systems individually set contribution rates within the allowable limits. The adequacy of employer contribution rates is determined annually by actuarial valuation using the entry age normal cost method. Under these provisions, each University's contribution is expected to finance the costs of benefits earned by employees during the year, with an additional amount to finance a portion of the unfunded accrued liability." + }, + { + "type": "text", + "text": "Member contributions are set at the maximums authorized by the ORC. The plans' 2018 employer and member contribution rates on covered payroll to each system are:" + }, + { + "type": "table", + "html": "
Employer Contribution RateMember Contribution Rate
PensionPost
Retirement
Healthcare		Death
Benefits		TotalTotal
STRS14.00%0.00%0.00%14.00%14.00%
SERS13.20%0.75%0.05%14.00%10.00%
OPERS - State/Local (through 12/31/17)13.00%1.00%0.00%14.00%10.00%
OPERS - State/Local (beginning 1/1/18)14.00%0.00%0.00%14.00%10.00%
OPERS - Law Enforcement (through 12/31/17)17.10%1.00%0.00%18.10%13.00%
OPERS - Law Enforcement (beginning 1/1/18)18.10%0.00%0.00%18.10%13.00%
" + }, + { + "type": "text", + "text": "The plans' 2017 employer and member contribution rates on covered payroll to each system are:" + }, + { + "type": "table", + "html": "
Employer Contribution RateMember Contribution Rate
PensionPost
Retirement
Healthcare		Death
Benefits		TotalTotal
STRS (beginning 7/1/16)14.00%0.00%0.00%14.00%14.00%
SERS13.21%0.74%0.05%14.00%10.00%
OPERS - State/Local (through 12/31/16)12.00%2.00%0.00%14.00%10.00%
OPERS - State/Local (beginning 1/1/17)13.00%1.00%0.00%14.00%10.00%
OPERS - Law Enforcement (through 12/31/16)16.10%2.00%0.00%18.10%13.00%
OPERS - Law Enforcement (beginning 1/1/17)17.10%1.00%0.00%18.10%13.00%
" + }, + { + "type": "text", + "text": "The University's required and actual contributions to the plans are:" + }, + { + "type": "table", + "html": "
For the years ended June 30
20182017
PensionOPEBPensionOPEB
STRS$ 10,288,321$ -$ 11,264,364$ -
SERS5,305,417573,8106,535,649375,817
OPERS1,599,21940,101634,63356,166
UA Plan-2,205,549-2,673,154
$ 17,192,957$ 2,819,460$ 18,434,646$ 3,105,137
" + }, + { + "type": "page_number", + "text": "34" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_12.json b/diagrams-and-tables/annotations/en_simple_table_12.json new file mode 100644 index 0000000000000000000000000000000000000000..1eb56e3d67e1b52bf842f7ab7e5e931f23a5aab3 --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_12.json @@ -0,0 +1,46 @@ +[ + { + "type": "header", + "text": "CDL HOSPITALITY TRUSTS" + }, + { + "type": "title", + "text": "NOTES TO THE FINANCIAL STATEMENTS" + }, + { + "type": "title", + "text": "10 LOANS AND BORROWINGS (CONT'D)" + }, + { + "type": "text", + "text": "OVERVIEW AND FINANCIAL REVIEW" + }, + { + "type": "text", + "text": "MARKET REVIEW" + }, + { + "type": "text", + "text": "LEADERSHIP STRUCTURE" + }, + { + "type": "text", + "text": "PROPERTY PORTFOLIO" + }, + { + "type": "text", + "text": "REPORTS" + }, + { + "type": "title", + "text": "Reconciliation of movements of liabilities to cash flows arising from financing activities" + }, + { + "type": "table", + "html": "
HBT GroupH-REIT GroupStapled Group
Loans and
borrowings
$'000		Lease
liabilities
$'000		Other
payables
$'000		Loans and
borrowings
$'000		Lease
liabilities
$'000		Other
payables
$'000		Loans and
borrowings
$'000		Lease
liabilities
$'000		Other
payables
$'000
Balance at 1 January 201993,418–198917,950–1,6671,011,368–1,865
Recognition of lease
liabilities on initial
application of
FRS 116 / SFRS(I) 16		–52,046––26,496––35,160–
Adjusted balance at
1 January 2019		93,41852,046198917,95026,4961,6671,011,36835,1601,865
Changes from
financing cash flows
Proceeds from bank loans–––322,957––322,957––
Repayment of bank loans–––(264,340)––(264,340)––
Payment of transaction costs
related to borrowings		–––(2,304)––(2,304)––
Payment of lease liabilities–(2,020)––(1,022)––(1,064)–
Finance costs paid–(2,650)(2,592)–(1,285)(17,327)–(1,816)(19,919)
Total changes from
financing cash flows		–(4,670)(2,592)56,313(2,307)(17,327)56,313(2,880)(19,919)
Effect of changes in
foreign exchange rates		983(344)–(6,200)(229)(3,566)(5,217)(85)(3,566)
Other changes
Liability-related
Remeasurement of lease
liabilities		–5,749–––––5,749–
Amortisation of
transaction costs		153––1,310––1,463––
Interest expense–2,6502,594–1,28520,608–1,81623,202
Total liability-related
other changes		1538,3992,5941,3101,28520,6081,4637,56523,202
Balance as at
31 December 2019		94,55455,431200969,37325,2451,3821,063,92739,7601,582
" + }, + { + "type": "page_number", + "text": "199" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_13.json b/diagrams-and-tables/annotations/en_simple_table_13.json new file mode 100644 index 0000000000000000000000000000000000000000..a60aa3eaa48bcde2f42f1fd41854bbacce663c3a --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_13.json @@ -0,0 +1,58 @@ +[ + { + "type": "title", + "text": "Segment Operating Performance" + }, + { + "type": "text", + "text": "The following table shows net sales by reportable segment for 2023, 2022 and 2021 (dollars in millions):" + }, + { + "type": "table", + "html": "
2023Change2022Change2021
Net sales by reportable segment:
Americas$ 162,560(4)%$ 169,65811 %$ 153,306
Europe94,294(1)%95,1187 %89,307
Greater China72,559(2)%74,2009 %68,366
Japan24,257(7)%25,977(9)%28,482
Rest of Asia Pacific29,6151 %29,37511 %26,356
Total net sales$ 383,285(3)%$ 394,3288 %$ 365,817
" + }, + { + "type": "title", + "text": "Americas" + }, + { + "type": "text", + "text": "Americas net sales decreased 4% or $7.1 billion during 2023 compared to 2022 due to lower net sales of iPhone and Mac, partially offset by higher net sales of Services." + }, + { + "type": "title", + "text": "Europe" + }, + { + "type": "text", + "text": "Europe net sales decreased 1% or $824 million during 2023 compared to 2022. The weakness in foreign currencies relative to the U.S. dollar accounted for more than the entire year-over-year decrease in Europe net sales, which consisted primarily of lower net sales of Mac and Wearables, Home and Accessories, partially offset by higher net sales of iPhone and Services." + }, + { + "type": "title", + "text": "Greater China" + }, + { + "type": "text", + "text": "Greater China net sales decreased 2% or $1.6 billion during 2023 compared to 2022. The weakness in the renminbi relative to the U.S. dollar accounted for more than the entire year-over-year decrease in Greater China net sales, which consisted primarily of lower net sales of Mac and iPhone." + }, + { + "type": "title", + "text": "Japan" + }, + { + "type": "text", + "text": "Japan net sales decreased 7% or $1.7 billion during 2023 compared to 2022. The weakness in the yen relative to the U.S. dollar accounted for more than the entire year-over-year decrease in Japan net sales, which consisted primarily of lower net sales of iPhone, Wearables, Home and Accessories and Mac." + }, + { + "type": "title", + "text": "Rest of Asia Pacific" + }, + { + "type": "text", + "text": "Rest of Asia Pacific net sales increased 1% or $240 million during 2023 compared to 2022. The weakness in foreign currencies relative to the U.S. dollar had a significantly unfavorable year-over-year impact on Rest of Asia Pacific net sales. The net sales increase consisted of higher net sales of iPhone and Services, partially offset by lower net sales of Mac and iPad." + }, + { + "type": "footer", + "text": "Apple Inc. | 2023 Form 10-K | 21" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_14.json b/diagrams-and-tables/annotations/en_simple_table_14.json new file mode 100644 index 0000000000000000000000000000000000000000..0f64ed37211a2eeb6ba475b7be220e22ee9468f7 --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_14.json @@ -0,0 +1,62 @@ +[ + { + "type": "header", + "text": "Intel® 600 Series Chipset Family for IoT Edge PCH—8254 Timers" + }, + { + "type": "text", + "text": "If a counter is programmed to read/write 2-byte counts, the following precaution applies - a program must not transfer control between writing the first and second Byte to another routine, which also writes into that same counter. Otherwise, the counter will be loaded with an incorrect count." + }, + { + "type": "text", + "text": "The Control Word Register at port 43h controls the operation of all three counters. Several commands are available:" + }, + { + "type": "text", + "text": "• Control Word Command. Specifies which counter to read or write, the operating mode, and the count format (binary or BCD).\n• Counter Latch Command. Latches the current count so that it can be read by the system. The countdown process continues.\n• Read Back Command. Reads the count value, programmed mode, the current state of the OUT pins, and the state of the Null Count Flag of the selected counter." + }, + { + "type": "text", + "text": "The table below lists the six operating modes for the interval counters:" + }, + { + "type": "title", + "text": "Table 16. Counter Operating Modes" + }, + { + "type": "table", + "html": "
ModeFunctionDescription
0Out signal on end of count (=0)Output is 0. When count goes to 0, output goes to 1 and stays at 1 until counter is reprogrammed.
1Hardware retriggerable one-shotOutput is 0. When count goes to 0, output goes to 1 for one clock time.
2Rate generator (divide by n counter)Output is 1. Output goes to 0 for one clock time, then back to 1 and counter is reloaded.
3Square wave outputOutput is 1. Output goes to 0 when counter rolls over, and counter is reloaded. Output goes to 1 when counter rolls over, and counter is reloaded, and so on
4Software triggered strobeOutput is 1. Output goes to 0 when count expires for one clock time.
5Hardware triggered strobeOutput is 1. Output goes to 0 when count expires for one clock time.
" + }, + { + "type": "title", + "text": "10.2 Reading from the Interval Timer" + }, + { + "type": "text", + "text": "It is often desirable to read the value of a counter without disturbing the count in progress. There are three methods for reading the counters—a simple read operation, counter Latch command, and the Read-Back command. Each one is explained below:" + }, + { + "type": "text", + "text": "With the simple read and counter latch command methods, the count must be read according to the programmed format; specifically, if the counter is programmed for 2-byte counts, 2-bytes must be read. The 2-bytes do not have to be read one right after the other. Read, write, or programming operations for other counters may be inserted between them." + }, + { + "type": "title", + "text": "Simple Read" + }, + { + "type": "text", + "text": "The first method is to perform a simple read operation. The counter is selected through Port 40h (Counter 0) or 42h (Counter 2)." + }, + { + "type": "footer", + "text": "Intel® 600 Series Chipset Family for IoT Edge Platform Controller Hub (PCH)\nDatasheet, Volume 1 of 2" + }, + { + "type": "page_number", + "text": "46" + }, + { + "type": "footer", + "text": "September 2022\nDoc. No.: 743330, Rev.: 001" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_15.json b/diagrams-and-tables/annotations/en_simple_table_15.json new file mode 100644 index 0000000000000000000000000000000000000000..2ecd1b5809a5f976c393f3dbd4b08f9ae44ed5df --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_15.json @@ -0,0 +1,22 @@ +[ + { + "type": "header", + "text": "Intel® 600 Series Chipset Family for IoT Edge PCH—Audio Voice and Speech" + }, + { + "type": "table", + "html": "
Signal NameTypeDescription
I$^{2}$S/PCM Interface
GPP_R0 / HDA_BCLK /
I2S0_SCLK / DMIC_CLKB0 /
HDA_PROC_BCLK		I/OI$^{2}$S/PCM serial bit clock 0:Clock used to control the
timing of a transfer. Can be generated internally (Main
mode) or taken from an external source (Subordinate
mode).
GPP_S0 / SNDW0_CLK /
I2S1_SCLK		I/OI$^{2}$S/PCM serial bit clock 1:This clock is used to
control the timing of a transfer. Can be generated
internally (Main mode) or taken from an external
source (Subordinate mode).
GPP_R4 / HDA_RST# /
I2S2_SCLK / DMIC_CLK_A0		I/OI$^{2}$S/PCM serial bit clock 2:This clock is used to
control the timing of a transfer. Can be generated
internally (Main mode) or taken from an external
source (Subordinate mode).
GPP_R1 / HDA_SYNC /
I2S0_SFRM / DMIC_CLKB1		I/OI$^{2}$S/PCM serial frame indicator 0: This signal
indicates the beginning and the end of a serialized data
word. Can be generated internally (Main mode) or
taken from an external source (Subordinate mode).
GPP_S1 / SNDW0_DATA /
I2S1_SFRM		I/OI$^{2}$S/PCM serial frame indicator 1: This signal
indicates the beginning and the end of a serialized data
word. Can be generated internally (Main mode) or
taken from an external source (Subordinate mode).
GPP_R5 / HDA_SDI1 /
I2S2_SFRM / DMIC_DATA0		I/OI$^{2}$S/PCM serial frame indicator 2: This signal
indicates the beginning and the end of a serialized data
word. Can be generated internally (Main mode) or
taken from an external source (Subordinate mode).
GPP_R2 / HDA_SDO /
I2S0_TXD / HDA_PROC_SDO		OI$^{2}$S/PCM transmit data (serial data out)0: This
signal transmits serialized data. The sample length is a
function of the selected serial data sample size.
GPP_S2 / SNDW1_CLK /
DMIC_CLKA0 / I2S1_TXD		OI$^{2}$S/PCM transmit data (serial data out)1: This
signal transmits serialized data. The sample length is a
function of the selected serial data sample size.
GPP_R6 / I2S2_TXD /
DMIC_CLKA1		OI$^{2}$S/PCM transmit data (serial data out)2: This
signal transmits serialized data. The sample length is a
function of the selected serial data sample size.
GPP_R3 / HDA_SDI0 /
I2S0_RXD / HDA_PROC_SDI		II$^{2}$S/PCM receive data (serial data in)0: This signal
receives serialized data. The sample length is a
function of the selected serial data sample size.
GPP_S3 / SNDW1_DATA /
DMIC_DATA0 / I2S1_RXD		II$^{2}$S/PCM receive data (serial data in)1: This signal
receives serialized data. The sample length is a
function of the selected serial data sample size.
GPP_R7 / I2S2_RXD /
DMIC_DATA1		II$^{2}$S/PCM receive data (serial data in)2: This signal
receives serialized data. The sample length is a
function of the selected serial data sample size.
GPP_D19 / I2S_MCLK1_OUTOI$^{2}$S/PCM Main reference clock 1: This signal is the
main reference clock that connects to an audio codec.
DMIC Interface
GPP_S2 / SNDW1_CLK /
DMIC_CLKA0 / I2S1_TXD
or
GPP_R4 / HDA_RST# /
I2S2_SCLK / DMIC_CLK_A0		ODigital Mic Clock A0:Serial data clock generated by
the HD Audio controller. The clock output frequency is
up to 4.8 MHz. May be duplicated into CLKA and CLKB
for individual left / right DMIC power control.
continued...
" + }, + { + "type": "footer", + "text": "Intel® 600 Series Chipset Family for IoT Edge Platform Controller Hub (PCH)\nDatasheet, Volume 1 of 2" + }, + { + "type": "page_number", + "text": "54" + }, + { + "type": "footer", + "text": "September 2022\nDoc. No.: 743330, Rev.: 001" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_16.json b/diagrams-and-tables/annotations/en_simple_table_16.json new file mode 100644 index 0000000000000000000000000000000000000000..e05f5fa3e0654e598932f6c6aa934381f4aa35f5 --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_16.json @@ -0,0 +1,42 @@ +[ + { + "type": "header", + "text": "Intel® 600 Series Chipset Family for IoT Edge PCH—Audio Voice and Speech" + }, + { + "type": "title", + "text": "11.3 Integrated Pull-Ups and Pull-Downs" + }, + { + "type": "title", + "text": "Table 19. Integrated Pull-Ups and Pull-Downs" + }, + { + "type": "table", + "html": "
Signal NameResistor TypeValue (Ω)
HDA_SYNCPull-down20 kohm
HDA_SDOPull-down20 kohm
HDA_SDI[1:0]Pull-down20 kohm
HDA_PROC_SDOPull-down20 kohm
HDA_PROC_SDIPull-down20 kohm
I2S[2:0]_SCLKPull-down20 kohm
I2S[2:0]_SFRMPull-down20 kohm
I2S[2:0]_TXDPull-down20 kohm
I2S[2:0]_RXDPull-down20 kohm
I2S_MCLK1_OUTPull-down20 kohm
DMIC_DATA[1:0]Pull-down20 kohm
SNDW[3:0]_DATAPull-down5 kohm
SPKRPull-down20 kohm
" + }, + { + "type": "title", + "text": "11.4 I/O Signal Planes and States" + }, + { + "type": "title", + "text": "Table 20. I/O Signal Planes and States" + }, + { + "type": "table", + "html": "
Signal NamePower PlaneDuring Reset$^{2}$Immediately After Reset$^{2}$S4/S5Deep Sx
High Definition Audio Interface
HDA_RST#PrimaryDriven LowDriven LowDriven LowOFF
HDA_SYNCPrimaryInternal Pull-downDriven LowInternal Pull-downOFF
HDA_BCLKPrimaryDriven LowDriven LowDriven LowOFF
HDA_SDOPrimaryInternal Pull-downDriven LowInternal Pull-downOFF
HDA_SDI[1:0]PrimaryInternal Pull-downInternal Pull-downInternal Pull-downOFF
I$^{2}$S/PCM Interface
I2S[2:0]_SCLKPrimaryInternal Pull-downInternal Pull-downInternal Pull-downOFF
I2S[2:0]_SFRMPrimaryInternal Pull-downInternal Pull-downInternal Pull-downOFF
I2S[2:0]_TXDPrimaryDriven LowDriven LowDriven LowOFF
I2S[2:0]_RXDPrimaryInternal Pull-downInternal Pull-downInternal Pull-downOFF
I2S_MCLK1_OUTPrimaryInternal Pull-downInternal Pull-downInternal Pull-downOFF
DMIC Interface
DMIC_CLKA[1:0]PrimaryDriven LowDriven LowDriven LowOFF
DMIC_CLKB[1:0]PrimaryDriven LowDriven LowDriven LowOFF
DMIC_DATA[1:0]PrimaryInternal Pull-downInternal Pull-downInternal Pull-downOFF
continued...
" + }, + { + "type": "footer", + "text": "Intel® 600 Series Chipset Family for IoT Edge Platform Controller Hub (PCH)\nDatasheet, Volume 1 of 2" + }, + { + "type": "page_number", + "text": "56" + }, + { + "type": "footer", + "text": "September 2022\nDoc. No.: 743330, Rev.: 001" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_17.json b/diagrams-and-tables/annotations/en_simple_table_17.json new file mode 100644 index 0000000000000000000000000000000000000000..9f3a7f1cebae979750d372afecb2c222c80f2983 --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_17.json @@ -0,0 +1,54 @@ +[ + { + "type": "header", + "text": "Intel® 600 Series Chipset Family for IoT Edge PCH—Controller Link" + }, + { + "type": "title", + "text": "12.0 Controller Link" + }, + { + "type": "text", + "text": "The controller link is used to manage the wireless devices supporting Intel® CSME Technology. Controller Link will transmit data at 60.0 Mbps on Controller Link Port. The Controller Link clock frequency is 30.0 MHz." + }, + { + "type": "table", + "html": "
AcronymsDescription
CLController Link
WLANWireless Local Area Network
" + }, + { + "type": "title", + "text": "12.1 Signal Description" + }, + { + "type": "table", + "html": "
Signal NameTypeDescription
CL_DATAI/OController Link Data: Bi-directional data that connects to a Wireless LAN Device supporting Intel® Active Management Technology.
CL_CLKI/OController Link Clock: Bi-directional clock that connects to a Wireless LAN Device supporting Intel® Active Management Technology.
CL_RST#OController Link Reset:Controller Link reset that connects to a Wireless LAN Device supporting Intel® Active Management Technology.
" + }, + { + "type": "title", + "text": "12.2 Integrated Pull-Ups and Pull-Downs" + }, + { + "type": "table", + "html": "
Signal NameResistor TypeValue (Ohm)Notes
CL_DATAPull-up31.25I/O Signal Planes and
States on page 58
Pull-down100
CL_CLKPull-up31.25
Pull-down100
" + }, + { + "type": "title", + "text": "12.3 I/O Signal Planes and States" + }, + { + "type": "table", + "html": "
Signal NamePower PlaneDuring Reset$^{3}$Immediately After Reset$^{3}$S4/S5Deep Sx
CL_DATAPrimaryRefer to NotesRefer to NotesInternal Pull-downOFF
CL_CLKPrimaryRefer to NotesRefer to NotesInternal Pull-downOFF
CL_RST#PrimaryDriven LowDriven HighDriven HighOFF
Notes: 1. The Controller Link clock and data buffers use internal Pull-up or Pull-down resistors to drive a logical 1 or 0.
2. The terminated state is when the I/O buffer Pull-down is enabled.
3. Reset reference for primary well pins is RSMRST#.
" + }, + { + "type": "footer", + "text": "Intel® 600 Series Chipset Family for IoT Edge Platform Controller Hub (PCH)\nDatasheet, Volume 1 of 2" + }, + { + "type": "page_number", + "text": "58" + }, + { + "type": "footer", + "text": "September 2022\nDoc. No.: 743330, Rev.: 001" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_18.json b/diagrams-and-tables/annotations/en_simple_table_18.json new file mode 100644 index 0000000000000000000000000000000000000000..fbbcc67ba1b44ded98125dc70bfb0f30f4516dbc --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_18.json @@ -0,0 +1,34 @@ +[ + { + "type": "header", + "text": "Intel® 600 Series Chipset Family for IoT Edge PCH—Host System Management Bus (SMBus)\nController" + }, + { + "type": "title", + "text": "Table 74. Subordinate Read Cycle Format" + }, + { + "type": "table", + "html": "
BitDescriptionDriven ByComment
1StartExternal Micro controller
2-8Subordinate Address - 7 bitsExternal Micro controllerMust match value in Receive Subordinate
Address register
9WriteExternal Micro controllerAlways 0
10ACKPCH
11-18Command code - 8 bitsExternal Micro controllerIndicates which register is being accessed.
Refer to the Table below for a list of
implemented registers.
19ACKPCH
20Repeated StartExternal Micro controller
21-27Subordinate Address - 7 bitsExternal Micro controllerMust match value in Receive Subordinate
Address register
28ReadExternal Micro controllerAlways 1
29ACKPCH
30-37Data BytePCHValue depends on register being accessed.
Refer to the Table below for a list of
implemented registers.
38NOT ACKExternal Micro controller
39StopExternal Micro controller
" + }, + { + "type": "title", + "text": "Table 75. Data Values for Subordinate Read Registers" + }, + { + "type": "table", + "html": "
RegisterBitsDescription
07:0Reserved
12:0System Power State
000 = S0
100 = S4
101 = S5
Others = Reserved
7:3Reserved
23:0Reserved
7:4Reserved
35:0Watchdog Timer current value
Note: The Watchdog Timer has 10 bits, but this field is only 6 bits. If the current value is
greater than 3Fh, the PCH will always report 3Fh in this field.
7:6Reserved
40Intruder Detect. 1 = The Intruder Detect (INTRD_DET) bit is set. This indicates that the system
cover has probably been opened.
1Reserved
2Reserved
31 = SECOND_TO_STS bit set. This bit will be set after the second Timeout (SECOND_TO_STS
bit) of the Watchdog Timer occurs.
continued...
" + }, + { + "type": "footer", + "text": "Intel® 600 Series Chipset Family for IoT Edge Platform Controller Hub (PCH)\nDatasheet, Volume 1 of 2" + }, + { + "type": "page_number", + "text": "164" + }, + { + "type": "footer", + "text": "September 2022\nDoc. No.: 743330, Rev.: 001" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_19.json b/diagrams-and-tables/annotations/en_simple_table_19.json new file mode 100644 index 0000000000000000000000000000000000000000..3034b7fc48d6524b71c496460f6453aa598f959a --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_19.json @@ -0,0 +1,10 @@ +[ + { + "type": "header", + "text": "1 Executive Summary to the 2018 Financial Report of U.S. Government" + }, + { + "type": "table", + "html": "
NATION BY THE NUMBERS
A Snapshot of
The Government's Financial Position & Condition
20182017*
Financial Measures (Dollars in Billions):
Gross Costs$ (4,808.5)$ (4,606.2)
Less: Earned Revenue$ 392.8$ 431.9
Gain/(Loss) from Changes in Assumptions$ (125.2)$ (356.5)
Net Cost$ (4,540.9)$ (4,530.8)
Less: Total Tax and Other Revenues$ 3,384.3$ 3,374.6
Unmatched Transactions and Balances$ (2.4)$ 2.6
Net Operating Cost$ (1,159.0)$ (1,153.6)
Budget Deficit$ (779.0)$ (665.7)
Assets, comprised of:
Loans Receivable, Net$ 1,419.1$ 1,350.2
Property, Plant, and Equipment, Net$ 1,090.5$ 1,087.0
Other$ 1,327.1$ 1,097.7
Total Assets$ 3,836.7$ 3,534.9
Less: Liabilities, comprised of:
Debt Held By the Public & Accrued Interest$ (15,812.7)$ (14,724.1)
Federal Employee & Veteran Benefits$ (7,982.3)$ (7,700.1)
Other$ (1,562.5)$ (1,472.6)
Total Liabilities$ (25,357.5)$ (23,896.8)
Net Position (Assets Less Liabilities)$ (21,520.8)$ (20,361.9)
Sustainability Measures (Dollars in Trillions):
Social Insurance Net Expenditures$ (53.8)$ (49.0)
Total Federal Non-Interest Net Expenditures$ (46.2)$ (16.2)
Sustainability Measures as Percent of Gross Domestic Product (GDP):
Social Insurance Net Expenditures(4.0%)(4.0%)
Total Federal Non-Interest Net Expenditures(3.3%)(1.2%)
Fiscal Gap$^{1}$(4.1%)(2.0%)
*Restated - see Financial Statement Note 1.U
$^{1}$ To prevent the debt-to-GDP ratio from rising over the next 75 years,a combination of non-interest spending reductions and receipts increases that amounts to 4.1 percent of GDP on average is needed (2.0 percent of GDP on average in 2017). See Financial Statement Note 23.
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_20.json b/diagrams-and-tables/annotations/en_simple_table_20.json new file mode 100644 index 0000000000000000000000000000000000000000..8220b1459a82210e0e2261bc1f603ae2de4bfb27 --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_20.json @@ -0,0 +1,22 @@ +[ + { + "type": "header", + "text": "FINANCIAL STATEMENTS" + }, + { + "type": "title", + "text": "United States Government\nStatements of Social Insurance (Note 22), continued\nPresent Value of Long-Range (75 Years, except Black Lung) Actuarial Projections" + }, + { + "type": "table", + "html": "
(In trillions of dollars)20182017201620152014
Social Insurance Summary$^{11}$
Participants who have attained eligibility age:
Revenue (e.g., contributions and dedicated taxes) .....................3.63.33.12.82.3
Expenditures for scheduled future benefits ................................(27.1)(24.7)(22.9)(21.3)(19.4)
Present value of future expenditures in excess of future revenue.........................................................................(23.5)(21.4)(19.8)(18.5)(17.1)
Participants who have not attained eligibility age:
Revenue (e.g., contributions and dedicated taxes) .....................51.848.947.143.440.0
Expenditures for scheduled future benefits ................................(101.8)(95.7)(92.2)(83.1)(79.6)
Present value of future expenditures in excess of future revenue.........................................................................(50.0)(46.8)(45.1)(39.7)(39.6)
Closed-group - Total present value of future expenditures in excess of future revenue.....................................................(73.5)(68.2)(64.9)(58.2)(56.7)
Future participants:
Revenue (e.g., contributions and dedicated taxes) .....................45.143.341.936.834.3
Expenditures for scheduled future benefits ................................(25.2)(24.0)(23.7)(20.1)(19.6)
Present value of future revenue in excess of future expenditure ............................................................................19.919.318.216.814.8
Open-group - Total present value of future expenditures in excess of future revenue .............................................................(53.8)(49.0)(46.7)(41.5)(41.9)
" + }, + { + "type": "text", + "text": "$^{1}$ The projection period for Social Security and Medicare is 1/1/2018-12/31/2092 and the valuation date is 1/1/2018.\n$^{2}$ The projection period for Social Security and Medicare is 1/1/2017-12/31/2091 and the valuation date is 1/1/2017.\n$^{3}$ The projection period for Social Security and Medicare is 1/1/2016-12/31/2090 and the valuation date is 1/1/2016.\n$^{4}$ The projection period for Social Security and Medicare is 1/1/2015-12/31/2089 and the valuation date is 1/1/2015.\n$^{5}$ The projection period for Social Security and Medicare is 1/1/2014-12/31/2088 and the valuation date is 1/1/2014.\n$^{6}$ These amounts represent the present value of the future transfers from the General Fund to the SMI Trust\nFund. These future intragovernmental transfers are included as income in both HHS' and the Centers for Medicare and Medicaid Services'\nFinancial Reports but, by accounting convention, are not income from the governmentwide perspective of this report.\n$^{7}$ Includes Railroad Retirement and Black Lung.\n$^{8}$ These amounts do not include the present value of the financial interchange between the railroad retirement and social security systems,\nwhich is included as income in the Railroad Retirement Financial Report, but is not included from the governmentwide perspective of this\nreport. (See discussion of Railroad Retirement Program in the unaudited required supplementary information section of this report).\n$^{9}$ Does not include interest expense accruing on the outstanding debt of the Black Lung Disability Trust Fund.\n$^{10}$ For information on the projection periods and valuation dates for the Railroad Retirement and Black Lung programs, refer to the financial\nstatements of RRB and DOL, respectively.\n$^{11}$ Current participants for the Social Security and Medicare programs are assumed to be the \"closed-group\" of individuals who are at least\n15 years of age at the start of the projection period, and are participating as either taxpayers, beneficiaries, or both." + }, + { + "type": "text", + "text": "Totals may not equal the sum of components due to rounding.\nThe accompanying notes are an integral part of these financial statements." + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_21.json b/diagrams-and-tables/annotations/en_simple_table_21.json new file mode 100644 index 0000000000000000000000000000000000000000..65098b3d7f9d3c0ae3ced0d67c28d700dc65af4d --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_21.json @@ -0,0 +1,18 @@ +[ + { + "type": "header", + "text": "NOTES TO THE FINANCIAL STATEMENTS" + }, + { + "type": "title", + "text": "Note 3. Accounts and Taxes Receivable, Net" + }, + { + "type": "table", + "html": "
Accounts and Taxes Receivable as of September 30, 2018, and 2017
(In billions of dollars)20182017
Accounts receivable:
Gross accounts receivable .....................................................................................112.4117.9
Allowance for uncollectible amounts .....................................................................(30.5)(29.8)
Accounts receivable, net ..........................................................................................81.988.1
Taxes receivable:
Gross taxes receivable .............................................................................................226.7203.8
Allowance for uncollectible amounts .....................................................................(163.7)(148.6)
Taxes receivable, net................................................................................................63.055.2
Total accounts and taxes receivable, net ..........................................................144.9143.3
" + }, + { + "type": "text", + "text": "Gross accounts receivable include related interest receivable of $3.6 billion and $3.4 billion as of September 30, 2018, and 2017, respectively.\nTreasury comprises approximately 41.1 percent of the government's reported accounts and taxes receivable, net, as of September 30, 2018. The following list of entities comprise 98.3 percent of the government's accounts and taxes receivable, net, of $144.9 billion as of September 30, 2018. Please refer to the following entities financial statements for details on gross accounts and taxes receivable and the related allowance for uncollectible amounts:\n• Treasury\n• HHS\n• SSA\n• DOI\n• DHS\n• DOD\n• PBGC\n• DOE\n• Federal Deposit Insurance Corporation (FDIC)\n• VA\n• Tennessee Valley Authority (TVA)\n• OPM\n• DOL\n• USDA\n• USPS\n• Federal Communications Commission (FCC)\n• HUD\n• Federal Trade Commission (FTC)\n• Environmental Protection Agency (EPA)" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_22.json b/diagrams-and-tables/annotations/en_simple_table_22.json new file mode 100644 index 0000000000000000000000000000000000000000..0cf2ae5328cc8ddf09395ba63393489580b77d20 --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_22.json @@ -0,0 +1,10 @@ +[ + { + "type": "title", + "text": "STANDARD NORMAL DISTRIBUTION: Table Values Represent AREA to the LEFT of the Z score." + }, + { + "type": "table", + "html": "
Z.00.01.02.03.04.05.06.07.08.09
-3.9.00005.00005.00004.00004.00004.00004.00004.00004.00003.00003
-3.8.00007.00007.00007.00006.00006.00006.00006.00005.00005.00005
-3.7.00011.00010.00010.00010.00009.00009.00008.00008.00008.00008
-3.6.00016.00015.00015.00014.00014.00013.00013.00012.00012.00011
-3.5.00023.00022.00022.00021.00020.00019.00019.00018.00017.00017
-3.4.00034.00032.00031.00030.00029.00028.00027.00026.00025.00024
-3.3.00048.00047.00045.00043.00042.00040.00039.00038.00036.00035
-3.2.00069.00066.00064.00062.00060.00058.00056.00054.00052.00050
-3.1.00097.00094.00090.00087.00084.00082.00079.00076.00074.00071
-3.0.00135.00131.00126.00122.00118.00114.00111.00107.00104.00100
-2.9.00187.00181.00175.00169.00164.00159.00154.00149.00144.00139
-2.8.00256.00248.00240.00233.00226.00219.00212.00205.00199.00193
-2.7.00347.00336.00326.00317.00307.00298.00289.00280.00272.00264
-2.6.00466.00453.00440.00427.00415.00402.00391.00379.00368.00357
-2.5.00621.00604.00587.00570.00554.00539.00523.00508.00494.00480
-2.4.00820.00798.00776.00755.00734.00714.00695.00676.00657.00639
-2.3.01072.01044.01017.00990.00964.00939.00914.00889.00866.00842
-2.2.01390.01355.01321.01287.01255.01222.01191.01160.01130.01101
-2.1.01786.01743.01700.01659.01618.01578.01539.01500.01463.01426
-2.0.02275.02222.02169.02118.02068.02018.01970.01923.01876.01831
-1.9.02872.02807.02743.02680.02619.02559.02500.02442.02385.02330
-1.8.03593.03515.03438.03362.03288.03216.03144.03074.03005.02938
-1.7.04457.04363.04272.04182.04093.04006.03920.03836.03754.03673
-1.6.05480.05370.05262.05155.05050.04947.04846.04746.04648.04551
-1.5.06681.06552.06426.06301.06178.06057.05938.05821.05705.05592
-1.4.08076.07927.07780.07636.07493.07353.07215.07078.06944.06811
-1.3.09680.09510.09342.09176.09012.08851.08691.08534.08379.08226
-1.2.11507.11314.11123.10935.10749.10565.10383.10204.10027.09853
-1.1.13567.13350.13136.12924.12714.12507.12302.12100.11900.11702
-1.0.15866.15625.15386.15151.14917.14686.14457.14231.14007.13786
-0.9.18406.18141.17879.17619.17361.17106.16853.16602.16354.16109
-0.8.21186.20897.20611.20327.20045.19766.19489.19215.18943.18673
-0.7.24196.23885.23576.23270.22965.22663.22363.22065.21770.21476
-0.6.27425.27093.26763.26435.26109.25785.25463.25143.24825.24510
-0.5.30854.30503.30153.29806.29460.29116.28774.28434.28096.27760
-0.4.34458.34090.33724.33360.32997.32636.32276.31918.31561.31207
-0.3.38209.37828.37448.37070.36693.36317.35942.35569.35197.34827
-0.2.42074.41683.41294.40905.40517.40129.39743.39358.38974.38591
-0.1.46017.45620.45224.44828.44433.44038.43644.43251.42858.42465
-0.0.50000.49601.49202.48803.48405.48006.47608.47210.46812.46414
" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_23.json b/diagrams-and-tables/annotations/en_simple_table_23.json new file mode 100644 index 0000000000000000000000000000000000000000..722f28a729f955420ac63690ede9c8ccbdc4e22d --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_23.json @@ -0,0 +1,38 @@ +[ + { + "type": "title", + "text": "Revision of Seasonally Adjusted Household Survey Data" + }, + { + "type": "text", + "text": "At the end of each calendar year, BLS updates the seasonal adjustment factors for the national labor force series derived from the household survey. As a result of this process, seasonally adjusted data for January 2021 through November 2025 were subject to revision. (Not seasonally adjusted data were not subject to revision.)" + }, + { + "type": "text", + "text": "Table A shows the unemployment rates for January 2025 through November 2025, excluding October 2025, as first published and as revised. (Household survey data were not collected for October 2025 due to the federal government shutdown.) The unemployment rate changed by one-tenth of a percentage point in 4 of the 10 months and was unchanged in the remaining 6 months. Revised seasonally adjusted data for other major labor force series back to December 2024 appear in table B." + }, + { + "type": "text", + "text": "More information on this year's revisions to seasonally adjusted household series is available at www.bls.gov/web/empsit/cps-seas-adjustment-methodology.pdf. Detailed information on the seasonal adjustment methodology is found at www.bls.gov/cps/seasonal-adjustment-methodology.htm." + }, + { + "type": "text", + "text": "Historical data for the household series contained in the A tables (A-1 through A-16) of this news release can be accessed at www.bls.gov/cps/cpsatabs.htm. Revised historical seasonally adjusted data are available at www.bls.gov/cps/data.htm and https://download.bls.gov/pub/time.series/ln." + }, + { + "type": "title", + "text": "Table A. Seasonally adjusted unemployment rates in 2025 and changes due to revision January - November 2025" + }, + { + "type": "table", + "html": "
MonthAs First PublishedAs RevisedChange
January...............................4.04.00.0
February.............................4.14.20.1
March..................................4.24.20.0
April....................................4.24.20.0
May.....................................4.24.30.1
June....................................4.14.10.0
July.....................................4.24.30.1
August................................4.34.30.0
September..........................4.44.40.0
October..............................———
November..........................4.64.5-0.1
" + }, + { + "type": "text", + "text": "NOTE: Data for October 2025 were not collected due to the federal government shutdown." + }, + { + "type": "page_number", + "text": "-5-" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_24.json b/diagrams-and-tables/annotations/en_simple_table_24.json new file mode 100644 index 0000000000000000000000000000000000000000..6edf3f5d96eb1e27bb7e66272ca16ade252e6667 --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_24.json @@ -0,0 +1,22 @@ +[ + { + "type": "title", + "text": "2026 Percentage Method Tables for Manual Payroll Systems With Forms W-4 from 2020 or Later" + }, + { + "type": "text", + "text": "DAILY Payroll Period" + }, + { + "type": "table", + "html": "
STANDARD Withholding Rate Schedules
(Use these if the box in Step 2 of Form W-4 is NOT checked.)		Form W-4, Step 2, Checkbox, Withholding Rate Schedules
(Use these if the box in Step 2 of Form W-4 IS checked.)
If the Adjusted Wage Amount (line 1h) is:The tentative amount to withhold is:Plus this percentageof the amount that the Adjusted Wage exceeds—If the Adjusted Wage Amount (line 1h) is:The tentative amount to withhold is:Plus this percentageof the amount that the Adjusted Wage exceeds—
At least—But less than—At least—But less than—
ABCDEABCDE
Married Filing JointlyMarried Filing Jointly
$0.00$123.80$0.000%$0.00$0.00$61.90$0.000%$0.00
$123.80$219.20$0.0010%$123.80$61.90$109.60$0.0010%$61.90
$219.20$511.50$9.5412%$219.20$109.60$255.80$4.7712%$109.60
$511.50$936.90$44.6222%$511.50$255.80$468.50$22.3122%$255.80
$936.90$1,676.00$138.2024%$936.90$468.50$838.00$69.1124%$468.50
$1,676.00$2,094.80$315.5932%$1,676.00$838.00$1,047.40$157.7932%$838.00
$2,094.80$3,080.40$449.6035%$2,094.80$1,047.40$1,540.20$224.8035%$1,047.40
$3,080.40$794.5637%$3,080.40$1,540.20$397.2837%$1,540.20
Single or Married Filing SeparatelySingle or Married Filing Separately
$0.00$61.90$0.000%$0.00$0.00$31.00$0.000%$0.00
$61.90$109.60$0.0010%$61.90$31.00$54.80$0.0010%$31.00
$109.60$255.80$4.7712%$109.60$54.80$127.90$2.3812%$54.80
$255.80$468.50$22.3122%$255.80$127.90$234.20$11.1522%$127.90
$468.50$838.00$69.1124%$468.50$234.20$419.00$34.5424%$234.20
$838.00$1,047.40$157.7932%$838.00$419.00$523.70$78.8932%$419.00
$1,047.40$2,525.80$224.8035%$1,047.40$523.70$1,262.90$112.3935%$523.70
$2,525.80$742.2437%$2,525.80$1,262.90$371.1137%$1,262.90
Head of HouseholdHead of Household
$0.00$92.90$0.000%$0.00$0.00$46.40$0.000%$0.00
$92.90$161.00$0.0010%$92.90$46.40$80.50$0.0010%$46.40
$161.00$352.30$6.8112%$161.00$80.50$176.20$3.4112%$80.50
$352.30$499.40$29.7722%$352.30$176.20$249.70$14.8922%$176.20
$499.40$868.80$62.1324%$499.40$249.70$434.40$31.0624%$249.70
$868.80$1,078.30$150.7832%$868.80$434.40$539.10$75.3932%$434.40
$1,078.30$2,556.70$217.8235%$1,078.30$539.10$1,278.40$108.9035%$539.10
$2,556.70$735.2637%$2,556.70$1,278.40$367.6537%$1,278.40
" + }, + { + "type": "page_number", + "text": "62" + }, + { + "type": "footer", + "text": "Publication 15-T (2026)" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/annotations/en_simple_table_25.json b/diagrams-and-tables/annotations/en_simple_table_25.json new file mode 100644 index 0000000000000000000000000000000000000000..0a740333e272a8c3e2d011e75effc21f53964078 --- /dev/null +++ b/diagrams-and-tables/annotations/en_simple_table_25.json @@ -0,0 +1,18 @@ +[ + { + "type": "title", + "text": "WHO Model List of Essential Medicines - 23rd List (2023)" + }, + { + "type": "table", + "html": "
22. MEDICINES FOR REPRODUCTIVE HEALTH AND PERINATAL CARE
22.1 Contraceptives
22.1.1 Oral hormonal contraceptives
☐ ethinylestradiol + ☐ levonorgestrel
Therapeutic alternatives to be reviewed		Tablet: 30 micrograms + 150 micrograms.
☐ ethinylestradiol + ☐ norethisterone
Therapeutic alternatives to be reviewed		Tablet: 35 micrograms + 1 mg.
levonorgestrelTablet: 30 micrograms; 750 micrograms (pack of two); 1.5 mg.
ulipristalTablet: 30 mg (as acetate).
22.1.2 Injectable hormonal contraceptives
estradiol cypionate + medroxyprogesterone acetateInjection: 5 mg + 25 mg.
medroxyprogesterone acetateInjection (intramuscular): 150 mg mL in 1 mL vial.
Injection (subcutaneous): 104 mg/0.65 mL in pre-filled syringe or single-dose injection delivery system.
norethisterone enantateOily solution: 200 mg/mL in 1 mL ampoule.
22.1.3 Intrauterine devices
copper-containing device
levonorgestrel-releasing intrauterine systemIntrauterine system: with reservoir containing 52 mg of levonorgestrel
22.1.4 Barrier methods
condoms
diaphragms
22.1.5 Implantable contraceptives
etonogestrel-releasing implantSingle-rod etonogestrel-releasing implant: containing 68 mg of etonogestrel.
levonorgestrel-releasing implantTwo-rod levonorgestrel-releasing implant: each rod containing 75 mg of levonorgestrel (150 mg total).
22.1.6 Intravaginal contraceptives
ethinylestradiol + etonogestrelVaginal ring: containing 2.7 mg + 11.7 mg
progesterone vaginal ring*Progesterone-releasing vaginal ring: containing 2.074 g of micronized progesterone.
*For use in women actively breastfeeding at least 4 times per day
" + }, + { + "type": "footer", + "text": "WHO Model List of Essential Medicines - 23rd List (2023)" + }, + { + "type": "page_number", + "text": "page 52" + } +] \ No newline at end of file diff --git a/diagrams-and-tables/images/cn_diagram_01.jpg b/diagrams-and-tables/images/cn_diagram_01.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d99fb3abe4d02e33b9d15b5c8c155696ed77c0be --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_01.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6dd9ee1c0eabf4898d26288bf9d1fd28577654d1d525c5636c6b5402f8b4499a +size 353746 diff --git a/diagrams-and-tables/images/cn_diagram_02.jpg b/diagrams-and-tables/images/cn_diagram_02.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3d21af08c0eae6dd33b681e1ce2d66f9ccc53bb --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_02.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04bdf49be57c7e4cd25b04f2411154b81decd1a6d567740013335adfea0a75e4 +size 316377 diff --git a/diagrams-and-tables/images/cn_diagram_03.jpg b/diagrams-and-tables/images/cn_diagram_03.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c1e53b80b66af6593ccb724bdb31e4695f9075b --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_03.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d05193eac2057cb0f7d11244f93ddc4c4b9b973f84eb7f604580487740bf28b +size 281231 diff --git a/diagrams-and-tables/images/cn_diagram_04.jpg b/diagrams-and-tables/images/cn_diagram_04.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b9d3f48a333fedbf09dbb735178b4f76ab92560 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_04.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8457f055645d9543bd3350e39cd383f39e794d7d828442491041174116e6a444 +size 335965 diff --git a/diagrams-and-tables/images/cn_diagram_05.jpg b/diagrams-and-tables/images/cn_diagram_05.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f4ea3c8dda2040fd9296f78b313b7f9ba337bab --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_05.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3f8a21e99d530ddfd5b88e25ade2ad2b1b9fd6a4c3c3f7bf6eeb1c93ef84238 +size 364706 diff --git a/diagrams-and-tables/images/cn_diagram_06.jpg b/diagrams-and-tables/images/cn_diagram_06.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a24b84c39bbef75076348874acb43210c82ca7cf --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_06.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71d583a1730b356ca9fc6ad0fa772defdfcdea61077d04f803f92bcbb8601575 +size 375077 diff --git a/diagrams-and-tables/images/cn_diagram_07.jpg b/diagrams-and-tables/images/cn_diagram_07.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1e9740504bb6f11a6833ec9b9875b24902ba019 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_07.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccbf85e9d5bc48fc44a13098a1d4d58de0432fa0d3f1e46a2665416a6a24c20a +size 295995 diff --git a/diagrams-and-tables/images/cn_diagram_08.jpg b/diagrams-and-tables/images/cn_diagram_08.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1a7d6f3966f6225c467244075b433bccc5ad7e7 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_08.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a37fb576ba43cd8b7bbef28e6fa3c794479ff7e44981f875bed79bdab902f282 +size 280486 diff --git a/diagrams-and-tables/images/cn_diagram_09.jpg b/diagrams-and-tables/images/cn_diagram_09.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0ad1a7a9a6cb0912098fd95eab58bf062db3703 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_09.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4216d8247e50e8cfb8bc096ed210ce0210a82c945807db602d4a57b3b95f4be +size 359869 diff --git a/diagrams-and-tables/images/cn_diagram_10.jpg b/diagrams-and-tables/images/cn_diagram_10.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2e0b0359f0f2b0ead7b7d6c96559e2686b8b19d --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_10.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0241d6a4a32a45d6c2debf6dbe393cbd4112c7bbfbc402802512f581bc08bcf9 +size 266337 diff --git a/diagrams-and-tables/images/cn_diagram_11.jpg b/diagrams-and-tables/images/cn_diagram_11.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32f7c6c5253e8a415f626fda6d7900435dcc0362 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_11.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7cd4cdcdc47171073ba65aaf5fc672474a8cd4037c3cdb855c05066f3c2ec390 +size 291616 diff --git a/diagrams-and-tables/images/cn_diagram_12.jpg b/diagrams-and-tables/images/cn_diagram_12.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47fb895cb234d99ba246d69edb6f191bb179fd5a --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_12.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84055b374aee712404a3a60a6d36ca49235030a92f1555d6bcb5335b9c99abb8 +size 181954 diff --git a/diagrams-and-tables/images/cn_diagram_13.jpg b/diagrams-and-tables/images/cn_diagram_13.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc7710e97cd6bd1a0a46e3fbd1b59f8f8b4767eb --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_13.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1b69f32cfc064d7f078d02e7da65868ec7db96bc233e3ae6486cfef00621271 +size 263826 diff --git a/diagrams-and-tables/images/cn_diagram_14.jpg b/diagrams-and-tables/images/cn_diagram_14.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fac4509a53105366c3e1f7994c9d6967daef500e --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_14.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d9d5fefb67a023f9e3a0eacea73ebf8943bf0e01525d852679fc982c1f7efa5 +size 286166 diff --git a/diagrams-and-tables/images/cn_diagram_15.jpg b/diagrams-and-tables/images/cn_diagram_15.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8853e8327ac058ddadc2f12b52dff67ba8518b6 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_15.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e88c8f8ab58419f3fc487996ddc356e70d9f98920550c50d6d1c787977eb017 +size 301109 diff --git a/diagrams-and-tables/images/cn_diagram_16.jpg b/diagrams-and-tables/images/cn_diagram_16.jpg new file mode 100644 index 0000000000000000000000000000000000000000..046264cd94d5e9f0fb03bb8967ff89656d314b25 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_16.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c4195ac12e9eb440608d065d2d0ce494ecb642adbcbd0062d0bbd8f6903e1dc +size 322641 diff --git a/diagrams-and-tables/images/cn_diagram_17.jpg b/diagrams-and-tables/images/cn_diagram_17.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73ce582c19d5b778af834bdc3e15f85bbd6eceec --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_17.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24fee8a4d1116935cd9360af6e3906a0e205fcca20779d4c6d76ed12986f3e60 +size 347626 diff --git a/diagrams-and-tables/images/cn_diagram_18.jpg b/diagrams-and-tables/images/cn_diagram_18.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac5c71801d537b8192dc2d31ec94677c24666f7e --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_18.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a310cb18d7f5a925acb9e1c3583ba73d02a0eff72a09343ccb4bcf5db8ce97e +size 412081 diff --git a/diagrams-and-tables/images/cn_diagram_19.jpg b/diagrams-and-tables/images/cn_diagram_19.jpg new file mode 100644 index 0000000000000000000000000000000000000000..673dbfd8e51d2e048bfef94fa73a2fbc8f2b8df5 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_19.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab9fe504ed5d6f5a41cf47cc5d65c34b75df776759a3658f1ef5e50a9d22c820 +size 424329 diff --git a/diagrams-and-tables/images/cn_diagram_20.jpg b/diagrams-and-tables/images/cn_diagram_20.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0dbeb56664a1e6dc006e06b7bec2260d6bc13b44 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_20.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bfb9827d9649819ca71ecfa1a16f60e5c412eb636372e5b56357339f5171aa7 +size 324303 diff --git a/diagrams-and-tables/images/cn_diagram_21.jpg b/diagrams-and-tables/images/cn_diagram_21.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b157b5740bdb7ad76006e85bd89637602ace070 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_21.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85755466080ee8e833db055bb1df151cdd5e67cfb6f3dbef6b2b7055945cd37d +size 305520 diff --git a/diagrams-and-tables/images/cn_diagram_22.jpg b/diagrams-and-tables/images/cn_diagram_22.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcfa2323b725ad5a41ac9e5bea5b53c6c54958aa --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_22.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb8786ca29df9905c28b11f6f240ed0a44d0e1387a3e39862666b55ee0ff7ba9 +size 309499 diff --git a/diagrams-and-tables/images/cn_diagram_23.jpg b/diagrams-and-tables/images/cn_diagram_23.jpg new file mode 100644 index 0000000000000000000000000000000000000000..607e6f7b31f64cc8123af6d12ef7c717e880392e --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_23.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbb1b97fa66c3f055e0145ac0b8925d918e18ee3858a48c46820a1a1ee8e67fe +size 445324 diff --git a/diagrams-and-tables/images/cn_diagram_24.jpg b/diagrams-and-tables/images/cn_diagram_24.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64206364ecf6edca00a255015e676e6b20c5f25a --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_24.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07e26539776ade9832dd84ca955184c2f97af654aaa827f938b8cbedfafbfbf5 +size 302242 diff --git a/diagrams-and-tables/images/cn_diagram_25.jpg b/diagrams-and-tables/images/cn_diagram_25.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2b85312aced0b89a987a7ae2f866afcd8923b6a --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_25.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b958ae880d3e980af2e2177e523f1db3e73ef8d114d88a68e3136e310795da2 +size 329033 diff --git a/diagrams-and-tables/images/cn_diagram_26.jpg b/diagrams-and-tables/images/cn_diagram_26.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb469ab97177af1463ee3601fa937509a51533b1 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_26.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e580da68c388c4f0045b1e04383fbe31828fab51eb0eef45a212b4f19e098974 +size 373856 diff --git a/diagrams-and-tables/images/cn_diagram_27.jpg b/diagrams-and-tables/images/cn_diagram_27.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fccf5d194017160e5e5d46454c0ff5c4b485af68 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_27.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc2ccb7a620d5b5dbc2f4c04fda06408f7b9972f18d1c8ab0c5e023d65638824 +size 367565 diff --git a/diagrams-and-tables/images/cn_diagram_28.jpg b/diagrams-and-tables/images/cn_diagram_28.jpg new file mode 100644 index 0000000000000000000000000000000000000000..318b05fbe9c23b15b4aa80c6933ae04ce9e2cbea --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_28.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:baac209ba13a67875fbe821507d7a39d32ca431e3e3c6c90d5fd0b6ce72f159b +size 292702 diff --git a/diagrams-and-tables/images/cn_diagram_29.jpg b/diagrams-and-tables/images/cn_diagram_29.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ebfc61a87c495602697a7d6d2b81a83187ea4fd --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_29.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b25a0f7273ed9e18c9024bd4a650c3c03cff1e744f608978d0a4329ff1aceabd +size 312558 diff --git a/diagrams-and-tables/images/cn_diagram_30.jpg b/diagrams-and-tables/images/cn_diagram_30.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21ad8a37716cdfdd72d3ea6fff4874744141c838 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_30.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:858391aa42207bf09a0dafbb51b951a142c4eedd5aa4ae3219b5f39cc6ce1c04 +size 675452 diff --git a/diagrams-and-tables/images/cn_diagram_31.jpg b/diagrams-and-tables/images/cn_diagram_31.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9022624b8b0ff9e9398bc1f29328411399588d7b --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_31.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2e87e3e657f6b68b03afb701756f1ef06e0586caf19009ca216bf13ce8d6fbf +size 480711 diff --git a/diagrams-and-tables/images/cn_diagram_32.jpg b/diagrams-and-tables/images/cn_diagram_32.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00b00a74ca3c44b0d15de14accb5bc4898022f92 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_32.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:254bc61df626e71f9ae6a10a813ddea9d7918f33c24cd1a50884e95d6e491fb6 +size 515695 diff --git a/diagrams-and-tables/images/cn_diagram_33.jpg b/diagrams-and-tables/images/cn_diagram_33.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3ec5d6cbfb67d9d4e8892060ceb33ab7be9289b --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_33.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:963912adf5a1580a8af20cdb0e25949ccfc07e46973f7145328afca21fdc6e88 +size 607567 diff --git a/diagrams-and-tables/images/cn_diagram_34.jpg b/diagrams-and-tables/images/cn_diagram_34.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa867d49bd76599e90974d2293259c7f254ecb76 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_34.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82b68e4ba719572afc0e992caff53ddc09c9f0685cb473bcbb235d64fd4b3ede +size 552671 diff --git a/diagrams-and-tables/images/cn_diagram_35.jpg b/diagrams-and-tables/images/cn_diagram_35.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed5bf4f09c2caa56fefd3f51c2902d798c0a606c --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_35.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45af8c9095d6b90584190d06384737196f5dcad44fdbe1eff3f40e401ea0ea3a +size 344309 diff --git a/diagrams-and-tables/images/cn_diagram_36.jpg b/diagrams-and-tables/images/cn_diagram_36.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c292e4749e6b0b0d30aca3a6349e824ab6535055 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_36.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a481c8afd1910d229355e9aa758ae7cf23fb54dae3bbdd17df921be3489cc1a4 +size 337196 diff --git a/diagrams-and-tables/images/cn_diagram_37.jpg b/diagrams-and-tables/images/cn_diagram_37.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97949691657aeeace97103d1320d025aee3e2b1c --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_37.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79d88d6064ed05a08b8d0a95ab2830eb51b9c670bb83390f3c63b677bdc2a327 +size 368331 diff --git a/diagrams-and-tables/images/cn_diagram_38.jpg b/diagrams-and-tables/images/cn_diagram_38.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd9aa8431c0deedd6a0d3b8d0ec9a817ccae9e58 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_38.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efb6736502365c7f073f2d90af302f7420cf88b1107bfea5c30d132acb648b02 +size 272969 diff --git a/diagrams-and-tables/images/cn_diagram_39.jpg b/diagrams-and-tables/images/cn_diagram_39.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98c5e2bc51e09919d5f0b2d44fc57091b1d6e4e7 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_39.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c6bc7dd9261a97dec5fdd783808e5156401c6eb5d1d870848004d245362cfeb +size 245165 diff --git a/diagrams-and-tables/images/cn_diagram_40.jpg b/diagrams-and-tables/images/cn_diagram_40.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95c7720321acb8288b467cf1e851f522c279f9fe --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_40.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c13d0bd141f304bf57d4484bc0e0841a8f4dc5602a38fdc0799108df3ae545bb +size 272487 diff --git a/diagrams-and-tables/images/cn_diagram_41.jpg b/diagrams-and-tables/images/cn_diagram_41.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98e2c68850925f736c46812216e383312e911604 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_41.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aac6609d0cb906efa716782dceda5bc2db71e9b7791c471d1ea489ea625038ef +size 243208 diff --git a/diagrams-and-tables/images/cn_diagram_42.jpg b/diagrams-and-tables/images/cn_diagram_42.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e23393130f18cf055580fbf8e51923d231f29181 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_42.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3424fbc33cfcff2ded9f15eb5893ef7f9e861c07b8bdbb84165a0a979ee3443 +size 182722 diff --git a/diagrams-and-tables/images/cn_diagram_43.jpg b/diagrams-and-tables/images/cn_diagram_43.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0334fb73d0e6737120b056f0f67cd5e9d9ca8e6b --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_43.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b1609bd0ea81444a2d4fb75b76c062dec830cba808ba2338714881dd781ea9c +size 151699 diff --git a/diagrams-and-tables/images/cn_diagram_44.jpg b/diagrams-and-tables/images/cn_diagram_44.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9b5db595c22f3283baec069ed8a1788165312dc --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_44.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4f1139f0d15260b01cee34b74437a6617d1806c6b1ac95162a0864a3c594854 +size 172332 diff --git a/diagrams-and-tables/images/cn_diagram_45.jpg b/diagrams-and-tables/images/cn_diagram_45.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d67fff0f395710995cbad7f48601cf39e9c36f3 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_45.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe731b8a29e21bdd0049135eb4b852b4512cf651315d682706cd3aff589109f8 +size 232073 diff --git a/diagrams-and-tables/images/cn_diagram_46.jpg b/diagrams-and-tables/images/cn_diagram_46.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ada0923c04810a1d72a772b6572b01cd9feeaba1 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_46.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c23ad750757ebc0fa1010e815d71d993ad6ffaeed843fdb6ec487e0c1d0e36a7 +size 246391 diff --git a/diagrams-and-tables/images/cn_diagram_47.jpg b/diagrams-and-tables/images/cn_diagram_47.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a71b7fac351f9c2cb5bc44baa022af6592376fd --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_47.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1946f9594265c7241455f7fc061ee6a3106f92f104c870c302f2767e60795451 +size 183999 diff --git a/diagrams-and-tables/images/cn_diagram_48.jpg b/diagrams-and-tables/images/cn_diagram_48.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca24ee33d95758a08f425ac24fb4a22aa6246c2b --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_48.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dfec732ace74a9667d4e4178e724197b2fe5ac491a5c772977ec10c28c43036b +size 268725 diff --git a/diagrams-and-tables/images/cn_diagram_49.jpg b/diagrams-and-tables/images/cn_diagram_49.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b44b8c0713bc481af8b8700d8d8824a00ce5ed7f --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_49.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5273908214b513db575ca1216ce68322735cb92f1455be6352a5c1488f8234dc +size 345366 diff --git a/diagrams-and-tables/images/cn_diagram_50.jpg b/diagrams-and-tables/images/cn_diagram_50.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48ea279fb1434407abfbfe41edb2cd527f7f96d4 --- /dev/null +++ b/diagrams-and-tables/images/cn_diagram_50.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e0a3dd06c94998f677e6f687ed05da13aa52d8451c77f5fa45f53a43e5b4a96 +size 352621 diff --git a/diagrams-and-tables/images/cn_nested_table_01.jpg b/diagrams-and-tables/images/cn_nested_table_01.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24693bf5d4fcdcfa4d715e2cd5ba93f9d49a41b1 --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_01.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f342947419590c926d75522539fb62eb1d7f4fff1ca760f0573b6e8b727dfa9d +size 260420 diff --git a/diagrams-and-tables/images/cn_nested_table_02.jpg b/diagrams-and-tables/images/cn_nested_table_02.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4364f6a89a999940d539e20f334a20586576a25 --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_02.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e2ce9cccbef252c4a6cd8f7482a01aff65d43bc1e89a5a20314c97529a929a9 +size 323620 diff --git a/diagrams-and-tables/images/cn_nested_table_03.jpg b/diagrams-and-tables/images/cn_nested_table_03.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6c49de8786464eb1a485f52ca8b27bae52bd929 --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_03.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5673acfc7fb62e7a60ac9c7525dab72361f4d28fdb4cb8b53e5cd188be79a2d +size 251338 diff --git a/diagrams-and-tables/images/cn_nested_table_04.jpg b/diagrams-and-tables/images/cn_nested_table_04.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad5e3c99a0063c8108d35cfc6b96303933a2427a --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_04.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:127a7de723c270137b886549636084793e827126eddd3644d6c512d83857bd67 +size 282343 diff --git a/diagrams-and-tables/images/cn_nested_table_05.jpg b/diagrams-and-tables/images/cn_nested_table_05.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a60951355d1a1a5b345b154cde717692057a39e --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_05.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4566fd416aa41e70659dc9d253ab44e2acdd8224b8cfc1ff91ad47d3590a222c +size 341267 diff --git a/diagrams-and-tables/images/cn_nested_table_06.jpg b/diagrams-and-tables/images/cn_nested_table_06.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8b5f2780287622850cf04a577da6a5197ae2280 --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_06.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95940811e9d425c8385577266462d379706ba702d51ac69bf9b3a031da26071a +size 262709 diff --git a/diagrams-and-tables/images/cn_nested_table_07.jpg b/diagrams-and-tables/images/cn_nested_table_07.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84ad9996331c5f6a93e66092c967ab4dd325b956 --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_07.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2ff2268f0b697be52bb3b6966ad82291a563152ee63d695a6576dd1abcd830f +size 286898 diff --git a/diagrams-and-tables/images/cn_nested_table_08.jpg b/diagrams-and-tables/images/cn_nested_table_08.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56ea005765c354a7c470688ef8ffe4ae4b54da29 --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_08.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75bf1433e1a6fbb66847b886d401b10ad9441c89fe291cc2e0a745614673c74d +size 239917 diff --git a/diagrams-and-tables/images/cn_nested_table_09.jpg b/diagrams-and-tables/images/cn_nested_table_09.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efd9930e9ec7ea0ddc1f7ab19f77edcdc50e6d03 --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_09.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2866480d9d2e1ff83440d038070e86f8bb698fbb6d2d1b602e22545b52de20b +size 180687 diff --git a/diagrams-and-tables/images/cn_nested_table_10.jpg b/diagrams-and-tables/images/cn_nested_table_10.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7da91ccd6e8b0ef49d51f1b37e65b5744e30407 --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_10.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1baa90815f95ab03b632e180c5db7e438f1f3fe8d4cfd14fa1b96247176d148 +size 235124 diff --git a/diagrams-and-tables/images/cn_nested_table_11.jpg b/diagrams-and-tables/images/cn_nested_table_11.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43fdd13b98e71342635df3ec67e064c672d84e92 --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_11.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e8bb3116f792cc62fa07c0f29e05882f704fd2acc38b6391f5ce051839ce67d +size 153252 diff --git a/diagrams-and-tables/images/cn_nested_table_12.jpg b/diagrams-and-tables/images/cn_nested_table_12.jpg new file mode 100644 index 0000000000000000000000000000000000000000..683dda115246f16698fc8a63c764ed39b5902d0d --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_12.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb726aac6b2e5791af6a1490305abe38516452f912a06d55bca1fecc4764fc6d +size 217537 diff --git a/diagrams-and-tables/images/cn_nested_table_13.jpg b/diagrams-and-tables/images/cn_nested_table_13.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31cde5e6c5a2ca7546cc512fd20c0ec238ec41cf --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_13.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b200eea6f700d4836bf38b5a128d63e21aacaa5fffd18f9648d4cc3a104620e +size 344427 diff --git a/diagrams-and-tables/images/cn_nested_table_14.jpg b/diagrams-and-tables/images/cn_nested_table_14.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4289c388ab195afe73f1e2081fd2758a32e8e76 --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_14.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edc6f7b52989403ea3357a0af98e21fc841f54e60dc9b83cf67119060b396bf7 +size 271832 diff --git a/diagrams-and-tables/images/cn_nested_table_15.jpg b/diagrams-and-tables/images/cn_nested_table_15.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d3f5ffa7838a9bd2a4b2d6b79fcf2afd73f98e0 --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_15.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40ae6a2e00f34a33d188747718098ce8fe09c46f76775017645fd7d339e1c947 +size 356470 diff --git a/diagrams-and-tables/images/cn_nested_table_16.jpg b/diagrams-and-tables/images/cn_nested_table_16.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbef17d1b9e48b84f02d581605cecb722dedaa49 --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_16.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aefe4882139a09c3ed12bd275effd8db32a44e1a17220f0e16d535c0bd1bfc61 +size 327442 diff --git a/diagrams-and-tables/images/cn_nested_table_17.jpg b/diagrams-and-tables/images/cn_nested_table_17.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8159c88a5f8acd427b78e5f029efea99a598c4c --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_17.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bfca50dcbe6762c58bdf4e8e77a7b9d95e7383683416d6bc34d1994d7312074 +size 379582 diff --git a/diagrams-and-tables/images/cn_nested_table_18.jpg b/diagrams-and-tables/images/cn_nested_table_18.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f28f12e5a617c6400d88715b98f59637ccbf1b7d --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_18.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd491aa09fb886c3201261ea34f40707d581a8a6b089cb3e4435106a8388e813 +size 271000 diff --git a/diagrams-and-tables/images/cn_nested_table_19.jpg b/diagrams-and-tables/images/cn_nested_table_19.jpg new file mode 100644 index 0000000000000000000000000000000000000000..103141cadecb26c45a9cbc851a066b7c3adeab83 --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_19.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d195a29eeb59473ae04558a70c4c97781bdb9c37bcc36daba8fe5df8c9c72463 +size 382576 diff --git a/diagrams-and-tables/images/cn_nested_table_20.jpg b/diagrams-and-tables/images/cn_nested_table_20.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bc046bef4769cd875c9a50df8c53a15e93e7121 --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_20.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:989e8b86e2295a0643c4543a4e072443c29ee4783003a9de67ee525731a70b3c +size 163493 diff --git a/diagrams-and-tables/images/cn_nested_table_21.jpg b/diagrams-and-tables/images/cn_nested_table_21.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7669d6b4ae71161a1648cd967f7bcb7ef67c7f00 --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_21.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3570335225fbac364da2c1ae9c25216cd53815da843e5ac789f4466f68dfe57b +size 286144 diff --git a/diagrams-and-tables/images/cn_nested_table_22.jpg b/diagrams-and-tables/images/cn_nested_table_22.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e10c8bdba05f36db91f4145a6f916584cdd517e5 --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_22.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c0d0c9e8a753d09bed5427b6122a72ed6d0043925c060b625310477feb6766c +size 311355 diff --git a/diagrams-and-tables/images/cn_nested_table_23.jpg b/diagrams-and-tables/images/cn_nested_table_23.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbfbb51728868dcdf239f7b6047cc6dd59444dbe --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_23.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3201a1dfe0f932cdb5f46c9458ca23fe6fe53d6a12a67a750327d0a8ff808650 +size 313958 diff --git a/diagrams-and-tables/images/cn_nested_table_24.jpg b/diagrams-and-tables/images/cn_nested_table_24.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f00601e62e6d12509e90848785a6fd6fbb4599c --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_24.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad3a11da70579f7a2466fe9b8d2a87888d62cdaf21397784400297993f9c2cda +size 180308 diff --git a/diagrams-and-tables/images/cn_nested_table_25.jpg b/diagrams-and-tables/images/cn_nested_table_25.jpg new file mode 100644 index 0000000000000000000000000000000000000000..362c5582070c51ad846ed71ac05c44a1ea2b3ef3 --- /dev/null +++ b/diagrams-and-tables/images/cn_nested_table_25.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81cc7fc44aab340274ef5c3d925cd04bf59a33a5a9d6e863a470b2fac6ce4ba3 +size 351660 diff --git a/diagrams-and-tables/images/cn_simple_table_01.jpg b/diagrams-and-tables/images/cn_simple_table_01.jpg new file mode 100644 index 0000000000000000000000000000000000000000..996648f17e4fa4af3835b50ae840714f23803ea2 --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_01.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87018a83a10f3a1f69c773065412c824d2e1b7c80859a343d494d06a4443cbc8 +size 340778 diff --git a/diagrams-and-tables/images/cn_simple_table_02.jpg b/diagrams-and-tables/images/cn_simple_table_02.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f6f1b4f4383756bdfe813c7bc88476ada787fbc --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_02.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43760245e8321f8d3505e796019e4acfa79f0202ca00442b360a64e41e92d13c +size 345812 diff --git a/diagrams-and-tables/images/cn_simple_table_03.jpg b/diagrams-and-tables/images/cn_simple_table_03.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81012d81b9e8222d941ed3c69596b9a060760709 --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_03.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff142ef7d58b14b8430d8aef47ddaa0037e25e0ef720f562ff335d31af33d3c5 +size 240375 diff --git a/diagrams-and-tables/images/cn_simple_table_04.jpg b/diagrams-and-tables/images/cn_simple_table_04.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fc44ed61121920bd12b27c1d4a7cb591467fd32 --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_04.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d34226c92ac056358a01e9b6699060c885ab55062a796c5fb10297aa25bf6af6 +size 536093 diff --git a/diagrams-and-tables/images/cn_simple_table_05.jpg b/diagrams-and-tables/images/cn_simple_table_05.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4fe2b55c57493623e9bf539a57b2de99d6f800cc --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_05.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62cebdac96ef172556f125c1277910e7cc3206987ce242aabbc0b2d235e80947 +size 618227 diff --git a/diagrams-and-tables/images/cn_simple_table_06.jpg b/diagrams-and-tables/images/cn_simple_table_06.jpg new file mode 100644 index 0000000000000000000000000000000000000000..347c55fb6c55963dfeae4e837d3fb47ac075b0d9 --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_06.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d84d8199d5e2aefee9ff9905796f4f481d5932d8ddb4a44f22e292d6c742ec0 +size 612883 diff --git a/diagrams-and-tables/images/cn_simple_table_07.jpg b/diagrams-and-tables/images/cn_simple_table_07.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de5aca0400a460734c4127e6aa5bde9cf00668c7 --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_07.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:507f5c324d4ce118a7b578dbb0f40382ae3f0c31f05e4cb6d56c626a223b6586 +size 368195 diff --git a/diagrams-and-tables/images/cn_simple_table_08.jpg b/diagrams-and-tables/images/cn_simple_table_08.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a41391cf542cb8e5920bf48971cb98c7454ced0e --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_08.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f22d28a16caad756ec770868f3a6896470255fcc947f3b48a266ee39b0918b14 +size 406670 diff --git a/diagrams-and-tables/images/cn_simple_table_09.jpg b/diagrams-and-tables/images/cn_simple_table_09.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f694a4f8bc0bf3160928ddf921fe7c33506b76f5 --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_09.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbce9aefe1a97dfb0ee264e3202b3be8547bb580c3b6b1c4952c0873e18a6ae5 +size 288635 diff --git a/diagrams-and-tables/images/cn_simple_table_10.jpg b/diagrams-and-tables/images/cn_simple_table_10.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24561ae45d2488e89b943fce88e2095a9aa438ca --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_10.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67459e304b299f35dbfc069b73edd73d2b73d58d44a3e2ee2d76828da9875038 +size 228716 diff --git a/diagrams-and-tables/images/cn_simple_table_11.jpg b/diagrams-and-tables/images/cn_simple_table_11.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b54aa89fd7c10a8f9714f5743aecd6cda66ab4df --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_11.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59ed4b21b6fa8b30b2449d57dcdd690f24097cc7dd50d7bc9f950a411a89dc1e +size 285750 diff --git a/diagrams-and-tables/images/cn_simple_table_12.jpg b/diagrams-and-tables/images/cn_simple_table_12.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7817d8ba9dde8ebe983b889ca18e454f9f9249bb --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_12.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ac9c1343ecb36395bf062ea3fe4f54f6e647b7a0574d4a2c268e0f8195e0209 +size 230303 diff --git a/diagrams-and-tables/images/cn_simple_table_13.jpg b/diagrams-and-tables/images/cn_simple_table_13.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69bb7220a91ee9a5db535edd4db96963cf5457d6 --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_13.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8637754d8f9ef963b4bd2272bfee14b3ff9da84dcd03d53841b4961df6ca4ef9 +size 325748 diff --git a/diagrams-and-tables/images/cn_simple_table_14.jpg b/diagrams-and-tables/images/cn_simple_table_14.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d7dfab5e7e6b303866e8ac7106a7995e1a62f50 --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_14.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cb56efd056a2ccbb03f197b21b99d7d3b03a72660607c1631ccfd0c917ec16e +size 321142 diff --git a/diagrams-and-tables/images/cn_simple_table_15.jpg b/diagrams-and-tables/images/cn_simple_table_15.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15cb677fa011549be00fbab6fdd840fbbed8f360 --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_15.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f9f9546b5fc31d4a2dae22b2136c267836f4032bfbe11ce83bcc6a64f46c326 +size 315183 diff --git a/diagrams-and-tables/images/cn_simple_table_16.jpg b/diagrams-and-tables/images/cn_simple_table_16.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8fde4ed035a4be5d1767a630d268907b0adbe1d9 --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_16.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3978b45fe8b20ba8d8c2a3c69b79f7f3bbb2b3469bd5d5e214b1870f69adee22 +size 324562 diff --git a/diagrams-and-tables/images/cn_simple_table_17.jpg b/diagrams-and-tables/images/cn_simple_table_17.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e19f9ef55cbca2da641fa78896282566aecab33 --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_17.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a4597064cf7dc30c2b679b8f3a3d318a2479713c9aace164b2a247f11db5cfe +size 226724 diff --git a/diagrams-and-tables/images/cn_simple_table_18.jpg b/diagrams-and-tables/images/cn_simple_table_18.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2f7f74dd4f0f6c94097f2443280d718e36febe0 --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_18.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:330e02ba32a3c7def3a3744d1b028b6823721f36751d4824dd883b9708326c22 +size 294973 diff --git a/diagrams-and-tables/images/cn_simple_table_19.jpg b/diagrams-and-tables/images/cn_simple_table_19.jpg new file mode 100644 index 0000000000000000000000000000000000000000..759aac497724a2b6285460cda3230825260f0bc2 --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_19.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e60f3afe6b4711974446404faca8cdabc4844a6ab76da0920aefa2fa30ffc8d +size 266886 diff --git a/diagrams-and-tables/images/cn_simple_table_20.jpg b/diagrams-and-tables/images/cn_simple_table_20.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b81ba9c93ec685f62db387417b5537c59f6eb8e --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_20.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82f4d2d8bc02b9c8a1ca798e77d56829cde4c24c2f76dc279edecd476b37f188 +size 370635 diff --git a/diagrams-and-tables/images/cn_simple_table_21.jpg b/diagrams-and-tables/images/cn_simple_table_21.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b8ea1b77629304a47360777bfadc60ec85a5983 --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_21.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0b60ff697ad989926c18bd83ecd041fb3ecb2e499986a8f8f561fba45297a28 +size 324297 diff --git a/diagrams-and-tables/images/cn_simple_table_22.jpg b/diagrams-and-tables/images/cn_simple_table_22.jpg new file mode 100644 index 0000000000000000000000000000000000000000..090ff86d4b01ab2ce0bed25315ea223bb9f0b1d4 --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_22.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:758c4a0eec48f8876758beac946e81a7779417e9e573f0348313f6007bec9373 +size 272477 diff --git a/diagrams-and-tables/images/cn_simple_table_23.jpg b/diagrams-and-tables/images/cn_simple_table_23.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31eef15b7204a7747459f28ad68cc46f2ddf18c8 --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_23.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b4d0b4e6e76e64c313499f7332e362d76019b7018fbc6a2ee8ce10e0a2e8642 +size 260971 diff --git a/diagrams-and-tables/images/cn_simple_table_24.jpg b/diagrams-and-tables/images/cn_simple_table_24.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cf5112c270a1e2bc138926589c0f6915d7d1c02 --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_24.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1ebacc243bd2de567837dbf5487c50bad2ff5eabcd7631ffb5109533eee972f +size 383940 diff --git a/diagrams-and-tables/images/cn_simple_table_25.jpg b/diagrams-and-tables/images/cn_simple_table_25.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dfd2447f7b224456a8f5aaa791cb85a0d64f493d --- /dev/null +++ b/diagrams-and-tables/images/cn_simple_table_25.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26c4e08cf2fc6243f0abbbe96dcf9081aa9fd4f47b99b9201f43dc289a78690f +size 203606 diff --git a/diagrams-and-tables/images/en_diagram_01.jpg b/diagrams-and-tables/images/en_diagram_01.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64be230b79ee1128fd9ab97e5c80cae0255d0b95 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_01.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca961a9ff483f6e67d16857cd1c87780562e1438b65391abbe2d4553c8c0e0d7 +size 674077 diff --git a/diagrams-and-tables/images/en_diagram_02.jpg b/diagrams-and-tables/images/en_diagram_02.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df90da41be65d03692c2c274d0ae2dcb08c02f87 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_02.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:888323b953c2116fb1b117a09ffca957249b0eefd36bec3a1a10a581ffdc4546 +size 720110 diff --git a/diagrams-and-tables/images/en_diagram_03.jpg b/diagrams-and-tables/images/en_diagram_03.jpg new file mode 100644 index 0000000000000000000000000000000000000000..330938965d9383f1253f75d6accbbab9765f7ed7 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_03.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bde390a235e1bfc800d6f6b5efd497f49e70824ca582d1264503e20719ddaf86 +size 584608 diff --git a/diagrams-and-tables/images/en_diagram_04.jpg b/diagrams-and-tables/images/en_diagram_04.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb154a9b36667c0b188c83e41b66769f0cf48100 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_04.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb31a085f5217e5b8bfdc3a80849fd23c9066f4c1249445fed2171cfb9009013 +size 488200 diff --git a/diagrams-and-tables/images/en_diagram_05.jpg b/diagrams-and-tables/images/en_diagram_05.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4740530b2cafbd5243d1220830b69dc69ab19ba0 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_05.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20302f7b1a7036d11eec9518551bd3b553947061157b8ad59e27642b8d6c4fcc +size 413333 diff --git a/diagrams-and-tables/images/en_diagram_06.jpg b/diagrams-and-tables/images/en_diagram_06.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69f718a591a80702d995e69510e5ea7ee70ac480 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_06.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33a64ef613557e4758c245c3cb8fb5975bda3a9d928a55914e377e56b6fbe74f +size 354480 diff --git a/diagrams-and-tables/images/en_diagram_07.jpg b/diagrams-and-tables/images/en_diagram_07.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdf5ac578684a454a107103312722da9e2f56eea --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_07.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7fdc36a8b31bb5302e2ea777ac16a4d154b9a388267c4dbe49ddee34a4eb3d5 +size 378487 diff --git a/diagrams-and-tables/images/en_diagram_08.jpg b/diagrams-and-tables/images/en_diagram_08.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a16a240b347dc0e3be73fe27d38799b325559429 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_08.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2dda95e2b005a5683e40f18df562b5c24852090f77fce03e6c5db31ba4d9091b +size 550930 diff --git a/diagrams-and-tables/images/en_diagram_09.jpg b/diagrams-and-tables/images/en_diagram_09.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b75ce77a6e6e4bee57b2a10bcbc2dce790b8d4c --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_09.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ebb4aa5e4680407196c2449250f6c864396ba924ff0ab92a870a5331de5e1f1 +size 197367 diff --git a/diagrams-and-tables/images/en_diagram_10.jpg b/diagrams-and-tables/images/en_diagram_10.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39207d09c9eddebbf62c15694c5ea26e2b28df21 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_10.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbefa9ae4fd8487d6eaeecefe41a351ea762f533abc7d6d6560481e566b655e8 +size 336856 diff --git a/diagrams-and-tables/images/en_diagram_11.jpg b/diagrams-and-tables/images/en_diagram_11.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d36ed2d8e3dd70de5c77f8f0094bd10616e0368 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_11.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41604129bd62f0f40fde3f91d596affa8faae2904230b46448f2b60533dd0f84 +size 228965 diff --git a/diagrams-and-tables/images/en_diagram_12.jpg b/diagrams-and-tables/images/en_diagram_12.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c3fdf79ca56d2cdb0e23a33eb8e1a4dcd6f49c4 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_12.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27afcd24f331ef4ffac1c50fe322a917c0bd7fd1f75fdfef7a7924ad72704dba +size 428982 diff --git a/diagrams-and-tables/images/en_diagram_13.jpg b/diagrams-and-tables/images/en_diagram_13.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb47180dee03d3b8fd40f44203850f4663610900 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_13.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96ae6d6ebc8fcf0d98a05455908a02dfaf0d2c9c6f5aeffdb71de86f25dda505 +size 418800 diff --git a/diagrams-and-tables/images/en_diagram_14.jpg b/diagrams-and-tables/images/en_diagram_14.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d672c44534b806f76d0427b196a1406b6830a82b --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_14.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9b671dfb304a7681cdd5d2e7303d586569d538eb443f4605ceb30926aa448fc +size 389177 diff --git a/diagrams-and-tables/images/en_diagram_15.jpg b/diagrams-and-tables/images/en_diagram_15.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7862d5009452efb32508bc675c66babdefc37fc --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_15.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2527543b6a1e06d7e6d4a4955b80941570a272fd5e612cd34b9d1f829b4fbf13 +size 418343 diff --git a/diagrams-and-tables/images/en_diagram_16.jpg b/diagrams-and-tables/images/en_diagram_16.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9aa0e7130c4d5aa4c1ff532ae9296cb0c282ddd --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_16.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ea6d96d487d60aa68fcd81b10331dfab8b950d69daa7f16f0311ba0bf300880 +size 400825 diff --git a/diagrams-and-tables/images/en_diagram_17.jpg b/diagrams-and-tables/images/en_diagram_17.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36dba1a4695d096a8d55782354e6b8148f1bccdf --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_17.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a737bae1fce1acf277ce46668663c7ba87294816ba2b636cabe3c46d2c7b4d2 +size 321113 diff --git a/diagrams-and-tables/images/en_diagram_18.jpg b/diagrams-and-tables/images/en_diagram_18.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39c44e3354218e9b127615a3f6e91001d804e527 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_18.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4449fa5bf36e8930853c649a0a99b83697322429237ed7bf07987544bb9edbd7 +size 323146 diff --git a/diagrams-and-tables/images/en_diagram_19.jpg b/diagrams-and-tables/images/en_diagram_19.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78bce938cb187281c3e3b27e4fd1897b00aa6405 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_19.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6f64bd2b29df3e9c0753fcf655037662e20b266a2abccb24676053c7ca96238 +size 414000 diff --git a/diagrams-and-tables/images/en_diagram_20.jpg b/diagrams-and-tables/images/en_diagram_20.jpg new file mode 100644 index 0000000000000000000000000000000000000000..760868e098455f36a4c6e0b1cba8c044363ef2a8 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_20.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9984a8b99dbcc62f51e04e6089dfa08591ef8ef4d7700b475a35224f7edb9c8d +size 508626 diff --git a/diagrams-and-tables/images/en_diagram_21.jpg b/diagrams-and-tables/images/en_diagram_21.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2aabeaa1d0079011f495bc0a4783ae2d4cf21eee --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_21.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:678cfab48628288103aad3c2a72fd933b849d5d331724f7c17893c7d2c5678a6 +size 364017 diff --git a/diagrams-and-tables/images/en_diagram_22.jpg b/diagrams-and-tables/images/en_diagram_22.jpg new file mode 100644 index 0000000000000000000000000000000000000000..983900c9844c14cd0f59666ebaaca950c4692246 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_22.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9972df5eff0f1d832e63ce48277d97f935fb470bd9239d473acb5a9bcebf8b3d +size 172893 diff --git a/diagrams-and-tables/images/en_diagram_23.jpg b/diagrams-and-tables/images/en_diagram_23.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be1c777e5ded776e7de85ba50bf0d65ebb9815e7 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_23.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60edf555981acc3120b2cb9a41d0cee3ff5f097eecb2cf8bb455981f82eb43eb +size 187403 diff --git a/diagrams-and-tables/images/en_diagram_24.jpg b/diagrams-and-tables/images/en_diagram_24.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc3a810358aea63c255ec1d957cf95bb88f83217 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_24.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6eeb2ae8b8b7ec852af7b5ca9ef29e56d2e506cb9ce19d11c1a4de6ef8ebb27a +size 322143 diff --git a/diagrams-and-tables/images/en_diagram_25.jpg b/diagrams-and-tables/images/en_diagram_25.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3e5ac2c6f09f2d824d0695bbe24cbfa8b310241 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_25.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dfcf6626a77971584924a871cd756f4cb1fa2aab27be156be948ef118f58e9e4 +size 224880 diff --git a/diagrams-and-tables/images/en_diagram_26.jpg b/diagrams-and-tables/images/en_diagram_26.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a70bf1d6033ec03ec1f0812f756938ba282d0d2 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_26.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:489e99c9aa0595e5d495b74cf3a84ee5e61d77c56c96ea1804a2b0e3776bd938 +size 357485 diff --git a/diagrams-and-tables/images/en_diagram_27.jpg b/diagrams-and-tables/images/en_diagram_27.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6793f05c80f56c90b58f3cc41b6d00f595757e6 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_27.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a101505a4208a50520d1d7841211c9ce4ccd4c1b279e92832fd75a32e4e6e286 +size 253537 diff --git a/diagrams-and-tables/images/en_diagram_28.jpg b/diagrams-and-tables/images/en_diagram_28.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce0b66abcce055ebee658daca1b64d67098169f8 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_28.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2515454dfedeb08cc6083fb9ddd4520d48f63f24246c30cf3e7cd5b6bbb4c39a +size 519329 diff --git a/diagrams-and-tables/images/en_diagram_29.jpg b/diagrams-and-tables/images/en_diagram_29.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6631d9c421da98433390f42101e966389634c8ef --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_29.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b78113e98e11eb1d8a5d4711d1c1974e5cc2795ebc63660c6b8f702c48a2758a +size 345999 diff --git a/diagrams-and-tables/images/en_diagram_30.jpg b/diagrams-and-tables/images/en_diagram_30.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aef0c12a2aa8a2c617ca2e9573854553255cc246 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_30.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9f5ee46095495abbec84230636760e61ba7b34e869c6baab9fcd250bb9136c0 +size 294123 diff --git a/diagrams-and-tables/images/en_diagram_31.jpg b/diagrams-and-tables/images/en_diagram_31.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74282bb85d6d69a5722b6afbcd60666c09ff9606 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_31.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:557680ecdb39e2925c32c17a7649523b2a5252d0ba772f3a675f14f546c74d15 +size 395539 diff --git a/diagrams-and-tables/images/en_diagram_32.jpg b/diagrams-and-tables/images/en_diagram_32.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e0e67039ffbef25e8a5bae1eeefe1b0ad28901f --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_32.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:157c2e0a2bb612cb92b2f312ff2b0345568bd38711e3f287e9d423046684a32d +size 359200 diff --git a/diagrams-and-tables/images/en_diagram_33.jpg b/diagrams-and-tables/images/en_diagram_33.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b64becdc8e015abdbc2ddad1e4127db51c3fc60a --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_33.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f31d4c4d9ec910b1d080f6c4a06218dce1d021ebb6f77d17f11addcebd3ad07 +size 220177 diff --git a/diagrams-and-tables/images/en_diagram_34.jpg b/diagrams-and-tables/images/en_diagram_34.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df9e3f15b42de9ec8433b6747ac17462a3d43725 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_34.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0088cc16c5b7c74ed31ec1ef97b5240b33fe0056b4dd63aef7e2efe913459f4 +size 256429 diff --git a/diagrams-and-tables/images/en_diagram_35.jpg b/diagrams-and-tables/images/en_diagram_35.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f18592cd80e052050524424a5c09a448a5d62e9 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_35.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34956ae18158aeb26378116b0f3fa536169d18004e6a552db748faf3059c1e0b +size 391136 diff --git a/diagrams-and-tables/images/en_diagram_36.jpg b/diagrams-and-tables/images/en_diagram_36.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90f3ec034ea56cc55a4b0b4e6954a905b14eb33b --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_36.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebe688f613680136681d4ee698243db7cbf19c17599d82f24fa7e3f0b30036a8 +size 336344 diff --git a/diagrams-and-tables/images/en_diagram_37.jpg b/diagrams-and-tables/images/en_diagram_37.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb37f5d4b53ba4769e83d9da03fe070387008643 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_37.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9d9d86459abe6d0e5c75e309e5d432fdcf96b5a7946ff72c51c24086093fbdc +size 312649 diff --git a/diagrams-and-tables/images/en_diagram_38.jpg b/diagrams-and-tables/images/en_diagram_38.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83277f2a2f9efb0c90da4961e12ff13f8f2a78a3 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_38.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e514768d5fccdae3fd85199ae839967ef2059b890d61a9224f9e6db3b4226720 +size 331096 diff --git a/diagrams-and-tables/images/en_diagram_39.jpg b/diagrams-and-tables/images/en_diagram_39.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d901afe03174d38c0b0ce23d182f8800e2f720f --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_39.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b828ace0ce022dc3bb5c2d08dcb81659599c76386dacfcd65577b48ccb7c89fc +size 526033 diff --git a/diagrams-and-tables/images/en_diagram_40.jpg b/diagrams-and-tables/images/en_diagram_40.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd4677f290ba0329df8d3759e74d502dddb09e3a --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_40.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:984033cffcef153f7c02ad6ec9234a7724f23b8e65f5a4172485652807e27b79 +size 397617 diff --git a/diagrams-and-tables/images/en_diagram_41.jpg b/diagrams-and-tables/images/en_diagram_41.jpg new file mode 100644 index 0000000000000000000000000000000000000000..464f375e740fa5153b049bae9c31eeae9642c5e1 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_41.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48f885e339f64aaf13b6c70e5740af2b951be78b0a30a5d65aabb870ffb24a26 +size 241024 diff --git a/diagrams-and-tables/images/en_diagram_42.jpg b/diagrams-and-tables/images/en_diagram_42.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36d5977b842035b4a88f829eb4052771a0dc0d77 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_42.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4868d63ffec04aabe957c21d5e3c1ea31293f47af8546249fc32f7c456add1a +size 162803 diff --git a/diagrams-and-tables/images/en_diagram_43.jpg b/diagrams-and-tables/images/en_diagram_43.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e4a906e9aafa63b4bd755eb75196eafee56e893 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_43.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4440cf1b0c0296e196884c5351eb3771d7771fcd49190348941c3a37d3ffbf9f +size 467415 diff --git a/diagrams-and-tables/images/en_diagram_44.jpg b/diagrams-and-tables/images/en_diagram_44.jpg new file mode 100644 index 0000000000000000000000000000000000000000..604daf7a4d5689f2af96e5d3e13e284f9a78697e --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_44.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74e4917524a606031d56ed0a797701391c7d34638cd1e1d56c2477588f8d9faf +size 351251 diff --git a/diagrams-and-tables/images/en_diagram_45.jpg b/diagrams-and-tables/images/en_diagram_45.jpg new file mode 100644 index 0000000000000000000000000000000000000000..834a7ce6f20e525a3451bd1cce36993fffb27a66 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_45.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:222374ab91b3416f75691c993bde5ce716490b2c2a615376b6bf70f86cc97602 +size 262437 diff --git a/diagrams-and-tables/images/en_diagram_46.jpg b/diagrams-and-tables/images/en_diagram_46.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fcacfcf5fbd4e39444444a1a2fedaaa90fcc5b9 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_46.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fd76b8d1f5ce83c9c8f0b4fef58a597db9bd4441f140a8dd97702611fec5dc6 +size 347110 diff --git a/diagrams-and-tables/images/en_diagram_47.jpg b/diagrams-and-tables/images/en_diagram_47.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1ab342d0b38692a469d3e4b64a724c024c57da9 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_47.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:119d93f42795d3a8be5c63cbf718d57b242abb2c3b6d241a147f1189c8076ff5 +size 365307 diff --git a/diagrams-and-tables/images/en_diagram_48.jpg b/diagrams-and-tables/images/en_diagram_48.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fee6c40f9e86b857695b6845d29942c62aa70dc5 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_48.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae709d89c81dce4815928963998e4a2ee16a526dbd47fe90aa893512fd4098d6 +size 369982 diff --git a/diagrams-and-tables/images/en_diagram_49.jpg b/diagrams-and-tables/images/en_diagram_49.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0364d179ca34231ac85fd6a73a355c99300d8a5 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_49.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30e3c5d2685d5f25c5431d2e8daccd060e6b93bd099f76ddc0e12281b83e7d8e +size 319708 diff --git a/diagrams-and-tables/images/en_diagram_50.jpg b/diagrams-and-tables/images/en_diagram_50.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be9ffc566caf01bc926f91d75ba78a6b772e4ed2 --- /dev/null +++ b/diagrams-and-tables/images/en_diagram_50.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6610c114fe7c2a4790ff77b8d87e8c0bcfe900380c5813d6c73abefe8a5010bb +size 356784 diff --git a/diagrams-and-tables/images/en_nested_table_01.jpg b/diagrams-and-tables/images/en_nested_table_01.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91f1d4b06416360353c8eced24d14310177ce40b --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_01.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f45604b1203ebecacc1f66f422b188dc523c24c9e524648c38e74244a9d32d7c +size 231973 diff --git a/diagrams-and-tables/images/en_nested_table_02.jpg b/diagrams-and-tables/images/en_nested_table_02.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d5f672a9ff928c78484a997ad1d3c613ecf516a --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_02.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d717a12b99b3b6f0df363e472cb0ea49ad28315644480fd875ba5a4f3c31fcc +size 341317 diff --git a/diagrams-and-tables/images/en_nested_table_03.jpg b/diagrams-and-tables/images/en_nested_table_03.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8946aec38f4079b6eaf2aae141e2ab1a67725e9e --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_03.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf831e47c12213305e0abe7994dbab1005ed073030afae3102e996d9b39f6dd8 +size 295431 diff --git a/diagrams-and-tables/images/en_nested_table_04.jpg b/diagrams-and-tables/images/en_nested_table_04.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb4c4eaa43ce7bca5cffbe2397f1a1360fa5b38e --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_04.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fac00220bce19efc21ef8fa6ca5105e68bc5d7f877ba3d2475ff64da002ea3a7 +size 388473 diff --git a/diagrams-and-tables/images/en_nested_table_05.jpg b/diagrams-and-tables/images/en_nested_table_05.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da1094877861e6a8f3db2a2437360fe6408ea910 --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_05.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4879027b7f83422d4c472b253d7a55ce4114a1dbf76d39a66b7e93267964b2b1 +size 361843 diff --git a/diagrams-and-tables/images/en_nested_table_06.jpg b/diagrams-and-tables/images/en_nested_table_06.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34fb1dcce37dda01b652a94b3de01d17ad8a0474 --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_06.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3473f848580e74369e380231f68d18032cb6a9b0d3015864f806a0d16a641f1d +size 285515 diff --git a/diagrams-and-tables/images/en_nested_table_07.jpg b/diagrams-and-tables/images/en_nested_table_07.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c0ef9fadeed8d0f50d1dcc80755b0876c0bcf43 --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_07.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bc0f7bcf0efffd2241fd5cfa0130a5c9216bfd319196a09d6da6b64d3dc693e +size 320542 diff --git a/diagrams-and-tables/images/en_nested_table_08.jpg b/diagrams-and-tables/images/en_nested_table_08.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab523e469750f18d877231956271db076b55b280 --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_08.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40633b1ab8679be61d31ee0f5d2d85172a8e6dd8640344734997ec5d7dcbf4ef +size 329047 diff --git a/diagrams-and-tables/images/en_nested_table_09.jpg b/diagrams-and-tables/images/en_nested_table_09.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23d0f407d90997772dfe71ad9b74d80dc6c2a0a4 --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_09.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4224762b2c1df064d1e3c6fa84e10110eeff50daa0336657b467b8b833348dcf +size 329336 diff --git a/diagrams-and-tables/images/en_nested_table_10.jpg b/diagrams-and-tables/images/en_nested_table_10.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a24dd8897ad4f7fefe0138cf12bf7353ed85de7 --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_10.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a5d96092e8014770f88f4d2d275bcdb641fb19c9cd02f449e9bb26d34b67bea +size 303485 diff --git a/diagrams-and-tables/images/en_nested_table_11.jpg b/diagrams-and-tables/images/en_nested_table_11.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc1cfab418a8151bd5c568fd6850589883c7a0a4 --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_11.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd337f64138cb8ff4dfd5064f23f4ece2d60b255ab94aeb6e4784519d96fc239 +size 421695 diff --git a/diagrams-and-tables/images/en_nested_table_12.jpg b/diagrams-and-tables/images/en_nested_table_12.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19ecfad476503727209d194566b99066abb277a2 --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_12.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:579cd93b941deae17d97a9e497bb3e90d5a0d02e0f4d16b1c8be3c5dd64eca11 +size 455402 diff --git a/diagrams-and-tables/images/en_nested_table_13.jpg b/diagrams-and-tables/images/en_nested_table_13.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f7c85e1b13ed2195ea0e991d3742dcbdd080006 --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_13.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ae78483627469b52dc7c64ef76bc56d5bbffa4b9e318a6c18bbe37240cbf6ba +size 300100 diff --git a/diagrams-and-tables/images/en_nested_table_14.jpg b/diagrams-and-tables/images/en_nested_table_14.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c44f39d1d114842f36496520d77a7c01d364f8f9 --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_14.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96e9ea2ff848e4515bf6fc9c5daa4dba06289d9d22b89d9f78ddbac7df0cca17 +size 349469 diff --git a/diagrams-and-tables/images/en_nested_table_15.jpg b/diagrams-and-tables/images/en_nested_table_15.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d52ffbc08dc9647c6653c6f19aa56207f26eef0c --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_15.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b0d726b3c52e54f6d44478d58555ee9c11004fdc9d7b328edc5fac4d50fa999 +size 262715 diff --git a/diagrams-and-tables/images/en_nested_table_16.jpg b/diagrams-and-tables/images/en_nested_table_16.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6786efbb2971d39e7e358ff45830286555c4d74d --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_16.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95d7fd2626724e4b8895f4aa7f96425c8d39e6952ff93f86126f09dd0ff91a91 +size 272958 diff --git a/diagrams-and-tables/images/en_nested_table_17.jpg b/diagrams-and-tables/images/en_nested_table_17.jpg new file mode 100644 index 0000000000000000000000000000000000000000..821d1f3436f19df5cacbb160253554f0902eeb67 --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_17.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea5507ec9db988a530b932635a9f0cb7eb29cb2205fe781a32be8f6fee35e801 +size 371181 diff --git a/diagrams-and-tables/images/en_nested_table_18.jpg b/diagrams-and-tables/images/en_nested_table_18.jpg new file mode 100644 index 0000000000000000000000000000000000000000..880483d3347de2eabba3f35ea280efa96486bb8c --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_18.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:baab958c6920e629265ef8d56a8111b3c2dab07d66c09fa6b297551b29012970 +size 470528 diff --git a/diagrams-and-tables/images/en_nested_table_19.jpg b/diagrams-and-tables/images/en_nested_table_19.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ca03e99c5b353ee22d72a4f08dbbab1fbd68d1a --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_19.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3296389389f68d6343de24f1f64aa60dbe590b5836bad4970fadb1dcb8ae39e +size 467236 diff --git a/diagrams-and-tables/images/en_nested_table_20.jpg b/diagrams-and-tables/images/en_nested_table_20.jpg new file mode 100644 index 0000000000000000000000000000000000000000..302961a62f39ea8b45f82ab987beabe0bf431117 --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_20.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8299693b12c4c565cd55cf7712c412fc9d0f8c0246fb2eff5fdafb90eb23faa +size 379371 diff --git a/diagrams-and-tables/images/en_nested_table_21.jpg b/diagrams-and-tables/images/en_nested_table_21.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70ffcff11760cc628abcd3ca6f5a519f6bdd4600 --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_21.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:764eb50507d45c9a48a83b8b02ee9ffe75ba2af527fe9703c1f12dde01d0de7f +size 371395 diff --git a/diagrams-and-tables/images/en_nested_table_22.jpg b/diagrams-and-tables/images/en_nested_table_22.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cbae39a2644cdbd1c70276a7af4a937695d40cb --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_22.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3195250792374b5178af5e2dc955d1615662af75d75300f539adfe228785ee22 +size 261435 diff --git a/diagrams-and-tables/images/en_nested_table_23.jpg b/diagrams-and-tables/images/en_nested_table_23.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46c621b7ccc37db93bc0ba48ac53d66c98a4aea3 --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_23.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e73cf690e31d536da7b7a3f985b98f3d9ee7c71034878488f573822ce771773c +size 256679 diff --git a/diagrams-and-tables/images/en_nested_table_24.jpg b/diagrams-and-tables/images/en_nested_table_24.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c766e6005b2dc86fa4f3e7113d6500baf28268e5 --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_24.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c00f1b4bd1090a5b0fc9520d4cce297345c5c521dd74ec9571aac6dae0acca15 +size 305174 diff --git a/diagrams-and-tables/images/en_nested_table_25.jpg b/diagrams-and-tables/images/en_nested_table_25.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f9cf8777f0568b33b140a6c0ca4092b26427a74 --- /dev/null +++ b/diagrams-and-tables/images/en_nested_table_25.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fe7349bb0bb1eee37b5696fd19c0c1b600c2c5f1985cf24622ba4fc60bacc41 +size 298523 diff --git a/diagrams-and-tables/images/en_simple_table_01.jpg b/diagrams-and-tables/images/en_simple_table_01.jpg new file mode 100644 index 0000000000000000000000000000000000000000..557373f367aaf6973777ea2c4efd40517bc3386d --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_01.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d55228f36d69c7e1ed4675b398e0479cf6edc1cbbdc8864e5c786800756c95c3 +size 328971 diff --git a/diagrams-and-tables/images/en_simple_table_02.jpg b/diagrams-and-tables/images/en_simple_table_02.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37ab665eb69961eb59a2438961c3018ccd24ebf5 --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_02.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24e1fb1139451d0f270c76e2686d7a2cd0202c25fd6a36307c3aca606fc7ea66 +size 369839 diff --git a/diagrams-and-tables/images/en_simple_table_03.jpg b/diagrams-and-tables/images/en_simple_table_03.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b5911eb752f83e67469f2ccef2b8453affb63a2 --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_03.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c5ea0d7babde1bcd6c018f71ac0a6eaf350d51d557b2ca76a100cceec5c3072 +size 251160 diff --git a/diagrams-and-tables/images/en_simple_table_04.jpg b/diagrams-and-tables/images/en_simple_table_04.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53c4a729d63856f2408cca568a85a3adce3cc15c --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_04.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f350701ec1d58a72687fb8e8e2817163225894d4388eb3355b3569cbf3270e53 +size 401523 diff --git a/diagrams-and-tables/images/en_simple_table_05.jpg b/diagrams-and-tables/images/en_simple_table_05.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b45c83c6a7dd0f90dac7c8703a2d21b8f2aff95f --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_05.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2cae5075253ca97c6056f1d2ae1776a4e85bc9c724a6dc7aa77f4153265ff95 +size 460219 diff --git a/diagrams-and-tables/images/en_simple_table_06.jpg b/diagrams-and-tables/images/en_simple_table_06.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff2387b315045d3af7e89fc5c57fb30872042832 --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_06.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4dda735ffc0836eae8fa40d54b46275512b97feb64f67a41df59a44362880881 +size 429504 diff --git a/diagrams-and-tables/images/en_simple_table_07.jpg b/diagrams-and-tables/images/en_simple_table_07.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebb1995e5f494a45ef53866f2198dd007131f3a2 --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_07.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e24795128e557906dac3670571d7a2212b1923ca7ec45a9e33d9c6f7e23abe05 +size 416820 diff --git a/diagrams-and-tables/images/en_simple_table_08.jpg b/diagrams-and-tables/images/en_simple_table_08.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43dad9e757cbd85cd11ae56fabf54849b2a89ce2 --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_08.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d2b191fff06981e70f69c1093f3f247644f01a02ddc3b3819fabaf17b566909 +size 548343 diff --git a/diagrams-and-tables/images/en_simple_table_09.jpg b/diagrams-and-tables/images/en_simple_table_09.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a04a9094747a9d7e476888e62c13bb53eb19fa03 --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_09.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62af7a594f9de2acf247626563fd7ec9bd914ed23a850b41dfe803dcc04481f8 +size 385594 diff --git a/diagrams-and-tables/images/en_simple_table_10.jpg b/diagrams-and-tables/images/en_simple_table_10.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b01750dc76b17072cf46b97bde0d2c945adb7729 --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_10.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:293eb5ebdfb84b351579a891a0d784c9b422fcabf91d38fc713a783c28418bb1 +size 308441 diff --git a/diagrams-and-tables/images/en_simple_table_11.jpg b/diagrams-and-tables/images/en_simple_table_11.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6d49e88b552c5b2f72f4ae855d352c65088d6bb --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_11.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4c6fb295d4c01d8768ccdf64b56d8b454fb7566a76d198a98810541b0014adc +size 342304 diff --git a/diagrams-and-tables/images/en_simple_table_12.jpg b/diagrams-and-tables/images/en_simple_table_12.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c3dc5ee08505094e4bd898956350c6d88d6b51d --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_12.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca4c54898becb4b70a058b5b1e3d4a11a7c34ae50a28bc1e558e6e6ebfc82e1f +size 235136 diff --git a/diagrams-and-tables/images/en_simple_table_13.jpg b/diagrams-and-tables/images/en_simple_table_13.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb6c2a36d4d0864370fe3a036e01c661a22b5315 --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_13.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65dcfa53c4b3abe74875773e8265ac1b6b5d22a0d94dcae27490b6513f0debba +size 293945 diff --git a/diagrams-and-tables/images/en_simple_table_14.jpg b/diagrams-and-tables/images/en_simple_table_14.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dfe0c276eed2ef4377d62c9ed2b87d742fccab0c --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_14.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6ff22152c063a4e38ca37debf8ccc3f16797a9f1c7a06ed5f22c012d6eba4f7 +size 386743 diff --git a/diagrams-and-tables/images/en_simple_table_15.jpg b/diagrams-and-tables/images/en_simple_table_15.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8d46a0cd973b050aa2084fb15285016e9200389 --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_15.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2752db368aac796c6ee53db3825e43f5e1b6cfc8c2c4ff47e2d32a98bf90b8b3 +size 406402 diff --git a/diagrams-and-tables/images/en_simple_table_16.jpg b/diagrams-and-tables/images/en_simple_table_16.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb90cd96a584a55983103dbad4591833969e498a --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_16.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:912130d3e6f6d6ae63942874098042eea994237cc5cf49361bc8be2a24057db5 +size 348722 diff --git a/diagrams-and-tables/images/en_simple_table_17.jpg b/diagrams-and-tables/images/en_simple_table_17.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac985b2fa057138e8c8b07dcc5dfb079ab4bb165 --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_17.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f077e04a6250cced8c6a8f5b2fe821b1cfda6f80a609b800a056dfcd4f0ae012 +size 317593 diff --git a/diagrams-and-tables/images/en_simple_table_18.jpg b/diagrams-and-tables/images/en_simple_table_18.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e60eba1394eaed61514d8522a3549109f79c2e90 --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_18.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61f813fdad7d9949ce52ff24f82bd3a804cacb8d8f17cbd4164d57bfcd5cb503 +size 297821 diff --git a/diagrams-and-tables/images/en_simple_table_19.jpg b/diagrams-and-tables/images/en_simple_table_19.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b601b0151d35a47e9f724905ead38368c5be30e9 --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_19.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aaa34d939eec56e4548d662f4970eca2679739f8dd9e04095032e53ebbfb9b06 +size 491196 diff --git a/diagrams-and-tables/images/en_simple_table_20.jpg b/diagrams-and-tables/images/en_simple_table_20.jpg new file mode 100644 index 0000000000000000000000000000000000000000..660a511a0e7cc35362db3bed4711cd358471a2f1 --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_20.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c97c02ff38104a15d2fa633b0c2db2bb609240f47e9f8059c7f6d1fd896736a +size 444042 diff --git a/diagrams-and-tables/images/en_simple_table_21.jpg b/diagrams-and-tables/images/en_simple_table_21.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6ec0da4f71deca0807a58aba751c61358548cef --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_21.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ab044379884dcb96444a9f2b1074a1f32ae088d9b46915db47af646126e35c7 +size 277782 diff --git a/diagrams-and-tables/images/en_simple_table_22.jpg b/diagrams-and-tables/images/en_simple_table_22.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c12da23e339be71230eddbaf074a17afa3abeeac --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_22.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b1403ac89758a630c08a040fa5096e89c8fe35512cf875d85082a7c619bbb0f +size 472526 diff --git a/diagrams-and-tables/images/en_simple_table_23.jpg b/diagrams-and-tables/images/en_simple_table_23.jpg new file mode 100644 index 0000000000000000000000000000000000000000..591880d0023ea3ba0b67f09a6d3cdb48f8799cc1 --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_23.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54246d5e34a111287a470acae1a6086760a95409881202e8c47c49059b36f157 +size 362722 diff --git a/diagrams-and-tables/images/en_simple_table_24.jpg b/diagrams-and-tables/images/en_simple_table_24.jpg new file mode 100644 index 0000000000000000000000000000000000000000..475077e4033b80be14d295693324474bdbdaa79e --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_24.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed780bac0fdd008769d10f5fc5af6fe4ad174909a7fc5f1174dfd58c12ed9e59 +size 324338 diff --git a/diagrams-and-tables/images/en_simple_table_25.jpg b/diagrams-and-tables/images/en_simple_table_25.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b000af9ba4c7a6f32d25b8213585a8c891d342e --- /dev/null +++ b/diagrams-and-tables/images/en_simple_table_25.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e51c628f4afb01841f40981ccb0af1775f1cb1c07838056d4ebcfafd33dccd30 +size 314926 diff --git a/seals/annotations/seal_01.json b/seals/annotations/seal_01.json new file mode 100644 index 0000000000000000000000000000000000000000..0122a5bde2ea93032b687582d9e17f8571b60515 --- /dev/null +++ b/seals/annotations/seal_01.json @@ -0,0 +1,8 @@ +[ + { + "type": "seal", + "circle": [ + "YANGTOU UU LORD OF THE SEVEN KINGDOM" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_02.json b/seals/annotations/seal_02.json new file mode 100644 index 0000000000000000000000000000000000000000..537f9355aba298f556f47a0256aa8b5c82f00a98 --- /dev/null +++ b/seals/annotations/seal_02.json @@ -0,0 +1,8 @@ +[ + { + "type": "seal", + "circle": [ + "UNIVERSITY OF TORONTO ESEIST RALLHONTRTAO" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_03.json b/seals/annotations/seal_03.json new file mode 100644 index 0000000000000000000000000000000000000000..e5407ebf212ed5bdb343911429b378d8f04ae107 --- /dev/null +++ b/seals/annotations/seal_03.json @@ -0,0 +1,8 @@ +[ + { + "type": "seal", + "circle": [ + "HARVARD UNIVERSITY VERITFOTRINA ET SCIENTIA" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_04.json b/seals/annotations/seal_04.json new file mode 100644 index 0000000000000000000000000000000000000000..b49d4bb8b997a0da49d0f0d72e970e3453f4c65a --- /dev/null +++ b/seals/annotations/seal_04.json @@ -0,0 +1,8 @@ +[ + { + "type": "seal", + "circle": [ + "MASTER CRAFTSMANN OF FINE ARTISANS" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_05.json b/seals/annotations/seal_05.json new file mode 100644 index 0000000000000000000000000000000000000000..fcd6460f4c0d5f44ed7fc8f3cd2b3a487039953a --- /dev/null +++ b/seals/annotations/seal_05.json @@ -0,0 +1,11 @@ +[ + { + "type": "seal", + "circle": [ + "HONOR AND INTEGRITY HONOR AND INTEGRITY" + ], + "horizontal": [ + "ORDER OF THE EAGLE" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_06.json b/seals/annotations/seal_06.json new file mode 100644 index 0000000000000000000000000000000000000000..caffa9347b711d0de7d964de850b203d19370c6f --- /dev/null +++ b/seals/annotations/seal_06.json @@ -0,0 +1,8 @@ +[ + { + "type": "seal", + "circle": [ + "DOCTOR OF MEDICINE BOARD CERTIFIED SPECIALIST" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_07.json b/seals/annotations/seal_07.json new file mode 100644 index 0000000000000000000000000000000000000000..7002cfafbe67a4582d791c95882ac16ead6ecd11 --- /dev/null +++ b/seals/annotations/seal_07.json @@ -0,0 +1,8 @@ +[ + { + "type": "seal", + "circle": [ + "QIANJUN HUANG SPEL SPECIFIC SEAL" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_08.json b/seals/annotations/seal_08.json new file mode 100644 index 0000000000000000000000000000000000000000..e1035065e6ecbddae693e7af114bd03915ac4e4a --- /dev/null +++ b/seals/annotations/seal_08.json @@ -0,0 +1,8 @@ +[ + { + "type": "seal", + "circle": [ + "DOCTOR BOYU HOU DEPAD OF HEPARTMENT" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_09.json b/seals/annotations/seal_09.json new file mode 100644 index 0000000000000000000000000000000000000000..68d54f4e66262bf937648cbb334aff4e9c8be69d --- /dev/null +++ b/seals/annotations/seal_09.json @@ -0,0 +1,8 @@ +[ + { + "type": "seal", + "circle": [ + "MINNISTRY OF MAGIC UNLOCK THE UNKNNOWNWEN" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_10.json b/seals/annotations/seal_10.json new file mode 100644 index 0000000000000000000000000000000000000000..544fa888202e40dd709cd405ba6f56aa51f5a6a5 --- /dev/null +++ b/seals/annotations/seal_10.json @@ -0,0 +1,11 @@ +[ + { + "type": "seal", + "circle": [ + "FIRST PRIZE FROM MORRIS HALL LILABRARY" + ], + "horizontal": [ + "EST.1923" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_11.json b/seals/annotations/seal_11.json new file mode 100644 index 0000000000000000000000000000000000000000..e470394535821532140407b7e32e41f60b17811d --- /dev/null +++ b/seals/annotations/seal_11.json @@ -0,0 +1,11 @@ +[ + { + "type": "seal", + "circle": [ + "MEDAL FROM JOE BIDEN INSTITUTTUTE" + ], + "horizontal": [ + "MEDAL" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_12.json b/seals/annotations/seal_12.json new file mode 100644 index 0000000000000000000000000000000000000000..7ccfafb88cfaa8b863a3c12d2d542a437e58d868 --- /dev/null +++ b/seals/annotations/seal_12.json @@ -0,0 +1,8 @@ +[ + { + "type": "seal", + "circle": [ + "MORGAN PRETTYMAN 1142 SOUTH GATE AVENUE" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_13.json b/seals/annotations/seal_13.json new file mode 100644 index 0000000000000000000000000000000000000000..395e3c4556f5a43d041fcc792529f88a1f098b0b --- /dev/null +++ b/seals/annotations/seal_13.json @@ -0,0 +1,8 @@ +[ + { + "type": "seal", + "circle": [ + "RON CIMINI FULL PROFESSOR UNIVERSITY OF OHIO" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_14.json b/seals/annotations/seal_14.json new file mode 100644 index 0000000000000000000000000000000000000000..e16a2b55f3b6d235b4c1d2702aa7d20032ef674e --- /dev/null +++ b/seals/annotations/seal_14.json @@ -0,0 +1,8 @@ +[ + { + "type": "seal", + "circle": [ + "JIELIN LI DEAN OF UNIVESITY OF TAIWAN" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_15.json b/seals/annotations/seal_15.json new file mode 100644 index 0000000000000000000000000000000000000000..aec43a5750f112b6c25e67077bb97b4d9edd7c35 --- /dev/null +++ b/seals/annotations/seal_15.json @@ -0,0 +1,8 @@ +[ + { + "type": "seal", + "circle": [ + "HINTOON HARRIS SENATOR OF CALIFORNIA" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_16.json b/seals/annotations/seal_16.json new file mode 100644 index 0000000000000000000000000000000000000000..c5cf012c6ac8afde0e351424acfedb6b2d6fec58 --- /dev/null +++ b/seals/annotations/seal_16.json @@ -0,0 +1,13 @@ +[ + { + "type": "seal", + "circle": [ + "CHARTERED IN 1945 BY THE REPUBLIC OF TEXAS" + ], + "horizontal": [ + "BAYLOR UNIVERSITY", + "PRO ECCLESIA", + "PRO TEXANA" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_17.json b/seals/annotations/seal_17.json new file mode 100644 index 0000000000000000000000000000000000000000..3ac587336f41a59bc58dcc86fb5d4bc7ddaeba7d --- /dev/null +++ b/seals/annotations/seal_17.json @@ -0,0 +1,13 @@ +[ + { + "type": "seal", + "circle": [ + "INSTRUCTION EXTENSION RESEARCH" + ], + "horizontal": [ + "AUBURN UNIVERSITY", + "FOR THE ADVANCEMENT OF SCIENCE AND ART", + "ESTABLISHED" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_18.json b/seals/annotations/seal_18.json new file mode 100644 index 0000000000000000000000000000000000000000..b07c32a6be3e13366e1157725bfe45c8538b548f --- /dev/null +++ b/seals/annotations/seal_18.json @@ -0,0 +1,11 @@ +[ + { + "type": "seal", + "circle": [ + "STUDIO WONDERFUL COMPANY" + ], + "horizontal": [ + "B.V.I" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_19.json b/seals/annotations/seal_19.json new file mode 100644 index 0000000000000000000000000000000000000000..5d0795d444579bf467199660340601f6f0849aeb --- /dev/null +++ b/seals/annotations/seal_19.json @@ -0,0 +1,11 @@ +[ + { + "type": "seal", + "circle": [ + "PETER C. WONG, CHOW & CHOW" + ], + "horizontal": [ + "SOLICITORS&NOTARIES" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_20.json b/seals/annotations/seal_20.json new file mode 100644 index 0000000000000000000000000000000000000000..79295b6ea1c9772c6f06c1e4c9cb9ce0e778a206 --- /dev/null +++ b/seals/annotations/seal_20.json @@ -0,0 +1,8 @@ +[ + { + "type": "seal", + "circle": [ + "KAMALA HARRIS SENATOR OF CALIFORNIA" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_21.json b/seals/annotations/seal_21.json new file mode 100644 index 0000000000000000000000000000000000000000..c174c3a07149021a31f9b7eca06e53f9f21752e9 --- /dev/null +++ b/seals/annotations/seal_21.json @@ -0,0 +1,9 @@ +[ + { + "type": "seal", + "horizontal": [ + "FROM THE LIBRARY OF", + "WIKTORIA POLRROWICZ" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_22.json b/seals/annotations/seal_22.json new file mode 100644 index 0000000000000000000000000000000000000000..5aa071ec43ea387c64d57ecccc2ce75d643d8641 --- /dev/null +++ b/seals/annotations/seal_22.json @@ -0,0 +1,9 @@ +[ + { + "type": "seal", + "horizontal": [ + "WILD EARTH", + "FLOWER FARM" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_23.json b/seals/annotations/seal_23.json new file mode 100644 index 0000000000000000000000000000000000000000..9587881b4fbe594c15744bebc1e039f10cecc745 --- /dev/null +++ b/seals/annotations/seal_23.json @@ -0,0 +1,8 @@ +[ + { + "type": "seal", + "horizontal": [ + "thank you for supporting my small business" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_24.json b/seals/annotations/seal_24.json new file mode 100644 index 0000000000000000000000000000000000000000..4368e80ec73e221318b4c2579135c664c64baab1 --- /dev/null +++ b/seals/annotations/seal_24.json @@ -0,0 +1,9 @@ +[ + { + "type": "seal", + "horizontal": [ + "FROM THE LIBRARY OF", + "SHARON HANNA" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_25.json b/seals/annotations/seal_25.json new file mode 100644 index 0000000000000000000000000000000000000000..c3d4d3ca8fb644d9ea0e0dff3802d96cb25e6a71 --- /dev/null +++ b/seals/annotations/seal_25.json @@ -0,0 +1,9 @@ +[ + { + "type": "seal", + "horizontal": [ + "FROM THE LIBRARY OF", + "AVRIL SMITH" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_26.json b/seals/annotations/seal_26.json new file mode 100644 index 0000000000000000000000000000000000000000..a72528a04323a55155a3b531e1038dfbc4d87c1a --- /dev/null +++ b/seals/annotations/seal_26.json @@ -0,0 +1,9 @@ +[ + { + "type": "seal", + "horizontal": [ + "FROM THE LIBRARY OF", + "FRASER SMITH" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_27.json b/seals/annotations/seal_27.json new file mode 100644 index 0000000000000000000000000000000000000000..a39041753a5bd1e9ff1c69ef08ebcdea58088908 --- /dev/null +++ b/seals/annotations/seal_27.json @@ -0,0 +1,9 @@ +[ + { + "type": "seal", + "horizontal": [ + "FROM THE LIBRARY OF", + "Jennifer Baker" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_28.json b/seals/annotations/seal_28.json new file mode 100644 index 0000000000000000000000000000000000000000..8bf87b7d91e445033ba5b4db035bed0a03819958 --- /dev/null +++ b/seals/annotations/seal_28.json @@ -0,0 +1,9 @@ +[ + { + "type": "seal", + "horizontal": [ + "FROM THE LIBRARY OF", + "VICTORIA THOMAS" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_29.json b/seals/annotations/seal_29.json new file mode 100644 index 0000000000000000000000000000000000000000..619e22ed8a36854571c6e5323eadc921289456e5 --- /dev/null +++ b/seals/annotations/seal_29.json @@ -0,0 +1,9 @@ +[ + { + "type": "seal", + "horizontal": [ + "FROM THE LIBRARY OF", + "Nisa Johnson" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_30.json b/seals/annotations/seal_30.json new file mode 100644 index 0000000000000000000000000000000000000000..4dc7cc56fc78723f9f22e19474bb33b8ef5e23ea --- /dev/null +++ b/seals/annotations/seal_30.json @@ -0,0 +1,9 @@ +[ + { + "type": "seal", + "horizontal": [ + "FROM THE LIBRARY OF", + "Wiktoria Politowicz" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_31.json b/seals/annotations/seal_31.json new file mode 100644 index 0000000000000000000000000000000000000000..5bcd2eb9f80cce557b5a4b8384fd66e11d472e9c --- /dev/null +++ b/seals/annotations/seal_31.json @@ -0,0 +1,9 @@ +[ + { + "type": "seal", + "horizontal": [ + "FROM THE LIBRARY OF", + "PAULA JANE" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_32.json b/seals/annotations/seal_32.json new file mode 100644 index 0000000000000000000000000000000000000000..54442c19b195988e47e462c358a6736f677bc7e7 --- /dev/null +++ b/seals/annotations/seal_32.json @@ -0,0 +1,9 @@ +[ + { + "type": "seal", + "horizontal": [ + "FROM THE LIBRARY OF", + "HARRINGTON ANNABELLE" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_33.json b/seals/annotations/seal_33.json new file mode 100644 index 0000000000000000000000000000000000000000..f2329178824455a82d54d99f1de02defb0f0c93c --- /dev/null +++ b/seals/annotations/seal_33.json @@ -0,0 +1,9 @@ +[ + { + "type": "seal", + "horizontal": [ + "6194 PHILIPS ROAD", + "STONEHAM, MA 02180" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_34.json b/seals/annotations/seal_34.json new file mode 100644 index 0000000000000000000000000000000000000000..82d9d8969bb301c2c530e8692c6a59522d4253c0 --- /dev/null +++ b/seals/annotations/seal_34.json @@ -0,0 +1,8 @@ +[ + { + "type": "seal", + "horizontal": [ + "2365 MOSSY OAK DRIVE MEMPHIS TX, 38133" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_35.json b/seals/annotations/seal_35.json new file mode 100644 index 0000000000000000000000000000000000000000..d8b6a9f359407e5d15133b3ce9822c85ff356ed9 --- /dev/null +++ b/seals/annotations/seal_35.json @@ -0,0 +1,9 @@ +[ + { + "type": "seal", + "horizontal": [ + "2913 PARK VISTA CT", + "ROCKY MOUNT, NC 27301" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_36.json b/seals/annotations/seal_36.json new file mode 100644 index 0000000000000000000000000000000000000000..8d4aff29fe03dc2e79c93f1a2b0c855670a5340e --- /dev/null +++ b/seals/annotations/seal_36.json @@ -0,0 +1,10 @@ +[ + { + "type": "seal", + "horizontal": [ + "5301 JACKSON DRIVE", + "DALLAS, TEXAS 75024", + "SORENSON" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_37.json b/seals/annotations/seal_37.json new file mode 100644 index 0000000000000000000000000000000000000000..dcfd0b0efed02bc45800851b68651c8e162e4044 --- /dev/null +++ b/seals/annotations/seal_37.json @@ -0,0 +1,8 @@ +[ + { + "type": "seal", + "horizontal": [ + "MAYFIELD POST OFFICE BOX 1275 FRISCO TEXAS 75034" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_38.json b/seals/annotations/seal_38.json new file mode 100644 index 0000000000000000000000000000000000000000..03ce744014d1d43f0cab0047b3ac36d0cf65df3d --- /dev/null +++ b/seals/annotations/seal_38.json @@ -0,0 +1,8 @@ +[ + { + "type": "seal", + "horizontal": [ + "MIKEL JASO PRINTS" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_39.json b/seals/annotations/seal_39.json new file mode 100644 index 0000000000000000000000000000000000000000..451da78157cd0f2dc4863c23c1a5da5194ec5d41 --- /dev/null +++ b/seals/annotations/seal_39.json @@ -0,0 +1,9 @@ +[ + { + "type": "seal", + "horizontal": [ + "KATE SPADE NEW YORK", + "ORIGINAL APTWORK 2011" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_40.json b/seals/annotations/seal_40.json new file mode 100644 index 0000000000000000000000000000000000000000..548194c4ec2767e13225928a240592a041b03e88 --- /dev/null +++ b/seals/annotations/seal_40.json @@ -0,0 +1,9 @@ +[ + { + "type": "seal", + "horizontal": [ + "GEORGE", + "93158 ASHPORT JACKSON TN 38305" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_41.json b/seals/annotations/seal_41.json new file mode 100644 index 0000000000000000000000000000000000000000..f1a1418e22b29d4260771f80c5a18aea952d1b75 --- /dev/null +++ b/seals/annotations/seal_41.json @@ -0,0 +1,8 @@ +[ + { + "type": "seal", + "horizontal": [ + "BEAU MERCI COUP" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_42.json b/seals/annotations/seal_42.json new file mode 100644 index 0000000000000000000000000000000000000000..a18dd1b8e978fdf86927aca535c4f34fe327fe65 --- /dev/null +++ b/seals/annotations/seal_42.json @@ -0,0 +1,9 @@ +[ + { + "type": "seal", + "horizontal": [ + "CLASSIC Retro label", + "VINTAGE" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_43.json b/seals/annotations/seal_43.json new file mode 100644 index 0000000000000000000000000000000000000000..f87bcb71f1d724caef210cbef55d81e2b47c42e7 --- /dev/null +++ b/seals/annotations/seal_43.json @@ -0,0 +1,10 @@ +[ + { + "type": "seal", + "horizontal": [ + "25 WEST TOWER AVENUE", + "MIDDLETON", + "LONDON, ON L6C1W95" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_44.json b/seals/annotations/seal_44.json new file mode 100644 index 0000000000000000000000000000000000000000..c87045aa2bb3399753a6b72252e41f504d07aac2 --- /dev/null +++ b/seals/annotations/seal_44.json @@ -0,0 +1,9 @@ +[ + { + "type": "seal", + "horizontal": [ + "96 WINDING LANE", + "NEWTOWN, PA 18940" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_45.json b/seals/annotations/seal_45.json new file mode 100644 index 0000000000000000000000000000000000000000..3ee93e01e12e327269c05c0519e461b9a4798785 --- /dev/null +++ b/seals/annotations/seal_45.json @@ -0,0 +1,12 @@ +[ + { + "type": "seal", + "horizontal": [ + "YOUR NAME HERE", + "LICENSE", + "No. 12345", + "DELAWARE", + "PROFESSIONAL ENGINEER" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_46.json b/seals/annotations/seal_46.json new file mode 100644 index 0000000000000000000000000000000000000000..cdda4f79194f9f1a68b917e7e461f4f762b8a536 --- /dev/null +++ b/seals/annotations/seal_46.json @@ -0,0 +1,10 @@ +[ + { + "type": "seal", + "horizontal": [ + "WARE COUNTRY HIGH SCHOOL", + "OFFICIAL SEAL", + "WAYCROSS, GA" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_47.json b/seals/annotations/seal_47.json new file mode 100644 index 0000000000000000000000000000000000000000..2ff8242dc69d8f7ee76c02c9fc9ab2af0d5fba55 --- /dev/null +++ b/seals/annotations/seal_47.json @@ -0,0 +1,10 @@ +[ + { + "type": "seal", + "horizontal": [ + "TRUSTED PARTNER", + "trust trust trust trust trust", + "trust trust trust trust trust" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_48.json b/seals/annotations/seal_48.json new file mode 100644 index 0000000000000000000000000000000000000000..bc66166a9b5b1f83347abbea7e0fd9ff4917a5e3 --- /dev/null +++ b/seals/annotations/seal_48.json @@ -0,0 +1,10 @@ +[ + { + "type": "seal", + "horizontal": [ + "CERTIFIED ORIGINAL", + "original original original", + "original original original" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_49.json b/seals/annotations/seal_49.json new file mode 100644 index 0000000000000000000000000000000000000000..7709e70d2b2b6778e3b8619b1176fa9e845d66eb --- /dev/null +++ b/seals/annotations/seal_49.json @@ -0,0 +1,10 @@ +[ + { + "type": "seal", + "horizontal": [ + "100% creative", + "100% creative 100% creative", + "100% creative 100% creative" + ] + } +] \ No newline at end of file diff --git a/seals/annotations/seal_50.json b/seals/annotations/seal_50.json new file mode 100644 index 0000000000000000000000000000000000000000..1956d14eea7ad7d194d4d611ea9f8f895b277c4e --- /dev/null +++ b/seals/annotations/seal_50.json @@ -0,0 +1,10 @@ +[ + { + "type": "seal", + "horizontal": [ + "TM pragali stamps", + "PRAGALI IMPRESSIONS", + "www.pragalistamps.com" + ] + } +] \ No newline at end of file diff --git a/seals/images/seal_01.png b/seals/images/seal_01.png new file mode 100644 index 0000000000000000000000000000000000000000..60aa727f0db33c2aa5387af3739d9a0e60ff1299 --- /dev/null +++ b/seals/images/seal_01.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d996b26ac8c404a54487d1ab0deda85f1957809309ec1c5011b2129fbb5da636 +size 120752 diff --git a/seals/images/seal_02.png b/seals/images/seal_02.png new file mode 100644 index 0000000000000000000000000000000000000000..cc55d20d8edf1a11eec07380311362bacb73299d --- /dev/null +++ b/seals/images/seal_02.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8777c979e0f5d149e9e0b1411bdd6eaa0afbe64be3887cdde160332265259c3f +size 157871 diff --git a/seals/images/seal_03.png b/seals/images/seal_03.png new file mode 100644 index 0000000000000000000000000000000000000000..937c49654511226ed272d4ca512d40bab81f8d46 --- /dev/null +++ b/seals/images/seal_03.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9d4391e74f0d28edb8c1bf81eacc1da27a166897e84a8433ac9a878b0393d84 +size 80890 diff --git a/seals/images/seal_04.png b/seals/images/seal_04.png new file mode 100644 index 0000000000000000000000000000000000000000..b5993dcae6d7e8fcac110d259db5ad071bd7a8ce --- /dev/null +++ b/seals/images/seal_04.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e24b862402dcfe60fc5fa29e708f1cd2bc154fcc62bfa70c3fb69a69b823f6e8 +size 315179 diff --git a/seals/images/seal_05.png b/seals/images/seal_05.png new file mode 100644 index 0000000000000000000000000000000000000000..a0cd78cce2b2ae77537e6fea0acc5dffd3ce3dd2 --- /dev/null +++ b/seals/images/seal_05.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eab4b924dd741340cfcddbcb6887bcf02da4e57899eb557cc3c9c55ea16fe689 +size 111984 diff --git a/seals/images/seal_06.png b/seals/images/seal_06.png new file mode 100644 index 0000000000000000000000000000000000000000..4786401c69b902ae60e2cf753db13e31ad8a4927 --- /dev/null +++ b/seals/images/seal_06.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b70a4d3df8840fbff82df827fcb958e94d50d30fddacbb9a502e3b2d8f0546fa +size 269249 diff --git a/seals/images/seal_07.png b/seals/images/seal_07.png new file mode 100644 index 0000000000000000000000000000000000000000..e7d84448e1d1a62d7be4db31566fcebb42f72739 --- /dev/null +++ b/seals/images/seal_07.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8244047adef9c5e58d591a47cbad38cbfab585d9812085e80a4e6da610d97adf +size 244177 diff --git a/seals/images/seal_08.jpg b/seals/images/seal_08.jpg new file mode 100644 index 0000000000000000000000000000000000000000..883da8533199352da022890feba7a967ee4f619d --- /dev/null +++ b/seals/images/seal_08.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc86eaf624dadc6a53ef1ad23d4c9d8376582fc01c1885b3b822f4b2ddb99ebb +size 4971 diff --git a/seals/images/seal_09.png b/seals/images/seal_09.png new file mode 100644 index 0000000000000000000000000000000000000000..0634b4973059aee6de1177e7b309215136bb18d7 --- /dev/null +++ b/seals/images/seal_09.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b26b22eba91cb6fe30340e86ee05de29f0af5a36f4eda7f6e9830e1a0f85a11 +size 245591 diff --git a/seals/images/seal_10.png b/seals/images/seal_10.png new file mode 100644 index 0000000000000000000000000000000000000000..14c639fcd8a6d692cf049b6cbddf23ddab64943b --- /dev/null +++ b/seals/images/seal_10.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:585e253726d9b1af448d1b847591b4ffe6e06feff831f6324dd4f13f67eb2945 +size 124569 diff --git a/seals/images/seal_11.png b/seals/images/seal_11.png new file mode 100644 index 0000000000000000000000000000000000000000..dc04b2f50bce88b0ff3b71941e51d9d539c67b05 --- /dev/null +++ b/seals/images/seal_11.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90a8f20c815e81b2561a7a80cb338da840d3db5058ffac20eb2c45105c862cfc +size 14517 diff --git a/seals/images/seal_12.png b/seals/images/seal_12.png new file mode 100644 index 0000000000000000000000000000000000000000..c41727b37d902628e77b28934781d7b6da1859a3 --- /dev/null +++ b/seals/images/seal_12.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76395e7f25ffb6f29478b12653a360d35fcec506980780247c28c55309e81399 +size 32096 diff --git a/seals/images/seal_13.png b/seals/images/seal_13.png new file mode 100644 index 0000000000000000000000000000000000000000..6299c855aae8f30b92ceaf23b01cad0dc483c4d6 --- /dev/null +++ b/seals/images/seal_13.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ca10efdfad09e4f7f8ee1ea60d659aeabd9629f5fb7fbd49e2158b10c48aea4 +size 256216 diff --git a/seals/images/seal_14.png b/seals/images/seal_14.png new file mode 100644 index 0000000000000000000000000000000000000000..a621ffe4b29191b6962ef0d71b490d5e1352ef4f --- /dev/null +++ b/seals/images/seal_14.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:befa6199b534c26af697a2926edc5b4a348442f0526792b88a402c82bc37405a +size 96412 diff --git a/seals/images/seal_15.png b/seals/images/seal_15.png new file mode 100644 index 0000000000000000000000000000000000000000..da27c829f1fc6daddd1b569d5fb8fcddbf0463a7 --- /dev/null +++ b/seals/images/seal_15.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28f84b520cc7d616f513ed623858a2e4edb068a86cbd542c2bbcbb70439bb740 +size 258449 diff --git a/seals/images/seal_16.png b/seals/images/seal_16.png new file mode 100644 index 0000000000000000000000000000000000000000..5e007ed18fc3165d057a8b036ee9e12ffb042bf0 --- /dev/null +++ b/seals/images/seal_16.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:204e49ab1f7b7bca798a6093e91268051411ae7d9493182f9f82e130f8d49856 +size 49713 diff --git a/seals/images/seal_17.png b/seals/images/seal_17.png new file mode 100644 index 0000000000000000000000000000000000000000..a9ea60ed2e545db4499f608e62f66c536f8552af --- /dev/null +++ b/seals/images/seal_17.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63d82fa36a04493bed84368a2e871b03d26b8149fd5af51e18fe0dfa3b6912d4 +size 149845 diff --git a/seals/images/seal_18.png b/seals/images/seal_18.png new file mode 100644 index 0000000000000000000000000000000000000000..82f3ea6d674a7348bbb22d0e1348f9b948f1a8f4 --- /dev/null +++ b/seals/images/seal_18.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46d3eb1a7653769a9ecb55eb7259c2b2e1c53e6bfef201aae1b0a06e652aeffd +size 154318 diff --git a/seals/images/seal_19.png b/seals/images/seal_19.png new file mode 100644 index 0000000000000000000000000000000000000000..164b37829c3b111493633829c6c26e8ef16d1b76 --- /dev/null +++ b/seals/images/seal_19.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32a0e7858dd09cf5a3b90ffbf6bc892d454d67a3aa52b66377940da649939c1d +size 89858 diff --git a/seals/images/seal_20.png b/seals/images/seal_20.png new file mode 100644 index 0000000000000000000000000000000000000000..f64f1266075705df2ac34517ec7e3f16f377d250 --- /dev/null +++ b/seals/images/seal_20.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c53b6d453db78eac5b2774b2f7d569720a9ad68224661e6c7e029b1ef513793 +size 378214 diff --git a/seals/images/seal_21.png b/seals/images/seal_21.png new file mode 100644 index 0000000000000000000000000000000000000000..3bde19bf14e34a30a4d357ce88b0e1e742b878c4 --- /dev/null +++ b/seals/images/seal_21.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:528f7660fd429a34d2198a81ed913296b4d99b6cb8bf64adc77e9e8f13f9900a +size 45442 diff --git a/seals/images/seal_22.png b/seals/images/seal_22.png new file mode 100644 index 0000000000000000000000000000000000000000..5334594f2a5fcbf2ccc04299cd7dc6da2367bb31 --- /dev/null +++ b/seals/images/seal_22.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52e1d09b84b65666d591a873a122bcc834ef0f9b6401d0644db9dc053ab91099 +size 54758 diff --git a/seals/images/seal_23.png b/seals/images/seal_23.png new file mode 100644 index 0000000000000000000000000000000000000000..82be711bf259b9eb93ff1c895f7e4b4fe66290b7 --- /dev/null +++ b/seals/images/seal_23.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4cfe99983b3807dde4b2696b9b8ac4fafc81cc33df22de011a1d20c0abe91cb +size 258260 diff --git a/seals/images/seal_24.png b/seals/images/seal_24.png new file mode 100644 index 0000000000000000000000000000000000000000..f3bad499019803d05f10bdc0c5355873fd77b71d --- /dev/null +++ b/seals/images/seal_24.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c5c0b955c7c5b588867628cd444ba37c7e059123e84d493b306e5015e7b30c4 +size 14952 diff --git a/seals/images/seal_25.png b/seals/images/seal_25.png new file mode 100644 index 0000000000000000000000000000000000000000..3804c6dd4c9f77c988b389f38e9b1c7a2ecd7abb --- /dev/null +++ b/seals/images/seal_25.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:549bb3c07c3fe8e5d72de5c6a782e215ae323bf1262058feb0dd99a94fe647b1 +size 29742 diff --git a/seals/images/seal_26.png b/seals/images/seal_26.png new file mode 100644 index 0000000000000000000000000000000000000000..253359924f400372ff51cf5f908cb5fe82ec2103 --- /dev/null +++ b/seals/images/seal_26.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:665a9ee67656c60f11cc61a3b1a06f064464a71cca1d27dd33f60f942e50ba57 +size 12191 diff --git a/seals/images/seal_27.png b/seals/images/seal_27.png new file mode 100644 index 0000000000000000000000000000000000000000..58f0637d1e0612706a32165654103b631e08d1f6 --- /dev/null +++ b/seals/images/seal_27.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5f2ee184cf574ec82ce7e71330b7774185ec921cf9f8e5207f4a7ed6f1b0b9e +size 21856 diff --git a/seals/images/seal_28.png b/seals/images/seal_28.png new file mode 100644 index 0000000000000000000000000000000000000000..248aa7049e5cfc67b3617d90c7d29f8a8f7255af --- /dev/null +++ b/seals/images/seal_28.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb6d81892f81e4f729fd1ea4f2cb611f07d64439549f79c264ef874e75df9bdc +size 95207 diff --git a/seals/images/seal_29.png b/seals/images/seal_29.png new file mode 100644 index 0000000000000000000000000000000000000000..fda8b882b3ea3039109fee63022b6057d45c9731 --- /dev/null +++ b/seals/images/seal_29.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c3464d889bb53e1958fa2430ce0ed0cd3206be7b047e997406fb93d3319b5c1 +size 253706 diff --git a/seals/images/seal_30.png b/seals/images/seal_30.png new file mode 100644 index 0000000000000000000000000000000000000000..3563dda1e5c5ed262b0805f7745a45ac0462051c --- /dev/null +++ b/seals/images/seal_30.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bb2b18789b46e95d83596b97194bf8d6082272959264413f6c66443f33b81ac +size 52968 diff --git a/seals/images/seal_31.png b/seals/images/seal_31.png new file mode 100644 index 0000000000000000000000000000000000000000..bec13e79e27d8d4e2d3fdc6812c745f71b868330 --- /dev/null +++ b/seals/images/seal_31.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6e0db6748d113860d0f9b1d2ab922d2a3cd716708aadbe997429db6d6f49dca +size 90428 diff --git a/seals/images/seal_32.png b/seals/images/seal_32.png new file mode 100644 index 0000000000000000000000000000000000000000..c4e5eeed9d86809c5be7409aeaca405401bd969b --- /dev/null +++ b/seals/images/seal_32.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7454e84df02a21bb1d48dcb7289d0dfaf994d83e1d61b5217c90fba1b2557f60 +size 232297 diff --git a/seals/images/seal_33.png b/seals/images/seal_33.png new file mode 100644 index 0000000000000000000000000000000000000000..b0b3cf9d0edcca663532b23e1ccc0950cac8bdb9 --- /dev/null +++ b/seals/images/seal_33.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8e53ea5c1b59c5133dd16bd80f00e1ea79a1621d80e360e7983e4e964d5f89b +size 140052 diff --git a/seals/images/seal_34.png b/seals/images/seal_34.png new file mode 100644 index 0000000000000000000000000000000000000000..688c75f74e7fc39fd9c50762bca34be90a40701d --- /dev/null +++ b/seals/images/seal_34.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff34ac2f697d54c200d1f226f11bb4f1c1750c269fd7ea54fd3dec459062b954 +size 251326 diff --git a/seals/images/seal_35.png b/seals/images/seal_35.png new file mode 100644 index 0000000000000000000000000000000000000000..35206a28c2aa657572078205f8a33fc57072d48b --- /dev/null +++ b/seals/images/seal_35.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8190e981fc37ac5d937e9fef0b16b3fed81834aaab868740c5f53c650b886855 +size 133211 diff --git a/seals/images/seal_36.png b/seals/images/seal_36.png new file mode 100644 index 0000000000000000000000000000000000000000..5d6c0fd332d7bdd483b67e4df5ee2c4e1a45f71c --- /dev/null +++ b/seals/images/seal_36.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1aa0829dc5cf1cff0a4bfb02069bcc2adf97972d220b22f8084eb5c6c369b3a +size 145879 diff --git a/seals/images/seal_37.png b/seals/images/seal_37.png new file mode 100644 index 0000000000000000000000000000000000000000..6fb1d9787cc4ffde6231ecf507844cf14a3a4eaa --- /dev/null +++ b/seals/images/seal_37.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebbc54ea7291426162187369e13e642c91ec885245025b5f355e466971a17008 +size 347000 diff --git a/seals/images/seal_38.png b/seals/images/seal_38.png new file mode 100644 index 0000000000000000000000000000000000000000..44a377d5393547442ec1b669b61ec3b277629299 --- /dev/null +++ b/seals/images/seal_38.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac5638e63485d8bb5a54e843a69b23c6009103332c98740b990ce5cdca594134 +size 290560 diff --git a/seals/images/seal_39.png b/seals/images/seal_39.png new file mode 100644 index 0000000000000000000000000000000000000000..9ef08e8172ed6cc6b4b5553f7235aec7080a931d --- /dev/null +++ b/seals/images/seal_39.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71ba55d2624b183c735118ef20a14070dcb48247589331b920f861161b25af80 +size 69806 diff --git a/seals/images/seal_40.png b/seals/images/seal_40.png new file mode 100644 index 0000000000000000000000000000000000000000..aff9a2692b1c52143e0a142252ed3c841d8710ce --- /dev/null +++ b/seals/images/seal_40.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d6fabac8466e2b0a947ca399a3ddee2e05295f2cb299644c49350347eec618c +size 24224 diff --git a/seals/images/seal_41.png b/seals/images/seal_41.png new file mode 100644 index 0000000000000000000000000000000000000000..530a56358c70ff7dac3c0af88d7e32be9ccb1c6c --- /dev/null +++ b/seals/images/seal_41.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7eb600228fba6fc1446db91b2b147463f9ac19e6826714914556c3bdfe90e669 +size 176446 diff --git a/seals/images/seal_42.png b/seals/images/seal_42.png new file mode 100644 index 0000000000000000000000000000000000000000..8bbf8e848eb163a23e97b0484b62f8cbb532b73b --- /dev/null +++ b/seals/images/seal_42.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65c31765b26ff26fa20fcba9948a02ff15bfb98dcee76fedfcb8123637dde9b4 +size 33333 diff --git a/seals/images/seal_43.png b/seals/images/seal_43.png new file mode 100644 index 0000000000000000000000000000000000000000..f5ae1c0c3c442951ad6bf01fc6b283faa5b40c86 --- /dev/null +++ b/seals/images/seal_43.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d979e3652339289c6efc12bd1548b3a2adc5403fcf3b85a7a75a42fae1007bc9 +size 41690 diff --git a/seals/images/seal_44.png b/seals/images/seal_44.png new file mode 100644 index 0000000000000000000000000000000000000000..ca72a69dfebeb39a22c6382deb54dbcaf77ae938 --- /dev/null +++ b/seals/images/seal_44.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b55ffa02e93479bafe3178cb2c0f222903b82b81f183b96d78e52fa351dff18e +size 199266 diff --git a/seals/images/seal_45.png b/seals/images/seal_45.png new file mode 100644 index 0000000000000000000000000000000000000000..f7e2d5bbd29f4a653e27375ed82e41f612e3787b --- /dev/null +++ b/seals/images/seal_45.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe3a7bea49517ea021c16801b2ece3c6db6944f1bf408661886e4f66100570a3 +size 169961 diff --git a/seals/images/seal_46.png b/seals/images/seal_46.png new file mode 100644 index 0000000000000000000000000000000000000000..6a4e8e9a2e1b59ba332a8b5b32912f032d264af2 --- /dev/null +++ b/seals/images/seal_46.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e996ebe0c9491186404525a50308cad63f3797ed119a05b030d7130be7176e2e +size 81793 diff --git a/seals/images/seal_47.png b/seals/images/seal_47.png new file mode 100644 index 0000000000000000000000000000000000000000..45c5d0d4251e6dabe84a3ed2a5a8b613b1e872b4 --- /dev/null +++ b/seals/images/seal_47.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2716d84990cc78d1fe458c446976836085c08b6aa90139781cecdcf0e5f1809 +size 122780 diff --git a/seals/images/seal_48.png b/seals/images/seal_48.png new file mode 100644 index 0000000000000000000000000000000000000000..835f5ad6b67db43e78813858fcd3696fcb5ddf09 --- /dev/null +++ b/seals/images/seal_48.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46388b92873dc467c44d0c14f45cb5f0c6b3964937f87519e71657d06a4de34d +size 168475 diff --git a/seals/images/seal_49.png b/seals/images/seal_49.png new file mode 100644 index 0000000000000000000000000000000000000000..17626c23bc2a376651bd2ff8cbf1c9427fec81b4 --- /dev/null +++ b/seals/images/seal_49.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65786f7dab955775fe2d8457f78890af50763fdc48f43c1146b5d1bcb99ff868 +size 47028 diff --git a/seals/images/seal_50.png b/seals/images/seal_50.png new file mode 100644 index 0000000000000000000000000000000000000000..dd80abb5375a74c619dfaf92c2b96b3e2635a743 --- /dev/null +++ b/seals/images/seal_50.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b2ac8a20fe50f135c1f2ca70d34735aba8054d0bd0e5711c54922acea801946 +size 261119