I meant (with respect to earlier screenshot): 'Properties (5) - of class SpdxElement' 'Properties (4) - of class SpdxItem' 'Properties (11) - of class Package'
________________________________ From: Bill Schineller Sent: Tuesday, July 29, 2014 1:57 PM To: Gary O'Neall; [email protected] Subject: RE: RDF documentation update Good stuff Gary! I see what you're trying to do. I had to look closely at the screenshot to figure out which of the Superclasses each bucket of inherited properties is inherited from. Beggars can't be choosers, but an enhancement might be to indicate a little more clearly for each 'inherited' property, which Superclass it was inherited from. Perhaps next to the word 'Properties (5)' it could be altered to say 'Properties (5) - of class SpdxElement' 'Properties (4) - of class SpdxItem' 'Properties (11) - of class Package' ________________________________ From: [email protected] [[email protected]] on behalf of Gary O'Neall [[email protected]] Sent: Monday, July 28, 2014 6:17 PM To: [email protected] Subject: RDF documentation update Greetings all. I've been working on the problem of the RDF documentation and I think I came up with a solution. I downloaded the source for the RDF HTML documentation plugin that runs in Protege (OWLDoc). After a bit of sleuthing, I was able to figure out how it worked and modify it to better meet our needs. I made 3 significant changes: 1. I split the superclass restrictions into 2 parts - Superclasses, and properties. The latter being superclass restrictions on a property. 2. For the Superclasses, I generated and superclasses of the superclasses, so you can see the nesting all the way up to Thing. I also added the properties of the superclass, so you can see all the properties of the package within a single HTML page. The embedded superclasses are "boxed", so that you can see the nesting visually. You can see that below in the SpdxItem has a superclass SpdxElement. 3. If a property restriction is "min cardinality 0", I render that as "optional" - you can see that below in the annotation optional Annotation. Below is a screenshot of what it generates for the Package class. Although there are some limitations with the OWLDoc design, I may be able to modify the output further - so let me know what you think. Gary [cid:[email protected]] ------------------------------------------------- Gary O'Neall Principal Consultant Source Auditor Inc. Mobile: 408.805.0586 Email: [email protected]<mailto:[email protected]>
_______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
