W3C home > Mailing lists > Public > public-webpayments-ig@w3.org > March 2015

Re: [use cases] Requirements as links

From: <chaals@yandex-team.ru>
Date: Wed, 18 Mar 2015 13:03:25 +0300
To: Manu Sporny <msporny@digitalbazaar.com>, Web Payments IG <public-webpayments-ig@w3.org>
Message-Id: <104451426673005@webcorp02g.yandex-team.ru>
Yeah, I did this with the longdesc spec too - http://www.w3.org/TR/html-longdesc/#UCnR

It makes life a lot clearer all round.

cheers

18.03.2015, 06:27, "Manu Sporny" <msporny@digitalbazaar.com>:
> During the Credentials Community Group call today, Gregg Kellogg
> provided a link to the CSV on the Web use cases document, which does
> something that I think we should shamelessly embrace and extend.
>
> Look at how they do requirements (search for "Requires:"):
>
> http://w3c.github.io/csvw/use-cases-and-requirements/index.html#UC-PaloAltoTreeData
>
> Each use case links to a set of requirements that are published at the
> end of the document:
>
> http://w3c.github.io/csvw/use-cases-and-requirements/index.html#req
>
> Gregg said that doing so made it much easier to categorize and track the
> technical requirements of the solution.
>
> -- manu
>
> --
> Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
> Founder/CEO - Digital Bazaar, Inc.
> blog: The Marathonic Dawn of Web Payments
> http://manu.sporny.org/2014/dawn-of-web-payments/

--
Charles McCathie Nevile - web standards - CTO Office, Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com
Received on Wednesday, 18 March 2015 10:03:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:08:33 UTC