This also reminds me, that like for namespaces and
content handlers, we
should probably keep a list of known rvslot names, to avoid
potential
conflicts.
Would be nice if extensions could register with mediawiki what rvslot names
they provide/manage. :)
On Thu, Jan 12, 2023 at 10:18 AM Derk-Jan Hartman <
d.j.hartman+wmf_ml(a)gmail.com> wrote:
> Oh Thomas. I notice that you use "json" as the content model, but if
I'm
> not mistaken, the content model is supposed to describe "what" you are
> storing, not how you are storing it. For instance: commons metadata uses
> "wikibase-mediainfo" as its content model.
>
This also reminds me, that like for namespaces and
content handlers, we
> should probably keep a list of known rvslot names, to
avoid potential
> conflicts.
>
>
https://www.mediawiki.org/wiki/Extension_default_namespaces
>
https://www.mediawiki.org/wiki/Content_handlers
>
> So probably just somewhere here?
>
https://www.mediawiki.org/wiki/Multi-Content_Revisions
>
>
> DJ
>
>
> On Thu, Jan 12, 2023 at 4:00 PM Derk-Jan Hartman <
> d.j.hartman+wmf_ml(a)gmail.com> wrote:
>
>> This is looking really nice !
>>
>> For those wondering, here is an example of the raw api output for this
>> extra slot when requested:
>>
>>
https://wikienterprise.org/w/api.php?action=query&format=json&prop=…
>>
>> This could be very useful ! Glad to finally see slots getting some more
>> usage.
>>
>> DJ
>>
>> On Thu, Jan 12, 2023 at 10:23 AM <tdvit(a)mail.com> wrote:
>>
>>>
>>> Hello, I've released a major upgrade of PageProperties extension
>>> and completely rewritten the extension page
>>>
>>>
https://www.mediawiki.org/wiki/Extension:PageProperties
>>>
>>> most of the recent work is intended for the use in conjunction with
>>> Semantic MediaWiki
>>> (it now offers a complete GUI based on OOUI to interactively create/edit
>>> properties, create/edit forms and even
>>> to perform a semantic import from csv fields to local properties
>>> registered in the Wiki).
>>>
>>> However at the same time the extension can be considered a proof of
>>> concept for the use of
>>> Slots, since all the data-structure is completely based on SLOTS
>>> (properties associated to a page are recorded within a slot with JSON
>>> content model)
>>> and they can also be navigated through the interface.
>>>
>>> The extension makes also significant use of the OOUI library, and I want
>>> to thank the authors for their wonderful work.
>>>
>>> If you want to check out the extension, I've set up this wiki
>>>
>>>
https://wikienterprise.org/wiki/Main_Page
>>>
>>> where you can freely test it.
>>>
>>> I also plan to contribute whenever possible to the development
>>> of MCR/slots for the coming versions of Mediawiki, since currently
>>> the extension uses at least one hack, and the edit of slots
>>> in addition to the first could in my opinion be strongly simplified
>>> possibly with a
>>> a few changes in the code base.
>>>
>>> best
>>> (Thomas)
>>>
>>>
>>>
>>> _______________________________________________
>>> Wikitech-l mailing list -- wikitech-l(a)lists.wikimedia.org
>>> To unsubscribe send an email to wikitech-l-leave(a)lists.wikimedia.org
>>>
>>>
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
>>
>> _______________________________________________
> Wikitech-l mailing list -- wikitech-l(a)lists.wikimedia.org
> To unsubscribe send an email to wikitech-l-leave(a)lists.wikimedia.org
>
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/