Re: the Best Practices skeleton

Hi All,

I will put this on the agenda for tomorrow's call, I would like to get the
input from the editors as to the best way to do this...

Ed


On Tue, 30 Jun 2015 at 09:43 Frans Knibbe <frans.knibbe@geodan.nl> wrote:

> 2015-06-30 4:52 GMT+02:00 Thiago José Tavares Ávila <thiago.avila@ic.ufal.
> br>:
>
>> Ok Kerry and Frans. I want to collaborate with these stories.
>>
>> If I understand correctly we may have a good narrative using some characters
>> (like Alice, Bob or Carol) crossing all Best Practices for publishing
>> spatial data and Best Practices for consuming spatial data.
>>
>> What is the best way to extract the best practices (for publishing and
>> consuming) from the use cases, considering the great experience of all
>> of you?
>>
>
> Hello Thiago,
>
> It seems to me that the best way to create best practices is to look at
> the requirements for the Best Practices deliverable in the Use Cases and
> Requirements document.
>
> One idea was to add a bit of javascript to the UCR document that creates
> an overview of requirements by deliverable. If the BP editors think that
> would be helpful I will add an action item to the tracker to ensure this
> will be done.
>
> As for the narratives, you could consider starting with a bare collection
> of best practices and add narratives that 'connect the dots' later. By the
> way, I think an additional benefit of storytelling is that it will be a
> kind of check for completeness. If there are holes in a story that could be
> an indication of the best practices not being complete.
>
> Greetings,
> Frans
>
>
>>
>> All the best.
>>
>> Thiago
>>
>>
>> 2015-06-28 21:45 GMT-03:00 Kerry Taylor <Kerry.Taylor@acm.org>:
>>
>>> I like this idea. We would need then two overlaid structures, pointing
>>> to the same underlying  detail, rather like the UCR doc. In this case there
>>> would be more narrative, perhaps making it trickier to write so that it
>>> hangs together, but it does seem like a useful way to do it. Do you know
>>> those "pick-a-path"children's stories? At the end of each chapter the
>>> reader  gets to choose from 2 different resolutions of the problem so they
>>> go through the story in different ways but they all traverse towards the
>>> same ending( ie outcome).
>>>
>>> Kerry
>>>
>>>
>>>
>>> On 29 Jun 2015, at 1:34 am, Thiago José Tavares Ávila <
>>> thiago.avila@ic.ufal.br> wrote:
>>>
>>> Hello Frans.
>>>
>>> I agree about using stories to illustrate the needs of the users of our
>>> best practices. To be clear, at what part of the skeleton the stories will
>>> be written ? Will it be a running example, crossing all the topics ?
>>>
>>> Congrats. Thiago.
>>>
>>> IntroductionWhy we are herePrinciplesTarget audience (ie producers and
>>> consumers, characterised as discussed)Identity and IdentifiersSpatial
>>> Relations/ OntologiesGeometry and CRSAPI and Implementation services
>>> MetadataAspects related to Time, SSN and CoveragePerhaps just the
>>> integrated view of these threeConclusion
>>>
>>> 2015-06-25 6:12 GMT-03:00 Frans Knibbe <frans.knibbe@geodan.nl>:
>>>
>>>> Dear group.
>>>>
>>>> We did not get to discuss the Best Practices skeleton at the meeting
>>>> yesterday but I did think about the item a bit so I would like to share my
>>>> thoughts before they fade away.
>>>>
>>>> The suggested skeleton
>>>> <https://www.w3.org/2015/spatial/wiki/Notes_for_Context#Suggested_Skeleton>
>>>> looks like the document is going to be a collection of recommendations,
>>>> with chapters grouping together strongly related recommendations. I think
>>>> it could be nice to present recommendations in the form of recipes or
>>>> stories. Not instead of the suggested structure, but perhaps next to that.
>>>>
>>>> Two basic stories that can be told are:
>>>>
>>>>    1. How to publish spatial data on the web
>>>>    2. How to consume spatial data on the web
>>>>
>>>> Such stories could provide step by step instructions on what to do,
>>>> illustrated by examples. If such general stories will have too many
>>>> variations, some more focused stories could be told, for instance:
>>>>
>>>>    1. Alice has a data set containing spatial data. She thinks it
>>>>    might be useful to someone, so she wants to publish it on the web. Which
>>>>    steps does she need to take?
>>>>    2. Bob is developing a smart phone application that provides a user
>>>>    with information based on current location. How can he tap in to the web of
>>>>    spatial data and put the data to use in his application?
>>>>    3. Carol is doing research on global climate change. How can she
>>>>    find and query the data that might be applicable to her research?
>>>>
>>>> Of course the collected use cases could serve as a source of
>>>> inspiration for specific stories.
>>>>
>>>> I believe stories are easy to read and easy to understand. And I think
>>>> that step by step instructions with examples are what many people would
>>>> appreciate.
>>>>
>>>> Next to stories we could have a comprehensive set of recommendations on
>>>> various subjects. That would allow people to look up information about a
>>>> specific subject. Such reference information could be structured according
>>>> to the suggested skeleton. From the stories references could be made to
>>>> those recommendations, allowing someone reading a story to drill down to
>>>> background information, if required.
>>>>
>>>> Regards,
>>>> Frans
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Frans Knibbe
>>>> Geodan
>>>> President Kennedylaan 1
>>>> 1079 MB Amsterdam (NL)
>>>>
>>>> T +31 (0)20 - 5711 347
>>>> E frans.knibbe@geodan.nl
>>>> www.geodan.nl
>>>> disclaimer <http://www.geodan.nl/disclaimer>
>>>>
>>>>
>>>
>>
>
>
> --
> Frans Knibbe
> Geodan
> President Kennedylaan 1
> 1079 MB Amsterdam (NL)
>
> T +31 (0)20 - 5711 347
> E frans.knibbe@geodan.nl
> www.geodan.nl
> disclaimer <http://www.geodan.nl/disclaimer>
>
> --

Ed Parsons
Geospatial Technologist, Google

Mobile +44 (0)7825 382263
www.edparsons.com @edparsons