- From: Harshvardhan J. Pandit <me@harshp.com>
- Date: Tue, 23 Apr 2019 18:11:24 +0100
- To: Axel Polleres <axel.polleres@wu.ac.at>, public-dpvcg@w3.org
- Message-ID: <d5b28e25-326e-431c-7d55-e524a0288170@harshp.com>
Hi Axel, I automated the import procedure so it now imports the HTML from spreadsheet into the document. To do this, execute the generate_docs.sh script from the repo, and it will fetch latest data from spreadsheet and google doc and combine them. See for example: https://dpvcg.github.io/extract-sheets/dpvcg.html It's possible (possibly trivial) to clean Google's CSS and structure, and to use our own CSS in the future. Regards, Harsh DEVNOTE: One thing to note is that editing the import lines in Google Doc breaks this process, so if anyone makes any changes to the line containing import, then the entire #import TAB.html line has to be rewritten so that it occurs together in the HTML output - otherwise Google breaks it into separate spans. On 22/04/2019 13:54, Axel Polleres wrote: > Note: this also completes - in essence - a proposed process for ACTION-97 "Define a process to get from spreadsheets to spec." > > My proposed simple process for now is: > > 1. Fill all the fields in the spreadsheets following the template and column order from the "BaseOntology" tab. > 2. Run: > python dpvcg-extract.py 'BaseOntology' > BaseOntology.html > python dpvcg-extract.py 'TechnicalOrganisationalMeasure' > TechnicalOrganisationalMeasure.html > python dpvcg-extract.py 'PersonalDataCategory' > PersonalDataCategory.html > python dpvcg-extract.py 'Processing' > Processing.html > python dpvcg-extract.py 'Purpose' > Purpose.html > python dpvcg-extract.py 'RecipientsDataControllersDataSubjects' > RecipientsDataControllersDataSubjects.html > python dpvcg-extract.py 'LegalBasis' > LegalBasis.html > python dpvcg-extract.py 'Consent' > Consent.html > > (note that for now this really only works well for the base ontology, you need to cleanly fix your spreadsheets to follow the example in order to produce reasonable outputs...) > > 3. In the raw document, at > https://docs.google.com/document/d/1Z3Eb5rZjrdWcE5u5o0CYzA_LPyGaTqmg84ecGve_ZLA/ > I have for the moment added placeholders, where the respective HTML should be added, just putting lines such as > #import BaseOntology.html > > into the gdoc (Please do not remove these'#import' lines for now!) > > 4. replacing these imports and importing the html files generated in step 2 can be done with a combination of tidy and some other scripts, but the result isn't yet very clean, so I would like to put this process up for discussion... for the moment, I attach a manual import where I replaced BasOntology.html. > > For the moment, though, I think this is good enough to work for everybody, if you: > * complete the explanations of the terms in the spreadsheet > * add explaining text in the gdoc. > > best regards, > Axel > > -- > Prof. Dr. Axel Polleres > Institute for Information Business, WU Vienna > url: http://www.polleres.net/ twitter: @AxelPolleres > >> On 22.04.2019, at 14:21, Axel Polleres <axel.polleres@wu.ac.at> wrote: >> >> Hi all, >> >> As per ACTION-89 I did a pass over the BaseOntology on >> https://docs.google.com/spreadsheets/d/13d1eRXZZBCw84vYGoCJeMU08rzkkzadDzxY3n2iOi8k/edit#gid=0 >> >> Additionally, I wrote a python script that extracts html out of the google spewadsheet, which can serve as a basis for the spec. >> Attached the script (dpvcg-extract.py) and the html it generated (BaseOntology.html). >> >> If you want to run/use this, you need to enable the spreadsheets API in google spreasheets >> and install google-api-python-client, cf. [1] >> >> >> <BaseOntology.html><dpvcg-extract.py> >> >> 1. https://developers.google.com/sheets/api/quickstart/python >> >> >> -- >> Prof. Dr. Axel Polleres >> Institute for Information Business, WU Vienna >> url: http://www.polleres.net/ twitter: @AxelPolleres >> -- --- Harshvardhan Pandit PhD Researcher ADAPT Centre Trinity College Dublin
Received on Tuesday, 23 April 2019 17:13:00 UTC