Freephile Wiki:ToDo: Difference between revisions
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Replace in-text annotations == | == Replace in-text annotations == | ||
Need to convert any usage of SMW property annotation to use the parsoid-friendly [https://www.semantic-mediawiki.org/wiki/Help:Setting_values #set parser function syntax]. <code>#set</code> was favored all the way back in 2014 but deprecating in-text annotation was debated and not actually removed or resolved.<ref>[https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/584 584 was closed because it wasn't deprecated] [https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/4727 4727 is still open in 2025]</ref>. | |||
Note that <nowiki>[[foo::bar]]</nowiki> '''inside''' an ask query does not need to change because it is already in the <nowiki>{{#ask: }}</nowiki> context which is parsed differently. You can see an ask query in action at [[People]] | Note that <nowiki>[[foo::bar]]</nowiki> '''inside''' an ask query does not need to change because it is already in the <nowiki>{{#ask: }}</nowiki> context which is parsed differently. You can see an ask query in action at [[People]] | ||
| Line 23: | Line 23: | ||
=== Info === | === Info === | ||
There are some edge cases and complexities involved like the property link syntax of <nowiki>[[has property::@@@]]</nowiki> | |||
# https://www.youtube.com/watch?v=lS1xPkERWCM&t=2146s | # https://www.youtube.com/watch?v=lS1xPkERWCM&t=2146s | ||
# https://www.mediawiki.org/wiki/Parsoid/Extension_API | # https://www.mediawiki.org/wiki/Parsoid/Extension_API | ||
| Line 29: | Line 30: | ||
# [https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/5624 '''Issue #5624''' Enhance #set: parser function with display option] | # [https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/5624 '''Issue #5624''' Enhance #set: parser function with display option] | ||
# [https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/6226 '''Issue #6226''' request for comment] | # [https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/6226 '''Issue #6226''' request for comment] | ||
== Merge Conf repo == | |||
The conf repo is using the qb-merge branch. We need to merge it back to 'master'([https://github.com/freephile/meza-conf-public/issues/2 Issue #2]) and then change the name of master to main. There are multiple other branches that we could examine for possible flags or features that can be brought into main to clean up the structure (eliminating those branches). | |||
{{References}} | {{References}} | ||
Latest revision as of 15:31, 5 September 2025
Replace in-text annotations[edit]
Need to convert any usage of SMW property annotation to use the parsoid-friendly #set parser function syntax. #set was favored all the way back in 2014 but deprecating in-text annotation was debated and not actually removed or resolved.[1].
Note that [[foo::bar]] inside an ask query does not need to change because it is already in the {{#ask: }} context which is parsed differently. You can see an ask query in action at People
A template for 'Animal' could use this:
{{#set:
Species = {{{Species|}}}
| Habitat = {{{Habitat|}}}
| Diet = {{{Diet|}}}
}}
Any any page such as 'Lion' would call the template
{{Animal|Species=Lion|Habitat=Savanna|Diet=Carnivore}}instead of in-page property annotations.
Some of the property annotations that were updated
Info[edit]
There are some edge cases and complexities involved like the property link syntax of [[has property::@@@]]
- https://www.youtube.com/watch?v=lS1xPkERWCM&t=2146s
- https://www.mediawiki.org/wiki/Parsoid/Extension_API
- https://www.semantic-mediawiki.org/wiki/Help:Setting_values/Working_with_the_template_parameter
- https://www.semantic-mediawiki.org/wiki/Semantic_Annotations#Technical_threat_for_inline_annotations
- Issue #5624 Enhance #set: parser function with display option
- Issue #6226 request for comment
Merge Conf repo[edit]
The conf repo is using the qb-merge branch. We need to merge it back to 'master'(Issue #2) and then change the name of master to main. There are multiple other branches that we could examine for possible flags or features that can be brought into main to clean up the structure (eliminating those branches).
