Hi Yaron, thanks for your reply.
I am saying indeed there's a /very very good reason/ to install both
Cargo and SMW, today.
Several persons asked about any use case that might exist, today, for a
Cargo+SMW wiki
... I've identified a valuable, important service that Cargo provides
that SMW does not
... thank you for developing Cargo for this reason!
Thanks also for the comment about Wikibase - I didnt think much about
Cargo vs Wikibase until last night
I note that Cargo+Wikibase makes sense for the very same reason: silo
integration
... though I do now think Cargo is more a Wikibase competitor (in
monolingual wikis), given neither supports ontologies.
... soon, SMW's direct support for ontologies will be a crystal clear
difference SMW enjoys in future software comparisons!
cheers/john
------------------------------------------------------------------------
On 1/16/2015 2:29 PM, Yaron Koren wrote:
Hi John,
I'm not going to answer the use case question, since I'm not sure that
any good can come of answering it. :) If you want to provide your own
answer to the question, that's fine.
As for Wikibase, there's no shared code between Cargo between
Wikibase; and there's no relationship between them, other than both
having in some sense been inspired by SMW.
-Yaron
On Fri, Jan 16, 2015 at 3:58 PM, John McClure <jmccl...@hypergrove.com
<mailto:jmccl...@hypergrove.com>> wrote:
Hello Yaron,
Funny, but I've not seen any use case detailed for the Cargo
extension.
Eliminating (what is perceived) to be SMW's code complexity, is
*not* a use case per se.
*Use Case. ...*a list of steps, typically defining
interactions between a role... and a system, to achieve a goal.
So I think of two use cases for which Cargo is a candidate solution
1. An organization does /not/ want to install SMW, but wants to
query structured wikipage content
2. An organizaton wants to interface separate SQL database
applications, one being MW with structured content
The first use case is not directly interesting to the SMW community
-- although it IS of real interest that stable & supported
Wikibase is not ever noted as a competitive solution
-- and why/whether Wikibase query printers (or any other modules)
have any relationship to Cargo
The second use case gets to headaches with silo-ed systems, that
is, systems not sharing a common repository
-- enter data to system A, a/synchronously update system B, and
vice versa
-- change system A data stored in system B, a/synchronously update
system A, and vice versa
It's the "a/synchronously update..." part that is a hair-pulling
pain in the arse for IT depts, right?
therefore
---> Cargo creates & maintains a common repository between
otherwise silo-ed applications
So, is this a (or, the /only/) use case for Cargo being installed
alongside SMW?
And, please, is there a relationship between Cargo & Wikibase?
thanks for comments/john
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
