Ecosyste.ms: Awesome

- Dublin Core
Terms provide basic bibliographic metadata,
- The
Bibliography
Ontology provides additional bibliographic metadata plus dozens
of useful document types,
- FRBR Core and
Extended
provides terms for modeling even more sophisticated intertextual
relations,
- SKOS provides a
rich substrate for concept schemes and taxonomies,
- Friend of a
Friend and
The
Organization Ontology give us models of people and business
entities,
- The Event Ontology enables the modeling
of processes, factors, and outcomes,
- The
Provenance Ontology gives us a vocabulary for recording the
handling of content over time,
- The
Data Cube
Vocabulary organizes quantitative and statistical data.

This document is organized in terms of
[Classes](https://vocab.methodandstructure.com/content-inventory#sec-classes),
[Properties](https://vocab.methodandstructure.com/content-inventory#sec-properties),
[Individuals](https://vocab.methodandstructure.com/content-inventory#sec-individuals),
and an appendix for the [Data Structure
Definition](https://vocab.methodandstructure.com/content-inventory#sec-dsd)
for quantitative content analytics. Terms are organized topologically
first, and alphabetically second.

### Reading the Examples

Examples are given in [the Turtle
syntax](https://www.w3.org/TR/turtle/). The basic syntax reads like so:

; .

, .

That is, complete statements are separated by periods, predicate-object
pairs are collated by semicolons, and sets of objects are separated by
commas. Turtle also provides for prefix
mappings to shorten the terms. This is denoted by:

@prefix p: .

and thus would map `p:some-term` to
`https://example.club/long/uri/some-term`. Note that these strings are
just concatenated together, in contrast to conventional relative URI
resolution. Terms belonging to this specification have been emphasized
to make them easier to pick out.

## Classes

There are currently many extant vocabularies that deal with documents
and related entities. The classes here are those that aren't otherwise
accounted for.

![This diagram shows the classes and properties defined in this document
using solid lines, and third-party classes and properties using dashed
lines.](https://vocab.methodandstructure.com/content-inventory-classes)

### Editorial Action

These classes enable the assignment of specific things to *do* to a
document.

#### `Action`

An action, as its name implies, is meant to represent something a person
or other agent ought to do to a document.

Being a subclass of an event, a `ci:Action` can have agents, factors,
products, places and times ascribed to it.

Subclass of:
ev:Event

Currently defined:
- [`keep`](https://vocab.methodandstructure.com/content-inventory#keep)
- [`split`](https://vocab.methodandstructure.com/content-inventory#split)
- [`tentative-merge`](https://vocab.methodandstructure.com/content-inventory#tentative-merge)
- [`update-metadata`](https://vocab.methodandstructure.com/content-inventory#update-metadata)
- [`proofread`](https://vocab.methodandstructure.com/content-inventory#proofread)
- [`revise`](https://vocab.methodandstructure.com/content-inventory#revise)
- [`rewrite`](https://vocab.methodandstructure.com/content-inventory#rewrite)
- [`retire`](https://vocab.methodandstructure.com/content-inventory#retire)

#### `Merge`

In order to merge a document, we must define the target to which it
ought to be merged. This class is identical to an Action, save for such
a property.

Subclass of:
ci:Action

Properties:
ci:target

### Document Classes/Decorators

Ontologies like BIBO are far from exhaustive in their breadth of
document types, so any additional salient document types will go here.

#### `Abstract`

This is an explicit document abstract/executive summary class, intended
to belong to BIBO, which appears to be abandonware.

Subclass of:
bibo:DocumentPart

#### `Advertisement`

In general there is no programmatic way to tell whether a resource is an
advertisement, since advertisements on the Web look (to a machine) like
any other resource. This is intended to be a decorator class to indicate
that the subject is an advertisement. It can therefore be combined with
other classes such as `foaf:Image`, or `bibo:AudioVisualDocument`.

```
@prefix bibo: .
@prefix dct: .
@prefix foaf: .
@prefix ci: .

a bibo:Article ;
dct:title "17 Mindblowing Ways to Write Listicles!"@en ;
dct:hasPart .

a foaf:Image, ci:Advertisement ;
dct:title "Punch The Monkey And WIN!#@$!%%^!"@en .
```

Subclass of:
foaf:Document

#### `Appendix`

This is an explicit document appendix class, intended to belong to BIBO,
which appears to be abandonware.

Subclass of:
bibo:DocumentPart

#### `Block`

This is intended to represent a generic block-level segment, such as a
paragraph, list, figure, or table.

Subclass of:
bibo:DocumentPart

#### `Section`

This is an explicit document section (i.e., sub-chapter) class.

Subclass of:
bibo:DocumentPart

### Variation

This section is for classes that have to do with creating content that
can vary. Currently the only class defined is `ci:Variable`, which is a
way to refer to values which are defined elsewhere and thus can maintain
their consistency across the document.

#### `Variable`

Identifies a variable which can be embedded into a document and assigned
an `rdf:value`.

Consider the markup:

Shingy's bill-out rate is
100.00
USD
per hour.

…which when parsed will produce the statements:

@base .
@prefix rdf: .
@prefix xsd: .
@prefix dct: .
@prefix ci: .

<> dct:references <#rate>, <#unit> .

<#rate> a ci:Variable ; rdf:value "100.00"^^xsd:decimal .
<#unit> a ci:Variable ; rdf:value "USD"^^xsd:token .