YC/T 341.4-2010 烟草病害预测预报调查规程 第4部分：青枯病
作者:标准资料网 时间:2024-05-21 14:15:50 浏览:8584
来源:标准资料网
基本信息
| 标准名称： | 烟草病害预测预报调查规程 第4部分：青枯病 |
| 英文名称： | Rules for investigation and forecast of tobacco diseases—Part 4:Tobacco Wilt |
| 中标分类： |
食品 >>
制烟 >>
烟草制品 |
| ICS分类： |
农业 >>
烟草、烟草制品和烟草工业设备
|
| 发布部门： | 国家烟草专卖局 |
| 发布日期： | 2010-02-08 |
| 实施日期： | 2010-02-20 |
| 首发日期： | |
| 作废日期： | |
| 主管部门： | 全国烟草标准化技术委员会农业分技术委员会(SAC/TC 144/SC 2) |
| 提出单位： | 国家烟草专卖局 |
| 归口单位： | 全国烟草标准化技术委员会农业分技术委员会(SAC/TC 144/SC 2) |
| 起草单位： | 中国烟草总公司青州烟草研究所 |
| 起草人： | 孔凡玉、王静、张成省、顾钢、高正良、周志成、王凤龙 |
| 出版社： | 中国标准出版社 |
| 出版日期： | 2010-02-20 |
| 页数： | 12页 |
| 批文号： | 27793-2010 |
适用范围
YC/T341的本部分规定了烟草青枯病系统调查、大田普查方法,以及测报资料收集、汇报和汇总方法。
本部分适用于各级测报站点对烟草青枯病的测报调查。
前言
没有内容
目录
没有内容
引用标准
下列文件对于本文件的应用是必不可少的。凡是注日期的引用文件,仅注日期的版本适用于本文件。凡是不注日期的引用文件,其最新版本(包括所有的修改单)适用于本文件。
GB/T23222 烟草病虫害分级及调查方法
YC/T341.1 烟草病害预测预报调查规程 第1部分:赤星病
所属分类： 食品 制烟 烟草制品 农业 烟草 烟草制品和烟草工业设备
基本信息
| 标准名称： | 万能工具磨床 参数 |
| 中标分类： |
机械 >>
金属切削机床 >>
磨床 |
| ICS分类： |
机械制造 >>
机床 >>
磨床和抛光机
|
| 替代情况： | JB 3875-1985 |
| 发布部门： | 全国金属切削机床标委会磨床分会 |
| 发布日期： | 1999-05-20 |
| 实施日期： | 2000-01-01 |
| 首发日期： | 1900-01-01 |
| 作废日期： | 1900-01-01 |
| 归口单位： | 全国金属切削机床标委会磨床分会 |
| 出版日期： | 1900-01-01 |
| 页数： | 2 页 |
| 批文号： | 国机管[1999]283号 |
适用范围
JB/T 3875.1-1999 本标准是对 JB 3875-85《万能工具磨床 参数》的修订。 本标准是 JB/T 3875《万能工具磨床》系列标准的一部分，该系列标准包括以下三个部分： JB/T 3875.1-1999 万能工具磨床 参数 JB/T 3875.2-1999 万能工具磨床 精度检验 JB/T 3875.3-1999 万能工具磨床 技术条件 本标准规定了一般用途的万能工具磨床的参数。 本标准适用于新设计的一般用途的万能工具磨床。 本标准于 1985 年 1 月首次发布。
前言
没有内容
目录
没有内容
引用标准
没有内容
所属分类： 机械 金属切削机床 磨床 机械制造 机床 磨床和抛光机
Product Code:SAE AS5506/1
Title:SAE Architecture Analysis and Design Language (AADL) Annex Volume 1: Annex A: Graphical AADL Notation, Annex C: AADL Meta-Model and Interchange Formats, Annex D: Language Compliance and Application Program Interface Annex E: Error Model Annex
Issuing Committee:As-2c Architecture Analysis And Design Lanaguage
Scope:This document contains three annexes to the SAE AS5506 Standard - the SAE Architecture Analysis and Description Language. The first annex, Annex A Graphical AADL Notation, defines a set of graphical symbols for the graphical AADL notation. These graphical symbols can be used to express relationships between components, features, and connections in an AADL model. Graphical AADL diagrams are legal in accordance with the AADL core standard if the AADL model being presented graphically is legal and if the correct graphical symbols are used. For example, a graphical editor is not permitted to create a connection whose source and destination are not connected. Graphical presentations of AADL models are permitted to show subsets of legal AADL models. For example, property values may be entered through a property sheet or dialog box. The figures in this annex present different views of an AADL model. These views are not prescriptive, but intended to illustrate possible views and layouts.The second annex, Annex C AADL Meta Model and Interchange Formats, defines the AADL meta model and XML-based interchange formats for AADL models. The AADL meta model defines the structure of AADL models, i.e., an object representation of AADL specifications that corresponds to a semantically decorated abstract syntax tree. The object representation of AADL models can be manipulated programmatically through an API. The object representation of AADL models can also be persistently stored as XML documents in a standard interchange format. This permits different tools that support the AADL XML schema [XML 2001] or XMI meta model specification [XMI 2003] to interoperate on AADL models. Both the XML schema and the XMI meta model specification for the AADL are derived from the AADL meta model, thus, the two representations are consistent with the meta model.The third annex, Annex D Language Compliance and Application Program Interface, defines language-specific rules for source text to be compliant with an architecture specification written in AADL. While the AADL is source text language independent, this annex provides guidelines for users to transition between AADL models and source text written in Ada [ISO 1995, IEEE 2001] and source text written in C [ISO 1999]. This annex recommends the use of an Application Program Interface (API) between the application software and the execution environment to facilitate the use of mixed language application source code modules in a common execution environment.The forth annex, Annex E Error Model Annex, defines features to enable the specification of redundancy management and risk mitigation methods in an architecture, and enable qualitative and quantitative assessments of system properties such as safety, reliability, integrity, availability, and maintainability. This annex defines a sublanguage that can be used to declare error models within an error annex library and associate them with components in an architecture specification. This annex also defines a sublanguage that may be used within an error annex clause within a core AADL standard implementation declaration.
