ng the essential API, due to the issues
that are the topic of this thread.
David
On Tue, 4 Sep 2018 at 20:08, Yaron Koren wrote:
> Hi,
>
> On Mon, Sep 3, 2018 at 12:13 PM david mason <
> vid_semediawiki-de...@zooid.org> wrote:
>
>> However, as Markus
>> identif
On Mon, 3 Sep 2018 at 09:58, Markus Krötzsch
wrote:
> I have asked this questions myself a lot when I was still the person
> that got such emails, and I have to admit that I do not have a good
> answer. The transition from a super-tiny/one-person dev team to a small
> size team (with a plan, and
I think some kind of survey should be done to see what aspects of the
'semantic web' people are interested in. We all know as a few-year project
intended to comprehensively remake the web SW failed, but it has many
significant aspects which are important in the long term that SMW purported
to
Hi all,
Maybe I am running with this, but it would benefit the community to make
these efforts generally reusable.
I understand SMW is no longer trying to fit into the Wikimedia universe,
but it still honours the MW approach of edits and source being human
parseable and benefits from ongoing MW
, arts and community groups, developers,
consultants, business representatives and researchers.
Organizing Committee
René Witte [General Chair]
David Mason [Program Chair]
Bahar Sateli [Local Chair]
Sponsors
Concordia University, Montréal, Canada
Faculty of Engineering and Computer Science
users contribute
* Modelling complex domains
* Access control and security aspects
* Multi-lingual and cross-lingual sites
Organizing Committee
René Witte [General Chair]
David Mason [Program Chair]
Bahar Sateli [Local Chair]
Sponsors
Concordia University, Montréal, Canada
Faculty of Engineering
complex domains
* Access control and security aspects
* Multi-lingual and cross-lingual sites
== Organizing Committee ==
* René Witte [General Chair]
* David Mason [Program Chair]
* Bahar Sateli [Local Chair]
== Sponsors ==
Concordia University, Montréal, Canada
Faculty of Engineering and Computer
another option is to explore something like nobackend (Hoodie).
http://nobackend.org/ http://nobackend.org/examples.html
the design is to support multiple storage storage 'backends,' one could be
added for SMW.
https://gist.github.com/gr2m/5463475
David
On 5 December 2013 06:13, Neill
While there is discussion of SRF graphs…
I hacked in support for dagre https://github.com/cpettitt/dagre graphs —
see https://wiki.deflect.ca/wiki/BotnetDBP#Diagram
this is a JavaScript implementation of graphviz style rendering. lots of
possibilities due to its browser based nature. this
With regard to ES and data recovery/transactions, if SMW continues to be
able to generate this data at any time it doesn't seem to be much of an
issue. ES is also horizontally scalable as one of its main features, and
supports geo features and advanced search, although graph traversal is
manual
May I suggest that ElasticSearch is considered instead of MongoDB.
ElasticSearch is the index engine of the new MediaWiki Search, so end users
won't need to set up and support multiple data stores. Like MongoDB it is a
document store that natively uses JSON, and is really easy to set up and
run
I would like to suggest that unit/functional/integration tests would be the
best solution for this. I know it's not easy to get into a testing culture,
but various projects including parts of SMW are adopting this. It solves
these problems:
1. provides clear examples of how to do things using SMW
12 matches
Mail list logo
