... | ... | @@ -64,4 +64,13 @@ i like the idea of giving the tag an id like in this example |
|
|
}
|
|
|
```
|
|
|
Then it's possible to provide services by each platform to ask if a tag is verified. Or receive all verified tags in common in a separate request.
|
|
|
'verify' and 'reject' sounds like separate activities, that occurre when the activity happens. |
|
|
\ No newline at end of file |
|
|
'verify' and 'reject' sounds like separate activities, that occurre when the activity happens.
|
|
|
|
|
|
# image & logo
|
|
|
[image](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-image)
|
|
|
|
|
|
# coordinates
|
|
|
[latitude](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-latitude) & [longitude](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-longitude)
|
|
|
|
|
|
# address, legalAddress, contacts
|
|
|
There is not really a matching for adresses. [Profile](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-profile) has a property [describes](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-describes). But we should not exchange address data, we should maybe only link to the profile page of the actor. |