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

Re: PROPOSAL: Capture terminology in stand-alone glossary document

From: Adrian Hope-Bailie <adrian@hopebailie.com>
Date: Sat, 2 May 2015 13:17:01 +0200
Message-ID: <CA+eFz_+JyvQA2=mV7EvypCSW-3dy3cevoKj6NEX=z4uYSqxY_Q@mail.gmail.com>
To: Ian Jacobs <ij@w3.org>
Cc: Web Payments IG <public-webpayments-ig@w3.org>
Thanks Ian.

Do we need to then include the terminology in other documents or is it
sufficient to reference the glossary?

I think we should consider including some of the terms from the Gates
Foundation's Level One glossary which seems to have been very well put
together to be easy to consume for a less informed audience. They aren't
all applicable probably and we certainly have some additions but it's a
good reference.

https://leveloneproject.org/the-guide/glossary-of-terms/

Adrian





On 1 May 2015 at 19:34, Ian Jacobs <ij@w3.org> wrote:

>
> > On May 1, 2015, at 11:37 AM, Adrian Hope-Bailie <adrian@hopebailie.com>
> wrote:
> >
> > As we begin formulating the architecture document it appears that we are
> replicating the set of terms from the use case document.
> >
> > Trying to maintain multiple copies of the same content across what may
> end up being numerous documents is a recipe for confusion and inefficiency.
> >
> > Since this content is key to all of our work does it not make sense to
> capture this in a  stand-alone document that can be referenced from both
> the use cases and architecture docs and any other docs that we produce in
> future.
> >
> > Precedent that I could find:
>
> Hi Adrian,
>
> We have a glossary task force and all share the goal of having uniform
> vocabulary usage. Manu is working on tools to mechanically include terms
> that may be defined in one place. I don’t think that work has been
> completed yet.
>
> We are also looking at how to keep the terms as simple as possible for a
> broad readership, while at the same time having “mappings” from our terms
> to those (similar terms) used in other standards. Evert has led that work
> and is looking for feedback on this kin of approach:
>  https://www.w3.org/Payments/IG/wiki/GlossaryReference
>
> I’ve taken Evert’s page and turned it into this:
>
>  EXPERIMENT: Web Payments Glossary
>  http://www.w3.org/2015/04/wpay-glossary
>
> Summary:
>
>  * I believe there is strong agreement to manage terms carefully including
> defining them in one place
>  * There is also agreement to use them where needed in specs (by importing
> them from a single source)
>  * There is also agreement to map them to other definitions found in the
> broader ecosystem.
>
> Ian
>
> >
> > http://www.w3.org/TR/2004/NOTE-ws-gloss-20040211/
> > http://www.w3.org/TR/2013/NOTE-ld-glossary-20130627/
> > http://www.w3.org/TR/2014/NOTE-mbui-glossary-20140107/
> >
> > Please can this be put on the agenda for Monday's call?
>
> --
> Ian Jacobs <ij@w3.org>      http://www.w3.org/People/Jacobs
> Tel:                       +1 718 260 9447
>
>
>
>
Received on Saturday, 2 May 2015 11:17:29 UTC

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