https://wiki.esipfed.org/w/api.php?action=feedcontributions&user=65.52.109.149&feedformat=atomEarth Science Information Partners (ESIP) - User contributions [en]2024-03-28T14:12:00ZUser contributionsMediaWiki 1.35.14https://wiki.esipfed.org/w/index.php?title=July_8,_2009&diff=40351July 8, 20092012-07-30T12:46:10Z<p>65.52.109.149: Reverted edits by Carolbmeyer (talk) to last revision by Raskin</p>
<hr />
<div>{| width="96%"<br />
|- valign="top"<br />
== Wednesday ==<br />
| <small>[[Main_Page|Main ESIP page]] >> [[July_7-10%2C_2009%2C_ESIP_Federation_Meeting%2C_Santa_Barbara%2C_CA|Summer 09 Meeting Main Page]]</small><br />
<small>[[July_7%2C_2009|'''< July 7''']]</small><br />
| align="right"|<small>.</small><br />
<small>[[July_9%2C_2009|'''July 9 >''']]</small><br />
|}<br /><br />
{| width="95%" border="1" {{table}}<br />
|-<br />
| <b>Session Time</b>||<b>Session Details</b>||<b>Room</b><br />
|-<br />
| 7:30 - 12:00 ||Registration Desk Open||Loma Pelona<br />
|-<br />
| 9:00 - 9:15||Opening Welcome, James Frew, UCSB and ESIP Federation President ||Loma Pelona 1108<br />
|-<br />
| 9:15 - 10:15||Clifford Lynch, Executive Director, Coalition for Networked Information - ''Cyberinfrastructure Challenges: Data Curation, Data Reuse, and Data Integration'' ||Loma Pelona 1108<br />
|-<br />
| 10:15 - 10:30||Break ||Loma Pelona<br />
|-<br />
| 10:30 - 10:45 ||Falkenberg Award Presentation ||Loma Pelona 1108<br />
|-<br />
| 10:45 - 11:45||Jeff Dozier, Professor, Bren School, UCSB and Chief Scientist, WATERS Project Office - ''Living in the Water Environment - The WATERS Network's Plans and Status''||Loma Pelona 1108<br />
|-<br />
| 11:45 - 1:00||Lunch||Bren Courtyard<br />
|-<br />
| 12:00 - 5:30 || Registration Desk Re-Opens|| Bren Courtyard<br />
|-<br />
| 1:00 - 3:00||||<br />
|-<br />
| <center>Track 1</center>||[[Interagency_Data_Stewardship/LifeCycle/Jul2009MeetingPlans |Data Preservation and Stewardship]]||Colloquium <br />
|-<br />
| <center>Track 2</center>||[[Air_Quality_Community_Summer_2009_Meeting |Air Quality Community: Next Steps]]||Sycamore <br />
|-<br />
| <center>Track 3</center>||[[Teacher_Workshops |Teacher Workshops]]||GIS Lab<br />
|-<br />
| <center>Track 4</center>||[[Environmental_Decision_Making |Environmental Decision Making]]||Seminar<br />
|-<br />
| <center>Track 5</center>||Open||Oak <br />
|-<br />
| 3:00 - 3:30||Break with Poster Viewing||Bren Courtyard<br />
|-<br />
| 3:30 - 5:30||||<br />
|-<br />
| <center>Track 1</center>||[[Interagency_Data_Stewardship/LifeCycle/Jul2009MeetingPlans |Data Preservation and Stewardship]]||Colloquium <br />
|-<br />
| <center>Track 2</center>||[[Air_Quality_Community_Summer_2009_Meeting |Air Quality Community: Next Steps]]||Sycamore<br />
|-<br />
| <center>Track 3</center>||[[Teacher_Workshops |Teacher Workshops]]||GIS Lab<br />
|-<br />
| <center>Track 4</center>||[[Environmental_Decision_Making |Environmental Decision Making]]||Seminar <br />
|-<br />
| <center>Track 5</center>||Open||Oak <br />
|-<br />
| 5:30 - 7:00||Reception & Poster Session||Bren Courtyard<br />
|}</div>65.52.109.149https://wiki.esipfed.org/w/index.php?title=Module_Review_Criteria&diff=40345Module Review Criteria2012-07-29T03:03:15Z<p>65.52.109.149: Reverted edits by Rduerr (talk) to last revision by Nhoebelheinrich</p>
<hr />
<div>[http://wiki.esipfed.org/index.php/Data_Management_Short_Course Back to the main data management training page]<br />
<br />
[http://wiki.esipfed.org/index.php/AuthorsGuide Back to the Authors Guide page]<br />
<br />
[http://wiki.esipfed.org/index.php/Voiceover_Script On to the Voiceover Script page]<br />
<br />
== Module Review Criteria == <br />
<br />
<br />
=== 1. Module successfully addresses the Target Audience who is a Researcher / Scientist ''and'' ===<br />
<br />
* ''Is'' the data creator focused on the concepts within the data<br />
* ''Is'' the team member who just needs to know enough about data management to pass on the data to be stored / archived<br />
* ''Is'' the person who best knows the conceptual focus and context<br />
* ''Is'' the person motivated by use and re-use of the data (their own, if not others)<br />
* ''Is'' also a non-expert user of the data, geared to the undergraduate or general college level<br />
* ''Is'' considered to be part of the ESIP community<br />
* ''Is not'' the data manager who needs to receive, store, and archive the data and its context<br />
* ''Is not'' the data curator who must place this data within the collections of the data center<br />
* ''Is not'' the data librarian who helps others find, render, and use the data<br />
<br />
=== 2. Module has Conceptual Integrity ===<br />
<br />
* Concepts discussed match the overall topic <br />
* Concepts discussed fit where the topic is placed, <br />
** e.g., specifics of "Backing up your data" fit within "Managing your data" framework<br />
* Concepts discussed succinctly and accurately <br />
* Concepts covered completely within timeframe of 3 - 7 minutes for review or presentation <br />
* Links to other modules / topics are logical and accurate<br />
<br />
=== 3. Expression of concepts is appropriate and eye-catching ===<br />
* Concepts conveyed simply<br />
* Concepts described understandably<br />
* Illustrations and/or humor used effectively and liberally<br />
* Imagery used appropriately, and cited to an openly available source<br />
* Jargon terms used sparingly <br />
* When used, jargon terms explained succinctly <br />
<br />
=== 4. Module template followed ===<br />
* Title slide contains the name of the section header in the "Module Template" field<br />
* Title slide contains the name of the module in the "Subtitle" field<br />
* Author names and organizations follow the proper form [http://wiki.esipfed.org/index.php/AuthorsGuide See Authors Guide -- Module cover page]<br />
* Total number of slides is between 5 and 10<br />
* Any URLs included are relevant, live and accurate<br />
* Resources listed on the "Resource" slide include a single phrase or short sentence explanation followed on the next line with a live URL <br />
* Citable References used in the "References" slide listed using the [http://www.chicagomanualofstyle.org/16/ch15/ch15_sec009.html Chicago Manual of Style citation guidelines]<br />
<br />
=== 5. Voiceover script included for slides common to all modules (Title, Overview, etc.) ===<br />
* [[Voiceover Script | See Voiceover Script page]]</div>65.52.109.149https://wiki.esipfed.org/w/index.php?title=Best_Practices_in_Services_and_Data_Interoperability&diff=40340Best Practices in Services and Data Interoperability2012-07-28T22:34:26Z<p>65.52.109.149: Reverted edits by Rhusar (talk) to last revision by Steveolding</p>
<hr />
<div>[[July_16-18%2C_2008%2C_ESIP_Federation_Meeting%2C_Durham%2C_NH#Technical_Workshops_.28July_15.2C_2008.29 | Return to the master meeting page]]<br />
<br />
As the Federation membership grows, we have a continuing need to share with each other our diverse knowledge and experience in developing and deploying services oriented architectures based upon a variety of standards and in service of a diverse community of scientific and public users. This session will provide a variety of presentations that cover the basics of standard services, architectural models developed around services, and specific experiences in implementations and service interactions. <br />
<br />
There will also be a lot of interoperability expertise on hand, so bring any questions and problems you have in this area to get answers!<br />
<br />
==Agenda==<br />
* [[Web Service Protocols|Web Service Protocols, Experiences and Best Practices]] (8:30am - 10:00am)<br />
** Best Practices in REST, Pat Cappelaere, [[Media:BestPractices_REST.pdf|Presentation (pdf)]]<br />
** Best Practices in SOAP (discussion), Brian Wilson/Liping Di/Andy Mitchell<br />
** Web Mapping Service, Chris Lynnes, [[Media:BestPractices_WMS.pdf|Presentation (pdf)]]<br />
** [[The OGC Web Coverage Service Specification and Its Implementation]], Liping Di, [[Media:BestPractices_WCS.pdf|Presentation (pdf)]]<br />
* Discovery (10:30am - 12:00pm)<br />
** ECHO - Enabling Interoperability with NASA Earth Science Data and Services, Andy Mitchell, [[Media:BestPractices_ECHO.pdf|Presentation (pdf)]]<br />
** [[Atom ServiceCasting to advertise Web Services]], Brian Wilson<br />
* Understanding and Orchestration (1:00pm - 3:30pm)<br />
** [[Ontologies|Ontologies for Earth System Science]], Rob Raskin, [[Media:BestPractices_SWEET.pdf|Presentation (pdf)]]<br />
** [[SciFlo workflows, and ECHO Client for space/time granule query]], Brian Wilson<br />
** [[GeoBrain BPELPower Workflow Engine]], Liping Di, [[Media:BestPractices_BPEL.pdf|Presentation (pdf)]]<br />
* OPeNDAP (4:00pm - 5:30pm)<br />
** [[Hyrax Installation and Customization]], James Gallagher<br />
<br />
<br />
----<br />
Please follow the below example in submitting your workshop for inclusion in the program.<br />
<br />
* [[Workshop Title]] (created as a separate WIKI page for the abstract and presenter name. After creating the link [colored red because the page has not yet been created], click on the link to edit the page with your abstract and presenter information)<br />
<br />
==Additional Resources==<br />
[http://www.esdswg.com/techinfusion/infusion_news/081027-datainterop Practical Data Interoperability for Earth Scientists]</div>65.52.109.149https://wiki.esipfed.org/w/index.php?title=Air_Quality_Data_Systems_Assessment&diff=40336Air Quality Data Systems Assessment2012-07-28T16:31:00Z<p>65.52.109.149: Reverted edits by Erinmr (talk) to last revision by Rhusar</p>
<hr />
<div>{{AQDS_Backlinks}}<br />
<br />
==Air Quality Data Systems Assessment is now [[Media:Air Quality Data Systems Assessment rev.pdf|published ]]==<br />
<br />
EPA needs these systems to serve EPA’s customers better and more efficiently<br />
<br />
EPA cannot make the needed investments alone <br />
<br />
There are many AQ data systems that operate independently, without a common vision.<br />
<br />
'''GEOSS provides a global vision; it will take work and partnership to apply it to EPA.'''<br />
<br />
EPA as a “user-focused Agency” can lead and invest in formal partnerships with defined goals and shared technical principles.<br />
<br />
* In the near-term, make minor re-alignment of current EPA systems and invest towards these principles, and, more importantly, establishing them in future investments.<br />
<br />
* A better functioning partnership will help EPA understand its unique role, the roles of other partners and help it focus and target its own resource investments.<br />
<br />
* EPA should establish an OAQPS Data Coordinator to lead the partnerships within and outside EPA and moving the science-to-operations process.<br />
<br />
* Refresh the list of OAQPS internal data priorities and establish a systems roadmap<br />
towards them.<br />
<br />
* Focus on EPA’s data provider responsibilities: stewardship, basic access, and metadata collection and delivery.</div>65.52.109.149https://wiki.esipfed.org/w/index.php?title=Best_Practices_for_Developing_and_Maintaining_a_Metadata_Catalogue_System_-_The_NASA_Global_Change_Master_Directory_(GCMD)_Perspective&diff=40327Best Practices for Developing and Maintaining a Metadata Catalogue System - The NASA Global Change Master Directory (GCMD) Perspective2012-07-28T08:14:03Z<p>65.52.109.149: Reverted edits by Krbm (talk) to last revision by Kbene</p>
<hr />
<div>Abstract:<br />
<br />
Metadata catalogue systems that promote access to data and data-related<br />
services evolve over time through input from the science community and<br />
technological trends. Recognizing the importance of input from a<br />
diverse community can be attributed to the long-term success of NASA's<br />
Global Change Master Directory (GCMD), which has been assisting users in<br />
finding Earth science data for almost 20 years. Additionally, access to<br />
data-related services has also been beneficial in helping users utilize,<br />
visualize, analyze, handle, manage, and model Earth science data. Best<br />
practices for developing and maintaining our system for Data-Related<br />
Services will be discussed, along with some insight into who the users<br />
are and how they play a role in software development.<br />
<br />
Presenter:<br />
Tyler Stevens</div>65.52.109.149https://wiki.esipfed.org/w/index.php?title=Past_Visioneer_Telecons&diff=40322Past Visioneer Telecons2012-07-28T07:06:23Z<p>65.52.109.149: Reverted edits by Brogan (talk) to last revision by Carolbmeyer</p>
<hr />
<div>[[January 22, 2010]]</div>65.52.109.149https://wiki.esipfed.org/w/index.php?title=Air_Quality_Breakout,_ESIP_2011_Winter_Meeting&diff=40320Air Quality Breakout, ESIP 2011 Winter Meeting2012-07-28T06:35:52Z<p>65.52.109.149: Reverted edits by Erinmr (talk) to last revision by Sfalke</p>
<hr />
<div>''back to [[Preliminary_agenda | full ESIP Winter Meeting agenda]]'' | [[Air_Quality_Work_Group|Air Quality Main Page]]<br />
__TOC__<br />
The Air Quality Workgroup will be meeting on '''Wednesday''' January 5 during the ESIP Winter Meeting.<br />
<br />
= Remote Participation = <br />
== GoTo Meeting == <br />
URL for screen share:<br><br />
https://www1.gotomeeting.com/join/286518929<br />
<br><br />
Audio:<br><br />
Dial +1 (805) 309-0016<br><br />
Access Code: 286-518-929<br><br />
<br />
Meeting ID: 286-518-929<br />
<br />
<br />
<br />
=January 5, Wednesday =<br />
===1:45-3:15 Eastern===<br />
<br />
==== Welcome, Introduction and Overview (5-minutes)====<br />
* ESIP Winter Meeting theme: Evaluating and Maximizing the Impact of Earth Science Information<br />
<br />
==== New Projects ====<br />
* if you have a newly funded air quality project and would like to present an overview, please add it to this list<br />
<br />
==== Existing Project Networking Updates (5-min each) ====<br />
* [http://wiki.esipfed.org/images/b/b7/ACPortal_Update.ppt CEOS AC Portal]<br />
* [http://wiki.esipfed.org/images/f/f6/CIERA_Update.ppt CIERA]<br />
* HTAP Data Network<br />
* GEOSS Air Quality Community of Practice<br />
* [http://wiki.esipfed.org/images/6/6f/AIP3_AQH_Update.ppt GEOSS AIP]<br />
* AIRNow<br />
* others (please add to this list)<br />
<br />
====Indepth Discussion Topics ====<br />
* Recommendations for Air Quality Cyberinfrastructure <br />
** Summary of recommendations generated by CyAir<br />
** Review and feedback <br />
<br />
===''(scheduled break from 3:15-3:45 Eastern)''===<br />
<br />
===3:45-5:15 Eastern===<br />
<br />
====Indepth Discussion Topics continued ====<br />
* GEO Mid-Term Evaluation<br />
** Summary of evaluation<br />
** Review and feedback <br />
<br />
* GEOSS AQ Community of Practice<br />
<br />
* New ESIP Air Quality Workgroup Chair/co-Chairs</div>65.52.109.149https://wiki.esipfed.org/w/index.php?title=Discovery_Telecon_2012-02-14&diff=40209Discovery Telecon 2012-02-142012-07-22T17:56:14Z<p>65.52.109.149: Reverted edits by Rozele (talk) to last revision by Clynnes</p>
<hr />
<div>[[Discovery_Telecons|<< Back to the Discovery Telecons page]]<br />
<br />
* Tuesday, February 14, 2011. 4:00pm ET / 1:00pm PT<br />
* WebEx Info:<br />
** Call-in toll-free number (US/Canada): 1-877-668-4493<br />
** Attendee access code: 231 407 50<br />
** To start the online portion of the Personal Conference meeting , go to https://esipfed.webex.com/mw0306ld/mywebex/default.do?siteurl=esipfed&service=1 and select the Discovery Cluster meeting.<br />
<br />
== Attendees ==<br />
<br />
== Action Items ==<br />
<br />
== Agenda ==<br />
<br />
* Recap of Winter Meeting (if needed)<br />
* Status of new DCPs<br />
** DCP-4: Use of xlink attributes in Atom <link> tags<br />
** DCP-5: Use of OpenSearch <Query> tags for valid parameter values<br />
** DCP-6: Replace overloaded time:start and time:end tags with dc:date<br />
** DCP-7: define error handling best practices<br />
<br />
== Notes ==<br />
<br />
=== Recap of Winter Meeting (if needed) ===<br />
<br />
=== DCP-4: Use of xlink attributes in Atom <link> tags ===<br />
Current Version: [[DCP-4|DCP-4: OPeNDAP Links in the Atom <link/> element]]<br />
<br />
=== DCP-5: Use of OpenSearch <Query> tags for valid parameter values ===<br />
<br />
=== DCP-6: Adopt Dublin Core Date Specification in Atom Response ===<br />
Current version: [[Discovey_Change_Proposal-6|DCP-6: Adopt Dublin Core Date Specification in Atom Response]]<br />
<br />
=== DCP-7: define error handling best practices ===</div>65.52.109.149https://wiki.esipfed.org/w/index.php?title=AQ_2007_10_31_Discussion&diff=40204AQ 2007 10 31 Discussion2012-07-22T11:43:11Z<p>65.52.109.149: Reverted edits by Sfalke (talk) to last revision by HowardBurrows</p>
<hr />
<div>[[Workshop|''back to 2007-10-31 Workshop page'']]<br />
----<br />
<br />
==Data lineage tracking==<br />
*Do we need to coordinate conventions for tracking provenance, even in readme files?<br />
*How do we recognize and track sources of variance (and their magnitude) within and across datasets throughout the processing chain?<br />
**Take as an example the case x and y variance are not the same.<br />
**Which processing tools compound error? How do we account for it?<br />
*How do we make apparent critical aspects of data interpretation as these aspects change along the processing chain? Which propagate?<br />
**Do we need rules? How about conventions? Community organization to provide oversite and promote use, especially responsible use?<br />
*Air quality forecasting application<br />
**plus special/exceptional events<br />
*Assessment of control programs application<br />
**attention special/exceptional events<br />
<br />
==Focus: HTAP and exceptional events==<br />
*Identify users in these applications<br />
*Connect the existing projects (Airnow Tech, RSIG, Giovanni, etc.)<br />
**Exceptional events: Airnow Tech is becoming source for surface data<br />
**HTAP: model evaluation is needed (e.g., RSIG, Giovanni)<br />
*How to support analysis and comparison of datasets<br />
*Create "interoperability network" and connect appropriate players<br />
*Lineage info required is driven by uses: How to capture this up front?<br />
<br />
==Data quality considerations==<br />
*Can we list spurious sources of variance that must be taken into consideration as we visualize or composite datasets?<br />
**Cloud cover<br />
**Registration issues<br />
***sensitivity to neighboring measurements<br />
**Instrument issues<br />
***resolution<br />
****types of interpixel contamination<br />
***interference (NOx, chemical, electrical)<br />
***"viewing" angle (each pixel, terrain issues)<br />
**Timing issues<br />
***Time of day<br />
***Day of week<br />
***Lunar cycle<br />
***Special (car exhaust, sporting event, volcanic activity)<br />
**Magnetic issues (no omi for Rio)<br />
***Raised as a confounding issue only known to remote sensing elders<br />
***How much of an effect is seen at other sites (besides Rio)<br />
<br />
*What is the best way to determine "best available evidence"?<br />
**How do we know if a remote sensing product has been verified with ground data and in situations comparable to use?<br />
*How and why might we tag a dataset "bad data"?<br />
<br />
==Use Cases: Question-Driven Approach==<br />
===Puget Sound Challenge===<br />
*Highlight at EPA OEI Symposium Nov 14<br />
===Wildfire Scenario Southern California===<br />
*How to advertise the needs and opportunities?<br />
===Beijing China Olympics===<br />
*Door may be closed to participate ahead of time<br />
*High visibility for anything accomplished<br />
===How much NO2 is man made?===<br />
*How would we provide data to justify the statement, "Man-made emissions of nitrogen oxides dominate total emissions"? <br />
:::See http://www.apis.ac.uk/overview/pollutants/overview_NOx.htm<br />
===Thessolonika dataset===<br />
*Perhaps useful to discuss formally Ernest Hilsenrath's Thessolonika slide<br />
===Compare appropriate use of "near real time" vs "standard product"===<br />
*Provides example in which absolutes are not all there is<br />
*Would give experience in a limited context that might generalize<br />
*Has immediate effect on use and users<br />
===Is the air safe to breath?===<br />
*Can't give satisfying answer: spatial/temporal variation<br />
*Is it getting better?<br />
*How do we get people used to tracking environmental indicators and In Situ monitoring to track and use the remote sensing data?<br />
**Need to train and re-train experts and decision makers<br />
<br />
==Solutions==<br />
===Technology problem===<br />
*Statement was made that this may not be technology problem<br />
*But we don't have technology for capturing inference or causes<br />
**we are barely handling ontology when we need epistemology, grammar, rhetoric, and dialectics<br />
*We don't capture emergent properties<br />
**Rudy's frames provide slots for lots of the necessary ancillary data<br />
**Frame-based reasoning is brittle and doesn't handle ambiguity<br />
*Compare "readme" files and wiki<br />
**wiki can be more interesting and see larger audience participation<br />
**wiki may provide too many structural decisions; needs hourly grooming and attention<br />
*How do we capture the chain of decisions involved in data collection, processing, and use?<br />
**The "chain" begins before the sensor is designed and extends through many intermediaries out to each user in new contexts. <br />
***How do we tag data appropriately for an educator or policy maker?<br />
***Decisions are made between perceived choices. At the extreme, what if there are whole new sets of considerations that hadn't arisen at the time the mission was designed? What if they arise for some irreversible processing decision?<br />
<br />
===Social problem===<br />
*How do we get people to use the technology<br />
**Dedicate a person to capturing ephemera<br />
**But there is an inestimable volume of such, it would be too expensive<br />
*Question may be, "How do we elevate those few really significant details?"<br />
**What tools would facilitate this? Easy way to raise "level 3" objections or warnings<br />
*Different communities don't know enough to ask each other for the "right" things<br />
**Need low level interaction to raise common ground<br />
*Sometimes more than a "chain" of intermediaries: a whole social network<br />
**There is feedback even to the design of the next sensor<br />
**Create a wire diagram of specific flows (chain diagrams)<br />
**Examine tools from popular social networking sites (Orkut, deli.cio.us, Amazon, friendster, linkedin)<br />
<br />
===Systemic problem===<br />
*Are there appropriate rewards for investment of time in metadata?<br />
*How do we control for bias, institutional and other?<br />
**There are always reasons to "sell" aspects of what was done<br />
**Everyone has a bias; courts require id for advocacy; should science?<br />
**Science has an assumption of no unbiased judgments: is a non-rhetorical assumption valid?<br />
***data processing and presentation canbe/is rhetorical, advocating a decision<br />
*Are the right people at the table?<br />
**ESIP Federation was established to assure that the right mix of experts were involved in data decisions.<br />
**Can we expedite reviews using "federalism" (balanced interests)?<br />
<br />
===Useful analogies===<br />
*Process for creating "data spaces" used for data sheets in education<br />
**DLESE and NSDL Data Access Working Group<br />
**Data sheets are one-page summaries giving the "vibe of the thing"<br />
*Stock Market<br />
**Used to be little information available; every one used broker<br />
**Now day traders can get high level realtime data<br />
**Idiots get weeded out<br />
*Radar images in weather report<br />
**Having Google Earth OMI visualizations scares folks<br />
**It is not like weather; seems like only stupid people live in Northeast urban areas<br />
**2004 Sciamachy image got frontpage coverage showing European pollution sites; people knew red meant bad; raises whole issue of color scales and interpretation; AQI has regulatory requirement for color values<br />
**Might better inform people who could drive change.<br />
*Ecosystem Model<br />
**Data services are in an environment competing/cooperating<br />
**Diversity is good to avoid collapse<br />
**Valuable to have multiple overlapping products to compare<br />
<br />
==Opening Issues==<br />
*What is the particular niche for this group?<br />
**Comparison to science meeting<br />
***Was this more like a science meeting?<br />
::Can we segment topics so all parties participate in all discussions?<br />
::Is there a way to capture all the discussion that happened around presentations?<br />
*Special opportunities to build "knowledge base"<br />
**Journal articles may not capture all available discussion<br />
::Could we test tools that would allow us to elaborate and apportion the significance of topics? Maybe we could use a wiki for this.<br />
::The comment was made that our measurements are "unstable", which elicited the comment, "Then what are we doing here?" How do we avoid defaming all our data with details? Certainly these satellite differences are significant. How can we state that while questioning the details of our understanding?<br />
*Opportunity to reach across communities<br />
**Clearly an advantage of the ESIP Federation is the opportunity to put technology people together with data people, scientists, educators, and applied science people. How can we take best advantage of this opportunity?<br />
::It might be that we could use discussion tools to help create an effective knowledge base that communicates appropriately to different audiences. Policy makers need to see that there is a human effect, not that there is still some question which of the effects are the most significant.<br />
*Data/tool Decision Tree<br />
::wonder if we could set up table comparing products<br />
::might do by datasource, visualization tool, processing tool, etc.<br />
*Usage considerations<br />
**Legal<br />
***EPA always has to defend its judgments in court<br />
***Court needs "preponderance of evidence" or "beyond a reasonable doubt"<br />
::This is quite different from 0.95% certainty.<br />
**Science<br />
***Needs detailed information about sources and models used in "correcting" data<br />
**Education<br />
***Special considerations for "real-time" data<br />
***Special considerations for hiding and introducing complexity</div>65.52.109.149https://wiki.esipfed.org/w/index.php?title=Semantic_Web_2010_Special_Topics&diff=40201Semantic Web 2010 Special Topics2012-07-22T07:39:41Z<p>65.52.109.149: Reverted edits by Clynnes (talk) to last revision by Pfox</p>
<hr />
<div>==Special Topics==<br />
<br />
* SWEET Governance<br />
** Status update on 2.0<br />
** Application tools<br />
** Use<br />
** Call for Updates<br />
** Governance committee - 5 people<br />
** please add here<br />
<br />
* Data-type and Service Ontologies<br />
** Update<br />
** Discussion of paper that Peter and Rahul are writing<br />
** Application examples (possible overlap with next topic)<br />
<br />
* Applications for Aug (GMU) ESSI Workshop<br />
** Chris to edit here<br />
<br />
* Possible one other topic here...</div>65.52.109.149