Re: [w3c/manifest] WIP: purpose (#493)

> +          <li>Let <var>value</var> be the result of calling the
> +          <a>[[\GetOwnProperty]]</a> internal method of <var>image</var>
> +          passing " <code>purpose</code>" as the argument.
> +          </li>
> +          <li>Let <var>type</var> be <a>Type</a>(<var>value</var>).
> +          </li>
> +          <li>If <var>type</var> is not "string", then:
> +            <ol>
> +              <li>If <var>type</var> is not "<code>undefined</code>", <a>issue
> +              a developer warning</a> that the type is unsupported.
> +              </li>
> +              <li>Return <code>undefined</code>.
> +              </li>
> +            </ol>
> +          </li>
> +          <li>Let <var>keywords</var> be the result of <a>splitting</a>

I gave this more thought, and I think I want to stick with a string here - because it's rare that something will have multiple purpose (and we only define one purpose). Should probably only use arrays for complex types. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/493/files/c33d8ca424da40f2d7144c5cdfac6f7ba35ed689#r78314037