Re: the Best Practices skeleton

+1 to having a strong narrative element to the document.

ed


On Mon, 29 Jun 2015 at 01:46 Kerry Taylor <Kerry.Taylor@acm.org> wrote:

> 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>
>>
>>
> --

Ed Parsons
Geospatial Technologist, Google

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