Human friendly presentation of class and property information (proposal)

(example used: http://vocab.deri.ie/cogs#AdHocProcess)

Currently the presentation of a class looks like this:

Class: [Class fragment identifier]
[Class name] - [description]
URI: [full class URI identifier]
Superclass: [Superclass fragment identifier]
Subclasses: [subclass fragment identifiers]

This is a very technical presentation of the class information. It would be 
great if the human friendly view of  a vocabulary displayed human friendly 
information first and technical details second. Rewriting the above example 
(http://vocab.deri.ie/cogs#AdHocProcess) it could look like this:

---
_Ad Hoc Process_ - a kind of _Execution_

Definition:
Process that seeks a solution designed for a specific problem or task, 
non-generalizable, and not intended to be able to be adapted to other purposes.

Identifier (URI):    http://vocab.deri.ie/cogs#AdHocProcess
Superclass:    _Execution_
Subclasses:    _Automated ad-hoc process_, _Manual ad-hoc process_

---

In short, provide human friendly data first using the labels entered 
(identifiers later). This would make vocabularies easier to read for domain 
experts (that may have trouble reading a document with too much technical 
jargon).

Original issue reported on code.google.com by pe...@peterkrantz.se on 16 Jul 2012 at 5:09

guidocecilio / neologism

Human friendly presentation of class and property information (proposal) #209