- From: Little, Chris <chris.little@metoffice.gov.uk>
- Date: Fri, 5 May 2017 15:47:23 +0000
- To: VAGLIANO IACOPO <d034466@polito.it>, "public-sdw-comments@w3.org" <public-sdw-comments@w3.org>
- CC: "Simon.Cox@csiro.au" <Simon.Cox@csiro.au>
Dear Iacopo, Thank you for this even more useful information, confirming backward compatibility. Best of luck for a successful defence/viva voce. Chris > -----Original Message----- > From: VAGLIANO IACOPO [mailto:d034466@polito.it] > Sent: Thursday, May 04, 2017 5:57 PM > To: Little, Chris; public-sdw-comments@w3.org > Cc: Simon.Cox@csiro.au > Subject: Re: OWL Time Ontology update > > Dear Chris, > > I am sorry for the delay in answering, I am preparing my PhD defense. > Thank you for your feedback and your interest. > > In my case, the changing should not have any impact. I have extended > time:ProperInterval for some classes I have introduced, while for > common time parameters as year, month, etc. I am referring to > time:Interval withouth any assumpion, thus the change should be > transparent. > > About the relaxed constraints on some properties, I don't see any > adverse consequences in the main application scenarios I had in mind. > However, my view is limited since I focus on recommender systems, and I > am not an expert ontology designer. > > Best regards, > > Iacopo > > > On Thu, 13 Apr 2017 09:00:45 +0000 > "Little, Chris" <chris.little@metoffice.gov.uk> wrote: > > Dear Iacopo, > > > > Thank you for this very useful information. > > > > We will not extend the OWL Time ontology because it has a small, > >tight, scope and there are so many extension that people desire. > > > > Please bear in mind that one of the purposes of the revision of the > >Ontology was to allow and support extensions including to non- > Gregorian > >calendars. > > > > Is your re-use and extension work affected by the deprecated > elements? > > (time:DateTimeInterval - use time:ProperInterval instead, > > time:Year - replaced by time:unitYear, > > time:January - replaced by greg:January) > > > > If modification is necessary, is it straightforward to modify your > >extensions to work correctly? > > > > Practices in ontology engineering have evolved since the original > 2006 > >version of the ontology. One concern is the use of global constraints > >on properties (domain, range) versus local constraints > >(owl:Restriction). The revised ontology relaxes the constraints on > >some properties from the original ontology, and we would be interested > >in hearing if there are any adverse consequences. > >(time:hasBeginning, time:hasEnd, > >time:hasDurationDescription) > > > > We look forward to your response with interest. > > > > Best wishes, Chris > > > > > > Chris Little > > Chair, OGC Temporal Domain Working Group > > > > IT Fellow - Operational Infrastructures Met Office FitzRoy Road > >Exeter Devon EX1 3PB United Kingdom > > Tel: +44(0)1392 886278 Fax: +44(0)1392 885681 Mobile: > >+44(0)7753 880514 > > E-mail: chris.little@metoffice.gov.uk http://www.metoffice.gov.uk > > > > I am normally at work Tuesday, Wednesday and Thursday each week > > > > > > > > > > > >> -----Original Message----- > >> From: VAGLIANO IACOPO [mailto:d034466@polito.it] > >> Sent: Monday, April 10, 2017 9:45 AM > >> To: public-sdw-comments@w3.org > >> Subject: OWL Time Ontology update > >> > >> Dear all, > >> > >> I reused and extended the Time Ontology in the Recommender System > >>Context > >> (RSCtx) > >> ontology [1, 2]. In my use case, it was useful also to have some > >>"symbolic" > >> time such us the part > >> of the day (morning, afternoon, etc.) or if a day is a weekend or > >>weekday. > >> Additionally, > >> the season could also be of interest. These concepts may also be > >>useful in other scenarios. > >> In [2] the use of RSCtx is described. > >> > >> Best regards, > >> > >> Iacopo Vagliano > >> > >> [1] http://softeng.polito.it/rsctx/ > >> [2] https://fedcsis.org/proceedings/2016/pliks/428.pdf > >> > >> > >> -- > >> Iacopo Vagliano > >> Ph.D. Student > >> > >> Dip. Automatica e Informatica > >> Politecnico di Torino > >> Corso Duca degli Abruzzi, 24 > >> 10129 Torino, ITALY > >> > >> Phone: +39 0110907087 > >> Web: http://softeng.polito.it/vagliano/ > >> -- > >> > > > > -- > Iacopo Vagliano > Ph.D. Student > > Dip. Automatica e Informatica > Politecnico di Torino > Corso Duca degli Abruzzi, 24 > 10129 Torino, ITALY > > Phone: +39 0110907087 > Web: http://softeng.polito.it/vagliano/ > --
Received on Friday, 5 May 2017 15:48:01 UTC