- From: Rob Warren <warren@muninn-project.org>
- Date: Tue, 12 Nov 2013 13:28:33 -0500
- To: public-gld-comments@w3.org
- Cc: Dave Reynolds <dave.e.reynolds@gmail.com>
David, I plan to replace a number of my own homegrown organization ontology constructs with the organization ontology. I really appreciate the binary and n'ary relationships to deal with relationships at different levels of granularity. I'd also like to support the use of the Time Ontology because of its support for odd time periods that everyone can relate to but which standardize poorly to the calendar. A typical example is the financial year of a corporation which will differ in actual calendar dates across corporations. However, people are still comfortable referencing third quarter, 2012 or the 2012 financial year without knowing the underlying calendar dates. It has proven to be particularly useful in dealing with time periods that are poorly defined, be it with missing or invalid information. The use of the time ontology, as opposed to a data type, enables me to separate the label of the period (eg: February 31) with the actual date (somewhere between February / March). The other example is someone who joins the organization in 2012. When in 2012 is ambiguous, but there currently no datatype that can record this properly besides Time Owl. best, rhw
Received on Tuesday, 12 November 2013 18:31:49 UTC