15. 相互運用性 - interoperability
2015-12-10 オープン技術特論
山口琢
システムの相互運用性
生活・仕事
モデル
システム
モデル
システム
The capability to communicate, execute programs, or
transfer data among various functional units in a manner
that requires the user to have little or no knowledge of
the unique characteristics of those units
ISO/IEC 2382-01,
Information Technology Vocabulary, Fundamental Terms,
via Wikipedia
15
16. 相互運用性 - interoperability
2015-12-10 オープン技術特論
山口琢
システムの相互運用性
生活・仕事
モデル
システム
モデル
システム
The capability
能力・性能
to communicate, execute programs, or transfer data
通信する、プログラムを実行する、データを送る
among various functional units
さまざまな機能的な単位の間で
in a manner
方法で
that requires the user to have little or no knowledge
利用者に知識を求めない
of the unique characteristics of those units
それら単位に固有の特徴に関する
ISO/IEC 2382-01,
Information Technology Vocabulary, Fundamental Terms
16
45. iCalendar: 3.3.5. Date-Time
19980118T230000
DATE-TIME values of this type are said to be "floating" and are not bound to
any time zone in particular. They are used to represent the same hour, minute,
and second value regardless of which time zone is currently being observed.
For example, an event can be defined that indicates that an individual will be
busy from 11:00 AM to 1:00 PM every day, no matter which time zone the
person is in. In these cases, a local time can be specified. The recipient of an
iCalendar object with a property value consisting of a local time, without any
relative time zone information, SHOULD interpret the value as being fixed to
whatever time zone the "ATTENDEE" is in at any given moment. This means
that two "Attendees", in different time zones, receiving the same event
definition as a floating time, may be participating in the event at different actual
times. Floating time SHOULD only be used where that is the reasonable
behavior.
2015-12-10 オープン技術特論 山口琢
45