Project

General

Profile

CIM Issues #4344

AbsoluteDateTime's 'value' attribute, which is of type Time

Added by Herbert Falk over 2 years ago.

Status:
Closed
Priority:
Normal
Author/Contact Info:
Dan Martin
Base Release:
Solution to be Applied To:
Solution Version:
CIM10
Solution Applied By:
Completion Date:
CIM Keywords:
Breaking Change:
No
Breaking Change Description:
CIM Impacted Groups:
WG13
Requestor:
Standard(s):
Version:
Clause:
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
CIM10
Origination Date:
06/14/2004
Origination ID:
192
Originally Assigned To:

Description

AbsoluteDateTime's 'value' attribute, which is of type TimeStamp. TimeStamp has a single attribute named 'value'. The effect is that when you try to fully resolve the inherited field you end up with something like 'ActivityRecord.lastModifiedDate.value.value'. I can see where this will lead to a lot of confusion from a message mapping perspective. Can you give me some history regarding the purpose of the TimeStamp class with a single 'value' attribute and its intended use in the model?

Proposed Solution

[Terrence Saxton] Dan, it looks to me like we have an issue that needs resolution. A while back, we created AbsoluteDateTime to be the data type to be used for the attribute timeStamp in the MeasurementValue and Control classes. So I think when we did that, we should have done the following: 1) Eliminated TimeStamp as a data type from the Domain package. 2) Changed the value attribute of AbsoluteDateTime to the primitive string.

Decision

6/22/04: WG13: Agree to proposed change. Not correct in current UML model. 040505: Deferred to parking lot on Time issues.
6-Sept-2006: AbsoluteDateTime is now a string conforming to ISO 8601. Issue closed.

No data to display

Also available in: Atom PDF