Re: header syntax.

On Sat, Nov 24, 2012 at 8:09 PM, marbux <marbux@gmail.com> wrote:

> On Sat, Nov 24, 2012 at 1:06 PM, Pablo Olmos de Aguilera C.
> <pablo@glatelier.org> wrote:
>
> > Then after almost a week I don't understand what is a "profile".
>
> I'll take a swing at answering that, since it's a definition I
> researched about 3 years ago.
>
> Given a specification A, a profile is a subset (B) of  the
> supersetting A specification. In effect, a sub-specification to which
> implementers can claim conformance. A superset specification can have
> multiple subsetting profiles, optimally layered so that each profile
> incorporates by reference all profiles with a smaller feature set in a
> linear fashion until the full specification is reached. Hence the need
> to begin by identifying and specifying a "core" profile and working
> our way outward to a full specification. And by logical extension,
> once the full specification is supersetted, it becomes a profile of
> the new superset specification.
>

Thanks, Paul. Your description clarifies the profile/spec setup nicely.

Pablo and Max, does this help? While certain commonly-used markdown
constructs may be absent from the core profile, they'll still (often) be
made available in a higher-level profile, and hence part of the full spec?

Ryan