PIL OWL Ontology Meeting 2011-08-02
- 1 Meeting Information
- 2 Attendees
- 3 Background
- 4 Agenda
- 5 Discussions
- 5.1 Group organization
- 5.2 Wiki page
- 5.3 Missing relationship between generation/use/derivation and Time/Location
- 5.4 Roles
- 5.5 Arities (i.e., cardinalities)
- 5.6 HTML document
- 5.7 process execution
- 5.8 Generation
- 5.9 Diagrams
- 5.10 Entailments
- 5.11 References
- 5.12 Next meeting
- date: 2011-08-02
- time: 9am PT, 12 noon ET, 5pm UK
- via Skype conversation call - Satya hosting
- wiki page: http://www.w3.org/2011/prov/wiki/PIL_OWL_Ontology_Meeting_2011-08-02
- titanpad: http://titanpad.com/lExgp045YP
- next meeting
Tim: Jim McCusker is joining the group, but not in today's telecon
Reuse - time and location
Daniel: looking at OWL doc and html. Propose reusing wgs and owl time for Time and Location. James: use directly or recommend?
Time ontology has interval and instant.
TODO: Tim to dig up his owl time diagram.
TODO: refering from OWL class to the Conceptual Model. (e.g., why is "Time" in this ontology?)
Time: process execution and BOB
- Beginning of a process, end of a process
- use and generation
- derivation has temporal
Khalid: this class is abstract class and people instantiate or extend it with their vocab?
Daniel: list recommendations. We don't constrain them to use one.
Tim: keep it general, but elaborate with OWL time and WGS (which people can grab and use). (RESOLVED)
Daniel: we have PIL types, but will offer subclasses that people will use.
James: pil:Time but not saying anything about it, then saying "if you want, equiv it to dateTimeDescription".
James: two levels, 1) "there are times, there are locations." 2) concrete "wgs and owl time"
Satya: Reference and domain.
topic: elaborated and unelaborated ontologies vs. a single elaborated ontology.
- theoretical vs. practical application uses
Daniel: group agreed that we are NOT defining time or location.
Missing relationship between generation/use/derivation and Time/Location
Missing relationship between generation/use/derivation and Time/Location. (Daniel G)
pe_1 generated b_1 . pe_1 occuring_at_location loc_1 .
Daniel: do not rely on rules.
Daniel: modeling n-ary as classes makes it difficult to use inference.
Help avoid using owl:Classes:
Should these be pushed back to the conceptual model?
Roles are not represented yet
TODO: Daniel (to do): Role examples from Journalism scenario
Arities (i.e., cardinalities)
how many bobs are derived from another bob. how many bobs does a process
TODO: Khalid to try to find some cardinaltity constraints
How to get the HTML file? From the w3c repository.
RESOLVED: The wiki is the "starting point" and will be transitioned to the HTML document. RESOLVED: Things that don't make it to the HTML will be archived in the wiki page.
"continuous" interval of time.
Satya concerned about "it doesn't occupy the entire interval".
(did we address this?)
TODO: "role" - role of the generated BOB?
TODO: Tim to describe roles of input and params.
TODO: Tim to revisit his graphml output
TODO: we want diagrams in section 2 http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html#owl2-encoding-of-the-provenance-model
Satya: start by describing it in HTML, then move to OWL when we have clarity on how it should be modeled.
TODO: James add something to section 3 (entailments)
James: They might not belong in the ontology but in the semantics document. Luc mentioned we should know what we are expecting or not expecting with entailments.
Satya: RDFS/OWL entailments. Other stuff needs to be described in the entailments section (as rules?).
Q: why is "is" used in the relationships, and not "was"? -Tim
Monday. We'll figure out time over email. 9am California 12 noon 5pm UK