I am busy upgrading SMW 1.9.2 to version 2.2. How do I know which version to use of the accompanying extensions like Semantic Forms or Semantic Extra Special Properties?
As you can see at the SMW docs:
Various MediaWiki extensions are available for further extending
Semantic MediaWiki with additional functionality, and some basic
extensions of MediaWiki are generally useful for employing SMW.
Most extensions are not maintained by the SMW Project. Please see the
extension's main page and installation files to find out whom to
contact for support and where to report bugs. Questions related to
these extensions can be discussed on the mailing list or forum for the
extension (where specified), or on the Semantic MediaWiki user mailing
list.
So, in case that you don't find the relation between your SMW version and the version of each extension in the Semantic MediaWiki user mailing list or the forum for the extension, you should look at the official docs for every extension or contact the developers of each extension, as there is not official reference about the relation you're looking for.
Related
I am creating a site under mediawiki. Is there a feature or an extension to know for a version which users have contributed to this version and in what proportion? For example, for the article on new-york in wikipedia, know the list of contributors of this version and in what proportion did they participate?
prop=contributors. See the contributors API doc page for details.
Your question mainly seems to be about Wikipedia, which has a tool for this:
https://xtools.wmflabs.org/articleinfo
For your specific example, the link is:
https://xtools.wmflabs.org/articleinfo/fr.wikipedia.org/New%20York
The tool, XTools, is open source and may be useful for other MediaWiki installations as well:
https://github.com/x-tools/xtools
The license of Schema.org is Creative Commons Attribution-ShareAlike License (version 3.0).
Does this mean that any search engine can use Schema.org to implement structure data?
See the FAQ Under what terms can we re-use this documentation (and schemas, examples, software)?
As noted in our terms of service document, schema.org schemas are made available under the Creative Commons Attribution-ShareAlike License (version 3.0). These terms also apply to the supporting documentation on this site and on our blog, as well as to the markup examples used in this site. The software used for our site is also available for opensource re-use under an Apache 2 license. If you have feedback on these terms please get in touch.
Depending on your meaning of "use schema.org", it might be that your search engine doesn’t have to follow the license.
For example, if you parse HTML documents, find Schema.org markup, and interpret it according to the Schema.org definitions, you don’t have to license/attribute anything.
However, if you include definitions/examples (taken from schema.org) on your search engine’s documentation site, you have to license it under CC BY-SA 3.0 and attribute accordingly.
Yes, it means you can use its content, and modify without delete the maker name (or whatever), and share it.
But you can't use it for commercial purpose.
Schema.org is released with the Apache License Version 2.0, you can have a look at it in the development repo: https://github.com/schemaorg/schemaorg/blob/sdo-deimos/LICENSE
You can also check What are the real life implications for an Apache 2 license?
We're upgrading from Semantic MediaWiki 1.9.2 to version 2.2 and will no longer use the Semantic Bundle.
So we no longer include SemanticBundleSettings.php and SemanticBundle.php in LocalSettings.php but use Composer and the vendor/autoload.php.
The Special:Version page shows the correct version and most things seem to work well but there are some issues.
For example when editing a template this message appears: "This page is not enabled for semantic in-text annotations due to namespace restrictions. Details about how to enable the namespace is described on the configuration help page".
(assuming this has something to do with upgrading)
My question: is there some roadmap to upgrade in a structured way rather then trial-and-error?
I've read Upgrade from SMW 1.9+ for MW 1.22+ and the release notes for SMW 2.0 but this does not give me enough information.
I'm running my blog using Jekyll, and it is hosted on github.
My blogs are written in Chinese now, and I'm considering to write English version as well.
What is the best practice to support multi-language for the blogs so that readers can choose their preference language while reading?
There are many plugins available for this scenario but unfortunately GitHub-hosted Jekyll blogs do not support any plugins since GitHub has disabled them for safety's sake. But if you choose to manually build and publish to GitHub, here are some pointers.
The following plugins are compatible with Jekyll 2.x:
https://github.com/screeninteraction/jekyll-multiple-languages-plugin103
https://github.com/liaohuqiu/jekyll-multiple-languages97
https://github.com/drallgood/jekyll-multilingual150
I liked neither of those since I found them too restrictive so I have created a plugin compatible with Jekyll 3.0 and very easy to use:
https://github.com/vwochnik/jekyll-language-plugin
Of course, there are also approaches without any plugins, like the following:
https://www.sylvaindurand.org/making-jekyll-multilingual/
Is it possible to extend Media Wiki with semantic services using Apache Stanbol?
The Stanbol Website indicates that "any content repository compliant with JCR or CMIS specifications" can be used. However, I could not find whether this is the case for (Semantic) Media Wiki?
Usually both JCR and CMIS are protocols much more popular on Java environments. As far as I know MediaWiki does not support any of them.
However, you can still use Stanbol via its RESTful interfaces.