- From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Oct 2018 21:13:10 +0000
- To: public-dxwg-wg@w3.org
Its a very long document if we start reviewing all the cases where some sort of profile might be implied through recommendations to reuse vocabularies. This is why we must stick to process and address requirements introduced via Use Cases. What is relevant here is that some profiles are (sometimes partially) described using constraints languages, and there are a range of such languages. If we take "specification" as the intention of dct:Standard, then under for example OpenGeospatial Consoritium model, the "conformance target" must be identified and a set of testable requirements identified. (constraints languages introduce the "testable" aspect. As an experiment, we can consider documenting any of these vocabulary reuse scenarios as profiles if we can identify a testable requirement. If its merely "should use terms from X" i think these cases fall outside our definition of profile - its not a constraint. -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/366#issuecomment-426432468 using your GitHub account
Received on Tuesday, 2 October 2018 21:13:11 UTC