- From: Sebastien Lambla via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Jul 2021 09:54:30 +0000
- To: public-hydra-logs@w3.org
I do believe that the fact the spec doesn't guide in where things go between operation and ApiDocument makes me bleieve that something should be touched upon in the spec, which would prevent people like me from building enabled / disabled as I did :) That said, looking over to other api documentation tools, having an operation have an Id is quite common, so i wouldn't mind much leveraging this to make operation identification more clear, if it enables those scenarios. So from me, I'm happy for this to be in core in it's simplest form, i'd be happy with additional information about the availability of an operation to be in an extension so it can bake longer until we learn enough about the scenarios, and i'd be happy with IRIs for operations. -- GitHub Notification of comment by serialseb Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/241#issuecomment-882413112 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 19 July 2021 09:54:32 UTC