BS ISO 11787-1996 Machinery for agriculture and forestry - Data interchange between management computer and process computers - Data interchange syntax《农业用和林业用设备 管理计算机和加工计算机间的数据交换 .pdf

《BS ISO 11787-1996 Machinery for agriculture and forestry - Data interchange between management computer and process computers - Data interchange syntax《农业用和林业用设备 管理计算机和加工计算机间的数据交换 .pdf》由会员分享，可在线阅读，更多相关《BS ISO 11787-1996 Machinery for agriculture and forestry - Data interchange between management computer and process computers - Data interchange syntax《农业用和林业用设备 管理计算机和加工计算机间的数据交换 .pdf（23页珍藏版）》请在麦多课文档分享上搜索。

1、BSI BS*ISO 11787 95 lb24bb9 0520028 441 BRITISH STANDARD Implementation of IS0 11787 : 1995 Machinery for agriculture and forestry - Data interchange between management computer and process computers - I Data interchange syntax Product code 00655990 ICs 65.020.10 BS IS0 11787 : 1995 BS IS0 11787 : 1

2、996 Amd.No. Date Committees responsible for this British Standard Text afected The preparation of this British Standard was entrusted to Technicd Committee AGEX31, Agricultural electronic equipment, upon which the following bodies were represented Agricultural Engineers Association Forestry Commissi

3、on Heaith and Safety Executive Milk Marketing Board Ministry of Agricdture, Fisheries and Food National Farmers Union Silsoe College, Cdeld Institute of Technology Silsoe Research Institute This British Standard, having been prepared under the direction of the Engineering Sector Board, was published

4、 under the authority of the Standards Board and comes into effect on 15 January 1996 O BSI 1996 The following BSI references relate to the work on this Standard Committee reference AGEY31 Draft for comment 9Y82978 DC ISBN O 680 26184 6 BS IS0 11787 : 1995 National foreword This British Standard repr

5、oduces verbatim IS0 11787 : 1995 and implements it as the UK national standard. This British Standard is published under the direction of the Engineering Sector Board whose Technical Committee AGE431 has the responsibility to: - aid enquirers to understand the text; - present to the responsible inte

6、rnational committee any enquiries on interpretation, or proposals for change, and keep UK interests informed; - monitor related international and European developments and promulgate them in the UK. NOTE. International and European Standards, as wel as overseas standards, are available from Customer

7、 Services, BSI, 389 Chiswick High Road, London W4 4AL. Compliance with a British Standard does not of itself confer immunity from legal obligations. I NTERNAT I ONA L S TA N DA R D IS0 1787 First edition 1995-06-1 5 Machinery for agriculture and forestry - Data interchange between management compute

8、r and process computers - Data interchange syntax Machines agricoles et forestires - Transfert de donnes entre lordinateur de gestion et les ordinateurs de contrle de process - change des donnes (syntaxe) Reference number IS0 1 1787:1995(E) ES1 BS+ISO 33787 95 3b246b9 0520032 972 = IS0 11787:1995(E)

9、 Contents Page Scope 1 Normative reference . . 2 Definitions . 2 General . Main ADIS characteristics . 3 Reserved characters 3 Line types 3 7.1 Line type identification . 3 7.2 Classification of line types 3 7.3 Standardized line types 3 7.4 Definition line 4 7.5 Value line 4 7.6 End line . 4 7.7 Co

10、mment line . 4 7.8 Search line 4 7.9 Request line 4 7.10 File line . 4 7.11 Include line . 4 7.12 Output line 4 7.13 Termination line 4 7.14 Physical end of file line 4 8 Status characters . 5 8.1 Status identification 5 8.2 Standardized status characters 5 8.3 Header data 5 O IS0 1995 All rights re

11、served . Unless otherwise specified. no part of this publication may be reproduced or utilized in any form or by any means. electronic or mechanical. including photocopying and microfilm . without permission in writing from the publisher . International Organization for Standardization Case Postale

12、56 CH-1211 Genve 20 Switzerland Printed in Switzerland ES1 BSSISO 11787 95 Lb24bb 0520033 809 IS0 11787:1995(E) 8.4 Normal data _._. 5 8.5 Synchronization data . , , . 5 8.6 Faulty data . 5 8.7 Deletion data _ 5 9 Combination of line types and status characters . 5 6 10 Event numbers contains the de

13、scription of an item; .I conditional (not mandatory) parts are put between square brackets; (.) parts between parentheses can occur a number of times repeatedly, at least once. EXAMPLE DN() means that the combination of a DOI number, its field length and resolution can occur a number of times. 5 Mai

14、n ADIS characteristics 5.1 acters (IS0 class B: class A plus additional use of F, I and T lines; class C: class A plus additional use of R and O lines; class D: class A plus additional use of S, R and O lines. Class A is mandatory for using ADIS. Classes B. C and D are permissible extensions. It doe

15、s not mean that, for instance, when class C is supported that automatically class B will be sup ported. When synchronizing (initializing), the sender and receiver (communication group) must tell each other in which class they can communicate. This can be done, for instance, on paper, but also automa

16、tically by using a DDI number in the ADIS file for line type classification. 7.3 Standardized line types The following line types are standardized: D Definition V Value E End of logical file C Comment S Search R Request F File 3 - - BSI BS*ISO 31787 95 Lb24bb9 0520040 T49 IS0 11787:1995(E) I Include

17、 o output T Terminate Z Physical end of file 7.10 File line A file line (F line) gives the complete name of a library file (pathname and filename). This line avoids includ- ing the file itself. F 7.4 Definition line A definition line (D line) specifies the contents of the value lines that succeed it

18、. A D line shall always be succeeded by 1 or more V lines. If no data are avail- able then all fields (starting from position 9 of the line) of the complete v line are filled out with (see also 15.3). 7-91 include line An include line (1 line) holds the Pathname and filename Of a file to be included

19、 at the position of the I line. The include file shall meet the ADIS require- ments as if it were pari of the parent file. This implies that the combination of the parent file and the include file shall meet the ADIS requirements. D(cresolution) 7.5 Value line I NOTE 8 The include option is a way to

20、 separate files physically which are one logically. The included file can contain a header, if the combination with the parent file meets the ADIS requirements. Value lines N lines) contain the Of the DD items that were specified in the last preceding D line. V lines without a preceding D line with

21、the same event number are illegal (see also 10.2). 7.12 Output line V() 7.6 End line An output line (O line) holds the pathname and An end line (E line) marks the logical end of a data file. In a file more than one E line can occur. The E line is always followed by a DH+VH line or a Z line. The phys

22、ical end of the file is marked by a Z line. The last filename of a file to which data must be written. O E line just before the Z line is not mandatory. An E line is always the same: 7.13 Termination line A termination line (T line) marks the end of a main unit of information in an ADIS file. A T li

23、ne can be used to distinguish different blocks within one file. A T line cannot be followed by a DH + VH line (see also E line). A T line is always the same: EN 7.7 Comment line Comment lines (C lines) can be put anywhere in an ADIS file. They can hold free text. TN CcCR 7.8 Search line In a search

24、line (S line) one or more search conditions can be specified. See also clause 11. 7.9 Request line A request line (R line) holds the data dictionary num- bers of attributes which are requested. See also clause 11. 7.14 Physical end of file line A physical end of file line (Z line) marks the end of a

25、 physical datafile. When a Z line occurs, the physical end of the file is reached. Everything beyond the Z line will be ignored. There shall never occur a new DH+VH line after a 2 line. It is possible but not man- datory to put an E line before the Z line. A Z line is always the same: 4 BSI BSJISO 3

26、3787 95 3624667 0520043 985 W IS0 11787:1995(E) 8 Status characters The second position of each line holds the status character. This character explains the function of the data in that line. 8.1 Status identification The standard file syntax requires capitalized status characters. Lower case charac

27、ters are manufacturer- specific, and shall be agreed upon by both the sending and receiving party. If the status character is un- known, the line is ignored. 8.2 Standardized status characters The following status characters are standardized: H Header data N Normal data S Synchronization data F Faul

28、ty data D Deletion data 8.3 Header data Each data file shall have a header. This implies that an ADIS file has to start with one DH line, followed by a VH line. Only comment lines (irrespective of their status characters) can precede the header. If the header is omitted, the whole file is illegal. I

29、t is mandatory to start the header data (right after the event number) with the name of the data dictionary that was used when creating the file. Several data dictionaries can be used. To read the received ADIS file. the receiver needs to known which data diction- ary has to be used for recognizing

30、the DDI numbers. It is recommended that the header also contains at least the following information (from the sender): Manufacturer: organization/company that made the ADIS file; Receiver: the name of the receiver of the ADIS file; DDI list version: version of the DDI list that was used when creatin

31、g the file; Product name: name of the software program that created the file: Sofware version: Program version that was used to create the file; Creation date: date of creation of the file; Creation time: time of creation of the file. It is permissible to put more data in the header. The DDI numbers

32、 of these data items have to be part of the data dictionary. 8.4 Normal data Normal data is data that is sent for updating the da- tabase of the receiving party. 8.5 Synchronization data Synchronization data is sent with the intention of initializing the database (filling the first time); comparing

33、data in the databases of the sending and the receiving party to determine which is cor- rect between the communication groups. 8.6 Faulty data If an ADIS file contains a line which seems to contain one or more errors, it is possible for the receiver to put this whole line in a separate ADIS file, wi

34、th the status character changed into an “F“. It is also poss- ible that an F status line has more fields than the corresponding N status line. For instance the F status line can contain detailed information about the kind of error, what is wrong, etc. This kind of information can be placed in the F

35、status line, according to the preceding DF line. The receiver discovers the errors in the ADIS line, and sends the F line back to the OB ginai sender. 8.7 Deletion data If an ADIS file has been sent that kept incorrect in- formation, the transmitter can copy the line that con- tained the error into

36、another ADIS file, with the status character changed into a “D“, and send that file as well. A line with a D status shall be deleted com pletely. The use of the D status is conditional. if the D status is not supported, it shall be answered by an F line. 9 Combination of line types and status charac

37、ters The matrix in figure2 shows which combinations of line types and status characters are allowed and which are not. 5 BSI BSWISO 11787 95 Lb24669 0520092 811 Is0 11787:1995(E) Status characters H N S F D Header Normal Synch Fault Delete O Definition V Value E End C Comment 3 S Search a R Request

38、a T Terminate F File I Include o output Z Phys.end c c 1- :I :I” * * + + + 1) An S line requires an R line. but an R line does not need an S line. 2) An S or R line with an F status is not a query, but a response from the receiver to the original sender that the query could not be handled. Key + All

39、owed - Not allowed Required combination Figure 2 - Combinations of line types and status characters 10 Event numbers Positions 3 to 8 of each line hold the event number of that line. Event numbers can be used in three ways, as follows. al Centrally registered event numbers. These are predefined and

40、alresdy known to all members of the communication group before receiving: 1) each registered event number is a template for a specified group of DDI numbers, in a specified order; 2) each registered event number is an event for a specified minimum/maximum group of DDI numbers, without a specified or

41、der. b) The event numbers are created by the system, when writing an ADIS file. The event number does hot have a specified meaning. It can be used to identify different data blocks. c) The event number does not have any meaning: its value is ”000000”. Event numbers starting with a zero are free to b

42、e used by manufacturers. Event numbers starting with a zero may be standardized. Event numbers can be standardized in the same way DDI numbers are standardized. An event is a group of DD items which are a logical group komparable to an entity type with key attri- butes and normal attributes). Theref

43、ore it is advisable to group data which belong to a same event. 10.1 Length of an event number An event number has a fixed length of 6 digits. It is a numerical value. 10.2 Linking value lines to definition line The event number of a D line shall be the same as the event numbers of the related succe

44、eding V lines. If the event number of a V line differs from the event number of the preceding D line, that V line is illegal. 10.3 Event numbers in search and request lines The event number of a R line shall be the same as the event numbers of the related preceding S lines (if there are any precedin

45、g S lines). If the event numbers 6 of a R and S line differ from each other, the request is impossible. The receiving party can use the event number of a R line in its response. 11 Queries Each query consists of 1 or more S lines (optional) and one R line (mandatory). The S lines hold the search con

46、ditions, the R line holds the DDI numbers of attri- butes that contain the data that is requested. An S line can only have conditions that refer to a combination of key data that refer to the key of the event. DDI numbers of the S line shall refer to key data. NOTE 9 The implementation of query hand

47、lers in pro- grams that deal with ADIS files is not mandatory. Because search conditions depend heavily on key data (known in the data dictionary). the response to a query can be implementation-dependent. 11.1 Query syntax A query has the following syntax: (S() R( ) It is not permissible to put sear

48、ch/request lines be tween related D and V lines. The S lines (if present) always immediately precede the R line. Only com- ment lines can, irrespective of their status, be placed in a group of query lines. It is recommended to sep- arate queries from the D and V lines by using a T line or by putting

49、 queries in separate files. If a query con- tains an illegal search or request line, the whole query is illegal. 11.2 Search condition of a query ( S ( ) Note that one search line can contain several search conditions. These conditions are implicitly linked with a logical AND operator. If a query contains more than one S line, the conditions in these S lines are also implicitly linked with a logical AND operator. Each search condition contains a lower value and a higher value, which means that a search can be done on a range: IS0