Re: Sample activity lists in standard format

Hi all,

After looking at the PDFs I was wondering what the terms 'BT', 'NT', 'TT'
next to activities meant. Just in case anyone else is having the same
thought, I thought I'd send out Leigh's answers to my query.

This is SKOS terminology, and has been included by the PDF generation tool
rather than being something specifically related to OpenActive's standards.

   - TT references to top terms, if necessary.
   - BT references to broader terms.
   - NT references to narrower terms.
   - RT references to related terms.

This link
<https://www.w3.org/2006/07/SWD/wiki/SkosDesign/PresentationInformation>
provides some more information on what these mean, and gives a couple of
examples.

Hope this helps anyone else who may be in the dark!

Thanks,

Sally

On 20 March 2017 at 15:54, Leigh Dodds <leigh.dodds@theodi.org> wrote:

> Hi,
>
> At our last call I took an action to convert some of the activity lists
> provided so far into a common JSON format.
>
> You can find the results of that here:
>
> https://github.com/openactive/w3c-cg-example-data/tree/
> master/activity-lists
>
> I've only converted the Sports Suite, Sport England and Open Sessions
> lists for the moment but they all demonstrate different aspects of the
> model.
>
> The Open Sessions list is a flat list of names, while the other two
> include more complex hierarchies.
>
> For the Sports Suite and Sport England lists I've also done a conversion
> to PDF using a SKOS visualisation tool. This might help with identifying
> overlaps. (And also provides a reference if you're not happy reading the
> data!)
>
> The JSON format is close to what I'd expect to be recommending in the
> standard. The main change I forsee is how the JSON LD context is specified.
> Currently this is provided inline for each file, but we'll be publishing a
> context at a standard location, so the first few lines of each file will be
> replaced with a simple link. We can also simplify some of the property
> naming to remove prefixes (e.g. "narrower" rather than "skos:narrower").
>
> I'm also intending to specify a CSV format for Activity Lists that should
> allow the same data to be specified in alternative formats.
>
> The sample activity list from Imin is actually a merge of data collected
> other providers. As it includes occurrence counts and names the source of
> the data, its most useful as evidence of overlaps between existing lists.
>
> If anyone has any comments or questions then please let me know.
>
> Cheers,
>
> L.
>
> --
> Leigh Dodds, Senior Consultant, theODI.org
> @ldodds
> The ODI, 65 Clifton Street, London EC2A 4JE
>
>


-- 
Sally Jenkinson
*ODI Associate*
The Open Data Institute <http://theodi.org>
The ODI, 65 Clifton Street, London EC2A 4JE