Skip to content

PlinianCore_Classes

WUlate edited this page May 1, 2022 · 71 revisions

To understand how the Plinian Core standard is built, we need to know how the elements of the standard are structured.

Most elements are grouped in complex in complex terms, which are defined as "types". These types are called "classes" in some contexts. For most of the content bearing terms, Plinian Core allows for containing information in two fashions: unstructured or structured. Thus, these types fork in two branches: one as a single element --in which content is contained as a text block (unstructured)-- and the other organizing the content in a series of elements, in an structured way, which is refereed in Plinian Core as "atomized". This arrangement allows for implementing Plinian Core with different levels of granularity depending of the specific project requirements while maintaining a a high degree of interoperability between projects.

Whether users choose to implement the unstructured or the atomized terms, they can add context to each content item by using the the AncillaryData element, borrowed from the Encyclopedia of Life Schema, where images, references, rights, etc. can be recorded.

Types in Plinian Core can be "Simple" --those containing only atomic terms, i.e., elements that do not contain other elements; or complex, types that contain elements containing other elements.

List of the types that make up the standard of Plinian Core:

Complex classes:

Simple classes:

Clone this wiki locally