You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@esme.apache.org by rh...@apache.org on 2011/06/26 11:34:01 UTC

svn commit: r1139748 - in /esme/site/trunk/doap: ./ doap_ESME.rdf esme.rdf

Author: rhirsch
Date: Sun Jun 26 09:34:01 2011
New Revision: 1139748

URL: http://svn.apache.org/viewvc?rev=1139748&view=rev
Log:
[ESME-350] Add DOAP File to site

Added:
    esme/site/trunk/doap/
    esme/site/trunk/doap/doap_ESME.rdf
    esme/site/trunk/doap/esme.rdf

Added: esme/site/trunk/doap/doap_ESME.rdf
URL: http://svn.apache.org/viewvc/esme/site/trunk/doap/doap_ESME.rdf?rev=1139748&view=auto
==============================================================================
--- esme/site/trunk/doap/doap_ESME.rdf (added)
+++ esme/site/trunk/doap/doap_ESME.rdf Sun Jun 26 09:34:01 2011
@@ -0,0 +1,53 @@
+<?xml version="1.0"?>
+<?xml-stylesheet type="text/xsl"?>
+<rdf:RDF xml:lang="en"
+         xmlns="http://usefulinc.com/ns/doap#" 
+         xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
+         xmlns:asfext="http://projects.apache.org/ns/asfext#"
+         xmlns:foaf="http://xmlns.com/foaf/0.1/">
+<!--
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+   
+         http://www.apache.org/licenses/LICENSE-2.0
+   
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+  <Project rdf:about="http://esme.apache.org">
+    <created>2011-06-21</created>
+    <license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />
+    <name>Apache ESME</name>
+    <homepage rdf:resource="http://esme.apache.org" />
+    <asfext:pmc rdf:resource="http://dl.dropbox.com/u/24055733/esme.rdf" />
+    <shortdesc>Apache ESME (Enterprise Social Messaging Environment) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context.   </shortdesc>
+    <description>Apache ESME (Enterprise Social Messaging Environment) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context.   
+You can hardly turn a web page these days without seeing a story that describes how people are using social networks, whether it is Twitter, Facebook or some other service to develop and build their personal communities. In business, we increasingly see blogs and wikis demonstrating utility in problem solving and communications but the real time nature of business process problem solving largely remains untouched by social networking tools. Existing services, while attractive do not scale well and have proven unreliable. This is unacceptable to business which must be 'Always On' and able to support people in their daily working lives. Such applications must therefore be scalable and reliable but also provide a lot more.
+When solving problems, how good might it be if a user was able to tap into the collective knowledge of her peers or surrounding groups of people with whom she might naturally network in the workplace setting? How much quicker and with greater precision might she be able to solve daily problems? What if there was a communications mechanism that takes the best of what services like Twitter offers and co-mingled that with readily recognizable business processes? That solution is Apache ESME.</description>
+    <bug-database rdf:resource="https://issues.apache.org/jira/browse/ESME" />
+    <download-page rdf:resource="http://svn.apache.org/repos/asf/esme/" />
+    <programming-language>Scala</programming-language>
+    <category rdf:resource="http://projects.apache.org/category/content" />
+    <release>
+      <Version>
+        <name>esme-1.2</name>
+        <created>2011-03-04</created>
+        <revision>1.2</revision>
+      </Version>
+    </release>
+    <repository>
+      <SVNRepository>
+        <location rdf:resource="http://svn.apache.org/repos/asf/esme"/>
+        <browse rdf:resource="http://svn.apache.org/viewvc/esme/"/>
+      </SVNRepository>
+    </repository>
+    <maintainer rdf:resource="http://www.dakoller.net/foaf.rdf#me"/>
+  </Project>
+</rdf:RDF>

Added: esme/site/trunk/doap/esme.rdf
URL: http://svn.apache.org/viewvc/esme/site/trunk/doap/esme.rdf?rev=1139748&view=auto
==============================================================================
--- esme/site/trunk/doap/esme.rdf (added)
+++ esme/site/trunk/doap/esme.rdf Sun Jun 26 09:34:01 2011
@@ -0,0 +1,160 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<rdf:RDF xml:lang="en"
+         xmlns="http://usefulinc.com/ns/doap#" 
+         xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
+         xmlns:asfext="http://projects.apache.org/ns/asfext#"
+         xmlns:foaf="http://xmlns.com/foaf/0.1/">
+  <asfext:PMC rdf:about="esme">
+    <asfext:name>Apache ESME</asfext:name>
+    <asfext:chair>
+        <foaf:Person>
+            <foaf:name>Richard Hirsch</foaf:name>
+            <foaf:holdsAccount>
+                <foaf:OnlineAccount>
+                    <foaf:accountServiceHomepage>http://twitter.com/</foaf:accountServiceHomepage>
+                    <foaf:accountName>rhirsch</foaf:accountName>
+                </foaf:OnlineAccount>
+            </foaf:holdsAccount>
+        </foaf:Person>
+    </asfext:chair>
+    <asfext:member>
+        <foaf:Person>
+            <foaf:name>Anne Kathrine Petterøe</foaf:name>
+            <foaf:holdsAccount>
+                <foaf:OnlineAccount>
+                    <foaf:accountServiceHomepage>http://twitter.com/</foaf:accountServiceHomepage>
+                    <foaf:accountName>akPetteroe</foaf:accountName>
+                </foaf:OnlineAccount>
+            </foaf:holdsAccount>
+        </foaf:Person>
+    </asfext:member>
+    <asfext:member>
+        <foaf:Person>
+            <foaf:name>Bertrand Delacretaz</foaf:name>
+            <foaf:holdsAccount>
+                <foaf:OnlineAccount>
+                    <foaf:accountServiceHomepage>http://twitter.com/</foaf:accountServiceHomepage>
+                    <foaf:accountName>bdelacretaz</foaf:accountName>
+                </foaf:OnlineAccount>
+            </foaf:holdsAccount>
+        </foaf:Person>
+    </asfext:member>
+    <asfext:member>
+        <foaf:Person>
+            <foaf:name>Darren Hague</foaf:name>
+            <foaf:holdsAccount>
+                <foaf:OnlineAccount>
+                    <foaf:accountServiceHomepage>http://twitter.com/</foaf:accountServiceHomepage>
+                    <foaf:accountName>dhague</foaf:accountName>
+                </foaf:OnlineAccount>
+            </foaf:holdsAccount>
+        </foaf:Person>
+    </asfext:member>
+    <asfext:member>
+        <foaf:Person>
+            <foaf:name>Daniel Kulp</foaf:name>
+            <foaf:holdsAccount>
+                <foaf:OnlineAccount>
+                    <foaf:accountServiceHomepage>http://twitter.com/</foaf:accountServiceHomepage>
+                    <foaf:accountName>dkulp</foaf:accountName>
+                </foaf:OnlineAccount>
+            </foaf:holdsAccount>
+        </foaf:Person>
+    </asfext:member>
+    <asfext:member>
+        <foaf:Person>
+            <foaf:name>Ethan Jewett</foaf:name>
+            <foaf:holdsAccount>
+                <foaf:OnlineAccount>
+                    <foaf:accountServiceHomepage>http://twitter.com/</foaf:accountServiceHomepage>
+                    <foaf:accountName>esjewett</foaf:accountName>
+                </foaf:OnlineAccount>
+            </foaf:holdsAccount>
+        </foaf:Person>
+    </asfext:member>
+    <asfext:member>
+        <foaf:Person>
+            <foaf:name>J. Aaron Farr</foaf:name>
+            <foaf:holdsAccount>
+                <foaf:OnlineAccount>
+                    <foaf:accountServiceHomepage>http://twitter.com/</foaf:accountServiceHomepage>
+                    <foaf:accountName>farra</foaf:accountName>
+                </foaf:OnlineAccount>
+            </foaf:holdsAccount>
+        </foaf:Person>
+    </asfext:member>
+    <asfext:member>
+        <foaf:Person>
+            <foaf:name>Gianugo Rabellino</foaf:name>
+            <foaf:holdsAccount>
+                <foaf:OnlineAccount>
+                    <foaf:accountServiceHomepage>http://twitter.com/</foaf:accountServiceHomepage>
+                    <foaf:accountName>gianugo</foaf:accountName>
+                </foaf:OnlineAccount>
+            </foaf:holdsAccount>
+        </foaf:Person>
+    </asfext:member>
+    <asfext:member>
+        <foaf:Person>
+            <foaf:name>Mrinal Wadhwa</foaf:name>
+            <foaf:holdsAccount>
+                <foaf:OnlineAccount>
+                    <foaf:accountServiceHomepage>http://twitter.com/</foaf:accountServiceHomepage>
+                    <foaf:accountName>mrinal</foaf:accountName>
+                </foaf:OnlineAccount>
+            </foaf:holdsAccount>
+        </foaf:Person>
+    </asfext:member>
+    <asfext:member>
+        <foaf:Person>
+            <foaf:name>Imitiaz Ahmed H E</foaf:name>
+            <foaf:holdsAccount>
+                <foaf:OnlineAccount>
+                    <foaf:accountServiceHomepage>http://twitter.com/</foaf:accountServiceHomepage>
+                    <foaf:accountName>imitiaz</foaf:accountName>
+                </foaf:OnlineAccount>
+            </foaf:holdsAccount>
+        </foaf:Person>
+    </asfext:member>
+    <asfext:member>
+        <foaf:Person>
+            <foaf:name>Syllvain Wallez</foaf:name>
+            <foaf:holdsAccount>
+                <foaf:OnlineAccount>
+                    <foaf:accountServiceHomepage>http://twitter.com/</foaf:accountServiceHomepage>
+                    <foaf:accountName>sylvain</foaf:accountName>
+                </foaf:OnlineAccount>
+            </foaf:holdsAccount>
+        </foaf:Person>
+    </asfext:member>
+    <asfext:member>
+        <foaf:Person>
+            <foaf:name>Vladimir Ivanov</foaf:name>
+            <foaf:holdsAccount>
+                <foaf:OnlineAccount>
+                    <foaf:accountServiceHomepage>http://twitter.com/</foaf:accountServiceHomepage>
+                    <foaf:accountName>lester</foaf:accountName>
+                </foaf:OnlineAccount>
+            </foaf:holdsAccount>
+        </foaf:Person>
+    </asfext:member>
+    <asfext:member>
+        <foaf:Person>
+            <foaf:name>Vassil Dichev</foaf:name>
+            <foaf:holdsAccount>
+                <foaf:OnlineAccount>
+                    <foaf:accountServiceHomepage>http://twitter.com/</foaf:accountServiceHomepage>
+                    <foaf:accountName>vdichev</foaf:accountName>
+                </foaf:OnlineAccount>
+            </foaf:holdsAccount>
+        </foaf:Person>
+    </asfext:member>
+    
+    
+    <asfext:charter>Apache ESME (Enterprise Social Messaging Environment) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context.   
+You can hardly turn a web page these days without seeing a story that describes how people are using social networks, whether it is Twitter, Facebook or some other service to develop and build their personal communities. In business, we increasingly see blogs and wikis demonstrating utility in problem solving and communications but the real time nature of business process problem solving largely remains untouched by social networking tools. Existing services, while attractive do not scale well and have proven unreliable. This is unacceptable to business which must be 'Always On' and able to support people in their daily working lives. Such applications must therefore be scalable and reliable but also provide a lot more.
+When solving problems, how good might it be if a user was able to tap into the collective knowledge of her peers or surrounding groups of people with whom she might naturally network in the workplace setting? How much quicker and with greater precision might she be able to solve daily problems? What if there was a communications mechanism that takes the best of what services like Twitter offers and co-mingled that with readily recognizable business processes? That solution is Apache ESME.
+    </asfext:charter>
+  </asfext:PMC>
+</rdf:RDF>
+