Re: ontologies for SCADA and Smart Grid
Dear Miltion, Personally, I am also interested in sustainability - I will be grateful if you can point me to any ontologies that you find in this area. While I don't think there is much out there at this time, the following may be helpful to get started: 1. Toward knowledge structuring of sustainability science based on ontology engineeringhttp://www.google.com/url?sa=trct=jq=esrc=ssource=webcd=1ved=0CCgQFjAAurl=http%3A%2F%2Fwww.geraldkembellec.fr%2FdocOntology%2FToward%2520knowledge%2520structuring%2520of%2520sustainability%2520science%2520based%2520on%2520ontology%2520engineering.pdfei=gdlkT8WCJ4KbiQLS6rGiDwusg=AFQjCNGB0fVV21NyADMhTYkxjqGChEu_wA 2. Biodiversity Information Standards (TDWG)http://www.tdwg.org/about-tdwg/ 3. Research on heterogeneous data integration for Smart Gridhttp://ieeexplore.ieee.org/Xplore/login.jsp?url=http%3A%2F%2Fieeexplore.ieee.org%2Fiel5%2F5550976%2F5563521%2F05564620.pdf%3Farnumber%3D5564620authDecision=-203 4. Smart Grid Maturity Model (SGMM) http://www.sei.cmu.edu/smartgrid/tools/index.cfm Professionally, I work for Semantic Artshttp://www.semanticarts.com/semantictechnology/how-we-design-semantic-technology/, whose core business includes developing ontologies for our clients. In the event that you wish to use our services, please do not hesitate to get in touch. Regards, Michael Michael Uschold, PhD Senior Ontology Consultant, Semantic Arts http://www.semanticarts.com LinkedIn: http://tr.im/limfu Skype, Twitter: UscholdM On Thu, Mar 15, 2012 at 10:04 AM, ProjectParadigm-ICT-Program metadataport...@yahoo.com wrote: I am looking for ontologies for SCADA and Smart Grid applications in particular in agro-industrial, (renewable) energy technology, water, sewage and waste water processing, production and distribution settings and for generalized industrial processes e.g. in manufacturing, multi-modal transportation and logistics. Milton Ponson GSM: +297 747 8280 PO Box 1154, Oranjestad Aruba, Dutch Caribbean Project Paradigm: A structured approach to bringing the tools for sustainable development to all stakeholders worldwide by creating ICT tools for NGOs worldwide and: providing online access to web sites and repositories of data and information for sustainable development This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.. If you have received this email in error please notify the system manager.. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
[EKAW 2012] Call for Papers
Call for Papers: 18th International Conference on Knowledge Engineering and Knowledge Management (EKAW 2012) National University of Ireland Galway Quadrangle October 8-12, 2012. http://ekaw2012.ekaw.org The 18th International Conference on Knowledge Engineering and Knowledge Management is concerned with all aspects of eliciting, acquiring, modeling and managing knowledge, and its role in the construction of knowledge-intensive systems and services for the semantic web, knowledge management, e-business, natural language processing, intelligent information integration, etc. The special focus of the 18th edition of EKAW will be on Knowledge Engineering and Knowledge Management that matters. We are explicitly calling for papers that have a potentially high impact on a specific community or application domain (e.g. pharmacy and life sciences), as well as for papers which report on the development or evaluation of publicly available data sets relevant for a large number of applications. Moreover, we welcome contributions dealing with problems specific to modeling and maintenance of real-world data or knowledge, such as scalability and robustness of knowledge-based applications, or privacy and provenance issues related to organizational knowledge management. In addition to the main research track, EKAW 2012 will feature a tutorial and workshop program, as well as a poster and demo track. Moreover, there will be a Doctoral Consortium giving new PhD students a possibility to present their research proposals, and to get feedback on methodological and practical aspects of their planned dissertation. The proceedings of the conference will be published by Springer Verlag in the LNCS series. The LNCS volume will contain the contributed research papers as well as descriptions of the demos presented at the conference. Papers published at any of the workshops will be published in dedicated workshop proceedings. EKAW 2012 welcomes papers dealing with theoretical, methodological, experimental, and application-oriented aspects of knowledge engineering and knowledge management. In particular, but not exclusively, we solicit papers about methods, tools and methodologies relevant with regard to the following topics: 1) “Knowledge Management and Knowledge Engineering that matters” • Real-world applications of methods for knowledge management and engineering in domains such as - e-Government and public administration - Life sciences, health and medicine - Automotive and manufacturing industry - Cultural heritage applications - Digital libraries • Development and evaluation of publicly available knowledge repositories for new applications or domains • Methods and methodologies addressing the challenges of real-world data, e.g., - Scalability, robustness etc. - Maintenance costs and financial risks - Privacy and data security • Lessons learned from case studies, e.g., - Knowledge management in large organizations - Adoption of semantic web technologies - Maintenance of corporate knowledge repositories 2) Knowledge Management • Methodologies and tools for knowledge management • Knowledge sharing and distribution, collaboration • Best practices and lessons learned from case studies • Provenance and trust in knowledge management • Methods for accelerating take-up of knowledge management technologies • Corporate memories for knowledge management • Evolution, maintenance and preservation of knowledge • Web 2.0 technologies for knowledge management • Incentives for human knowledge acquisition (e.g. games with a purpose) 3) Knowledge Engineering and Acquisition • Tools and methodologies for ontology engineering • Ontology design patterns • Ontology localization • Ontology alignment • Knowledge authoring and semantic annotation • Knowledge acquisition from non-ontological resources (thesauri, folksonomies etc.) • Semi-automatic knowledge acquisition, e.g., ontology learning • Mining the Semantic Web and the Web of Data • Ontology evaluation and metrics • Uncertainty and vagueness in knowledge representation • Dealing with dynamic, distributed and emerging knowledge 4) Social and Cognitive Aspects of Knowledge Representation • Knowledge representation inspired by cognitive science • Synergies between humans and machines • Knowledge emerging from user interaction and networks • Knowledge ecosystems • Expert finding, e.g., by social network analysis • Trust and privacy in knowledge representation • Collaborative and social approaches to knowledge management and acquisition • Crowdsourcing in knowledge management As last EKAW conference we will accept different types of papers. The papers will all have the same status and follow the same formatting guidelines in the proceedings but will receive special treatment during the reviewing phase. In particular, each paper type will be subject to own evaluation criteria. The PC will also make sure that there is a reasonable balance of the
RE: HCLS IG Note on mapping and publishing life sciences RDF
hi scott, finally got a chance to go through the note and, yes, it is well put together. being naive on this subject, some of my comments may safely be ignored. Introduction: * instead of being in the body of the test, shouldn't the explanation for Figure 1 be a caption? Section 2: * what is a Linked Data interface? it doesn't seem to be a defined standard, rather it seems like each different RDF data would define its own interface. some clarity on what is meant by this term would help. * Q2 grammar: Also, it is often unnecessary to convert every table into a class and can create scaling problems. these points are mentioned but i didn't see any discussion about how they affect the DB to RDF mapping (the specific case of data warehousing is covered but that is but one way to denormalize): RDB schemas can vary in their level of normalization as quantified by normalized forms (Date 2009). and In practice, many databases are not normalized because the overhead of working with the schema is not worth the extra reliability and space savings that may result. * Q3 perhaps a comment on what in the original non-relational information affects the quality of the RDF would be nice * Q5 doesn't multiple FROM clauses also allow combining datasets but from different graphs? This sentence implies that Structure descriptors always link datasets containing drugs and small molecules, i think this is supposed to be more general: Structure descriptors, such as SMILES strings, and InChi identifiers may be used to establish links between datasets containing drugs and small molecules. should be : Structure descriptors, such as SMILES strings and InChi identifiers, may be used to establish links between datasets. ? * Q7 not a sentence: Use of the BioPortal for matching entities and their URIs (including ontologies from Open Biomedical Ontology (OBO) Foundry (OBO 2011)). * Q12 since this is a note on Mapping and linking life science data using RDF, how does the following help one map their RDF data to the web (it's an important point but seems a little off target in this note, maybe the emphasis should be how one can use these tools in publishing their data)? An important part of improving the utility of the Web is by documenting the reliability and performance of information services. In the area of biomedical information services,... * Q14 grammar (delete 'a'?): ... and to use classes as a values in the metadata for a graph; Section 4: perhaps change reflect the state of the art to reflect the current state of the art? cheers, michael Michael Miller Software Engineer Institute for Systems Biology -Original Message- From: M. Scott Marshall [mailto:mscottmarsh...@gmail.com] Sent: Tuesday, March 13, 2012 2:31 PM To: David Booth; Erich Gombocz Cc: HCLS; biohackat...@googlegroups.com; linkedlifedatapracticesn...@googlegroups.com; public-lod@w3.org Subject: Re: Fwd: HCLS IG Note on mapping and publishing life sciences RDF On Tue, Mar 13, 2012 at 10:17 PM, David Booth da...@dbooth.org wrote: On Tue, 2012-03-13 at 21:16 +0100, M. Scott Marshall wrote: [ . . . ] IG Note (Draft) HCLS IG Note on mapping and publishing life sciences RDF [1] https://docs.google.com/document/d/1XzdsjCfPylcyOoNtDfAgz15HwRdCD- 0e0ixh21_U0y0/edit?hl=en_US Nice work on this! A couple of small editorial suggestions: Thanks for the encouragement from you and Erich. About the use of a priori , a posteriori - I will mull that over. I was pretty happy with the way it seemed to communicate our thoughts, a little attached actually.. :( 2. The intro mentions that a query for Homo sapiens gene label Alg2 in Entrez Gene (http://www.ncbi.nlm.nih.gov/gene) returns multiple results. Among them is one gene located in chromosome 5 (Entrez ID:85365) and the other in chromosome 9 (Entrez ID:313231), each with multiple aliases. But the results that I see show ID:85365 as the ID for the one on chromosome 9, and the other one (maybe?) has ID 10016: http://www.ncbi.nlm.nih.gov/gene?term=Alg2[sym]%20homo%20sapiens Oops! Thanks for catching that. We had corrected id mixup in the article but forgot to correct it in the note. Thanks!, Scott
Web Science Meetup at WWW Conferene - Lyon , France, Friday April 20th, 2012
Dear all, We are pleased to announce and invite you to participate in the Web Science Meetup that will be held in Lyon during the WWW Conference (http://www2012.wwwconference.org http://www2012.wwwconference.org/ ), Friday April 20th at 6pm (the afternoon after the WWW Web Science session) The Meetup is neither a conference nor a workshop but rather an informal meeting to gather people interested in Web Science. We propose to meet in the WWW conference center (room will be provided later) and continue the meeting in famous downtown Lyon ;) The event is organized by our modest Web Science Montpellier Meetup group which involves researchers from different organizations (Universities, and institutes) in the Montpellier area or not. Please learn more and subscribe to the Meetup by visiting: http://www.meetup.com/webscience-montpellier/events/17450374/ There are currently no formal way to express interest (e.g., communication), but if you are interested by the meetup please let me know and I will gather everything. Feel free to transfer the invitation to anyone that might be interested. Learn more about Web Science: Web Science Trust, http://webscience.org http://webscience.org ACM Web Science Conference 2012, http://www.websci12.org/ Best regards The organizers, Dr. Clement Jonquet, University of Montpellier, LIRMM Pr. Stefano A. Cerri, University of Montpellier, LIRMM --- Dr. Clement JONQUET - PhD in Informatics - Assistant Professor jonq...@lirmm.fr http://www.lirmm.fr/~jonquet University of Montpellier LIRMM 161 rue Ada 34095 Montpellier Cdx 5 France Tel:+33/4 67 14 97 43 Fax: +33/4 67 41 85 00 Skype: clementpro Twitter:@jonquet_lirmm http://twitter.com/jonquet_lirmm Slideshare: jonquet http://www.slideshare.net/jonquet ---
Re: [lod2] World Bank Linked Data
On 12-03-16 07:35 PM, Hugh Glaser wrote: On 16 Mar 2012, at 16:22, Sarven Capadisli wrote: On 12-03-16 02:19 PM, Hugh Glaser wrote: Hi Sarven, That's great. I have added your owl:sameAs links to sameAs.org (I read your Terms of Use, which seemed to a allow it, but if you want I can remove them.) (http://sameas.org/?uri=http://worldbank.270a.info/classification/country/AD) Really gives a sense of the linkage in the LD cloud on countries. What can I say other than, thank you :) Great :-) If I were to stick to a super restricted view on owl:sameAs and the fact that the country resources are just concepts (as I claim them to be skos:Concepts), it should use skos:exactMatch to DBpedia's country resource. To keep the LOD crowd happy and slightly loosen the view on the relationship between the two resources, I went ahead with owl:sameAs. Either way has its pluses and minuses and that burden is unfortunately dumped on the consumer. If there is an intelligent way to go at it while keeping a great number of people happy, I'd be glad to update things accordingly from this end. As far as the exact predicate, I avoid venturing into what is best. I would have done the same harvest if you had put skos:exactMatch or even skos:closeMatch. sameAs.org is a discovery mechanism - it helps people/agents find things (I hope), and then they can choose whether they believe it! Hmmm. Now I notice you *do* have some skos:exactMatch and even three skis:closeMatch. So they have gone in as well :-D (I missed them earlier as they were not in your nice voiD file, which is the place I looked, of course :-) ) I've just updated the VoID file. However, I didn't put in skos:exactMatch and skos:closeMatch this time around in void:Linkset because there are only a few of them in the whole dataset. I will however revisit this when there is more stuff going on. By the way, you have the 2 letter skos:exactMatch with the 3 letter (e.g. AW = ABW). But the 3 letter (e.g. http://worldbank.270a.info/classification/country/ABW) resolution has very little information. Is this intentional? Yes, that is intentional. I don't have a perfect solution to my intentions at this time. Perhaps you can chime in on that. What I was thinking is that, the URI for the three letter code is just there to allow consumers which are aware of the three letter code (as opposed to the two letter code) to easily jump to the two letter URI. I suppose that could have been also achieved with a literal for the two literal resource as well. In the name of automatic discovery, of course more triples can be introduced for the three letter resource (e.g., rdf:type), but I think that unnecessarily bloats the data. The three letter resource is only there as a hook for the two letter resource. In the end, the consumer will have to comb through the data any way to find out about the three letter code. I'm not sure if there is any real benefit of one way over the other i.e., to use a skos:exactMatch to three letter URI vs. the three letter literal value for the two letter URI. I've created a URI for the three letter code because I /sort of/ wanted to give both of the codes equal importance even though only one of them contains the data. Perhaps owl:sameAs would be more appropriate here. -Sarven
Re: [lod2] World Bank Linked Data
On 19 Mar 2012, at 00:05, Sarven Capadisli wrote: On 12-03-16 07:35 PM, Hugh Glaser wrote: On 16 Mar 2012, at 16:22, Sarven Capadisli wrote: On 12-03-16 02:19 PM, Hugh Glaser wrote: Hi Sarven, That's great. I have added your owl:sameAs links to sameAs.org (I read your Terms of Use, which seemed to a allow it, but if you want I can remove them.) (http://sameas.org/?uri=http://worldbank.270a.info/classification/country/AD) Really gives a sense of the linkage in the LD cloud on countries. What can I say other than, thank you :) Great :-) If I were to stick to a super restricted view on owl:sameAs and the fact that the country resources are just concepts (as I claim them to be skos:Concepts), it should use skos:exactMatch to DBpedia's country resource. To keep the LOD crowd happy and slightly loosen the view on the relationship between the two resources, I went ahead with owl:sameAs. Either way has its pluses and minuses and that burden is unfortunately dumped on the consumer. If there is an intelligent way to go at it while keeping a great number of people happy, I'd be glad to update things accordingly from this end. As far as the exact predicate, I avoid venturing into what is best. I would have done the same harvest if you had put skos:exactMatch or even skos:closeMatch. sameAs.org is a discovery mechanism - it helps people/agents find things (I hope), and then they can choose whether they believe it! Hmmm. Now I notice you *do* have some skos:exactMatch and even three skis:closeMatch. So they have gone in as well :-D (I missed them earlier as they were not in your nice voiD file, which is the place I looked, of course :-) ) I've just updated the VoID file. However, I didn't put in skos:exactMatch and skos:closeMatch this time around in void:Linkset because there are only a few of them in the whole dataset. I will however revisit this when there is more stuff going on. By the way, you have the 2 letter skos:exactMatch with the 3 letter (e.g. AW = ABW). But the 3 letter (e.g. http://worldbank.270a.info/classification/country/ABW) resolution has very little information. Is this intentional? Yes, that is intentional. I don't have a perfect solution to my intentions at this time. Perhaps you can chime in on that. What I was thinking is that, the URI for the three letter code is just there to allow consumers which are aware of the three letter code (as opposed to the two letter code) to easily jump to the two letter URI. I suppose that could have been also achieved with a literal for the two literal resource as well. In the name of automatic discovery, of course more triples can be introduced for the three letter resource (e.g., rdf:type), but I think that unnecessarily bloats the data. The three letter resource is only there as a hook for the two letter resource. In the end, the consumer will have to comb through the data any way to find out about the three letter code. I'm not sure if there is any real benefit of one way over the other i.e., to use a skos:exactMatch to three letter URI vs. the three letter literal value for the two letter URI. I've created a URI for the three letter code because I /sort of/ wanted to give both of the codes equal importance even though only one of them contains the data. Perhaps owl:sameAs would be more appropriate here. -Sarven I (still) won't comment on which predicates you use to describe equivalence :-) My observation was that it was hard (impossible unless you use sameAs.org :-) ?) to get from your 3-letter URIs to the 2-letter ones, which seemed strange. To be more specific: If someone gives me the URI http://worldbank.270a.info/classification/country/AND I can find nothing about it, not even http://worldbank.270a.info/classification/country/AD. In fact this actually contradicts principle 3 of Linked Data - you don't Provide useful information, as far as I can tell. Not a big deal - just a link (of some kind) to the 2-letter one would help. In fact, I think, from what you say, you think the link is there from 3-letter to 2-letter. But I couldn't find it. I am looking at http://worldbank.270a.info/classification/country/AND.turtle Best Hugh -- Hugh Glaser, Web and Internet Science Electronics and Computer Science, University of Southampton, Southampton SO17 1BJ Work: +44 23 8059 3670, Fax: +44 23 8059 3045 Mobile: +44 75 9533 4155 , Home: +44 23 8061 5652 http://www.ecs.soton.ac.uk/~hg/
