Warning:
This wiki has been archived and is now read-only.
PIL OWL Ontology Meeting 2012-07-23
From Provenance WG Wiki
Contents
Meeting Information
prov-wg - Modeling Task Force - OWL group telecon
- previous meeting
- date: 2012-07-23
- time: 12pm ET, 5pm GMT
- via Zakim Bridge +1.617.761.6200, conference 695 ("OWL")
- wiki page: http://www.w3.org/2011/prov/wiki/PIL_OWL_Ontology_Meeting_2012-07-23
- titan page: http://titanpad.com/9q4ZpS5kwu
- next meeting
Attendees
- Tim
- Khalid
- Daniel
- Stephan
Regrets:
- Stian
- David
- Satya
- Jun
Agenda
For the issues that you are assigned:
- describe the original concern
- describe any perspectives already expressed
- recommend next step, or propose a solution
Rescheduling the regular call
- Jun cannot make 5pm beginning in Sept. (4pm or 4:30pm would be better)
- Daniel is in California for the next few months.
So I think our timezone span is back to:
- -8 (Daniel)
- -7 (Stephan)
- -5 (Tim/Satya)
- 0 (Stian, Khalid, Jun, David)
ISSUES
Satya (Khalid standing in)
- we need blog post by 24 July
- just a quick update - what's changed from the
- last version. What's important in the ontology (e.g. the sectioning).
- I guess a bit about using it in applications.
- It doesn't have to be long maybe 2 paragraphs.
- https://docs.google.com/document/d/170_NF7mOHg4PlJ_tK8gytRJA2K2AcCOOEo_Z5GycvpE/edit
- Khalid: we have something that is okay and can be released.
- ... the w3c process.
- Tim: TODO David, Daniel, Stephan to read and give comments to Khalid
- ... Khalid will hand off to Paul.
David
- New diagrams http://dvcs.w3.org/hg/prov/file/tip/ontology/diagram-history/2012-07-09-david
- David did expanded terms, too. (notes in July 11, 2012 8:57:25 AM EDT email)
- http://dvcs.w3.org/hg/prov/file/tip/ontology/diagram-history/2012-07-09-david
- http://dvcs.w3.org/hg/prov/file/9f0b37eaf74e/ontology/diagram-history/2012-07-09-david/expanded-terms-example-all.svg
- activity used something that was quoted from something that the activity generated
- :quote1, :publicationActivity1123
- Qual section: A diagram was also requested for after the first paragraph of 3.3, with another comment later regarding the same section focusing on rearranging the example/text; the raised editorial says "not sure how to resolve this" - I guess we should hold off doing a diagram until a decision is made?
- Tim only got the first one in for LC.
- TODO: David to review the comments on the daigram/ ordering in qualificatoin section narrative and provide recommendation to group.
- David did expanded terms, too. (notes in July 11, 2012 8:57:25 AM EDT email)
Jun
(TL: I think everything in Jun's section that does NOT have a TODO should be dropped, since they are settled.)
- http://www.w3.org/2011/prov/track/issues/442 (what prov.owl terms can we omit in prov.html)
- https://docs.google.com/spreadsheet/ccc?key=0Ahxrga9AQHb_dDBQV3ZyWEN6S2RXcWVZMzI0S0xKeEE
- focus is on sections 3.1 - 3.3
- Jun: I reviewed all comments related to my reviews. The only outstanding terms on my side that I can see include:
- line 51 and 52, about influenced and influencer. I don't think we need actual examples for these two in section 3.2/3.3, do we?
- TL: I see no need to. Let's let it as is.
- Line 54, about mentionOf, comments to be processed by TimL TODO
- line 51 and 52, about influenced and influencer. I don't think we need actual examples for these two in section 3.2/3.3, do we?
- I also processed outstanding lines from others listed below
- TODO Stephan close comment by "Done" in col D:
- Line 24, about Plan
- Line 28, about Role
- Satya
- Line 30, about source
- seems to be settled.
- TODO Stephan close comment by "Done" in col D:
- http://www.w3.org/2011/prov/track/issues/382 qualification section feedback
- 4th column of qualification tables is hard to understand (we're up to 6 now!)
- Jun: I don't have the same old problem with using terms from the old 4th column terms, the now 5th column. But I see this issue is being expanded to a totally separate discussion now. I suggest if we do keep this new discussion theme going on, we should move it out of this context.
- http://aquarius.tw.rpi.edu/prov-wg/prov-o#description-qualified-terms
- Stephan: mouse over on the header (within style guidlines)
- TODO: what text to put into span title hover text that is there now?
- We can also do slightly nicer mouseover using CSS :hover http://www.w3schools.com/cssref/sel_hover.asp http://www.scientificpsychic.com/etc/css-mouseover.html
- extra paragraph for "now that we've qualified, what can we do?" (right at the beginning of the section, after or before the cheat-sheet tables)
- Jun: I think this has been covered by the currently expanded explanations right at the beginning of the section, by giving an example of how association can be qualified.
- activity, entity, agent, dictionary point to the objects being qualified
- hadActivity, hadGeneration, hadUsage hadPlan and hadRole provide the additional statements about the can-be-qualifeid properties, via their corresponding qualify classes or an involvement class
- TODO: Tim to make sure all are covered.
- 4th column of qualification tables is hard to understand (we're up to 6 now!)
Stian
- http://www.w3.org/2011/prov/track/issues/349 [good] turtle examples in cross ref
- do the examples "fit the ontology"? TODO (CODE)
- David, Stian, Stephan, Tim will work on this as we go (no clear leader)
- Stian's report
- Just use something that makes sense for that example. Like http://example.org/car http://example.org/customer http://example.org/alice http://example.org/workingAtHome
- Stian: a bit long, log book on what he did. Lots of considerations came up.
- ... example called the same (e1, e1, e1).
- ... spelling mistakes
- TODO: do the renaming to avoid the collisions. TODO: Stian to coordinate the renaming, assign them, coordinate.
- TODO: do as a whole, then backtrack to the examples.
- work request: http://www.w3.org/mid/CAPRnXt=+Ownsy-Sw6Z3pUrmbHCz=wXaOCECuiN0txWtn0xPrJA@mail.gmail.com
Stephan
- http://www.w3.org/2011/prov/track/issues/456 superclass in domain union
- Tim: TODO make the change, since no team objections.
- Stephan: add a justifications for any changes after LC
- http://www.w3.org/2011/prov/track/issues/457 domain mismatch
- change has been made in ProvenanceOntology.owl and staged LC files. This issue can be closed
- prov:wasInfluencedBy rdfs:domain prov:Entity .
- prov:wasAssociatedWith rdfs:domain prov:Agent ; rdfs:subPropertyOf prov:wasInfluencedBy .
- The above was an error.
- TODO: Tim to rerun the editors draft and TODO stephan to review
Khalid
- highlighting focus terms in prov-o examples
- with strong HTML elements
- Khalid: we should see if the group wants / does not want it.
- http://aquarius.tw.rpi.edu/prov-wg/prov-o#AgentInfluence
- TODO: Khalid to redo markup example from LC draft.
- we can use <code instead of <pre, which will allow us to markup the code content
- for example, the following code markup uses strong and style coloring
<code>var faq = <strong style="color:blue;">new</strong> Array(3)</code>
Daniel
- Work through review of prov-o july 3 2012 for last call (33 RAISED feedback points left of 100+)
- The only 2 things that I have detected is that in section 3.2 there is no example for mention and asInBundle (even though the example has bundles) and there is no wasInfluencedBy in the example (it could be easily added as an inference of wasAttributedTo).
- The latest version is always http://aquarius.tw.rpi.edu/prov-wg/prov-o
- Rename chart maker, make consistent.
- - I wonder if a better example organization instead of ex:chartgen would be "National Newspaper".
- - I think the team was already looking at the consistency of the examples. It was Chart Generators and now in this example it's Chart Generators Inc.
- it was suggested for prov-dm that examples should be described in past tense. It should be done here too.
Tim
Someone please take
- http://www.w3.org/2011/prov/track/issues/461 (Graham's printed cross reference)
- http://www.w3.org/2011/prov/track/issues/455 (Source vs. PrimarySource)
- Stephan TODO look at the thread.
- How would you encode http://aquarius.tw.rpi.edu/prov-wg/prov-o#acknowledgements in prov-o? In RDFa?
Mine
- http://aquarius.tw.rpi.edu/prov-wg/prov-o#Derivation should seeAlso Source, Revision, Quotation. (plus LC comment for others seeAlsos)
- Luc's scan
- http://www.w3.org/2011/prov/track/issues/336 pre-WD2 feedback
- These are editorial, and thus second priority before LC.
- prov:category and prov:component should be URIs, not literals (requires code, many filename dependencies across systems)
- http://aquarius.tw.rpi.edu/prov-wg/prov-o#description-starting-point-terms
- http://aquarius.tw.rpi.edu/prov-wg/prov-o#description-expanded-terms
- http://aquarius.tw.rpi.edu/prov-wg/prov-o#description-qualified-terms
- Tim asked Luc to rename the following:
- http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html#component1
- http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html#component2
- https://www.w3.org/2011/prov/track/issues/388 (tools and demos)
- https://www.w3.org/2011/prov/track/issues/389 extensions to prov-o