-
Since v0.13, the spaceAPI officially supports the field "trigger_person", which contains the nickname of the entity which opened the space. We could draw this useful information on the widget.
-
@slopjong @chron0 @lanthaler could we please [mumble](https://apollo.open-resource.org/lab:dspace#discussion) one day to discuss enabling [SpaceAPI](http://spaceapi.net/) with [JSON-LD](http://json-ld…
-
The `location.address` field is described as "The postal address of your space (street, block, housenumber, zip code, city, whatever you usually need in your country, and the country itself).".
Thi…
dbrgn updated
6 months ago
-
I would like to propose an addition to the directory to maybe make the repository obsolete in the future and get us out of the picture.
I would leave the directory.json as it is for now, but would …
-
When I validate my new endpoint using
`curl -X POST -H "Content-Type: application/json" https://validator.spaceapi.io/v2/validateURL -d'{"url": "https://acsgateway.hal9k.dk/spaceapi"}'`
I get t…
-
This is from the former "TODO.md":
"give a possibility to add new communities via web form (maybe ask the SpaceAPI developers)"
-
With some hackerspaces the app doesn't load the JSON.
For example if I test the hackerspace breizh-entropy I have :
"Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote r…
-
as far as i understand we shouldn't use just a random term for **rel** attribute of **link** we could either use URI or register **spaceapi** with IANA http://www.iana.org/assignments/link-relations/l…
-
The warnings seem to have no effect. Should we force the spaces to set the appropriate value for _Access-Control-Allow-Origin_?
-
Right now, we call our fork the "Space Directory" but still refer to the API as "Space API".
Ideally, we can reach an agreement with the original SpaceAPI developer in order to take over the name. …
dbrgn updated
7 years ago