Re: automated prov-o html prototype

Great work Tim. You managed to make the automation work in no time :-)

Just a couple of observations.

- Currently in Section 2 " PROV-O at a glance" will be better in the 
Introduction, or in Section 3. For example the example can be mentioned 
in the intro paragraph of Section 3.
- Section 2, should be compact, and will contains mainly the three 
indexes of the terms in the three parts of the ontology. I notice that 
such indexes are in Section 3!
- If we go with the option of having one example that is shown mainly in 
Section 3.1 (Core terms) and Section 3.2 (Qualified relationships), then 
I think that we will not anymore need the "hide/show examples" button. I 
didn't discuss this last point with jun, so she may have a different 
opinion.

Thanks, khalid

On 06/03/2012 02:23, Timothy Lebo wrote:
> prov-o,
>
> I have a prototype that shows the essential features that we discussed today in our telecon:
>
>
> 0) Follows the new section organization from Khalid and Jun.
>
>
> 1) Permitting areas for manual editing
>
> This can be done by editing the main body, or a separate file that is included upon page request.
>
>
> 2) Listing classes and properties according to the "three categories"
>
> This is done via SPARQL query into a triple store named graph that caches http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceOntology.owl
>
>
> 3) Including manually-created diagrams.
>
> This is done by traditional HTML.
>
>
> 4) Example hiding
>
> Taken from the previous WD. The input type is odd but can be fixed.
>
>
> 5) Including examples directly from the version controlled examples listed in http://www.w3.org/2011/prov/wiki/PROV_examples
>
> This is done a priori with a script that fetches the examples to include, which are then included upon page request.
>
>
>
> The prototype can be seen at:
>
> http://aquarius.tw.rpi.edu/prov-wg/prov-o
>
> The code is version controlled at https://github.com/timrdf/prov-lodspeakr/tree/master/components/services/prov-o
>
>
> Suggestions and feedback welcome.
>
> Regards,
> Tim
>