1、AIIM MSb0 96 1012348 050070b 507 ASSOCIATION FOR INFORMATION 1100 Wayne Avenue Suite 1 1 O0 Maryland 20910 AIIM MANAGEMENT 301 -587-8202 INTERNATIONAL COPYRIGHT Association for Information it is a part of this standard. Annex C covers datastream syntax. The scope of this standard is constrained to d
2、ata interchange. For example, it does not address issues of database replication or synchronization. nor does it address all possible issues around annotation objects such as “notes.” It is expected that future balloted extensions to this standard will address these and other issues. Suggestions for
3、 improving this standard are welcome. They should be sent to the Chair, AIIM Standards Board, Association for Information and Image Management international, 1 100 Wayne Avenue, Suite I 100, Silver Spring, Maryland, 20910-5603. At the time it approved this standard, the AIIM Standards Board had the
4、following members: Name of Representative Judy Kilpatrick, Chair Jewel M. Drass John C. Gale Tom Heltzel Bruce A. Holroyd James Meyer Roy Pierce Charles A. Plesums Fernando L. Podio Shahzad S. Qazi Michael L. Thomas Stephen Urban OrEanization Represented Association for Information and Image Managem
5、ent International Bell bi-level image,file format: Part 1. ANSI X3.135- 1992, American National Standard .for information ,Yystems - Database language - SQL. ANSI X3.4, American National Standard - Coded character set - 7-bit - Code ,for information interchange. 2.4 Referenced publications AIIM TR2-
6、 1992, Technical Report for the Association for Information und Image Management - Glossar). of imaging technolog),. Gane, Chris. Rapid system development, using structured techniques and relational technology. Prentice Hall, 1989. 2.5 Related publications AIIM TR4-I 995, Technical Report jor the As
7、sociation for Injivmation and Image Management International - Suggested index fields for documents in EIM environments. AIIM TR25-199.5, Technical Report for the Association for Information and Image Management International - The use of optical disks,for public records. AIIM TR21 -I 991, Technical
8、 Report for the Association fw Infortnation and Image Management - Recommendation ,for identibing information to be placed on Write-Once-Read-Many (WORM) and rewritable Optical Disk (OD) cartridge label(s) and optical disk curtridge packaging (shipping containers). 1 Association for Information and
9、Image Management International COPYRIGHT Association for Information object and action relationships are shown in table 2. 9. Fields in parentheses are optional. However, unless lower-level expansions indicate otherwise, optional fields must be complete. If an optional field is included, all require
10、d subfields must also be present. Those fields that are present must be in the order shown, except as specified by the accompanying text. Fields followed by an ellipsis can occur more than once in a structure. 8 Association for Information and Image Management International COPYRIGHT Association for
11、 Information & Imaging ManagementLicensed by Information Handling ServicesCINSF F Parameters CINST L Valid For CINSD L Sink Document Name Sink Folder Name AIIGI GIS60 96 H 3032348 0500939 365 ANSUAIIM MS60- 1996 Standard for the Electronic Folder Interchange Datastream Document Document Folder Attri
12、bute (folder) Note (folder) Event (foider) Document None None Document All I Folder Replace Insert in this Insert in this Insert in this Folder Divider Document Sink Divider Name Note (folder) Attribute (folder) (folder) Event Sink Folder Name Sink Document Name CINSF CINSF CINSF Sink Folder Name Do
13、cument Note (document) (document) (document) Attribute Event Folder Document CNEW CRPL CINSF CINST CINSD CINSD CINSD Note (document) Attribute (document) Event (document) Folder UID I Folder Relationship to Sink Data New Folder or Document Replace this Document Insert in this Folder (No Divider) Ins
14、ert in this Divider in this Folder Insert in this Document Insert in or Create this Folder Insert an Item with Matching Identifier Unknown Relationship I New Folder I CNEW I I CINSF I CINST I 9 Association for Information and Image Management International COPYRIGHT Association for Information & Ima
15、ging ManagementLicensed by Information Handling Services AIIM MSbR b U lQl2348 0500920 987 M ANSI/AIIM MS60- 1996 Standard for the Electronic Folder Interchange Datastream Figure 9 - Note set data structure“ - (EVENTSET) (NOTESET) (ATTSET) (Content) I (CSID) I (LANG) I (PRIV) I UID I EVENT I Figure
16、11 - Event set data structure“ 11 Association for Information and Image Management International COPYRIGHT Association for Information & Imaging ManagementLicensed by Information Handling Services - AIIM MSb0 96 W L0L2348 0500922 75T W ANSVAIIM MS60- 1996 Standard for the Electronic Folder Interchan
17、ge Datastream 8.8.5 Attribute set (profile) The attribute set associated with a folder or document contains a variable number of system-defined and user-defined attributes and the values of these attributes to be associated with the referenced object. Refer to figure 12, Attribute set (profile) data
18、 structure, for an illustration of the attribute set (profile) data structure. I (CSID) 1 (LANG) I (PRIV) I UID I AITRIB . 1 Figure 12 - Attribute set (profile) data structure* The attribute set contains one or more attributes. The attributes included are in a standard type and value format. The att
19、ribute set does not necessarily contain all the attributes that are defined for an object. The receiving system may have to supply some additional attributes that it considers essential. (Only one attribute can be provided, for example, as an identifier for an object that is being transferred as par
20、t of a table of contents of a folder or search result, rather than as an object in its own right.) Fields in parentheses are optional. However, unless lower-level expansions indicate otherwise, optional fields must be complete. If an optional field is included, all required subfields must also be pr
21、esent. Those fields that are present must be in the order shown, except as specified by the accompanying text. Fields followed by an ellipsis can occur more than once in a structure. 12. 8.8.6 System-specific private data A field called Privare Data (PRIV) is optional in every occurrence in the data
22、stream. (The field is also a part of each CIU and the datastream as a whole). This field provides a place for the generating system (standard platform-dependent code or application code by way of a user exit or other mechanism) to include non-standard data that is not built into the datastream. The
23、content of this field (after the ID and length) can be structured according to any needs of an enterprise for private information. Application code at the two ends of the transfer can use this mechanism to communicate information that goes beyond the scope of the datastream definition, for example:
24、- to provide security-related parameters (this field is permitted at the start of each major element to assist in item-level access control) - to provide mappings between the conventions of two different applications - to provide parameters when the application in the two systems has augmented the c
25、ontents of the database or the relationships 12 Association for Information and Image Management International COPYRIGHT Association for Information & Imaging ManagementLicensed by Information Handling Services AIIM MSbO 96 H 1012348 0500923 b9b DIVISION ANSIAIIM MS60- 1996 Standard for the Electron
26、ic Folder Interchange Datastream is managed by manages MANAGER Annex A Ganes entity relationship diagram notation (Informative) - SALE (This annex is not a part of the American National Standard for Information and Image Management. Standard - Electronic Folder Interchange Datastream MS60- 1996.) in
27、volves * SALEITEM is part of Figure A4, Ganes entity relationship diagram notation, illustrates the relationship between divisions and managers, sales and sale items, suppliers and products, and employees and projects. SUPPLIER supplies * * is supplied by PRODUCT I I l I 1: 1 - Each Division is mana
28、ged by one. and only one. Manager. Each Manager manages one, and only one. Division. 1 :Many - Each Sale involves one or more Sale Items. Each Sale Item is a part of only one Sale. Many: Many - Each Supplier supplies one or more Products. Each Product is supplied by one or more Suppliers. Other nota
29、tions - An Employee may be assigned to one or more Prqjects. A Project is (must be) staffed by one or more Employees. From Rapid System Development, Using Structured Techniques and Relational Technology, Prentice Hall, 1989. Chris Gane Figure Al - Ganes entity relationship diagram notation 13 Associ
30、ation for Information and Image Management International COPYRIGHT Association for Information & Imaging ManagementLicensed by Information Handling Services AIIM MSbO %b 6 LOL2348 0500924 522 ANSVAIIM MS60- I996 Standard for the Electronic Folder Interchange Datastream Annex B ASN.l BER Notes (Infor
31、mative) (This annex is not a part of the American National Standard for Information and Image Management, Standard - Electronic Folder Interchange Datastream MS60- 1996.) B1 ASN.l data types The detailed definitions of Abstract Syntax Notation One (ASN.1) and its Basic Encoding Rules (BER) are conta
32、ined in ISOIEC 8824 and 8825. This appendix summarizes the definitions and representations of a subset of the ASN. data types and options that satisfy the current requirements of the FIA datastream. This appendix assumes a familiarity with the basic terminology of ASN. I and its BER, as described in
33、 B2, ASN.1 Basic Encoding Rules (BER) format. Note 1: ASN. uses the IS0 terminology “octet” rather than “byte” for the basic 8-bit entity. Each of these ASN. 1 data types is associated with a particular “Universal” class tag: 31.1 Boolean (UNIVERSAL 1) The content is always a one-byte primitive. A v
34、alue of zero represents “false.” Any non-zero value of the byte represents “true.” B1.2 Integer (UNIVERSAL 2) The content is a twos-complement integer, occupying one or more bytes. It is always primitive, and must not contain more bytes than necessary (that is, if it occupies two or more bytes, then
35、 the first nine bits must not be all zeroes nor all ones). B1.3 Octetstring (UNIVERSAL 4) A means of representing an integral number of bytes of data when the format has no special predefined (to ASN.1) significance (other than the order). When the content is primitive, it consists of zero or more b
36、ytes that contain the data itself with no added information and no padding. If desired (for example, for very long strings), the content can be treated as constructed and split into two or more pieces. In this case, each piece is preceded by its own ID/L fields and thus becomes its own triplet of ty
37、pe octetstring. The successive contents portions should be treated as if they had been concatenated as part of a single primitive string. (The length field of the overall composite octetstring includes the length of the inserted IDL fields.) B1.4 Object identifier (UNIVERSAL 6) A specially encoded s
38、equence of integers that corresponds to an IS0 convention for uniquely identifying objects, definitions, and other information. Note 2: This type is not supported in this version of the datastream. B1.5 Enumerated (UNIVERSAL 10) The contents are as defined for the integer type, representing the sele
39、cted integer. B1.6 Sequence and sequence-of (UNIVERSAL 16) The content is always constructed. It consists of zero or more triplets, each corresponding to an element of the sequence. The order of these elements is significant. 14 Association for Information and Image Management International COPYRIGH
40、T Association for Information & Imaging ManagementLicensed by Information Handling ServicesANSIIAIIM MS60- 1996 Standard for the Electronic Folder Interchange Datastream ID (1 byte) B1.7 The content is always constructed. It consists of zero or more triplets, each corresponding to an element of the
41、set. The order of these elements is not significant. See notes 3 and 4. Notes: 3. Set and set-of (UNIVERSAL 17) The FIA datastream uses “simplicity tagging” wherever possible. Thus the universal class tags shown previously are usually replaced in the datastream by some application class or context-s
42、pecific class tag (but the content format remains as described here). L (1 byte) Content (L bytes) 4. In the ASN.1 BER all fields are “big-endian.” This means the order within a byte is always from the most significant bit to the least significant bit. and the order within a multi-byte field is alwa
43、ys from most significant byte to least significant byte. ID (I byte) B2 ASN.l Basic Encoding Rules (BER) format 80 (I byte) Content (any length) (2 bytes of value O) content field: - the type of content - primitive content is atomic - constructed content consists of zero, one, or equivalent) - the c
44、lass of the tag assigned to the data. All tags are divided - universal (defined by ASN.1) more interior triplets (or into four classes: - private (reserved for use on an enterprise- specific basis) - application (global within a particular syntax definition, as identified by a specific standard or p
45、rivate agreement. such as the set of Application tags defined for this FIA datastream) - context-specific (used to provide a locally unambiguous identification within a more complex construct and represented by a null or empty class designator in the formal syntax) - the number of the tag assigned t
46、o the data 15 Association for Information and Image Management International COPYRIGHT Association for Information & Imaging ManagementLicensed by Information Handling Services AIIM MSb0 96 1 101i2346 0500926 3T5 H Class (2 bits) ANSUAIIM MS60- 1996 Standard for the Electronic Folder Interchange Dat
47、astream P/C (i bit) Number (5 bits) The combination of class and number defines a tag, which is the unique identifier of a data field that provides its meaning and syntactic structure (in the context identified by its class). where the Class bits are encoded as follows: O0 = Universal O1 = Applicati
48、on 10 = Context-specific 11 = Private and the P/C bit is encoded as follows: O = Primitive 1 = Constructed The length field gives the length in bytes of the associated content portion. It does NOT include the length of the preceding identifier. nor of the length field itself. Not counting the indefi
49、nite form described previously, two options for the length field are as follows: - Short form: Lengths between O (no content part) and 127 bytes, inclusive, can be represented by the corresponding integer as a one-byte length field. - Long form: Any length (including O) can be represented by a byte containing hexadecimal 8n followed by n bytes containing the length (in bytes) as an unsigned integer. Thus, this length field occupies n+l bytes (two or more) and can be longer than the minimum necessary to hold the needed integer. 16 Association for Informat
