I just checked. Pixelfed already implements the location property. It's contained in the ActivityPub objects and shown on its webpage. So it's literally already there.
On what I might agree, that it's hard to determine what the Fediverse is capable of. As a technically inclined guy, I can just look at the raw data and form opinions. So my opinion "anything" is probably not what most people experience.
I take it for granted that users must be able to decide upon the precision of the #geocoding they use for their postings.
And that they must also be able to decide upon the geogaphic range of search when they lookup #georef|erenced postings.
🌺
🏷️ #OLC #QTH #SemanticFediverse #ActivityPub #Mastodon #Friendica #Pixelfed #Fediverse #Geocode #Georeferencing #OpenLocationCode #PlusCode #Maidenhead #HamRadio #AFU #CBFunk #CitizenBand #CiBi #ActivityVocabulary
The location property of the #ActivityVocabulary does not only support exact locations but also areas in the sense that it allows for ›logical locations‹.
A logical location could be ›near Berlin«, but also a #geocode with reduced precision.
🌺
🏷️ #OLC #QTH #SemanticFediverse #ActivityPub #Mastodon #Friendica #Pixelfed #Fediverse #Geocoding #Georef #Georeferencing #OpenLocationCode #PlusCode #Maidenhead #HamRadio #AFU #CBFunk #CitizenBand #CiBi
Relax, no one is seeking to re-invent any wheel.
This thread is more about usability than it is about implementation.
No one can make use of #semantic properties in a vocabulary as long as they do not show up in frontends.
So, rather than deter consideration, let's keep the dialogue going.
🌺
🏷️ #OLC #QTH #SemanticFediverse #ActivityPub #Mastodon #Friendica #Pixelfed #Fediverse #Geocode #Geocoding #Georef #Georeferencing #OpenLocationCode #PlusCode #Maidenhead
