Simple Enumerations Helpful in Defining Ontology
For others not so simple see hierarchies.htm
For earlier discussion see typesofoccurrence.htm
This is not a PSI-tree, but it is a sketch for one that could be built
to publish unique IDs for various things one can select - typically as
the enumerated legal values for an attribute of a home page or DatedResource.
In each sub-tree below, we could add more options, and better
definitions. These are simply working examples.
- Summary (of a Page Type)
- Modality (Format)
- HTML text
- graphic or image component
- spreadsheet
- PDF file
- Versioning of Recurring Pages
- page subject does not recur regularly
- page instance always cites latest data
- page instance should be rebuilt daily
- page instance should be rebuilt weekly
- page instance should be rebuilt monthly
- Attribution Policies
- page is not attributed
- page attributed to staff or analyst(s)
- page attributed to specific analyst(s)
- Tagging Policies
- page is not to be tagged
- page tagged by its attributed authors
- page tagged by someone else (who?)
- resourceData details
- Range = a PSI node ID from each list above
- list is comma separated; order irrelevant
- must indicate one PSI from each list
- Cardinality = exactly 1 set
- Updated = by UI coders only
- Comments = describes a page type internally
- Obligation (of a Company or Country)
- Currency Type
- Dollar
- Euro
- Yen
- Sterling
- Debt Markets
- US
- Europe
- Asia
- resourceData details
- Range = a PSI node ID from each list above
- list is comma separated; order irrelevant
- must indicate one PSI from each list
- Cardinality = 0 or more combinations as needed
- Updated = by Analysts only
- Comments = describes how bonds are sold
- Market could be a filter on what to display
- Currency seems related, but unsure how