Re: [dxwg] Profile description model and vocabulary

This seems a little inverted: we have a set of requirements, and to meet those requirements we will create the minimal set of resources needed support interoperability of data exchange within communities of practice.

Profile guidance is the key deliverable - but for several key requirements we can offer no guidance in the absence of an available solution - other than to "go and develop a standard solution". ProfileDesc is a candidate, but not proscriptive, option for meeting some specific requirements.

I fear that if we continue to confuse this with the issue of the "perfect" profile specification language, (which also doesnt appear to exist) then we will keep on worrying about "i dont know how to describe my profile with profiledesc therefore there is something wrong". It doesnt peel potatoes either.

GitHub Notification of comment by rob-metalinkage
Please view or discuss this issue at using your GitHub account

Received on Tuesday, 28 August 2018 12:47:44 UTC