haudio-brainstorming

From Microformats Wiki
Revision as of 03:02, 31 July 2011 by HughP (talk | contribs) (→‎Contributor Roles)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

hAudio Brainstorming

Inheritance of Properties

Suggest that the following section in the spec:

Parser Processing Notes

  • It is important to understand that ITEM is an opaque element. When processing the ITEM element, none of the properties of the child hAudio should be pulled into the parent hAudio. However, it is recommended that child hAudio SHOULD inherit the following parent hAudio properties, if they are not specified on the child:
    • album
    • contributor
    • category
    • published
    • photo

Be replaced with:

Parser Processing Notes

It is important to understand that ITEM is an opaque element. When processing the ITEM element, the properties of the child hAudio should not be pulled into the parent hAudio, nor vice versa, with the following exceptions.

  • It is recommended that child hAudio SHOULD inherit the following parent hAudio properties, if they are not specified on the child:
    • album
    • contributor
    • category
    • published
    • photo
  • The parent hAudio MAY inherit the following properties from its children:
    • sample (Note that sample is plural, so it is OK for the parent to inherit this property from multiple children)

Download links

Suggested we change this:

The type of the file MAY be specified by using the type specifier for a URI.

To:

The type of the file SHOULD be specified by using the type specifier for a URI.

All examples in the spec should be updated to include the type attribute, and an informative section in the spec should list commonly used types.

Contributor Roles

Is there a list of Roles somewhere that we can use to "limit" the types of contributors? This list need not be germain to just audio genres, it could be inclusive of print media and video or photo media. I work with OLAC [1] and we have a set of contributors which we pull from an RDF set somewhere. Could something simular be done here?

Related Pages