Re: Separate conformance class for HTML5

+1. We just need to make sure that in this conformance class the same
aspects like in xml conformance are taken into account, like: at least
global or local selection, inheritance and defaults are mandatory (if
applicable), overriding is always complete. I am saying this because of the
latest provenance draft that turned complete overriding off for the
combination of local HTML5 markup and global rules. That doesn't work.

Felix
Am 15.10.2012 11:55 schrieb "Jirka Kosek" <jirka@kosek.cz>:

> Hi,
>
> currently our spec defines two conformance classes:
>
> 4.1 Conformance Type 1: ITS Markup Declarations
> 4.2 Conformance Type 2: The Processing Expectations for ITS Markup
>
> For HTML5 Type 1 doesn't make sense as we are predefing markup to be
> used in HTML5 and HTML5 doesn't use schemas for defining vocabulary
> extensions. But HTML5 specification itself requires having so called
> applicable specification in order to extend HTML language.
>
> I think that we should create separate conformance class (Type 3) which
> will join Type1&2 taylored for HTML usage. Then we can remove all HTML
> mentions from Type2 class.
>
> Thoughts?
>
>                                 Jirka
>
> --
> ------------------------------------------------------------------
>   Jirka Kosek      e-mail: jirka@kosek.cz      http://xmlguru.cz
> ------------------------------------------------------------------
>        Professional XML consulting and training services
>   DocBook customization, custom XSLT/XSL-FO document processing
> ------------------------------------------------------------------
>  OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
> ------------------------------------------------------------------
>
>