OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

legalruleml message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [legalruleml] Time Instants or Time Points

I agree on the fact that LegalRuleML should be neutral respect any temporal ontology and any temporal logic model (linear, discrete, intervals, events, point, hybrid, modal, defeasible, etc.).

I understand also that the method proposed provides more flexibility.
I am ok with the example.

  <ruleml:Time key="t1"> <ruleml:Data xsi:type="xs:dateTime">2012-07-21T00:00:00Z</ruleml:Data> </ruleml:Time>
  <ruleml:Time key="t2"> <ruleml:Data xsi:type="xs:date">2012-07-21</ruleml:Data> </ruleml:Time>

However I would like to share with you some comments/cases/examples before to take a final decision:

1. Personally I'd prefer TimeInstant because in the legal domain "Instant" is more close to the domain vocabulary: instant of the crime, instant of the publication into the gazette, instant of creation of work (IPR), instant of the signature, etc.

2. my major concern is not on the terminology, but on the definition of "date" as interval of 24 hours.

CASE A. From legal point of view often a "date" embedded more information rather than a time or an interval of 24hr.
These information are derived by the nature of the date of the nature of the event.
E.g. for the enter into force the date is just a starting point of an interval with unlimited duration [date, infinite [
The date of abrogation of the same act, stops the interval of in "enforceability".
"On the 1st of April this year, the new Consumer Protection Act comes into effect."

There are implicit rules linked to the duration of the "dates" in several legal circumstances (e.g. if the date is a festive date, it is shifted to the next labour date; if it is the date of publication, its "validity" starts after the end of the day before, if it is a date of notification it starts from the ordinance of the judge, etc.) that are embedded in the legal temporal concept linked to the date.

CASE B. Another usage of the date in law, is for indicating a deadline for a duty: "The consumer must present the application request within 31/12/2012 at 5.00pm".

CASE C. Interval of dates [date1, date2] explicitly indicated in the legal text.

CASE D. Finally the date could be also used for indicating an interval of 24 hr. "Order to suspend the traffic at 20 October 2012."

3. some time the enter into force is linked to the date of publication in the Official Journal and more and more it is important to fix the exact time: 2012-07-21T09:032:00Z. Especially if the Official Journal is distributed on-line with digital signature (fixed with the timestamp)

Article 2
This Regulation shall enter into force on the date of its publication in the Official Journal of the European Union.

Section 89
This Constitutional Act comes into force immediately.

4. Duration. I would like to see how to model this sentence in LegalRuleML.
Article 12. Law in force
The current act shall be in force after 6 months since its publication.
(date of publication is known, e.g. 2012-10-10)

5. Sunset clauses.
I would like to see how to model this sentence in LegalRuleML.
This Act ceases to be in force after 30 June 2012.
This Act shall cease to have effect on December 31, 2005.
In this case the endPoint date means that the Act is repealed after the midnight of the 30 June 2012/31 December 2005.


Il 18/10/2012 01:01, Tara Athan ha scritto:
There is a relatively recent date-time ontology published by OMG (http://www.nist.gov/customcf/get_pdf.cfm?pub_id=911074) that addresses time scale granularity and also solves the problem of duration (is 1 month greater, equal or less than 30 days?)

While LegalRuleML is not supposed to be dependent on any particular ontology, this work does provide a useful conceptualization that allows certain intervals of time to be specified with a single datum. For example the date 2012-10-12 corresponds to a particular interval of time which can be specialized to a particular 24 hr interval when a timezone is added. This general concept of a point on a time scale with a particular granularity is called "time point". It is more general than a "point in time" or "time instant", but could include that concept if the time scale is continuous.

I proposed that we adopt this terminology, (but not the ontology) by referring to a collection of <ruleml:Time> elements as <lrml:TimePoints>

This also avoids the unfortunate plural "Times", which could be confused with multiplication or repitition, while retaining generality regarding the granularity, if any, of the time scale.


  <ruleml:Time key="t1"> <ruleml:Data xsi:type="xs:dateTime">2012-07-21T00:00:00Z</ruleml:Data> </ruleml:Time>
  <ruleml:Time key="t2"> <ruleml:Data xsi:type="xs:date">2012-07-21</ruleml:Data> </ruleml:Time>


Associate professor of Legal Informatics 
School of Law
Alma Mater Studiorum Università di Bologna 
C.I.R.S.F.I.D. http://www.cirsfid.unibo.it/ 
Palazzo Dal Monte Gaudenzi - Via Galliera, 3 
I - 40121 BOLOGNA (ITALY) 
Tel +39 051 277217 
Fax +39 051 260782 
E-mail  monica.palmirani@unibo.it 

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]