Difference (from revision 5 to 6)
Changed: 1c1,6
|
= OntologySummit2012: (Track-4) "Large-scale domain applications" Community Input {nid 32CO} = |
|
<h2><a name="nid32CO" id="nid32CO"></a><a href="http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012" class="wikiword">OntologySummit2012</a>: (Track-4) "Large-scale domain applications" Community Input <a class="nid" title="32CO" href="#nid32CO">(32CO)</a></h2> <p><a name="nid338X" id="nid338X"></a>Track Co-Champions: Dr. <a href="http://ontolog.cim3.net/cgi-bin/wiki.pl?SteveRay" class="wikiword">SteveRay</a> and Dr. <a href="http://ontolog.cim3.net/cgi-bin/wiki.pl?TrishWhetzel" class="wikiword">TrishWhetzel</a> <a class="nid" title="338X" href="#nid338X">(338X)</a></p> <h3><a name="nid32CP" id="nid32CP"></a>Mission Statement: <a class="nid" title="32CP" href="#nid32CP">(32CP)</a></h3> <p><a name="nid32E0" id="nid32E0"></a>'''<b>This track will help to ground the discussions in the other tracks and bring key challenges to light by describing current large-scale systems and systems of systems that either use, or could use, ontologies in their deployment. "Large-scale" can mean either very large data sets, very complex data sets, federated systems, highly distributed systems, or real-time, continuous data systems. Examples of large data sets might include scientific observations and studies; complex data sets could be technical data packages for manufactured products, or electronic health records; federated systems could include information sharing to combat terrorism, highly distributed systems includes items such as the smart electrical grid (aka Smart Grid), and real-time systems include network management systems. Of course, some big systems might include all five aspects.''' <a href="http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012_Applications_Synthesis#nid32DZ" class="nid">T</a></b> <a class="nid" title="32E0" href="#nid32E0">(32E0)</a></p> <p><a name="nid32EE" id="nid32EE"></a>see also: <a href="http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012_Applications_Synthesis" class="wikiword">OntologySummit2012_Applications_Synthesis</a> <a class="nid" title="32EE" href="#nid32EE">(32EE)</a></p> <hr /> {nid 35DN} |
Changed: 3c8,43
|
Track Co-Champions: Dr. SteveRay and Dr. TrishWhetzel {nid 338X} |
|
<p><a name="nid32CQ" id="nid32CQ"></a>'''Enter your input below''' ... ''(please identify yourself and date your entry)'' <a class="nid" title="32CQ" href="#nid32CQ">(32CQ)</a></p> <p><a name="nid35D3" id="nid35D3"></a>Entry by <a href="http://ontolog.cim3.net/cgi-bin/wiki.pl?SteveRay" class="wikiword">SteveRay</a>, 2/21/2012 <a class="nid" title="35D3" href="#nid35D3">(35D3)</a></p> <ul> <li><a name="nid35D4" id="nid35D4"></a>Observations / Lessons learned: <a class="nid" title="35D4" href="#nid35D4">(35D4)</a><ul> <li><a name="nid35D5" id="nid35D5"></a>UML to OWL is a common requirement for legacy systems <a class="nid" title="35D5" href="#nid35D5">(35D5)</a><ul> <li><a name="nid35D6" id="nid35D6"></a>Need better tools to help interpret legacy systems, transform into semantic systems. <a class="nid" title="35D6" href="#nid35D6">(35D6)</a></li> <li><a name="nid35D7" id="nid35D7"></a>Starting from scratch is rare. <a class="nid" title="35D7" href="#nid35D7">(35D7)</a></li> </ul> </li> <li><a name="nid35D8" id="nid35D8"></a>Ontology patterns are very helpful, and encourage model reuse <a class="nid" title="35D8" href="#nid35D8">(35D8)</a></li> <li><a name="nid35D9" id="nid35D9"></a>Look for the 80-20 rule of semantic development <a class="nid" title="35D9" href="#nid35D9">(35D9)</a></li> <li><a name="nid35DA" id="nid35DA"></a>Semantic techniques work best when not compromised by implementation tradeoffs <a class="nid" title="35DA" href="#nid35DA">(35DA)</a></li> <li><a name="nid35DB" id="nid35DB"></a>Semantic methods are faster to implement and easier to maintain <a class="nid" title="35DB" href="#nid35DB">(35DB)</a></li> <li><a name="nid35DC" id="nid35DC"></a> <a class="nid" title="35DC" href="#nid35DC">(35DC)</a></li> <li><a name="nid35DD" id="nid35DD"></a>Semantic approaches particularly suited to systems with many complex constraints, rules, laws, with frequent changes <a class="nid" title="35DD" href="#nid35DD">(35DD)</a></li> </ul> </li> </ul> <ul> <li><a name="nid35DE" id="nid35DE"></a>Needs: <a class="nid" title="35DE" href="#nid35DE">(35DE)</a><ul> <li><a name="nid35DF" id="nid35DF"></a>Need better standards for common elements: <a class="nid" title="35DF" href="#nid35DF">(35DF)</a><ul> <li><a name="nid35DG" id="nid35DG"></a>Datatypes (Are xsd types enough? I think not) <a class="nid" title="35DG" href="#nid35DG">(35DG)</a></li> <li><a name="nid35DH" id="nid35DH"></a>Ontology patterns (e.g. whole/part patterns) <a class="nid" title="35DH" href="#nid35DH">(35DH)</a></li> <li><a name="nid35DI" id="nid35DI"></a>Collect ontological primitives from observation data <a class="nid" title="35DI" href="#nid35DI">(35DI)</a></li> </ul> </li> <li><a name="nid35DJ" id="nid35DJ"></a>Need repositories (When is OOR going to be ready for production use?) <a class="nid" title="35DJ" href="#nid35DJ">(35DJ)</a><ul> <li><a name="nid35DK" id="nid35DK"></a>Repositories of ontological patterns could be more useful than repositories of ontologies <a class="nid" title="35DK" href="#nid35DK">(35DK)</a></li> </ul> </li> <li><a name="nid35DL" id="nid35DL"></a>Need industrial strength semantic services resident in the cloud <a class="nid" title="35DL" href="#nid35DL">(35DL)</a></li> <li><a name="nid35DM" id="nid35DM"></a>Need better visualization tools and approaches <a class="nid" title="35DM" href="#nid35DM">(35DM)</a></li> </ul> </li> </ul> <hr /> {nid 35DO} |
Changed: 5,40c45,47
|
== Mission Statement: {nid 32CP} == '''[t 32DZ]''' {nid 32E0} see also: OntologySummit2012_Applications_Synthesis {nid 32EE} ---- '''Enter your input below''' ... ''(please identify yourself and date your entry)'' {nid 32CQ} Entry by SteveRay, 2/21/2012 {nid 35D3} * Observations / Lessons learned: {nid 35D4} ** UML to OWL is a common requirement for legacy systems {nid 35D5} *** Need better tools to help interpret legacy systems, transform into semantic systems. {nid 35D6} *** Starting from scratch is rare. {nid 35D7} ** Ontology patterns are very helpful, and encourage model reuse {nid 35D8} ** Look for the 80-20 rule of semantic development {nid 35D9} ** Semantic techniques work best when not compromised by implementation tradeoffs {nid 35DA} ** Semantic methods are faster to implement and easier to maintain {nid 35DB} ** {nid 35DC} ** Semantic approaches particularly suited to systems with many complex constraints, rules, laws, with frequent changes {nid 35DD} * Needs: {nid 35DE} ** Need better standards for common elements: {nid 35DF} *** Datatypes (Are xsd types enough? I think not) {nid 35DG} *** Ontology patterns (e.g. whole/part patterns) {nid 35DH} *** Collect ontological primitives from observation data {nid 35DI} ** Need repositories (When is OOR going to be ready for production use?) {nid 35DJ} *** Repositories of ontological patterns could be more useful than repositories of ontologies {nid 35DK} ** Need industrial strength semantic services resident in the cloud {nid 35DL} ** Need better visualization tools and approaches {nid 35DM} ---- * ... {nid 32CR} |
|
<ul> <li><a name="nid32CR" id="nid32CR"></a>... <a class="nid" title="32CR" href="#nid32CR">(32CR)</a></li> </ul> {nid 35DP} |