[SMW-devel] Results of the first day of SMWCon

2012-11-16 Thread Yury Katkov
Hi everyone!

You can now watch all the talks that were on the first day of SMWCon.

http://www.youtube.com/playlist?list=PLwtfwT1GnUQRaLki-YcF-_n8ndayi--W5

Here is a small summary for those who haven't been at the event.

  The day have begun with magnificent talk about Wikidata from its
project leader, Denny Vrandečić. In some sense Wikidata implements the
original vision of SMW and make the Wikipedia semantically annotated.

  We next had three sessions.

  First one was pretty technical and was dedicated mostly to
performance issues: after the traditional talk about the current state
of the project by Markus and Jeroen, Nischay told about the new
storage meschnism in SMW. Then Eloy describes how SMW is used in Wikia
and what benefits it gives to the wiki-owners and what problems it
sometimes caused.
  Second session was not about SMW but about the other wiki engines
that have similar functions. OntoWiki that separates the text and the
semantic annotations is used by AKSW laboratory for a lot of Linked
Data projects. BlueSpice, an extension bundle to make MediaWiki more
user-friendly and ready-to-use in the enterprises. KWARC tools that
allows to include machine-readable data to the mathematical content.
There are a lot of things SMW community can learn from these great
tools.
  Third session was dedicated to SMW applications in different
domains. We've seen how SMW helps people to support structured
discussion about the ontology objects (Cicero system). The other talk
was about using enhanced SMW for synchronizing the long-term
strategies of organizations to design the common future (Foresight
creation). Benedikt shows how to apply the platform for financial
analysis of a small organization. Finally Remco presented the case of
government application of SMW (Architectural Knowledge).

Ask questions here and on the talk's pages!
Cheers,
-
Yury Katkov, WikiVote

--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


[SMW-devel] s13n stands for semantification

2012-11-16 Thread Yury Katkov
Hi everyone!

I talked about the topic of semanticfication of the MediaWiki
extension with a lot of people in SMWCon and saw the great interest to
this topic.

We have tried to describe the problem on this page:
http://semantic-mediawiki.org/wiki/User:Yury_Katkov/s13n_stands_for_semantification

To the users: if you're interested in topics of s13n and have the use
case that is not described there - please describe it.

To the developers: let's think together what's needed to be done in
the SMW core to make s13n of the extensions cleaner and easier. Also
the rough time/effort  estimate would be great (maybe SMW companies
can sponsor the development?)

Cheers,
Yury Katkov, WikiVote

--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


Re: [SMW-devel] s13n stands for semantification

2012-11-16 Thread Markus Krötzsch
On 16/11/12 11:27, Yury Katkov wrote:
 Hi everyone!

 I talked about the topic of semanticfication of the MediaWiki
 extension with a lot of people in SMWCon and saw the great interest to
 this topic.

 We have tried to describe the problem on this page:
 http://semantic-mediawiki.org/wiki/User:Yury_Katkov/s13n_stands_for_semantification

 To the users: if you're interested in topics of s13n and have the use
 case that is not described there - please describe it.

 To the developers: let's think together what's needed to be done in
 the SMW core to make s13n of the extensions cleaner and easier. Also
 the rough time/effort  estimate would be great (maybe SMW companies
 can sponsor the development?)

I have discussed this already with Jeroen. We can help to provide an 
infrastructure for this. However, the access paths for enabling 
efficient #ask queries are different from the traditional MW access 
paths to metadata, so all data that is to be s8ed (;-) will need to be 
replicated in SMW tables, even if the same MySQL DB is used.

Cheers,

Markus


 Cheers,
 Yury Katkov, WikiVote

 --
 Monitor your physical, virtual and cloud infrastructure from a single
 web console. Get in-depth insight into apps, servers, databases, vmware,
 SAP, cloud infrastructure, etc. Download 30-day Free Trial.
 Pricing starts from $795 for 25 servers or applications!
 http://p.sf.net/sfu/zoho_dev2dev_nov
 ___
 Semediawiki-devel mailing list
 Semediawiki-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/semediawiki-devel



--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


Re: [SMW-devel] s13n stands for semantification

2012-11-16 Thread Yury Katkov
Hi Markus!

That's very nice! How hard/long is that task?

We can now use something like SMWStore::updateDataBefore hook, but not
good approach sometimes: with voting and history s13n you'll need to
create a lot of property values each time the data is updated.  When
you semantify the page history you'll need to create several hundreds
datavalues representing the revisions of the current page - that's too
exprensive.

-
Yury Katkov, WikiVote



On Fri, Nov 16, 2012 at 4:34 PM, Markus Krötzsch
mar...@semantic-mediawiki.org wrote:
 On 16/11/12 11:27, Yury Katkov wrote:

 Hi everyone!

 I talked about the topic of semanticfication of the MediaWiki
 extension with a lot of people in SMWCon and saw the great interest to
 this topic.

 We have tried to describe the problem on this page:

 http://semantic-mediawiki.org/wiki/User:Yury_Katkov/s13n_stands_for_semantification

 To the users: if you're interested in topics of s13n and have the use
 case that is not described there - please describe it.

 To the developers: let's think together what's needed to be done in
 the SMW core to make s13n of the extensions cleaner and easier. Also
 the rough time/effort  estimate would be great (maybe SMW companies
 can sponsor the development?)


 I have discussed this already with Jeroen. We can help to provide an
 infrastructure for this. However, the access paths for enabling efficient
 #ask queries are different from the traditional MW access paths to metadata,
 so all data that is to be s8ed (;-) will need to be replicated in SMW
 tables, even if the same MySQL DB is used.

 Cheers,

 Markus


 Cheers,
 Yury Katkov, WikiVote


 --
 Monitor your physical, virtual and cloud infrastructure from a single
 web console. Get in-depth insight into apps, servers, databases, vmware,
 SAP, cloud infrastructure, etc. Download 30-day Free Trial.
 Pricing starts from $795 for 25 servers or applications!
 http://p.sf.net/sfu/zoho_dev2dev_nov
 ___
 Semediawiki-devel mailing list
 Semediawiki-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/semediawiki-devel



--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


Re: [SMW-devel] s13n stands for semantification

2012-11-16 Thread Nischay Nahata
Hi Yury,

On Fri, Nov 16, 2012 at 8:02 PM, Yury Katkov katkov.ju...@gmail.com wrote:

 Hi Markus!

 That's very nice! How hard/long is that task?

 We can now use something like SMWStore::updateDataBefore hook, but not
 good approach sometimes: with voting and history s13n you'll need to
 create a lot of property values each time the data is updated.  When
 you semantify the page history you'll need to create several hundreds
 datavalues representing the revisions of the current page - that's too
 exprensive.


The update of data can take long if there are way too many properties, but
I think they will do fine with
about 10-15 on each page edit. More experienced developers will know more :)

What do you mean by semantify the page history? Is this a ask query that
shows up history?


 -
 Yury Katkov, WikiVote



 On Fri, Nov 16, 2012 at 4:34 PM, Markus Krötzsch
 mar...@semantic-mediawiki.org wrote:
  On 16/11/12 11:27, Yury Katkov wrote:
 
  Hi everyone!
 
  I talked about the topic of semanticfication of the MediaWiki
  extension with a lot of people in SMWCon and saw the great interest to
  this topic.
 
  We have tried to describe the problem on this page:
 
 
 http://semantic-mediawiki.org/wiki/User:Yury_Katkov/s13n_stands_for_semantification
 
  To the users: if you're interested in topics of s13n and have the use
  case that is not described there - please describe it.
 
  To the developers: let's think together what's needed to be done in
  the SMW core to make s13n of the extensions cleaner and easier. Also
  the rough time/effort  estimate would be great (maybe SMW companies
  can sponsor the development?)
 
 
  I have discussed this already with Jeroen. We can help to provide an
  infrastructure for this. However, the access paths for enabling efficient
  #ask queries are different from the traditional MW access paths to
 metadata,
  so all data that is to be s8ed (;-) will need to be replicated in SMW
  tables, even if the same MySQL DB is used.
 
  Cheers,
 
  Markus
 
 
  Cheers,
  Yury Katkov, WikiVote
 
 
 
 --
  Monitor your physical, virtual and cloud infrastructure from a single
  web console. Get in-depth insight into apps, servers, databases, vmware,
  SAP, cloud infrastructure, etc. Download 30-day Free Trial.
  Pricing starts from $795 for 25 servers or applications!
  http://p.sf.net/sfu/zoho_dev2dev_nov
  ___
  Semediawiki-devel mailing list
  Semediawiki-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
 
 


 --
 Monitor your physical, virtual and cloud infrastructure from a single
 web console. Get in-depth insight into apps, servers, databases, vmware,
 SAP, cloud infrastructure, etc. Download 30-day Free Trial.
 Pricing starts from $795 for 25 servers or applications!
 http://p.sf.net/sfu/zoho_dev2dev_nov
 ___
 Semediawiki-devel mailing list
 Semediawiki-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/semediawiki-devel




-- 
Cheers,

Nischay Nahata
nischayn22.in
--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


Re: [SMW-devel] [Semediawiki-user] s13n stands for semantification

2012-11-16 Thread Markus Krötzsch
On 16/11/12 14:32, Yury Katkov wrote:
 Hi Markus!

 That's very nice! How hard/long is that task?

Unknown. First we need to decide what we want to have.


 We can now use something like SMWStore::updateDataBefore hook, but not
 good approach sometimes: with voting and history s13n you'll need to
 create a lot of property values each time the data is updated.  When
 you semantify the page history you'll need to create several hundreds
 datavalues representing the revisions of the current page - that's too
 exprensive.

The idea was to have data that is not governed by page updates. There 
are two basic designs:

(1) We introduce something like named graphs. All data belongs to a 
graph. Only data in the default graph is updated with the page contents; 
other writing methods are provided for the rest. Maximally flexible, but 
some storage overhead.

(2) We do not use graphs but bind this information to properties: some 
properties are governed by page contents, other properties are governed 
in other ways. Less flexible, but no storage overhead.

Cheers,

Markus


 -
 Yury Katkov, WikiVote



 On Fri, Nov 16, 2012 at 4:34 PM, Markus Krötzsch
 mar...@semantic-mediawiki.org wrote:
 On 16/11/12 11:27, Yury Katkov wrote:

 Hi everyone!

 I talked about the topic of semanticfication of the MediaWiki
 extension with a lot of people in SMWCon and saw the great interest to
 this topic.

 We have tried to describe the problem on this page:

 http://semantic-mediawiki.org/wiki/User:Yury_Katkov/s13n_stands_for_semantification

 To the users: if you're interested in topics of s13n and have the use
 case that is not described there - please describe it.

 To the developers: let's think together what's needed to be done in
 the SMW core to make s13n of the extensions cleaner and easier. Also
 the rough time/effort  estimate would be great (maybe SMW companies
 can sponsor the development?)


 I have discussed this already with Jeroen. We can help to provide an
 infrastructure for this. However, the access paths for enabling efficient
 #ask queries are different from the traditional MW access paths to metadata,
 so all data that is to be s8ed (;-) will need to be replicated in SMW
 tables, even if the same MySQL DB is used.

 Cheers,

 Markus


 Cheers,
 Yury Katkov, WikiVote


 --
 Monitor your physical, virtual and cloud infrastructure from a single
 web console. Get in-depth insight into apps, servers, databases, vmware,
 SAP, cloud infrastructure, etc. Download 30-day Free Trial.
 Pricing starts from $795 for 25 servers or applications!
 http://p.sf.net/sfu/zoho_dev2dev_nov
 ___
 Semediawiki-devel mailing list
 Semediawiki-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/semediawiki-devel



 --
 Monitor your physical, virtual and cloud infrastructure from a single
 web console. Get in-depth insight into apps, servers, databases, vmware,
 SAP, cloud infrastructure, etc. Download 30-day Free Trial.
 Pricing starts from $795 for 25 servers or applications!
 http://p.sf.net/sfu/zoho_dev2dev_nov
 ___
 Semediawiki-user mailing list
 semediawiki-u...@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/semediawiki-user



--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


Re: [SMW-devel] s13n stands for semantification

2012-11-16 Thread Yury Katkov
s13n of page history is just converting all revision data into
properties and subobjects. Many promising usecases have been show in
Semantic History extension:
http://tw.rpi.edu/proj/semhis.wiki/index.php/Main_Page
Here are some examples of questions that can be answered with s13n of history:

- Show me the edits made by postdocs
- Show me the edits that were commented as 'style improvement'
- Who has changed the first name of James Hendler?
- What kind of properties do users from Category:Developers change mostly?


-
Yury Katkov, WikiVote



On Fri, Nov 16, 2012 at 7:24 PM, Nischay Nahata nischay...@gmail.com wrote:

 Hi Yury,

 On Fri, Nov 16, 2012 at 8:02 PM, Yury Katkov katkov.ju...@gmail.com wrote:

 Hi Markus!

 That's very nice! How hard/long is that task?

 We can now use something like SMWStore::updateDataBefore hook, but not
 good approach sometimes: with voting and history s13n you'll need to
 create a lot of property values each time the data is updated.  When
 you semantify the page history you'll need to create several hundreds
 datavalues representing the revisions of the current page - that's too
 exprensive.


 The update of data can take long if there are way too many properties, but I
 think they will do fine with
 about 10-15 on each page edit. More experienced developers will know more :)

 What do you mean by semantify the page history? Is this a ask query that
 shows up history?


 -
 Yury Katkov, WikiVote



 On Fri, Nov 16, 2012 at 4:34 PM, Markus Krötzsch
 mar...@semantic-mediawiki.org wrote:
  On 16/11/12 11:27, Yury Katkov wrote:
 
  Hi everyone!
 
  I talked about the topic of semanticfication of the MediaWiki
  extension with a lot of people in SMWCon and saw the great interest to
  this topic.
 
  We have tried to describe the problem on this page:
 
 
  http://semantic-mediawiki.org/wiki/User:Yury_Katkov/s13n_stands_for_semantification
 
  To the users: if you're interested in topics of s13n and have the use
  case that is not described there - please describe it.
 
  To the developers: let's think together what's needed to be done in
  the SMW core to make s13n of the extensions cleaner and easier. Also
  the rough time/effort  estimate would be great (maybe SMW companies
  can sponsor the development?)
 
 
  I have discussed this already with Jeroen. We can help to provide an
  infrastructure for this. However, the access paths for enabling
  efficient
  #ask queries are different from the traditional MW access paths to
  metadata,
  so all data that is to be s8ed (;-) will need to be replicated in SMW
  tables, even if the same MySQL DB is used.
 
  Cheers,
 
  Markus
 
 
  Cheers,
  Yury Katkov, WikiVote
 
 
 
  --
  Monitor your physical, virtual and cloud infrastructure from a single
  web console. Get in-depth insight into apps, servers, databases,
  vmware,
  SAP, cloud infrastructure, etc. Download 30-day Free Trial.
  Pricing starts from $795 for 25 servers or applications!
  http://p.sf.net/sfu/zoho_dev2dev_nov
  ___
  Semediawiki-devel mailing list
  Semediawiki-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
 
 


 --
 Monitor your physical, virtual and cloud infrastructure from a single
 web console. Get in-depth insight into apps, servers, databases, vmware,
 SAP, cloud infrastructure, etc. Download 30-day Free Trial.
 Pricing starts from $795 for 25 servers or applications!
 http://p.sf.net/sfu/zoho_dev2dev_nov
 ___
 Semediawiki-devel mailing list
 Semediawiki-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/semediawiki-devel




 --
 Cheers,

 Nischay Nahata
 nischayn22.in

--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


Re: [SMW-devel] [Semediawiki-user] s13n stands for semantification

2012-11-16 Thread Yury Katkov
Hi!
Can you clarify the idea of named graphs a little bit? And what
storage overhead we have in them?
-
Yury Katkov, WikiVote



On Fri, Nov 16, 2012 at 7:33 PM, Markus Krötzsch
mar...@semantic-mediawiki.org wrote:
 On 16/11/12 14:32, Yury Katkov wrote:

 Hi Markus!

 That's very nice! How hard/long is that task?


 Unknown. First we need to decide what we want to have.



 We can now use something like SMWStore::updateDataBefore hook, but not
 good approach sometimes: with voting and history s13n you'll need to
 create a lot of property values each time the data is updated.  When
 you semantify the page history you'll need to create several hundreds
 datavalues representing the revisions of the current page - that's too
 exprensive.


 The idea was to have data that is not governed by page updates. There are
 two basic designs:

 (1) We introduce something like named graphs. All data belongs to a graph.
 Only data in the default graph is updated with the page contents; other
 writing methods are provided for the rest. Maximally flexible, but some
 storage overhead.

 (2) We do not use graphs but bind this information to properties: some
 properties are governed by page contents, other properties are governed in
 other ways. Less flexible, but no storage overhead.

 Cheers,

 Markus


 -
 Yury Katkov, WikiVote



 On Fri, Nov 16, 2012 at 4:34 PM, Markus Krötzsch
 mar...@semantic-mediawiki.org wrote:

 On 16/11/12 11:27, Yury Katkov wrote:


 Hi everyone!

 I talked about the topic of semanticfication of the MediaWiki
 extension with a lot of people in SMWCon and saw the great interest to
 this topic.

 We have tried to describe the problem on this page:


 http://semantic-mediawiki.org/wiki/User:Yury_Katkov/s13n_stands_for_semantification

 To the users: if you're interested in topics of s13n and have the use
 case that is not described there - please describe it.

 To the developers: let's think together what's needed to be done in
 the SMW core to make s13n of the extensions cleaner and easier. Also
 the rough time/effort  estimate would be great (maybe SMW companies
 can sponsor the development?)



 I have discussed this already with Jeroen. We can help to provide an
 infrastructure for this. However, the access paths for enabling efficient
 #ask queries are different from the traditional MW access paths to
 metadata,
 so all data that is to be s8ed (;-) will need to be replicated in SMW
 tables, even if the same MySQL DB is used.

 Cheers,

 Markus


 Cheers,
 Yury Katkov, WikiVote



 --
 Monitor your physical, virtual and cloud infrastructure from a single
 web console. Get in-depth insight into apps, servers, databases, vmware,
 SAP, cloud infrastructure, etc. Download 30-day Free Trial.
 Pricing starts from $795 for 25 servers or applications!
 http://p.sf.net/sfu/zoho_dev2dev_nov
 ___
 Semediawiki-devel mailing list
 Semediawiki-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/semediawiki-devel




 --
 Monitor your physical, virtual and cloud infrastructure from a single
 web console. Get in-depth insight into apps, servers, databases, vmware,
 SAP, cloud infrastructure, etc. Download 30-day Free Trial.
 Pricing starts from $795 for 25 servers or applications!
 http://p.sf.net/sfu/zoho_dev2dev_nov
 ___
 Semediawiki-user mailing list
 semediawiki-u...@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/semediawiki-user



--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


Re: [SMW-devel] [Semediawiki-user] s13n stands for semantification

2012-11-16 Thread Jeroen De Dauw
Hey,

Can you clarify the idea of named graphs a little bit? And what
 storage overhead we have in them?


Instead of having rows such as

( subject id, property id, value )

in the store, you instead have

( subject id, property id, value, graph id )

Of course our schema is more complex then this, but it's the same idea.

Cheers

--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


[SMW-devel] SMW devs - Boston Area - We're hiring!

2012-11-16 Thread Thomas Fellows
Hey everyone,

First, I apologize for the spam, and the duplicate from the Wikitech list,
so I'll keep it short - We're a Cambridge, MA based firm that's looking to
change the world (yay!), and have 2 openings on our development team.  We
are developing all sorts of extensions for MediaWiki (and SMW!), and are
looking to expand our team before our international launch!

The full job listing with more detailed info:
http://boston.craigslist.org/gbs/sof/3398038106.html

And if you have any questions or want further information just send me an
email!

Thanks,

Tom
--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel