GB/T 32656-2016 in English
VALIDData format of the calendar and schedule
- Issued on:2016-04-25
- Implemented on:2016-11-01
- File Format:PDF
- Delivery:Via email within 5 business days
$359.00
| Standard No: | GB/T 32656-2016 |
| Document status: | VALID |
| Title in English: | Data format of the calendar and schedule |
| Title in Chinese: | 日历及日程数据格式 |
| Language: | English |
| File Format: | Electronic (PDF) |
| Delivery: | Via email within 5 business days |
| Issued on: | 2016-04-25 |
| Implemented on: | 2016-11-01 |
| ICS Classification: | 35.040-Character sets and information coding |
| Professional Classification: | GB-National Standard |
| Related Keywords: | schedule data format
data format standard time format structured data format schedule introduction standard overview gb/t |
| Related Topics: | calendar
calendar ultraviolet Mass Spectrometry Data Format Mass Spectrometry Data Format schedule number of days data grid Atmospheric daily data Egypt weekend product schedule GBT32656 GB/T 32656-2016 China’s M2 data over the years Data Format |
《GB/T 32656-2016日历及日程数据格式》由TC28(全国信息技术标准化技术委员会)归口,主管部门为国家标准化管理委员会。
Introduction
Standard Overview
GB/T 32656-2016 Calendar and Schedule Data Format is a national standard proposed by the National Information Technology Standardization Technical Committee, which specifies the structured data format of electronic calendar and schedule information. This standard uses XML as the basic data carrier and is applicable to the development of schedule management functions of various information systems.
Core structure analysis
| Structure part | Core elements | Function description |
|---|---|---|
| Header part | UID, VERSION, TZ, etc. | Contains basic information such as file metadata and time zone |
| Body part | TITLE, DT_PERIOD, CATEGORIES, etc. | Record specific schedule content and attributes |
| Subfile part | SUBKEY | Supports nested schedule structure |
Key technical elements
1. Time representation specification
The ISO 8601 standard time format (YYYY-MM-DDThh:mm:ss) is used, and time zone identification (such as TZ="+08:00") is supported. The time period element DT_PERIOD defines the time range through the DT_START and DT_END attributes.
2. Repeating rules (RRULE)
Support five repeating modes:
- Daily rule: Starting with D, such as "D2#10" means repeating 10 times every 2 days
- Weekly rule: Starting with W, such as "W1MO,WE" means repeating every Monday and Wednesday
- Monthly rule: MP/MD type, such as "MP1+FR" means the first Friday of every month
- Yearly rule: YM/YD type, such as "YM6,7" means June and July every year
- Specific date: Starting with TD, you can specify an irregular date
Typical application scenarios
Meeting schedule example
<G_TODO> <TITLE>Quarterly Sales Meeting</TITLE> <DT_PERIOD DT_START="2023-03-15T14:00:00" DT_END="2023-03-15T16:00:00">7200</DT_PERIOD> <CATEGORIES Name="Meeting">Sales Analysis</CATEGORIES> <RRULE>YM3#4</RRULE> <!-- Repeat 4 times each quarter--> <PARTICIPANT> <PERSON APPELLATION="Director" TEL="13800138000">Manager Zhang</PERSON> </PARTICIPANT> </G_TODO>
Standard Implementation Recommendations
- Character set support: The system must be compatible with the GB18030 character set to ensure correct processing of Chinese information
- Time zone processing: All time data should be associated with time zone information to avoid cross-time zone synchronization issues
- Extension mechanism: Custom field extension is implemented through the EXT element to maintain standard compatibility
- Status management: Standardize the use of STATUS elements (0-6) to track the schedule life cycle
Technology Evolution Analysis
This standard refers to the iCalendar (RFC 5545) international standard. The main innovations include:
- Add Chinese-specific elements such as the category naming of CATEGORIES
- Optimize repetition rule expressions to support local needs such as lunar calendar dates
- Define a standardized template mechanism (TEMPLATE) to improve applicability in professional fields such as medical care

Loading PDF document...
Error loading PDF. Please make sure the file is valid and try again.
We also recommend
-

GB/T 32912-2016 in English
Information technology - Traditional Mongolian words - Word form specification - Basic set
2016-08-29 -

GB/T 28448-2019 in English
Information security technology—Evaluation requirement for classified protection of cybersecurity
2019-05-10 -

GB/T 40413-2021 in English
Drafting rules for common identification codes of emergency logistics
2021-08-20 -

GB/T 21049-2022 in English
Han Xin code
2022-03-09 -

GB/T 34947-2017 in English
Information technology-Generic requirement for Chinese bi-spelling and tri-spelling pinyin inputting
2017-11-01 -

GB/T 36322-2018 in English
Information security technology-Cryptographic device application interface specifications
2018-06-07 -

GB/T 41205.1-2021 in English
Code and attribute description of emergency supplies—Part 1:Personal protective equipment
2021-12-31