Hi guys,
I will not be able to be there on Tuesday due to an internal Marsh meeting.
I do have some things to say about the date time, and have included them in
this email. I have already sent them to Gunther and Mike as part of the
document...
COMMENTS FROM ALAN STITZER
It is difficult to see from this document what you are recommending. I
think the options are all very well thought. ACORD is compliant (right
now) with ISO 8601 format. We did not use 8601 for duration because of
the complexity of what had to go into it.
When I submitted the ACORD "DURATION" entity from the DTD I was
expecting to see something like that come out of your exercise. What I
would like to see is something like this (and I am not an XSD guru by
any stretch of the imagination) so I am just going to put in an XML
stream of what I thought I was going to see:
For instance (Don't worry about the tag names??) The tag <ContractTerm>
would be made up of a collection of other elements, start and end dates,
start and end times, an indicator for local time, a duration period, and
a recurring details section.
<ContractTerm>
<StartTime>
<EndTime>
<StartDt>
<EndDt>
<Description>
<LocalStandardTimeInd>
The basic information is start and end dates, times, a description (if
necessary ? to describe an event, for instance this is to take effect as
soon as the shuttle clears earth's atmosphere), and an indicator to show
that these same terms apply to the enterprise's entire operation across
the globe at the given date/time in that area.
<DurationPeriod>
<NumUnits>
<UnitMeasurement>
</DurationPeriod>
The duration period is used to express, say, 30 days, although 30 days
means nothing without something in the description. We find that in
insurance when a specific start and end time would not be possible to
pin down.
<RecurringDetails>
<NumUnits>
<UnitMeasurement>
<FrequencyCd>
</RecurringDetails>
The recurring details would take into account every nth "something".
You would not need a start/end date/time within that because it already
exists as basic information ? so all you have to specify is a number of
units, a unit of measurement, and a frequency.
</ContractTerm>
ajs
<<< Memo from @Internet on 03 July, 2002,
08:46:44 PM Wednesday >>>
@Internet on 3 Jul 2002, 20:46 Wednesday
To: Alan Stitzer
cc:
Subject: Re: [ubl-lcsc] Action Items for this week
it may be useful to post your comments to the discussion list so we can
debate them prior to next tuesday.
wrote:
