- From: tombaker via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Aug 2019 09:42:27 +0000
- To: public-dxwg-wg@w3.org
@nicholascar In my reading, @paulwalk is not asking that PROF propose a conventional way to automatically validate data instances of application profiles, as you imply in your [first](https://github.com/w3c/dxwg/issues/698#issue-403402577) and [last](https://github.com/w3c/dxwg/issues/698#issuecomment-523867509) postings to this issue. Rather, he is questioning the value, for validation, of documenting dependencies between the documents needed for validation in PROF-based metadata (the "graph to be traversed"). As he writes above: > In the use-case where someone wishes to validate data against some declared conformance with some metadata profile, I just don't see any advantage in the validation process being able to somehow automatically interrogate the application profile to determine which mechanisms its supports. This can be simply documented in prose - it is for the systems developer to decide which mechanism they want to use. The mechanisms themselves need formal descriptions, but that is a separate issue being taken care of by those communities. @paulwalk is questioning whether developers really need, or would use, PROF-based metadata in support of validation as opposed to more community-specific mechanisms. Or @nicholascar, do you mean to imply that PROF-based metadata is not intended to have any relevance for validation? -- GitHub Notification of comment by tombaker Please view or discuss this issue at https://github.com/w3c/dxwg/issues/698#issuecomment-524249360 using your GitHub account
Received on Friday, 23 August 2019 09:42:28 UTC