Re: [dxwg] A mechanism must be available to identify conformance to each inherited profile given conformance to a profile that specialises it (6.1)

Requirement 6.8.2 "RPFRP" starts off with the requirement - and these
cannot be met be existing ad-hoc documentation of profiles (PDF,
schematron, word docs, etc, nor SHACL ans SHex as far as i can tell)

   1. Machine-readable specifications of application profiles need to be
   easily publishable, and optimize re-use of existing specifications.
   2. Application profiles need a rich expression for the validation of
   metadata
   3. Profiles must have properties for at least two levels of
   documentation: 1) short definition 2) input and editing guidance
   4. Profiles must support declaration of vocabulary constraints
   5. A mechanism must be available to identify conformance to each
   inherited profile given conformance to a profile that specialises it.

(#2 points towards SHACL etc, but the other aspects motivate profileDesc)



On 11 May 2018 at 16:57, kcoyle <notifications@github.com> wrote:

> Looking at profileDesc I don't see this functionality explicitly
> expressed. It may be inherent in roles, but then much depends on how far we
> wish to go in defining specific roles. It actually appears to me that at
> least for the FPWD we do not need to specify anything relating to
> inheritance, and in fact we may not need to in order to fulfill 1.0. If
> that is so, then I could imagine a note or some other document that
> specifically addresses how dependencies between profiles are handled *when
> that is desirable*. To be sure, creating profiles with dependences should
> not be required.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/dxwg/issues/214#issuecomment-388278224>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AIR3YX8CKaxtsW6msfFm7YICpxyRHCzMks5txTZQgaJpZM4TiAu_>
> .
>


-- 
GitHub Notification of comment by rob-metalinkage
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/214#issuecomment-388659304 using your GitHub account

Received on Sunday, 13 May 2018 22:04:57 UTC