René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Action schema defines links inconsistently with Thing Description","articleBody":"Thing Description defines the `links` property of a Thing to be an array of objects, each with \"rel\" and \"href\" properties (among others). Would it make sense for Actions to follow suit? This isn't a normative part of the spec, but it would feel quite sensible. It would mean changing from:\r\n\r\n```json\r\n{\r\n  \"status\": \"completed\",\r\n  \"output\": true,\r\n  \"links\": {\r\n    \"self\": {\r\n      \"href\": \"https://my_host/actions/id\"\r\n    }\r\n  }\r\n}\r\n```\r\nto\r\n```json\r\n{\r\n  \"status\": \"completed\",\r\n  \"output\": true,\r\n  \"links\": [\r\n    {\"rel\": \"self\", \"href\":\"https://my_host/actions/id\"},\r\n  ]\r\n}\r\n```\r\n\r\nThe resulting object is slightly less convenient (I can't just do `action[\"links\"][\"self\"][\"href\"]`) but it is more in keeping with the standard.\r\n\r\nThis is really a decision for LabThings-FastAPI, but I'm keen not to break compatibility if there was a good reason for doing it the current way.\r\n","author":{"url":"https://github.com/rwb27","@type":"Person","name":"rwb27"},"datePublished":"2023-08-10T10:38:07.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/324/python-labthings/issues/324"}