Wikidata:Property proposal/Matrix room (2)
Matrix room
[edit]Originally proposed at Wikidata:Property proposal/Authority control
Description | Name of Matrix (Q22906785) room the entity is using. |
---|---|
Data type | External identifier |
Allowed values | strings in the form of #somewhere:example.org (#<room name>:<domain> ) no longer than 255 characters (spec) |
Example 1 | Wikimedia movement (Q3568028) → #wikimedia-space:matrix.org |
Example 2 | Wikimedia Central and Eastern Europe (Q114309441) → #wikimedia-cee:matrix.org |
Example 3 | Matrix (Q22906785) → #matrix:matrix.org |
Example 4 | for more examples see this query |
Implied notability | Wikidata property for an identifier that does not imply notability (Q62589320) |
Formatter URL | https://matrix.to/#/$1 |
See also | IRC channel URL (P1613), Discord server numeric ID (P9345), X username (P2002), Facebook username (P2013) etc |
Motivation
[edit]Similar to IRC channel URL (P1613) - Matrix is slowly replacing IRC as FLOSS discussion infrastructure. Useful for generating contact sections. Could be represented with IM channel URL (P8009) and a qualifier, but that seems needlessly complex and hard to use.
2nd nomination, sort of. Originally proposed as Matrix channel but as pointed out below "room" makes more sense; I only noticed while renaming that Wikidata:Property proposal/Matrix room already exists.
Some thoughts:
- Could be an URL instead of an identifier, see URI spec. Not sure which is better. (Although note that a
matrix:
URI can represent a number of other things than a room, e.g. a user.) - Technically, Matrix has room IDs and room aliases. Room IDs are random strings (used to avoid collisions) and not terribly useful. Room aliases are non-unique - a room can have many names and technically there isn't any "primary" name. But in practice / socially there always is (the one that gets linked from the project homepage etc) so I think making room name (and not ID) into a property is reasonable.
- There is Wikidata:Property proposal/Matrix space already. Depending on how you look at it, spaces are a subset of rooms (room is a fundamental building block in Matrix, kind of like directories in a file system, and gets used under the hood for a bunch of thing the end user would not think of as rooms – so spaces are implamented as a special type of room), or something entirely different (from the user POV, they are a tagging system for grouping rooms belonging to the same community). So not sure if this proposal would obsolete that one or not. In any case, I think rooms are more often relevant to a Wikidata entity than spaces.
- The URL formatter would either be
matrix:r/$1
but with the first character of $1 sliced off (e.g.matrix:r/somewhere:example.org
- see spec) orhttps://matrix.to/#/$1
but with $1 urlencoded (e.g.https://matrix.to/#/%23somewhere%3Aexample.org
- see spec). I imagine that wouldn't work out of the box. A third possibility would behttps://app.element.io/#/room/$1
which opens the room in a hosted instance of Element, the most popular Matrix client – that works without any manipulation of the identifier, but the URL is less generic and not useful to people using other clients or other Element service providers.
-- Tgr (talk) 18:20, 30 September 2022 (UTC)
Discussion
[edit]- Comment This property is named Martix channel, but not Matrix room alias? Laftp0 (talk) 06:53, 4 October 2022 (UTC)
- Support Laftp0 (talk) 23:05, 17 November 2022 (UTC)
- @Laftp0 uh, not sure why I named it like that. I agree "Matrix room" is a better name (I don't think adding "alias" is useful, it's technically correct but no one ever uses it when talking about Matrix room names). I'll rename the proposal if there are no objections in a few days. Tgr (talk) 07:03, 28 November 2022 (UTC)
- Renamed. (Turns out there was an older Wikidata:Property proposal/Matrix room proposal already.) --Tgr (talk) 18:35, 25 December 2022 (UTC)
- Strong support --Push-f (talk) 12:45, 16 October 2022 (UTC)
- I updated the proposal to use
https://matrix.to/#/$1
as the formatter URL. Note that $1 is automatically URL encoded so that works just out of the box. I think the matrix.to service is clearly preferable over the matrix URI because it's also usable by people who don't have a matrix: URI handler installed. --Push-f (talk) 02:13, 3 November 2022 (UTC)
- I updated the proposal to use
- Support --Waldyrious (talk) 13:10, 16 October 2022 (UTC)
- WikiProject Informatics has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.. --Push-f (talk) 15:26, 2 November 2022 (UTC)
- Support --1-Byte (talk) 15:51, 2 November 2022 (UTC)
- Oppose This Property needlessly duplicates what IM channel URL (P8009) is for. I would propose using IM channel URL (P8009) with the matrix: URI scheme. --Haansn08 (talk) 00:32, 3 November 2022 (UTC)
- I think it has been well argued in the motivation that using IM channel URL (P8009) is needlessly complex and hard to use. And it also does not result in hyperlinks (IM channel URL (P8009) has datatype string), unlike the proposed property. Also note that many people don't have a matrix: URI handler installed so matrix: URIs are often not particularly helpful and would require further processing. I see absolutely no drawbacks to creating the proposed property, only benefits. --Push-f (talk) 02:16, 3 November 2022 (UTC)
- Support --快乐的老鼠宝宝 (talk) 15:43, 16 November 2022 (UTC)
- Support --MTRNord (talk) 12:12, 17 November 2022 (UTC)
- Somewhat off-topic but I think it would be nice to have a way to model that an IRC channel URL (P1613) is bridged to a Matrix channel. For an idea how to do that see my object identifies property proposal. --Push-f (talk) 09:42, 23 November 2022 (UTC)
- Support The only proposed alternative so far, custom URI schemes, are more of a hassle to search or automatically process and have poor UX as mentioned above. IRC channel URL (P1613) also has a custom URI scheme and a specific property. Custom URI schemes on their own are also not really semantic web-y without custom support by (user) agents, as far as I know (I would love to be enlightened about how they are supposed to fit into hypermedia/HATEOAS etc.). --SlowByte (talk) 23:12, 23 November 2022 (UTC)
- Support +1 for "matrix room", with support for an optional matrix room type qualifier enum of ["space"] Dandellion Dali99 (talk) 03:42, 29 November 2022 (UTC)
- Comment listed this on Wikidata:Property proposal/Authority control after the property type was changed recently. --Tgr (talk) 18:36, 25 December 2022 (UTC)
@Tgr, Laftp0, Push-f, Waldyrious, 1-Byte, Haansn08:@快乐的老鼠宝宝, MTRNord, SlowByte, Dandellion Dali99: Done as Matrix room ID (P11478). I added some examples from the first proposal. I listed https://matrix.org/ as source website, which might be doubtful. Feel free to correct that. Lymantria (talk) 09:43, 7 January 2023 (UTC)
- Thanks! --Push-f (talk) 15:24, 8 January 2023 (UTC)
- @Dandellion Dali99: I see that you qualified a bunch of statements with this new property with instance of (P31)Matrix room (Q114785432) or instance of (P31)Matrix Space (Q116081600). I don't think P31 should be used as a qualifier. I think it would make more sense to use subject has role (P2868). --Push-f (talk) 15:29, 8 January 2023 (UTC)
- I don't think we need to qualify matrix rooms at all. There's an argument to be had over whether spaces should be represented with this property and a qualifier (from an UX point of view, it's a quite distinct concept; at the technical level, they are implemented as a special kind of room, so e.g. the formatter URL will work) or a dedicated property, but rooms being rooms should go without saying. Tgr (talk) 22:11, 8 January 2023 (UTC)
- My logic here is that if you do qualify spaces. e.g. for Q22906785 separating #matrix:matrix.org from #community:matrix.org, you'd have to also specify chat rooms. How else would you separate "missing data" and "chat room"?
- It also wouldn't sit right for me to have "matrix room" just mean chat, matrix is very explicit about not being an exclusively chat based protocol. Would a Thirdroom[1] world be just modeled as a chat room? What about rooms specifically for storing sticker packs? Or cereuleans microblogging feeds. There are matrix clients using rooms to share pdf annotations, synchronize collaborative documents and whiteboards. Many of these might not be super useful for most items on wikidata, but I still think we should be accurate and open for different forms of rooms being adopted.
- Whether or not that means we make a new property for each and one of them, qualify the matrix rooms with types like Q116081600 and matrix room (or maybe matrix chat or just chat would be more preferable), or something else entirely I'm not sure what's best. But if we are limiting this property to just chat rooms I think this property should be named something like matrix chat room instead at least Dandellion Dali99 (talk) 03:26, 9 January 2023 (UTC)
- I don't think we need to qualify matrix rooms at all. There's an argument to be had over whether spaces should be represented with this property and a qualifier (from an UX point of view, it's a quite distinct concept; at the technical level, they are implemented as a special kind of room, so e.g. the formatter URL will work) or a dedicated property, but rooms being rooms should go without saying. Tgr (talk) 22:11, 8 January 2023 (UTC)