@Ankry the fix is planned to be deployed soon. Have some real pages still affected is a good way to check that the problem is indeed solved.

@Tpt any idea how can we create propoer header/footer here (if this is the source of the problem)?

It seems that the two pages could be parsed as JSON by PHP and so, ProofreadPage assumes that they are using the JSON serialization for Page: pages. But, because they are not using the good JSON serialization format, an exception is thrown.

Also, I understand it's still disabled on both wikidata and test.wikidata.

There is still one feature missing: outputting statements on form and senses when the RDF representation of a lexeme is required (e.g. on Special:EntityData/L12.nt).

Is https://gerrit.wikimedia.org/r/449718 covering this?

Indeed the set of property and their datatypes is very static and cachable so we could use them as keys of a StatementByProperty object and then have StringStatement, StringSnak... types. The object would just be huge and maybe raise some performance problems of the various GraphQL tools (we would have 4K+ keys).

Thanks!

Deployed

Thank you!

Thank you!

@Tpt so it looks like right now you can't get a datavalue or recursively call item from a statement. I added a sample query to the task description.

Done as part of T153120

@Billinghurst Is the problem still happening now that the quality color bug is solved?

The fallback to the categories seems to work. I plan to keep it as long as their exists Page: pages that do not contain the pageproperty

Sorry, I was wrong, the fix is not deployed yet. It should be deployed this evening UTC.

As a logged-in user, it will also show normally/as expected.

@Tpt it does not seem to work: https://fr.wikisource.org/wiki/Livre:Revue_du_monde_nouveau,_vol._I,_1874.djvu

The change that should fix this problem have been deployed yesterday. A purge of the pages where blank ids are displayed should fix the problem (for Index: pages it could be done with a not null edit on MediaWiki:Proofreadpage_index_template)

This is a side effect of T198470. A fix for it should be deployed next week.

Fallback have been implemented and merged into ProofreadPage. It is live now on https://en.wikisource.beta.wmflabs.org and will be deployed on Wikisources next Tuesday.

@Ankry here is the query you are looking for: https://quarry.wmflabs.org/query/27922

It's probably because of change rEPRP502ff8adeddde1749001df704e0f389c37cb6e5e that uses a page property for the quality lookup instead of the categories. It's much leaner and it allows to have the same storage for all Wikisources independently of the quality category name. The page property have been introduced by rEPRPec94d4f460c1221a4f794a32e8e3d6b677d326d4 last September so I hoped most pages would have been purged but it seems it's not the case...

There is still to implement output of forms statements when the RDF representation of a lexeme is requested (i.e. Special:EntityData/L42.ttl) and the schema:inLanguage relation for lexemes.

Great! Thanks!

Merging the current namespace fix in the next SWAT looks like a sensible thing to do to have the namespaces properly working.

@Urbanecm Hey, it would be much better to not allocate custom namespace ids for the Page: and Index: namespaces but just let ProofreadPage setup the two namespaces with the proper names with the standard namespaces 250 and 252. I just did a change to ProofreadPage for that: https://gerrit.wikimedia.org/r/440010

Do you think it's okay to change the keys for ores responses from "1" to "one".

An example:

Thank you for the reminder!

I have updated the draft of RDF implementation change: https://gerrit.wikimedia.org/r/c/433953
It uses the existing namespace for Lexemes specific terms but provides a new ontology file which URI is http://wikiba.se/lexeme/ontology# (but it could be easily changed)

Not sure if you are proposing prefix as http://wikiba.se/lexeme/ontology/ or as http://wikiba.se/lexeme/ontology#.

Thank you for your feedbacks!

@Kaganer Thank you for your input.

Ok, so it seems to not be fully fixed :-(.

The full list of terms we have to define is:

@Dick_Bos @Peteforsyth @Vladis13 @Bodhisattwa A change that should fix this problem has just been deployed on Wikisource. Could you confirm that this bug is not happening anymore after having purge your browser cache [1]?

why not just http://wikiba.se/ontology# ?

Ok for the file. For the canonical namespace URI should we use something like "http://wikiba.se/ontology-lexeme#" to have something similar to "http://wikiba.se/ontology-beta#"? Or maybe "http://wikiba.se/lexeme/ontology#"? Should we also use the beta tag (that looks a lot like the FOAF version trap)?

@daniel Do you think that the ontology terms specific to lexemes should live in the same namespace and ontology definition file as the other Wikibase terms or should we create a new namespace?