The on-wiki version of this newsletter can be found here:
https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Updates/2023-09-20
--
Renderers and parsers for types
Wikifunctions currently supports two types: Strings and Booleans. To make
Wikifunctions useful, we need to support many more types, such as numbers,
dates, geocoordinates, and eventually Wikidata lexemes and items. Types
define what kind of inputs and outputs the functions in Wikifunctions can
have.
With Wikifunctions, we don’t want to just repeat what different programming
languages have done, but, if possible, gently update the lessons that have
been learned from programming language research and experience and make
sure that we are as inclusive as possible.
Strings and Booleans were very carefully chosen for the first deployment of
Wikifunctions: Strings <https://www.wikifunctions.org/wiki/Z6>, because
they are just a specific sequence of Characters, and do not depend on the
user’s language. Booleans <https://www.wikifunctions.org/wiki/Z40>, because
they are a key basis of logic flow for programming. Further, they can be
fully translated in Wikifunctions – the two values, True
<https://www.wikifunctions.org/wiki/Z41> and False
<https://www.wikifunctions.org/wiki/Z42>, are both represented by a
Wikifunctions object that can have names in any of the languages we
support. Since the initial deployment, more than a dozen translations have
been added! If you can add more, that would be great.
One example of a possible next type that would be interesting to introduce
would be whole numbers. This raises a big question: how should we represent
an integer?
Most programming languages have two answers for that: one, they internally
represent it, usually, as a binary string of a specific length, in order to
efficiently store and process these numbers. But then there is also their
representation in the human-readable source code, and here they are usually
represented as a sequence of Arabic numerals
<https://en.wikipedia.org/wiki/Arabic_numerals>, e.g. 4657388. Some
programming languages are nice enough to allow for grouping of the numbers,
e.g. in Ada <https://en.wikipedia.org/wiki/Ada_(programming_language)> you
may write 4_657_388, or, if you prefer the Indian system
<https://en.wikipedia.org/wiki/Indian_numbering_system>, 46_57_388, making
these numbers a bit more readable.
But programming languages where one can write ৪৬,৫৭,৩৮৮ using Bengali
numerals <https://en.wikipedia.org/wiki/Bengali_numerals>, referring to the
same number, are rare <https://sjishan.github.io/chascript/>. For
Wikifunctions, we want to rectify this, to make sure that the whole system
supports every human language fluently and consistently.
Internally, we will represent numbers - like every other object - as
ZObjects. The above number would be represented internally as follows
(using the prototype ZID from the Beta
<https://wikifunctions.beta.wmflabs.org/view/en/Z10015>, since we don’t yet
have the respective type in the real Wikifunctions):
{ "Z1K1": "Z10015", "Z10015K1": "4657388"}
Or, with labels in English:
{ "type": "positive integer", "value": "4657388"}
Even though this solves the internal representation, we would want to avoid
displaying this object in the system if possible. Instead, we plan to allow
the Wikifunctions community to attach a 'renderer' and a 'parser' to each
type. The renderer would be a function that takes an object of the given
type (in this case, an object of the type positive integer) and a language,
and returns a string. The parser is the opposite of that: it takes a string
and a language, and returns an object of type positive integer.
This would allow the Wikifunctions community to create functions for each
type and language that would decide how the values of the type are going to
be displayed in the given language. In a Bengali interface, the above
number can then be displayed in the most natural representation for
Bengali, which might be ৪৬,৫৭,৩৮৮.
When entering a number, we will use the parsing function to turn the input
of the user into the internal representation. It is then up to the
community to decide how flexible they want to be: if they would only accept
৪৬,৫৭,৩৮৮ as the input, or whether ৪৬৫৭৩৮৮ would be just as good - or even
also or only 4657388. The decision would be for the Wikifunctions community
to make.
Note that we made a lot of assumptions in the above text. For example,
using the ZID from the Beta, calling the type “positive integer”, assuming
the internal representation of positive integers being Arabic numerals
without formatting (instead of say, hexadecimal, base 64 or a binary
number, which also could be good solutions), and other assumptions. All of
these decisions are up to you, but we used assumptions here to talk
concretely about the proposal.
We plan to implement this proposal incrementally, over a few weeks and
months. It will likely be the case that we will at first only accept the
internal representation (just as it currently works on the Beta), and that
we will then add renderers and finally parsers.
We are looking forward to hearing your feedback on this plan.
This edition of the newsletter can be found on-wiki here:
https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Updates/2023-09-08
--
Let’s start building morphological paradigms!
Morphological functions are functions that take one form of a word and
create a different form of the word that is required in order to follow
grammatical and semantic rules. For example, it might take a word such as
“letter” and return the plural form “letters”, or the present participle
“lettering”. We talked previously about morphological paradigms
<https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Updates/2021-09-10>,
about the need for both lexemes in Wikidata and paradigms in Wikifunctions
<https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Updates/2021-09-17>,
and about a tool to check lexemes and paradigms against each other
<https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Updates/2022-11-09>.
We think that Wikifunctions is now ready for us to start building functions
that support morphological paradigms! We would like to invite the different
language communities to join us at Wikifunctions and to start creating
functions that create lexical forms.
Here are a few examples of such functions from the Wikifunctions Beta:
-
English plural <https://wikifunctions.beta.wmflabs.org/view/en/Z10241>
-
French plural <https://wikifunctions.beta.wmflabs.org/view/en/Z10106>
-
Swedish genitive <https://wikifunctions.beta.wmflabs.org/view/en/Z10297>
-
German feminine plural
<https://wikifunctions.beta.wmflabs.org/view/en/Z10358>
-
Croatian feminine plural nominative
<https://wikifunctions.beta.wmflabs.org/view/en/Z10335>
In most cases, these functions would be taking a string and returning a
string (but there might be exceptions). The examples above illustrate two
kinds of case: functions which aim to work for all words of a given part of
speech (e.g. the English and French plural and the Swedish genitive, which
aims to work for any noun), and those that work for a subset of a given
part of speech (the examples cover German and Croatian feminine nouns, but
could be more complex, such as Zaliznyak’s classification of Russian nouns
<https://en.wikipedia.org/wiki/Andrey_Zaliznyak> or maybe also noun classes
in Niger-Congo languages).
The morphological paradigms will often not be complete inside
Wikifunctions. The idea is for exceptions to be caught by adding as forms
to the lexicographical knowledge in Wikidata. The functions are for the
reasonably regular forms and for the often generative rules agglutinative
languages (but what is a regular form and what is an exception is
something the given language community will need to figure out). We are
looking forward to communities to come together around the individual
languages and for morphologizers, sets of morphological paradigms for a
given language, to grow in Wikifunctions! We are particularly excited to
see how far these can be built in a given natural language, and how
autonomous the languages can become (and where they still depend on
understanding English) - and how much these functions will benefit across
languages. We also hope that capturing the paradigms can be a contribution
to language preservation and revitalization.
We are aware that the situation is not yet ideal for this call to action,
but we want to make this call sooner rather than later. We are actively
working on improving the situation. If you want to contribute to this
challenge, but don’t yet have functioneer rights, please apply here and
explain which language you plan to work on
<https://www.wikifunctions.org/wiki/Wikifunctions:Apply_for_editing>. We
will prioritize such applications. We are also aware that the current
limitation on function calls to logged-in users makes it difficult to demo
the functions and prevents it from integrating it into tools such as Form
Checker <https://williamavery.github.io/formcheck/> or Lucas Werkmeister’s
Wikidata Lexeme Forms <https://lexeme-forms.toolforge.org/>. We are
prioritizing resolving these issues.
Please reach out to us if you need help starting this effort for the
language you are interested in, or if you hit any stumbling blocks on the
way. We are looking forward to supporting you.
A few days ago, we started a conversation on the Wikifunctions Project Chat
about what the right type for morphological functions
<https://www.wikifunctions.org/wiki/Wikifunctions:Project_chat#Type_for_morp…>
should be, which also extended to IRC / Telegram
<https://wm-bot.wmcloud.org/logs/%23wikipedia-abstract/20230830.txt>. My
summary of the comments is that we can go ahead with using strings as the
argument and output type for morphological paradigms, given that in most
cases a string-based function would be at the core of any other solution
anyway. Thanks to everyone who participated in that discussion!
Thanks to Kutz Arrieta for a discussion and review of this newsletter.
Thanks to William Avery for improving and working on the Form Checker tool.
Thanks to everyone who participated in the discussion about the right type
for morphological functions.
Volunteer’s Corner
The next Volunteer’s Corner will be on September 18, 2023, at 17:30 UTC
<https://zonestamp.toolforge.org/1695058220> at
meet.jit.si/AWVolunteersCorner. We plan to kick off that meeting with a
live tutorial on building functions together.
The on-wiki version of this newsletter can be found here:
https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Updates/2023-08-31
Wikifunctions at Wikimania 2023
We presented Wikifunctions at *Wikimania 2023*
<https://wikimania.wikimedia.org/wiki/2023:Wikimania>, the annual gathering
of Wikimedians from all around the world. This year, Wikimania saw
participants from 138 languages. The conference was held from 16 to 19
August in Singapore.
<https://meta.wikimedia.org/wiki/File:Wikimania_2023_Singapore_Blue_Header_l…>Wikimania
2023 in Singapore, August 16-19
It was exciting to see the Wikifunctions logo featured during Wikimania as
part of logos of the Wikimedia projects on the materials and big screens -
including on the largest high definition video wall in the world, according
to the Guiness Book of Records. It was even more exciting to present
Wikifunctions to the Wikimedia community.
We had two sessions, one that featured a presentation and question and
answer session, *Wikifunctions is here*, where we discussed where we are
and our plans, and were listening to the ideas and requests from the other
projects. A recording of this session is available, split in two parts with
a slight gap due to technical difficulties (one
<https://www.youtube.com/watch?v=sKoMYHnZhEk&t=20046s>, two
<https://www.youtube.com/watch?v=ldHYoD_1j5I>). The Wikimania organizers
are still working on uploading the individual parts to Commons, and we hope
to have an unbroken recording in the future.
The second session, *First steps with Wikifunctions*, was a tutorial with
the goal of taking contributors to work on their first function. We are
very happy about how the tutorial went. All participants managed to create
their first function on Wikifunctions. We are particularly happy about the
people who self-described themselves as non-developers also being able to
successfully follow the tutorial and work on functions, tests, and
implementations themselves. We certainly identified steps that need
improvement, particularly for creating tests and for the selection of
arguments in implementations, and we are grateful for these having clear
ways forward. A recording of the first part
<https://www.youtube.com/watch?v=YiwjqxqSENs&t=24940s> of the session is
available, but we did not record the working part of the session.
We want to thank the organizers of Wikimania for providing us with a stage
to present Wikifunctions, and the attendees who gave such valuable feedback!
CoSMo language
Members of Abstract Wikipedia’s natural language generation special
interest group (NLG SIG) under the lead of Maria Keet and Kutz Arrieta have
worked on the CoSMo content selection modeling language. CoSMo is a
language that enables the specification of which pieces of structured data
to use to drive the generation of a piece of text. This allows to decide
what part of the billions of statements in Wikidata would be considered
relevant for the generation of a given piece of text in Abstract Wikipedia.
Maria describes CoSMo and its background further in her blog post “CoSMo: a
content selection modelling language
<https://keet.wordpress.com/2023/08/20/cosmo-a-content-selection-modelling-l…>”
on the Keet blog. The full tech report is available on Arxiv
<https://arxiv.org/abs/2308.02539>.
GFpedia demo
Over the last few weeks, Krasimir Angelov, one of the developers of
Grammatical Framework (GF), and member of the NLG SIG, has developed
GFpedia, a system to demonstrate how parts of Abstract Wikipedia could work
using GF technology.
A few example pages:
- The Netherlands in English
<https://cloud.grammaticalframework.org/wikidata/index.wsgi?id=Q55&lang=en>
- Sweden in Bulgarian
<https://cloud.grammaticalframework.org/wikidata/index.wsgi?id=Q34&lang=bg>
Grammatical Framework <https://en.wikipedia.org/wiki/Grammatical_Framework> is
a programming language focused specifically on writing grammars for natural
languages, both for parsing and generation. In this case, the demo calls
the data from Wikidata and uses it to drive the generation of text. It is
using a template per type of entity, i.e. you will find the same template
used for every country, whereas many other types have smaller or no
templates currently.
CCKS keynote on Wikidata and Wikifunctions
On Sunday, Denny gave the keynote presentation to the 17th China Conference
on Knowledge Graphs and Semantic Computing <https://sigkg.cn/ccks2023/en/> in
Shenyang, China. In the keynote he presented Wikidata and Wikidata’s
lexical extension as well as Wikifunctions. The pre-recorded presentation
is available on YouTube <https://www.youtube.com/watch?v=MXEctjXD_GU>. The
questions in the Q&A session focused entirely on Wikifunctions, and the
interest in our new project was delightful.
The on-wiki version of this newsletter can be found here:
https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Updates/2023-08-14
--
Wikifunctions at Wikimania
This week is Wikimania 2023 in Singapore
<https://wikimania.wikimedia.org/wiki/2023:Wikimania>!
<https://meta.wikimedia.org/wiki/File:Wikimania_2023_Singapore_Blue_Header_l…>
Under the motto “Diversity. Collaboration. Future”, the Wikimedia
communities are having their annual event, for the first time since 2019 in
Stockholm again also in person. The motto could not be any more fitting for
Wikifunctions, a project where we hope that in the *future* the *diversity* of
Wikimedia projects will *collaborate* with each other more and deeper than
it has ever done before.
Only weeks after taking Wikifunctions online, we are looking forward to
presenting Wikifunctions at the conference, and to gather feedback and
discussions about the project, in order to shape its future and to let more
people know what Wikifunctions is aiming for.
We will have two sessions in the program:
- On Thursday, August 17, at 15:30-16:30 local time / 7:30-8:30 UTC
<https://zonestamp.toolforge.org/1692257416>, we will have our main
sessions, *Wikifunctions is here*
<https://pretalx.com/wm2023/talk/ZBXFNP/>. We will present the vision of
Wikifunctions, in particular how it can be helpful for the other Wikimedia
projects, for example for your local language Wikipedia and Wiktionary. We
will give a live demo of the project, and we will invite you to answer any
questions you may have, discuss ideas, and collaborate on the future of
Wikifunctions and how to integrate it with your home projects. We expect
this session to be streamed and recorded.
- On Friday, August 18 at 16:45–18:00 local time
<https://zonestamp.toolforge.org/1692348349>, based on a community
request, we will offer a session at the Hackathon, *First steps with
Wikifunctions* <https://phabricator.wikimedia.org/T343905>. This will be
a hands-on session on how to edit Wikifunctions. We expect this session not
to be streamed and recorded, but we are planning to offer similar sessions
in the near future for online participation.
The team will be represented by Denny Vrandečić, James Forrester, and Nick
Wilson at Wikimania.
<https://meta.wikimedia.org/wiki/File:Dr._Denny_Vrande%C4%8Di%C4%87-3.jpg>
Denny Vrandečić
<https://meta.wikimedia.org/wiki/File:James_Forrester_(WMF)_2013.jpg>
James Forrester
<https://meta.wikimedia.org/wiki/File:Wilson,_Nick_January_2016.jpg>
Nick Wilson
Regarding handing out further functioneer rights, we will focus on giving
rights to Wikimania attendees, in order to maximize engagement with
attendees. Following Wikimania, and assuming everything is still going
fine, we will pick up handing out rights again to more people, and also are
expecting to do so faster than so far.
If you are at Wikimania, we would be glad to talk to you about
Wikifunctions! We want to hear your thoughts, concerns, and ideas. We are
very excited to meet with the community!
This newsletter can be found on the Web here:
https://diff.wikimedia.org/2023/08/07/wikifunctions-is-starting-up/
After three years of development, we are excited to share that Wikifunctions
<https://www.wikifunctions.org/wiki/Special:MyLanguage/Wikifunctions:Main_Pa…>
is
slowly beginning to roll out.
Wikifunctions, the newest Wikimedia project, is a new space to
collaboratively create and maintain a library of functions. You can think
of these functions like recipes for a meal—they take inputs and produce an
output (a reliable answer). You might have experienced something similar
when using a search engine to find the distance between two locations, the
volume of an object, converting two units, and more.
You can learn more about how Wikifunctions works in this short video on
Commons
<https://commons.wikimedia.org/wiki/File:Wikifunctions_in_7_minutes.webm>
and YouTube <https://www.youtube.com/watch?v=bHy63VOp0RQ>.
Wikifunctions is a project that allows you to create new functions, run
existing functions, and understand how they work. We anticipate that the
system will eventually be able to generate sentences, texts, and full
articles. Using the simple facts housed in Wikidata
<https://www.wikidata.org/wiki/Wikidata:Main_Page>, you will be able to
write functions that make calculations, provide a person’s age, estimate
population densities, and more, and integrate the results into Wikipedia.
Additionally, Wikifunctions allows you to read and implement functions in
your native language, be that English, Spanish, Arabic, Bengali, or one of
the hundreds of other supported languages.
At the moment, just like any other new Wikimedia initiative, we are rolling
out Wikifunctions with minimal content and features to start. Logged-in
contributors can run a few early functions, and editing will be limited as
we test the project’s stability. You can request edit access
<https://www.wikifunctions.org/wiki/Wikifunctions:Apply_for_editing> on
Wikifunctions, and we will give out the rights to more people as we test
and learn. Things will bend, break, get fixed, and break again as we build
up the project’s capabilities. For now, we are excited to announce that the
Wikimedia communities have decided on the very first function: *join
together* <https://www.wikifunctions.org/view/en/Z10000>. The function
takes two strings and returns them combined. If you are logged-in, you can
try it out now on Wikifunctions
<https://www.wikifunctions.org/view/en/Z10000>.
We are looking forward to a thriving community to grow and maintain a
library of many useful and interesting functions in the future.
------------------------------
Wikifunctions is a core component of the larger Abstract Wikipedia
<https://meta.wikimedia.org/wiki/Special:MyLanguage/Abstract_Wikipedia>
initiative,
which will enable Wikimedia volunteer editors to create and maintain
content in a single place that can be shared across languages. In short:
Abstract Wikipedia will build a system where an editor can contribute
knowledge using their native Swahili, and a reader will be able to benefit
from that knowledge by reading it in their native Japanese.
Thank you
On behalf of the Abstract Wikipedia team and the whole Wikimedia movement,
please join me in welcoming Wikifunctions as a new project. We can’t be
more excited to invite you to experience it.
We plan to continue developing Wikifunctions to add new features: we will
build in better support for programming languages, access to Wikidata,
integration with Wikipedia and other Wikimedia projects, the ability to
deal with binary data files, and much more.
If you are interested in working with us to build a catalog of functions
(and have some patience to deal with the hiccups of an early new project),
please join us <https://www.wikifunctions.org/> as a contributor on
Wikifunctions! We are looking forward to becoming a new community.
We thank Google.org, the Rockefeller Foundation, and the Wikimedia
Endowment for their support.
Well tired of people still blocking me out of my accounts.
Sent from Yahoo Mail for iPhone
On Monday, August 7, 2023, 1:26 PM, abstract-wikipedia-request(a)lists.wikimedia.org wrote:
Send Abstract-Wikipedia mailing list submissions to
abstract-wikipedia(a)lists.wikimedia.org
To subscribe or unsubscribe, please visit
https://lists.wikimedia.org/postorius/lists/abstract-wikipedia.lists.wikime…
You can reach the person managing the list at
abstract-wikipedia-owner(a)lists.wikimedia.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Abstract-Wikipedia digest..."
Today's Topics:
1. Newsletter #114: Wikifunctions is starting up (Denny Vrandečić)
2. Re: Newsletter #114: Wikifunctions is starting up
(Denny Vrandečić)
----------------------------------------------------------------------
Message: 1
Date: Mon, 7 Aug 2023 13:18:49 -0700
From: Denny Vrandečić <dvrandecic(a)wikimedia.org>
Subject: [Abstract-wikipedia] Newsletter #114: Wikifunctions is
starting up
To: Abstract Wikipedia list <abstract-wikipedia(a)lists.wikimedia.org>
Message-ID:
<CA+bik1frcYQO6oAzpAtdDFmqDmEvg=Fhv9fNJHn+-HuB7-JSSA(a)mail.gmail.com>
Content-Type: multipart/alternative;
boundary="000000000000f4f3af06025af41d"
This newsletter can be found on the Web here:
https://diff.wikimedia.org/2023/08/07/wikifunctions-is-starting-up/
After three years of development, we are excited to share that Wikifunctions
<https://www.wikifunctions.org/wiki/Special:MyLanguage/Wikifunctions:Main_Pa…>
is
slowly beginning to roll out.
Wikifunctions, the newest Wikimedia project, is a new space to
collaboratively create and maintain a library of functions. You can think
of these functions like recipes for a meal—they take inputs and produce an
output (a reliable answer). You might have experienced something similar
when using a search engine to find the distance between two locations, the
volume of an object, converting two units, and more.
You can learn more about how Wikifunctions works in this short video on
Commons
<https://commons.wikimedia.org/wiki/File:Wikifunctions_in_7_minutes.webm>
and YouTube <https://www.youtube.com/watch?v=bHy63VOp0RQ>.
Wikifunctions is a project that allows you to create new functions, run
existing functions, and understand how they work. We anticipate that the
system will eventually be able to generate sentences, texts, and full
articles. Using the simple facts housed in Wikidata
<https://www.wikidata.org/wiki/Wikidata:Main_Page>, you will be able to
write functions that make calculations, provide a person’s age, estimate
population densities, and more, and integrate the results into Wikipedia.
Additionally, Wikifunctions allows you to read and implement functions in
your native language, be that English, Spanish, Arabic, Bengali, or one of
the hundreds of other supported languages.
At the moment, just like any other new Wikimedia initiative, we are rolling
out Wikifunctions with minimal content and features to start. Logged-in
contributors can run a few early functions, and editing will be limited as
we test the project’s stability. You can request edit access
<https://www.wikifunctions.org/wiki/Wikifunctions:Apply_for_editing> on
Wikifunctions, and we will give out the rights to more people as we test
and learn. Things will bend, break, get fixed, and break again as we build
up the project’s capabilities. For now, we are excited to announce that the
Wikimedia communities have decided on the very first function: *join
together* <https://www.wikifunctions.org/view/en/Z10000>. The function
takes two strings and returns them combined. If you are logged-in, you can
try it out now on Wikifunctions
<https://www.wikifunctions.org/view/en/Z10000>.
We are looking forward to a thriving community to grow and maintain a
library of many useful and interesting functions in the future.
------------------------------
Wikifunctions is a core component of the larger Abstract Wikipedia
<https://meta.wikimedia.org/wiki/Special:MyLanguage/Abstract_Wikipedia>
initiative,
which will enable Wikimedia volunteer editors to create and maintain
content in a single place that can be shared across languages. In short:
Abstract Wikipedia will build a system where an editor can contribute
knowledge using their native Swahili, and a reader will be able to benefit
from that knowledge by reading it in their native Japanese.
Thank you
On behalf of the Abstract Wikipedia team and the whole Wikimedia movement,
please join me in welcoming Wikifunctions as a new project. We can’t be
more excited to invite you to experience it.
We plan to continue developing Wikifunctions to add new features: we will
build in better support for programming languages, access to Wikidata,
integration with Wikipedia and other Wikimedia projects, the ability to
deal with binary data files, and much more.
If you are interested in working with us to build a catalog of functions
(and have some patience to deal with the hiccups of an early new project),
please join us <https://www.wikifunctions.org/> as a contributor on
Wikifunctions! We are looking forward to becoming a new community.
We thank Google.org, the Rockefeller Foundation, and the Wikimedia
Endowment for their support.
A quick update on the current status of Wikifunctions:
* everyone can read Wikifunctions
* the right to call functions has been restored for logged-in users. All
logged-in users can call functions.
* all logged-in users can edit outside of the main namespace. We can start
building a community. Say hi on the Project Chat at
https://www.wikifunctions.org/wiki/Wikifunctions:Project_chat
* users with the functioneer role can edit object pages. We have so far
given this role out to more people every day, there will be another batch
later today. You can apply here:
https://www.wikifunctions.org/wiki/Wikifunctions:Apply_for_editing
* We are still remaining a bit quiet and are not sending out the message to
the wider community just yet. We still have a few blocking issues to work
through. Our current target is Monday to let more people know.
Cheers,
Denny
Hello all!
Today was a very busy day for the development team.
We enabled general editing of the wiki on Wikifunctions.org. But the
planned roll-out of object editing rights - that is, the ability to create
and edit functions, tests, implementations, etc. - hit a stumbling block.
It's currently not possible.
An unrelated issue was discovered on the backend, and just to be cautious,
we also disabled the ability to call functions at all for now. That issue
bound most of our resources, so that we couldn't get to fixing the other
issue above.
Also, object history was broken, but we were able to deploy a fix for that.
A more complete list of issues can be found on our Status page:
https://www.wikifunctions.org/wiki/Wikifunctions:Status
We will not be giving out functioneer rights until the blocking issues are
resolved. We will keep you updated here daily for now.
Contributions to wikifunctions.org in making this a nice wiki to visit,
with the necessary help pages and community pages, are more than welcome.
Thank you all for your patience,
And thanks to the team for their hard work today,
Denny
In https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Examples we have
json-like form with statenents Object_with_modifier_and_of, Ranking
in https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Examples/Jupiter
is a bit differ
How fast create abstract form of content if we know English text?
We have Polish sentence: „W głuchej puszczy, przed chatką leśnika rota
strzelców stanęła zielona” it is poetically, normal will “W głuchej
puszczy, przed chatką leśnika stanęła zielona rota strzelców.”
to English: “In the deaf forest, a green rota of riflemen has stood in
front of the forester's hut.”
Dissection of this sentence with indentation:
(rota,
<what did?>(stand,
<where?>(in forest,
<what?>deaf),
(in front,
<of?> (of hut,
<whose?)forester)))
<what?>green,
<whose?>riflemen
there is less information here than in San Francisco example , only
what? whose? etc
What can be added to make it a correct abstract article?
Whether too many relations hinder sentence construction? Maybe
complicated relations split to simpler?
_2013.jpg){kind=link}
