W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > October 2019

Re: [dxwg] Query string implementation of profile selection (#544)

From: Annette Greiner via GitHub <sysbot+gh@w3.org>
Date: Thu, 24 Oct 2019 01:51:00 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-545706580-1571881859-sysbot+gh@w3.org>
I still don't see anything reassuring to developers that explains whether they can just build something that conforms to the abstract model without also formalizing and posting a "profile" for it. I don't think that should be required at all. I do think it would be reasonable to consider what would be required to make a web API usable programmatically. This is typically accomplished by documenting the API itself. I wonder if there is some more specific approach that would be more helpful for systems attempting to harvest data, though. It might be something closer to a list of URIs that meet the requirements of the abstract model.

GitHub Notification of comment by agreiner
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/544#issuecomment-545706580 using your GitHub account
Received on Thursday, 24 October 2019 01:51:09 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:28:33 UTC