W3C home > Mailing lists > Public > public-webplatform@w3.org > February 2015

Re: Adding HTML element data

From: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>
Date: Wed, 4 Feb 2015 22:31:40 -0700
Message-ID: <CAFDDJ7wLK0+0E+uVoSRYN=pPOgFevJZQ-fhXcZ=3phmCEZS4qQ@mail.gmail.com>
To: Austin William Wright <aaa@bzfx.net>
Cc: WebPlatform <public-webplatform@w3.org>
I like the idea of automating the process of populating basic data tables
from the specs.

But I do agree that in order to make this really useful, it needs to be
fully integrated with the Semantic Mediawiki properties, so that we can
generate all the cross-reference information that you can't currently get
from reading the specs themselves.

Do you have a public version of all the templates you're creating?  Have
you tried to figure out the information architecture of the properties
(e.g., which ones would need multiple values, how they all relate together
and so on)?


On 4 February 2015 at 21:44, Austin William Wright <aaa@bzfx.net> wrote:

> Hey HTML section maintainers,
> I'm planning to go through all the HTML elements with a bot and populate
> the pages with all the element metadata taken directly from the HTML5
> Recommendation, like categories, attributes, content model, ARIA info, and
> fixes to DOM interface where that's incorrect. I have it mostly ready, the
> changes will look like this (taking for example the "a" tag):
>>  {{Markup_Element
>> +|Categories=
>> +  {{Markup_Element_Category|name=Flow content}}
>> +  {{Markup_Element_Category|name=Phrasing content}}
>> +  {{Markup_Element_Category|name=Interactive content}}
>> +  {{Markup_Element_Category|name=Palpable content}}
>> +|Contexts=Where phrasing content is expected
>> +|Model=Transparent, but there must be no interactive content descendant
>> +|Attributes=
>> +  {{Markup_Element_Attribute_global_attributes}}
>> +  {{Markup_Element_Attribute|name=href|description=Address of the
>> hyperlink}}
>> +  {{Markup_Element_Attribute|name=target|description=Default browsing
>> context for hyperlink navigation and form submission}}
>> +  {{Markup_Element_Attribute|name=download|description=Whether to
>> download the resource instead of navigating to it, and its file name if so}}
>> +  {{Markup_Element_Attribute|name=rel|description=Relationship between
>> the document containing the hyperlink and the destination resource}}
>> +  {{Markup_Element_Attribute|name=hreflang|description=Language of the
>> linked resource}}
>> +  {{Markup_Element_Attribute|name=type|description=Hint for the type of
>> the referenced resource}}
>> +|Tag_omissions=Neither tag is omissible
>> +|ARIA_roles=link (default - do not set), button, checkbox, menuitem,
>> menuitemcheckbox, menuitemradio, tab or treeitem
>> +|ARIA_states=Global aria-* attributes, Any aria-* attributes applicable
>> to the allowed roles
>>  |DOM_interface=dom/HTMLAnchorElement
> I'll also be creating some apparently missing pages for some elements
> described in the TR: data, rb, rtc, rp, bdi, keygen, output.
> Any suggestions for better ways to format this? For instance, is there a
> better way to enumerate lists of categories, ARIA roles, and ARIA states?
> Also considering many of these items can be conditional, e.g. "If the type
> attribute is not in the Hidden state: Interactive content"
> For after this is published, I can't seem to be able to edit the
> Markup_Element template to make use if this data. How would I be able to do
> that, or who can do that for me? With all the information, what I really
> want is to calculate a list of valid parent and child elements, too, with
> Semantic Mediawiki-foo.
> Thanks,
> Austin Wright.
Received on Thursday, 5 February 2015 05:32:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:14:09 UTC