This form contains a series of questions that need to be answered. As you go about answering the questions, please keep the following things in mind:

• While it is not required that each question be answered at this time, all questions must have answers before the response is submitted to The Open Group for review and publication.
• Press the "Save" button at any time to save work in progress. Once the work has been saved, there is the option to continue editing if required.
• Many questions have instructions to assist in development of answers. They are marked with the indicator. Please look at the instructions carefully.
• Although HTML markup can be included in answers, this is not recommended apart from basic tags such as <p> and <br>, since incorrect markup could effect the format of other items in the document.
• Questions on this system should be addressed to the Conformance Statement manager at The Open Group.

Enter the name of the Organization that produced the implementation and the name of the author of the Conformance Statement.

1. Calendaring and Scheduling

Product Information

Environment Specification

Answer the questions for each binary-compatible family. Alternately, provide the answers in the Appendix at the end of this document.

	Testing Environment	Binary-compatible Family	Portability Environment	Indicator of Compliance	Compliance Details
			None.	None.	None.
			None.	None.	None.
			None.	None.	None.
			None.	None.	None.
			None.	None.	None.

Temporary Waivers

1.1 Basic Data Types

Question 1: How are the basic data types defined?

Response

Data Type	Definition
CSA_sint16
CSA_sint32
CSA_uint8
CSA_uint16
CSA_uint32

Rationale

Some of the abstract data types are defined in terms of intermediate or basic data types whose precise definitions in C are system-defined.

Reference

X/Open CAE Specification, Calendaring and Scheduling API (XCS), Section 3.1, Basic Data Types.

1.2 Users

Question 2: What optional user types are supported?

Response

User Type	Supported
CSA_TYPE_GROUP	Yes   No
CSA_TYPE_RESOURCE	Yes   No

Rationale

The user can either be an individual, CSA_TYPE_INDIVIDUAL, or a group, CSA_TYPE_GROUP, or a resource, CSA_TYPE_RESOURCE. Support for user types of GROUP and RESOURCE is optional.

Reference

X/Open CAE Specification, Calendaring and Scheduling API (XCS), Chapter 3, Data Structures, Calendar User.

Question 3: What calendar address formats are supported?

Response

Rationale

The CSA_calendar_user data structure has a calendar_address field that contains the address that is acceptable to the underlying calendaring service for the calendar associated with the user. The format of the address is not defined by the Calendaring and Scheduling API specification.

Reference

X/Open CAE Specification, Calendaring and Scheduling API (XCS), Chapter 3, Data Structures, Calendar User.

1.3 Calendar Attributes

Question 4: What optional calendar attributes are supported?

Response

Attribute	Supported
Calendar Size	Yes   No
Character Set	Yes   No
Country	Yes   No
Date Created	Yes   No
Language	Yes   No
Number Entrie	Yes   No
Work Schedule	Yes   No

Rationale

Support for each of the above attributes is optional.

Reference

X/Open CAE Specification, Calendaring and Scheduling API (XCS), Section 3.3, Calendar Attributes, Calendar Size, Character Set, Country, Date Created, Language, Number Entries and Work Schedule.

1.4 Entry Attributes

1.4.1 Optional Entry Attributes

Question 5: What optional entry attributes are supported?

Response

Attribute	Supported
Attendee List	Yes   No
Audio Reminder	Yes   No
Date Completed	Yes   No
Date Created	Yes   No
Description	Yes   No
Due Date	Yes   No
End Date	Yes   No
Exception Dates	Yes   No
Exception Rule	Yes   No
Flashing Reminder	Yes   No
Last Update	Yes   No
Mail Reminder	Yes   No
Number Recurrences	Yes   No
Popup Reminder	Yes   No
Priority	Yes   No
Recurring Dates	Yes   No
Recurrence Rule	Yes   No
Sequence Number	Yes   No
Sponsor	Yes   No
Status	Yes   No
Subtype	Yes   No
Time Transparency	Yes   No

Rationale

Support for each of the above attributes is optional.

Reference

X/Open CAE Specification, Calendaring and Scheduling API (XCS), Section 3.4, Entry Attributes, Attendee List, Audio Reminder, Date Completed, Date Created, Description, Due Date, End Date, Exception Dates, Exception Rule, Flashing Reminder, Last Update, Mail Reminder, Number Recurrences, Popup Reminder, Priority, Recurring Dates, Recurrence Rule, Sequence Number, Sponsor, Status, Subtype and Time Transparency.

1.4.2 Subtype Values

Question 6: If the Subtype entry attribute is supported, what are its values?

Response

Complete the table below, where Value is the identity of the value (e.g. CSA_SUBTYPE_CLASS) and Description is a brief description.



	Value	Description

Rationale

Support for the Subtype entry attribute is optional. Implementations may define their own set of values for this attribute.

Reference

X/Open CAE Specification, Calendaring and Scheduling API (XCS), Section 3.4, Entry Attributes, Subtype, and Chapter 4, Functional Interface, Add Event.

1.4.3 Status

Question 7: If the Status entry attribute is supported, what status values are supported?

Response

Status	Supported
CSA_STATUS_ACCEPTED	Yes   No
CSA_STATUS_NEEDS_ACTION	Yes   No
CSA_STATUS_SENT	Yes   No
CSA_STATUS_TENTATIVE	Yes   No
CSA_STATUS_CONFIRMED	Yes   No
CSA_STATUS_REJECTED	Yes   No
CSA_STATUS_COMPLETED	Yes   No
CSA_STATUS_DELEGATED	Yes   No

Rationale

Support for the status entry attribute is optional. Support for the listed attendee status values is optional.

Reference

X/Open CAE Specification, Calendaring and Scheduling API (XCS), Section 3.4, Entry Attributes, Status, and Chapter 4, Functional Interface, Add Event and Add Todo.

1.5 Character Sets

Question 8: What is the default character set?

Response

Rationale

To determine the character set of characters in a string, the CSA implementation looks at the session context. If there is no session context created before the call, the string will be interpreted using the implementation's default character set.

Reference

X/Open CAE Specification, Calendaring and Scheduling API (XCS), Chapter 3, Data Structures, String.

Question 9: If the Character Set calendar attribute is supported, what is its default value?

Response

Rationale

Support for the Character Set calendar attribute is optional. This attribute is defaultable to an implementation-specific value.

Reference

X/Open CAE Specification, Calendaring and Scheduling API (XCS), Section 3.3, Calendar Attributes, Character Set.

Question 10: If the Character Set calendar attribute is supported, what additional character sets are supported for it?

Response

	Identifier	Description	Value

Rationale

Support for the Character Set calendar attribute is optional. Implementations may provide support for other character sets in addition to those listed.

Reference

X/Open CAE Specification, Calendaring and Scheduling API (XCS), Section 3.3, Calendar Attributes, Character Set.

1.6 Functional Interface

1.6.1 Simple Calendaring and Scheduling Interface

Question 11: Is the simple calendaring and scheduling interface supported?

Response

Yes   No

Rationale

Support for the simple calendaring and scheduling interface is optional.

Reference

X/Open CAE Specification, Calendaring and Scheduling API (XCS), Chapter 4, Functional Interface, Add Event, Add Todo and Add Memo.

1.6.2 Attendee Priorities

Question 12: If the simple calendaring and scheduling API is supported, what attendee priorities are supported?

You need not fill in the table below if the answer to Question 11 (above) was "No."

Response

Attendee Priority	Supported
CSA_FOR_YOUR_INFORMATION	Yes   No
CSA_ATTENDANCE_REQUESTED	Yes   No
CSA_ATTENDANCE_REQUIRED	Yes   No
CSA_IMMEDIATE_RESPONSE	Yes   No

Rationale

Support for the listed attendee priority values is optional.

Reference

X/Open CAE Specification, Calendaring and Scheduling API (XCS), Chapter 4, Functional Interface, Add Event and Add Todo.

1.6.3 Optional Functions

Question 13: What optional functions are supported?

Response

Function	Supported
Administration:
Add Event	Yes   No
Add Memo	Yes   No
Add Todo	Yes   No
List Calendars	Yes   No
Look Up	Yes   No
Restore	Yes   No
Save	Yes   No
Calendar Management:
Add_Calendar	Yes   No
Call Callbacks	Yes   No
Delete Calendar	Yes   No
List Calendar Attributes	Yes   No
Read Calendar Attributes	Yes   No
Register Callback Functions	Yes   No
Unregister Callback Functions	Yes   No
Update Calendar Attributes	Yes   No
Entry Management:
Free Time Search	Yes   No
List Entry Sequence	Yes   No
Read Next Reminder	Yes   No

Rationale

Support for each of the above functions is optional.

Reference

X/Open CAE Specification, Calendaring and Scheduling API (XCS), Chapter 4, Functional Interface, Add Event, Add Memo, Add Todo, List Calendars, Look Up, Restore, Save, Add_Calendar, Call Callbacks, Delete Calendar, List Calendar Attributes, Read Calendar Attributes, Register Callback Functions, Unregister Callback Functions, Update Calendar Attributes, Free Time Search, List Entry Sequence and Read Next Reminder.

1.7 Common Extensions

Question 14: What common extensions are supported?

Response

Extension	Description	Supported
CSA_X_COM_SUPPORT_EXT	Query extensions supported	Yes   No
CSA_X_UI_ID_EXT	User interface	Yes   No
CSA_X_XT_APP_CONTEXT_EXT	Xt application context	Yes   No

Rationale

The Calendaring and Scheduling API common extension set contains those function and data extensions that are common to most calendaring and scheduling services, but are not in the base specification for various reasons.

Reference

X/Open CAE Specification, Calendaring and Scheduling API (XCS), Section 6.2, Common Extension Set.

1.8 Extended Recurrence Rule Grammar

Question 15: Is the extended recurrence rule grammar supported for recurrence rules?

Response

Yes   No

Rationale

The extended recurrence rule grammar may be useful to implementations wishing to extend the capability of the basic recurrence rule grammar defined in the Calendaring and Scheduling API specification. It is equally applicable to extended support of the exception rules for repeating events.

Reference

X/Open CAE Specification, Calendaring and Scheduling API (XCS), Chapter 8, Extended Recurrence Rule Grammar.

Question 16: Is the extended recurrence rule grammar supported for exception rules?

Response

Yes   No

Rationale

The extended recurrence rule grammar may be useful to implementations wishing to extend the capability of the basic recurrence rule grammar defined in the Calendaring and Scheduling API specification. It is equally applicable to extended support of the exception rules for repeating events.

Reference

X/Open CAE Specification, Calendaring and Scheduling API (XCS), Chapter 8, Extended Recurrence Rule Grammar.

2. Appendix

Copyright © 
All rights reserved.

3. Change History