Re: Use-Case document structure on Github

Hello Yaso,

I understand your point of view and I agree that it could be nice if we
could use the use cases to help the identification of required best
practices (challenges) and a guidance of how to implement the best
practices (lessons).

However, most of the use cases don't present enough technical details to
help us the identification of how to implement a best practice or how to
answer questions like yours.

On the other hand, if I understood correctly, then the current use case
document should help the identification of required best practices instead
of implementation or technical details. In this case, I believe that the
main contribution of the use document should be a set of requirements
(required best practices) that reflects the main challenges faced by the
actors of the use cases.

I believe that we can go deeper on some of the use cases in order to
extract more technical details as well as some learned lessons. However,
this work requires getting in contact with the actors participating in the
use case (ex: publishers, consumers, developers...) to pose specific
questions, which can help us the definition of best practices
implementation. This can be one of the next steps towards the best
practices and vocabs definition.

Does it make sense for you?

Cheers,
Bernadette


2014-03-26 16:44 GMT-03:00 Yaso <yaso@nic.br>:

> Cool, Deirdree and Bernadette!
>
> As you said that you are prepare something on Thursday to discuss on
> Friday's call, I ran to write my impressions of the use cases  document,
> rather than later :-)
>
> As a (humble) developer, when I have in my hands a project, I'm used to
> pickup a similar app and analyze it to collect weaknesses and strengths.
>  Generally, the strengths will become a kind of  "personal best
> practices" and weaknesses will become "something to improve" or just
> "don't do that"
>
> I try to do this by observing the project documentation (when it's
> available) and trying to understand the process that lead to the
> development of the application. Then, I ask things like:
>
> - How I can extract this data (tables or pdf to JSON, usually)
> - How can I mix this data with other datasets using web API's
> - How can I share this data easily using a tool like Github or something
> in the cloud, like dropbox, or should I use it?  (I know it's not
> appropriate, but yes we use it)
>
> and so on...
>
> In other words, I miss a clear method for investigation of weaknesses
> and strengths, although the document seems to be going on the right
> track, I do not see yet how best practices can come while we just watch
> isolated aspects of each Use Case. I really think we should investigate
> them and document it regarding the processes that lead developers to
> take decicions on how to use/share/mix/store data on the web.
>
> See this use case:
> http://onehumanheartbeat.com/
>
> Jen Lowe[1] took his data on heartbeats of his gadget using a well
> documented method [2] and a script that is (wonderfully explained) here
> [3]. If I think on doing the same, but combining this info wit some info
> from my sensor-shoes to see how to optimize my steps, how can I do that
> using the W3C standards?
>
> And if it was a HUGE dataset?
>
>
> [1] http://datatelling.com/
> [2]
>
> http://www.quantifiedbob.com/2013/04/liberating-your-data-from-the-basis-b1-band/
> [3] https://github.com/btroia/basis-data-export/blob/master/README.md
>
>
> Cheers,
> Yaso
>
>
>
>
> Em 3/25/14, 10:34 AM, Lee, Deirdre escreveu:
> > Hi,
> >
> > Bernadette and I have uploaded the first version of the use-case ReSpec
> to the dwbp Github repo https://github.com/w3c/dwbp/. This shows the
> structure of the final use-case document, namely:
> >
> > 3. Use Cases
> >     3.1 Use-Case 1
> >     3.2 Use-Case 2
> >     ...
> > 4. General Challenges
> >     4.1 Gen Challenge 1
> >     4.2 Gen Challenge 2
> >     ...
> > 5. Requirements
> >     5.1 Requirements for Data on the Web Best Practices
> >     5.2 Requirements for Quality and Granularity Description Vocabulary
> >     5.3 Requirements for Data Usage Description Vocabulary
> >>From the existing use-cases, we will extract the general challenges and
> draft the initial requirements. This will be done by Thursday, so we can
> discuss at Friday's telco. Based on initial feedback, we will prepare a
> second draft by Monday's F2F, which we can discuss in more detail in London
> > So please if you haven't added your use-cases yet, add them today! Or
> update some of the existing ones with more detail.
> >
> > Cheers,
> > Deirdre & Bernadette
> >
> > -----------------------------------------------------------------------
> > Deirdre Lee
> > Research Associate
> > eGovernment Domain (DEG)
> > Insight-NUIG
> > IDA BusinessPark, Lower Dangan,
> > Galway, Ireland
> >
> > deirdre.lee@deri.org<mailto:deirdre.lee@deri.org>
> > skype: deirdrelee
> > twitter: @deirdrelee
> > linkedin: ie.linkedin.com/in/leedeirdre/<
> http://ie.linkedin.com/in/leedeirdre/>
> > -----------------------------------------------------------------------
> >
> >
>
>
> --
> Brazilian Internet Steering Committee - CGI.br
> W3C Brazil Office
> @yaso - yaso.eu
>
> 55 11 5509-3537 (4025)
> skype: yasocordova
>
>


-- 
Bernadette Farias Lóscio
Centro de Informática
Universidade Federal de Pernambuco - UFPE, Brazil
----------------------------------------------------------------------------