2026-02 NJC: removed multi-language tags and all things imported, not defined here
Copyright 2019-, International Council on Archives (ICA)
RiC-O (Records in Contexts-Ontology) is an OWL ontology for describing archival record resources. As the third part of Records in Contexts standard, it is a formal representation of Records in Contexts Conceptual Model (RiC-CM).
International Council on Archives Records in Contexts Ontology (ICA RiC-O) version 1.0.1
In order to manage an instantiation of a record resource it is necessary to note the extent of the carrier as well as that of the instantiation itself. Whether it is necessary to note dimensions, the number of relevant units or both depends on the nature of the carrier and particular business needs.
Number of physical units and/or physical dimensions of the carrier of an Instantiation.
Class implementation of RiC-A04 (Carrier Extent) attribute
Physical or logical extent of a resource
Countable characteristics of the content of an entity expressed as a quantity.
When it exists, specifies the identifier and name of RiC-CM component that corresponds to the annotated class or property.
Countable characteristics of an Instantiation expressed as a quantity.
Class implementation of RiC-A23 (Instantiation Extent attribute)
The method and precision of expressing the quantity of information represented in a Record Resource will vary according to the kind of record resource being described, processing economy constraints, etc. For Record Sets, quantity may be expressed as number of records, or, for analogue records in particular, by the physical storage dimensions of the members of the Record Set. For individual Records or Record Parts, quantity may be expressed in more precise terms.
The quantity of information content, as human experienced, contained in a Record Resource.
Class implementation of RiC-A35 (Record Resource extent attribute)
Accruing - there is an agreement with the creator that additional snapshots of their email directory will be accessioned at yearly intervals
Information on the anticipated accession(s) to the Record Set.
corresponds to RiC-A01 (Accruals attribute)
Record set is a kind of Record Resource. The member records in a Record Set may physically reside together, though physical proximity is not essential. In a particular context, an Agent (for example, administrator, records manager, archivist, end-user, etc.) may select the member records of a Record Set based on any shared attribute or attributes, or any shared relation or relations. The grouping of the records serves a purpose or purposes specific to the context of the Agent. For example, all member records of a Record Set have been accumulated by the same Agent; have the same Documentary Form Type; or are related to and document the same Activity. A Record Set may represent the act of classifying the records in accordance with a formal classification scheme that may be based on activity, subject, organizational structure, or other criteria; an act of archival arrangement (for example, based on common provenance); or some other selection and grouping that fulfils a particular purpose or purposes (for example, a classification that reflects or supports the purposes of a researcher). By exception, some records are brought together based on their not belonging in the context of selection to other designated groups: a 'Miscellaneous' series, for example. A Record Sset accumulated by an Agent in the course of life or work activity should be described in a manner that preserves context and evidential value. Record Sets may also contain other Record Sets. A Record Set or Record may simultaneously be a member of more than one Record Set, and over the course of its existence, a Record Set or Record may be a member of an indeterminate number of Record Sets in an indeterminate number of contexts. Record Sets and Records contained within a Record Set may be ordered into a sequence based on a common property or relation, or common properties or relations (for example, alphabetical by agent or related place); chronological order by creation date; or some other criterion (for example, an imposed order by relevance).
One or more records that are grouped together by an Agent based on the records sharing one or more attributes or relations.
Corresponds to RiC-E03 (Record Set entity)
A text statement or single words such as “Closed” to indicate that no additional Record Resource will (or is anticipated to) be added to the Record Set; “Open” to indicate that additional records or record sets will (or are expected to) be added to the Record Set; or “Unknown” to indicate that this information is not available, for example. See also accruals
Information on the status of possible accruals
specialization of RiC-A01 (Accruals attribute)
Longitudinal and latitudinal information about a Place.
Class implementation of RiC-A11 (Coordinates attribute)
Framework or standard used to represent an information.
Property of the Coordinates class. If you don't use this class, use geographicalCoordinates property, a property of Place class.
The height of a Place above a reference level, especially above sea level.
The extent, quantity, amount, or degree of an entity, as determined by measurement or calculation.
The deed is digitally signed by the Notary. The electronic signature validity cannot be assessed, but the content was not modified from the moment of signing.
The timestamp exists but cannot be verified.
May be used in a Record Set description when its value is shared by some or all members of the Record Set. For digital records, it may include results from automated means of checking the validity of signatures and timestamp. In particular cases it may be contextually related to the state attribute, for example, a document can be an original or a copy, either of which can be authentic or a forgery.
Description of the evidence that a Record Resource or Instantiation is what it purports to be, was created or sent by the said Agent at the said time, and has not been tampered with, corrupted, or forged.
Corresponds to RiC-A03 (Authenticity Note attribute)
A Record or Record Part must have been instantiated at least once, though this instantiation may no longer exist at the moment of description. An instantiation might also exist at the moment of description, but be destroyed at a later moment in time, when, for example, a derived instantiation might become the only remaining instantiation. A Record Set may have an instantiation, which is to say that it is not a necessary condition. An Instantiation may be derived from another Instantiation. A Record Resource may have many Instantiations simultaneously (for instance, a record printed and saved in the same time as DOCX and PDF/A would have 3 concurrent instantiations) or through time (for example, copy of a record). Depending on the context, a new instantiation may be seen as a new or as the same record resource. During in the process of re-instantiation something is lost and something is preserved, but it is up to the context and the Agent that produces or uses that Instantiation to assess whether the two instantiations are functionally equivalent or not. For instance, a postcard representing a town map from 1874 (Instantiation 1) is digitized and kept as a JPEG file (Instantiation 2). The digital copy may be considered as instantiating the "same" Record by an Agent considering the information transmitted by the Record (e.g., the urban landscape displayed), but as a" different" Record by an antiquarian more focused on the materiality of the carrier. Successive instantiations may change the perceivable boundaries of a Record Resource. For instance, a case file comprising many records may be digitized and saved as one single PDF file, which, from management perspective, may be treated as one Record. Similarly, a large Record Set (a fonds or a series) may be maintained as one database. On the other hand, one record (main document and its annexes) may be digitized in separate files and each one may be managed as a discrete “physical” item. Instantiations may require mediation to communicate the information in the Record Resource. While a traditional Record on paper can simply be read by an Agent in order to understand the information, a vinyl recording, a video cassette or a digital file needs a device (mediator) to codify or decodify the information conveyed. This mediator may imply simple physical components (a turntable needle, for example), or a complex gallery of software and hardware elements. Instantiations are more than the mere informational content of Record Resource and may be the focus of preservation and physical management of records. The use of particular document types for records, such as a medieval charter, may have implications for the authenticity of the records. Hence, the way a Record Resource is instantiated contributes to the contextualizing of the content.record resource is instantiated contributes to the contextualizing the content. Distinguishing the message conveyed (Record Resource) and its physical representations (Instantiation) allows for the efficient management of their descriptions, and preserve information about a Record Resource even when no physical representation of it exists or is known to exist anymore. The relations between distinct instantiations can then be expressed wherever they coexist, and they can be related to the Record Resource they instantiate.
The inscription of information made by an Agent on a physical carrier in any persistent, recoverable form as a means of communicating information through time and space.
Corresponds to RiC-E06 (Instantiation entity)
Record resource is a kind of Thing. Producing a record resource may imply either its initial creation or a reuse of previous existing information by combination, rearrangement, selecting, reformatting, etc. Record set, record, and record part are kinds of record resource. A record resource is evidence of the activity of an agent. More than one agent may be involved in the creation of a record resource. The role of the agent in creating the record resource may take different forms, for example, authoring of an individual record, accumulating a record set, or arranging a record set. Though a record, record set, and record part, under most circumstances, may be easily distinguished from one another, identifying the boundary of each may frequently present particular challenges. Documentary forms provide the rules governing the structure of many types of records, providing criteria for identifying a record's boundary, and identifying its essential parts. Many records, though, do not have well-established documentary forms, particularly in the case of digital records, where it may be difficult to determine whether individual elements represented in separate bitstreams are record parts, records, or record sets. For example, is photographic information represented independently in a bitstream embedded in a text document a record or a record part? Or is the same photographic information attached to an email that maintains its independent representation, a record or a record part? Information grouped for some purpose, for example, ZIP or TAR "file compression" for saving storage space, presents a further challenge. One file comprises multiple bitstreams subjected to techniques that remove bits that can be losslessly recovered when decompressed. Under what circumstances is such a compressed bitstream a record or a record set? Determining when an information object is a record, record set, or record part is based on perspective and judgement exercised in a particular context. In one context, the agent describing an information object may designate it a record, while another agent in a different context may designate it a record part. Both designations are supported by RiC-CM, and the significance of the difference for users of the records is ameliorated by the fact that all of the attributes and relations employed in describing record and record part are shared, as are many of the attributes and relations employed in describing a record set.
Information produced or acquired and retained by an Agent in the course of life or work activity.
Corresponds to RiC-E02 (Record Resource entity)
Provided for usability reasons. May be deprecated and removed later on. Use only if you don't use the Mandate class for handling mandates.
Information on a Mandate that authorizes an Agent to perform an Activity.
An Agent may have one or more identities; an identity is a constellation of properties or relations that together “identify” the Agent. A Person or Group commonly has one identity, though each also may have one or more alternative identities. Such alternative identities may be shared by more than one Person or Group. Alternative identities include but are not limited to pseudonyms, heteronyms, DBA (Doing Business As), and trade identities. An alternative identity should not be confused with a Position in a Group, for example, presidents, prime ministers, governors, popes, royalty, or bishops. Nor should an alternative identity be confused with a variant name or identifier of the same identity. Agent also includes entities created by a Person or Group that act on behalf of the creating Agent in an autonomous or semi-autonomous manner. Examples of a Mechanism include software agents, robots, and space and underwater probes that generate data (records) in the course of Activity assigned to and in conformance with the instructions given to them by the creating Person or Group.
A Person, or Group, or an entity created by a Person or Group (Mechanism), or a Position, that acts in the world.
Provided for usability reasons. May be deprecated and removed later on. Use only if you don't use the Rule class for handling rules.
The rule or conditions that govern the existence or lifecycle of a Thing.
Provided for usability reasons. May be deprecated and removed later on. Use only if you don't use Date classes for handling dates.
Datatype property specialized implementation of RiC-E18 (Date entity)
Person is a kind of Agent. Most commonly, a human being (biological person) has a single socially constructed identity or persona. Less common though not rare, one or more personae in addition to the original persona which emerges at or near birth may be associated with the human being over the course of that human being’s lifetime. Such "alternative personae" are most often created by the original person for specific purposes. The original persona may, in everyday discourse, be regarded as “the real person”. Under some circumstances, an alternative persona might eclipse or replace the original person (Mark Twain eclipsing Samuel Clemens; John Wayne eclipsing Marion Mitchell Morrison), that is, the alternative identity becomes the predominant identity. Less common is when two or more persons collaborate to create a shared persona. A persona shared by two or more persons constitutes a kind of group. Within the archival context, the description of a person commonly will focus on the original associated persona, with alternative personae noted. Exceptionally, an alternative persona may displace the original persona as the focus of the description. Under some circumstances, for example, when record resources are associated with two or more different personae of one person, describing the different personae as separate though related persons may be desirable. Alternatively, a person may change their identity over the course of their lifetime.
For digital resources, it may be used to indicate the size of storage capacity (disk, tape, film, etc.). Carrier extent should not be confused with instantiation extent or record resource extent. For a given Record Resource, the instantiation extent may vary, based on format, density of information on the carrier, etc. For example, a CD with a storage capacity of 700 MB (carrier extent) might hold a record of 1500 words (record resource extent) represented in two versions, one a Word document with an instantiation extent of 3 KB and the other a PDF file with an instantiation extent of 5 KB.
Number of physical units and/or physical dimensions of the carrier of an Instantiation. In order to manage an Instantiation of a record resource it is necessary to note the extent of the carrier as well as that of the Instantiation itself. Whether it is necessary to note dimensions, the number of relevant units, or both, depends on the nature of the carrier and particular business needs.
Corresponds to RiC-A04 (Carrier Extent attribute)
Provided for usability reasons. Use only if you cannot use the subproperties (particularly if the same free text is being used in your current metadata for describing the record resource, carrier and instantiation extent).
BUD-01-F002 (classification number from a corporate file plan)
May be used in a Record Set description when its value is shared by some or all members of the record set. This datatype property is not to be confused with Identifier although, in some cases, the information may be the same.
A term, number or alphanumeric string that is usually taken from an external classification vocabulary or scheme that qualifies a Record Resource.
Corresponds to RiC-A07 (Classification attribute)
An annotation property for recording a possible mapping to a component in another model or ontology
Closed as awaiting conservation treatment
Closed under data protection legislation
Recognita software, min. version 3.0, is needed in order to open the file
The Archives cannot provide VHS reader to access the content of the tape
Acceso libre a través de los terminales de consulta
May be used in a Record Set description when its value is shared by some or all members of the Record Set. The attribute provides information about the accessibility of a Record Resource, as well as the physical, technical or legal limitations that exist for providing access to it.
Terms and circumstances affecting the availability of a Record Resource or an Instantiation for consultation.
Corresponds to RiC-A08 (Conditions of Access attribute)
Cannot be copied using warm light copying machines or photographed using flashlight
Permission of the copyright owner must be obtained before use
May be used in a Record Set description when its value is shared by some or all members of the Record Set.
Terms and circumstances affecting the use of a Record Resource or an Instantiation after access has been provided. Includes conditions governing reproduction of the Record Resource under applicable copyright (intellectual property) and/or property legislation or due to conservation status.
Corresponds to RiC-A09 (Conditions of Use attribute)
Includes all RiC entities as well as any concept, material thing, or event that may be the subject of a Record Resource or associated with an Activity. Examples of entities not explicitly addressed in RiC includes but is not limited to the following: abstract concepts; cultural movements, named periods and events; named things, objects and works; legendary, mythical or fictitious figures, characters or beings.
Any idea, material thing, or event within the realm of human experience.
Most often, this human readable expression of the accuracy of the date is used along with an ISO 8601 representation of the date. The qualifier can also be expressed as a machine-readable value, using the EDTF standard (thus, a specialization of the normalizedDateValue datatype property).
A human readable qualification of a Date to indicate the level of precision or certainty.
Corresponds to RiC-A13 (Date Qualifier attribute)
A Date may be represented in natural language, based on a digital standard, or both. Digital standard dates will typically be based on ISO 8601, or Extended Date-Time Format (EDTF)
Chronological information associated with an entity that contributes to its identification and contextualization.
The second semester of 1951 to 1952 (academic reference system)
15 thermidor an IV (calendrier révolutionnaire français)
Die jovis ultima mensis martii anno domini millesimo quingentesimo quadragesimo ante Pascha
Natural language expression of a date. This property is a specialization of the name property. In order that the precise meaning of the date can be understood, information such as the calendar used or other specific context should be included.
Corresponds to RiC-A19 (Expressed Date attribute)
Digital copy of the Pomarius archival inventory from 1575 (about an Instantiation)
Fundraising, University of Glasgow (about an Activity)
Papers of the Earls of Liverpool (about a Record Set)
Providing hearing services (about an Activity)
Sketch Map of the Qatar Peninsula (about a Record)
The Letter of Neacsu from Campulung to the Mayor of Brasov (about a Record)
Use only if you don't use Name class for handling names. Provides brief information about the content or other individual characteristics of the entity being described, necessary to distinguish it from other perhaps similar entities.
A label, title or term designating an entity in order to make it distinguishable from other similar entities.
Corrresponds to RiC-A28 (Name attribute)
A textual expression of an Appellation or Date.
Reference system used for geographical coordinates.
Provided for usability reasons. May be deprecated and removed later on. Use only if you don't use PhysicalLocation and Coordinates classes with Place. Coordinates may be based on ISO 6709 Standard representation of geographic point location by coordinates.
Corresponds to RiC-A11 (Coordinates attribute)
A jurisdiction is the bounded geographic area within which an Agent has the authority to perform specified activities constrained by rules. Jurisdictions, man-made structures, and natural features are historical entities. A Place thus may have a beginning date and ending date and changing boundaries that result from human or natural events. A Place may be systematically referenced to a location on the earth (geographic coordinates).
Bounded, named geographic area or region.
Connects two Persons that correspond or have corresponded with each other. This relation is symmetric.
RiC-R052 ('has or had correspondent' relation)
The relation implies that the two Persons met or at least corresponded with each other.
Connects two Persons that directly know each other during their existence. This relation is symmetric.
This property 'rolifies' the CorrespondenceRelation class. It should be used only when you have to manage instances of the CorrespondenceRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a CorrespondenceRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Correspondence Relation
Connects an n-ary Relation to any of the Things involved.
Connects two Persons who are or were married. This relation is symmetric.
Use hasOrHadMember for connecting a Family and a Person.
Connects two Persons that have some type of family link, i.e. belong to the same family. This relation is symmetric.
RiC-R047 ('has family association with' relation)
This property 'rolifies' the SpouseRelation class. It should be used only when you have to manage instances of the SpouseRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a SpouseRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
Connects two Agents that have or had some type of work relation in the course of their activities. This relation is symmetric.
RiC-R046 ('has or had work relation with' relation)
Use only if it is not possible to specify a narrower Agent to Agent relation, for example has or had work relation with.
Connects two Agents. This object property is symmetric.
RiC-R044 ('is agent associated with agent' relation)
This property 'rolifies' the WorkRelation class. It should be used only when you have to manage instances of the WorkRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a WorkRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
Connects two Persons who are siblings. This relation is symmetric.
This property 'rolifies' the SiblingRelation class. It should be used only when you have to manage instances of the SiblingRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a SiblingRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
The manuscripts are part of the collections of Robert Harley (d 1724) and Edward Harley (d 1741), 1st and 2nd Earls of Oxford, that were brought by Parliament and transferred to the British Museum in 1753. Those materials were then separated into this collection and those for Harley Charters and Harley Rolls and became part of the collections of the British Library in 1972. (about a Record Set)
El primer sorteo de lotería se celebró el 13 de mayo de 1771, siendo desarrollado por la Real Lotería General de Nueva España… (sobre una actividad)
Nacido en Barbastro en 1892, donde realizó sus primeros estudios con los escolapios. Licenciado en Derecho por la Universidad de Zaragoza, aprobó las oposiciones al cuerpo nacional de notarios… (sobre una persona)
For a record set, may be used to summarize the history of the Record Set itself, or additionally to summarize the history of some or all members of the Record Set. Should not be confused with the scope and content property.
Summary of the development of an entity throughout its existence.
Corresponds to RiC-A21 (History attribute)
An event may be caused by nature, an agent, or a combination of nature and agent. Events have temporal and spatial boundaries. An event may actively involve some agent(s) and affect any entity. An event may be discrete, happening at a specific moment in time, or may occur over an extended period of time. Events may have events as parts, and events may precede or follow one another. Multiple agents may participate in the same event, and in different roles.
Something that happens or occurs in time and space.
LODE Event class (http://linkedevents.org/ontology/#Event)
Rule is a kind of Thing. Rule can be related directly to agent, activity, or anything created or managed by agents, such as a record resource or instantiation. A rule may be unwritten or written or otherwise documented. Unwritten rules may include though are not limited to the following: social mores, customs, or community expectations. Written rules may include though are not limited to the following: constitutions, legislation, acts (legal), statutes, legal codes, ordinances, charters, mission statements, regulations, policies, procedures, instructions, codes of conduct or ethics, professional standards, work assignments, or work plans. The source or sources of some rules governing the existence or activity of an agent may be external (for example, expressed in elections, social mores, customs, community expectations, laws, regulations, standards, and best practice codes), while others may be expressed within the immediate context of an agent (for example, policies, or written or verbal instructions). The evidence for identifying rules may be found in their entirety in one documentary source (for example, a law or regulation) or may be found in two or more sources. Rule should not be confused with the one or more documentary sources that serve as evidence of its identity. A documentary source is a record.
Conditions that govern the existence, responsibility, or authority of an Agent; or the performance of an Activity by an Agent; or that contribute to the distinct characteristics of things created or managed by an Agent.
B-000091 (example of a unique identifier for an instantiation assigned by a repository)
BUD-01-F002 (example of a classification number from a corporate file plan)
F 1204 (example of a local identifier for a record set assigned by a repository)
NAS1/A/1.1 (example of a local identifier for a record)
http://isni.org/0000000073572182 (example of a persistent International Standard Name Identifier for a person)
http://n2t.net/ark:/99166/w6tz44ht (example of an Archival Resource Key for a person)
http://n2t.net/ark:/99166/w6v1266v (example of an Archival Resource Key for a record)
Use only if you don't use Identifier class for handling identifiers. Within a given domain (a closed system), identifiers are used to uniquely reference instances of an entity. Identifiers are instruments of control that facilitate management of the entities within the domain. The formulation of identifiers commonly is based on rules. In addition to an identifier needing to be unique within a domain, it is also highly desirable that it be persistent, that is, that the identifier uniquely identifies the entity over time. A variety of organizations provide rules for the formation of identifiers, and services designed to facilitate the persistence of identifiers. Such identifiers are commonly referred to as Persistent Identifiers (or PIDs). PIDs conform to RFC 3986, but impose additional rules. Common examples are Archival Resource Keys (ARKs) and Digital Object Identifiers (DOIs). Within the global environment of the Internet, there are special rules for the formation of identifiers to ensure that they are unique within the domain of the Internet. Such identifiers must conform to the Internet Engineering Task Force (IETF) Uniform Resource Identifier rules (RFC 3986).
A word, number, letter, symbol, or any combination of these used to uniquely identify or reference an individual instance of an entity within a specific information domain. Can include Global Persistent Identifiers (globally unique and persistently resolvable identifier for the entity) and/or Local Identifiers. Both the domain within which the identifier is unique, and the rules used in forming the identifier value should be provided with the identifier value.
Corresponds to RiC-A22 (Identifier attribute)
Instantiation extent should not be confused with record resource extent or carrier extent. For a given Record Resource, the instantiation extent may vary, based on format, density of information on the carrier, etc. For example, a CD with a storage capacity of 700 MB (carrier extent) might hold a record of 1500 words (record resource extent) represented in two versions, one a Word document with an instantiation extent of 3 KB and the other a PDF file with an instantiation extent of 5 KB.
Corresponds to RiC-A23 (Instantiation Extent attribute)
Information about the physical arrangement and composition of an Instantiation.
Specialization of RiC-A40 (Structure attribute)
Inside each file, the records are arranged chronologically (about a record set)
The database has three related tables: names, addresses, and passport numbers (about a record)
The record has two appendices, comprising a full account of the income from car taxes and real estate taxes
The series have the files arranged according to the alphabetical order of the places concerned
Use only if you cannot use the subproperties (particularly if the same free text is being used in your current metadata for describing the record resource and the instantiation structure). For a Record Set, may be used to summarize the structure of the Record Set itself, or additionally to summarize the structure of some or all members of the Record Set. Should not be confused with the classification datatype property, which provides information about the category which the Record Set belongs to within a classification scheme.
Information about the intellectual arrangement and composition of a Record Resource or the physical arrangement and composition of an Instantiation. For Record and Record Part, it encompasses information about the intellectual composition of the record, the presence of record parts and their functions. For Record Set, it encompasses information about the methodology or criteria used for arranging the Record Set members or Record members within the containing Record Set. For Instantiation, it may comprise information about the composition of the physical elements of the instantiation
Corresponds to RiC-A40 (Structure attribute)
A web page (HTML, 15 images, 2 CSS, 1 javascript), with 5 images missing.
For record set: series of letters, one is missing so the integrity is compromised.
Line three of a hand-written letter was cut out and a replacement text was inserted by an unknown person.
Part of the text is missing (because a corner on the instantiation was cut out, which is a physical characteristic). See also the examples of physicalCharacteristics.
May be used in a Record Set description when its value is shared by some or all members of the Record Set. The information about integrity may be generated manually or automatically. Not to be confused with the physical completeness of the instantiation, which is covered by the physical characteristics note attribute. The integrity of a Record Resource and the physical characteristics note of an Instantiation may be complementary. This attribute also covers any additions to or removal of original information.
Information about the known intellectual completeness of a Record Resource.
Corresponds to RiC-A24 (Integrity Note attribute)
Connects two Dates that overlap. This relation is symmetric.
Inverse of 'is date associated with' object property.
RiC-R068i ('is associated with date' relation)
Use to connect a date and an entity only if it is not possible to specify a narrower date relation, for example, is beginning date of.
Connects a Date to a Thing with whose existence and lifecycle the Date is associated.
RiC-R068 ('is date associated with' relation)
Two Instantiations, from some point of view, may be considered as equivalent. This equivalence is usually based upon the fact that the Instantiations have at least the same intellectual content (they instantiate the same Record Resource).
Connects two Instantiations which may be considered as equivalent. This relation is symmetric.
RiC-R035 ('is functionally equivalent to' relation)
Connects two Things that are considered equivalent.
Use only if it is not possible to specify a narrower Instantiation to Instantiation relation, for example is functionally equivalent to.
Connects two Instantiations. This relation is symmetric.
is instantiation associated with instantiation
RiC-R034 ('is instantiation associated with instantiation' relation)
This property 'rolifies' the FunctionalEquivalenceRelation class. It should be used only when you have to manage instances of the FunctionalEquivalenceRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a FunctionalEquivalenceRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Functional Equivalence Relation
Use for connecting two adjacent geographical or administrative regions.
Connects two Places that are or were geographically adjacent. This relation is symmetric.
RiC-R077 ('is or was adjacent to' relation)
Inverse of 'is place associated with' object property.
RiC-R074i ('is associated with place' relation)
Use to connect a Place to an entity only if it is not possible to specify a narrower spatial relation, for example, is or was location of.
Connects a Place to a Thing with whose existence and lifecycle the Place is associated.
RiC-R074 ('is place associated with' relation)
Date at which an entity was last updated.
Distance in degrees north or south of the equator.
May be used, among other cases, for storing the length of some places like streets.
25 rue Saint-Denis à Paris
Use only if you don't use PhysicalLocation class with Place. Use the geographicalCoordinates property, or the Coordinates class, to record the geographical coordinates of the Place. Use the spatial relations (particularly 'has or had location') to capture a relation between two places.
A delimitation of the physical territory of a Place. Used to describe basic human-readable text such as an address, a cadastral reference, or less precise information found in a Record.
Corresponds to RiC-A27 (Location attribute)
Distance in degrees east or west of a prime meridian.
1948-03 (an ISO 8601 form of a single date)
1948-03-08 (an ISO 8601 form of a single date)
1948-03~ (a single date in ETDF, meaning March 1948 approximately)
1948/ (a date range in EDTF, starting in 1948, end unknown)
1948/.. (an open date range in EDTF, starting in 1948)
2012/2015-03 (an ISO 8601 form of a date range)
Used to represent the date in a standardized format that can be processed programmatically. The main standard used today is ISO 8601, which is based on the Gregorian calendar. See also the Extended Date Time Format (EDTF), which is an extension of ISO 8601, and enables, among other features, to represent a date set, and to indicate the date is approximate.
Machine readable representation of the date based on a public technical standard.
Corresponds to RiC-A29 (Normalized Date attribute)
Value representation based on a standard, preferably machine-readable.
Connects two Places that geographically overlap or overlapped. This relation is symmetric.
RiC-R078 ('overlaps or overlapped' relation)
Use only if you have free text or don't have a controlled vocabulary for production techniques (in this case, use the ProductionTechniqueType class)
The method used in the representation of information on an Instantiation.
Corresponds to RiC-A33 (Production Technique attribute)
Date of the publication of a Record Resource.
Provided for usability reasons, like its subproperties. May be deprecated and removed later on. Use only if you don't use Date classes for handling dates.
Datatype property implementation of RiC-E18 (Date entity)
Black and white digitization may have led to loss of some information.
some loss of information due to poor quality of image capture
Quality of representation note is a specialization of physical characteristics note. Quality of representation note should be used in conjunction with physical characteristics note when the physical characteristics impact the ability to recover the intellectual content.
Characteristics of an Instantiation that affect the ability to recover the intellectual content. Such characteristics may be related to the methods used in creating the Instantiation or introduced subsequent to the creation through accident.
Corresponds to RiC-A34 (Quality of Representation Note attribute)
A web page (HTML, 15 images, 2 CSS, 1 JavaScript), with 1 CSS missing.
For carrier: hard drives on which the author wrote physically (using a pen).
Letter physical characteristics: corner without text missing – the carrier is damaged, but no information of the content is missing
Not to be confused with the intellectual completeness of a Record Resource and its sub-entities, which is covered by the Integrity attribute. May include digital file fixity.
Information about the physical features, completeness, or conservation status of an Instantiation. Includes information about the physical nature and condition such as conservation status or the deterioration of an Instantiation (for example its carrier) affecting the ability to recover information.
Corresponds to RiC-A31 (Physical Characteristics Note attribute)
Use if you use the Extent class and its properties for handling an accurate description of the extent of a resource.
Use if you don't use RecordResourceExtent class and its properties for handling such information. Record resource extent should not be confused with instantiation extent or carrier extent. The number, size or duration of the information content unit(s) remains the same even if the information is instantiated in various carriers. For example, a CD with a storage capacity of 700 MB (carrier extent) might hold a record of 1,500 words (record resource extent) represented in two versions, one a Word document with an instantiation extent of 3 KB and the other a PDF file with an instantiation extent of 5 KB.
The quantity of information content, as human experienced, contained in a Record Resource. The method and precision of expressing the quantity of information represented in a Record Resource will vary according to the kind of Record Resource being described, processing economy constraints, etc. For record sets, quantity may be expressed as number of records, or, for analogue records in particular, by the physical storage dimensions of the members of the Record Set. For individual records or record parts, quantity may be expressed in more precise terms.
Corresponds to RiC-A35 (Record Resource Extent attribute)
Inside each file, the records are arranged chronologically.
The database has 3 related tables: names, addresses, and passport numbers.
The record has 2 appendixes, comprising a full account of the income from car taxes and real estate taxes.
Information about the intellectual arrangement and composition of a Record Resource. For Record and Record Part, it encompasses information about the intellectual composition of the record, the presence of record parts and their functions. For Record Set, it encompasses information about the methodology or criteria used for arranging the Record Set members or Record members within the containing Record Set
Qualifies the level of certitude of the accuracy of a Relation.
Corresponds to RiC-RA01 (Certainty of Relation attribute)
Use when direct, binary object properties are not enough, e.g. when you need to record a date, a location or any other descriptive element for a relation (till RDF-Star becomes a W3C recommendation and provides a lighter method for doing so); or when the relation invloves more than two entities (n-ary relation). It is recommended to use the subclasses of the Relation class.
The top level relation class. It connects at least two Things. An instance of a Relation may have some datatype and object properties: a general description (datatype property) like any Thing; a certainty (for 'certain', 'quite probable', 'uncertain','unknown'); a date (use either the date datatype property or the Date class and isAssociatedWithDate object property); a state (relationState); a location (use the Place class and isAssociatedWithPlace object property); a source of information that can be used as an evidence for it (use either source datatype property or hasSource object property). This Relation is the most generic one; it is not oriented.
Use only if you don't use the 'isEvidencedBy' object property.
A source of information used for identifying and describing a Relation.
Corresponds to RiC-RA05 (Source of Relation attribute).
Used to qualify the state of a Relation (e. g. present, past, ongoing, unknown).
Among the witnesses, the Duke of Normandy.
Includes a detailed list of the lands and villages given by the King to the Abbey.
Letter from Vlad the Impaler (Dracula) to the Council of Kronstadt asking them to send military support against the Ottomans, within the framework of their alliance treaty.
The author explains why he does not agree with the decision made and adds that it cannot be applied.
Se hace referencia a construcción del Gran Hotel, iniciada en 1899 bajo el nombre de Casa Celestino. Tras su interrupción en 1902, continuó la obra ya con su nombre actual.
Scope and content is a specialization of general description. For a Record Set, may be used to summarize the scope and content of the Record Set itself, or additionally to summarize the scope and content of some or all members of the Record Set. It is not to be confused with the history dataytpe property which focuses on the origination and subsequent changes to a Record Resource.
Summary of the scope (such as time periods, geography) and content (such as subject matter, administrative processes) of a Record Resource. Provides a more complete summary of the informational content of the Record Resource highlighting the information conveyed in the Record Resource, why it was created, received, and/or maintained, and the agents connected to it. It may include description of relations with agents, activities, dates and places, or with other record resources.
Corresponds to RiC-A38 (Scope and Content attribute)
The Senate is the academic governing body of the University of Strathclyde and is responsible for all academic matters including academic standards and quality. Meetings of the Senate are chaired by the Principal and the membership is drawn entirely from within the University, comprising academic and research staff. (about a corporate body, University of Strathclyde Senate)
This activity involves regulating the nursing profession by conducting examinations and on-going education for nurses, maintaining rolls of those qualified as enrolled or registered nurses, midwives, psychiatric, and other specialised nurses. It also covers hearing disciplinary charges against nurses (and where necessary, removing them temporarily or permanently from the registers), as well as promoting the nursing profession. (about an activity, Nursing Profession Regulation)
General information about an entity. General description may be used to describe any entity. There are different appropriate uses for general description. First, while it is recommended that more specific properties be used in describing an entity, it may be desirable, for economic or other reasons, to describe two or more specific properties together. Second, general description may be used to describe one or more characteristics that are not otherwise accommodated in RiC-O. Third, it may be used to provide a succinct summary or abstract description in addition to more detailed specific description.
Corresponds to RiC-A43 (General Description attribute)
Hubble Space Telescope had until 2002 a flawed mirror that introduced severe spherical aberration for the images.
Does not include references to the workflow that the Mechanism is involved in, which is described under the Activity entity. It emphasizes those features that provide a better understanding of the impact of the Mechanism on the records.
Describes any relevant physical or software feature of any device involved in the creation or management of a Record Resource.
Corresponds to RiC-A41 (Technical Characteristics attribute)
Mechanism is a kind of Agent. A mechanism may have both mechanical and software components or may be exclusively software. A mechanism acts in the world producing physical or social effects and may generate or modify records. A mechanism performs activities based on rules determined by the agent that designed and created it. A mechanism has an essential, derivative relation with the designing and creating agent.
A process or system created by a Person or Group that performs an Activity.
Corresponds to RiC-E13 (Mechanism entity)
Use only if you don't use Title class for handling titles.
An identifying name of a Record Resource, Instantiation or Rule.
Specialization of RiC-A28 (Name attribute)
Provided for usability reasons. May be deprecated and removed later on. Use only if you don't use Type subclasses for handling categories.
Use if you do not use the UnitOfMeasurement class for handling units of measurement along with Extent.
A definite magnitude of a quantity, defined and adopted by convention or by law, that is used as a standard for measurement of the same kind of quantity. Can be spacial units (cm, m), weight (g, kg), time (s, h), storage (MB, TB) or more informal units used in the archival context like number of boxes, pages or words.
Date at which an Appellation was first used.
A concept of any kind that is used for designating an Entity and referring to it.
Connects an Activity to an Agent Temporal Relation (when the Activity is transferred from an Agent to another one) or a Mandate Relation (the Mandate assigns the Activity to the Agent or defines it).
Activity is a kind of Event. Activity is specifically used to designate purposeful human activity. Activity may be understood from two perspectives. First it can be understood as leading to an end. The end is the purpose of the Activity, or why the Activity is performed. Second, it can be understood in terms of the processes that lead to achieving the end, how the end is realized through coordinated actions. Purpose and process are complementary understandings of Activity. Together the two perspectives address why the Activity is performed, the expected ends or outcomes; and how the Activity fulfills the purpose. While activity has an intended end, it also has unintended consequences and results, or side-effects. By and large, these may not be the focus of the description, but they are, unquestionably, context. |In a corporate or government context an Activity may also be called a 'function'. An Activity exists in a specific social and cultural context, and within that context is subject to change over time. An Activity may be composed of other Activities.
The doing of something for some human purpose.
Corresponds to RiC-E15 (Activity entity)
There may be zero to many intermediate agents, ignored or unknown, between the two connected agents. Can be used when there is a transfer of function from the first agent to the second agent.
Connects at least one Agent to at least another Agent that succeeds it chronologically for, for instance, fullfilling some functions or performing some activities. The Relation is oriented chronologically, from the predecessor to the successor: the predecessor Agent(s) is the source of the Relation, and the successor Agent(s) is the target.
Class implementation of RiC-R016 and RiC-016i relations
Connects at least one Mandate and at least one Agent, when the first gives or gave the second one the authority or competencies to act. May also involve one to many Activities that the Mandate(s) assign(s) or assigned to the Agent(s). The Mandate(s) is the source of the Relation and the Agent(s) is the target.
Class implementation of RiC-R067 and RiC-R067i relations
Connects a Thing (that is a secondary, contextual entity during the existence of the Relation) to a n-ary Relation.
Connects an Agent Temporal Relation or Mandate Relation, to an Activity that is, either transferred from an Agent to another one, or assigned by a Mandate to an Agent.
Connects an Event to a Thing on which the Event has or had some significant impact.
RiC-R059 ('affects or affected' relation)
Connects an Event to a Thing that is or was actively or passively involved in it.
RiC-R058 ('has or had participant' relation)
Inverse of 'affects or affected' object property.
RiC-R059i ('is or was affected by' relation)
Inverse of 'is or was location of agent' object property.
Inverse of 'is or was location of' object property.
RiC-R075i ('has or had location' relation)
Inverse of 'is place associated with agent' object property.
Connects a Place to an Agent that is or was located in this Place.
Mandate is a kind of Rule. A mandate confers the responsibility or authority of an agent to perform a specified activity. In addition to assigning an activity and delegating responsibility or authority to perform the activity to an agent, a mandate commonly limits the place (jurisdiction) and date (time period) within which an agent may perform the activity (where and when). Mandates exist in a specific social and cultural context, and within that context are subject to change over time. While a mandate may be tacit, in whole or part, it may be explicitly expressed in a variety of documentary sources (for example, constitutions, legislation, (legal) acts, statutes, legal codes, ordinances, charges, charters, or mission statements). The evidence for identifying a mandate may be found in its entirety in one documentary source (for example, a law or regulation), or may be found in two or more sources. A mandate should not be confused with the one or more documentary sources that serve as evidence of its identity. A documentary source is a record.
Delegation of responsibility or authority by an Agent to another Agent to perform an Activity.
Inverse of 'is rule associated with' object property.
RiC-R062i ('is associated with rule' relation)
Connects a Mandate to the Agent that the Mandate gives the authority or competencies to act.
Connects a Thing (that is the target of a Relation) to a n-ary Relation.
This property 'rolifies' the MandateRelation class. It should be used only when you have to manage instances of the MandateRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a MandateRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
Connects an n-ary Relation to a Thing that is its source.
Use only if it is not possible to specify a narrower Rule relation, for example, regulates or regulated.
Connects a Rule to a Thing that is associated with the Rule.
RiC-R062 ('is rule associated with' relation)
Connects a Thing (that is the source of a Relation) to a Relation.
Connects an n-ary Relation to a Thing that is its target.
Connects a Mandate Relation to an Agent that assigns the Mandate.
The secondary entity may be, for instance, a Position or a Role Type.
Connects an n-ary Relation to a Thing that is a secondary, contextual entity during the existence of the Relation.
Connects an Agent that assigns the Mandate, to a Mandate Relation.
is authorizing agent in mandate relation
Connects a Place to a Place that it contained in the past.
Use for connecting two geographical or administrative regions.
Connects a Place to a region that is or was within it.
RiC-R007 ('contains or contained' relation)
Connects a Thing to a Thing that was a constitutive or component part of that Thing in the past.
Connects a Place to a Place within which it was contained.
Connects a Creation Relation to the Role Type that the creator Agent(s) has in the creation process
Covers the definition of "author" in diplomatics, and any agent that makes a contribution to the intellectual content of a record resource. Can also be used for any agent that was involved in the genesis (e.g. with the role of witness, representative of the author etc.) or in the production (e.g. with the role of scribe, secretary, notary, printer etc.) of the record resource or instantiation.
Connects at least one Record Resource or Instantiation to at least one Agent, when the Agent is either responsible for all or some of the content of the Record Resource, or is a contributor to the genesis or production of the Instantiation. The Record Resource or Instantiation is the source of the Relation, and the Agent(s) is the target.
Class implementation of RiC-R027 and RiC-R027i relations
The role an Agent plays in some context (usually in some creation relation). Not to be confused with a Position (position of an agent in some group). For example, a Person who is the head of some Corporate Body may play the role of annotator (of a record) in a creation relation.
Connects a Role Type to a Creation Relation (this Role Type being the specific role played by the creating Person in the context of this Relation).
Can be used, among other situations, for specifying that some finding aid (a Record that has Documentary Form Type Finding Aid) describes some Record Set.
Connects a Record Resource to a Thing that it describes or described.
RiC-R021 ('describes or described' relation)
The subject of a Record Set may be affected if the Record Set loses some of the Records.
Connects a Record Resource to a Thing that is or was its subject.
RiC-R019 ('has or had subject' relation)
Inverse of 'describes or described' object property.
RiC-R021i ('is or was described by' relation)
Connects a Place to another Place that it directly contains.
Connects a Place to a Place that it contains, directly or indirectly. This is a transitive relation.
To be used only when the current partitive relation is direct, without any intermediate node between the related things.
Connects a Thing to a Thing that is a direct constitutive or component part of that Thing.
Connects a Place to a Place that directly contains it.
Connects a Thing to a Thing that it follows directly in some non chronological sequence.
Connects a Thing to a Thing that it directly or indirectly follows in some non chronological sequence.
Connects a Thing to a Thing that it precedes directly in some non chronological sequence.
Connects a Record Set to a Record or Record Set which it includes directly.
Record is a kind of Record Resource. A Record may itself contain one or more Records, or may consist of one or more Record Parts. A Record must have or have had at least one Instantiation. A Record may have more than one Instantiation. An Instantiation derived from another Instantiation of a Record may be considered the instantiation of the same Record or an instantiation of a new Record, depending on the context. A Record may serve a variety of purposes, though it always documents or is evidence of Activity.
Discrete information content formed and inscribed, at least once, by any method on any carrier in any persistent, recoverable form by an Agent in the course of life or work activity.
Connects a Record Set to a Record or Record Set which it includes directly or indirectly. This is a transitive relation.
Connects a Record to a Record or Record Set in which it is directly included.
Connects a Thing to a Thing that follows it directly or indirectly in some non chronological sequence. This is a transitive relation.
Inverse of 'has organic or functional provenance' object property.
Connects an Event to a Thing that results or resulted from the Event.
RiC-R061 ('results or resulted in' relation)
To be used to describe the functional provenance of a Record Resource or Instantiation.
Connects a Record Resource or an Instantiation to the Activity that generates the Record Resource or Instantiation.
This property 'rolifies' the ActivityDocumentationRelation class. It should be used only when you have to manage instances of the ActivityDocumentationRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a ActivityDocumentationRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Activity Documentation Relation
Connects a Record Resource or an Instantiation to an Agent that creates or accumulates it, receives it, or sends it, or to an Activity that generates it.
Inverse of 'results or resulted in' object property.
RiC-R061i ('results or resulted from' relation)
Connects a Record Resource to a Relation, when the first is used for proving the existence of the second one, or for describing it.
Inverse of 'is evidenced by' object property.
Connects a Relation to a Record Resource that is used for proving is existence or describing it.
Object property implementation of RiC-RA05 (Source of Relation attribute).
Connects a Position to a Group in which that Position exists or existed, or that is defined by that Group's organizational structure.
RiC-R056 ('exists or existed in' relation)
Position is a kind of Agent. Position is the intersection of a Person and a Group. Position exists independently of the Person that holds the Position within a Group. More than one Person may hold a Position. Position is commonly defined in a Mandate, often called a position description or job description. The Mandate may specify the work to be performed (Activity) as well as the competencies for performing the Activity. A Position is often given a Name. A Position may be tied to a project or to a set of tasks and thus have a defined duration. A Position may change over time, as the Group that establishes it changes over time. Position is not to be confused with Occupation or Activity. Within the records created by a Corporate Body, a Position may be used to identify the record sets resulting from activities performed by one or more persons holding the Position over time, without necessarily identifying or describing the Person or persons, or identifying which records were created by each Person.
The functional role of a Person within a Group.
Corresponds to RiC-E12 (Position entity)
Group is a kind of Agent. A Group has a socially recognized identity. Each member of the Group plays a particular role or roles (that is has a particular Position) in the coordinated activity of the Group. Corporate bodies and families are kinds of groups, though other kinds of groups are possible. For example, the “electorate” -- all of the voters in a given election. Complex, large groups may be subdivided into other groups.
Two or more Agents that act together as an Agent.
Inverse of 'exists or existed in' object property.
RiC-R056i ('has or had position' relation)
This property 'rolifies' the PositionToGroupRelation class. It should be used only when you have to manage instances of the PositionToGroupRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a PositionToGroupRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Position to Group Relation
Inverse of 'is or was expressed by' object property.
RiC-R064i ('expresses or expressed' relation)
Connects a Rule to a Record Resource that expresses or expressed the Rule.
RiC-R064 ('is or was expressed by' relation)
Connects a Thing to a Thing that it followed in some non chronological sequence in the past.
Inverse of 'precedesOrPreceded' object property.
RiC-R008i ('follows or followed' relation)
Connects a Thing to a Thing that followed it in some non chronological sequence in the past.
Connects an Instantiation to another Instantiation that was its component in the past.
Connects an Instantiation to one of its present or past component instantiations.
RiC-R004 ('has or had component' relation)
Connects an Instantiation to another Instantiation of which it was a component in the past.
Connects a Record or Record Part to another Record or Record Part that was its constituent in the past.
Record Part is a kind of Record Resource. A Record Part may itself have Record Parts.
Component of a Record with independent information content that contributes to the intellectual completeness of the Record.
Corresponds to RiC-E05 (Record Part entity)
Connects a Record or Record Part to a Record or Record part that is or was a constituent of that Record or Record Part.
RiC-R003 ('has or had constituent' relation)
Connects a Record or Record Part to another Record or Record Part of which it was a constituent in the past.
Connects a Group to one of its past subdivisions.
Connects an Agent to an Agent that was hierarchically inferior in the past.
Connects a Group to one of its present or past subdivisions.
RiC-R005 ('has or had subdivision' relation)
Connects a subdivision to the Group it was a part of in the past.
Connects a past Event to one of a series of past Events that constituted that original, broader, past Event.
Since an Activity is a kind of Event, this Relation can also be used for Activity.
Connects an Event to one of a series of Events that constitute the original, broader, past or ongoing Event.
RiC-R006 ('has or had subevent' relation)
Connects a past Event to the broader Event of which it was a part.
Connects an Activity to an Activity Type that categorizes it.
Can be extended with any number of subclasses, e.g. “function/action” and “activity domain”. This allows for a faceted approach that enables an Activity to be categorized using a combination of components, general or more specific. For example, “monitoring” can be used in combination with “election polls” or “water resources”.
Corresponds to RiC-A02 (Activity Type attribute)
Connects a Thing to a Type that categorizes or categorized it.
Connects an Activity Type to an Activity that it categorizes.
The identity of the addressee is (usually) evidenced by the Record Resource or Instantiation itself.
Connects a Record Resource or an Instantiation to the Agent that it is addressed to.
This is the most general organic provenance relation. Use it to connect a Record Resource or Instantiation with an Agent only if it is not possible to use a narrower, more specific relation, for example has creator.
Connects a Record Resource or an Instantiation to an Agent that creates or accumulates the Record Resource, receives it, or sends it.
Inverse of 'has addressee' object property.
To be used for a Person, Group or Position that makes any contribution to the content of a record. Includes the Person, Group or Position in whose name or by whose command the content may have been formulated and first instantiated (for example the Person who signed the Record).
Connects a Record to the Group, Person or Position that is responsible for conceiving and formulating the information contained in the Record.
Covers the definition of author in diplomatics, and any contribution to the intellectual content of a Record Resource.
Connects a Record Resource or an Instantiation to an Agent that is either responsible for all or some of the content of the Record Resource or is a contributor to the genesis or production of an Instantiation.
Inverse of 'has author' object property.
This property 'rolifies' the AuthorshipRelation class. It should be used only when you have to manage instances of the AuthorshipRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a AuthorshipRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
Inverse of 'is birth date of' object property
Inverse of 'is beginning date of' object property
RiC-R069i ('has beginning date' relation)
Connects a Date to a Person that was born on that Date.
Inverse of 'is birth place of' object property
Connects a Place to a Person who was born in that Place.
Connects an Instantiation to a Carrier Type which categorizes its carrier.
In order to manage an instantiation of a record resource, it is necessary to note the type of carrier on which the record resource is instantiated as its nature will determine the environmental storage conditions and the prerequisites for and possible ways of accessing and using the record resource.
Categorization of physical material on which information is represented.
Corresponds to RiC-A05 (Carrier Type attribute)
Connects a Carrier Type to an Instantiation whose carrier it categorizes.
Connects a Person to one of their children.
There may be zero to many intermediate persons, ignored or unknown, between the two connected persons.
Connects a Person to one of their descendants. This is a transitive relation.
This property 'rolifies' the ChildRelation class. It should be used only when you have to manage instances of the ChildRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a ChildRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
Connects a Record Resource or an Instantiation to the Agent that collects it intentionally, i.e., the Agent is a collector.
Connects a Record Resource or an Instantiation to the Agent that accumulates it, be it intentionally (collecting) or not (receiving in the course of its activities).
Inverse of 'has collector' object property.
Connects a Record or a Record Part to a Content Type which categorizes its content.
Content Type should not be confused with Representation Type or Carrier Type that would concern a related Instantiation since the form of communication can be independent of the representation or carrier, for example a map (content type "cartographic image") may be represented as a sketch (representation type "visual") recorded as a physical document (carrier type "paper"). It also should not be confused with the Documentary Form Type of a Record, or Record Part, which describes a specific document form (for example a deed of sale).
The fundamental form of communication in which a Record or Record Part is expressed.
Corresponds to RiC-A10 (Content Type attribute)
Connects a Content Type to a Record or Record Part whose content it categorizes.
Is both a temporal and genetic relation between the two Record Resources.
Connects a Record Resource to a copy of that Record Resource.
Use to connect two Record Resources only if it is not possible to use a narrower, more specific, asymmetric Record Resource to Record Resource relation, for example is original of.
Connects two Record Resources when there is a genetic link between them. Genetic in this sense is as defined by diplomatics, i.e. the process by which a Record Resource is developed. This relation is symmetric.
RiC-R023 ('has genetic link to record resource' relation)
There may actually be zero to many intermediate Entities, ignored or unknown, in the chronological sequence between the two connected Entities.
Connects a Thing to a Thing that follows it in chronological order. This is a transitive relation.
Inverse of 'is creation date of' object property
RiC-R080i ('has creation date' relation)
When used for a Record Set (e.g. a file), it is the creation date of the Record Set itself rather than the creation date of the members of the Record Set. To record the creation date of members of the Record Set, use 'is or was creation date of all members of', 'is or was creation date of most members of’ or 'is or was creation date of some members of’.
Connects a Date to a Record Resource or Instantiation that was created at this Date.
RiC-R080 ('is creation date of' relation)
May be used to categorize a Date as a single date, a date range or a date set or sub-categories of these broad types. This attribute should not be confused with the date relations defined to connect a Date entity and any other entity (such as RiC-R069 ‘is beginning date of’).
Corresponds to RiC-A42 (Date Type attribute) (new in RiC-CM 1.0).
Connects a Date Type to a Date that it categorizes.
Inverse of 'is death date of' object property
Inverse of 'is end date of' object property.
Connects a Date to a Person who died on that Date.
Inverse of 'is death place of' object property
Connects a Place to a Person who died in that Place.
Inverse of 'is destruction date of' object property.
Connects a Date to a Thing that was destructed at that Date.
Connects an Instantiation to another Instantiation that is its direct component.
Connects an Instantiation to another Instantiation that is, directly or indirectly, a component of that Instantiation. This is a transitive relation.
Connects an Instantiation to another Instantiation of which it is a direct component.
Connects a Record to another Record or Record Part that is its direct constituent.
Connects a Record or Record Part to another Record or Record Part that is its constituent, directly or indirectly. This is a transitive relation.
Connects a Record or Record Part to another Record or Record Part of which it is a direct constituent.
Connects a Group to one of its direct subdivisions.
Connects an Agent to an Agent that is its direct subordinate.
Connects a Group to another Group that is one of its direct or indirect subdivisions. This is a transitive relation.
Connects a Group to the Group it is a direct subdivision of.
Connects an ongoing Event to one of a series of Events that directly constitute that broader, ongoing Event.
Connects an ongoing Event to one of a series of Events that directly or indirectly constitute that broader, ongoing Event. This is a transitive relation.
Connects an ongoing Event to the Event it is a direct part of.
Connects a Record or Record Part to its Documentary Form Type.
Documentary Form Type plays an important role in determining the type of information a Record may comprise, its status of perfection, and its authenticity and reliability. Documentary form types exist in a specific social and cultural context, and within that context, are subject to change over time.
Categorization of a Record or Record Part with respect to its extrinsic and intrinsic elements that together communicate its content, administrative and documentary context, and authority.
Corresponds to RiC-A17 (Documentary Form Type attribute)
Connects a Documentary Form Type to a Record or Record Part that it categorizes.
Inverse of 'is draft of' object property.
Inverse of 'precedes in time' object property. This is a transitive relation.
There may be zero to many intermediate records, ignored or unknown, between the two connected Records.
Connects a draft to the final version of a Record.
Connects an Event to an Event Type which categorizes it.
Events of all kinds can be categorized. Curation event types include creation; acquisition; transfer; arrangement; description; digitization, etc. Biographical event types include birth, marriage, death, etc.
Corresponds to RiC-A18 (Event Type attribute)
Connects an Event Type to an Event that it categorizes.
Connects a Record Resource or Instantiation to an Extent
The most generic relation, is related to, connects any Thing to any other Thing. This relation is symmetric.
Connects an Extent to an Extent Type that categorizes what is being measured.
Categorization of the extent that is being measured.
Connects an Extent Type to an Extent that it categorizes.
Connects a Family to a Family Type that categorizes it.
Family is a kind of Group. “Family” is used here as a general term that encompasses a wide variety of familial groups. Other types of familial groups include Dynasty, Clan, House, Tribe and others. Though family may be a recognized legal group in specific contexts, the term may also be used for groups that are socially recognized as families. A family may be a group of persons related either by consanguinity or affinity or cohabitation or other social conventions. In some context, a Family may be legally recognized as Corporate Body. For example, certain North American peoples (tribes) retain self-government rights and have jurisdiction over defined tribal lands.
Two or more persons related by birth, or through marriage, adoption, civil union, or other social conventions that bind them together as a socially recognized familial group.
Encompasses a wide variety of familial groups related by consanguinity, affinity, cohabitation, or other social conventions.
Corresponds to RiC-A20 (Family Type attribute)
Connects a Family Type to a Family that it categorizes.
Connects an Identifier and an Identifier Type that categorizes it.
Can include Global Persistent Identifiers (globally unique and persistently resolvable identifier for the entity) and/or Local Identifiers. Both the domain within which the identifier is unique, and the rules used in forming the identifier value should be provided with the identifier value.
A word, number, letter, symbol, or any combination of these used to uniquely identify or reference an individual instance of an entity within a specific information domain.
Class implementation of RiC-A22 (Identifier attribute) (see also the identifier datatype property)
For example, 'old identifier' ; 'ISNI' (for a person or corporate body), etc.
Connects an Identifier Type and an Identifier that it categorizes.
Connects an Agent and (one of) its present or past Agent Name.
A label, title or term designating an Agent in order to make it distinguishable from other similar entities.
Class implementation of a specialization of RiC-A28 (Name attribute)
Connects a Thing to one of its past or present Names.
Connects an Agent Name to an Agent it designates or designated.
Connects a Record Set and a Content Type that categorizes all the Records or Record Parts that are or were included in the Record Set.
has or had all members with content type
Connects a Record Set and a Category (Type) to which all the Records or Record Parts that are or were included in the Record Set belong.
Connects a Content Type and a Record Set whose all past or present Record or Record Part members have that Content Type.
is or was content type of all members of
Inverse of 'is or was creation date of all members of' object property
has or had all members with creation date
RiC-R081i ('has or had all members with creation date' relation)
Connects a Date to a Record Set all of whose present or past members were created at this Date.
is or was creation date of all members of
RiC-R081 ('is or was creation date of all members of' relation)
Connects a Record Set and a Documentary Form Type that categorizes all the Records or Record Parts that are or were included in the Record Set.
has or had all members with documentary form type
Connects a Documentary Form Type and a Record Set whose all past or present Record or Record Part members have that Documentary Form Type.
is or was documentary form type of all members of
Connects a Record Set and a Language used by all the Records or Record Parts that are or were included in the Record Set.
A spoken or written human language represented in a Record Resource or used by an Agent.
Corresponds to RiC-A25 (Language attribute)
Connects a Language and a Record Set whose all present or past Record or Record Part members use that Language.
Connects a Record Set and a Legal Status that categorizes all the Records or Record Parts that are or were included in the Record Set.
has or had all members with legal status
Corresponds to RiC-A26 (Legal Status attribute)
Connects a Legal Status and a Record Set whose all past or present Record or Record Part members have that Legal Status.
is or was legal status of all members of
Connects a Record Set and a Record State that categorizes all the Records or Record Parts that are or were included in the Record Set.
has or had all members with record state
Can refer both to a record's stage of creation (for example "draft") and its form of transmission when the record was received (for example "copy").
Description of the production or reproduction status of a Record or Record Part.
Corresponds to RiC-A39 (State attribute)
Connects a Record State and a Record Set whose all past or present Record or Record Part members have that Record State.
is or was record state of all members of
In some situations, it may be useful or necessary to connect a record resource to an analogue instantiation that no longer exists or has been lost.
Connects a record resource to one of its analogue instantiations, whether it exists or has been lost or destroyed.
In some situations, it may be useful or necessary to connect a record resource to an instantiation that no longer exists or or has been lost, when some of its characteristics are known from some source, like an old finding aid.
Connects a Record Resource to an Instantiation, which either may exist or may have been lost or destroyed.
RiC-R025 ('has or had instantiation' relation)
Inverse of 'has or had analogue instantiation' object property.
Connects a Physical Location to its past or present coordinates in a reference system.
Used to describe basic human-readable text such as an address, a cadastral reference, or less precise information found in a record. Use the coordinates datatype property, or the Coordinates class to capture the geographical coordinates of the Place. Use spatial relations (particularly 'has or had location') to capture a relation between two places.
A delimitation of the physical territory of a Place.
Class implementation of RiC-A27 (Location attribute)
Connects an instance of Coordinates to a Physical Location it locates or located on earth, according to some reference system.
Connects a Corporate Body to a Corporate Body Type which categorizes or categorized it.
Corporate body is a kind of Group (RiC-E09). By exception, within some legal contexts, a sole trader or sole proprietor may be recognized as a corporate body, even when the economic enterprise does not have additional members. Corporate bodies often have a mandate giving them the authority to act within their area(s) of competence. They will also usually act within a particular jurisdiction being governed by legal and other rule-based frameworks. A corporate body though may be constituted in a more informal manner and exist as an entity by virtue of its recognition as such by its members.
An organized group of persons that act together as an Agent, and that has a recognized legal or social status.
Corresponds to RiC-E11 (Corporate Body entity)
Corresponds to RiC-A12 (Corporate Body Type attribute)
Connects a Corporate Body Type to a Corporate Body that it categorizes or categorized.
This property can be used, among other cases, when you want to convert findings aids encoded in EAD/XML and need a simple and accurate migration path to process dao or daogrp EAD elements. Also, in some situations, it may be useful or necessary to connect a record resource to a digital instantiation that no longer exists or or has been lost.
Connects a record resource to one of its digital instantiations, whether it exists or has been lost or destroyed.
Inverse of 'has or had digital instantiation' object property.
Inverse of 'is or was employer of' object property.
Inverse of 'is or was controller of' object property.
RiC-R041i ('has or had controller' relation)
Connects a Corporate Body or a Person to a Person who is or was their employee.
Inverse of 'is or was holder of' object property.
RiC-R039i ('has or had holder' relation)
Inverse of 'is or was manager of' object property.
RiC-R038i ('is or was managed by' relation)
Connects an Agent to a Record Resource or Instantiation that the Agent holds or held.
RiC-R039 ('is or was holder of' relation)
This property 'rolifies' the RecordResourceHoldingRelation class. It should be used only when you have to manage instances of the RecordResourceHoldingRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a RecordResourceHoldingRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Record Resource Holding Relation
Connects a Thing to one of its past or present Identifiers.
Connects a Thing to an Appellation that is or was used for designating it.
Connects an Identifier to a Thing that it identified or identifies.
Inverse of 'is or was holder of intellectual property rights of' object property.
has or had intellectual property rights holder
RiC-R040i ('has or had intellectual property rights holder ' relation)
Inverse of 'has or had authority over' object property.
RiC-R036i ('is or was under authority of' relation)
Connects an Agent to a Record Resource or Instantiation on which the Agent has or had some intellectual property rights.
is or was holder of intellectual property rights of
RiC-R040 ('is or was holder of intellectual property rights of' relation)
This property 'rolifies' the IntellectualPropertyRightsRelation class. It should be used only when you have to manage instances of the IntellectualPropertyRightsRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a IntellectualPropertyRightsRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Intellectual Property Rights Relation
Inverse of 'is or was jurisdiction of' object property.
RiC-R076i ('has or had jurisdiction' relation)
Connects a Place to an Agent that has or had jurisdiction over the Place.
RiC-R076 ('is or was jurisdiction of' relation)
Connects an Agent, Record or Record Part to a Language that uses or used it.
Connects a Language to an Agent, Record or Record Part that uses or used it.
Inverse of 'is or was leader of' object property.
RiC-R042i ('has or had leader' relation)
Connects a Person to the Group that Person leads or led in the past.
RiC-R042 ('is or was leader of' relation)
This property 'rolifies' the LeadershipRelation class. It should be used only when you have to manage instances of the LeadershipRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a LeadershipRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
Connects an Agent or Record Resource to a Legal Status which categorized or categorizes it.
Connects a Legal Status to an Agent, Record or Record Part that it categorized or categorizes.
Connects a Legal Status to an Agent or Record Resource that it categorizes.
Use for specifying, for example, that a Record Set of type personal file has main subject some person, which would help end users to retrieve the main archival resources about this person.
Connects a Record Resource to a Thing that is or was its main subject.
RiC-R020 ('has or had main subject' relation)
Inverse of 'has or had main subject' object property.
RiC-R020i ('is or was main subject of' relation)
Connects a Mandate to a Mandate Type that categorized or categorizes it.
For example : charter, treaty, contract, letter of appointment, papal mandate, episcopal mandate, ciurt mandate, election mandate, popular mandate, federal mandate, etc.
Corresponds to RiC-A44 (Mandate Type attribute).
Connects a Rule to a Rule Type that categorized or categorizes it.
Connects a Mandate Type to a Mandate that it categorized or categorizes.
Connects a Group to a Person that is or was a member of that Group.
Inverse of 'has or had member' object property.
RiC-R055i ('is or was member of' relation)
This property 'rolifies' the MembershipRelation class. It should be used only when you have to manage instances of the MembershipRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a MembershipRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
Inverse of 'is or was creation date of most members of' object property
has or had most members with creation date
RiC-R083i ('has or had most members with creation date' relation)
Inverse of 'is or was creation date of some members of' object property
has or had some members with creation date
RiC-R082i ('has or had some members with creation date' relation)
To be used for specifying a bulk date, i.e. the predominant date of the members of the record set.
Connects a Date to a Record Set most of whose present or past members were created at this Date.
is or was creation date of most members of
RiC-R083 ('is or was creation date of most members of' relation)
Connects a Person to an Occupation Type that categorized or categorizes his/her occupation (profession, trade or craft).
The pursuit of an occupation involves the performance of an Activity. Successful performance of the Activity is based on the ability to perform related competencies successfully. Such competencies may be acquired through education or experience, or a combination of both. The authority of the Person to pursue the occupation may be derived tacitly or explicitly from an external Agent, based on a demonstrated mastery of the competency. An occupation may be pursued independently by a Person or a Group, thereby contributing to the fulfilment of the function (activity) of the group. Should not be confused with Position where, for example, an agent with the occupation type "lawyer" holds the position of "legal counsel" in an agency. Related to but should not be confused with the domain or field of activity, such as an archivist who works in the domain of archival science.
Categorization of a profession, trade, or craft pursued by a Person in fulfilment of an Activity.
Corresponds to RiC-A30 (Occupation Type attribute)
Connects a Person or a Group to a Demographic Group to which it belongs or belonged.
Connects an Occupation Type to a Person whose occupation is or was categorized by it.
Inverse of 'is or was owner of' object property.
Connects a Group, Person or Position to a Thing that this Agent owns or owned.
RiC-R037 ('is or was owner of' relation)
This property 'rolifies' the OwnershipRelation class. It should be used only when you have to manage instances of the OwnershipRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a OwnershipRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
Connects a Place to one of its past or present Physical Location.
Connects a Physical Location to a Place, when it is or was its location.
Connects a Place to one of its past or present names.
A label, title or term designating a Place in order to make it distinguishable from other similar entities.
Connects a Place Name to a Place that was or is designated by it.
Connects a Place to a Place Type that categorized or categorizes it.
Broadly, a Place may be a member of three broad categories: jurisdiction, manmade structure, or a natural feature. Each of these three categories can subdivided into narrower categories.
Corresponds to RiC-A32 (Place Type attribute)
Connects a Place Type to a Place that is or was categorized by it.
Connects a Record Set and a Content Type that categorizes some of the Records or Record Parts that are or were included in the Record Set.
has or had some members with content type
Connects a Record Set and a Category (Type) to which some of the Records or Record Parts that are or were included in the Record Set belong.
Connects a Content Type and a Record Set whose some past or present Record or Record Part members have that Content Type.
is or was content type of some members of
Connects a Record Set and a Documentary Form Type that categorizes some of the Records or Record Parts that are or were included in the Record Set.
has or had some members with documentary form type
Connects a Documentary Form Type and a Record Set whose some past or present Record or Record Part members have that Documentary Form Type.
is or was documentary form type of some members of
Connects a Record Set and a Language used by some of the Records or Record Parts that are or were included in the Record Set.
Connects a Language and a Record Set whose some present or past Record or Record Part members use that Language.
Connects a Record Set and a Legal Status that categorizes some of the Records or Record Parts that are or were included in the Record Set.
has or had some members with legal status
Connects a Legal Status and a Record Set whose some past or present Record or Record Part members have that Legal Status.
is or was legal status of some members of
Connects a Record Set and a Record State that categorizes some of the Records or Record Parts that are or were included in the Record Set.
has or had some members with record state
Connects a Record State and a Record Set whose some past or present Record or Record Part members have that Record State.
is or was record state of some members of
Inverse of 'has or had teacher' object property.
RiC-R053i ('has or had student' relation)
Connects a Person to another Person who is or was their teacher.
RiC-R053 ('has or had teacher' relation)
This property 'rolifies' the TeachingRelation class. It should be used only when you have to manage instances of the TeachingRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a TeachingRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
Connects a Record Resource, Instantiation or Rule to a title that is or was used for designating it.
A name that is used for a Record Resource or a Rule
Connects a Title to a Record Resource, Instantiation or Rule that it designated or designates.
Inverse of 'is original of' object property.
Connects the original version of a Record to a copy or a later version.
Connects an Instantiation to a Production Technique Type that categorizes its production technique.
Class implementation of RiC-A33 (Production Technique attribute)
Connects a Production Technique Type to an Instantiation whose production technique is categorized by it.
Inverse of 'is publication date of' object property
Connects a Date to a Record Resource that was made public at this Date.
Connects a Record resource to an Agent who published it.
Connects an Agent to a Record Resource that it published.
Connects a Record Resource or an Instantiation to the Agent that receives it in the course of the Agent's activities.
Inverse of 'received by' object property.
Connects a Record Set to a Record Set Type that categorizes it.
Four instances of Record Set Type are included for now in RiC-O; they also are instances of skos:Concept and, as such, part of a SKOS vocabulary. Record Set Type may also be used (or extended) to categorize types of Record Set that have not traditionally been considered archival, e.g. search result list.
A broad categorization of the type of Record Set.
Corresponds to RiC-A36 (Record Set Type attribute)
Connects a Record Set Type to a Record Set that it categorizes.
Connects a Record or Record Part to a Record State that categorizes its state.
Connects a Record State to a Record or Record Part whose state it categorizes.
Connects a Record Resource to a reply, usually in the form of correspondence.
Use to connect two Record Resources only if it is not possible to use a narrower, more specific relation, for example has genetic link to.
Connects two Record Resources. This relation is symmetric.
is record resource associated with record resource
RiC-R022 ('is record resource associated with record resource' relation)
Connects an Instantiation to a Representation Type that categorizes its representation type.
Can be unmediated (which allows humans to receive the message communicated without an intermediation of a device) and mediated (which needs a device to decode the message). A lot of contemporary mediated types are digital. Each representation type may present specific features: bit rate for audio, resolution for digital images, encoding format for video etc. Depending on the type, specific attributes may be added to describe their characteristics.
Method of recording the content type of an Instantiation
Corresponds to RiC-A37 (Representation Type attribute)
Connects a Representation Type to an Instantiation that it categorizes.
The identity of the sender is (usually) evidenced by the Record Resource or Instantiation itself.
Connects a Record Resource or an Instantiation to the Agent that sends it
Inverse of 'has sender' object property.
Connects an Extent to a Unit Of Measurement
Inverse of 'has unit of measurement' object property
Use to connect a Thing to another Thing that is or was a part of the whole Thing only if it is not possible to use a narrower, more specific whole/part relation, for example has or had constituent. The end of existence of a whole/part relation may affect the integrity or nature of the domain entity.
Connects a Thing to a constitutive or component part of that Thing.
Connects a Date to a Date in which it is contained.
Connects a Record Set to a Record or Record Set which it included in the past.
A Record or Record Set can be aggregated in one or many Record Sets simultaneously or through time.
Connects a Record Set to a Record or Record Set it aggregates, or aggregated in the past.
RiC-R024 ('includes or included' relation)
Connects a Record to a Record or Record Set in which it was included in the past.
Connects a Type (a category) to a Thing that it categorizes or categorized.
Inverse of 'has organic provenance' object property.
Inverse of 'has creator' object property.
Connects a Date to a Thing that came into existence on that Date.
RiC-R069 ('is beginning date of' relation)
Connects a Place to an Agent which is related to that Place.
Inverse of 'has descendant' object property. This is a transitive relation.
Inverse of 'has accumulator' object property.
RiC-R028i ('is accumulator of' relation)
Connects a Date to an Event that occurred at this Date. An event or activity can be recurrent, which implies that one single event can be related to several dates.
RiC-R084 ('is date of occurrence of' relation)
Inverse of 'is event associated with' object property.
RiC-R057i ('is associated with event' relation)
Inverse of 'is date of occurrence of' object property
Connects a Date to a Thing whose existence ended on that Date.
Connects an Instantiation to another Instantiation of which it is, directly or indirectly, a component. This is a transitive relation.
Connects a Thing to a Thing of which it is direct constitutive or component part.
Connects a Record or Record Part to another Record or Record Part of which it is a constituent, directly or indirectly. This is a transitive relation.
Connects an Agent to an Agent that is directly hierarchically superior.
Connects a Group to the Group it is a direct or indirect subdivision of. This is a transitive relation.
Connects an ongoing Event to an Event of which it is a direct or indirect part. This is a transitive relation.
Connects a Place to a Place that is, directly or indirectly, contained by it. This is a transitive relation.
Connects a Record to a Record or Record Set in which it is directly or indirectly included. This is a transitive relation.
Connects a Date to an Appellation, when it is the date at which the Appellation was first used.
Connects an Appellation to the Date from which it was used.
Connects a Date and a Thing that was last modified at this Date.
Connects a Date to a Thing that was modified on that Date.
RiC-R073 ('is modification date of' relation)
Connects a Thing to the Date when it was last modified.
Inverse of 'has or had participant' object property.
RiC-R058i ('is or was participant in' relation)
Connects a Name to a Thing that it designated or designates.
Inverse of 'has or had instantiation' object property.
RiC-R025i ('is or was instantiation of' relation)
Connects a Category (Type) and a Record Set whose all present or past Record or Record Part members belong to that Category.
Connects a Category (Type) and a Record Set whose some present or past Record or Record Part members belong to that Category.
Connects a Date to a Record Set some of whose present or past members were created at this Date.
is or was creation date of some members of
RiC-R082 ('is or was creation date of some members of' relation)
Inverse of 'has or had subject' object property.
RIc-R019i ('is or was subject of' relation)
Connects an Agent to another Agent it controls or controlled.
RiC-R041 ('is or was controller of' relation)
Connects a Rule to an Agent that enforces or enforced the Rule.
RiC-R066 ('is or was enforced by' relation)
Inverse of 'is or was enforced by' object property.
RiC-R066i ('is or was responsible for enforcing' relation)
Connects an Agent to a Record Resource or Instantiation that the Agent managed or manages.
RiC-R038 ('is or was manager of' relation)
Use only if it is not possible to specify a narrower authority relation, for example is or was owner of.
Connects an Agent to a Thing over which the Agent has or had some kind of authority.
RiC-R036 ('has or had authority over' relation)
Connects an Appellation to a Thing that it designates or designated.
Connects a Place to a Thing that is or was located in the Place.
RiC-R075 ('is or was location of' relation)
Connects a Rule Type to a Rule that it categorized or categorizes.
Connects a Demographic Group to a Person or Group which belongs or belonged to it.
Inverse of 'occupies or occupied' object property.
RiC-R054i ('is or was occupied by' relation)
Connects a Person to a Position they occupy or occupied.
RiC-R054 ('occupies or occupied' relation)
This property 'rolifies' the PositionHoldingRelation class. It should be used only when you have to manage instances of the PositionHoldingRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a PositionHoldingRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Position Holding Relation
Connects an Activity to an Agent that performed or performs the Activity.
RiC-R060 ('is or was performed by' relation)
Inverse of 'is or was performed by' object property.
RiC-R060i ('performs or performed' relation)
This property 'rolifies' the PerformanceRelation class. It should be used only when you have to manage instances of the PerformanceRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a PerformanceRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Performance Relation
Inverse of the 'regulates or regulated' object property.
RiC-R063i ('is or was regulated by' relation)
Connects a Rule to a Thing that it regulates or regulated.
RiC-R063 ('regulates or regulated' relation)
RiC-R065i ('is responsible for issuing' relation)
Connects a Rule to the Agent that issued or published the Rule.
Connects a Date to an Appellation, when it is the date till which the Appellation was used.
Connects an Appellation to the Date till when it was used.
RiC-R002i ('is or was part of' relation)
Connects a Person to another Person they have some knowledge of through time or space.
This property 'rolifies' the KnowingOfRelation class. It should be used only when you have to manage instances of the KnowingOfRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a KnowingOfRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
Inverse of 'migrated into' object property.
Inverse of 'has or had derived instantiation' object property.
RiC-R014i ('is or was derived from instantiation' relation)
Connects an Instantiation to a version it has been migrated into.
This property 'rolifies' the MigrationRelation class. It should be used only when you have to manage instances of the MigrationRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a MigrationRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
In some situations, it may be useful or necessary to connect an instantiation to an instantiation that was derived from it but no longer exists or or has been lost.
Connects an instantiation to an instantiation that is derived from it, whether it exists or has been lost or destroyed.
RiC-R014 ('has or had derived instantiation' relation)
Use to connect an Event and an entity only if it is not possible to specify a narrower Event relation, for example has or had participant.
Connects an Event to a Thing that is associated with the existence and lifecycle of the Event.
RiC-R057 ('is event associated with' relation)
Connects a Position to a Leadership Relation (the leading Person occupies that Position).
position is context of leadership relation
Connects at least one Person and at least one Group, when the first one(s) lead(s) or led the second one(s). The Relation is oriented from the leading Person to the Group: the leading Person(s) is the source of the Relation, and the Group(s) is the target.
Class implementation of RiC-R042 and RiC-R042i relations
Connects a Leadership Relation to the Position occupied by the leading Person.
Connects a Position to a Membership Relation (the member Person occupies that Position).
position is context of membership relation
Connects a Group and at least one Person, when the first one has or had the second one(s) among its members. The Relation is oriented from the Group to its members: the Group(s) is the source of the Relation, and the Person(s) is the target.
Class implementation of RiC-R055 and RiC-R055i relations
Connects a Membership Relation to the Position occupied by the member Person(s).
The relation does not specify by itself what criteria are used for ordering the sequence. There may actually be zero to many intermediate Entities, ignored or unkown, in the sequence between the two connected Things. Can be used, for example, for specifying that some Record 'precedes' (has next) some Record within a Record Set.
Connects a Thing to a Thing that follows or followed it in some sequence.
RiC-R008 ('precedes or preceded' relation)
Connects a Proxy to the Record Resource it stands for in the specific context of a Record Set.
Useful for handling in RDF the sequencing of records or records sets in the context of a Record set. A Record Resource has only one Proxy in the context of one specific Record Set. It may have many Proxies simultaneously or through time.
A Proxy represents (stands for) a Record Resource as it exists in a specific Record Set.
ORE Proxy (http://www.openarchives.org/ore/terms/Proxy)
Connects a Proxy to the Record Set in which it stands for (represents) another Record Resource.
Inverse of 'was merged into' object property.
Inverse of 'has successor' object property.
Connects a Corporate Body to another Corporate Body that is the result of a merger of the previous one with one to many other corporate bodies.
Inverse of 'was split into' object property.
Connects a Corporate Body to one of the Corporate Bodies that results from the split of the previous one into two to many corporate bodies.
Inverse of 'has or had component' object property.
RiC-R004i ('is or was component of' relation)
Connects a Thing to a Thing of which it was a constitutive or component part in the past.
Inverse of 'has or had constituent' object property.
RiC-R003i ('is or was constituent of' relation)
Inverse of 'contains or contained' object property.
RiC-R007i ('is or was contained by' relation)
Inverse of 'includes or included' object property.
RiC-R024i ('is or was included in' relation)
Inverse of 'is modification date of' object property.
RiC-R073i ('has modification date' relation)
Connects an Agent to another Agent that succeeds it chronologically.
Inverse of 'has or had subdivision' object property.
RiC-R005i ('is or was subdivision' relation)
Connects an Agent to an Agent that was hierarchically superior in the past.
Inverse of 'has or had subevent' object property.
RiC-R006i ('is or was subevent of' relation)
Connects at least one Record Resource or Instantiation to at least one Agent, when the Record Resource or Instantiation is or was accumulated by the Agent, be it intentionally (collecting it) or not (receiving it in the course of its activities). The Record Resource(s) or Instantiation(s) is the source of the Relation, and the Agent(s) is the target.
Class implementation of RiC-R028 and RiC-R028i relations
This is the most general organic provenance relation. Use it to connect a record resource or instantiation with an agent only if it is not possible to use a narrower, more specific relation, for example Creation Relation.
Connects at least one Record Resource or an Instantiation to at least one Agent that creates or accumulates the Record Resource, receives it, or sends it. The Record Resource(s) or Instantiation(s) is the source of the Relation, and the Agent(s) is the target.
Class implementation of RiC-R026 and RiC-R026i relations
This property 'rolifies' the AccumulationRelation class. It should be used only when you have to manage instances of the AccumulationRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a AccumulationRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Accumulation Relation
Connects at least one Record Resource or Instantiation to at least one Activity, when the Record Resource or Instantiation results from the Activity. The Record Resource(s) or Instantiation(s) is the source of the Relation, and the Activity(-ies) is the target.
Class implementation of RiC-R033 and RiC-R033 relations
Use to connect an event and an entity only if it is not possible to specify a narrower event relation, for example a PerformanceRelation.
Connects at least one Event to at least one Thing, when the first is associated with the existence and lifecycle of the second one. The Event(s) is the source of the Relation, and the Thing(s) is the target.
Class implementation of RiC-R057 and RiC-R057i relations
This relation stands for organic and for functional provenance.
Connects at least one Record Resource or Instantiation to at least one Agent or Activity, when the Agent or Activity is the provenance of the Record Resource or Instantiation (i.e. when the Agent created, accumulated or maintained the Record Resource or Instantiation, or when the Activity resulted into them). The Record Resource(s) or Instantiation(s) is the source of the Relation, and the Agent(s) or Activity(-ies) is the target.
Organic or functional provenance Relation
Provides brief information about the content or other individual characteristics of the entity being described, necessary to distinguish it from other perhaps similar entities.
Class implementation of RiC-A28 (Name attribute) (see also the name datatype property)
Connects an Appellation and at least one Thing that the Appellation designates or designated. The Appellation is the source of the Relation and the Thing(s) is the target.
This property 'rolifies' the AppellationRelation class. It should be used only when you have to manage instances of the AppellationRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a AppellationRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Appellation Relation
Connects at least one Record to at least one Person, Group or Position that is or was responsible for conceiving and formulating the information contained in the Record. The Record is the source of the Relation and the Person(s), Group(s) or Position(s) is the target.
Class implementation of RiC-R079 and RiC-R079i relations
A superclass for any category of some thing. A type characterizes an entity.
Connects at least one Person to at least another Person, when the first has(ave) child(s) the second one(s). The Relation is oriented from the parent to the child: the parent is the source of the relation, and the child(ren) is the target.
Class implementation of RiC-R018 and RiC-R018i relations
Connects at least one Person to at least another Person, when the first has/have descendant the second one(s). The Relation is oriented from the ascendant to the descendant: the ascendant Person(s) is the source of the Relation, and the descendant Person(s) is the target.
Class implementation of RiC-R017 and RiC-R017i relations
Connects at least two Persons, when they correspond or corresponded to each other. This Relation is not oriented.
Class implementation of RiC-R052 and Ri052i relations
Connects at least two Persons who directly know each other during their existence. This Relation is not oriented.
Class implementation of RiC-R051 and RiC—R051i relations
Connects at least two Instantiations which may be considered as equivalent. This Relation is not oriented.
Class implementation of RiC-R035 and RiC-R035i relations
Connects at least two instantiations. This Relation is a generic, not oriented one.
Connects a Group and at least another Group, when the first one has or had the second one(s) among its subdivisions. The Relation is oriented from the Group to its subdivision(s): the parent Group is the source and the subdivision Group(s) is the target.
Class implementation of RiC-R005 and RiC-R005i relations
The hierarchical relation can be an authority relation, or a whole/part relation between two agents.
Connects at least one Agent to at least another Agent, when the first one is or was hierarchically superior to the second one. The Relation is oriented towards the 'bottom' of the hierarchical tree: the superior Agent(s) is the source of the Relation, and the inferior Agent(s) is the target.
Class implementation of RiC-R045 and RiC-R045i relations
Connects a Thing to at least one other Thing that is or was a portion or division of the whole Thing. The Relation is oriented from the Thing to its part(s): the Thing is the source of the Relation, and the part Thing(s) is the target.
Class implementation of RiC-R002 and RiC-R002i relations
This property 'rolifies' the GroupSubdivisionRelation class. It should be used only when you have to manage instances of the GroupSubdivisionRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a GroupSubdivisionRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Group Subdivision Relation
Can be used, when the record resource is a work, for specifying the connection between the record resource and its author(s).
Connects at least one Agent and one Record Resource or Instantiation on which the Agent has or had some intellectual property rights. The Agent(s) is the source of the Relation and the Record Resource(s) or Instantiation(s) is the target.
Class implementation of RiC-R040 and RiC-R040i relations
Use only if it is not possible to specify a narrower authority relation, for example OwnershipRelation.
Connects at least one Agent and at least one Thing over which the Agent has or had some authority. The Agent(s) is the source of the relation, and the Thing(s) is the target.
Class implementation of RiC-R036 and RiC-R036i relations
Connects at least one Person to at least another one, when the first one has some knowledge of the second one through time or space. The first Person is the source of the Relation, and the second one is the target.
Class implementation of RiC-R050 and RiC-R050i relations
Use only if it is not possible to specify a narrower agent to agent relation, for example a WorkRelation.
Connects at least two Agents. This Relation is a generic, not oriented one.
Class implementation of RiC-R044 and RiC-044i relations
For example, for rules that can be applied to record resources : access rule, use rule, etc.
Corresponds to RiC-A45 (Rule Type attribute).
Connects an Instantiation and at least another Instantiation it has been migrated into. The Relation is oriented chronologically, from the first Instantiation in time (the migrated one) to the one which results from its migration: the first Instantiation in time is the source of the Relation, and the resulting Instantiation is the target.
Class implementation of RiC-R015 and RiC-R015i relations
In some situations, it may be useful or necessary to connect an instantiation to an instantiation that was derived from it but no longer exists or has been lost.
Connects an Instantiation to at least one Instantiation that is derived from it, whether it exists or has been lost or destroyed. The Relation is oriented chronologically, from the first Instantiation in time to the derived Instantiation: the first Instantiation is the source of the Relation, and the derived Instantiation(s) is the target.
Class implementation of RiC-R014 and RiR014i relations
Can be extended with any number of specific subclasses. Among possible specific demographic groups are gender, (biological) sex, education, identity, place, ancestry, ethnic/cultural identification, and religion.
Categorization of a Person or Group based on shared characteristics.
Corresponds to RiC-A15 (Demographic Group attribute)
Among other probably more rare use cases for archival description, can be used between agents (a person owns a corporate body, a corporate body owns a mechanism), or between agents and record resources.
Connects at least one Group, Person or Position and at least a Thing that these Agent(s) own(s) or owned. The Group(s), Person(s) or Position(s) is the source of the Relation, and the Agent(s) is the target.
Class implementation of RiC-R037 and RiC-R037i relations
Connects at least one Activity to at least one Agent that performs or performed the activity. The Activity(-ies) is the source of the Relation and the Agent(s) is the target.
Class implementation of RiC-R060 and RiC-R060i relations
Connects a Place and at least one Thing when the first is associated with the existence and lifecycle of the second one. The Place is the source of the Relation and the Thing(s) is the target.
Class implementation of RiC-R074 and RiC-R074i relations
This property 'rolifies' the PlaceRelation class. It should be used only when you have to manage instances of the PlaceRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a PlaceRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
Connects at least one Person and at least one Position that the Person(s) occupies or occupied. The Person is the source of the Relation and the Position is the target.
Class implementation of RiC-R054 and RiC-R054i relations
Connects at least one Position and a Group in which the position(s) exist(s) or existed, or that is (are) defined by that group's organizational structure. The Position(s) is the source of the Relation and the Group is the target.
Class implementation of RiC-R056 and RiC-R056i relations
An idea, unit of thought, abstract cultural object or category
Connects two or more record resources when there is a genetic link between them. Genetic in this sense is as defined by diplomatics, i.e., the process by which a record resource is developed. This Relation is a generic, not oriented one.
Class implementation of RiC-R023 and RiC-023i relations
Use to connect two record resources only if it is not possible to use a narrower, more specific relation, for example RecordResourceGeneticRelation.
Connects at least two Record Resources. This Relation is a generic, not oriented one.
Record Resource to Record Resource Relation
Class implementation of RiC-R022 and RiC-022i relations
This property 'rolifies' the RecordResourceGeneticRelation class. It should be used only when you have to manage instances of the RecordResourceGeneticRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a RecordResourceGeneticRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Record Resource Genetic Relation
Connects at least one Agent and one or more Record Resource or Instantiation that the Agent(s) hold(s) or held. The Agent(s) is the source of the Relation and the Record Resource(s) or Instantiation is the target.
Class implementation of RiC-R039 and RiC-039i relations
Connects at least one Agent and at least one Record Resource or Instantiation that the Agent manages or managed. The Agent(s) is the source of the Relation, and the Record Resource(s) or Instantiation(s) is the target.
Class implementation of RiC-R038 and RiC-R038i relations
In some situations, it may be useful or necessary to connect a record resource to an instantiation that no longer exists or has been lost, when some of its characteristics are known from a source, such as an old finding aid.
Connects a Record Resource to one or more Instantiations that instantiate it, and which either may exist or may have been lost or destroyed. The Record Resource is the source of the Relation and the Instantiation(s) is the target.
Record Resource to Instantiation Relation
Class implementation of RiC-R025 and RiC-R025i relations
This property 'rolifies' the RecordResourceToInstantiationRelation class. It should be used only when you have to manage instances of the RecordResourceToInstantiationRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a RecordResourceToInstantiationRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Record Resource to Instantiation Relation
Connects at least two Persons, when they are siblings. This Relation is not oriented.
Class implementation of RiC-R048 and RiC-R048i relations
Use the MembershipRelation class for connecting a family and a person.
Connects at least two Persons, when they have some family link, i.e. belong to the same family. This Relation is a generic, not oriented one.
Class implementation of RiC-R047 and RiC-R047i relations
Connects at least two Persons, when they are spouses. This Relation is not oriented.
Class implementation of RiC-R049 and RiC-R049i relations
Connects at least one Person to at least another Person who is or was their student. The Relation is oriented from the teacher(s) to the student(s): the teacher Person(s) is the source of the Relation, and the student Person(s) is the target.
Class implementation of RiC-R053 and RiC-R053i relations
may be useful at least for some types (e.g. demographic group)
Connects a category (a Type) and at least one Thing that belongs to this category. The Type(s) is the source of the Relation, and the Thing(s) is the target.
This property 'rolifies' the TypeRelation class. It should be used only when you have to manage instances of the TypeRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a TypeRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
Connects at least two Agents that have or had some type of work relation in the course of their activities. This Relation is not oriented.
Class implementation of RiC-R046 and RiR046i relations
To be used, either to infer, then query or browse, relations from existing direct 'hasDirectPart' relations between things, or to record a current partitive relation when you do not know if there are intermediate nodes between the related things.
Connects a Thing to a Thing that is, directly or indirectly, a constitutive or component part of that Thing. This is a transitive relation.
This property 'rolifies' the KnowingRelation class. It should be used only when you have to manage instances of the KnowingRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a KnowingRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
This property 'rolifies' the InstantiationToInstantiationRelation class. It should be used only when you have to manage instances of the InstantiationToInstantiationRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a InstantiationToInstantiationRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Instantiation to Instantiation Relation
Connects an Agent to an Agent that is hierarchically inferior.
RiC-R045 ('has or had subordinate ' relation)
This property 'rolifies' the DescendanceRelation class. It should be used only when you have to manage instances of the DescendanceRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a DescendanceRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Descendance Relation
This property 'rolifies' the CreationRelation class. It should be used only when you have to manage instances of the CreationRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a CreationRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
Connects an Agent to an Agent that is directly or indirectly hierarchically inferior. This is a transitive relation.
This property 'rolifies' the DerivationRelation class. It should be used only when you have to manage instances of the DerivationRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a DerivationRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
This property 'rolifies' the ManagementRelation class. It should be used only when you have to manage instances of the ManagementRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a ManagementRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
To be used, either to infer, then query or browse, relations from existing direct 'isDirectPartOf' relations between things, or to record a current partitive relation when you do not know if there are intermediate nodes between the related things.
Connects a Thing to a Thing of which it is a a constitutive or component part, directly or indirectly. This is a transitive relation.
Connects an Agent to an Agent that is directly or indirectly hierarchically superior. This is a transitive relation.
This property 'rolifies' the RecordResourceToRecordResourceRelation class. It should be used only when you have to manage instances of the RecordResourceToRecordResourceRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a RecordResourceToRecordResourceRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Record Resource to Record Resource Relation
This property 'rolifies' the FamilyRelation class. It should be used only when you have to manage instances of the FamilyRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a FamilyRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
Inverse of 'has or had subordinate' object property.
RiC-R045i ('is or was subordinate to' relation)
This property 'rolifies' the AgentToAgentRelation class. It should be used only when you have to manage instances of the AgentToAgentRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a AgentToAgentRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
Connects at least one Agent, to at least another Agent, when the first one(s) control(s) or controlled in a way the activities of the second one(s). The Relation is oriented from the controlling agent to the controlled one: the controlling Agent(s) is the source of the Relation, and the controlled Agent(s) is the target.
Class implementation of RiC-R041 and RiC-R041i relations
This property 'rolifies' the AgentControlRelation class. It should be used only when you have to manage instances of the AgentControlRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a AgentControlRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Agent Control Relation
There may be zero to many intermediate entities, ignored or unknown, in the chronological sequence between the connected entities.
Connects at least one Thing to at least one other Thing that follows it in chronological order. The Relation is oriented chronologically: the preceding Thing(s) is the source of the Relation, the following Thing(s) is the target.
Class implementation of RiC-R009 and RiC-R009i relations
Connects at least one Rule to at least one Thing when it is associated with existence and lifecycle of the Thing. The Rule(s) is the source of the Relation, and the Thing(s) is the target.
Class implementation of RiC-R062 and RiC-R062i relations
This property 'rolifies' the RuleRelation class. It should be used only when you have to manage instances of the RuleRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a RuleRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
The relation does not specify the criteria used for ordering the sequence. There may be zero to many intermediate entities, ignored or unknown, in the sequence between the two connected things. Can be used, for example, for specifying that a record "has next" another record within a record set.
Connects at least one Thing to at least one other Thing that follows or followed it in some sequence. The Relation is oriented from the first Thing(s) in the sequence to the following one(s): the first Thing(s) is the source, and the following Thing(s) is the target.
Class implementation of RiC-R008 and RiC-R008i relations
This property 'rolifies' the SequentialRelation class. It should be used only when you have to manage instances of the SequentialRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a SequentialRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
This property 'rolifies' the WholePartRelation class. It should be used only when you have to manage instances of the WholePartRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a WholePartRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
This property 'rolifies' the OrganicProvenanceRelation class. It should be used only when you have to manage instances of the OrganicProvenanceRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a OrganicProvenanceRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Organic Provenance Relation
This property 'rolifies' the EventRelation class. It should be used only when you have to manage instances of the EventRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a EventRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
This property 'rolifies' the OrganicOrFunctionalProvenanceRelation class. It should be used only when you have to manage instances of the OrganicOrFunctionalProvenanceRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a OrganicOrFunctionalProvenanceRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Organic or functional provenance Relation
This property 'rolifies' the generic Relation class. It should be used only when you have to manage instances of this Relation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a Relation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
This property 'rolifies' the AgentHierarchicalRelation class. It should be used only when you have to manage instances of the AgentHierarchicalRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a AgentHierarchicalRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Agent Hierarchical Relation
This property 'rolifies' the AuthorityRelation class. It should be used only when you have to manage instances of the AuthorityRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a AuthorityRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
This property 'rolifies' the TemporalRelation class. It should be used only when you have to manage instances of the TemporalRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a TemporalRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
This property 'rolifies' the AgentTemporalRelation class. It should be used only when you have to manage instances of the AgentTemporalRelation class, to connect each instance to itself, in order to be able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary class.
Connects a AgentTemporalRelation to itself. It is a reflexive property, that can stand for an instance of the class when necessary, e.g. when you explore a knowledge graph.
has the role of the Agent Temporal Relation
0.5.1 2026-04: made ValPub valid 0.5.0: Handles artifacts as objects with predicates, not just literals (file paths) 0.4.0: First public version
The SHACL Shapes Validator for the Prez Ontology Manifest Model
ShapeP01: You must supply at least one value for prof:hasResource for a prez:Manifest and it must be either a Blank Node or an IRI
ShapeP02: You must supply at least one value for prof:hasArtifact for a prez:Manifest's Resource Descriptors and each must be a string that can be interpreted as a file path, either relative to the manifest file, or an absolute system path or a URL or a Blank Node with a schema:contentLocation and schema:mainEntity predicates
ShapeP03: You must supply exactly one value for prof:hasRole for a prez:Manifest's Resource Descriptors with the value selected from the Prez Manifest Resource Roles Vocabulary
ShapeP04: If you supply a schema:description for a prez:Manifest's Resource Descriptors, it must be either a plain string or a langString literal
ShapeP05: If you supply a schema:name for a prez:Manifest's Resource Descriptors, it must be either a plain string or a langString literal
ShapeN04: If you supplied a prof:hasArtifact for a prez:Manifest's Resource Descriptors that indicated a Blank Node, the Blank Node must contain exactly one schema:contentLocation and exactly one schema:mainEntity predicates
ShapeN03 P06: Role values indicated by prof:hasRole must indicate the Concept Scheme they are defined or used in with skos:inScheme
ShapeN04 P01: You supplied a prof:hasArtifact value as Blank Node, the Blank Node so it must contain exactly exactly one schema:contentLocation predicate
ShapeN04 P02: You supplied a prof:hasArtifact value as Blank Node, the Blank Node so it must contain exactly exactly one schema:mainEntity predicate
Department of Climate Change, Energy, the Environment and Water
1.2 2025-07: Tidy up for inclusion in the BDR Validators Catalogue 1.1 2025-05: Minor updates 1.0 2025-04: First version
Created by the BDR Team in 2025 to validate data bound for the Biodiversity Data Repository
SHACL validator for the Biodiversity Data Repository (BDR)'s profile of Australian Biodiversity Information Standard (ABIS)
Australian Biodiversity Information Governance Group
Dataset IRIs must match the BDR Profile of ABIS' proscribed pattern of https://linked.data.gov.au/dataset/bdr/{UUID}
Site IRIs must match the BDR Profile of ABIS' proscribed pattern which includes linked.data.gov.au
Survey IRIs must match the BDR Profile of ABIS' proscribed pattern which includes linked.data.gov.au
SiteVisit IRIs must match the BDR Profile of ABIS' proscribed pattern which includes linked.data.gov.au
Sample IRIs must match the BDR Profile of ABIS' proscribed pattern which includes linked.data.gov.au
Observation IRIs must match the BDR Profile of ABIS' proscribed pattern pattern of https://linked.data.gov.au/dataset/bdr/{UUID}/ + supplier pattern
Agent (Person and Organization) IRIs must match the BDR Profile of ABIS' proscribed pattern which includes linked.data.gov.au
EDES Herbivory And Physical Damage Shapes Graph
Ecological Monitoring System - Australia Protocols
The value in `sosa:hasResult` _MUST_ be xsd:string.
The value of `rdf:value` _MUST_ have the datatype xsd:string.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/aeca4fcd-5b42-4e23-9880-9013d6976fb3> ; sosa:hasResult ?this . }
TERN's ecologists have determined the feature type is _vegetation disturbance_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/d4fc54b1-0ad3-4512-86b7-d42b121ece45[`vegetation disturbance`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/aeca4fcd-5b42-4e23-9880-9013d6976fb3>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
Value of `sosa:hasSimpleResult` _MUST_ be the same as the value in `sosa:hasResult`.
The observation's `sosa:hasSimpleResult` _MUST_ have a value that is the same as the value in the value node of `sosa:hasResult`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/aeca4fcd-5b42-4e23-9880-9013d6976fb3> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
Observations following the Active Plot Search Protocol are made in the context of a site visit.
Observations _MUST_ have a value for `tern:hasSiteVisit`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/aeca4fcd-5b42-4e23-9880-9013d6976fb3>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/2084a9b6-2927-4651-bd88-781a01c38664>`. `<https://linked.data.gov.au/def/nrm/2084a9b6-2927-4651-bd88-781a01c38664>` is the IRI for "Active Plot Search Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/2084a9b6-2927-4651-bd88-781a01c38664`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/aeca4fcd-5b42-4e23-9880-9013d6976fb3>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
The value of `sosa:hasResult` _MUST_ be a `tern:Text`.
The result _MUST_ be an instance of `tern:Text`.
TERN's ecologists have determined the feature type is _animal occurrence_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/2361dea8-598c-4b6f-a641-2b98ff199e9e[`animal occurrence`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/22fae1ac-9d23-5b11-9fc7-f4f29f900bdf>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the target species types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the target species types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/22fae1ac-9d23-5b11-9fc7-f4f29f900bdf> ; sosa:hasResult ?this . ?this a tern:IRI . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'ff157253-6923-5816-ac05-312dc32cd903'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/22fae1ac-9d23-5b11-9fc7-f4f29f900bdf> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/22fae1ac-9d23-5b11-9fc7-f4f29f900bdf>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/22fae1ac-9d23-5b11-9fc7-f4f29f900bdf>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
The value of `sosa:hasResult` _MUST_ be a `tern:IRI` or `tern:Text`.
The result _MUST_ be an instance of `tern:IRI` or `tern:Text`.
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/ff157253-6923-5816-ac05-312dc32cd903>`. `<https://linked.data.gov.au/def/nrm/ff157253-6923-5816-ac05-312dc32cd903>` is the IRI for "target species types".
The value of `tern:vocabulary` _MUST_ match the pattern `ff157253-6923-5816-ac05-312dc32cd903$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/22fae1ac-9d23-5b11-9fc7-f4f29f900bdf> ; sosa:hasResult ?this . }
TERN's ecologists have determined the feature type is _land surface disturbance_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/7e256d28-e686-4b6a-b64a-ac1b1a8f164d[`land surface disturbance`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a1f5f46b-d6fe-4a1f-8fa8-01b113a2d69f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a1f5f46b-d6fe-4a1f-8fa8-01b113a2d69f>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
Result value's unit of measure _MUST_ have the value `unit:M2`.
The result _MUST_ have `unit:M2` as the value for `tern:unit`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/a1f5f46b-d6fe-4a1f-8fa8-01b113a2d69f> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a1f5f46b-d6fe-4a1f-8fa8-01b113a2d69f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 0 and 10000 inclusive. Datatype should be `xsd:float`.
The result _MUST_ have a value between 0 and 10000 inclusively. Datatype should be `xsd:float`.
The value of `sosa:hasResult` _MUST_ be a `tern:Float`.
The result _MUST_ be an instance of `tern:Float`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/26f843a5-e1ed-46da-b22b-053e567e3227> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/26f843a5-e1ed-46da-b22b-053e567e3227>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/26f843a5-e1ed-46da-b22b-053e567e3227> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/26f843a5-e1ed-46da-b22b-053e567e3227>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/26f843a5-e1ed-46da-b22b-053e567e3227>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/40631c45-30c6-5caa-afbc-221a3024f622>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/40631c45-30c6-5caa-afbc-221a3024f622>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
Result value's unit of measure _MUST_ have the value `unit:PERCENT`.
The result _MUST_ have `unit:PERCENT` as the value for `tern:unit`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/40631c45-30c6-5caa-afbc-221a3024f622> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/40631c45-30c6-5caa-afbc-221a3024f622>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 0 and 100 inclusive.
The result _MUST_ have a value between 0 and 100 inclusively.
The value of `sosa:hasResult` _MUST_ be a `tern:Integer`.
The result _MUST_ be an instance of `tern:Integer`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/02dbcc73-afc3-5425-80a2-eef898bddb67>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Grazing severity types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Grazing severity types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/02dbcc73-afc3-5425-80a2-eef898bddb67> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'cb9ba2d1-3a37-5f68-b6d8-7deefb307835'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/02dbcc73-afc3-5425-80a2-eef898bddb67> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/02dbcc73-afc3-5425-80a2-eef898bddb67>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/02dbcc73-afc3-5425-80a2-eef898bddb67>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
The value of `sosa:hasResult` _MUST_ be a `tern:IRI`.
The result _MUST_ be an instance of `tern:IRI`.
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/cb9ba2d1-3a37-5f68-b6d8-7deefb307835>`. `<https://linked.data.gov.au/def/nrm/cb9ba2d1-3a37-5f68-b6d8-7deefb307835>` is the IRI for "Grazing severity types".
The value of `tern:vocabulary` _MUST_ match the pattern `cb9ba2d1-3a37-5f68-b6d8-7deefb307835$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dd1769b9-c475-4732-915c-9b890a8d5f65>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Growth forms controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Growth forms controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/dd1769b9-c475-4732-915c-9b890a8d5f65> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'d0fc07a7-3ec9-45ed-8850-885a32828d3c'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/dd1769b9-c475-4732-915c-9b890a8d5f65> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dd1769b9-c475-4732-915c-9b890a8d5f65>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dd1769b9-c475-4732-915c-9b890a8d5f65>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/d0fc07a7-3ec9-45ed-8850-885a32828d3c>`. `<https://linked.data.gov.au/def/nrm/d0fc07a7-3ec9-45ed-8850-885a32828d3c>` is the IRI for "Growth forms".
The value of `tern:vocabulary` _MUST_ match the pattern `d0fc07a7-3ec9-45ed-8850-885a32828d3c$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/f8d5c98b-ecee-5c56-9b95-a57280faec60>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Herbivory damage types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Herbivory damage types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/f8d5c98b-ecee-5c56-9b95-a57280faec60> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'eb8f8696-f7ec-5793-8f7a-7331195762db'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/f8d5c98b-ecee-5c56-9b95-a57280faec60> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/f8d5c98b-ecee-5c56-9b95-a57280faec60>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/f8d5c98b-ecee-5c56-9b95-a57280faec60>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/eb8f8696-f7ec-5793-8f7a-7331195762db>`. `<https://linked.data.gov.au/def/nrm/eb8f8696-f7ec-5793-8f7a-7331195762db>` is the IRI for "Herbivory damage types".
The value of `tern:vocabulary` _MUST_ match the pattern `eb8f8696-f7ec-5793-8f7a-7331195762db$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/58668d01-0a2e-5cb1-8623-f1f4e1338a3e>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/58668d01-0a2e-5cb1-8623-f1f4e1338a3e>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
Result value's unit of measure _MUST_ have the value `unit:M`.
The result _MUST_ have `unit:M` as the value for `tern:unit`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/58668d01-0a2e-5cb1-8623-f1f4e1338a3e> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/58668d01-0a2e-5cb1-8623-f1f4e1338a3e>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 0 exclusive and 10000 inclusive. Datatype should be `xsd:float`.
The result _MUST_ have a value between 0 exclusively and 10000 inclusively. Datatype should be `xsd:float`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ce3fd96d-e68d-4b14-b3fd-27690c566440>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Life stages controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Life stages controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/ce3fd96d-e68d-4b14-b3fd-27690c566440> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'5f82c583-167b-4ed2-b25e-4d67decb3f2d'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/ce3fd96d-e68d-4b14-b3fd-27690c566440> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ce3fd96d-e68d-4b14-b3fd-27690c566440>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ce3fd96d-e68d-4b14-b3fd-27690c566440>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/5f82c583-167b-4ed2-b25e-4d67decb3f2d>`. `<https://linked.data.gov.au/def/nrm/5f82c583-167b-4ed2-b25e-4d67decb3f2d>` is the IRI for "Life stages".
The value of `tern:vocabulary` _MUST_ match the pattern `5f82c583-167b-4ed2-b25e-4d67decb3f2d$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/924f1a84-9d02-5120-b8e8-af847c36b7e8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/924f1a84-9d02-5120-b8e8-af847c36b7e8>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/924f1a84-9d02-5120-b8e8-af847c36b7e8> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/924f1a84-9d02-5120-b8e8-af847c36b7e8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8dd72792-5085-5678-bb35-46153daa282f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8dd72792-5085-5678-bb35-46153daa282f>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/8dd72792-5085-5678-bb35-46153daa282f> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8dd72792-5085-5678-bb35-46153daa282f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 0 and 100 inclusive. Datatype should be `xsd:float`.
The result _MUST_ have a value between 0 and 100 inclusively. Datatype should be `xsd:float`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/68d048e9-11f2-5c43-a27f-ae744b2c9799>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Fauna physical damage types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Fauna physical damage types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/68d048e9-11f2-5c43-a27f-ae744b2c9799> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'51fa78ee-187a-5788-9fe0-e68cc476ea91'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/68d048e9-11f2-5c43-a27f-ae744b2c9799> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/68d048e9-11f2-5c43-a27f-ae744b2c9799>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/68d048e9-11f2-5c43-a27f-ae744b2c9799>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/51fa78ee-187a-5788-9fe0-e68cc476ea91>`. `<https://linked.data.gov.au/def/nrm/51fa78ee-187a-5788-9fe0-e68cc476ea91>` is the IRI for "Fauna physical damage types".
The value of `tern:vocabulary` _MUST_ match the pattern `51fa78ee-187a-5788-9fe0-e68cc476ea91$`.
TERN's ecologists have determined the feature type is _plant community_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/ea3a4c64-dac3-4660-809a-8ad5ced8997b[`plant community`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/58f2bd87-17d0-5d11-9ca1-b8f3b76d563b>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the NVIS Major Vegetation Groups controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the NVIS Major Vegetation Groups controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/58f2bd87-17d0-5d11-9ca1-b8f3b76d563b> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'2aa40711-7c6d-506f-ae57-90551476d521'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/58f2bd87-17d0-5d11-9ca1-b8f3b76d563b> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/c7d48965-c779-4398-9315-2cd465b08513>`. `<https://linked.data.gov.au/def/nrm/c7d48965-c779-4398-9315-2cd465b08513>` is the IRI for "Off-plot Belt Transect Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/c7d48965-c779-4398-9315-2cd465b08513`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/58f2bd87-17d0-5d11-9ca1-b8f3b76d563b>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/58f2bd87-17d0-5d11-9ca1-b8f3b76d563b>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/2aa40711-7c6d-506f-ae57-90551476d521>`. `<https://linked.data.gov.au/def/nrm/2aa40711-7c6d-506f-ae57-90551476d521>` is the IRI for "NVIS Major Vegetation Groups".
The value of `tern:vocabulary` _MUST_ match the pattern `2aa40711-7c6d-506f-ae57-90551476d521$`.
Result value's unit of measure _MUST_ have the value `unit:CentiM`.
The result _MUST_ have `unit:CentiM` as the value for `tern:unit`.
Observations following the Within-plot Belt Transect Protocol are made in the context of a site visit.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/e0cb4c61-eaa4-4c57-b627-2061cc9311bd>`. `<https://linked.data.gov.au/def/nrm/e0cb4c61-eaa4-4c57-b627-2061cc9311bd>` is the IRI for "Within-plot Belt Transect Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/e0cb4c61-eaa4-4c57-b627-2061cc9311bd`.
TERN's ecologists have determined the feature type is _weather events_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/e196c39e-959f-4dd4-8816-d0a58b7cc630[`weather events`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a30248c3-33ce-4ffe-8130-7b03aa4e5322>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/a30248c3-33ce-4ffe-8130-7b03aa4e5322> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
Observations following the Active Search Protocol are made in the context of a site visit.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a30248c3-33ce-4ffe-8130-7b03aa4e5322>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
Result value's unit of measure _MUST_ have the value `unit:DEG_C`.
The result _MUST_ have `unit:DEG_C` as the value for `tern:unit`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/a30248c3-33ce-4ffe-8130-7b03aa4e5322> ; sosa:hasResult ?this . }
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/e76e99ef-de1d-4387-9b2e-3455b9f9ff78>`. `<https://linked.data.gov.au/def/nrm/e76e99ef-de1d-4387-9b2e-3455b9f9ff78>` is the IRI for "Active Search Protocol".
The procedure's `tern:methodType` _MUST_ have the value `https://linked.data.gov.au/def/nrm/e76e99ef-de1d-4387-9b2e-3455b9f9ff78`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a30248c3-33ce-4ffe-8130-7b03aa4e5322>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between -30 and 55 exclusive.
The result _MUST_ have a value between -30 and 55 exclusively.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/111a2971-f7c3-4d9d-b079-d9afa0bcc8b0>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the cloud cover types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the cloud cover types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/111a2971-f7c3-4d9d-b079-d9afa0bcc8b0> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'b001aab8-d5c2-4268-a750-bed499386691'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/111a2971-f7c3-4d9d-b079-d9afa0bcc8b0> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/111a2971-f7c3-4d9d-b079-d9afa0bcc8b0>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/111a2971-f7c3-4d9d-b079-d9afa0bcc8b0>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/b001aab8-d5c2-4268-a750-bed499386691>`. `<https://linked.data.gov.au/def/nrm/b001aab8-d5c2-4268-a750-bed499386691>` is the IRI for "cloud cover types".
The value of `tern:vocabulary` _MUST_ match the pattern `b001aab8-d5c2-4268-a750-bed499386691$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/455d3f64-0523-5202-8db4-4775e8dff114> ; sosa:hasResult ?this . }
TERN's ecologists have determined the feature type is _habitat_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/2090cfd9-8b6b-497b-9512-497456a18b99[`habitat`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/455d3f64-0523-5202-8db4-4775e8dff114>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/455d3f64-0523-5202-8db4-4775e8dff114> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/455d3f64-0523-5202-8db4-4775e8dff114>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/455d3f64-0523-5202-8db4-4775e8dff114>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6ca76175-3404-41d4-8ca7-2ade3947f00e>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Microhabitat (tier 2) types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Microhabitat (tier 2) types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/6ca76175-3404-41d4-8ca7-2ade3947f00e> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'2cf23037-6afa-4523-8e9f-0bd86190ccc8'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/6ca76175-3404-41d4-8ca7-2ade3947f00e> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6ca76175-3404-41d4-8ca7-2ade3947f00e>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6ca76175-3404-41d4-8ca7-2ade3947f00e>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/2cf23037-6afa-4523-8e9f-0bd86190ccc8>`. `<https://linked.data.gov.au/def/nrm/2cf23037-6afa-4523-8e9f-0bd86190ccc8>` is the IRI for "Microhabitat (tier 2) types".
The value of `tern:vocabulary` _MUST_ match the pattern `2cf23037-6afa-4523-8e9f-0bd86190ccc8$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ec6a65f7-ff1a-5d00-a6e1-fa3af778aa74>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the weather condition - moon phases controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the weather condition - moon phases controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/ec6a65f7-ff1a-5d00-a6e1-fa3af778aa74> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'30688460-6aaa-53aa-94e7-be1164f5343b'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/ec6a65f7-ff1a-5d00-a6e1-fa3af778aa74> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ec6a65f7-ff1a-5d00-a6e1-fa3af778aa74>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ec6a65f7-ff1a-5d00-a6e1-fa3af778aa74>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/30688460-6aaa-53aa-94e7-be1164f5343b>`. `<https://linked.data.gov.au/def/nrm/30688460-6aaa-53aa-94e7-be1164f5343b>` is the IRI for "weather condition - moon phases".
The value of `tern:vocabulary` _MUST_ match the pattern `30688460-6aaa-53aa-94e7-be1164f5343b$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/25d4c7b7-4cdf-4b69-8774-064055c74e23>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the rainfall duration types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the rainfall duration types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/25d4c7b7-4cdf-4b69-8774-064055c74e23> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'34789810-a3bc-4def-9ddb-d14ff4ba02ea'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/25d4c7b7-4cdf-4b69-8774-064055c74e23> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/25d4c7b7-4cdf-4b69-8774-064055c74e23>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/25d4c7b7-4cdf-4b69-8774-064055c74e23>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/34789810-a3bc-4def-9ddb-d14ff4ba02ea>`. `<https://linked.data.gov.au/def/nrm/34789810-a3bc-4def-9ddb-d14ff4ba02ea>` is the IRI for "rainfall duration types".
The value of `tern:vocabulary` _MUST_ match the pattern `34789810-a3bc-4def-9ddb-d14ff4ba02ea$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b7e7f67b-d983-4167-baca-57cab6dd89a2>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the rainfall types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the rainfall types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/b7e7f67b-d983-4167-baca-57cab6dd89a2> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'36e4cff5-f238-45e3-85ec-bdd0973f09d7'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/b7e7f67b-d983-4167-baca-57cab6dd89a2> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b7e7f67b-d983-4167-baca-57cab6dd89a2>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b7e7f67b-d983-4167-baca-57cab6dd89a2>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/36e4cff5-f238-45e3-85ec-bdd0973f09d7>`. `<https://linked.data.gov.au/def/nrm/36e4cff5-f238-45e3-85ec-bdd0973f09d7>` is the IRI for "rainfall types".
The value of `tern:vocabulary` _MUST_ match the pattern `36e4cff5-f238-45e3-85ec-bdd0973f09d7$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e8f03cc8-33a3-4c2f-9a0d-95a40c34523d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Wind description types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Wind description types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/e8f03cc8-33a3-4c2f-9a0d-95a40c34523d> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'0fb03c4e-ad42-445a-a2c5-688d7d7effd8'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/e8f03cc8-33a3-4c2f-9a0d-95a40c34523d> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e8f03cc8-33a3-4c2f-9a0d-95a40c34523d>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e8f03cc8-33a3-4c2f-9a0d-95a40c34523d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/0fb03c4e-ad42-445a-a2c5-688d7d7effd8>`. `<https://linked.data.gov.au/def/nrm/0fb03c4e-ad42-445a-a2c5-688d7d7effd8>` is the IRI for "Wind description types".
The value of `tern:vocabulary` _MUST_ match the pattern `0fb03c4e-ad42-445a-a2c5-688d7d7effd8$`.
Observations following the Malaise Trapping Protocol are made in the context of a site visit.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/4a2c4309-da43-4ad4-b1eb-637d2e70580d>`. `<https://linked.data.gov.au/def/nrm/4a2c4309-da43-4ad4-b1eb-637d2e70580d>` is the IRI for "Malaise Trapping Protocol".
The procedure's `tern:methodType` _MUST_ have the value `https://linked.data.gov.au/def/nrm/4a2c4309-da43-4ad4-b1eb-637d2e70580d`.
TERN's ecologists have determined the feature type is _animal specimen_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/cd5cbdbb-07d9-4a5b-9b11-5ab9d6015be6[`animal specimen`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8b3281a3-1538-5c9f-b666-a54a934db87c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/8b3281a3-1538-5c9f-b666-a54a934db87c> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8b3281a3-1538-5c9f-b666-a54a934db87c>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
Result value's unit of measure _MUST_ have the value `unit:GM`.
The result _MUST_ have `unit:GM` as the value for `tern:unit`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/8b3281a3-1538-5c9f-b666-a54a934db87c> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8b3281a3-1538-5c9f-b666-a54a934db87c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 0.1 and 500 exclusive.
The result _MUST_ have a value between 0.1 and 500 exclusively.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/badf6713-cfd0-5e44-a32d-e299b9eb6ceb>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/badf6713-cfd0-5e44-a32d-e299b9eb6ceb> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/badf6713-cfd0-5e44-a32d-e299b9eb6ceb>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/badf6713-cfd0-5e44-a32d-e299b9eb6ceb> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/badf6713-cfd0-5e44-a32d-e299b9eb6ceb>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/07216660-5082-428e-9f78-f1139d5c2b1f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the voucher specimen sample types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the voucher specimen sample types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/07216660-5082-428e-9f78-f1139d5c2b1f> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'a3333793-95bd-47fc-ba90-b8fc65a40456'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/07216660-5082-428e-9f78-f1139d5c2b1f> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/07216660-5082-428e-9f78-f1139d5c2b1f>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/07216660-5082-428e-9f78-f1139d5c2b1f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/a3333793-95bd-47fc-ba90-b8fc65a40456>`. `<https://linked.data.gov.au/def/nrm/a3333793-95bd-47fc-ba90-b8fc65a40456>` is the IRI for "voucher specimen sample types".
The value of `tern:vocabulary` _MUST_ match the pattern `a3333793-95bd-47fc-ba90-b8fc65a40456$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/369e6136-c442-4836-8db0-d6722143c48b>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the voucher specimen types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the voucher specimen types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/369e6136-c442-4836-8db0-d6722143c48b> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'bd389ad0-db83-4f22-b32a-4a4ebedb737d'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/369e6136-c442-4836-8db0-d6722143c48b> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/369e6136-c442-4836-8db0-d6722143c48b>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/369e6136-c442-4836-8db0-d6722143c48b>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/bd389ad0-db83-4f22-b32a-4a4ebedb737d>`. `<https://linked.data.gov.au/def/nrm/bd389ad0-db83-4f22-b32a-4a4ebedb737d>` is the IRI for "voucher specimen types".
The value of `tern:vocabulary` _MUST_ match the pattern `bd389ad0-db83-4f22-b32a-4a4ebedb737d$`.
Observations following the Rapid Ground Trapping Protocol are made in the context of a site visit.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/e9a8e65a-59d3-49f0-831d-094c568c5284>`. `<https://linked.data.gov.au/def/nrm/e9a8e65a-59d3-49f0-831d-094c568c5284>` is the IRI for "Rapid Ground Trapping Protocol".
The procedure's `tern:methodType` _MUST_ have the value `https://linked.data.gov.au/def/nrm/e9a8e65a-59d3-49f0-831d-094c568c5284`.
Observations following the Wet Pitfall Trapping protocol are made in the context of a site visit.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/7e4bfab2-4056-4309-bd22-f070f6952bc0>`. `<https://linked.data.gov.au/def/nrm/7e4bfab2-4056-4309-bd22-f070f6952bc0>` is the IRI for "Wet Pitfall Trapping protocol".
The procedure's `tern:methodType` _MUST_ have the value `https://linked.data.gov.au/def/nrm/7e4bfab2-4056-4309-bd22-f070f6952bc0`.
The FRBR-aligned Bibliographic Ontology (FaBiO) is an ontology for describing entities that are published or potentially publishable (e.g., journal articles, conference papers, books), and that contain or are referred to by bibliographic references. **URL:** http://purl.org/spar/fabio **Creators**: [David Shotton](http://orcid.org/0000-0001-5506-523X), [Silvio Peroni](http://orcid.org/0000-0003-0530-4305) **Contributors:** [Paolo Ciccarese](https://orcid.org/0000-0002-5156-2703), [Tim Clark](https://orcid.org/0000-0003-4060-7360) **License:** [Creative Commons Attribution 4.0 International](https://creativecommons.org/licenses/by/4.0/legalcode) **Website:** http://www.sparontologies.net/ontologies/fabio **Cite as:** Peroni, S., Shotton, D. (2012). FaBiO and CiTO: ontologies for describing bibliographic resources and citations. In Journal of Web Semantics, 17: 33-43. https://doi.org/10.1016/j.websem.2012.08.001. Open Access at: http://speroni.web.cs.unibo.it/publications/peroni-2012-fabio-cito-ontologies.pdf
This work is distributed under a Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/legalcode).
FaBiO, the FRBR-aligned Bibliographic Ontology
A Digital Object Identifier for a serial publication item, a dataset or some other entity.
An International Standard Serial Number, ISSN, for electronic versions of serial publications.
An identifier for one of several alternative issues of a magazine, a book or other resource.
Identifies the last page of an entity such as a journal article.
The International Standard Book Number, ISBN, used to identify published books or, more rarely, journal issues.
The International Standard Serial Number, ISSN, an identifer for serial publications.
An identifier used to identify a specific issue of a magazine, a journal or other resource.
A property used to tag a resource with a keyword that is likely to be used in search queries.
Identifies the page range of an entity such as a journal article.
The date on which a document or entity is published. The date can be expressed in three different formats: - yyyy-mm-dd (i.e., xsd:date) - yyyy-mm (i.e., xsd:gYearMonth) - yyyy (i.e., xsd:gYear)
The date on which a resource is published or disclosed.
The name or identifier of the section or part of a resource, for example Part 2 of Issue 6 of Volume 127 of the Journal of Cell Biology, or the Travel Section of a newspaper issue.
Identifies the first page of an entity such as a journal article.
An identifier for a version of a resource, for example a text book, a draft of an article, or a data file.
An identifier for a particular volume of a resource, such as a journal or a multi-volume book.
The count of the number of words in a textual resource.
An item of material added at the end of a book or other publication, typically to include omitted or late-arriving material.
A fabio:Expression can only have part or be part of another fabio:Expression. Moreover, it can be a representation only of a fabio:Work, and it can be embodied only in fabio:Manifestation(s).
A subclass of FRBR expression, restricted to expressions of fabio:Works. For your latest research paper, the preprint submitted to the publisher, and the final published version to which the publisher assigned a unique digital object identifier, are both expressions of the same work.
A precise sequential set of pre-defined logical rules or computational operations to be employed for solving a particular problem in a finite number of steps.
An explicit description of, or set of requirements to be satisfied by, a material, product, resource, service or standard.
A set of metadata elements, policies and guidelines defined for a particular application. The metadata elements used in the application profile may be drawn from more than one element sets, including locally defined sets.
A separate work that provides information describing one or more characteristics of a resource or entity.
A computer program that enables a separate computer to interact programmatically with the computer running the API. (Commonly abbreviated 'API'.)
A unit of computer code in source or compiled form, employing one or more algorithms to be executed by a digital computer to undertake a particular task. Computer programs are collectively called 'software' to distinguish them from the equipment ('hardware') upon which they run.
Meaning = has part. As defined by FRBR (http://www.ifla.org/VII/s13/frbr/frbr1.htm; http://purl.org/vocab/frbr/core#part), a property indicating that one entity includes another entity.
An archival record connotes a material created or received by a person, family, or organization, public or private, in the conduct of their affairs that is preserved because of the enduring value contained in the information it contains or as evidence of the function and the responsibilities of its creator.
As defined by FRBR (http://www.ifla.org/VII/s13/frbr/frbr1.htm; http://purl.org/vocab/frbr/core#realization), a property representing an expression that is an intellectual or artistic realization of a work.
As defined by FRBR (http://www.ifla.org/VII/s13/frbr/frbr1.htm; http://purl.org/vocab/frbr/core#realizationOf), a property representing the work that has been realized by an expression.
The creative work of making an electrical or mechanical recording of sounds, such as the spoken voice, singing, instrumental music, animal vocalizations or sound effects.
A database providing an authoritative source of bibliographic information, for example PubMed (http://www.ncbi.nlm.nih.gov/pubmed), CrossRef Metadata Search (http://search.crossref.org/) and PubMed Central (http://www.ncbi.nlm.nih.gov/pmc/).
A structured collection of logically related records or data usually stored and retrieved using computer-based means.
Standard bibliographic metadata describing an expression of a work. To take the example of a journal article, bibliographic metadata typically include the authors' names, the date of publication, the title of the article, the journal name and volume number, the first and last page numbers, and the Digital Object Identifier (DOI).
An account of the events, works and achievements, both personal and professional, of a person, either living or dead.
A fabio:Work can only have part or be part of another fabio:Work. Moreover, it can be realized only by fabio:Expression(s).
A subclass of FRBR work, restricted to works that are published or potentially publishable, and that contain or are referred to by bibliographic references, or entities used to define bibliographic references. FaBiO works, and their expressions and manifestations, are primarily textual publications such as books, magazines, newspapers and journals, and items of their content. However, they also include datasets, computer algorithms, experimental protocols, formal specifications and vocabularies, legal records, governmental papers, technical and commercial reports and similar publications, and also bibliographies, reference lists, library catalogues and similar collections. For this reason, fabio:Work is not an equivalent class to frbr:ScholarlyWork. An example of a fabio:Work is your latest research paper.
Information manifested in a blog, one of a set of periodic sequential entries containing commentary, descriptions of events, or other material such as images or videos, usually displayed in reverse-chronological order and usually maintained by an individual, or comments on such a post.
An item written or printed in a diary, list, account book, reference book, or database.
Information prepared specifically and primarily for manifestation in a web page, comprising text, images, datasets and/or other works.
A defined chapter of a book, usually with a separate title or number.
Meaning = is part of. As defined by FRBR (http://www.ifla.org/VII/s13/frbr/frbr1.htm; http://purl.org/vocab/frbr/core#partOf), a property indicating that one entity is a part of another entity.
A non-serial document that is complete in one volume or a designated finite number of volumes. A book published by a publisher is usually identified by an International Standard Book Number (ISBN), and may be manifested as a physical printed publication on paper bound in a hard or soft cover, or in electronic format as an 'e-book'.
A defined document section, forming part of or intended for inclusion within a larger document, usually with its own title or chapter number. Different chapters within a document such as a book or a report may each be independently authored, or may all be authored by a single individual or group of authors.
A written review and critical analysis of the content, scope and quality of a book or other monographic work.
A sequence of books having certain characteristics in common that are formally identified together as a group - for instance, the books in the Law, Governance and Technology Series published by Springer.
A sequence of expressions having certain characteristics in common that are formally identified together as a group.
A set of books having certain characteristics in common that informally allow their identification together as a group - for instance, the books of the Harry Potter saga.
A document published by a funding agency requesting submission of applications for financial grants to fund projects, for example to enable research investigations in areas specified in the Call.
A proposal or proposition of a new conceptualization, hypothesis, idea, theory, activity or organisation.
A document containing the case for support for a particular project, usually contained within a grant application document but sometimes distributed separately, without the financial and organizational information that the grant application document also contains.
A part of a grant application that provides a description of a proposed project and gives reasons why it is worthy of funding. (See also fabio:GrantApplication).
Metadata describing the citations made within a work to other works, and (optionally) some characteristics of the expressions of the cited works.
A presentation of findings following a clinical or medical investigation on a human or animal patient, that may contain a diagnosis and proposals for therapeutic treatment and/or epidemiological control measures, or may propose further evaluative studies that will eventually lead to such outcomes.
A report about a particular case or situation.
A recommendation on the appropriate treatment and care of people with a specific disease or condition, based on the best available evidence, designed to help healthcare professionals in their work.
A work created for the purpose of education or instruction, that may be expressed as a text book, a lecture, a tutorial or an instruction manual.
A predefined written procedural method, designed to ensure reliability of findings, for undertaking a medical or veterinary clinical study of the safety, efficacy, or optimum dosage schedule of one or more diagnostic, therapeutic or prophylactic drugs or treatments, or of devices or techniques, involving a randomized controlled trial for evidence-based assessment in humans or animals, specifying criteria of eligibility, nature of controls, sampling schedules, data collection parameters, statistical analyses, reporting standards, etc. to be employed in undertaking the clinical trial.
The report of a pre-planned medical or veterinary clinical study of the safety, efficacy, or optimum dosage schedule of one or more diagnostic, therapeutic or prophylactic drugs, or of devices, treatments or techniques, involving a randomized controlled trial for evidence-based assessment in humans or animals selected according to predetermined criteria of eligibility and observed for evidence of favourable and unfavourable effects.
The report of a trial, for example an experimental trial or a legal trial.
A collection of all the literary or scholastic works of a single person.
A collection of the literary or scholastic works of a single person.
A computer program designed to assist a human user to perform one or more goal-oriented tasks such as word processing or image processing. A computer application will typically save its output files in one or more specific formats, conforming either to proprietary or open standards.
A digital item containing information in computer-readable form encoded in a particular format.
A digital item is an exemplar of a digital manifestation only and it is always stored in a storage medium suitable for digital objects, such as CDs, DVDs, HDs and the Web.
A digital object, such as a computer file.
A display poster, typically containing text with illustrative figures and/or tables, usually reporting research results or proposing hypotheses, submitted for acceptance to and/or presented at a conference, seminar, symposium, workshop or similar event.
A document containing the programme and collected conference papers, or their abstracts, presented at a conference, seminar, symposium or similar event.
A paper, typically the realization of a research paper reporting original research findings, usually published within a conference proceedings volume.
A document containing the programme and collected papers, or their abstracts, presented at an academic meeting.
A formal correction to an error introduced by the author into a previously published document.
A correction to an error in a previously published document.
A protective covering used to bind together the pages of a document or the first, informative, page of a digital document.
A new edition of a historical publication, edited by a scholar other than the original author, containing within the body text the supposedly best version of the original work, with footnotes detailing and commenting on textual variations between different versions, typically with an introduction to the original work written by the scholar, and with a bibliography listing related publications.
A realisation of a fabio:Dataset (a frbr:Work) containing a defined collection of data with specific content and possibly with a specific version number, that can be embodied as a fabio:Digital Manifestation (a frbr:Manifestation with a specific format) and be represented by a specific fabio:ComputerFile (a frbr:Item) on someone's hard drive.
A collection of related facts, often expressed in numerical form and encoded in a defined structure.
A structured document giving information about how data arising from a research project or other endeavour is to be manages, preserved and shared.
A policy that descibes and defines how data should be managed, preserved and shared.
A description and definition of how something should be done. Ideally a policy should be both effective in achieving its goals and acceptable to those who have to abide by it.
A document embodying a policy that descibes and defines how data should be managed, preserved and shared.
A document embodying a policy that descibes and defines how something should be done.
A computer system in which information may be stored.
The software used to create a database. (Commonly abbreviated 'DBMS'.)
The final published expression of a work that bears the publisher's imprimatur. Typically for a journal article, the Definitive Version results from revision of an earlier submitted version of the work following peer review, and is then published in print and/or digital form after the publisher has assigned it a DOI. The Definitive Version is also known as the Version of Record, although according to the CrossRef Glossary (http://crossref.org/02publishers/glossary.html) that term can also refer to the author's final version of a work that is not formally published.
A textual work prepared 'by hand', such as a typescript or word-processed pre-publication draft of a research paper or a report, or a work not otherwise reproduced in multiple copies. [Note: fabio:Manuscript is not intended to describe a handwritten historical document on paper or parchment, for which the FRBR distinctions between work, expression, manifestation and item (individual copy) becomes blurred.].
A demonstration paper, typically describing a new product, service or system created as a result of research, usually presented during a conference or workshop.
A personal record, in a form of book, with discrete entries (often handwritten) arranged by date, reporting what has happened over the course of a day or other period of time.
A book containing personal notes, typically created by writing into a physical book with blank pages.
A database of information which is heavily optimized for reading.
A detachable outer cover, usually made of paper and printed with text and illustrations. This outer cover has folded flaps that hold it to the cover of a document.
A message transmitted over the internet as an item of electronic mail, typically based on the Simple Mail Transfer Protocol (SMTP). Emails can have computer files containing documents, dataset and images attached to them or embedded within them.
Metadata describing the work itself, including for example the name of the creator(s), the title of the work, and the date and place of its creation.
A formal correction to an error introduced by the publisher into a previously published document.
A piece of non-fiction writing on a particular subject, usually of moderate length and without chapters.
A set of questions on a particular topic designed to test the academic, professional or technical ability of the person taking the examination, with achievement of a pass grade in the examination typically being a prerequisite for the award of an educational award such as a degree, or of a professional or technical qualification.
An executive summary is a brief report summarizing a longer formal report, designed to present the key points, conclusions and recommendations arising from the study being reported, for readers too busy to take the time to read the complete report.
A brief report document. This term may also be used synonymously with Rapid Communication to mean 'A short rapidly published research article or conference paper, typically reporting significant research results that have been recently discovered, or a brief news item reporting such discoveries.'
A predefined written procedural method, designed to ensure successful replication of results by others in the same or other laboratories, that describes the overall objectives, organization and implementation of a scientific experiment, and specifies the experimental design, experimental methods, reagents, instrumentation, sampling schedules, data collection parameters, statistical analyses, image processing procedures, safety precautions, reporting standards, etc. employed in undertaking the experiment.
A visual communication object comprising one or more still images on a related theme. If included within a publication, a figure is typically unaligned with the main body of text, having its own descriptive textual figure legend.
A recorded static visual representation. This class of image includes diagrams, drawings, graphs, graphic designs, plans, maps, photographs and prints.
A movie with an accompanying soundtrack, typically created by a professional film studio, designed to communicate a fictional story, record an artistic event, or impart information that is scientific or documentary in nature.
A system of classification derived from the practice and method of collaboratively creating and managing tags to annotate and categorize content in a particular domain. [Contrast fabio:Ontology]
A non-defined collection of words and phrases relating to a particular domain of knowledge, usually added freely by a community, in which homonyms, synonyms and similar ambiguities of meaning present in natural language are not formally disambiguated.
A horizontal bar chart used to guide project planning, execution and control, illustrating the project schedule, with a separate line indicating the start and end dates of each of the key project activities or workpackages, and optionally showing the dependencies between these items. A Gantt chart is typically part of a project plan.
The realization of a grant application, usually containing a case for support document.
A formal written request for financial support from a grant-giving body in support of a project, for example an academic research project. (See also fabio:CaseForSupport.)
A print object bound with rigid protective covers (typically of cardboard covered with cloth, heavy paper, or sometimes leather).
An analog manifestation in physical printed form, typically on paper.
An 'In Brief' is a journal or magazine news item that describes all the articles (or all the important articles) in that issue of the periodical. The content of an 'In Brief' may be constructed from the abstracts of the articles it highlights, but is more likely to be written by a member of the periodical staff especially for the issue.
A news report published in a journal issue.
A news report published in a magazine issue.
A scholarly work that describes applied and validated solutions such as software tools, systems or architectures that benefit from the use of the technology of a particular scholarly domain. Usually, papers of this kind should also provide convincing evidence that there is use of the proposed application or tool by the target user group, preferably outside the institution that conducted its development. E.g. see http://iswc2018.semanticweb.org/call-for-in-use-track-papers/.
A work that reports scholarly activity on a particular topic, either published in written form, or delivered orally at a meeting.
An alphabetically-ordered list of words and phrases ('headings') and associated pointers ('locators') to where useful material relating to that heading can be found in a document.
An instructional document typically supplied with a technologically advanced consumer product, such as a car or a computer application, or with an item of complex equipment such as a microscope.
A fabio:Item can only have part or be part of another fabio:Item. Moreover, it can be an exemplar only of a fabio:Manifestation.
A subclass of FRBR item, restricted to exemplars of fabio:Manifestations. An example of a fabio:Item is a printed copy of a journal article on your desk, or a PDF file of that article that you purchased from a publisher and that now resides in digital form on your computer hard drive.
An article, typically the realization of a research paper reporting original research findings, published in a journal issue.
A particular published issue of a journal, one or more of which will constitute a volume of the journal.
The realization of a piece of writing on a particular topic, usually published within a periodical publication (e.g. journal, magazine and newspaper).
An editorial published in an issue of a journal.
The realization of an opinion written by an editor.
A notebook used by an individual research scientist as the primary record of his or her research activities. A researcher may use a laboratory notebook to document hypotheses, to describe experiments and to record data in various formats, to provide details of data analysis and interpretation, or to record the validation or invalidation of the original hypotheses. The laboratory notebook serves as an organizational tool and a memory aid. It may also have a role in recording and protecting any intellectual property created during the research, and may be used in evidence when establishing priority of discoveries, for example in patent applications. Electronic versions of laboratory notebooks are increasingly being employed by researchers, particularly in chemistry and the pharmaceutical industry.
A document containing notes that summarize a lecture or course of lectures.
A written explanation by a judge or group of judges that accompanies a ruling in a legal case, laying out the reasons and legal principles for the ruling, and sometimes containing pronouncements about what the law is and how it should be interpreted.
An expression of a personal or professional opinion on an issue or topic.
A written or printed communication of a personal or professional nature between individuals and/or representatives of corporate bodies, usually transmitted by the postal service or published in a periodical. In the latter case, the letter is typically addressed to the editor and comments on or discussed an item previously published by that periodical, or of interest to its readership.
The catalog of the holdings of a library, for example that of the Library of Congress (http://catalog.loc.gov/).
A list of items describing the content of a resource, for example items in an exhibition, items offered for sale by a vendor, or entities contained within a library or collection. Ideally, catalogs are created according to specific and uniform principles of construction and are under the control of an authority file.
An article published in a magazine issue.
A particular published issue of a magazine, identified by date, and sometimes also by place (e.g. 'West Coast edition') or language (e.g. 'Spanish edition').
An editorial published in an issue of a magazine.
A fabio:Manifestation can only have part or be part of another fabio:Manifestation. Moreover, it can be an embodiment only of a fabio:Expression and it can be exemplified only by fabio:Item(s).
A subclass of FRBR manifestation, restricted to manifestations of fabio:Expressions. fabio:Manifestation specifically applies to electronic (digital) as well as to physical manifestations of expressions. Examples of different manifestations of a single 'version of record' expression of a scholarly work include an article in a print journal or the on-line version of that article as a web page.
A formal factual, methodological, statistical, technical or research report issued by an individual, group, agency, government body or other institution.
A document that contains metadata information describing one or more characteristics of an entity.
A scholarly work detailing a method, procedure or experimental protocol employed in a particular scholarly domain.
A social networking publication medium such as Twitter, Tumblr, FriendFeed, Facebook or MySpace. A microblog differs from a traditional blog in that its individual content items are smaller than a traditional blog posts, typically containing just a short sentence, a single image, or a URI. These small messages are referred to as microposts.
A Web publication medium containing blog posts.
A mathematical, graphical or physical representation of some physical reality, conceptual idea or theoretical construct.
A single, attributable and machine-readable factual assertion - the smallest unit of publishable information that can be uniquely identified and attributed to its author – typically expressed in RDF. The minimal components of a nanopublication are as follows: * the factual assertion itself, in the form subject, predicate and object (e.g. malaria is_a disease); * provenance information about the nanopublication, defining its authorship and creation date; * supporting information (optional), providing context for the assertion; * a unique identifier for the nanopublication, in the form of a URI; * an integrity key that ensures that the nanopublication is in its original form and has not been altered.
An article written by a journalist and published in a newspaper.
A particular published issue of a newspaper, identified by date, and sometimes also by place or time (e.g. 'Late London Edition').
An editorial published in an issue of a newspaper.
A news report published in a newspaper issue.
A notification of receipt of something, for example of receipt of a book that will later be the subject of a book review.
A long fictitious narrative written in literary prose.
A literary creative work, such as a novel, play, poem or song.
A news item reporting the death of a person, typically accompanied by an description of that person's life and contributions to his or her profession and to society at large.
A document containing an ontology, for example an OWL (Web Ontology Language) file (http://www.w3.org/TR/owl-features/).
A formal representation of a set of concepts within a domain of knowledge, and the logical relationships between those concepts. [Contrast fabio:Folksonomy]
A formal speech, for example one delivered at a ceremonial occasion, or the written transcript of such a speech.
A print object with a flexible cover, usually made of paper or paperboard.
The physical or electronic realization of a patent application.
A formal disclosure of a new invention, made in application for a patent.
The realization of a specification (a standard, a workflow, etc.).
The physical or electronic realization of a patent.
A formal disclosure of a new invention approved by a governmental patent agency, made to register intellectual property rights, and to give exclusive rights to the inventor or assignee to manufacture, use, license or sell the invention for a certain number of years.
A piece of writing published in a periodical issue, typically accompanied by other items by different authors.
A particular issue of a periodical, identified and distinguished from other issues of the same publication by date and/or issue number and/or volume number, and comprising separate periodical items such as editorials, articles and news items.
A particular published volume of a periodical.
Information communicated personally by verbal or written means from one individual to one or more another persons or organizations.
A paper, usually presented during a specific session of a conference dedicated to Ph.D. students, that describes ongoing Ph.D. student's research.
A form of literature written by a playwright, usually consisting of scripted dialogue between characters, intended for theatrical performance rather than reading.
An artistic work written with an intensity or beauty of language more characteristic of poetry than of prose.
A scholarly work that reports a particular intellectual position or viewpoint regarding a particular scholarly topic. Usually, these papers are dependent on the author's opinion or interpretation, do not have an evaluation, and need to present relevant and novel discussion points in a thorough manner. E.g. see https://datasciencehub.net/content/guidelines-authors
A paper that typically accompanies a poster describing some preliminary results of research, usually presented during a conference or a workshop.
The version of an author's original scholarly work, such as a research paper or a review, re-submitted for publication after revision by the author in the light of comments from reviewers. [Note: For the version before peer review, use fabio:Preprint. For the final piblished version, use fabio:DefinitiveVersion.]
The version of an author's original scholarly work, such as a research paper or a review, first submitted to publisher for publication. [Note: For that version resubmitted after peer-review and revision, use fabio:Postprint. For the final published version use fabio:DefinitiveVersion.]
A set of slides containing text, tables or figures, designed to communicate ideas or research results, for projection and viewing by an audience at a conference, symposium, seminar, lecture, workshop or other gatherings, typically embodied in a particular manifestation format such as a SlideShare or PowerPoint slideshow.
A news report published by an organization to provide information to journalists.
A written review and critical analysis of the purpose, features, performance and other qualities of a product.
Metadata describing a project, for example the project name, the names of those who conducted the project, the name of the institution in which the project was conducted, and the project funding information.
A document used to guide project planning, execution and control, specifying the project's goal and objectives and the activities and resources required to achieve these, setting out the project schedule, and identifying the major workpackages, milestones and deliverables. A project plan will typically contain a Gantt chart.
A document containing a project report, intended to be delivered to a customer or funding agency describing the results achieved within a specific project.
A report describing the outcomes of specific project, typically listing 'deliverables' created or 'milestones' achieved during the project.
The realization of a report, usually in printed form.
In printing and publishing, a proof copy is the preliminary version of a publication, after the inclusion of any author corrections following review, and after copy editing and formatting to bring the manuscript into the house style, intended for final checking prior to publication to detect and eliminate typographical errors, omissions or transpositions of text, incorrect layout or placement of illustrations and tables, or other formatting errors. Those who check proofs include the editor, possibly the peer-reviewers (to ensure that their requested modifications have been included to their satisfaction), possibly an in-house professional proof-reader, and / or the author, who is ultimately responsible for ensuring the published work says what (s)he means it to say. Substantive changes to the text are not permitted once the manuscript has reached proof stage.
A set of questions on a particular topic, usually in the form of multiple choice questions requiring the respondent to select the correct answer, or providing the ability to indicate support for or against a proposal on a numerical scale, designed for rapid numerical analysis of responses and often used in surveying public opinion.
A book containing authoritative factual information, such as a dictionary, encyclopaedia, handbook or field guide, which is a realisation of a certain reference work and may contain several reference entries.
A work to which people refer for authoritative factual information, such as a dictionary, encyclopaedia, entry, handbook or field guide, or an informative web page such as an institutional, research group or project home page.
A particular reference entry containing authoritative factual information on a certain topic, usually contained in a larger expression.
A database in which the data are arranged in tables according to their common characteristics, with relationships between the tables being defined by a relational model or schema. A relational database is highly optimized for performance, and is queried using a database query language such as SQL (Structured Query Language). The software used to create a relational database is called a relational database management system (RDBMS).
A work that is a reply, either to a letter or other direct communication, or to feedback or comments about a piece of submitted writing. The latter is typically written by the author of a journal article submitted for publication, or by an applicant making a grant application, in response to reviews of the work from peer reviewers prior to publication (for the journal article) or prior to funding decision (for the grant application). Alternatively, it can be written in response to post-publication peer-review of a published journal article, or comments about it.
A set of recommendations for the minimum reporting requirements to be employed when reporting a particular type of investigation or project, for example a randomized clinical trial. A reporting standard may involve a checklist and a flow diagram, offers a standard way for authors to prepare a complete and transparent report of their findings, and aids their critical appraisal and interpretation of their data. [See also fabio:MinimalInformationStandard.]
A scholarly work that reports original research contributions addressing theoretical, analytical or experimental aspects of a particular scholarly domain. E.g. see http://iswc2018.semanticweb.org/call-for-research-track-papers/.
A scholarly work that describes resources developed to provide experimental materials or facilities, support a research hypothesis, to provide answers to a research question, or that have contributed to the generation of novel scientific work. Examples of such resources include, for experimental sciences, mouse mutant lines and large communally used X-ray or neutron sources, and, for computer sciences, datasets, ontologies, vocabularies, ontology design patterns, evaluation benchmarks or methods, services, APIs and software frameworks, workflows, crowdsourcing task designs, protocols and metrics. E.g. see http://iswc2018.semanticweb.org/call-for-resources-track-papers/
The realization of a retraction. A formal document which publicly withdraws, cancels, refutes, reverses an earlier statement or publication or announces the act of desisting from publishing the original statement.
A formal statement retracting a statement or publication A retraction is a public statement made about an earlier statement that withdraws, cancels, refutes, diametrically reverses the original statement or ceases and desists from publishing the original statement.
A verbal or written remark concerning some entity. In written form, a comment is often appended to that entity and termed an annotation. Within computer programs or ontologies, comments are added to enhance human understanding, and are usually prefaced by a special syntactic symbol that ensures they are ignored during execution of the program.
A scholarly work that surveys the state of the art of topics central to a particular subject or relating to a specific domain (e.g. the scope of a certain journal or conference). Papers of this kind may contain a selective bibliography listing key papers related to the subject or providing advice on information sources, or they may strive to be comprehensive, covering all contributions to the development of a topic and exploring their different findings or views. E.g. see http://www.emeraldgrouppublishing.com/products/journals/author_guidelines.htm?id=JD
A written work made especially for a film or television program. Screenplays can be original works or adaptations from existing pieces of writing, for example novels.
A small computer program written in a scripting language such as JavaScript, PHP or Perl that allows control of one or more software applications.
A work of fiction that is usually written in prose, often in narrative format. This format tends to be more focused and less elaborate than longer works of fiction such as novels.
A musical composition that contains vocal parts ('lyrics') that are performed ('sung').
A piece of music, typically in the form of a composition recorded in musical notation.
An electronic form of data storage that displays a grid of rows and columns, in which each editable cell can contain alphanumeric text, a numeric value, or a formula that defines how the content of that cell is to be calculated from the content of another cell or cells.
Clear and detailed written instructions of a prescribed step-by-step procedure to be routinely followed, and decisions to be made when undertaking a specific task, process or function, to achieve consistent performance, ensure safety and/or assure data quality. (Commonly abbreviated 'SOP'.)
A supplement to a publication such as a book, journal, magazine or newspaper, additional to the main publication. For example, a colour supplement to a sunday newspaper, or a special supplementary issue of a journal or a journal volume containing invited articles on a special topic, or abstracts or papers presented at a scientific conference.
A file accompanying a published journal article, containing additional information of relevance to the article, typically available from the publisher's web site via a hyperlink from the journal article itself.
A literature review focused on a single question that tries to identify, appraise, select and synthesize all high quality research evidence relevant to that question. Systematic reviews of high-quality randomized controlled trials are crucial to evidence-based medicine. An understanding of systematic reviews and how to implement them in practice is becoming mandatory for all professionals involved in the delivery of health care. Systematic reviews are not limited to medicine, and are quite common in other sciences such as psychology, educational research and sociology.
A table listing the parts of publication such as a book or technical specification, and the pages on which these content elements start (if the publication is printed or otherwise organized into pages), usually listed in order of appearance. The Table of Contents typically includes first-level headers, such as the chapter titles of a book, and may also include second- and even third-level headers. In electronic works, the Table of Contents entries are often internally hyperlinked to the content items, so that clicking on the entry takes the reader to that item.
A graphical means of presenting data in a grid of rows and columns, within which the cells usually contain alphanumeric text or numeric values. If included within a publication, a table typically appearing unaligned with the main body of text, with its own descriptive title.
An official or public specification of, or requirement for, a technical method, practice, process or protocol that is involved in, for example, manufacturing, computation, electronic communication, or digital media.
A book containing instructional material relating to a particular topic of academic study, designed to be read by students.
A tabular dataset providing information about the times and locations of a planned series of events.
A database specifically designed for the storage and retrieval of Resource Description Framework (RDF) data consisting of subject-predicate-object triples. A triple store is queried using the RDF query language SPARQL.
A posting made on the social networking site Twitter. A tweet is a text message limited to 140 characters in length, that is broadcast and readable by anyone who accesses Twitter.
A content item that is published in a Microblog, typically containing just a short sentence, a single image, or a URL.
A document containing a vocabulary mapping
A mapping of correspondences between two vocabularies. For controlled vocabularies, such mappings may be expressed using SKOS (http://www.w3.org/2004/02/skos/).
A snapshots of (part of) the World Wide Web.
A Web manifestation usually identified by a Uniform Resource Identifier (URI), and made accessible to a user by means of the Hypertext Transport Protocol (HTTP) in a Web browser window. Several interlinked web pages hosted together on a Web server and accessed through a single domain name or IP address constitute a web site.
A manifestation that represents pages either in physical (e.g., one side of a sheet of paper) or in digital form (e.g., a page in a PDF, or a web page).
A digital manifestation on the Web, such as a wiki, a web site, a web page or a blog.
A collection of related web pages containing text, images, videos and/or other digital assets that are addressed relative to a common Uniform Resource Locator (URL). A web site is hosted on at least one web server, accessible via a network such as the Internet or a private local area network.
An authoritative report or guide designed to educate readers and help people make decisions, or to explain technical problems and how to solve them. White papers are typically published by governments to propose new legislation for discussion, and by commercial companies to inform readers about products or services, as aids to marketing.
A collaborative Web manifestation, usually maintained by a project team or group, providing easy-to-edit pages that can be used to accumulate related information for shared use by the group and/or publication.
Information about a particular topic in one of the versions of Wikipedia, the online encyclopedia (http://www.wikipedia.org/).
A component of the case for support of a grant application, describing a particular aspect of the work to be undertaken.
A recorded sequence of connected steps, which may be automated, specifying a reliably repeatable sequence of operations to be undertaken when conducting a particular job, for example an in silico investigation that extracts and processes information from a number of bioinformatics databases.
An unpublished paper, usually circulated privately among a small group of peers, to provide information or with a request for comments or editorial improvement.
A document containing the programme and collected workshop papers, or their abstracts, presented at a workshop or similar event.
A paper, typically the realization of a research paper reporting original research findings, usually presented at a workshop and published within a workshop proceedings volume.
An analog medium for magnetic recording of audio and video information, made of a thin magnetizable coating on a long, narrow plastic tape, typically wound on a spool.
A means of storing information in non-digital form, e.g. paper, film (for analogue photographs or movies), magnetic tape (for analogue sound recordings or video recordings) or vinyl disc.
A non-rewritable optical disc used to store digital data.
A means of storing information in digital form, involving binary encoding of data in 0s and 1s, e.g. a computer random access memory, hard disc, USB stick, CD, DVD or digital magnetic tape.
A distributed and commoditized Internet-based computing resource, whereby shared services, software programs, and information storage facilities are provided to computers and other devices on demand, at locations of which the user may be unaware, like the electricity grid.
The date on which a particular endeavour, such as an ontology, was last updated.
A rewritable digital medium for magnetic recording of audio, video and other data, made of a thin magnetizable coating on a long, narrow strip of plastic, usually wound on a spool.
A non-rewritable optical disc storage medium resembling a compact disc (CD), usually used for video and data storage. A DVD has the same physical dimensions as a CD, but is capable of storing more than six times as much data.
A thin flexible strip of plastic or other material coated with light-sensitive emulsion upon which images can be recorded, typically using a camera, usually used to record photographic images or motion pictures.
A rewritable data storage medium that is composed of a disk of thin, flexible (floppy) magnetic storage medium encased in a square or rectangular plastic shell. Data are encoded magnetically by a read/write head that float on a cushion of air in close proximity to the surface of the rotated disk.
A non-volatile storage device for digital data, composed of one or more rigid discs (platters) mounted side by side on a motor-driven spindle within a metal case. Data are encoded magnetically by read/write heads that float on cushions of air in close proximity to the surfaces of the rotated platters.
The date on which a particular digital item, such as a PDF or an HTML file, has been accessed by somebody.
An identifier used by the preprint repository ArXiv.
A CODEN is a six character, alphanumeric bibliographic identification code, that provides concise, unique and unambiguous identification of the titles of serials and non-serial publications.
The count of the number of characters in a textual resource.
The year in which an entity has been copyrighted.
The date on which something, for example a document, is corrected.
The date on which some item has been collected, for example the data gathered by means of questionnaires.
The date on which some item is received, for example a document being received by a publisher.
A date by which something has to be done.
The date on which a particular endeavour, such as a grant application, has been or will be approved or rejected by somebody.
The date on which an entity has been deposited, for example in a library, repository, supplementary information archive, database or similar place of document or information storage.
The discipline to which a subject vocabulary belongs.
A term dictionary is a collection of subject terms.
A controlled vocabulary, usually referring to terms within a particular classification system, such as the ACM Computing Classification System or MeSH, the Medical Subject Headings, or a controlled vocabulary of disciplines.
A concept that identifies a field of knowledge or human activity defined in a controlled vocabulary, such as Computer Science, Biology, Economics, Cookery or Swimming.
This property relates a subject vocabulary to the discipline to which it belongs.
This property expresses the fact that a scheme contains a concept.
The date on which something is distributed, for example the date on which a preprint of a document is e-mailed to colleagues and other academics by the author(s), or the date on which a printed announcement of forthcoming theatre events is mailed to those those on the theatre's mailing list.
A local identifier for an article within an electronic (i.e. on line, in HTML format) periodical issue. Use in preference to prism:startingPage when the article lacks page numbers
The date before which an entity should not be published, or before which a press release should not be reported on. For open-access journal articles, the embargo date is the date before which availability of the open-access version of the article is restricted by the publisher, following subscription-access availability of the published work. The duration of the embargo period can be specified by fabio:hasEmbargoDuration.
The time period for which an entity is embargoed. During this period, the entity should not be published or, in the case of a press release, should not be reported on. For open-access journal articles, the embargo duration specifies that period of time during which availability of the open-access version of the article is delayed by the publisher, following subscription-access availability of the published work. The end of the embargo period can be specified by fabio:hasEmbargoDate.
A persistent identifier of the Handel system for digital objects and other resources on the Internet.
A linking International Standard Serial Number.
A property linking a particular work to its manifestations. This property is additional to the relationships between FRBR endeavours present in the classical FRBR data model.
A property linking a particular manifestation to the work it is manifesting. This property is additional to the relationships between FRBR endeavours present in the classical FRBR data model.
As defined by FRBR (http://www.ifla.org/VII/s13/frbr/frbr1.htm; http://purl.org/vocab/frbr/core#embodiment), a property representing a manifestation that embodies an expression.
An internal identifier for the abbreviation of the title of journals available from the National Library of Medicine repository.
has National Library of Medicine journal title abbreviation
A short version of the title of an entity, typically used to label or refer to a particular entity in an abbreviated form, for example an abbreviated journal title in a reference, or a short title of a document used as the running title in a page header.
An internal identifier for journals available from the National Library of Medicine repository.
has National Library of Medicine journal identifier
The count of the number of pages in a textual resource.
A unique identifing number issued by a patent authority to identify a patent, displayed at the beginning of the patent document.
The place (usually, the city) where the publisher of a particular bibliographic resource is located.
A property linking a particular work to its items. This property is additional to the relationships between FRBR endeavours present in the classical FRBR data model.
A property linking a particular item to the work it portrays. This property is additional to the relationships between FRBR endeavours present in the classical FRBR data model.
As defined by FRBR (http://www.ifla.org/VII/s13/frbr/frbr1.htm; http://purl.org/vocab/frbr/core#exemplar), a property representing an item that exemplifies a manifestation.
This property is used to associate a frbr:Endeavour to a term in a particular classification system - and the term is considered one of the main topics for the endeavour in consideration.
This property is used to associate a frbr:Endeavour to a term in a particular classification system.
An identifier for bibliographic entities hosted by the PubMed Central repository.
An identifier for bibliographic records held by the PubMed repository.
The year in which a resource is published.
A property linking a particular expression to its items. This property is additional to the relationships between FRBR endeavours present in the classical FRBR data model.
A property linking a particular item to the expression it represents. This property is additional to the relationships between FRBR endeavours present in the classical FRBR data model.
The date on which an agent is requested to do something, for example a reviewer is requested to write a review of a paper submitted to a journal for publication, or an author is requested to supply a revised version of the paper in response to the reviews received.
The date on which something, for example a claim or a journal article, is retracted.
The Serial Item and Contribution Identifier is a code used to uniquely identify specific volumes, articles or other identifiable parts of a periodical. It is intended primarily for use by those members of the bibliographic community involved in the use or management of serial titles and their contributions.
Permits specification of the season of the year, for example spring, summer, autumn and winter in British English.
A literal (for example a number or a letter) that identifies the sequence position of a work within a particular context, for example a book in a book series, a chapter in a document, a volume in a journal.
The number defining an international standard, for example Z39.96 - 201x, identifying NISO JATS, the Journal Article Tag Suite.
A secondary title that follows the main title of a work.
A version of the subtitle of an entity translated into another language, which may be specified using the object property dcterms:language.
A version of the title of an entity translated into another language, which may be specified using the object property dcterms:language.
An identifier, in form of an HTTP Universal Resource Locator (URL), for a particular resource on the World Wide Web.
The count of the number of volumes a work includes.
A global system of interconnected computer networks that uses the standard Internet Protocol Suite (TCP/IP) to serve billions of users worldwide. The internet connects millions of private, public, academic, business and governmental computers, that are individually attached to local networks linked together by a broad array of electronic, radio and optical networking technologies to form the internet.
A private computer network, unconnected to the internet or separated from it by a firewall, that uses a network operating system and Internet Protocol technologies to permit an organization's information to be shared securely within that organization.
A thin flat material, typically made from wood pulp, mainly used for writing upon, for printing upon or for packaging.
Abbreviation of Random Access Memory. A form of rewritable computer data storage that takes the form of integrated circuits that allow data to be stored and accessed in any order (i.e. at random), thereby achieving greater speed than for access of data stored in linear form on digital magnetic tape.
A digital storage device built entirely from solid electronic materials with no moving parts, e.g. a USB flash drive.
A property that identifies the calendar system used to specify a date, for example the Chinese, Gregorian, Hebrew, Islamic or Lunar calendar.
An analog sound storage medium consisting of a flat disc made of moulded vinyl plastic with an inscribed, modulated spiral groove.
A system of interlinked hypertext documents written in HTML and accessed using the HTTP protocol via the Internet.
A brief summary of a work on a particular subject, designed to act as the point-of-entry that will help the reader quickly to obtain an overview of the work's contents. The abstract may be an integral part of the work itself, written by the same author(s) and appearing at the beginning of a work such as a research paper, report, review or thesis. Alternatively it may be separate from the published work itself, and written by someone other than the author(s) of the published work, for example by a member of a professional abstracting service such as CAB Abstracts.
A structured summary containing essential metadata describing a research investigation and/or the research outputs that have resulted from it, for example datasets and journal articles, structured according to some minimal information standard. Such a structured summary can be embodied in both human-readable and machine-readable manifestations, e.g. HTML and RDF. Such a structured summary differs from the Abstract of a journal article, in that the latter is written as a piece of continuous prose, but typically omits vital factual information about the investigation, such as when and where it was conducted, by whom, and on now many specimens or subjects.
A collection of selected literary or scholastics works, for example poems, short stories, plays or research papers.
A collection of expressions, for example a periodical or a book series.
An archival document is a realization of the content related to an archival record. It can be exemplified as a book, a document, a letter, a database, etc.
It describes any work regarded as art in its widest sense, including works from literature and music, visual art, etc.
A controlled vocabulary or official list that establishes, for consistency, the authoritative forms of headings, and the preferred terms or proper names to be used, when creating a catalogue or when indexing and searching a set of entities within a defined domain.
A collection of selected words and phrases related to a particular domain of knowledge used to permit consistency of metadata annotation and improved retrieval following a search, in which homonyms, synonyms and similar ambiguities of meaning present in natural language are disambiguated.
A thesis reporting a research project undertaken as part of an undergraduate course of education leading to a bachelor's degree.
A book authored by a student containing a formal presentations of research outputs submitted for examination in completion of a course of study at an institution of higher education, to fulfil the requirements for an academic degree. Also know as a dissertation. [For the alternative meaning of the word 'thesis', namely the formulation of a concept, hypothesis, idea, point of view or theory presented for review and/or discussion, use fabio:Proposition.]
A paper, typically the realization of a research paper reporting original research findings, usually published within an academic proceedings volume.
A discipline dictionary is a collection of subject disciplines.
A thesis reporting the research undertaken during a period of graduate study leading to a doctoral degree.
An excerpt is more general than a quotation, and is generally used to indicate a re-published extract from a book, instruction manual, film, radio programme, etc, that need not be what someone said. For example: Oxford 01865 Oxshott 01372 Oxted 01883 Oxton 01578 is an excerpt from the UK Dialling Codes section of the Oxford Telephone Directory. Similarly, the following concluding passage from William Wordsworth's poem Lines written a Few Miles above Tintern Abbey is an excerpt rather than a quotation: Nor wilt thou then forget, That after many wanderings, many years Of absence, these steep woods and lofty cliffs, And this green pastoral landscape, were to me More dear, both for themselves and for thy sake.
A segment or passage selected from a larger expression for use in another expression, usually with specific attribution to its original source. [Note: Use fabio:Excerpt to indicate a segment or passage selected from another expression that is not a passage of speech, and fabio:Quotation to indicate a segment or passage selected from another expression that is a passage of speech.]
A quotation is a repetition of what someone has said, and is presented "within quotation marks", for example: On June 4th 1940, Winston Churchill made a speech on the radio that has since become famous, that included the words: " . . . we shall fight on the beaches, we shall fight on the landing grounds, we shall fight in the fields and in the streets, we shall fight in the hills; we shall never surrender . . ." Similarly, the words "but Brutus is an honourable man" from Mark Antony's funeral speech in Shakespeare's play Julius Caesar is a quotation, since Mark Antony says these words in the play.
A passage of speech selected from a larger verbal or written expression for use in another expression, with specific attribution to its original source, and usually demarcated by quotation marks and / or by placing it in a separate indented paragraph. [Note: Use fabio:Quotation to indicate a segment or passage selected from another expression that is a passage of speech, and fabio:Excerpt to indicate a segment or passage selected from another expression that is not a passage of speech.]
A scholarly periodical primarily devoted to the publication of original research papers. [Printed and electronic manifestations of the same journal are usually identified by separate print and electronic International Standard Serial Numbers (ISSN or eISSN, respectively), that identifies the journal as a whole, not to individual issues of it.]
A particular published volume of a journal, comprising one or more journal issues.
A publication issued on a regular and ongoing basis as a series of issues, each issue comprising separate periodical items, for example editorials, articles, news items and/or other writings.
A periodical, usually devoted to a particular topic or domain of interest, and usually published weekly or monthly, consisting primarily of non-peer reviewed editorials, journalistic news items and more substantive articles, reviews, book reviews and discussions concerning current or recent events and publications, and matters of interest to the domain served by the magazine. [Some scientific journals, notably Science and Nature, also secondarily serve as science magazines by containing substantive editorials and news items on vital or controversial issues].
A thesis reporting a research project undertaken as part of a graduate course of education leading to a master's degree.
A metadata standard specifying items to be included when creating metadata describing a dataset of a particular type, or when creating a structured summary of the main findings of an article or report in a particular domain of interest, thereby ensuring adequate descriptive information is recorded for subsequent resource discovery and/or interpretation of the information described. [See also fabio:ReportingStandard.]
A moving display, either generated dynamically by a computer program or formed from a series of pre-recorded still images imparting an impression of motion when shown in succession. Examples include animations, cine films, videos, and computational simulations. Expressions of moving images may incorporate synchronized soundtracks.
A visual representation other than text, including all types of moving image and still image.
A non-peer reviewed periodical, usually published daily or weekly, consisting primarily of editorials and news items concerning current or recent events and matters of public interest.
A short rapidly published research article or conference paper, typically reporting significant research results that have been recently discovered, or a brief news item reporting such discoveries.
A classification arranged in a hierarchical structure of classes and subclasses, showing parent-child isA relationships, or broader_than - narrower_than relationships.
A type of controlled vocabulary used in information retrieval applications for indexing or tagging purposes, in which relationships between terms are made explicit. These are normally hierarchical relationships (is-a, subsumption; e.g. a cow is a mammal), equivalency relationships relating non-preferred terms to preferred terms (e.g. pitch and frequency), or associative relationships, in which the relationship that exists is neither one of hierarchy or equivalence, but rather one of similarity (e.g. sports and leisure pursuits).
A set of words, either constituting a language, or more specifically used to describe a particular domain of knowledge.
A concept that defines a term within the controlled vocabulary of a particular classification system, such as the ACM Computing Classification System or MeSH, the Medical Subject Headings, used as an annotation to describe the subject, meaning or content of an entity.
As defined by FRBR (http://www.ifla.org/VII/s13/frbr/frbr1.htm; http://purl.org/vocab/frbr/core#embodimentOf), a property representing an expression that is embodied by a manifestation.
As defined by FRBR (http://www.ifla.org/VII/s13/frbr/frbr1.htm; http://purl.org/vocab/frbr/core#embodimentOf), a property representing a manifestation that is exemplified by an item.
An analog item is an exemplar of an analog manifestation only and it is always stored in a storage medium suitable for analog objects, such as paper, vinyl discs and films.
A real object that is an exemplar of a fabio:Manifestation, such as a particular copy of the book 'Alice's adventures in Wonderland', that a person may own.
This property relates a fabio:Item to the medium upon which it is stored.
A manifestation that represents data in binary form, encoding the data as a series of 0s and 1s.
A device for recording information or storing data.
This property relates a storage medium to the fabio:Item stored upon it.
SHACL translation of locally applicable checks from the qSKOS quality issue catalogue. Network-dependent checks, including broken-link detection, are not included.
SHACL shapes implementing structural and graph-based qSKOS quality checks for SKOS vocabularies.
qSKOS SHACL Validator
omitted or invalid language tags: alternative labels must be language-tagged strings.
Checks that alternative labels are language-tagged strings.
Concept alternative labels
omitted or invalid language tags: hidden labels must be language-tagged strings.
Checks that hidden labels are language-tagged strings.
Concept hidden labels
missing labels / inconsistent preferred labels: each concept must have at least one language-tagged preferred label and no more than one per language.
Checks required preferred labels, language tags and preferred-label uniqueness.
Concept preferred labels
Detects labels used simultaneously as preferred, alternative or hidden labels on one concept.
Disjoint labels
disjoint-label violation: the same lexical label and language is used with more than one SKOS label property on this concept.
SELECT DISTINCT $this ?value WHERE { VALUES (?p1 ?p2) { (skos:prefLabel skos:altLabel) (skos:prefLabel skos:hiddenLabel) (skos:altLabel skos:hiddenLabel) } $this ?p1 ?value ; ?p2 ?value . }
Detects empty or whitespace-only preferred, alternative and hidden labels.
Empty labels
empty labels: a SKOS label is empty or contains only whitespace.
SELECT DISTINCT $this ?path ?value WHERE { VALUES ?path { skos:prefLabel skos:altLabel skos:hiddenLabel } $this ?path ?value . FILTER(STRLEN(REPLACE(STR(?value), "\\s", "")) = 0) }
Detects cycles in the transitive broader hierarchy.
Hierarchical cycles
hierarchical cycle: following skos:broader one or more times returns to the same concept.
SELECT $this WHERE { $this skos:broader+ $this . }
Detects mapping properties used between concepts in the same scheme.
Mapping relations misuse
mapping relation misuse: a mapping property links concepts belonging to the same concept scheme.
SELECT DISTINCT $this ?path ?value WHERE { VALUES ?path { skos:broadMatch skos:narrowMatch skos:relatedMatch skos:closeMatch skos:exactMatch } $this ?path ?value ; skos:inScheme ?scheme . ?value skos:inScheme ?scheme . }
Warns when a concept scheme does not declare any top concepts.
Omitted top concepts
omitted top concepts: the concept scheme has no declared top concept.
SELECT $this WHERE { FILTER NOT EXISTS { $this skos:hasTopConcept ?concept } FILTER NOT EXISTS { ?concept skos:topConceptOf $this } }
Warns about concepts disconnected from semantic relations and top-concept declarations.
Orphan concepts
orphan concept: the concept has no semantic relation and is not declared as a top concept.
SELECT $this WHERE { FILTER NOT EXISTS { { $this (skos:broader|skos:narrower|skos:related) ?other } UNION { ?other (skos:broader|skos:narrower|skos:related) $this } UNION { $this skos:topConceptOf ?scheme } UNION { ?scheme skos:hasTopConcept $this } } }
Warns when concepts in the same scheme share an identical preferred label.
Overlapping preferred labels
overlapping labels: another concept in the same scheme has the same preferred label.
SELECT DISTINCT $this ?value WHERE { $this skos:inScheme ?scheme ; skos:prefLabel ?value . ?other skos:inScheme ?scheme ; skos:prefLabel ?value . FILTER(?other != $this) }
Detects semantic and mapping relations from a concept to itself.
Reflexive relations
reflexive relation: a concept has a semantic or mapping relation to itself.
SELECT DISTINCT $this ?path WHERE { VALUES ?path { skos:broader skos:narrower skos:related skos:broadMatch skos:narrowMatch skos:relatedMatch skos:closeMatch skos:exactMatch } $this ?path $this . }
Detects concept pairs linked by both hierarchical and associative relations.
Relation clashes
relation clash: two concepts are both hierarchically and associatively related.
SELECT DISTINCT $this ?value WHERE { $this (skos:broader|skos:narrower) ?value ; skos:related ?value . }
Detects declared top concepts that also have broader concepts.
Top concepts with broader concepts
top concept with broader concept: a declared top concept has skos:broader.
SELECT DISTINCT $this ?value WHERE { $this skos:broader ?value . }
Detects semantic or mapping relation targets that are not declared as SKOS concepts.
Undefined related resources
undefined SKOS resource: a semantic relation points to a resource not typed as skos:Concept.
SELECT DISTINCT $this ?path ?value WHERE { VALUES ?path { skos:broader skos:narrower skos:related skos:broadMatch skos:narrowMatch skos:relatedMatch skos:closeMatch skos:exactMatch } $this ?path ?value . FILTER NOT EXISTS { ?value a skos:Concept } }
Warns about concepts without notes, definitions, examples or other SKOS documentation.
Undocumented concepts
undocumented concept: the concept has no SKOS documentation property.
SELECT $this WHERE { FILTER NOT EXISTS { $this ?documentation ?value . VALUES ?documentation { skos:note skos:changeNote skos:definition skos:editorialNote skos:example skos:historyNote skos:scopeNote } } }
Warns when broader and narrower inverse statements are not both explicitly present.
Unidirectional hierarchy
unidirectional hierarchy: a broader or narrower relation lacks its explicit inverse.
SELECT DISTINCT $this ?path ?value WHERE { { $this skos:broader ?value . FILTER NOT EXISTS { ?value skos:narrower $this } BIND(skos:broader AS ?path) } UNION { $this skos:narrower ?value . FILTER NOT EXISTS { ?value skos:broader $this } BIND(skos:narrower AS ?path) } }
Warns when symmetric associative relations are not asserted in both directions.
Unidirectional related relations
unidirectional associative relation: the inverse skos:related statement is not explicitly present.
SELECT DISTINCT $this ?value WHERE { $this skos:related ?value . FILTER NOT EXISTS { ?value skos:related $this } }
Taken from the LoC website at IRI location
The Bibframe vocabulary consists of RDF classes and properties used for the description of items cataloged principally by libraries, but may also be used to describe items cataloged by museums and archives. Classes include the three core classes - Work, Instance, and Item - in addition to many more classes to support description. Properties describe characteristics of the resource being described as well as relationships among resources. For example: one Work might be a "translation of" another Work; an Instance may be an "instance of" a particular Bibframe Work. Other properties describe attributes of Works and Instances. For example: the Bibframe property "subject" expresses an important attribute of a Work (what the Work is about), and the property "extent" (e.g. number of pages) expresses an attribute of an Instance.
Title as abbreviated for citation, indexing, and/or identification.
Title associated with the resource that is different from the Work or Instance title.
Access restrictions and allowances regarding access to a resource, e.g., lending policy, access restrictions, embargos.
General statement of allowances and restrictions on access to a resource, including retention, reproduction, access, and lending.
2021-06-09 (Added editorial note [GH44])
Any entry from the Standard Identifiers vocabulary at ID may be used; all have been defined as a ont:Identifier
Token or name that is associated with a resource, such as a URI or an ISBN.
Information about an organization, person, etc., from which a resource may be obtained.
American National Standards Institute identifier.
2021-06-09 (Changed subclass to Material [GH28])
Physical or chemical substance applied to a base material of a resource.
Substance or composition of the resource.
Resources organically created, accumulated, and/or used by a person, family, or organization in the course of conduct of affairs and preserved because of their continuing value.
Resource reflecting an individual, material embodiment of a Work.
Resource that represents an arrangement of another resource.
Resource reflecting a conceptual essence of a cataloging resource.
2017-02-03 (Revised property name and definition)
Number assigned by publishers of sound recordings to identify the issue designation, or serial identification, of the resource.
Identifier assigned to the smallest identifiable unit of a recording session, e.g., a specific recording of an individual song.
2017-02-03 (Moved to Identifier class group from Item group)
Optical machine-readable representation of data relating to the item to which it is attached.
Underlying physical material of a resource.
Information about methods used to bind a published or unpublished resource, or other binding information.
System used to format a video resource for television broadcast, e.g., HDTV, PAL.
Technical specification relating to the encoding of video images in a resource.
Specifies the sound capture and storage technique used on a sound recording resource.
Technical specification relating to the encoding of sound in a resource.
Categorization reflecting the format of the storage medium and housing of a carrier.
Data type for encoding of geospatial information in a cartographic resource, e.g., raster, vector, point.
Technical specification relating to the digital encoding of text, image, audio, video, and other types of data in a resource.
Object type for encoding of geospatial information in a cartographic resource, e.g., point, line, polygon.
Resource that shows spatial information, including maps, atlases, globes, digital, and other cartographic resources.
Dates associated with issues or items held.
Numbering or other enumeration and dates associated with issues or items held.
Dewey Decimal Classification number used for subject access.
2021-06-09 (Added editorial note [GH55])
Any entry from the Classification Schemes vocabulary at ID may be used; all have been defined as a ont:Classification
System of coding and organizing materials according to their subject.
Library of Congress Classification number used for subject access.
National Library of Medicine Classification number used for subject access
Universal Decimal Classification number used for subject access.
Identifier for scientific and technical periodical titles assigned by the International CODEN Section of Chemical Abstracts Service.
Aggregation of resources, generally gathered together artificially.
Categorization reflecting the fundamental form of communication in which the content is expressed and the human sense through which it is intended to be perceived.
Identifier assigned to a copyright registration or legal deposit.
Data encoded in a defined structure. Includes numeric data, environmental data,etc., used by applications software to calculate averages, correlations, etc., or to produce models, etc., but not normally displayed in its raw form.
Identifier assigned to a thesis or dissertation for identification purposes .
Information relating to distribution of a resource.
Information about the agent or place relating to the publication, printing, distribution, issue, release, or production of a resource.
Resource that is intended for manipulation by a computer, accessed either directly or remotely.
Speed at which streaming audio, video, etc., is designed to play, e.g., 32 kbps.
Schema, standard, etc., used to encode the digital content of a resource, e.g., MP3, XML, JPEG.
Numbering or other enumeration associated with issues or items held.
Two or more persons related by birth, marriage, adoption, civil union, or similar legal status, or who otherwise present themselves as a family.
Entity having a role in a resource, such as a person or organization.
Number of bytes in a digital file, e.g., 162 KB.
General type of data content encoded in a computer file, e.g., text file, audio file.
Identifier that is used to assist in the identification of antiquarian books by recording information comprising groups of characters taken from specified positions on specified pages of the book.
Form category or genre to which a resource belongs.
Groove width of an analog disc or the groove pitch of an analog cylinder, e.g., coarse groove, microgroove
14 digit number assigned to identify trade items as various packaging levels. GTIN-14 encompasses EAN/UCC-128 and ITF-14.
Unique and persistent identifier for digital objects developed by the Corporation for National Research Initiatives.
2023-11-30 (moved to Basic Model Class [GH108])
An abstract resource that functions as a bridge between two Works.
Resource that is added to or changed by updates that do not remain discrete but are integrated into the whole.
Information that identifies the specific intended or target audience or intellectual level for which the content described is considered appropriate. Also used to record interest and motivation levels and special learner characteristics.
International Standard Audiovisual Number.
International Standard Name Identifier, a unique, persistent reference number for the identities of contributors to creative works.
International Organization for Standardization standard number.
International Standard Serial Number that links together various media versions of a continuing resource.
International Standard Text Code, a numbering system developed to enable the unique identification of textual works.
International Standard Musical Work Code, a unique, persistent reference number for the identification of musical works.
Legal or political unit administering a geographic area.
Unique title for a continuing resource that is assigned by the ISSN International Center in conjunction with an ISSN.
Resource that contains a mixture of various components issued as a unit and intended primarily for instructional purposes.
Resource comprised of multiple types which is not driven by software. For instance, an archival collection of text, photographs and sound recordings.
Identification number assigned by the Library of Congress to works acquired through one of its collaborative overseas acquisition programs.
Library of Congress Control Number that identifies a resource description.
Identifier established locally and not a standard number.
Information relating to manufacture of a resource.
Resource which is written in handwriting or typescript. These are generally unique resources.
Matrix identifier assigned to the master from which a specific sound recording was pressed.
Categorization reflecting the general type of intermediation device required to view, play, run, etc., the content of a resource.
Gathering of individuals or representatives of various bodies for the purpose of discussing and/or acting on topics of common interest.
Resource that contains microimages, either transparent or opaque, that may be reproductions of existing textual or graphic materials or may be original publications.
Information relating to modification of a resource.
Resource that is issued as a single physical unit or intangible single logical unit.
Physical material or object used for the support or backing to which the base material of a resource has been attached.
Information on the symbol system used to convey the content of a movement resource.
Information on the alphabet, script, or symbol system used to convey the content of the resource, including specialized scripts, typefaces, tactile notation, movement notation, and musical notation.
Images intended to be perceived as moving, including motion pictures (using liveaction and/or animation), video recordings of performances, events,etc.
Electronic resource which is a computer program or consists of multiple media types that are software driven, such as videogames.
Music resource expressed in an audible form.
Resources expressed in an audible form, including music or other sounds.
Identifier appearing on a resource assigned by a distributor to a specific audio recording, notated music publication, music-related publication, or videorecording.
2021-06-09 (Changed subclass to Ensemble [GH56])
Ensemble for which a musical work is appropriate.
Information on the symbol system used to convey the content of a music resource.
Identifiers assigned by a music publisher or printer to the printing plates for the notated portion of a notated music publication, or an identifier that emulates the printing plate tradition in contemporary publications.
Identifier assigned to a notated music publication other than an issue, matrix, or plate number.
National Bibliography Number that identifies a resource description.
Resource expressed in an audible form, including spoken word and other non-musical sounds.
Graphic, non-realized representations of movement intended to be perceived visually, e.g. dance.
Graphic, non-realized representations of musical works intended to be perceived visually.
Resource in a form intended to be perceived visually in three-dimensions. Includes man-made objects such as models, sculptures, clothing, and toys, as well as naturally occurring objects such as specimens mounted for viewing.
Number of objects in encoded geospatial information in a cartographic resource.
Corporation or group of persons and/or organizations that acts, or may act, as a unit.
Title in another language and/or script.
Individual or identity established by an individual (either alone or in collaboration with one or more other individuals).
Configuration/number of sound channels used to make a recording, such as one channel for a monophonic recording, e.g., mono, stereo, quadraphonic, surround.
Equalization system, noise reduction system, etc., used in making an audio recording, e.g., CCIR standard, CX encoded, Dolby.
Speed at which an audio carrier must be operated to produce the sound intended, e.g., 78 rpm, 19 cm/s.
Number assigned to a publication for which the specified postal service permits the use of a special mailing class privilege.
Format used in the production of a projected image, e.g., Cinerama, IMAX.
Technical specification relating to the projection of a motion picture film.
Contribution for which the agent is the name chosen as the name part of the name and title access point.
Agent and role with respect to the resource being described.
Information relating to production of a resource.
Speed at which a projected carrier must be operated to produce the moving image intended, e.g., 20 fps.
Information relating to publication of a resource.
Number assigned by a publisher that is not one of the specific defined types.
Type of medium used to record sound on an audio carrier, e.g., magnetic, optical.
Method used to encode audio content for playback, e.g., analog, digital.
Identification of the region of the world for which a videodisc has been encoded, e.g., region 4.
Identification number of a technical report that is not a Standard Technical Report Number.
Clarity or fineness of detail in a digital image, expressed by the measurement of the image in pixels, etc., e.g., 3.1 megapixels.
Policy of holding institution for retaining resource.
Information on the script, or symbol system used to convey the content of a text resource.
Resource that is issued in successive parts, usually numbered, that has no predetermined conclusion.
Resource with a collective title that applies to a group of separate resources, each of which also has its own title.
Shelf mark based on Dewey Decimal Classification.
Piece/item identifier, such as a call or other type of number.
Shelf mark based on Library of Congress Classification.
Shelf mark based on National Library of Medicine Classification.
Shelf mark based on Universal Decimal Classification.
Serial Item and Contribution Identifier.
Resource from which value or label came or was derived.
Resource expressed through line, shape, shading, etc., intended to be perceived visually as a still image or images in two dimensions. Includes two-dimensional images and slides and transparencies.
Identification number used for stock purposes and assigned by agencies such as distributors, publishers, or vendors.
Identification number for a computer data file.
Resource that is intended to be perceived by touch.
Information on the symbol system used to convey the content of a tactile resource.
Number of tracks on an audiotape, e.g., 12 track.
Resource intended to be perceived visually and understood through the use of language in written or spoken form.
Configuration of the audio track on a sound-track film, e.g., center track, edge track.
Title transliterated from one script to another.
2021-06-09 (Corrected definition [GH51])
Usage limitations placed on a resource with respect to reproduction, publication, exhibition, etc..
Standard, etc., used to encode the analog video content of a resource, e.g., Beta, 8mm.
2017-02-03 (Corrected case in class name)
Number assigned by a publisher to a video recording.
2017-02-06 (Changed from data to object property, slight change to definition)
Conditions under which the publisher, distributor, etc., will normally supply a resource, e.g., price of a resource.
Metadata about the metadata, especially provenance information.
Relates an Administrative metadata resource to the resource it captures information about.
Entity associated with a resource or element of description, such as the name of the entity responsible for the content or of the publication, printing, distribution, issue, release or production of a resource.
Property relating an agent, such as an entity responsible for the content or of the publication, printing, distribution, issue, release or production, to another resource.
Suggested use - With Work, Instance or Item
2021-06-09 (Broadened range [GH24], Broadened domain, Made subproperty of material [GH26])
Resource uses, is composed of, integrates, etc. the related material.
Relates a Material resource to that which it is the applied material of.
System for identifying the location of a celestial object in the sky covered by the cartographic content of a resource using the angles of right ascension and declination.
Content that represents the whole or part of the earth, any celestial body, or imaginary place at any scale.
Proportional relationship between an image's width and its height.
2021-06-09 (Broaden domain [GH60], Broadened range [GH63])
Entity that assigned the metadata, such as the entity that assigned a classification number, entity that assigned a name, entity that assigned an identifier.
See also the ARM Ontology for strategies to model this information in greater detail.
Information on awards associated with the described resource.
Relates a Material resource to that which it is the base material of.
A method used to bind a published or unpublished resource,or other binding information.
Result of folding a printed sheet to form a gathering of leaves.
Information about place and date associated with the capture (e.g., recording, filming) of the content of a resource.
Information about place and date associated with the capture (i.e., recording, filming, etc.) of the content of a resource.
Cartographic data that identifies characteristics of the resource, such as coordinates, projection, etc.
Date or date and time on which the metadata was modified.
Date designation associated with a resource or element of description, such as date of title variation; year a degree was awarded; date associated with the publication, printing, distribution, issue, release or production of a resource. May be date typed.
Classification number (single class number or beginning number of a span) that indicates the subject by applying a formal system of coding and organizing resources.
String of characters that serves as a code representing information.
Information about the organization and arrangement of a collection of resources.
Information about the organization and arrangement of a collection of items. For instance, for computer files, organization and arrangement information may be the file structure and sort sequence of a file; for visual materials, this information may be how a collection is arranged.
Relates an Arrangement resource to that which it describes.
Organization and arrangement of Collection
Manner in which the resource is divided into smaller units.
Color characteristics, e.g., black and white, multicolored.
Color characteristics of a resource, e.g., black and white, multicolored, etc.
2017-02-03 (changed from data to object property)
Information that assists those with a sensory impairment for greater understanding of content, e.g., captions.
Agent and its role in relation to the resource.
Suggested value - Work, Instance or Item
Relates a contribution resource, which associates an Agent and Role together, to the relevant resource.
Mathematical system for identifying the area covered by the cartographic content of a resource, expressed either by means of longitude and latitude on the surface of planets or by the angles of right ascension and declination for celestial cartographic content.
Date associated with a claim of protection under copyright or a similar regime.
Copyright and Legal Deposit registration information
Copyright or Legal Deposit registration information
Number associated with a measure of units, such as the number of units and/or subunits making up a resource.
Date or date and time on which the original metadata first created.
Information in note form of credits for persons or organizations who have participated in the creation and/or production of the resource.
Information about the provenance, such as origin, ownership and custodial history (chain of custody), of a resource.
Resource that is a data source to which the described resource is related. It may contain information about other files, printed sources, or collection procedures.
Any relationship between Work, Instance, Item, and Event resources.
Degree for which author was a candidate.
Information about a work presented as part of the formal requirements for an academic degree.
Link to the metadata that was the source of the data.
Indication of specific types of reviews that have been carried out on the description information.
Rules used for the descriptive content of the resource description.
Designation of the descriptive content of the metadata.
Measurements of the carrier or carriers and/or the container of a resource.
Work presented as part of the formal requirements for an academic degree.
Information about the playing time, running time, etc. of a resource.
Edition of the classification scheme, such as full, abridged or a number, when a classification scheme designates editions.
Enumeration of the edition; usually transcribed.
Information identifying the edition or version of the resource and associated statements of responsibility for the edition; usually transcribed.
Electronic location from which the resource is available.
Suspension of light-sensitive chemicals used as a coating on a microfilm or microfiche, e.g., silver halide.
2021-06-09 (Changed domain [GH56], Modified definition [GH56])
Specific type of ensemble, such as orchestra, band, guitar ensemble.
Numbering and dates of issues or items held.
One of two points of intersection of the ecliptic and the celestial equator, occupied by the sun when its declination is 0 degrees.
Coordinate pairs that identify the closed non-intersecting boundary of the area contained within the G-polygon outer ring that is excluded.
Number and type of units and/or subunits making up a resource.
Beginning date of a resource and/or the sequential designations.
Size of the type used to represent the characters and symbols in a resource.
Intervals at which the parts of a serially produced resource or the updates to an integrating resource are issued.
Information about intervals at which the parts of a serially produced resource or the updates to an integrating resource are issued.
Relationship between an original carrier and the carrier of a reproduction made from the original.
Date of conversion of the metadata from another format.
Indication of the program or process used to generate the description by application of a particular transformation.
2017-02-06 (Changed from data to object property)
Geographic coverage of the content of the resource.
Entity holding the item or from which it is available.
Hierarchical position of the described materials relative to other material from the same source.
Information about the history of a Work.
Information about content intended to illustrate a resource.
Information about the circumstances, e.g., source, date, method, under which the resource was directly acquired.
Instrument for which a musical Work is appropriate.
Specific role of instrument, such as alternate, doubling, solo, ensemble.
Information that identifies the specific audience or intellectual level for which the content of the resource is considered appropriate.
Categorization reflecting whether a resource is issued in one or more parts, the way it is updated, and its intended termination.
Information about whether a resource is issued in one or more parts, the way it is updated, and its intended termination.
2021-06-09 (Broadened range [GH62], Broadened domain [GH62])
Resource that is issued on the same carrier as the resource being described.
Resource that adds to or is issued with the described resource.
Number attached to a classification string that indicates a particular item.
Language associated with a resource or its parts.
Ending date of a resource and/or the sequential designations.
Arrangement of text, images, tactile notation, etc., in a resource.
Date of legal work, or promulgation of a law, or signing of a treaty.
Title being addressed. Possible title component.
Title information relating to a resource: work title, preferred title, instance title, transcribed title, translated title, variant form of title, etc.
Layout for content of a resource that is presented in the form of musical notation, such as full score, condensed score, vocal score, etc.
Layout for content of a resource that is presented in the form of musical notation.
Instrumental, vocal, and/or other medium of performance for which a musical resource was originally conceived, written or performed.
Summary statement of the medium for a musical work.
Numeric designation of a musical work assigned by a composer, publisher, or a musicologist.
Numeric designation for musical works consecutively numbered in music reference sources.
Numeric designation for a musical work as found in a thematic index for the composer.
Characterization that epitomizes the primary content of a resource, e.g., field recording of birdsong; combined time series analysis and graph plotting system.
Alphabet, script, or symbol system used to convey the content of the resource, including specialized scripts, typefaces, tactile notation, movement notation, and musical notation.
General textual information relating to a resource, such as Information about a specific copy of a resource or information about a particular attribute of a resource.
2021-06-09 (Added editorial note [GH35])
Any entry from the Note Types vocabulary at ID may be used; all have been defined as a ont:Note
Information, usually in textual form, on attributes of a resource or some aspect of a resource.
Relates a Note resource to the resource to which the note pertains.
2021-06-09 (Better align definition with property name [GH50])
Date or date range associated with the creation of a Work.
2021-06-09 (Better align definition with property name [GH50], Broadened range [GH19])
Place from which the creation of the resource originated.
Geographic location or place entity associated with a resource or element of description, such as the place associated with the publication, printing, distribution, issue, release or production of a resource, place of an event.
2021-06-09 (Change subproperty to relatedTo [GH61])
Resource has other available editions, for example simultaneously published language editions or reprints.
Resource that is manifested in another physical carrier.
Resource embodies the same content as the described resource.
Coordinate pairs that identify the closed non-intersecting boundary of the area covered.
Part of a resource to which information applies.
Part or section name of a title. Possible title component.
Part or section enumeration of a title. Possible title component.
Pattern of arrangement of materials within a unit.
Location in the holding agency where the item is shelved or stored.
Relationship of the colors and tones in an image to the colors and tones of the object reproduced.
Citation to the resource preferred by its custodian of the resource.
Method or system used to represent the surface of the earth or of a celestial sphere on a plane.
2017-02-03 (fixed typo in property name)
2017-02-03 (revised label and slightly revised definition)
Place, name, and/or date information relating to the publication, printing, distribution, issue, release, production, etc. of a resource.
Statement relating to providers of a resource; usually transcribed.
Relates a resource to a publication frequency resource to capture such details as first issue, last issue, status, etc.
Information about the publication frequency of a resource.
Qualifier of information, such as an addition to a title to make it unique or qualifying information associated with an identifier.
Size of a micro-image in relation to the original from which it was produced.
Relief term specified on a cartographic resource
Statement relating to any persons, families, or corporate bodies responsible for the creation of, or contributing to the content of a resource; usually transcribed.
2017-02-03 (Changed from data to object property, adjusted label and definition)
Function provided by a contributor, e.g., author, illustrator, etc.
Function played or provided by a contributor, e.g., author, illustrator, etc.
Ratio of the dimensions of a form contained or embodied in a resource to the dimensions of the entity it represents, e.g., for images or cartographic resources.
Designates whether the classification number is from the standard or optional part of a schedule or table.
Series enumeration of the resource; usually transcribed.
Statement of the series the resource is in; usually transcribed; includes the ISSN if applicable.
Piece identifier, such as a call or other type of number.
Indication of whether the production of sound is an integral part of the resource.
Resource from which value or label came or was derived, such as the formal source/scheme from which a classification number is taken or derived, list from which an agent name is taken or derived, source within which an identifier is unique.
Ending number of classification number span.
Designation of the validity or position of something, such as indication that the classification number is canceled or invalid, circulation availability of an item, indication of whether the identifier is canceled or invalid.
Designation of the validity or position of something, e.g., whether something is incorrect or available.
Suggested use - With Work, Instance, Item or Event
Suggested value - Work, Instance, Item or Event
Relates a subject to that which it describes.
Specific place within the holding entity where the item is located or made available.
Subseries enumeration of the resource; usually transcribed.
Statement of the subseries the resource is in; usually transcribed; includes the ISSN if applicable.
Word, character, or group of words and/or characters that contains the remainder of the title after the main title. Possible title component.
Summary or abstract of the resource described.
Description of the content of a resource, such as an abstract, summary, etc..
Material such as an index, bibliography, appendix intended to supplement the primary content of a resource.
Index, bibliography, appendix, etc. intended to supplement the primary content of a resource.
2017-02-06 (Changed from data to object property, changed property name from plural to singular)
Equipment or system requirement beyond what is normal and obvious for the type of carrier or type of file, such as make and model of equipment or hardware, operating system, amount of memory, programming language, other necessary software, any plug-ins or peripherals required to play, view, or run the resource, etc.
Equipment or system requirements beyond what is normal and obvious for the type of carrier or type of file, such as make and model of equipment or hardware, operating system, amount of memory, programming language, other necessary software, any plug-ins or peripherals required to play, view, or run the resource, etc.
Number of the table from which the classification number in a subdivision entry is taken, e.g., a DDC table.
Table of contents of the described resource.
Sequence number or other identifier for an internal classification sub arrangement or add in a classification scheme.
Time period coverage of the content of the resource.
Relates a title resource to that which it is the title of.
Units in which a value is expressed, such as the physical or logical constituent of a resource (e.g., a volume, audiocassette, film reel, a map, a digital file).
The date or date range during which the resource is accurate.
Type of title variation, e.g., acronym, cover, spine, earlier, later, series version.
Term or terms that identify works such as arranged for music, vulgate for religious work, etc.
Voice for which a musical work is appropriate, such as soprano, tenor, mixed.
Voice for which a musical work is appropriate.
Specific type of voice group, such as chorus, solo.
2016-04-29 (added inverse, updated range)
Resource that has been incorporated into another resource.
Resource that precedes the resource being described, e.g., is earlier in time or before in narrative.
Resource that incorporates another resource.
Resource that succeeds the resource being described, e.g., later in time or after in a narrative.
Relates one resource to another of which it is an arrangement of the first.
Relates an arrangement to the resource of which it is an arrangement.
Resource whose content continues an earlier resource under a new title.
Resource that is continued by the content of a later resource under a new title.
Resource part of whose content separated from an earlier resource to form a new resource.
Resource that spun off a part of its content to form a new resource.
Resource that split into two or more separate resources with new titles.
One of two or more resources resulting from the division of an earlier resource into separate resources.
Work whose content is the described event.
Something that happens at a certain time and location, such as a performance, speech, or athletic event.
Event that is the content of the described work.
2023-11-30 (Modified domain/range to support Hub [GH110])
Work or Hub that the described Work or Hub is an expression of. Use to connect Works and/or Hubs under LRM/RDA guidelines or similar implementations.
Work or Hub that is an expression of a described Work or Hub. Use to relate Works and/or Hubs under LRM/RDA guidelines or similar implementations.
Relationship for archival, visual, and manuscript resources to a finding aid or similar control materials.
Resource that accompanies the described resource.
Finding aid or similar control materials for archival, visual, and manuscript resources.
Instance is related to described Work. For use to connect Works to Instances in the BIBFRAME structure.
Work the Instance described instantiates or manifests. For use to connect Instances to Works in the BIBFRAME structure.
2017-02-07 (slight revision of definition)
Item which is an example of the described Instance.
Instance for which the described Item is an example.
Resource that reproduces another Resource.
Resource that is a reproduction of another Resource.
Resource in which the part has been issued; the title of the larger resource appears on the part.
Resource in which the described resource is physically or logically contained.
Resource that is a part of a larger resource.
series resource that is part of another series.
Series resource of which the described resource is a part.
Character string associated with a resource that serves to differentiate that resource from other resources, i.e., that uniquely identifies an entity.
Resource that is associated with a character string that serves to differentiate one resource from another.
One of two or more resources that come together to form a new resource.
One of two or more resources which came together to form a new resource.
Resource is the original version of which this resource is a reproduction.
Source work from which the described resource is derived.
Resource that is a modification of the described work.
Resource that references the described resource
Resource that is referenced by the described resource.
Later resource used in place of an earlier resource, usually because the later resource contains updated or new information.
Earlier resource whose content has been replaced by a later resource, usually because the later resource contains updated or new information.
Resource that is included either physically or logically in the described resource
Resource that updates or otherwise complements the predominant resource.
Resource that is updated or otherwise complemented by the augmenting resource.
Resource that translates the text of the source entity into a language different from that of the original.
Resource that has been translated, i.e., the text is expressed in a language different from that of the original resource.
United States, Library of Congress, Network Development and MARC Standards Office
A SHACL Shapes Validator for The Profiles Vocabulary's RDF vocabulary
Instances of prof:Profile must not also be instances of prof:ResourceDescriptor.
Profile Disjoint From Resource Descriptor Shape
Instances of prof:ResourceDescriptor must not also be instances of prof:Profile.
Resource Descriptor Disjoint From Profile Shape
Resource Descriptor Exactly One ArtifactShape
Each prof:ResourceDescriptor must have exactly one prof:hasArtifact value.
Resource Descriptor exactly 1 hasArtifact
Each prof:ResourceDescriptor must have exactly one prof:hasRole value.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/6fd39a33-9c4f-469e-80a5-e76b5d5f04a6>`. `<https://linked.data.gov.au/def/nrm/6fd39a33-9c4f-469e-80a5-e76b5d5f04a6>` is the IRI for "Opportune Module".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/6fd39a33-9c4f-469e-80a5-e76b5d5f04a6`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/65f4cb64-a0c0-4a41-a9b9-d2f42affebc5>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/65f4cb64-a0c0-4a41-a9b9-d2f42affebc5> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/65f4cb64-a0c0-4a41-a9b9-d2f42affebc5>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/65f4cb64-a0c0-4a41-a9b9-d2f42affebc5> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/65f4cb64-a0c0-4a41-a9b9-d2f42affebc5>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5ccfd7ed-12e4-42ed-83a1-1b85445f92d6>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Animal pouch conditions controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Animal pouch conditions controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/5ccfd7ed-12e4-42ed-83a1-1b85445f92d6> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'4fab0c1c-c127-474e-8f5e-4afe45fec0ed'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/5ccfd7ed-12e4-42ed-83a1-1b85445f92d6> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5ccfd7ed-12e4-42ed-83a1-1b85445f92d6>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5ccfd7ed-12e4-42ed-83a1-1b85445f92d6>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/4fab0c1c-c127-474e-8f5e-4afe45fec0ed>`. `<https://linked.data.gov.au/def/nrm/4fab0c1c-c127-474e-8f5e-4afe45fec0ed>` is the IRI for "Animal pouch conditions".
The value of `tern:vocabulary` _MUST_ match the pattern `4fab0c1c-c127-474e-8f5e-4afe45fec0ed$`.
TERN's ecologists have determined the feature type is _animal individual_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/ecb855ed-50e1-4299-8491-861759ef40b7[`animal individual`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/d78e0ad6-9ac8-4adc-a796-61ad458726b3>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
Result value's unit of measure _MUST_ have the value `unit:KiloGM`.
The result _MUST_ have `unit:KiloGM` as the value for `tern:unit`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/d78e0ad6-9ac8-4adc-a796-61ad458726b3> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/d78e0ad6-9ac8-4adc-a796-61ad458726b3>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/d78e0ad6-9ac8-4adc-a796-61ad458726b3>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/d8ed3241-8d97-4a63-be3a-5f610a4b8739>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Breeding statuses controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Breeding statuses controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/d8ed3241-8d97-4a63-be3a-5f610a4b8739> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'b7dc10d2-c0aa-46b3-94da-685cd0a723e4'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/d8ed3241-8d97-4a63-be3a-5f610a4b8739> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/d8ed3241-8d97-4a63-be3a-5f610a4b8739>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/d8ed3241-8d97-4a63-be3a-5f610a4b8739>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/b7dc10d2-c0aa-46b3-94da-685cd0a723e4>`. `<https://linked.data.gov.au/def/nrm/b7dc10d2-c0aa-46b3-94da-685cd0a723e4>` is the IRI for "Breeding statuses".
The value of `tern:vocabulary` _MUST_ match the pattern `b7dc10d2-c0aa-46b3-94da-685cd0a723e4$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/aad13f8f-230a-516e-ad91-f3508d7c01d1>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/aad13f8f-230a-516e-ad91-f3508d7c01d1> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/aad13f8f-230a-516e-ad91-f3508d7c01d1>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 1 and 100 exclusive.
The result _MUST_ have a value between 1 and 100 exclusively.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/aad13f8f-230a-516e-ad91-f3508d7c01d1>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/13d9b6a3-f600-50ee-a8a7-f31b5b27abff>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Clinical scoring - rump controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Clinical scoring - rump controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/13d9b6a3-f600-50ee-a8a7-f31b5b27abff> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'8799d474-09eb-5112-aa9d-87710cd1661c'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/13d9b6a3-f600-50ee-a8a7-f31b5b27abff> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/13d9b6a3-f600-50ee-a8a7-f31b5b27abff>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/13d9b6a3-f600-50ee-a8a7-f31b5b27abff>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/8799d474-09eb-5112-aa9d-87710cd1661c>`. `<https://linked.data.gov.au/def/nrm/8799d474-09eb-5112-aa9d-87710cd1661c>` is the IRI for "Clinical scoring - rump".
The value of `tern:vocabulary` _MUST_ match the pattern `8799d474-09eb-5112-aa9d-87710cd1661c$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/010ee3c8-bfbe-47c5-adc8-068ca664173d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Fauna specimen conditions controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Fauna specimen conditions controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/010ee3c8-bfbe-47c5-adc8-068ca664173d> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'f0647b85-a014-4299-b23f-6aeb25e834bc'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/010ee3c8-bfbe-47c5-adc8-068ca664173d> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/010ee3c8-bfbe-47c5-adc8-068ca664173d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/010ee3c8-bfbe-47c5-adc8-068ca664173d>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/f0647b85-a014-4299-b23f-6aeb25e834bc>`. `<https://linked.data.gov.au/def/nrm/f0647b85-a014-4299-b23f-6aeb25e834bc>` is the IRI for "Fauna specimen conditions".
The value of `tern:vocabulary` _MUST_ match the pattern `f0647b85-a014-4299-b23f-6aeb25e834bc$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a46d4478-4512-5a91-a4c9-a8f7720b38ed>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
Result value's unit of measure _MUST_ have the value `unit:MilliM`.
The result _MUST_ have `unit:MilliM` as the value for `tern:unit`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/a46d4478-4512-5a91-a4c9-a8f7720b38ed> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a46d4478-4512-5a91-a4c9-a8f7720b38ed>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 1 and 500 exclusive.
The result _MUST_ have a value between 1 and 500 exclusively.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a46d4478-4512-5a91-a4c9-a8f7720b38ed>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ac5a20c2-64f7-5335-b080-a6aacb92e5d8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/ac5a20c2-64f7-5335-b080-a6aacb92e5d8> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ac5a20c2-64f7-5335-b080-a6aacb92e5d8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ac5a20c2-64f7-5335-b080-a6aacb92e5d8>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/59df7c05-1521-4161-86e4-8e6a8feb4002>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Age classes controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Age classes controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/59df7c05-1521-4161-86e4-8e6a8feb4002> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'0e2641c3-0d7e-4d94-8cd7-02c21d564630'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/59df7c05-1521-4161-86e4-8e6a8feb4002> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/59df7c05-1521-4161-86e4-8e6a8feb4002>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/59df7c05-1521-4161-86e4-8e6a8feb4002>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/0e2641c3-0d7e-4d94-8cd7-02c21d564630>`. `<https://linked.data.gov.au/def/nrm/0e2641c3-0d7e-4d94-8cd7-02c21d564630>` is the IRI for "Age classes".
The value of `tern:vocabulary` _MUST_ match the pattern `0e2641c3-0d7e-4d94-8cd7-02c21d564630$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/2ad2e5ec-ec5c-4541-a98c-85278e93ad67>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Female teat conditions controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Female teat conditions controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/2ad2e5ec-ec5c-4541-a98c-85278e93ad67> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'d2665d51-db1d-48ad-a80d-48593d280b76'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/2ad2e5ec-ec5c-4541-a98c-85278e93ad67> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/2ad2e5ec-ec5c-4541-a98c-85278e93ad67>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/2ad2e5ec-ec5c-4541-a98c-85278e93ad67>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/d2665d51-db1d-48ad-a80d-48593d280b76>`. `<https://linked.data.gov.au/def/nrm/d2665d51-db1d-48ad-a80d-48593d280b76>` is the IRI for "Female teat conditions".
The value of `tern:vocabulary` _MUST_ match the pattern `d2665d51-db1d-48ad-a80d-48593d280b76$`.
TERN's ecologists have determined the feature type is either _plant occurrence_ or _animal occurrence_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link:http://linked.data.gov.au/def/tern-cv/b311c0d3-4a1a-4932-a39c-f5cdc1afa611[`plant occurrence`] or link:http://linked.data.gov.au/def/tern-cv/2361dea8-598c-4b6f-a641-2b98ff199e9e[`animal occurrence`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/d964ff76-9a75-5a12-87c2-a355545ca107>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/d964ff76-9a75-5a12-87c2-a355545ca107> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/d964ff76-9a75-5a12-87c2-a355545ca107>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/d964ff76-9a75-5a12-87c2-a355545ca107>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
TERN's ecologists have determined the feature type is _plant occurrence_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/b311c0d3-4a1a-4932-a39c-f5cdc1afa611[`plant occurrence`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/413a99e5-b31e-5011-8479-74b6297290bc>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/413a99e5-b31e-5011-8479-74b6297290bc> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/413a99e5-b31e-5011-8479-74b6297290bc>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/413a99e5-b31e-5011-8479-74b6297290bc>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/96ccc2b7-7b7f-4e5c-b11f-d5e5c88e245a>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/96ccc2b7-7b7f-4e5c-b11f-d5e5c88e245a> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/96ccc2b7-7b7f-4e5c-b11f-d5e5c88e245a>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/96ccc2b7-7b7f-4e5c-b11f-d5e5c88e245a>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/13aba314-0f3e-5bf4-8e81-0ffb2ca71fdf>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/13aba314-0f3e-5bf4-8e81-0ffb2ca71fdf> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/13aba314-0f3e-5bf4-8e81-0ffb2ca71fdf>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/13aba314-0f3e-5bf4-8e81-0ffb2ca71fdf>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3996d3ba-0812-55a4-9b27-4498ffb75e52>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3996d3ba-0812-55a4-9b27-4498ffb75e52> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3996d3ba-0812-55a4-9b27-4498ffb75e52>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3996d3ba-0812-55a4-9b27-4498ffb75e52>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/18f067e6-cf1c-4ee2-bdc9-291dc6133e13>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/18f067e6-cf1c-4ee2-bdc9-291dc6133e13> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/18f067e6-cf1c-4ee2-bdc9-291dc6133e13>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/18f067e6-cf1c-4ee2-bdc9-291dc6133e13> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/18f067e6-cf1c-4ee2-bdc9-291dc6133e13>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0c87c594-0002-479f-8a4b-6f63743065b8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the fauna testes positions controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the fauna testes positions controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0c87c594-0002-479f-8a4b-6f63743065b8> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'6a46703e-dbc3-440e-b06f-217c400a18b5'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0c87c594-0002-479f-8a4b-6f63743065b8> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0c87c594-0002-479f-8a4b-6f63743065b8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0c87c594-0002-479f-8a4b-6f63743065b8>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/6a46703e-dbc3-440e-b06f-217c400a18b5>`. `<https://linked.data.gov.au/def/nrm/6a46703e-dbc3-440e-b06f-217c400a18b5>` is the IRI for "fauna testes positions".
The value of `tern:vocabulary` _MUST_ match the pattern `6a46703e-dbc3-440e-b06f-217c400a18b5$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/88353d7b-8a2c-4b84-b034-71395f4edb93>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/88353d7b-8a2c-4b84-b034-71395f4edb93> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/88353d7b-8a2c-4b84-b034-71395f4edb93>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/88353d7b-8a2c-4b84-b034-71395f4edb93> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/88353d7b-8a2c-4b84-b034-71395f4edb93>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/40b39732-e10b-4c4e-968b-3404663a094d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Animal sexes controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Animal sexes controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/40b39732-e10b-4c4e-968b-3404663a094d> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'fcc3a1e1-3e35-4a4f-bd44-eface035025c'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/40b39732-e10b-4c4e-968b-3404663a094d> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/40b39732-e10b-4c4e-968b-3404663a094d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/40b39732-e10b-4c4e-968b-3404663a094d>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/fcc3a1e1-3e35-4a4f-bd44-eface035025c>`. `<https://linked.data.gov.au/def/nrm/fcc3a1e1-3e35-4a4f-bd44-eface035025c>` is the IRI for "Animal sexes".
The value of `tern:vocabulary` _MUST_ match the pattern `fcc3a1e1-3e35-4a4f-bd44-eface035025c$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/982ccdc7-5458-59b3-ab74-bac88eba95a8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/982ccdc7-5458-59b3-ab74-bac88eba95a8> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/982ccdc7-5458-59b3-ab74-bac88eba95a8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/982ccdc7-5458-59b3-ab74-bac88eba95a8>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6c9c53c2-3a6b-5ab1-93c6-198c853cdf49>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/6c9c53c2-3a6b-5ab1-93c6-198c853cdf49> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6c9c53c2-3a6b-5ab1-93c6-198c853cdf49>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6c9c53c2-3a6b-5ab1-93c6-198c853cdf49>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dfe2c0ec-dc72-5d75-97eb-1485040bbcfd>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/dfe2c0ec-dc72-5d75-97eb-1485040bbcfd> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dfe2c0ec-dc72-5d75-97eb-1485040bbcfd>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dfe2c0ec-dc72-5d75-97eb-1485040bbcfd>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/4b799bed-135c-505a-9476-ba3b92f6dfc8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/4b799bed-135c-505a-9476-ba3b92f6dfc8> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/4b799bed-135c-505a-9476-ba3b92f6dfc8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 1 and 200 exclusive.
The result _MUST_ have a value between 1 and 200 exclusively.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/4b799bed-135c-505a-9476-ba3b92f6dfc8>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/38d1419f-7f3b-4d0e-a2f6-4b152e2d91f7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/38d1419f-7f3b-4d0e-a2f6-4b152e2d91f7> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/38d1419f-7f3b-4d0e-a2f6-4b152e2d91f7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/38d1419f-7f3b-4d0e-a2f6-4b152e2d91f7>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0a985940-b8ca-4d90-a5d5-4d1945410006>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0a985940-b8ca-4d90-a5d5-4d1945410006> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0a985940-b8ca-4d90-a5d5-4d1945410006>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0a985940-b8ca-4d90-a5d5-4d1945410006>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/1b3904f4-df8c-49ba-a234-3b406fe11fa9>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Taxa types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Taxa types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/1b3904f4-df8c-49ba-a234-3b406fe11fa9> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'7ea12fed-6b87-4c20-9ab4-600b32ce15ec'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/1b3904f4-df8c-49ba-a234-3b406fe11fa9> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/1b3904f4-df8c-49ba-a234-3b406fe11fa9>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/1b3904f4-df8c-49ba-a234-3b406fe11fa9>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/7ea12fed-6b87-4c20-9ab4-600b32ce15ec>`. `<https://linked.data.gov.au/def/nrm/7ea12fed-6b87-4c20-9ab4-600b32ce15ec>` is the IRI for "Taxa types".
The value of `tern:vocabulary` _MUST_ match the pattern `7ea12fed-6b87-4c20-9ab4-600b32ce15ec$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0e0d9a10-a37d-527b-8b7e-120a4a3685f3>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0e0d9a10-a37d-527b-8b7e-120a4a3685f3> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0e0d9a10-a37d-527b-8b7e-120a4a3685f3>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0e0d9a10-a37d-527b-8b7e-120a4a3685f3>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5448fb0a-6f47-5aa4-9712-84508cbdb277>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/5448fb0a-6f47-5aa4-9712-84508cbdb277> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5448fb0a-6f47-5aa4-9712-84508cbdb277>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5448fb0a-6f47-5aa4-9712-84508cbdb277>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
TERN's ecologists have determined the feature type is _animal specimen_ or _plant specimen_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/2e122e23-881c-43fa-a921-a8745f016ceb[`plant specimen`] or http://linked.data.gov.au/def/tern-cv/cd5cbdbb-07d9-4a5b-9b11-5ab9d6015be6[`animal specimen`].
1.6 2026-04: Align schema:license allowed types with VocPub 1.5 2026-01: allow schema:license to indicate an IRI 1.4 2025-07: Changed to linked.data.gov.au IRI 1.3 2025-07: Alignment to VocPub, Own use of schema.org as much as possible 1.2 2025-06: Added schema:citation to allowed history properties 1.1 2023-05: This validator was updated in July 2023 to conform to itself & dcterms:provenance changed to skos:historyNote
This validator was made to improve teh consistency of Australian ontology formulation, initially by CSIRO and then handed to the AGLDWG
SHACL Shapes to validate RDF data according to the Ontology Publications Profile
Req 2.1.9b, Single history note predicate
Australian Government Linked Data Working Group
Requirement 2.1.10: OWL Ontologies SHOULD indicate a version using the property owl:versionIRI with an IRI object.
Requirement 2.1.11: OWL Ontologies SHOULD indicate any online version controlled source code repository storing the ontology and related content with the schema:codeRepository with a xsd:anyURI object.
Requirement 2.1.12a: OWL Ontologies SHOULD present any licence pertaining to its use using the schema:license predicate preferentially indicating the IRI of a license if in RDF form or a literal URL (datatype xsd:anyURI) if online but not in RDF form. If the licence is expressed in text, a literal text field may be indicated.
Requirement 2.1.12a: OWL Ontologies SHOULD present a license for its use indicated with the schema:license use indicating either the literal text of a license or a URL of a license using the datatype xsd:anyURI or they may link to a Semantic Web version of a license via its IRI.
Requirement 2.1.13: OWL Ontologies MAY present usage information alongside license information using the schema:usageInfo property indicating literal text.
Requirement 2.1.14: OWL Ontologies SHOULD present a copyright information for it indicated with properties schema:copyrightHolder, schema:copyrightNotice and schema:copyrightYear. schema:copyrightHolder may be used with a text object or, preferably, an schema:Person or schema:Organization object.
Ontology copyright info - property shape
Requirement 2.1.15: OWL Ontologies MUST present at least one sh:NodeShape or sh:PropertyShape within the ontology file
Requirement 2.1.16: All sh:NodeShape and sh:PropertyShape instances MUST indicate the ontology that defines then with the rdfs:isDefinedBy property.
Shape's defining ontology - property shape
Requirement 2.1.2: OWL Ontologies MUST be presented as a single owl:Ontology object & Requirement 2.1.3 Each OWL ontology MUST be presented in a single file which does not contain information other than that which is directly part of the ontology and the file is considered the point-of-truth
Requirement 2.1.4: OWL Ontologies MUST have exactly one title, a text literal, indicated using the skos:prefLabel or the schema:name property
Requirement 2.1.5: OWL Ontologies MUST have exactly one definition, a text literal text, indicated using either the skos:definition or schema:description property
Requirement 2.1.6: OWL Ontologies MUST have exactly one created date, exactly one modified date and exactly one issued date indicated using the schema:dateCreated & schema:dateModified properties respectively that must be either an xsd:date, xsd:dateTime or xsd:dateTimeStamp literal values
Requirement 2.1.7: OWL Ontologies MUST have at least one creator, indicated using schema:creator and at least one schema:publisher property that must be IRI values indicating agents, that is instances of schema:Person, schema:Organization or a subclass of either
Requirement 2.1.8: OWL Ontologies MAY have at least any number of contributors, indicated using schema:contributor property that must be a IRI value indicating an agent, that is an instance of schema:Person, schema:Organization or a subclass of either
This is a message about prov:wasDerivedFrom
This is a message about skos:historyNote
Requirement 2.1.9b: OWL Ontologies MUST NOT use skos:historyNote property more than once on any object.
Single history note predicate - property shape
Requirement 2.1.9c: You MUST NOT use schema:citation property more than once on any object.
Single source predicate - property shape
Requirement 2.1.9d: You MUST NOT use prov:wasDerivedFrom property more than once on any object.
Single was derived from predicate - property shape
Requirement 2.1.9e: Whenever schema:citation is used, it must be a datatype property indicating an object of type xsd:anyURI or xsd:string
Source predicate range type - property shape
Requirement 2.1.9f: Whenever skos:historyNote is used, it must be a datatype property indicating an object of type xsd:string or rdf:LangString
History node range type - property shape
Requirement 2.1.9g: Whenever prov:wasDerivedFrom is used, it must be an object property indicating an IRI
Was derived from range type - property shape
Requirement 2.2.1: Ontology elements MUST have at least one name indicated using either the skos:prefLabel or schema:name property that must be either a string or a language-typed text literal value. Only one value per language is allowed if languages are used.
Requirement 2.2.2: Ontology elements MUST have a message value, indicated using sh:message or a description, indicated using schema:description
Requirement 2.2.3: Ontology elements provenance, if different from that of the SHACL ontology being validated, SHOULD be indicated by at least one of the following properties: skos:historyNote, schema:citation or prov:wasDerivedFrom.
Requirement 2.2.4: Each element in an ontology SHOULD have at least one example of use indicated with a skos:example property that should be a text literal, preferably showing RDF source code.
Requirement 2.2.5: Each element in an ontology SHOULD indicate any non-IRI persistent identifiers with schema:identifier properties. Custom datatypes may be implemented for identifiers, in line with the advice for the use of skos:notation.
Requirement 2.7.2: Each agent MUST indicate at exactly one name property with the schema:name property that must be a text literal value
Requirement 2.7.3: Each organisation MUST indicate an schema:url property with a URL value
Requirement 2.7.3: Each person MUST indicate an schema:email property with an email value
Requirement 2.7.4: One agent MAY be affiliated with another using schema.org agent/agent linking properties, such as schema:affiliation between persons and organisations or schema:parentOrganization and similar between organizations.
Version 0.3 removed subclass declarations to classes outside of this ontology in accordance with Recommendation 2.9 of the VoMaG Report http://www.gbif.org/resource/80862
This vocabulary closely follows the structure of the ScientificName complex type that is part of the TDWG standard Taxon Concept Schema. The TCS structure was based on the name structures suggested by the LinneanCore and those found in schemas such as ABCD. It reflects the contributions of many authors over a number of years.
Ontology describing the metadata returned for LSIDs that are used for Taxon Names.
A paralectotype specimen that is the opposite sex of the lectotype. The term is not regulated by the ICZN. [Zoo.]
A kind of nomenclatural type. Nomenclatural types can be of different kinds (or types) to indicate whether they are duplicates, replacements, related specimens etc. Instances of this class describe kinds of nomenclatural types. Equivalent to TCS NomenclaturalTypeStatusOfUnitsEnum
A paraneotype specimen that is the opposite sex of the neotype. The term is not regulated by the ICZN. [Zoo.]
A paratype specimen designated from the type series by the original author that is the opposite sex of the holotype. The term is not regulated by the ICZN. [Zoo.]
Rules that govern the naming of bacteria species
A class for which instances can be defined to create a controlled vocabulary for the nomenclatural codes. Equivalent to TCS NomenclaturalCodesEnum
The current or subject name is the validation of a name that was not fully published before. Covers the use of ex in botanical author strings. ICBN Art. 46.4: e.g. if this name object represents G. tomentosum Nutt. ex Seem. then the pointer should point to G. tomentosum Nutt.
The different types of Nomenclatural Note. An object used to represent the different types of Nomenclatural Note. No direct equivalent in TCS but used to represents different elements of type NomenclaturalNoteType.
The current or subject name is conserved against the name pointed to. ICBN: Conservation is covered under Article 14 and Appendix II and Appendix III (this name is nomina conservanda). ICZN: Conservation is covered under Article 23.9 (this name is nomen protectum and the target name is nomen oblitum)
A deprecated term no longer recognized in the ICZN; formerly used for either syntype or paratype . [Zoo.]
An epitype is a specimen or illustration selected to serve as an interpretative type when any kind of holotype, lectotype, etc. is demonstrably ambiguous and cannot be critically identified for purposes of the precise application of the name of a taxon (see Art. ICBN 9.7, 9.18). An epitype supplements, rather than replaces existing types. [Bot./Bio.]
A strain or cultivation derived from epitype material. Ex-types are not regulated by the botanical or zoological code. [Bot.]
A strain or cultivation derived from holotype material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.]
A strain or cultivation derived from isotype material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.]
A strain or cultivation derived from lectotype material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.]
A strain or cultivation derived from neotype material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.]
A strain or cultivation derived from paratype material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.]
A strain or cultivation derived from some kind of type material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.]
One or more preparations of directly related individuals representing distinct stages in the life cycle, which together form the type in an extant species of protistan [ICZN Article 72.5.4]. A hapantotype, while a series of individuals, is a holotype that must not be restricted by lectotype selection. If an hapantotype is found to contain individuals of more than one species, however, components may be excluded until it contains individuals of only one species [ICZN Article 73.3.2]. [Zoo.]
The one specimen or other element used or designated by the original author at the time of publication of the original description as the nomenclatural type of a species or infraspecific taxon. A holotype may be 'explicit' if it is clearly stated in the originating publication or 'implicit' if it is the single specimen proved to have been in the hands of the originating author when the description was published. [Zoo./Bot./Bio.]
International Code of Botanical Nomenclature
International Code of Zoological Nomenclature
A drawing or photograph (also called 'phototype') of a type specimen. Note: the term "iconotype" is not used in the ICBN, but implicit in, e. g., ICBN Art. 7 and 38. [Zoo./Bot.]
A duplicate of a lectotype, compare lectotype. [Bot.]
A duplicate of a neotype, compare neotype. [Bot.]
A duplicate of a syntype, compare isotype = duplicate of holotype. [Bot.]
An isotype is any duplicate of the holotype (i. e. part of a single gathering made by a collector at one time, from which the holotype was derived); it is always a specimen (ICBN Art. 7). [Bot.]
Current or subject name has the same spelling as target name but was published later and has priority over it (unless conserved or sanctioned). See ICBN: Article 53, ICZN: Chapter 12, Article 52.
A specimen or other element designated subsequent to the publication of the original description from the original material (syntypes or paratypes) to serve as nomenclatural type. Lectotype designation can occur only where no holotype was designated at the time of publication or if it is missing (ICBN Art. 7, ICZN Art. 74). [Zoo./Bot.] -- Note: the BioCode defines lectotype as selection from holotype material in cases where the holotype material contains more than one taxon [Bio.].
A specimen designated as nomenclatural type subsequent to the publication of the original description in cases where the original holotype, lectotype, all paratypes and syntypes are lost or destroyed, or suppressed by the (botanical or zoological) commission on nomenclature. In zoology also called "Standard specimen" or "Representative specimen". [Zoo./Bot./Bio.]
For specimens erroneously labelled as types an explicit negative statement may be desirable. [General]
All of the specimens in the syntype series of a species or infraspecific taxon other than the lectotype itself. Also called "lectoparatype". [Zoo.]
All of the specimens in the syntype series of a species or infraspecific taxon other than the neotype itself. Also called "neoparatype". [Zoo.]
All of the specimens in the type series of a species or infraspecific taxon other than the holotype (and, in botany, isotypes). Paratypes must have been at the disposition of the author at the time when the original description was created and must have been designated and indicated in the publication. Judgment must be exercised on paratype status, for only rarely are specimens explicitly cited as paratypes, but usually as "specimens examined," "other material seen", etc. [Zoo./Bot.]
A copy or cast of holotype material (compare Plastotype).
A copy or cast of isotype material (compare Plastotype).
A copy or cast of lectotype material (compare Plastotype).
A copy or cast of neotype material (compare Plastotype).
A copy or cast of paratype material (compare Plastotype).
A copy or cast of syntype material (compare Plastotype).
A copy or cast of type material, esp. relevant for fossil types. Not regulated by the botanical or zoological code (?). [Zoo./Bot.]
Note concerning the nomenclatural status of the name. e.g. whether it is validly published or not. THIS SHOULD NOT BE USED TO IMPLY WHETHER THE NAME IS CONSIDERED TO REPRESENT AN ACCEPTED TAXON. An accepted taxon can only be represented as a TaxonConcept.
Current or subject name is replacement for target name. Also called 'Nomen Novum' or 'avowed substitute' ICBN: Article 7.3 ICZN: Article 60.3.
With reference to fungi. ICBN: Articles 13.1d and 15. ICZN: No equivalent term for animals
A referred, described, measured or figured specimen in the original publication (including a neo/lectotypification publication) that is not a primary type. [Zoo.]
The current or subject name is a spelling correction of the name that is pointed to.
A referred, described, measured or figured specimen in a revision of a previously described taxon. [Zoo.]
One of the series of specimens used to describe a species or infraspecific taxon when neither a single holotype nor a lectotype has been designated. The syntypes collectively constitute the name-bearing type. [Zoo./Bot.]
One or more specimens collected at the same location as the type series (type locality), regardless of whether they are part of the type series. Topotypes are not regulated by the botanical or zoological code. Also called "locotype". [Zoo./Bot.]
a) A specimen designated or indicated any kind of type of a species or infraspecific taxon. If possible more specific type terms (holotype, syntype, etc.) should be applied. b) the type name of a name of higher rank for taxa above the species rank. [General]
Rules that govern the names of viral species
ScientificName/NameAtomised/Bacterial/AuthorTeamAndYear or ScientificName/NameAtomised/Botanical/AuthorTeam (FIXME: Does this include the AuthorTeamParenthesis?) or [ScientificName/NameAtomised/Zoological/AuthorTeamOriginalAndYear and ScientificName/NameAtomised/Zoological/AuthorTeamParenthesisAndYear and ScientificName/NameAtomised/Zoological/CombinationAuthorTeamAndYear (FIXME: need clarification as to which of these occur))]
Name:AuthorTeamFk -> AuthorTeam::AuthorTeamCache
The full author string used for this name. The full code-appropriate author team string for this name at this rank. Use this property for all names including both original combinations and new combinations of bi and trinomial names (where some of the authors may be in brackets). If the TaxonName instance contains any details about authorship a representation of them should be included in this property.
No equivalent of an author team break down.
Name:AuthorTeamFk and Name:BasAuthorTeamFk
A breakdown of the authors who published this name including both basionym and combination authors (if any).
ScientificName/NameAtomised/Botanical/AuthorTeamParenthesis or ScientificName/NameAtomised/Zoological/AuthorTeamParenthesisAndYear
Name:BasAuthorTeamFk -> AuthorTeam::AuthorTeamCache
A string representing the authors of the basionym of this name. This represents the authors of the basionym. It is the part of authorship that is typically included in brackets. The brackets should be omitted. A year may be included as is common in citing names governed by the ICZN. This property is only used for names that are new combinations.
ScientificName/NameAtomised/Botanical/AuthorTeam (when AuthorTeamParenthesis present?) ScientificName/NameAtomised/Zoological/CombinationAuthorTeamAndYear
Name:AuthorTeamFk -> AuthorTeam::AuthorTeamCache (only when Name:BasAuthorTeamFk is present?)
A string representing the authors of this combination of the name. This represents the authors of the new combination of this name. The authors who come after the brackets in the traditional way of citing botanical names. These authors are not usually cited in zoology though the ICZN recommends that they should be included (Art.51G). A year may be included. See also note under year property. This property is only used for names that are new combinations.
A scientific biological name. An object that represents a single scientific biological name that either is governed by or appears to be governed by one of the biological codes of nomenclature. These are not taxa. Taxa, whether accepted or not, are represented by TaxonConcept objects.
The nomenclatural code under which this note should be interpreted.
A note on a Taxon Name. An object representing a comment or addition to a Taxon Name beyond it's original publication. Equivalent to TCS NomenclaturalNoteType
ScientificName/NameAtomised/Botanical/CultivarGroupName and ScientificName/NameAtomised/Botanical/CultivarName
Name::CultivarGroupName and Name::CultivarName
The cultivar or related name governed by ICNCP. The name of the Cultivar, Cultivar Group, grex, convar or graft chimera under the International Code for the Nomenclature of Cultivated Plants. Only include here the string of the name. i.e. omit the single quotes around cultivar names, the word Group that denotes cultivar group and the + sign used in chimeras. These symbols can be added in later on the basis of the rank of the name. For example the use of the word 'Group' is language dependent.
ScientificName/NameAtomised/*/GenusOrMonomial (but only when representing a genus name)
Genus (though this is used of taxonomic placement in DwC)
The genus part of a bi or trinomial name. The name of the genus for names below the rank of genus. This property should not be used for names at and above the rank of genus. For names at and above genus rank the uninomial property should be used.
RelName, NomStatus and NomStatusRel tables
Association between a name and the notes that it may have. Often notes relate to other names such as replacement names.
ScientificName/NameAtomised/botanical/FirstEpithet (but not in names at rank of species and below) or ScientificName/NameAtomised/Zoological/Subgenus or ScientificName/NameAtomised/Bacterial/Subgenus
The infrageneric part of a binomial name at ranks above species but below genus. Names at ranks between species and genus are composed of two words; the genus and this infrageneric epithet. This property should therefore always be accompanied by the genusPart property. If the infragenericEpithet property is present the uninomial, infraspecificEpithet, specificEpithet and subspecificEpithet properties should be absent.
ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or ScientificName/NameAtomised/Botanical/InfraspecificEpithet or ScientificName/NameAtomised/Zoological/SubSpeciesEpithet
The infraspecific epithet part of a trinomial name below the rank of species. Names at ranks below species are composed of three words; the genus epithet, the specific epithet and an infraspecific epithet. This property should therefore always be accompanied by the genusPart property and a specificEpithet property. If the specificEpithet property is present the uninomial and infragenusPart properties should be absent.
The complete uninomial, binomial or trinomial name without any authority or year components. Every TaxonName should have a DublinCore:title property that contains the complete name string including authors and year (where appropriate).
Indicated by whether bacterial, botanical, zoological or viral name constructs are used.
The nomenclatural code that governs this name. By definition all taxon names are governed by one of the codes of nomenclature. These include ICBN, ICZN, ICNCP and others.
The text of the nomenclatural note. Text describing the nomenclatural event/fact that is represented by this Nomenclatural Note.
The Taxon Name that is the target for this note. The TO side of the note relationship. The Taxon Name that this note refers to.
The nomenclatural code rule considered. The article/note/recommendation in the code in question that is commented on in the note property.
ScientificName/NameAtomised/botanical/FirstEpithet (but not in names above the rank of species) or ScientificName/NameAtomised/Zoological/SpeciesEpithet or ScientificName/NameAtomised/Bacterial/SpeciesEpithet or ScientificName/NameAtomised/Viral/ViralSpeciesDesignation
The specific epithet part of a binomial or trinomial name at or below the rank of species. Names at ranks of species and below are composed of two or three words; the genus epithet, the specific epithet and possibly an infraspecific epithet. This property should therefore always be accompanied by the genusPart property. If the specificEpithet property is present the uninomial and infragenericEpithet properties should be absent.
The Taxon Name that is the subject of this note. The FROM side of the note relationship. The Taxon Name that this note is qualifying.
The kind of nomenclatural note this is, e.g. sanctioning of name.
The name that is the type. TaxonNames at ranks above species level are typified by the NAME of a lower taxon. Ultimately, by following the chain of type names, all names resolve to a type species and so a type specimen. This property is mutually exclusive with typeSpecimen. A name can't have both. Equivalent to TCS ScientificName/Typification/TypeName.
A type name or specimen. Typification can be complex to represent. On the one hand a type is a property of a TaxonName that is created at the time the name is published. But it needs to exist as a structure so that the type of type can be indicated. On the other hand a type can be the result of a later typification event - almost like a nomenclatural note. This object can therefore be used in two ways. It can be the target of the 'type' property in a TaxonName object (in which case the typeOf property may be omitted) or it can be used as a free standing object with its own ID and the typeOf property used to indicate which TaxonName this is a type of - this is more likely scenario in a the case of a leptotypification event. Equivalent to TCS ScientificName/Typification
The kind of type this specimen is e.g. paratype, isotype, holotype etc. Types can be of different kinds. Equivalent to TCS ScientificName/Typification/TypeVouchers/TypeVoucher@typeOfType
The specimen that is the type. TaxonNames at ranks of family and below are typified by a specimen. This property is mutually exclusive with typeName. Equivalent to TCS ScientificName/Typification/TypeVouchers/TypeVoucher
ScientificName/NameAtomised/*/GenusOrMonomial (but only when NOT representing a genus name)
Name::SupragenericName (but not used for names at the rank of Genus)
Family, genus, infrafamilial, suprafamilial or other uninomial name. This property should be used for any 'single word' names. These include Family, genus, infrafamilial, and suprafamilial names. Note that this property should be used for Genus names. The genus field should only be used for names below rank of genus.
No equivalent other than through publication.
The year of publication of this name. This is the year this name was published. If it is a new combination of the name then it is the year of publication of the combination not the basionym. It should be the same as the year given in the publishedIn property. In zoology the place of first publication of a new combination is rarely given as it is not considered a nomenclatural act unless it leads to homonymy. For new combinations of names in zoology it may therefore be inappropriate to supply this property or the publishedIn, combintationAuthorship or combintationAuthorTeam properties. The main role of this property is to aid disambiguation where author strings may be confusing. This property is not restricted to a date type as feedback from TCS suggested that this restriction was inappropriate.
No direct equivalent. May be indicated in RelName table.
No equivalent in TCS but is inverse of ScientificName/Basionym
Relationship between a basionym and a new combination of the name.
The basionym of this name if it is a new combination. The current name is a recombination (comb. nov.) of the name pointed to and the name pointed to is not, itself, a recombination.
The taxonomic rank of this name. This is a link to an instance of TaxonomicRank. Compare with the rankString property.
Only below species with InfraspecificRank
The taxonomic rank of this name as a string. A string representation of the rank of this name. It is highly recommended that the rank property be used along with this one unless the correct rank is not available in the rank vocabulary.
No equivalent other than through Facts tables?
A string representing the typification of this name. See also the typifiedBy property.
A NomenclaturalType that typifies this name. An instance of NomenclaturalType that contains a type specimen or name for this name. See also note with NomenclaturalType class. See also the typificationString property.
The subject Real Graph is to be added to another Named Graph
The subject Real Graph is inferred from another Named Graph
The subject Real Graph is asserted without relation to another Named Graph
The subject Real Graph is removed from another Named Graph
The roles that Named Graphs can play within an Olis context
Create in 2025 for Kurra tool operations
The Australian Government's community of practice for Linked Data
This vocabulary lists the roles that Agents - People and Organisations - play in relation to data. This is an extended and Semantic Web version of the International Organisation for Standardization's ISO19115-1 standard's Role Codes codelist.
Derived from the ISO 19115's CI Role Code codelist and added to by Australian vocabulary users
IDN Role Codes
(c) Australian Government Linked Data Working Group, 2024
Role Codes presented in the ISO 19115 original standard's codelist
The list of Concepts from the original ISO 19115 Role Code codelist
ISO CI Role Code codes
Presented in the ISO 19115 original standard's codelist
author
co author
party who assists with the generation of the resource other than the principal investigator
collaborator
contributor
party that accepts accountability and responsibility for the resource and ensures appropriate care and maintenance of the resource
custodian
distributor
party who reviewed or modified the resource to improve the content
editor
party providing monetary support for the resource
funder
a class of entity that mediates access to the resource and for whom the resource is intended or useful
mediator
originator
owner
party who can be contacted for acquiring knowledge about or acquisition of the resource
point of contact
key party responsible for gathering information and conducting research
principal investigator
party who has processed the data in a manner such that the resource has been modified
processor
publisher
resource provider
party owning or managing rights over the resource
rights holder
sponsor
party who has an interest in the resource or the use of the resource
stakeholder
user
party that the resources contains information about
Created for the Indigenous Data Network's Catalogue Project, 2022
subject agent
The Indigenous Data Network (IDN) was established in 2018 to support and coordinate the governance of Indigenous data for Aboriginal and Torres Strait Islander peoples and empower Aboriginal and Torres Strait Islander communities to decide their own local data priorities.
party who can be contacted who best represents the interests of the subject agent
subject agent representative
Defined in this ontology for the first time
The subject Real Graph plays the object Olis Graph Role
PREFIX : <https://olis.dev/> PREFIX ex: <http://example.com> PREFIX gr: <http://olis.dev/GraphRoles/> PREFIX schema: <https://schema.org/> ex:realGraphX a :RealGraph ; :hasGraphRole gr:Original ; schema:name "Real Graph X" ; schema:description "A real graph, containing triples about ..." ; . ex:realGraphY a :RealGraph ; :hasGraphRole gr:Inferred ; :hasBaseGraph ex:realGraphX ; schema:name "Real Graph Y" ; schema:description "A real graph, containing triples inferred from Real Graph X" ; . ex:virtualGraphZ a :VirtualGraph ; schema:name "Virtual Graph Z" ; schema:description "A Virtual Graph that contains Real Graphs X & Y" ; :contains ex:realGraphX , ex:realGraphY ; .
The subject Real Graph is derived from, or to be added to, the object Named Graph
A Named Graph that does not and cannot contain triples but which may be related to Real Graphs
2025-12: Altered isAliasFor to contains. Added hasBaseGraph & hasGraphRole 2023-12: First public version
A model of RDF graphs and relations between them
The subject Virtual Graph contains the object Named Graph
This class is not expected to be instantiated, instead Real Graph and Virtual Graph should be used
An RDF Named Graph, as per RDF 1.2's definition
har distribution
Status: English Definition text modified by DCAT revision team, translations pending (except for Italian, Spanish and Czech).
An available distribution of the dataset.
Status: English Definition text modified by DCAT revision team, Italian, Spanish and Czech translations provided, other translations pending.
Relevant contact information for the catalogued resource. Use of vCard is recommended.
tema
Status: English Definition text modified by DCAT revision team, all except for Italian and Czech translations are pending.
The set of skos:Concepts used to categorize the resources are organized in a skos:ConceptScheme describing all the categories and their relations in the catalog.
A main category of the resource. A resource can have multiple themes.
Questa è una copia aggiornata del vocabolario DCAT v2.0 disponibile in https://www.w3.org/ns/dcat.ttl
This is an updated copy of v2.0 of the DCAT vocabulary, taken from https://www.w3.org/ns/dcat.ttl
Esta es una copia del vocabulario DCAT v2.0 disponible en https://www.w3.org/ns/dcat.ttl
English language definitions updated in this revision in line with ED. Multilingual text unevenly updated.
contributors: [ rdfs:seeAlso <https://orcid.org/0000-0001-9300-2694> ; foaf:homepage <http://www.andrea-perego.name/foaf/#me> ; foaf:name "Andrea Perego" ; ] , [ foaf:homepage <http://www.asahi-net.or.jp/~ax2s-kmtn/> ; foaf:name "Shuji Kamitsuna" ; ] , [ a foaf:Person ; schema:affiliation [ foaf:homepage <https://csiro.au> ; foaf:name "Commonwealth Scientific and Industrial Research Organisation" ; ] ; rdfs:seeAlso <https://orcid.org/0000-0002-3884-3420> ; foaf:name "Simon J D Cox" ; foaf:workInfoHomepage <http://people.csiro.au/Simon-Cox> ; ] , [ rdfs:seeAlso <https://orcid.org/0000-0001-5648-2713> ; foaf:homepage <http://www.imati.cnr.it/index.php/people/8-curricula/178-riccardo-albertoni> , <https://w3id.org/people/ralbertoni/> ; foaf:name "Riccardo Albertoni" ; ] , [ rdfs:seeAlso <http://www.eurecom.fr/~atemezin/gatemezing-foaf.rdf> ; foaf:name "Ghislain Auguste Atemezing" ; ] , [ rdfs:seeAlso <http://makxdekkers.com/makxdekkers.rdf#me> ; foaf:homepage <http://makxdekkers.com/> ; foaf:name "Makx Dekkers" ; ] , [ schema:affiliation <http://www.w3.org/data#W3C> ; rdfs:seeAlso <http://philarcher.org/foaf.rdf#me> ; foaf:homepage <http://www.w3.org/People/all#phila> ; foaf:name "Phil Archer" ; ] , [ schema:affiliation [ foaf:homepage <http://ec.europa.eu/dgs/informatics/> ; foaf:name "European Commission, DG DIGIT" ; ] ; foaf:name "Vassilios Peristeras" ; ] , [ schema:affiliation [ foaf:homepage <http://www.refinitiv.com> ; foaf:name "Refinitiv" ; ] ; foaf:name "David Browning" ; ] , [ rdfs:seeAlso <https://jakub.klímek.com/#me> ; foaf:homepage <https://jakub.klímek.com/> ; foaf:name "Jakub Klímek" ; ] , [ foaf:name "Richard Cyganiak" ; ] , [ foaf:name "Marios Meimaris" ; ] , [ schema:affiliation [ foaf:homepage <http://okfn.org> ; foaf:name "Open Knowledge Foundation" ; ] ; foaf:name "Rufus Pollock" ; ] , [ schema:affiliation [ foaf:homepage <http://stfc.ac.uk> ; foaf:name "Science and Technology Facilities Council, UK" ; ] ; rdfs:seeAlso <https://orcid.org/0000-0003-3499-8262> ; foaf:homepage <https://agbeltran.github.io> ; foaf:name "Alejandra Gonzalez-Beltran" ; ] , [ foaf:name "Boris Villazón-Terrazas" ; ] , [ foaf:name "Martin Alvarez-Espinar" ; ] ;
DCAT is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. By using DCAT to describe datasets in data catalogs, publishers increase discoverability and enable applications easily to consume metadata from multiple catalogs. It further enables decentralized publishing of catalogs and facilitates federated dataset search across sites. Aggregated DCAT metadata can serve as a manifest file to facilitate digital preservation. DCAT is defined at http://www.w3.org/TR/vocab-dcat/. Any variance between that normative document and this schema is an error in this schema.
Datasamling
2018-02 - subclass of dctype:Dataset removed because scope of dcat:Dataset includes several other types from the dctype vocabulary.
2020-03-16 A new scopenote added and need to be translated
This class describes the conceptual dataset. One or more representations might be available, with differing schematic layouts and formats or serializations.
The notion of dataset in DCAT is broad and inclusive, with the intention of accommodating resource types arising from all communities. Data comes in many forms including numbers, text, pixels, imagery, sound and other multi-media, and potentially other types, any of which might be collected into a dataset.
This class represents the actual dataset as published by the dataset provider. In cases where a distinction between the actual dataset and its entry in the catalog is necessary (because metadata such as modification date and maintainer might differ), the catalog record class can be used for the latter.
A collection of data, published or curated by a single source, and available for access or download in one or more represenations.
Dataudstilling
This represents a general availability of a dataset it implies no information about the actual access method of the data, i.e. whether by direct download, API, or through a Web page. The use of dcat:downloadURL property indicates directly downloadable distributions.
A specific representation of a dataset. A dataset might be available in multiple serializations that may differ in various ways, including natural language, media-type or format, schematic organization, temporal and spatial resolution, level of detail or profiles (which might specify any or all of the above).
English, Italian, Spanish definitions updated in this revision. Multilingual text not yet updated.
A web-based data catalog is typically represented as a single instance of this class.
A curated collection of metadata about resources (e.g., datasets and data services in the context of a data catalog).
adgangsURL
Status: English Definition text modified by DCAT revision team, updated Italian and Czech translation provided, translations for other languages pending.
If the distribution(s) are accessible only through a landing page (i.e. direct download URLs are not known), then the landing page link should be duplicated as accessURL on a distribution.
A URL of a resource that gives access to a distribution of the dataset. E.g. landing page, feed, SPARQL endpoint. Use for all cases except a simple download link, in which case downloadURL is preferred.
A site or end-point that gives access to the distribution of the dataset.
The root location or primary endpoint of the service (a web-resolvable IRI).
The range of this property is intentionally generic, with the purpose of allowing different geometry encodings. E.g., the geometry could be encoded with as WKT (geosparql:wktLiteral [GeoSPARQL]) or [GML] (geosparql:asGML [GeoSPARQL]).
The geographic bounding box of a resource.
The size in bytes can be approximated when the precise size is not known. The literal value of dcat:byteSize should by typed as xsd:decimal.
har delkatalog
A catalog whose contents are of interest in the context of this catalog.
centroide
The geographic center (centroid) of a resource.
This property is to be used when the files in the distribution are compressed, e.g. in a ZIP file. The format SHOULD be expressed using a media type as defined by IANA media types registry https://www.iana.org/assignments/media-types/, if available.
The compression format of the distribution in which the data is contained in a compressed form, e.g. to reduce the size of the downloadable file.
har datasæt
Status: English Definition text modified by DCAT revision team, Italian, Spanish and Czech translation provided, other translations pending.
A collection of data that is listed in the catalog.
Status: English Definition text modified by DCAT revision team, Italian, Spanish and Czech translation updated, other translations pending.
dcat:downloadURL SHOULD be used for the address at which this distribution is available directly, typically through a HTTP Get request.
The URL of the downloadable file in a given format. E.g. CSV file or RDF file. The format is indicated by the distribution's dct:format and/or dcat:mediaType.
The range of this property is intentionally generic, with the purpose of allowing different level of temporal precision for specifying the end of a period. E.g., it can be expressed with a date (xsd:date), a date and time (xsd:dateTime), or a year (xsd:gYear).
An endpoint description may be expressed in a machine-readable form, such as an OpenAPI (Swagger) description, an OGC GetCapabilities response, a SPARQL Service Description, an OpenSearch or WSDL document, a Hydra API description, else in text or some other informal mode if a formal representation is not possible.
The endpoint description gives specific details of the actual endpoint instance, while dct:conformsTo is used to indicate the general standard or specification that the endpoint implements.
A description of the service end-point, including its operations, parameters etc.
Dataservice
If a dcat:DataService is bound to one or more specified Datasets, they are indicated by the dcat:servesDataset property.
The kind of service can be indicated using the dct:type property. Its value may be taken from a controlled vocabulary such as the INSPIRE spatial data service type vocabulary.
A site or end-point providing operations related to the discovery of, access to, or processing functions on, data or related resources.
A Web page that can be navigated to in a Web browser to gain access to the catalog, a dataset, its distributions and/or additional information.
The range of dcat:mediaType has been tightened as part of the revision of DCAT.
Status: English Definition text modified by DCAT revision team, Italian and Czech translation provided, other translations pending. Note some inconsistency on def vs. usage.
This property SHOULD be used when the media type of the distribution is defined in the IANA media types registry https://www.iana.org/assignments/media-types/, otherwise dct:format MAY be used with different values.
The media type of the distribution as defined by IANA.
This property to be used when the files in the distribution are packaged, e.g. in a TAR file, a Frictionless Data Package or a Bagit file. The format SHOULD be expressed using a media type as defined by IANA media types registry https://www.iana.org/assignments/media-types/, if available.
The package format of the distribution in which one or more data files are grouped together, e.g. to enable a set of related files to be downloaded together.
Introduced into DCAT to complement the other PROV qualified relations.
Used to link to another resource where the nature of the relationship is known but does not match one of the standard Dublin Core properties (dct:hasPart, dct:isPartOf, dct:conformsTo, dct:isFormatOf, dct:hasFormat, dct:isVersionOf, dct:hasVersion, dct:replaces, dct:isReplacedBy, dct:references, dct:isReferencedBy, dct:requires, dct:isRequiredBy) or PROV-O properties (prov:wasDerivedFrom, prov:wasInfluencedBy, prov:wasQuotedFrom, prov:wasRevisionOf, prov:hadPrimarySource, prov:alternateOf, prov:specializationOf).
Link to a description of a relationship with another resource.
The class of all catalogued resources, the Superclass of dcat:Dataset, dcat:DataService, dcat:Catalog and any other member of a dcat:Catalog. This class carries properties common to all catalogued resources, including datasets and data services. It is strongly recommended to use a more specific sub-class. When describing a resource which is not a dcat:Dataset or dcat:DataService, it is recommended to create a suitable sub-class of dcat:Resource, or use dcat:Resource with the dct:type property to indicate the specific type.
dcat:Resource is an extension point that enables the definition of any kind of catalog. Additional subclasses may be defined in a DCAT profile or application for catalogs of other kinds of resources.
Resource published or curated by a single agent.
Use to characterize a relationship between datasets, and potentially other resources, where the nature of the relationship is known but is not adequately characterized by the standard Dublin Core properties (dct:hasPart, dct:isPartOf, dct:conformsTo, dct:isFormatOf, dct:hasFormat, dct:isVersionOf, dct:hasVersion, dct:replaces, dct:isReplacedBy, dct:references, dct:isReferencedBy, dct:requires, dct:isRequiredBy) or PROV-O properties (prov:wasDerivedFrom, prov:wasInfluencedBy, prov:wasQuotedFrom, prov:wasRevisionOf, prov:hadPrimarySource, prov:alternateOf, prov:specializationOf).
An association class for attaching additional information to a relationship between DCAT Resources.
har post
Status: English, Italian, Spanish and Czech Definitions modified by DCAT revision team, other translations pending.
A record describing the registration of a single dataset or data service that is part of the catalog.
English definition updated in this revision. Multilingual text not yet updated except the Spanish one and the Czech one and Italian one.
This class is optional and not all catalogs will use it. It exists for catalogs where a distinction is made between metadata about a dataset or data service and metadata about the entry for the dataset or data service in the catalog. For example, the publication date property of the dataset reflects the date when the information was originally made available by the publishing agency, while the publication date of the catalog record is the date when the dataset was added to the catalog. In cases where both dates differ, or where only the latter is known, the publication date should only be specified for the catalog record. Notice that the W3C PROV Ontology allows describing further provenance information such as the details of the process and the agent involved in a particular change to a dataset.
A record in a data catalog, describing the registration of a single dataset or data service.
udstiller
A collection of data that this DataService can distribute.
har datatjeneste
A site or endpoint that is listed in the catalog.
minimum spatial separation resolvable in a dataset, measured in metres.
Might appear in the description of a Dataset or a Distribution, so no domain is specified.
Alternative spatial resolutions might be provided as different dataset distributions. If the dataset is an image or grid this should correspond to the spacing of items. For other kinds of spatial dataset, this property will usually indicate the smallest distance between items in the dataset.
The range of this property is intentionally generic, with the purpose of allowing different level of temporal precision for specifying the start of a period. E.g., it can be expressed with a date (xsd:date), a date and time (xsd:dateTime), or a year (xsd:gYear).
Alternative temporal resolutions might be provided as different dataset distributions.
If the dataset is a time-series this should correspond to the spacing of items in the series. For other kinds of dataset, this property will usually indicate the smallest time difference between items in the dataset.
minimum time period resolvable in a dataset.
temataksonomi
It is recommended that the taxonomy is organized in a skos:ConceptScheme, skos:Collection, owl:Ontology or similar, which allows each member to be denoted by an IRI and published as linked-data.
The knowledge organization system (KOS) used to classify catalog's datasets.
Introduced into DCAT to complement prov:Role (whose use is limited to roles in the context of an activity, as the range of prov:hadRole).
Used in a qualified-attribution to specify the role of an Agent with respect to an Entity. It is recommended that the values be managed as a controlled vocabulary of agent roles, such as http://registry.it.csiro.au/def/isotc211/CI_RoleCode.
Used in a qualified-relation to specify the role of an Entity with respect to another Entity. It is recommended that the values be managed as a controlled vocabulary of entity roles such as: ISO 19115 DS_AssociationTypeCode http://registry.it.csiro.au/def/isotc211/DS_AssociationTypeCode; IANA Registry of Link Relations https://www.iana.org/assignments/link-relation; DataCite metadata schema; MARC relators https://id.loc.gov/vocabulary/relators.
A role is the function of a resource or agent with respect to another resource, in the context of resource attribution or resource relationships.
Introduced into DCAT to complement prov:hadRole (whose use is limited to roles in the context of an activity, with the domain of prov:Association.
May be used in a qualified-attribution to specify the role of an Agent with respect to an Entity. It is recommended that the value be taken from a controlled vocabulary of agent roles, such as http://registry.it.csiro.au/def/isotc211/CI_RoleCode.
May be used in a qualified-relation to specify the role of an Entity with respect to another Entity. It is recommended that the value be taken from a controlled vocabulary of entity roles such as: ISO 19115 DS_AssociationTypeCode http://registry.it.csiro.au/def/isotc211/DS_AssociationTypeCode; IANA Registry of Link Relations https://www.iana.org/assignments/link-relation; DataCite metadata schema; MARC relators https://id.loc.gov/vocabulary/relators.
The function of an entity or agent with respect to another entity or resource.
DASH is a SHACL library for frequently needed features and design patterns. The constraint components in this library are 100% standards compliant and will work on any engine that fully supports SHACL.
Can be used to link a property shape with an editor, to state a preferred editing widget in user interfaces.
An auto-complete field to enter the label of instances of a class. This is the fallback editor for any URI resource if no other editors are more suitable.
Links a node shape with the roles for which it shall be used as default view. User interfaces can use these values to select how to present a given RDF resource. The values of this property are URIs representing a group of users or agents. There is a dedicated URI dash:all representing all users.
Represents all users/roles, for example as a possible value of the default view for role property.
An editor for non-literal values, typically displaying a nested form where the values of the linked resource can be edited directly on the "parent" form. Implementations that do not support this (yet) could fall back to an auto-complete widget.
The class of possible values for dash:apiStatus.
A result representing a validation failure such as an unsupported recursion.
Base class for results produced by running test cases.
A suggestion consisting of added and/or deleted triples, represented as rdf:Statements via dash:addedTriple and dash:deletedTriple.
Base class of suggestions that modify a graph to "fix" the source of a validation result.
A multi-function is a function that can return zero or more result objects consisting of one or more result variables. While normal (SPARQL/SHACL) functions can only return a single result node, multi-functions may not only return multiple nodes but even multiple individual variables per solution. A common way of defining multi-functions is by wrapping a SPARQL SELECT query, using dash:SPARQLMultiFunction. However, some MultiFunctions (in TopBraid) may also be implemented natively.
The class of roles that a property (shape) may take for its focus nodes.
Encapsulates one or more SPARQL CONSTRUCT queries that can be parameterized. Parameters will become pre-bound variables in the queries.
A multi-function based on a SPARQL SELECT query. The query gets executed with the arguments pre-bound to the variables declared as parameters. The results of the multi-function are all result bindings from the SPARQL result set.
Encapsulates a SPARQL SELECT query that can be parameterized. Parameters will become pre-bound variables in the query.
A SuggestionGenerator based on a SPARQL UPDATE query (sh:update), producing an instance of dash:GraphUpdate. The INSERTs become dash:addedTriple and the DELETEs become dash:deletedTriple. The WHERE clause operates on the data graph with the pre-bound variables $focusNode, $predicate and $value, as well as the other pre-bound variables for the parameters of the constraint. In many cases, there may be multiple possible suggestions to fix a problem. For example, with sh:maxLength there are many ways to slice a string. In those cases, the system will first iterate through the result variables from a SELECT query (sh:select) and apply these results as pre-bound variables into the UPDATE query.
Base class of objects that can generate suggestions (added or deleted triples) for a validation result of a given constraint component.
Script functions can be used from SPARQL queries and will be injected into the generated prefix object (in JavaScript, for ADS scripts). The dash:js will be inserted into a generated JavaScript function and therefore needs to use the return keyword to produce results. These JS snippets can access the parameter values based on the local name of the sh:Parameter's path. For example ex:value can be accessed using value. SPARQL use note: Since these functions may be used from any data graph and any shapes graph, they must not rely on any API apart from what's available in the shapes graph that holds the rdf:type triple of the function itself. In other words, at execution time from SPARQL, the ADS shapes graph will be the home graph of the function's declaration.
An executable unit implemented in one or more languages such as JavaScript.
A shape script contains extra code that gets injected into the API for the associated node shape. In particular you can use this to define additional functions that operate on the current focus node (the this variable in JavaScript).
A result representing a successfully validated constraint.
Represents a successful run of a test case.
Indicates that a class is "abstract" and cannot be used in asserted rdf:type triples. Only non-abstract subclasses of abstract classes should be instantiated directly.
Class of results that have been produced as suggestions, not through SHACL validation. How the actual results are produced is up to implementers. Each instance of this class should have values for sh:focusNode, sh:resultMessage, sh:resultSeverity (suggested default: sh:Info), and dash:suggestion to point at one or more suggestions.
Abstract base class for test environments, holding information on how to set up a test case.
A test case that evaluates a dash:Action using provided input parameters. Requires exactly one value for dash:action and will operate on the test case's graph (with imports) as both data and shapes graph. Currently only supports read-only actions, allowing the comparison of actual results with the expected results.
A class that is also a node shape. This class can be used as rdf:type instead of the combination of rdfs:Class and sh:NodeShape.
A test case to verify that a (SHACL-based) feature works as expected.
A reusable instance of dash:AllObjectsTarget.
SELECT DISTINCT ?this WHERE { ?anyS ?anyP ?this . }
A target containing all objects in the data graph as focus nodes.
A reusable instance of dash:AllSubjectsTarget.
SELECT DISTINCT ?this WHERE { ?this ?anyP ?anyO . }
A target containing all subjects in the data graph as focus nodes.
A Viewer for blank nodes, rendering as the label of the blank node.
An editor for boolean literals, rendering as a select box with values true and false. Also displays the current value (such as "1"^^xsd:boolean), but only allows to switch to true or false.
Class of ADS scripts that are executed after edits to the data graph were made, but within the same edit. These scripts may access the current changes from the graphs with names dataset.addedGraphURI and dataset.deletedGraphURI to learn about which resource values have been added or deleted. For example query them using graph.withDataGraph(dataset.addedGraphURI, ...) or via SPARQL's GRAPH keyword. Change scripts may then perform further changes which would again become visible to other change scripts. They MUST NOT have other side effects though, because they may get executed in Preview mode, or the change may cause constraint violations and then be rejected. For side effects, after the change has been applied, use commit scripts (dash:CommitScript). Change scripts are executed by their relative sh:order, with a default value of 0. Use lower values to execute before other scripts.
Property {?path} is not among those permitted for any of the types
SELECT $this (?predicate AS ?path) ?value WHERE { FILTER ($closedByTypes) . $this ?predicate ?value . FILTER (?predicate != rdf:type) . FILTER NOT EXISTS { $this rdf:type ?type . ?type rdfs:subClassOf* ?class . GRAPH $shapesGraph { ?class sh:property/sh:path ?predicate . } } }
A constraint component that can be used to declare that focus nodes are "closed" based on their rdf:types, meaning that focus nodes may only have values for the properties that are explicitly enumerated via sh:property/sh:path in property constraints at their rdf:types and the superclasses of those. This assumes that the type classes are also shapes.
True to indicate that the focus nodes are closed by their types. A constraint violation is reported for each property value of the focus node where the property is not among those that are explicitly declared via sh:property/sh:path in any of the rdf:types of the focus node (and their superclasses). The property rdf:type is always permitted.
ClosedByTypesConstraintComponent closedByTypes
Values must co-exist with values of {$coExistsWith}
SELECT $this WHERE { { FILTER (EXISTS { $this $PATH ?any } && NOT EXISTS { $this $coExistsWith ?any }) } UNION { FILTER (NOT EXISTS { $this $PATH ?any } && EXISTS { $this $coExistsWith ?any }) } }
A constraint component that can be used to express a constraint on property shapes so that if the property path has any value then the given property must also have a value, and vice versa.
Can be set to true for those constraint components where the validation does not require to visit any other triples than the shape definitions and the direct property values of the focus node mentioned in the property constraints. Examples of this include sh:minCount and sh:hasValue. Constraint components that are marked as such can be optimized by engines, e.g. they can be evaluated client-side at form submission time, without having to make a round-trip to a server, assuming the client has downloaded a complete snapshot of the resource. Any component marked with dash:staticConstraint is also a dash:localConstraint.
The properties that must co-exist with the surrounding property (path). If the surrounding property path has any value then the given property must also have a value, and vice versa.
CoExistsWithConstraintComponent coExistsWith
Class of ADS scripts that are executed after edits to the data graph were made and have been committed. These scripts may access the changes that have just happened from the graphs with names dataset.addedGraphURI and dataset.deletedGraphURI to learn about which resource values have been added or deleted. For example query them using graph.withDataGraph(dataset.addedGraphURI, ...) or via SPARQL's GRAPH keyword. Commit scripts may then perform side effects such as updating other graphs or sending out notifications to external systems. For edits that should be made within a finishing change, use change scripts (dash:ChangeScript). Commit scripts are executed by their relative sh:order, with a default value of 0. Use lower values to execute before other scripts.
A script that is executed when a new instance of the class associated via dash:constructor is created, e.g. from a New button. Such scripts typically declare one or more parameters that are collected from the user when the script starts. The values of these parameters can be used as named variables in the script for arbitrary purposes such as setting the URI or initializing some property values of the new instance. The variable focusNode will hold the named node of the selected type, for example when a constructor is associated with a superclass but the user has pressed New for a subclass. The last expression of the script will be used as result of the constructor, so that the surrounding tool knows which resource shall be navigated to next.
An rdf:List that can be used in property constraints as value for sh:or to indicate that all values of a property must be either xsd:date or xsd:dateTime.
An editor for xsd:date literals, offering a calendar-like date picker.
An editor for xsd:dateTime literals, offering a calendar-like date picker and a time selector.
Depiction properties provide images representing the focus nodes. Typical examples may be a photo of an animal or the map of a country.
Features that have been marked deprecated will remain in the API but should no longer be used by new code and may get deleted in the foreseeable future (e.g., with the next major release).
Description properties should produce text literals that may be used as an introduction/summary of what a focus node does.
A Viewer for resources that shows the details of the value using its default view shape as a nested form-like display.
A drop-down editor for enumerated values (typically based on sh:in lists).
Features that are marked experimental can be used by early adopters but there is no guarantee that they will reach stable state.
An action typically showing up in an Explore section of a selected resource. Cannot make changes to the data.
An Action that can be executed for a selected resource. Such Actions show up in context menus once they have been assigned a sh:group.
A test case that verifies that a given SPARQL expression produces a given, expected result.
A service that does not apply to a specific resource (as ResourceService does) but operates on the whole graph. The focusNode variable will be the URI of the current base graph (e.g. <urn:x-evn-master:geo> as a NamedNode.
A script that gets exposed as a web service, e.g. /tbl/service/ex/MyService
A test case that can be used to verify that an RDF file could be loaded (from a file) and that the resulting RDF graph is equivalent to a given TTL file.
An rdf:List that can be used in property constraints as value for sh:or to indicate that all values of a property must be either rdf:HTML, xsd:string or rdf:langString (in that order of preference).
A Viewer for HTML encoded text from rdf:HTML literals, rendering as parsed HTML DOM elements. Also displays the language if the HTML has a lang attribute on its root DOM element.
At least one of the values must be in {$hasValueIn}
SELECT $this WHERE { FILTER NOT EXISTS { $this $PATH ?value . GRAPH $shapesGraph { $hasValueIn rdf:rest*/rdf:first ?value . } } }
A constraint component that can be used to express a constraint on property shapes so that one of the values of the property path must be a member of a given list of nodes.
At least one of the value nodes must be a member of the given list.
HasValueInConstraintComponent hasValueIn
All subjects where {$predicate} has value {$object}
The value that is expected to be present.
SELECT DISTINCT ?this WHERE { ?this $predicate $object . }
A target type for all subjects where a given predicate has a certain object value.
At least one of the values must be an instance of class {$hasValueWithClass}
SELECT $this WHERE { FILTER NOT EXISTS { $this $PATH ?value . ?value a ?type . ?type rdfs:subClassOf* $hasValueWithClass . } }
A constraint component that can be used to express a constraint on property shapes so that one of the values of the property path must be an instance of a given class.
Has value with class constraint component
One of the values of the property path must be an instance of the given class.
HasValueWithClassConstraintComponent hasValueWithClass
A Viewer for literals, rendering as a hyperlink to a URL. For literals it assumes the lexical form is the URL. This is often used as default viewer for xsd:anyURI literals. Unsupported for blank nodes.
ID properties are short strings or other literals that identify the focus node among siblings. Examples may include social security numbers.
Icon properties produce images that are typically small and almost square-shaped, and that may be displayed in the upper left corner of a focus node's display. Values should be xsd:string or xsd:anyURI literals or IRI nodes pointing at URLs. Those URLs should ideally be vector graphics such as .svg files. Instances of the same class often have the same icon, and this icon may be computed using a sh:values rule or as sh:defaultValue. If the value is a relative URL then those should be resolved against the server that delivered the surrounding page.
A Viewer for URI values that are recognized as images by a browser, rendering as an image.
The code associated with instances of this class will get injected into the generated APIs, as global code snippets. Typically used to declare libraries of utility functions or constants that are (compared to shape scripts) not necessarily associated with specific classes or shapes. Note that the JavaScript code stored in dash:js cannot use the export keyword because the code must also work in external scripts (such as on Node.js). Instead, you need to enumerate the exported symbols via dash:exports.
A constraint component that can be used to mark property shapes to be indexed, meaning that each of its value nodes must carry a dash:index from 0 to N.
True to activate indexing for this property.
A test case to verify whether an inferencing engine is producing identical results to those stored as expected results.
A multi-viewer that renders all values horizontally, in a more compact form that just a single value per row.
A viewer for multiple/all values at once.
A drop-down editor for all instances of the target class (based on sh:class of the property).
A tabular viewer for rdf:JSON literals with a lexical form in the following format: { vars: [ 'col1', 'col2' ], // These are the column keys headerLabels: [ 'Column 1', 'Column 2' ], // Optional, for the column headers bindings: [ // These become the rows { col1: { lex: 'Value2', datatype: '...#string', }, col2: { uri: 'http://.../Instance', label: 'Example Instance', }, }, ... ], } The resulting table will use the headerLabels (if they exist) as column headers, otherwise derive the headers from the variable names. The vars must match the fields in the bindings. The table will contain one row for each binding. Using Active Data Shapes, you can construct such literals dynamically using a sh:values rule, e.g. ex:MyClass-myProperty a sh:PropertyShape ; sh:path ex:myProperty ; sh:values [ dash:js """ DataViewers.createTableViewerJSON(focusNode.select(` SELECT ?col1 ?col2 WHERE { $this ex:prop1 ?col1 . $this ex:prop2 ?col2 . } `))""" ] . You may also produce the JSON literal programmatically in JavaScript, or assert the triples by other means.
The Key info role may be assigned to properties that are likely of special interest to a reader, so that they should appear whenever a summary of a focus node is shown.
Properties with this role produce strings that may serve as display label for the focus nodes. Labels should be either plain string literals or strings with a language tag. The values should also be single-line.
A Viewer for URI resources, rendering as a hyperlink to that URI based on the display label of the resource. Also includes other ways of interacting with the URI such as opening a nested summary display.
A Viewer for literals with a language tag, rendering as the text plus a language indicator.
A simple viewer for literals, rendering the lexical form of the value.
An action typically showing up in a Modify section of a selected resource. May make changes to the data.
An editor for multiple/all value nodes at once.
The class of widgets for editing value nodes.
An "editor" that simply informs the user that the values cannot be edited here, but for example through source code editing.
SELECT DISTINCT $this ($this AS ?value) WHERE { { FILTER (?nonRecursive) } $this $PATH $this . }
Used to state that a property or path must not point back to itself.
Used to state that a property or path must not point back to itself. For example, "a person cannot have itself as parent" can be expressed by setting dash:nonRecursive=true for a given sh:path. To express that a person cannot have itself among any of its (recursive) parents, use a sh:path with the + operator such as ex:parent+.
NonRecursiveConstraintComponent nonRecursive
A constraint component that can be used to verify that all value nodes conform to the given Parameter.
Parameter constraint component
The property {?predicate} is the primary key and URIs start with {?uriStart}
SELECT DISTINCT $this WHERE { FILTER ( # Must have a value for the primary key NOT EXISTS { ?this $PATH ?any } || # Must have no more than one value for the primary key EXISTS { ?this $PATH ?value1 . ?this $PATH ?value2 . FILTER (?value1 != ?value2) . } || # The value of the primary key must align with the derived URI EXISTS { { ?this $PATH ?value . FILTER NOT EXISTS { ?this $PATH ?value2 . FILTER (?value != ?value2) } } BIND (CONCAT($uriStart, ENCODE_FOR_URI(str(?value))) AS ?uri) . FILTER (str(?this) != ?uri) . } ) }
Enforces a constraint that the given property (sh:path) serves as primary key for all resources in the target of the shape. If a property has been declared to be the primary key then each resource must have exactly one value for that property. Furthermore, the URIs of those resources must start with a given string (dash:uriStart), followed by the URL-encoded primary key value. For example if dash:uriStart is "http://example.org/country-" and the primary key for an instance is "de" then the URI must be "http://example.org/country-de". Finally, as a result of the URI policy, there can not be any other resource with the same value under the same primary key policy.
The start of the URIs of well-formed resources. If specified then the associated property/path serves as "primary key" for all target nodes (instances). All such target nodes need to have a URI that starts with the given string, followed by the URI-encoded value of the primary key property.
A test case running a given SPARQL SELECT query and comparing its results with those stored as JSON Result Set in the expected result property.
Can be used to specify the node shape that may be applied to reified statements produced by a property shape. The property shape must have a URI resource as its sh:path. The values of this property must be node shapes. User interfaces can use this information to determine which properties to present to users when reified statements are explored or edited. Also, SHACL validators can use it to determine how to validate reified triples. Use dash:None to indicate that no reification should be permitted.
ReifiableByConstraintComponent reifiableBy
A Service that can (and must) be applied to a given resource as focus node. Use dash:resourceService to link a class to the services that apply to its instances.
A rich text editor to enter the lexical value of a literal and a drop down to select language. The selected language is stored in the HTML lang attribute of the root node in the HTML DOM tree.
A constraint component defining the parameter dash:rootClass, which restricts the values to be either the root class itself or one of its subclasses. This is typically used in conjunction with properties that have rdfs:Class as their type.
ASK { $value rdfs:subClassOf* $rootClass . }
Defines the properties that instruct the ADS Script API generator about what prefixes, constants and classes to generate.
The API generator will produce classes for each value of this property and all its subclasses and superclasses.
If a prefix (such as "edg") is listed here then the API generator will produce classes for all RDFS classes or node shapes from the associated namespace.
If a prefix (such as "edg") is listed here then the API generator will produce constants for class, datatype, shape and property names.
ScriptConstraintComponent scriptConstraint
A Suggestion Generator that is backed by an Active Data Shapes script. The script needs to return a JSON object or an array of JSON objects if it shall generate multiple suggestions. It may also return null to indicate that nothing was suggested. Note that the whole script is evaluated as a (JavaScript) expression, and those will use the last value as result. So simply putting an object at the end of your script should do. Alternatively, define the bulk of the operation as a function and simply call that function in the script. Each response object can have the following fields: { message: "The human readable message", // Defaults to the schema:name(s) of the suggestion generator add: [ // An array of triples to add, each triple as an array with three nodes [ subject, predicate, object ], [ ... ] ], delete: [ ... like add, for the triples to delete ] } Suggestions with neither added nor deleted triples will be discarded. At execution time, the script operates on the data graph as the active graph, with the following pre-bound variables: - focusNode: the NamedNode that is the sh:focusNode of the validation result - predicate: the NamedNode representing the predicate of the validation result, assuming sh:resultPath is a URI - value: the value node from the validation result's sh:value, cast into the most suitable JS object - the other pre-bound variables for the parameters of the constraint, e.g. in a sh:maxCount constraint it would be maxCount The script will be executed in read-only mode, i.e. it cannot modify the graph. Example with dash:js: ({ message: `Copy labels into ${graph.localName(predicate)}`, add: focusNode.values(rdfs.label).map(label => [ focusNode, predicate, label ] ) })
A test case that evaluates a script. Requires exactly one value for dash:js and will operate on the test case's graph (with imports) as both data and shapes graph. Supports read-only scripts only at this stage.
A SHACL validator based on an Active Data Shapes script. See the comment at dash:ScriptConstraint for the basic evaluation approach. Note that in addition to focusNode and value/values, the script can access pre-bound variables for each declared argument of the constraint component.
ASK { FILTER (!$singleLine || !isLiteral($value) || (!contains(str($value), '\n') && !contains(str($value), '\r'))) }
A constraint component that can be used to declare that all values that are literals must have a lexical form that contains no line breaks ('\n' or '\r'). User interfaces may use the dash:singleLine flag to prefer a text field over a (multi-line) text area.
True to state that the lexical form of literal value nodes must not contain any line breaks. False to state that line breaks are explicitly permitted.
SingleLineConstraintComponent singleLine
A constraint component that can be used to verify that every value node is an IRI and the IRI starts with a given string value.
Stem constraint component
Can be set to true for those constraint components where the validation does not require to visit any other triples than the parameters. Examples of this include sh:datatype or sh:nodeKind, where no further triples need to be queried to determine the result. Constraint components that are marked as such can be optimized by engines, e.g. they can be evaluated client-side at form submission time, without having to make a round-trip to a server.
If specified then every value node must be an IRI and the IRI must start with the given string value.
ASK { FILTER (isIRI($value) && STRSTARTS(str($value), $stem)) }
Checks whether a given node is an IRI starting with a given stem.
An rdf:List that can be used in property constraints as value for sh:or to indicate that all values of a property must be either xsd:string, rdf:langString or rdf:HTML (in that order of preference).
An editor for properties that declare a dash:rootClass. The editor allows selecting either the class itself or one of its subclasses.
Must be one of the values of {$subSetOf}
A constraint component that can be used to state that the set of value nodes must be a subset of the value of a given property.
Can be used to state that all value nodes must also be values of a specified other property at the same focus node.
SELECT $this ?value { FILTER ($symmetric) . $this $PATH ?value . FILTER NOT EXISTS { ?value $PATH $this . } }
A contraint component for property shapes to validate that a property is symmetric. For symmetric properties, if A relates to B then B must relate to A.
If set to true then if A relates to B then B must relate to A.
A multi-line text area to enter the value of a literal.
A multi-line text area to enter the value of a literal and a drop down to select a language.
A simple input field to enter the value of a literal, without the ability to change language or datatype. This is the fallback editor for any literal if no other editors are more suitable.
A single-line input field to enter the value of a literal and a drop down to select language, which is mandatory unless xsd:string is among the permissible datatypes.
An input field to enter the URI of a resource, e.g. rdfs:seeAlso links or images.
A Viewer for URI resources, rendering as a hyperlink to that URI. Also includes other ways of interacting with the URI such as opening a nested summary display.
Values must be unique among all instances of {?uniqueValueForClass}
Value {?value} must be unique but is also used by {?other}
SELECT DISTINCT $this ?value ?other WHERE { { $this $PATH ?value . ?other $PATH ?value . FILTER (?other != $this) . } ?other a ?type . ?type rdfs:subClassOf* $uniqueValueForClass . }
A constraint component that can be used to state that the values of a property must be unique for all instances of a given class (and its subclasses).
Unique value for class constraint component
States that the values of the property must be unique for all instances of a given class (and its subclasses).
UniqueValueForClassConstraintComponent uniqueValueForClass
A Viewer for HTML content from untrusted sources. This viewer will sanitize the HTML before rendering. Any a, button, checkbox, form, hidden, input, img, script, select, style and textarea tags and class and style attributes will be removed.
A viewer that renders all values of a given property as a table, with one value per row, and the columns defined by the shape that is the sh:node or sh:class of the property.
Links an Action with the ActionGroup that it should be arranged in.
An executable command triggered by an agent, backed by a Script implementation. Actions may get deactivated using sh:deactivated.
A group of ResourceActions, used to arrange items in menus etc. Similar to sh:PropertyGroups, they may have a sh:order and should have labels (in multiple languages if applicable).
The (CSS) class of an Action for display purposes alongside the label.
May link a dash:GraphUpdate with one or more triples (represented as instances of rdf:Statement) that should be added to fix the source of the result.
Defines how and whether the associated feature is part of an external API. APIs may be implemented as (REST) web services, via GraphQL or ADS Script APIs.
Can be used to state that a shape is applicable to instances of a given class. This is a softer statement than "target class": a target means that all instances of the class must conform to the shape. Being applicable to simply means that the shape may apply to (some) instances of the class. This information can be used by algorithms or humans.
If set to true then the results of the SHACL function can be cached in between invocations with the same arguments. In other words, they are stateless and do not depend on triples in any graph, or the current time stamp etc.
Can be used to indicate that a property/path represented by a property constraint represents a composite relationship. In a composite relationship, the life cycle of a "child" object (value of the property/path) depends on the "parent" object (focus node). If the parent gets deleted, then the child objects should be deleted, too. Tools may use dash:composite (if set to true) to implement cascading delete operations.
Used to mark certain parameterizables as context-free, meaning that the outcome of a process does not depend on the currently active query graph.
Can be used to annotate a graph (usually the owl:Ontology) with the default language that tools should suggest for new literal values. For example, predominantly English graphs should have "en" as default language.
May link a dash:GraphUpdate result with one or more triples (represented as instances of rdf:Statement) that should be deleted to fix the source of the result.
Can be used in dash:js node expressions to enumerate the predicates that the computation of the values may depend on. This can be used by clients to determine whether an edit requires re-computation of values on a form or elsewhere. For example, if the dash:js is something like "focusNode.firstName + focusNode.lastName" then the dependency predicates should be ex:firstName and ex:lastName.
Can be used to link a SHACL property shape with the URL of a SPARQL endpoint that may contain further RDF triples for the value nodes delivered by the property. This can be used to inform a processor that it should switch to values from an external graph when the user wants to retrieve more information about a value. This property should be regarded as an "annotation", i.e. it does not have any impact on validation or other built-in SHACL features. However, selected tools may want to use this information. One implementation strategy would be to periodically fetch the values specified by the sh:node or sh:class shape associated with the property, using the property shapes in that shape, and add the resulting triples into the main query graph. An example value is "https://query.wikidata.org/sparql".
Can be used to link a SHACL property shape with a SHACL node expression that produces the URIs of one or more graphs that contain further RDF triples for the value nodes delivered by the property. This can be used to inform a processor that it should switch to another data graph when the user wants to retrieve more information about a value. The node expressions are evaluated with the focus node as input. (It is unclear whether there are also cases where the result may be different for each specific value, in which case the node expression would need a second input argument). This property should be regarded as an "annotation", i.e. it does not have any impact on validation or other built-in SHACL features. However, selected tools may want to use this information.
The expected result(s) of a test case. The value range of this property is different for each kind of test cases.
A flag to indicate that the expected result represents a JSON string. If set to true, then tests would compare JSON structures (regardless of whitespaces) instead of actual syntax.
A flag to indicate that the expected result represents an RDF graph encoded as a Turtle file. If set to true, then tests would compare graphs instead of actual syntax.
Can be used to mark that certain validation results have already been fixed.
Properties marked as hidden do not appear in user interfaces, yet remain part of the shape for other purposes such as validation and scripting or GraphQL schema generation.
ASK { ?constraintOrShape sh:deactivated true . }
Checks whether a given shape or constraint has been marked as "deactivated" using sh:deactivated.
Features that have been marked stable are deemed of good quality and can be used until marked deprecated.
ASK { FILTER ($nodeKind IN ( sh:BlankNode, sh:BlankNodeOrIRI, sh:BlankNodeOrLiteral )) }
Checks if a given sh:NodeKind is one that includes BlankNodes.
ASK { FILTER ($nodeKind IN ( sh:IRI, sh:BlankNodeOrIRI, sh:IRIOrLiteral )) }
Checks if a given sh:NodeKind is one that includes IRIs.
ASK { FILTER ($nodeKind IN ( sh:Literal, sh:BlankNodeOrLiteral, sh:IRIOrLiteral )) }
Checks if a given sh:NodeKind is one that includes Literals.
ASK { $subclass rdfs:subClassOf* $superclass . }
Returns true if a given class (first argument) is a subclass of a given other class (second argument), or identical to that class. This is equivalent to an rdfs:subClassOf* check.
For file-typed properties, this can be used to specify the expected/allowed mime types of its values. This can be used, for example, to limit file input boxes or file selectors. If multiple values are allowed then they need to be separated by commas. Example values are listed at https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types
If set to true at a property shape then any sh:values and sh:defaultValue rules of this property will be ignored when 'all inferences' are computed. This is useful for property values that shall only be computed for individual focus nodes (e.g. when a user visits a resource) but not for large inference runs.
If set to true for a ScriptConstraint or ScriptValidator, then the associated script will receive all value nodes at once, as a value of the variable values. By default (or false), the script is called for each value node individually.
Links the constraint component with instances of dash:SuggestionGenerator that may be used to produce suggestions for a given validation result that was produced by a property constraint.
Used as a hint for user interfaces that values of the associated property should not be editable. The values of this may be the boolean literals true or false or, more generally, a SHACL node expression that must evaluate to true or false.
Links a class with the Resource Actions that can be applied to instances of that class.
States that a subject resource has a given shape. This property can, for example, be used to capture results of SHACL validation on static data.
Can be used to link a result with one or more suggestions on how to address or improve the underlying issue.
An optional confidence between 0% and 100%. Suggestions with 100% confidence are strongly recommended. Can be used to sort recommended updates.
Links a sh:SPARQLConstraint or sh:JSConstraint with instances of dash:SuggestionGenerator that may be used to produce suggestions for a given validation result that was produced by the constraint.
Can be used to link a suggestion with the group identifier to which it belongs. By default this is a link to the dash:SuggestionGenerator, but in principle this could be any value.
SELECT (xsd:string($arg) AS ?result) WHERE { }
Returns a literal with datatype xsd:string that has the input value as its string. If the input value is an (URI) resource then its URI will be used.
The literal value to insert into the template. Will use the URI-encoded string of the lexical form (for now).
The URI template, e.g. "http://example.org/{symbol}".
SELECT ?result WHERE { BIND (xsd:anyURI(REPLACE(?template, "\\{[a-zA-Z]+\\}", $value)) AS ?result) }
Inserts a given value into a given URI template, producing a new xsd:anyURI literal. In the future this should support RFC 6570 but for now it is limited to simple {...} patterns.
True to also validate the shapes itself (i.e. parameter declarations).
A test case that performs SHACL constraint validation on the whole graph and compares the results with the expected validation results stored with the test case. By default this excludes meta-validation (i.e. the validation of the shape definitions themselves). If that's desired, set dash:validateShapes to true.
The subject to get the number of objects of.
The predicate to get the number of objects of.
SELECT (COUNT(?object) AS ?result) WHERE { $subject $predicate ?object . }
Computes the number of objects for a given subject/predicate combination.
Can be used to link a property shape with a viewer, to state a preferred viewing widget in user interfaces.
The class of widgets for viewing value nodes.
ASK { $value rdf:type/rdfs:subClassOf* $class . }
Closed shape: only the enumerated properties can be used
Predicate {?path} is not allowed (closed shape)
SELECT $this (?predicate AS ?path) ?value WHERE { { FILTER ($closed) . } $this ?predicate ?value . FILTER (NOT EXISTS { GRAPH $shapesGraph { $currentShape sh:property/sh:path ?predicate . } } && (!bound($ignoredProperties) || NOT EXISTS { GRAPH $shapesGraph { $ignoredProperties rdf:rest*/rdf:first ?predicate . } })) }
Value does not have datatype {$datatype}
ASK { FILTER NOT EXISTS { $this $disjoint $value . } }
Property must not share any values with {$disjoint}
SELECT DISTINCT $this ?value WHERE { { FILTER NOT EXISTS { $this $equals $this } BIND ($this AS ?value) . } UNION { $this $equals ?value . FILTER (?value != $this) . } }
SELECT DISTINCT $this ?value WHERE { { $this $PATH ?value . MINUS { $this $equals ?value . } } UNION { $this $equals ?value . MINUS { $this $PATH ?value . } } }
SELECT $this WHERE { FILTER NOT EXISTS { $this $PATH $hasValue } }
ASK { GRAPH $shapesGraph { $in (rdf:rest*)/rdf:first $value . } }
Language must match any of {$languageIn}
Language does not match any of {$languageIn}
ASK { BIND (lang($value) AS ?valueLang) . FILTER EXISTS { GRAPH $shapesGraph { $languageIn (rdf:rest*)/rdf:first ?lang . FILTER (langMatches(?valueLang, ?lang)) } } }
SELECT $this ?value WHERE { $this $PATH ?value . $this $lessThan ?otherValue . BIND (?value < ?otherValue AS ?result) . FILTER (!bound(?result) || !(?result)) . }
Value is not <= value of {$lessThanOrEquals}
SELECT DISTINCT $this ?value WHERE { $this $PATH ?value . $this $lessThanOrEquals ?otherValue . BIND (?value <= ?otherValue AS ?result) . FILTER (!bound(?result) || !(?result)) . }
Must not have more than {$maxCount} values
SELECT $this WHERE { $this $PATH ?value . } GROUP BY $this HAVING (COUNT(DISTINCT ?value) > $maxCount)
Checks whether a given node (?value) has a value less than (<) the provided ?maxExclusive. Returns false if this cannot be determined, e.g. because values do not have comparable types.
ASK { FILTER ($value <= $maxInclusive) }
Checks whether a given node (?value) has a value less than or equal to (<=) the provided ?maxInclusive. Returns false if this cannot be determined, e.g. because values do not have comparable types.
Value must not have more than {$maxLength} characters
Value has more than {$maxLength} characters
ASK { FILTER (STRLEN(str($value)) <= $maxLength) . }
Checks whether a given string (?value) has a length within a given maximum string length.
SELECT $this WHERE { OPTIONAL { $this $PATH ?value . } } GROUP BY $this HAVING (COUNT(DISTINCT ?value) < $minCount)
Checks whether a given node (?value) has value greater than (>) the provided ?minExclusive. Returns false if this cannot be determined, e.g. because values do not have comparable types.
ASK { FILTER ($value >= $minInclusive) }
Checks whether a given node (?value) has value greater than or equal to (>=) the provided ?minInclusive. Returns false if this cannot be determined, e.g. because values do not have comparable types.
Value must have less than {$minLength} characters
Value has less than {$minLength} characters
ASK { FILTER (STRLEN(str($value)) >= $minLength) . }
Checks whether a given string (?value) has a length within a given minimum string length.
Value does not have node kind {$nodeKind}
ASK { FILTER ((isIRI($value) && $nodeKind IN ( sh:IRI, sh:BlankNodeOrIRI, sh:IRIOrLiteral ) ) || (isLiteral($value) && $nodeKind IN ( sh:Literal, sh:BlankNodeOrLiteral, sh:IRIOrLiteral ) ) || (isBlank($value) && $nodeKind IN ( sh:BlankNode, sh:BlankNodeOrIRI, sh:BlankNodeOrLiteral ) )) . }
Checks whether a given node (?value) has a given sh:NodeKind (?nodeKind). For example, sh:hasNodeKind(42, sh:Literal) = true.
Value does not match pattern "{$pattern}"
ASK { FILTER (!isBlank($value) && IF(bound($flags), regex(str($value), $pattern, $flags), regex(str($value), $pattern))) }
Checks whether the string representation of a given node (?value) matches a given regular expression (?pattern). Returns false if the value is a blank node.
No more than {$qualifiedMaxCount} values can have shape {$qualifiedValueShape}
More than {$qualifiedMaxCount} values have shape {$qualifiedValueShape}
No fewer than {$qualifiedMinCount} values can have shape {$qualifiedValueShape}
Fewer than {$qualifiedMinCount} values have shape {$qualifiedValueShape}
SELECT DISTINCT $this ?lang WHERE { { FILTER sameTerm($uniqueLang, true) . } $this $PATH ?value . BIND (lang(?value) AS ?lang) . FILTER (bound(?lang) && ?lang != "") . FILTER EXISTS { $this $PATH ?otherValue . FILTER (?otherValue != ?value && ?lang = lang(?otherValue)) . } }
Can be used to specify the node shape that may be applied to reified statements produced by a property shape. The property shape must have a URI resource as its sh:path. The values of this property must be node shapes. User interfaces can use this information to determine which properties to present to users when reified statements are explored or edited. Use dash:None to indicate that no reification should be permitted.
Can be used to attach sh:severity and sh:messages to individual constraints using reification.
An editor for properties that are either defined as instances of rdf:Property or used as IRI values of sh:path. The component uses auto-complete to find these properties by their schema:names or sh:names.
A viewer for properties that renders a hyperlink using the display label or sh:name, allowing users to either navigate to the rdf:Property resource or the property shape definition. Should be used in conjunction with PropertyAutoCompleteEditor.
Specifies a property that must have a value whenever the property path has a value, and must have no value whenever the property path has no value.
An rdf:List that can be used in property constraints as value for sh:or to indicate that all values of a property must be either xsd:string or rdf:langString.
Abstract superclass for test cases concerning SHACL constraint validation. Future versions may add new kinds of validatin test cases, e.g. to validate a single resource only.
Each list member (including this node) must be have the shape dash:ListNodeShape.
Defines constraints on what it means for a node to be a well-formed RDF list. The focus node must either be rdf:nil or not recursive. Furthermore, this shape uses dash:ListNodeShape as a "helper" to walk through all members of the whole list (including itself).
Specifies a constraint that at least one of the value nodes must be a member of the given list.
Specifies a constraint that at least one of the value nodes must be an instance of a given class.
Defines constraints on what it means for a node to be a node within a well-formed RDF list. Note that this does not check whether the rdf:rest items are also well-formed lists as this would lead to unsupported recursion.
The class of constraints that are based on Scripts. Depending on whether dash:onAllValues is set to true, these scripts can access the following pre-assigned variables: - focusNode: the focus node of the constraint (a NamedNode) - if dash:onAllValues is not true: value: the current value node (e.g. a JavaScript string for xsd:string literals, a number for numeric literals or true or false for xsd:boolean literals. All other literals become LiteralNodes, and non-literals become instances of NamedNode) - if dash:onAllValues is true: values: an array of current value nodes, as above. If the expression returns an array then each array member will be mapped to one validation result, following the mapping rules below. For string results, a validation result will use the string as sh:resultMessage. For boolean results, a validation result will be produced if the result is false (true means no violation). For object results, a validation result will be produced using the value of the field "message" of the object as result message. If the field "value" has a value then this will become the sh:value in the violation. Unless another sh:message has been directly returned, the sh:message of the dash:ScriptConstraint will be used, similar to sh:message at SPARQL Constraints. These sh:messages can access the values {$focusNode}, {$value} etc as template variables.
Specifies a string value that the IRI of the value nodes must start with.
stem
True to declare that the associated property path is symmetric.
Base class of user interface components that can be used to display or edit value nodes.
TERN's ecologists have determined the feature type is _landform_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/2cf3ed29-440e-4a50-9bbc-5aab30df9fcd[`landform`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0e0423c6-0dc3-40aa-9776-410a94299256>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0e0423c6-0dc3-40aa-9776-410a94299256> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
Observations following the Acoustics and Ultrasound Protocol are made in the context of a site visit.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0e0423c6-0dc3-40aa-9776-410a94299256>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
Result value's unit of measure _MUST_ have the value `unit:DEG`.
The result _MUST_ have `unit:DEG` as the value for `tern:unit`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0e0423c6-0dc3-40aa-9776-410a94299256> ; sosa:hasResult ?this . }
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/a15130ca-82ce-4c50-9392-66f9b0c73450>`. `<https://linked.data.gov.au/def/nrm/a15130ca-82ce-4c50-9392-66f9b0c73450>` is the IRI for "Acoustics and Ultrasound Protocol".
The procedure's `tern:methodType` _MUST_ have the value `https://linked.data.gov.au/def/nrm/a15130ca-82ce-4c50-9392-66f9b0c73450`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0e0423c6-0dc3-40aa-9776-410a94299256>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 0 inclusive and 360 inclusive.
The result _MUST_ have a value between 0 inclusive and 360 inclusive.
TERN's ecologists have determined the feature type is _land surface_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/8282fb22-4135-415c-8ca2-317860d102fb[`land surface`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b4db8328-1f0e-4428-813a-c716459ca9a5>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/b4db8328-1f0e-4428-813a-c716459ca9a5> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b4db8328-1f0e-4428-813a-c716459ca9a5>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/b4db8328-1f0e-4428-813a-c716459ca9a5> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b4db8328-1f0e-4428-813a-c716459ca9a5>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/5b60730b-d6e1-4339-90c0-8e740230f9ae> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5b60730b-d6e1-4339-90c0-8e740230f9ae>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/5b60730b-d6e1-4339-90c0-8e740230f9ae> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5b60730b-d6e1-4339-90c0-8e740230f9ae>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5b60730b-d6e1-4339-90c0-8e740230f9ae>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/616fdcea-b3fd-47b2-8ed9-2108de41f5b8> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/616fdcea-b3fd-47b2-8ed9-2108de41f5b8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/616fdcea-b3fd-47b2-8ed9-2108de41f5b8> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/616fdcea-b3fd-47b2-8ed9-2108de41f5b8>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/616fdcea-b3fd-47b2-8ed9-2108de41f5b8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/cf1aef8a-a782-4480-9c41-a7f6d170d7fc>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Fire history types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Fire history types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/cf1aef8a-a782-4480-9c41-a7f6d170d7fc> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'6e9d2f51-ce64-4c67-8391-d14a8bf96b6b'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/cf1aef8a-a782-4480-9c41-a7f6d170d7fc> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/cf1aef8a-a782-4480-9c41-a7f6d170d7fc>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/cf1aef8a-a782-4480-9c41-a7f6d170d7fc>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/6e9d2f51-ce64-4c67-8391-d14a8bf96b6b>`. `<https://linked.data.gov.au/def/nrm/6e9d2f51-ce64-4c67-8391-d14a8bf96b6b>` is the IRI for "Fire history types".
The value of `tern:vocabulary` _MUST_ match the pattern `6e9d2f51-ce64-4c67-8391-d14a8bf96b6b$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/325d5ff2-8c81-484a-a422-c13ff29666a9>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/325d5ff2-8c81-484a-a422-c13ff29666a9> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/325d5ff2-8c81-484a-a422-c13ff29666a9>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/325d5ff2-8c81-484a-a422-c13ff29666a9> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/325d5ff2-8c81-484a-a422-c13ff29666a9>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/57be29f6-1c6a-5c4d-89f2-00b21d4f4178> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/57be29f6-1c6a-5c4d-89f2-00b21d4f4178>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/57be29f6-1c6a-5c4d-89f2-00b21d4f4178> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/57be29f6-1c6a-5c4d-89f2-00b21d4f4178>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/57be29f6-1c6a-5c4d-89f2-00b21d4f4178>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/372ec5c5-79da-44a9-a56e-dd9ab311da06>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Australian Land Use and Management Classification controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Australian Land Use and Management Classification controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/372ec5c5-79da-44a9-a56e-dd9ab311da06> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/372ec5c5-79da-44a9-a56e-dd9ab311da06> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/372ec5c5-79da-44a9-a56e-dd9ab311da06>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/a15130ca-82ce-4c50-9392-66f9b0c73450>`. # `<https://linked.data.gov.au/def/nrm/a15130ca-82ce-4c50-9392-66f9b0c73450>` is the IRI for "Acoustics and Ultrasound Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/a15130ca-82ce-4c50-9392-66f9b0c73450`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/372ec5c5-79da-44a9-a56e-dd9ab311da06>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/9d4f8a2d-8e77-42dd-857b-0ecbc9c85696>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Landform element types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Landform element types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/9d4f8a2d-8e77-42dd-857b-0ecbc9c85696> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'c1a58967-cb12-4c2c-a7ca-9cee2589919c'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/9d4f8a2d-8e77-42dd-857b-0ecbc9c85696> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/9d4f8a2d-8e77-42dd-857b-0ecbc9c85696>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/9d4f8a2d-8e77-42dd-857b-0ecbc9c85696>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/c1a58967-cb12-4c2c-a7ca-9cee2589919c>`. `<https://linked.data.gov.au/def/nrm/c1a58967-cb12-4c2c-a7ca-9cee2589919c>` is the IRI for "Landform element types".
The value of `tern:vocabulary` _MUST_ match the pattern `c1a58967-cb12-4c2c-a7ca-9cee2589919c$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/58e4aba5-78c3-4361-b08a-ae39a93c8cb0>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the landform pattern types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the landform pattern types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/58e4aba5-78c3-4361-b08a-ae39a93c8cb0> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'19d91a7a-2733-4b84-9d2b-4bda4808c003'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/58e4aba5-78c3-4361-b08a-ae39a93c8cb0> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/58e4aba5-78c3-4361-b08a-ae39a93c8cb0>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/58e4aba5-78c3-4361-b08a-ae39a93c8cb0>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/19d91a7a-2733-4b84-9d2b-4bda4808c003>`. `<https://linked.data.gov.au/def/nrm/19d91a7a-2733-4b84-9d2b-4bda4808c003>` is the IRI for "landform pattern types".
The value of `tern:vocabulary` _MUST_ match the pattern `19d91a7a-2733-4b84-9d2b-4bda4808c003$`.
The value in `sosa:hasResult` _MUST_ be xsd:boolean.
The value of `rdf:value` _MUST_ have the datatype xsd:boolean.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/88c2fec1-d37a-5f5c-8850-3cc052c192f7> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/88c2fec1-d37a-5f5c-8850-3cc052c192f7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/88c2fec1-d37a-5f5c-8850-3cc052c192f7> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/88c2fec1-d37a-5f5c-8850-3cc052c192f7>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/88c2fec1-d37a-5f5c-8850-3cc052c192f7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
The value of `sosa:hasResult` _MUST_ be a `tern:Boolean`.
The result _MUST_ be an instance of `tern:Boolean`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8886590d-f947-4504-aff7-3eec5db03c9d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the intensive uses controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the intensive uses controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/8886590d-f947-4504-aff7-3eec5db03c9d> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/8886590d-f947-4504-aff7-3eec5db03c9d> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8886590d-f947-4504-aff7-3eec5db03c9d>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8886590d-f947-4504-aff7-3eec5db03c9d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/148f60c9-92c5-4324-81b6-61b59bccdb4c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil reliefs controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil reliefs controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/148f60c9-92c5-4324-81b6-61b59bccdb4c> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'9e377f67-190e-4d58-9ec9-adebedaf14e2'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/148f60c9-92c5-4324-81b6-61b59bccdb4c> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/148f60c9-92c5-4324-81b6-61b59bccdb4c>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/148f60c9-92c5-4324-81b6-61b59bccdb4c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/9e377f67-190e-4d58-9ec9-adebedaf14e2>`. `<https://linked.data.gov.au/def/nrm/9e377f67-190e-4d58-9ec9-adebedaf14e2>` is the IRI for "Soil reliefs".
The value of `tern:vocabulary` _MUST_ match the pattern `9e377f67-190e-4d58-9ec9-adebedaf14e2$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/632e4c3c-0e73-4b3d-b1d6-7b38897da5e8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the disturbance types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the disturbance types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/632e4c3c-0e73-4b3d-b1d6-7b38897da5e8> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'f5a470e8-d29f-4ff6-b50d-529b0444dbe4'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/632e4c3c-0e73-4b3d-b1d6-7b38897da5e8> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/632e4c3c-0e73-4b3d-b1d6-7b38897da5e8>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/632e4c3c-0e73-4b3d-b1d6-7b38897da5e8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/f5a470e8-d29f-4ff6-b50d-529b0444dbe4>`. `<https://linked.data.gov.au/def/nrm/f5a470e8-d29f-4ff6-b50d-529b0444dbe4>` is the IRI for "disturbance types".
The value of `tern:vocabulary` _MUST_ match the pattern `f5a470e8-d29f-4ff6-b50d-529b0444dbe4$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/103f26cb-0194-45d2-8b1a-e18e1da6df2b>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Vegetation structural formation types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Vegetation structural formation types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/103f26cb-0194-45d2-8b1a-e18e1da6df2b> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'6e9baf51-566e-4a5d-93c4-a6e097dc364d'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/103f26cb-0194-45d2-8b1a-e18e1da6df2b> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/103f26cb-0194-45d2-8b1a-e18e1da6df2b>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/103f26cb-0194-45d2-8b1a-e18e1da6df2b>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/6e9baf51-566e-4a5d-93c4-a6e097dc364d>`. `<https://linked.data.gov.au/def/nrm/6e9baf51-566e-4a5d-93c4-a6e097dc364d>` is the IRI for "Vegetation structural formation types".
The value of `tern:vocabulary` _MUST_ match the pattern `6e9baf51-566e-4a5d-93c4-a6e097dc364d$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a2c2f997-46c0-5c64-aca0-a43e624cf8d5>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the vegetation age structure classes controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the vegetation age structure classes controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/a2c2f997-46c0-5c64-aca0-a43e624cf8d5> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'30985f0b-095b-50ee-8dfe-f872f73ea5a0'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/a2c2f997-46c0-5c64-aca0-a43e624cf8d5> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a2c2f997-46c0-5c64-aca0-a43e624cf8d5>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a2c2f997-46c0-5c64-aca0-a43e624cf8d5>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/30985f0b-095b-50ee-8dfe-f872f73ea5a0>`. `<https://linked.data.gov.au/def/nrm/30985f0b-095b-50ee-8dfe-f872f73ea5a0>` is the IRI for "vegetation age structure classes".
The value of `tern:vocabulary` _MUST_ match the pattern `30985f0b-095b-50ee-8dfe-f872f73ea5a0$`.
Observations following the Active and Passive Search Protocol are made in the context of a site visit.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/37ed2dbb-b990-430c-9010-d0452588cf24>`. `<https://linked.data.gov.au/def/nrm/37ed2dbb-b990-430c-9010-d0452588cf24>` is the IRI for "Active and Passive Search Protocol".
The procedure's `tern:methodType` _MUST_ have the value `https://linked.data.gov.au/def/nrm/37ed2dbb-b990-430c-9010-d0452588cf24`.
TERN's ecologists have determined the feature type is _animal evidence_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/4507e510-bf25-467b-a97e-abd56776507a[`animal evidence`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/ab6c601a-49a2-5287-8d7b-164ff8cdc791> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ab6c601a-49a2-5287-8d7b-164ff8cdc791>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/ab6c601a-49a2-5287-8d7b-164ff8cdc791> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ab6c601a-49a2-5287-8d7b-164ff8cdc791>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ab6c601a-49a2-5287-8d7b-164ff8cdc791>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0bc353aa-f678-5948-9fe7-6e0c39b2a6d6> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0bc353aa-f678-5948-9fe7-6e0c39b2a6d6>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0bc353aa-f678-5948-9fe7-6e0c39b2a6d6> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0bc353aa-f678-5948-9fe7-6e0c39b2a6d6>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0bc353aa-f678-5948-9fe7-6e0c39b2a6d6>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/a46d4478-4512-5a91-a4c9-a8f7720b38ed> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/ac5a20c2-64f7-5335-b080-a6aacb92e5d8> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
TERN's ecologists have determined the feature type is _animal occurrence_ or _animal evidence, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/2361dea8-598c-4b6f-a641-2b98ff199e9e[`animal occurrence`] or link: http://linked.data.gov.au/def/tern-cv/4507e510-bf25-467b-a97e-abd56776507a[`animal evidence`].
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the fauna growth classes controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the fauna growth classes controlled vocabulary.
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/0e2641c3-0d7e-4d94-8cd7-02c21d564630>`. `<https://linked.data.gov.au/def/nrm/0e2641c3-0d7e-4d94-8cd7-02c21d564630>` is the IRI for "fauna growth classes".
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/7905c3ec-3901-4fb9-a042-b83066bee975>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/7905c3ec-3901-4fb9-a042-b83066bee975> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/7905c3ec-3901-4fb9-a042-b83066bee975>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/7905c3ec-3901-4fb9-a042-b83066bee975> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/7905c3ec-3901-4fb9-a042-b83066bee975>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/2c77369c-c827-506c-bc1a-0ec328029747>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Fauna reproductive status types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Fauna reproductive status types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/2c77369c-c827-506c-bc1a-0ec328029747> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'8d7c2dec-d8ba-5369-9b3b-be3ce76fec88'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/2c77369c-c827-506c-bc1a-0ec328029747> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/2c77369c-c827-506c-bc1a-0ec328029747>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/2c77369c-c827-506c-bc1a-0ec328029747>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/8d7c2dec-d8ba-5369-9b3b-be3ce76fec88>`. `<https://linked.data.gov.au/def/nrm/8d7c2dec-d8ba-5369-9b3b-be3ce76fec88>` is the IRI for "Fauna reproductive status types".
The value of `tern:vocabulary` _MUST_ match the pattern `8d7c2dec-d8ba-5369-9b3b-be3ce76fec88$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/de87eddf-1d65-57ed-99af-271f1458054d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Fauna sign ages controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Fauna sign ages controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/de87eddf-1d65-57ed-99af-271f1458054d> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'292b1cf8-6f25-514f-8a94-6d7d690335ed'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/de87eddf-1d65-57ed-99af-271f1458054d> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/de87eddf-1d65-57ed-99af-271f1458054d>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/de87eddf-1d65-57ed-99af-271f1458054d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/292b1cf8-6f25-514f-8a94-6d7d690335ed>`. `<https://linked.data.gov.au/def/nrm/292b1cf8-6f25-514f-8a94-6d7d690335ed>` is the IRI for "Fauna sign ages".
The value of `tern:vocabulary` _MUST_ match the pattern `292b1cf8-6f25-514f-8a94-6d7d690335ed$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3611c2c3-8347-5556-b6a2-ed1d17b0b5c7> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3611c2c3-8347-5556-b6a2-ed1d17b0b5c7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3611c2c3-8347-5556-b6a2-ed1d17b0b5c7> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3611c2c3-8347-5556-b6a2-ed1d17b0b5c7>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3611c2c3-8347-5556-b6a2-ed1d17b0b5c7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/27f979fe-7285-50cb-ab92-44a0bdd0f56c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Fauna sign types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Fauna sign types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/27f979fe-7285-50cb-ab92-44a0bdd0f56c> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'bc7eaeab-ff7c-5d54-aa41-a11003d7fff0'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/27f979fe-7285-50cb-ab92-44a0bdd0f56c> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/27f979fe-7285-50cb-ab92-44a0bdd0f56c>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/27f979fe-7285-50cb-ab92-44a0bdd0f56c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/bc7eaeab-ff7c-5d54-aa41-a11003d7fff0>`. `<https://linked.data.gov.au/def/nrm/bc7eaeab-ff7c-5d54-aa41-a11003d7fff0>` is the IRI for "Fauna sign types".
The value of `tern:vocabulary` _MUST_ match the pattern `bc7eaeab-ff7c-5d54-aa41-a11003d7fff0$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/d964ff76-9a75-5a12-87c2-a355545ca107> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/96ccc2b7-7b7f-4e5c-b11f-d5e5c88e245a> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3996d3ba-0812-55a4-9b27-4498ffb75e52> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
TERN's ecologists have determined the feature type is _animal population_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/8a68b4a9-167b-40f0-9222-293a2d20ffee[`animal population`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b2d28629-c986-4c05-9d4a-8b05e99a0a94>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/b2d28629-c986-4c05-9d4a-8b05e99a0a94> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b2d28629-c986-4c05-9d4a-8b05e99a0a94>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b2d28629-c986-4c05-9d4a-8b05e99a0a94>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
The result _MUST_ be a positive integer.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/b2d28629-c986-4c05-9d4a-8b05e99a0a94> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dd805508-1eca-5b8b-b2e4-c51c1682e81e>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/dd805508-1eca-5b8b-b2e4-c51c1682e81e> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dd805508-1eca-5b8b-b2e4-c51c1682e81e>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dd805508-1eca-5b8b-b2e4-c51c1682e81e>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/dd805508-1eca-5b8b-b2e4-c51c1682e81e> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c497a8eb-f720-52a4-bc76-8ec1cf7d4cf2>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/c497a8eb-f720-52a4-bc76-8ec1cf7d4cf2> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c497a8eb-f720-52a4-bc76-8ec1cf7d4cf2>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c497a8eb-f720-52a4-bc76-8ec1cf7d4cf2>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/c497a8eb-f720-52a4-bc76-8ec1cf7d4cf2> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/26147520-7e7c-5b55-b2fa-197a02b7ab33>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/26147520-7e7c-5b55-b2fa-197a02b7ab33> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/26147520-7e7c-5b55-b2fa-197a02b7ab33>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/26147520-7e7c-5b55-b2fa-197a02b7ab33>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/26147520-7e7c-5b55-b2fa-197a02b7ab33> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/38d1419f-7f3b-4d0e-a2f6-4b152e2d91f7> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/f16897cb-7775-55fb-9ba4-3239b2927260>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/f16897cb-7775-55fb-9ba4-3239b2927260> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/f16897cb-7775-55fb-9ba4-3239b2927260>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/f16897cb-7775-55fb-9ba4-3239b2927260> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/f16897cb-7775-55fb-9ba4-3239b2927260>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/dd7529e4-24ae-53a9-b7a6-94674c4b92c5> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dd7529e4-24ae-53a9-b7a6-94674c4b92c5>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/dd7529e4-24ae-53a9-b7a6-94674c4b92c5> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dd7529e4-24ae-53a9-b7a6-94674c4b92c5>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dd7529e4-24ae-53a9-b7a6-94674c4b92c5>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Observations following the Bird Survey Protocol are made in the context of a site visit.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/98db8232-2c51-4907-99a7-0ccb8b825382>`. `<https://linked.data.gov.au/def/nrm/98db8232-2c51-4907-99a7-0ccb8b825382>` is the IRI for "Bird Survey Protocol".
The procedure's `tern:methodType` _MUST_ have the value `https://linked.data.gov.au/def/nrm/98db8232-2c51-4907-99a7-0ccb8b825382`.
TERN's ecologists have determined the feature type is _bird occurrence_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/0c30e871-63ae-4f84-a37c-ef6e7ce02928[`bird occurrence`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/045fa754-487a-4346-8128-403c646a903b>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Fauna bird activities controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Fauna bird activities controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/045fa754-487a-4346-8128-403c646a903b> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'c7a51f30-97e8-4232-b1f3-a248d58f1a60'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/045fa754-487a-4346-8128-403c646a903b> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/045fa754-487a-4346-8128-403c646a903b>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/045fa754-487a-4346-8128-403c646a903b>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/c7a51f30-97e8-4232-b1f3-a248d58f1a60>`. `<https://linked.data.gov.au/def/nrm/c7a51f30-97e8-4232-b1f3-a248d58f1a60>` is the IRI for "Fauna bird activities".
The value of `tern:vocabulary` _MUST_ match the pattern `c7a51f30-97e8-4232-b1f3-a248d58f1a60$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/72cca5e4-2dc6-4a96-92e3-6f1e844b243c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Fauna bird breeding types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Fauna bird breeding types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/72cca5e4-2dc6-4a96-92e3-6f1e844b243c> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'028f570d-0cf0-4e94-b288-ac8d852f2230'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/72cca5e4-2dc6-4a96-92e3-6f1e844b243c> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/72cca5e4-2dc6-4a96-92e3-6f1e844b243c>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/72cca5e4-2dc6-4a96-92e3-6f1e844b243c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/028f570d-0cf0-4e94-b288-ac8d852f2230>`. `<https://linked.data.gov.au/def/nrm/028f570d-0cf0-4e94-b288-ac8d852f2230>` is the IRI for "Fauna bird breeding types".
The value of `tern:vocabulary` _MUST_ match the pattern `028f570d-0cf0-4e94-b288-ac8d852f2230$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0bc0fae9-6243-4d9f-a547-ef4c36244b5d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Fauna maturity types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Fauna maturity types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0bc0fae9-6243-4d9f-a547-ef4c36244b5d> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'a01656de-9627-4067-ad09-269242badbcb'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0bc0fae9-6243-4d9f-a547-ef4c36244b5d> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0bc0fae9-6243-4d9f-a547-ef4c36244b5d>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0bc0fae9-6243-4d9f-a547-ef4c36244b5d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/a01656de-9627-4067-ad09-269242badbcb>`. `<https://linked.data.gov.au/def/nrm/a01656de-9627-4067-ad09-269242badbcb>` is the IRI for "Fauna maturity types".
The value of `tern:vocabulary` _MUST_ match the pattern `a01656de-9627-4067-ad09-269242badbcb$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/d78e0ad6-9ac8-4adc-a796-61ad458726b3> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
Observations following the Identify, Measure and Release Protocol are made in the context of a site visit.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/7942c1d3-8cfc-4d74-931d-850cacfa5a63>`. `<https://linked.data.gov.au/def/nrm/7942c1d3-8cfc-4d74-931d-850cacfa5a63>` is the IRI for "Identify, Measure and Release Protocol".
The procedure's `tern:methodType` _MUST_ have the value `https://linked.data.gov.au/def/nrm/7942c1d3-8cfc-4d74-931d-850cacfa5a63`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c1d7f32d-bd8a-541f-9907-31dd7bb987fb>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Body condition scores controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Body condition scores controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/c1d7f32d-bd8a-541f-9907-31dd7bb987fb> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'90a0f5d0-0ac9-5723-acc5-f1c3ce8cd57e'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/c1d7f32d-bd8a-541f-9907-31dd7bb987fb> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c1d7f32d-bd8a-541f-9907-31dd7bb987fb>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c1d7f32d-bd8a-541f-9907-31dd7bb987fb>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/90a0f5d0-0ac9-5723-acc5-f1c3ce8cd57e>`. `<https://linked.data.gov.au/def/nrm/90a0f5d0-0ac9-5723-acc5-f1c3ce8cd57e>` is the IRI for "Body condition scores".
The value of `tern:vocabulary` _MUST_ match the pattern `90a0f5d0-0ac9-5723-acc5-f1c3ce8cd57e$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/683f7d77-f500-57f9-89b4-a712e866aad9>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Severity classes of chemosis of eyes controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Severity classes of chemosis of eyes controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/683f7d77-f500-57f9-89b4-a712e866aad9> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'e98fc5ff-8590-562d-800b-27d3d98838b2'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/683f7d77-f500-57f9-89b4-a712e866aad9> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/683f7d77-f500-57f9-89b4-a712e866aad9>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/683f7d77-f500-57f9-89b4-a712e866aad9>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/e98fc5ff-8590-562d-800b-27d3d98838b2>`. `<https://linked.data.gov.au/def/nrm/e98fc5ff-8590-562d-800b-27d3d98838b2>` is the IRI for "Severity classes of chemosis of eyes".
The value of `tern:vocabulary` _MUST_ match the pattern `e98fc5ff-8590-562d-800b-27d3d98838b2$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a58232bf-f332-509e-91b2-1077478692e5>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Fauna skin conditions controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Fauna skin conditions controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/a58232bf-f332-509e-91b2-1077478692e5> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'d77cb420-ad25-5feb-a59e-54e284fdf527'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/a58232bf-f332-509e-91b2-1077478692e5> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a58232bf-f332-509e-91b2-1077478692e5>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a58232bf-f332-509e-91b2-1077478692e5>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/d77cb420-ad25-5feb-a59e-54e284fdf527>`. `<https://linked.data.gov.au/def/nrm/d77cb420-ad25-5feb-a59e-54e284fdf527>` is the IRI for "Fauna skin conditions".
The value of `tern:vocabulary` _MUST_ match the pattern `d77cb420-ad25-5feb-a59e-54e284fdf527$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3600234c-2736-564d-ac18-ba24a13abea8> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3600234c-2736-564d-ac18-ba24a13abea8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3600234c-2736-564d-ac18-ba24a13abea8> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3600234c-2736-564d-ac18-ba24a13abea8>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3600234c-2736-564d-ac18-ba24a13abea8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/fe18c3aa-7af1-4fe8-bf5f-dcec29a3bea9>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/fe18c3aa-7af1-4fe8-bf5f-dcec29a3bea9> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/fe18c3aa-7af1-4fe8-bf5f-dcec29a3bea9>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/fe18c3aa-7af1-4fe8-bf5f-dcec29a3bea9> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/fe18c3aa-7af1-4fe8-bf5f-dcec29a3bea9>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/4f0ba64d-3c21-5f98-8a42-39e6efd33430>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Pouch young statuses controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Pouch young statuses controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/4f0ba64d-3c21-5f98-8a42-39e6efd33430> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'3b5820d3-bdbd-57a3-a177-d6381d6d66fe'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/4f0ba64d-3c21-5f98-8a42-39e6efd33430> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/4f0ba64d-3c21-5f98-8a42-39e6efd33430>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/4f0ba64d-3c21-5f98-8a42-39e6efd33430>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/3b5820d3-bdbd-57a3-a177-d6381d6d66fe>`. `<https://linked.data.gov.au/def/nrm/3b5820d3-bdbd-57a3-a177-d6381d6d66fe>` is the IRI for "Pouch young statuses".
The value of `tern:vocabulary` _MUST_ match the pattern `3b5820d3-bdbd-57a3-a177-d6381d6d66fe$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/68135f54-5e76-56b0-8496-75a078b839e6>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Severity classes of proliferation of eyes controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Severity classes of proliferation of eyes controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/68135f54-5e76-56b0-8496-75a078b839e6> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'65a0b138-bf44-5cd8-94fe-3b48786d4afd'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/68135f54-5e76-56b0-8496-75a078b839e6> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/68135f54-5e76-56b0-8496-75a078b839e6>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/68135f54-5e76-56b0-8496-75a078b839e6>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/65a0b138-bf44-5cd8-94fe-3b48786d4afd>`. `<https://linked.data.gov.au/def/nrm/65a0b138-bf44-5cd8-94fe-3b48786d4afd>` is the IRI for "Severity classes of proliferation of eyes".
The value of `tern:vocabulary` _MUST_ match the pattern `65a0b138-bf44-5cd8-94fe-3b48786d4afd$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0890f6e8-025d-5dd3-96f7-a7e6599335ea>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Testes sizes controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Testes sizes controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0890f6e8-025d-5dd3-96f7-a7e6599335ea> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'dd9b41aa-a409-5f8e-9d5a-0a6a756c8610'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0890f6e8-025d-5dd3-96f7-a7e6599335ea> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0890f6e8-025d-5dd3-96f7-a7e6599335ea>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0890f6e8-025d-5dd3-96f7-a7e6599335ea>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/dd9b41aa-a409-5f8e-9d5a-0a6a756c8610>`. `<https://linked.data.gov.au/def/nrm/dd9b41aa-a409-5f8e-9d5a-0a6a756c8610>` is the IRI for "Testes sizes".
The value of `tern:vocabulary` _MUST_ match the pattern `dd9b41aa-a409-5f8e-9d5a-0a6a756c8610$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/49d16413-623a-57f8-aa7c-a1bb813ecb55>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/49d16413-623a-57f8-aa7c-a1bb813ecb55> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/49d16413-623a-57f8-aa7c-a1bb813ecb55>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/49d16413-623a-57f8-aa7c-a1bb813ecb55> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/49d16413-623a-57f8-aa7c-a1bb813ecb55>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8997be1e-cf91-4ca6-a641-eb57aa10d9e6>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Vertebrate class types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Vertebrate class types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/8997be1e-cf91-4ca6-a641-eb57aa10d9e6> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'c6962b15-f7ce-46a8-bb5c-04d501d92262'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/8997be1e-cf91-4ca6-a641-eb57aa10d9e6> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8997be1e-cf91-4ca6-a641-eb57aa10d9e6>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8997be1e-cf91-4ca6-a641-eb57aa10d9e6>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/c6962b15-f7ce-46a8-bb5c-04d501d92262>`. `<https://linked.data.gov.au/def/nrm/c6962b15-f7ce-46a8-bb5c-04d501d92262>` is the IRI for "Vertebrate class types".
The value of `tern:vocabulary` _MUST_ match the pattern `c6962b15-f7ce-46a8-bb5c-04d501d92262$`.
5.6 2023-05: Test that broader/narrower indicates a Concept in this vocab (2.3.02), allow topConceptOf or hasTopConcept for 2.1.08 & 2.3.03; use same test for 2.1.08 & 2.3.03 5.5 2026-02: Added Shapes for Reqs 2.3.10 - 2.3.19 5.4 2026-02: Small fixes for a number of Issues raised in the Issue Tracker 5.3 ValPub valid. All propertyShape instances have IRIs, are not Blank Nodes. All Shapes have names & messages. SHACL-UI elements moved to shaclui.ttl 5.2 Implement Shape 2.1.2+3 using qualified shape pattern as this is supported by pySHACL 5.1 Remove targetNode -> ConceptScheme shape, use schema:, not schema: 5.0 Change IRI to linked.data.gov.au 4.11 Add VocEdit SHACL UI shapes and RDF statements 4.10 move all warning from PropertyShapes to NodeShapes 4.9 Fixed RDF syntax errors 4.8 Fixed Warning/Violation error for PropertyShapes 4.7 Fixed modified date alternate path listing bug 4.6 Fixed schema:historyNote->skos:historyNote bug 4.5 Added suggested predicates of license & copyrightHolder 4.4 Fixed versions across multiple Resources 4.3 Improved validator error messages by using more named Property Shapes 4.2: Included CONSTRUCT-based pre-validation inference in validator. First Git tagged version 4.1: Added Requirements 2.1.10, 2.1.11 & 2.1.12 and example RDF 4.0: Added a SPARQL function to allow for the inferencing of skos:inScheme predicates, skos:broader / skos:narrower and skos:topConceptOf/skos:hasTopConcept pairs of inverse predicates 3.3: Converted validator metadata to schema.org, enabled bibliographic references for Concepts, enabled DCTERMS or schema.org for many ConceptScheme predicates; simplified 2.1.6 from two Requirements to one; included skos:topConceptOf in 2.1.8 for Concepts at the top of the hierarchy; collapsed title & definition requirement pairs to single requirements 3.2: Allowed dcterms:provenance and skos:historyNote; removed max restriction on dcterms:source & prov:wasDerivedFrom 3.1: Changed dcterms:provenance to skos:historyNote 3.0: Removed Requirement-2.3.5 (identifiers) as these are auto-generated in systems like VocPrez; Added Requirement-2.1.10 & 2.1.11 and sub parts to test for qualifiedDerivation and status of a ConceptScheme
Created to validate Australian government vocabularies in 2020. Now used widely.
Requirement 2.1.11 The derivation status of the vocabulary SHOULD be given should be given with the predicate prov:qualifiedDerivation indicating a Blank Node that contains the predicated prov:entity, to indicate the vocabulary derived from and prov:hadRole to indicate the mode of derivation which SHOULD be taken from the Vocabulary Derivation Modes vocabulary (https://linked.data.gov.au/def/vocdermods)
Requirement 2.1.02 Each vocabulary MUST be presented as a single Concept Scheme object & Requirement 2.1.3 Each vocabulary MUST be presented in a single RDF file which does not contain information other than that which is directly part of the vocabulary
Requirement 2.1.04, 2.2.01 or 2.3.01 Each vocabulary, Collection or Concept MUST have exactly one title and at least one definition indicated using the skos:prefLabel and the skos:definition predicates respectively that must give textual literal values. Only one definition per language is allowed
Requirement 2.1.04, 2.2.1 or 2.3.1 Each vocabulary, Collection or Concept MUST have exactly one title and at least one definition indicated using the skos:prefLabel and the skos:definition predicates respectively that must give textual literal values. Only one definition per language is allowed
Requirement 2.15 - created date - violated
Requirement 2.15 - modified date - violated
Requirement 2.1.06 Each vocabulary MUST have at least one creator, indicated using schema:creator or dcterms:creator predicate and exactly one publisher, indicated using schema:publisher or dcterms:publisher, all of which MUST be IRIs indicating instances of schema:Person, or schema:Organization. This error message is for creator
Requirement 2.1.06 Each vocabulary MUST have at least one creator, indicated using schema:creator or dcterms:creator predicate and exactly one publisher, indicated using schema:publisher or dcterms:publisher, all of which MUST be IRIs indicating instances of schema:Person, or schema:Organization. This error message is for publisher
Requirement 2.1.04 Each vocabulary MUST have exactly one title and at least one definition indicated using the skos:prefLabel and the skos:definition predicates respectively that must give textual literal values. Only one definition per language is allowed
Requirement 2.1.05 Each vocabulary MUST have exactly one created date and exactly one modified date indicated using the schema:dateCreated and schema:dateModified or dcterms:created and dcterms:modified predicates respectively that must be either an xsd:date, xsd:dateTime or xsd:dateTimeStamp literal value
Requirement 2.1.06 Each vocabulary MUST have at least one creator, indicated using schema:creator or dcterms:creator predicate and exactly one publisher, indicated using schema:publisher or dcterms:publisher, all of which MUST be IRIs indicating instances of schema:Person, or schema:Organization
Requirement 2.1.07 The origins of a Concept Scheme MUST be indicated by at least one of the following predicates: skos:historyNote, schema:citation, prov:wasDerivedFrom. dcterms:source MAY be used instead of schema:citation and dcterms:provenance MAY be used instead of skos:historyNote but the schema.org and SKOS predicates are preferred
prov:wasDerivedFrom SHOULD be supplied and, if it is, MUST be an IRI
schema:citation SHOULD be supplied and, if it is, MUST be a literal of type xsd:string or xsd:anyURI
dcterms:source SHOULD be supplied and, if it is, MUST be a literal of type xsd:string or xsd:anyURI
skos:historyNote SHOULD be supplied and, if it is, MUST be a literal of type xsd:string or rdf:langString
dcterms:provenance SHOULD be supplied and, if it is, MUST be a literal of type xsd:string or rdf:langString
Requirement 2.1.08 - implemented by :Requirement-2.3.03
Requirement 2.1.09 Each vocabulary's Concept Scheme MUST link to at least one Concept within the vocabulary with the skos:hasTopConcept predicate
Requirement 2.1.10 The status of a vocabulary or a Concept SHOULD be given with the predicate schema:status and MAY be given with the predicate reg:status. Either, if used, MUST indicate a Concept from the Registry Statuses vocabulary (https://linked.data.gov.au/def/reg-statuses)
Requirement 2.1.11 If a vocabulary has a qualified derivation given, it MUST then give a prove:entity predicate within the derivation, indicating the IRI of the vocabulary it is derived from
Requirement 2.1.11 If a vocabulary has a qualified derivation given, it MUST then give a prove:hadRole predicate within the derivation, indicating the IRI of the role
Requirement 2.1.12 High-level theming of a vocabulary SHOULD be given by using the schema:keywords predicate indicating Concepts from another vocabulary. Alternatively, dcat:theme MAY be used. Text literal values for either predicate SHOULD NOT be used
Requirement 2.1.13 Vocabularies SHOULD present any licence pertaining to its use using the schema:license predicate preferentially indicating the IRI of a license if in RDF form or a literal URL (datatype xsd:anyURI) if online but not in RDF form. If the licence is expressed in text, a literal text field may be indicated.
Requirement 2.1.14 The copyright holder for the vocabulary SHOULD be given using the schema:copyrightHolder predicate preferentially indicating the IRI of an Agent or a Blank Node instance of an Agent containing details as per Agent requirements. A prov:qualifiedAttribution predicate indicating an Agent with the prov:hadRole predicate indicating the value isorole:rightsHolder may be used instead of schema:copyrightHolder
Requirement 2.1.04 Each Collection and Concept MUST have exactly one title and at least one definition indicated using the skos:prefLabel and the skos:definition predicates respectively that must give textual literal values. Only one definition per language is allowed
Requirement 2.2.02 The origins of a Collection, if different from its containing Concept Scheme, SHOULD be indicated by at least one of the following predicates: skos:historyNote, schema:citation, prov:wasDerivedFrom. dcterms:source MAY be used instead of schema:citation and dcterms:provenance MAY be used instead of skos:historyNote but the schema.org and SKOS predicates are preferred
Requirement 2.2.03 All Collections MUST indicate they are within the Concept Scheme of the vocabulary with the skos:inScheme predicate
Requirement 2.2.04 A Collection MUST indicate at least one Concept instance that is within the collection with use of the skos:member predicate. The Concept need not be defined by the Concept Scheme that defines the Collection
Requirement 2.3.2 Each Concept in a vocabulary MAY indicate the vocabulary that defines it by use of the rdfs:isDefinedBy predicate indicating a Concept Scheme instance. If no such predicate is given, the Concept Scheme in the file that a Concept is provided in is understood to be the defining Concept Scheme
Requirement 2.2.03 Collections and Concepts SHOULD indicate the vocabulary that defines it with the rdfs:isDefinedBy predicate
Requirement 2.2.02 The origins of a Concept, if different from its containing Concept Scheme, SHOULD be indicated by at least one of the following predicates: skos:historyNote, schema:citation, prov:wasDerivedFrom. dcterms:source MAY be used instead of schema:citation and dcterms:provenance MAY be used instead of skos:historyNote but the schema.org and SKOS predicates are preferred
Requirement 2.3.10 If a Concept indicates a skos:notation, its range value MUST be a literal. Note that it SHOULD be of a custom datatype
Requirement 2.3.11 If a Concept indicates a skos:historyNote, its range value MUST be a literal. A plain string value (xsd:string) may be used or, if values in multiple languages are desired, then multiple language string literals (rdf:langString) may be used, but ony one per language and plain strings and language strings should not be mixed
Requirement 2.3.12 If a Concept indicates was derived from, its range value MUST be an IRI
Requirement 2.3.13 If a Concept indicates revision of, its range value MUST be an IRI
Requirement 2.3.14 If a Concept indicates replaces, its range value MUST be an IRI
Requirement 2.3.15 If a Concept indicates is replaced by, its range value MUST be an IRI
Requirement 2.3.16 If a Concept indicates version, its range value MUST be a plain string (xsd:string)
Requirement 2.3.17 If a Concept indicates a date created, its range value MUST be a date (xsd:date)
Requirement 2.3.18 If a Concept indicates a date modified, its range value MUST be a date (xsd:date)
Requirement 2.3.19 If a Concept indicates a temporal coverage, its range value MUST be a temporal entity (time:TemporalEntity) with either or both schema:startDate and schema:endDate values which must be dates (xsd:date)
Requirement 2.3.19 If a Temporal Entity (time:TemporalEntity) indicates a start date (schema:startDate) value, it must be a literal date (xsd:date)
Requirement 2.3.19 If a Temporal Entity (time:TemporalEntity) indicates an end date (schema:startDate) value, it must be a literal date (xsd:date)
Requirement 2.3.19 A Temporal Entity (time:TemporalEntity) must indicate either or both a start date (schema:startDate) and an end date (schema:endDate) value
Requirement 2.4.2 Each Agent MUST have at least one name indicated with the schema:name predicate, pointing to a literal text value. If multiple names in multiple languages are desired, then multiple schema:name values are permitted with langString literals, but ony one per language
Requirement 2.4.3 Each Organization MUST indicate a website with the schema:url predicate, pointing to an xsd:anyURI value
Requirement 2.4.3 Each Person MUST indicate an email address with the schema:email predicate, pointing to an xsd:anyURI value
Requirement 2.3.03 Each Concept in a vocabulary MUST indicate that it appears within that vocabulary's hierarchy of Concepts either directly by use of the skos:topConceptOf predicate indicating the vocabulary or indirectly by use of one or more skos:broader / skos:narrower predicates placing the Concept within a chain of other Concepts, the end of which is indicated as a top concept of the vocabulary
Requirement 2.3.20 If a Concept indicates a broader Concept with skos:broader, that Concept must exist in the vocabulary
This model validator was made for the Queensland Department of Resources, Spatial Information unit to assist with future Address database design.
(c) The State of Queensland (Department of Natural Resources and Mines, Manufacturing and Regional and Rural Development) 2026
This validator is a Shapes Constraint Language (SHACL) resource that can be used to check the conformance of RDF data to the ANZ ICSM Address Model with extensions for Queensland
Each ACT Address must indicate an Address Part with the ASGS IRI for Queensland
Observations following the Enhanced protocol are made in the context of a site visit.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/576f634e-2706-4f18-b561-0636d4c007d0>`. `<https://linked.data.gov.au/def/nrm/576f634e-2706-4f18-b561-0636d4c007d0>` is the IRI for "Enhanced protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/576f634e-2706-4f18-b561-0636d4c007d0`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/85bdd25a-fa08-49de-9f0b-98895cb79aa6> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/85bdd25a-fa08-49de-9f0b-98895cb79aa6>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/85bdd25a-fa08-49de-9f0b-98895cb79aa6> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/85bdd25a-fa08-49de-9f0b-98895cb79aa6>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/85bdd25a-fa08-49de-9f0b-98895cb79aa6>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0e9da717-6c8e-4194-9385-c995d54702e4>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0e9da717-6c8e-4194-9385-c995d54702e4>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0e9da717-6c8e-4194-9385-c995d54702e4> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0e9da717-6c8e-4194-9385-c995d54702e4>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 0 and 100 exclusive.
The result _MUST_ have a value between 0 and 100 exclusively.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ddd0c631-bfdd-4b0f-88de-a5eb1a0181c6>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Plant statuses controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Plant statuses controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/ddd0c631-bfdd-4b0f-88de-a5eb1a0181c6> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'b7368a37-a4ac-4c84-8a78-1fb9755ad849'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/ddd0c631-bfdd-4b0f-88de-a5eb1a0181c6> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ddd0c631-bfdd-4b0f-88de-a5eb1a0181c6>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ddd0c631-bfdd-4b0f-88de-a5eb1a0181c6>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/b7368a37-a4ac-4c84-8a78-1fb9755ad849>`. `<https://linked.data.gov.au/def/nrm/b7368a37-a4ac-4c84-8a78-1fb9755ad849>` is the IRI for "Plant statuses".
The value of `tern:vocabulary` _MUST_ match the pattern `b7368a37-a4ac-4c84-8a78-1fb9755ad849$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/75f55bf0-6972-42ba-ad46-7e24f91e8f6a>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Substrate types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Substrate types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/75f55bf0-6972-42ba-ad46-7e24f91e8f6a> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'b061d7db-a608-4062-96d4-b367d6d9a792'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/75f55bf0-6972-42ba-ad46-7e24f91e8f6a> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/75f55bf0-6972-42ba-ad46-7e24f91e8f6a>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/75f55bf0-6972-42ba-ad46-7e24f91e8f6a>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/b061d7db-a608-4062-96d4-b367d6d9a792>`. `<https://linked.data.gov.au/def/nrm/b061d7db-a608-4062-96d4-b367d6d9a792>` is the IRI for "Substrate types".
The value of `tern:vocabulary` _MUST_ match the pattern `b061d7db-a608-4062-96d4-b367d6d9a792$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/dd25002d-6fd8-4c1f-a1df-c556d43daea8> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dd25002d-6fd8-4c1f-a1df-c556d43daea8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/dd25002d-6fd8-4c1f-a1df-c556d43daea8> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
Observations following the Standard protocol are made in the context of a site visit.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dd25002d-6fd8-4c1f-a1df-c556d43daea8>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/aa1525f9-c3f2-4f7d-98cc-6a7d3aec9d8a>`. `<https://linked.data.gov.au/def/nrm/aa1525f9-c3f2-4f7d-98cc-6a7d3aec9d8a>` is the IRI for "Standard protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/aa1525f9-c3f2-4f7d-98cc-6a7d3aec9d8a`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dd25002d-6fd8-4c1f-a1df-c556d43daea8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/7817e244-a5cf-54c1-9ea1-9dca8469bce7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Fractional cover response types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Fractional cover response types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/7817e244-a5cf-54c1-9ea1-9dca8469bce7> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'51d1a677-0688-57b3-91c7-6f1e3beee188'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/7817e244-a5cf-54c1-9ea1-9dca8469bce7> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/7817e244-a5cf-54c1-9ea1-9dca8469bce7>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/7817e244-a5cf-54c1-9ea1-9dca8469bce7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/51d1a677-0688-57b3-91c7-6f1e3beee188>`. `<https://linked.data.gov.au/def/nrm/51d1a677-0688-57b3-91c7-6f1e3beee188>` is the IRI for "Fractional cover response types".
The value of `tern:vocabulary` _MUST_ match the pattern `51d1a677-0688-57b3-91c7-6f1e3beee188$`.
This vocabulary was created in the FOAF project, based on experience with FOAF, Dublin Core and other early RDF vocabularies. Deployment experience shows that changing namespace URIs is expensive and unrewarding, so this vocabulary provides terms to support in-place evolution of structured data vocabularies. By indicating status at the level of terms rather than vocabularies, dictionary-style, fine grained improvements become easier. Different organizations and parties can agree or disagree on the status of a vocabulary term; however the status published alongside the term may deserve special attention. Future work could include patterns for citing announcements and decisions, or using SKOS to decentralise the extension of the basic status levels.
An RDF vocabulary for relating SW vocabulary terms to their status.
the status of a vocabulary term, expressed as a short symbolic string; known values include 'unstable','testing', 'stable' and 'archaic'
more information about the status etc of a term, typically human oriented
human-oriented documentation, examples etc for use of this term
SHACL validator for the BDR Data Release Model
BDR Data Release Model Validator
Constraints on Dataset relating to data release
A Dataset that uses an embargo period predicate must use it to indicate an instance of the class time:DurationDescription from OWL Time
A Dataset that uses an embargoed until predicate must use it to indicate a xsd:date, xsd:dateTime or xsd:dateTimeStamp literal value
The roles that major elements of a Supermodel play in that Supermodel's context
Created for the original Supermodel document release in late 2025
Supermodel Element Roles
A supermodel element may play more than one role and may play different roles in different Supermodel contexts
Acting as a controlled collection of terms, usually with a hierarchy but sometimes just a list, used as Reference Dataset by Datasets.
Vocabulary
Acting as a Dataset that is used as an integration point by one or more Datasets.
Reference Dataset
Acting as a Model for a Dataset of Reference Dataset.
Background Model
Acting as an abstract information object that organises elements of data and standardises how they relate to one another and to the properties of real-world entities.
Model
Acting as Data that is the main subject of the supermodel that may or may not also be used as Reference Data.
Foreground Data
Acting as a collection of discrete or continuous values that convey information, describing the quantity, quality, fact, statistics, other basic units of meaning.
Data
Acting as a collection of foreground Data.
Foreground Dataset
Acting as a managed aggregation of foreground or reference Data.
Dataset
Acting as a Model for a Dataset of Foreground Data.
Foreground Model
Acting as Data that is not the main subject of the supermodel but is linked to by such data.
Reference Data
Acting as the definitional object of the Supermodel and container of all its elements.
Supermodel Definition
Acting as resource to validate the conformance of Datasets to Profiles.
Validator
This property is analogous to dcat:distribution however the domain is not necessarily dcat:Dataset. dcat:Dataset and prof:Profile are not disjoint, so it is up to implementations to decide if these are equivalent properties
A resource which describes the nature of an artifact and the role it plays in relation to the Profile
A set of common roles are defined by the Profiles Vocabulary. These are not exhaustive or disjoint, and may be extended for situations where finer grained description of purpose is necessary. A resource may perform multiple roles
The function of an artifact described by a Resource Descriptor, such as specification, guidance etc.
A property to link from a Resource Descriptor to an actual information resource (rdfs:Resource; an individual) that implements it
The URL of a downloadable file with particulars such as its format and role indicated by the Resource Descriptor
Can be use to indicate the formalism (via dct:format) and any adherence to a dct:Standard (via dct:conformsTo) to allow for machine mediation as well as its purpose via relation to a ResourceRole (via hasRole)
A description of a resource that defines an aspect - a particular part, feature or role - of a Profile
A specification that constrains, extends, combines, or provides guidance or explanation about the usage of other specifications. This definition includes what are often called "application profiles", "metadata application profiles", or "metadata profiles".
2026-01 NJC: added OntPub elements, including the Ontology class definition
This vocabulary is for describing relationships between standards/specifications, profiles of them and supporting artifacts such as validating resources. This model starts with [http://dublincore.org/2012/06/14/dcterms#Standard](dct:Standard) entities which can either be Base Specifications (a standard not profiling any other Standard) or Profiles (Standards which do profile others). Base Specifications or Profiles can have Resource Descriptors associated with them that defines implementing rules for the it. Resource Descriptors must indicate the role they play (to guide, to validate etc.) and the formalism they adhere to (dct:format) to allow for content negotiation. A vocabulary of Resource Roles are provided alongside this vocabulary but that list is extensible.
Specific terms must come from a vocabulary
A role that an profile resource, described by a Resource Descriptor, plays
A simple lexical form of identifier that may be accepted in some circumstances, such as API arguments to reference this profile. This is the “preferred term”, since alternative identifiers may be declared and used by any implementation
The preferred identifier for the Profile, for use in circumstances where its URI cannot be used
This property is created for the convenience of clients. When profile describers wish to allow clients to discover all resources relevant to a Profile without having to navigating an inheritance hierarchy of prof:profileOf relations, this predicate may be used to directly associate inherited Profile Descriptors with the Profile. If this property is present, it should be used consistently and all relevant resources a client may need to utilise the profile should be present and described using this predicate
A base specification, a Resource Descriptor from which is to be considered a Resource Descriptor for this Profile also
A Profile may define constraints on the usage of one or more specifications. All constraints of these specifications are inherited, in the sense that an object conforming to a profile conforms to all the constraints specified the targets of prof:isProfileOf relations. This property is optional, allowing any specification to be declared at the root of a profile hierarchy using the Profile class
A specification for which this Profile defines constraints, extensions, or which it uses in combination with other specifications, or provides guidance or explanation about its usage
This is a convenience property that may be used to access all specifications (including other profiles) that could provide useful information and related resources for the Profile (for example, for better identifying conformance requirements). This avoids forcing clients to traverse a profile hierarchy to find all relevant resources. If this property is used, then all such relationships should be present so a client can safely avoid hierarchy traversal
The transitive closure of the prof:isProfileOf property. Relates a profile to another specification that it is a profile of, possibly via a chain of intermediate profiles that are in prof:isProfileOf relationships
KurrawongAI is a small, Artificial Intelligence, company in Australia specialising in Knowledge Graphs.
Nicholas J. Car
The IDN is within the University of Melbourne. It was established in 2018 to support and coordinate the governance of Indigenous data for Aboriginal and Torres Strait Islander peoples and empower Aboriginal and Torres Strait Islander communities to decide their own local data priorities.
This validator for the IDN Catalogue Profile was made within the IDN's ID Catalogue project 2021 - 2022.
A SHACL validator IDN Catalogue Profile.
IDN CP Validator
Req AG1: Each Agent instance MUST be either an schema:Organization or a schema:Person instance.
Req AG3: Each Agent instance SHOULD be described with a schema:description property and, if the Agent has them, identifiers for it should be indicated with schema:identifier with xsd:anyURI or xsd:token values.
Req AG2: Each Agent instance MUST be described with at least the schema:name property and, if an schema:Organization, also an schema:url property with a xsd:anyURI value or, if a schema:Person, an schema:email property with a xsd:anyURI value.
Req AG3: Each Agent instance SHOULD be described with a schema:description property and, if the Agent has them, identifiers for it should be indicated with schema:identifier with either xsd:anyURI, xsd:token or a datatype from the Library of Congress Standard Identifiers vocabulary.
Req A1: Each Attribution instance MUST indicate an Agent instance with the property prov:agent and a role for that Agent, as a skos:Concept, in relation to the attributing entity, with the roleCode property.
Each Attribution instance MUST indicate an Agent instance with the property schema:agent and a role for that Agent, as a skos:Concept, in relation to the attributing entity, with the hadRole property.
Req C2: Each Catalog instance MUST contain at least one Resource indicated by the hasPart property.
Req R2: Each Resource instance MUST provide basic Resource metadata so that exactly one of each of the following properties is required with range value as per Resource requirements: name, description, created & modified. The particular validator violated here is for created. Req R3: Allowed Semantic Web date/time properties for created & modified properties are xsd:date, xsd:dateTime, xsd:dateTimeStamp, time:Interval
Req R2: Each Resource instance MUST provide basic Resource metadata so that exactly one of each of the following properties is required with range value as per Resource requirements: name, description, created & modified. The particular validator violated here is for description.
Req R4: Each Resource instance MUST NOT indicate Agent roles with direct properties other than publisher and creator and MUST instead indicate them with PROV qualified attribution pattern with each prov:Attribution indicated with the property prov:qualifiedAttribution.
Req R1: Each Resource instance SHOULD indicate a persistent identifier to be used to gain access to its point-of-truth metadata. The PID SHOULD be used as the Dataset instance's IRI, if it is an HTTP/HTTPS IRI, or else it SHOULD be quoted as a literal value, indicated with the property schema:identifier of datatype xsd:token.
Req R2: Each Resource instance MUST provide basic Resource metadata so that exactly one of each of the following properties is required with range value as per Resource requirements: name, description, created & modified. The particular validator violated here is for modified. Req R3: Allowed Semantic Web date/time properties for created & modified properties are xsd:date, xsd:dateTime, xsd:dateTimeStamp, time:Interval
Req R2: Each Resource instance MUST provide basic Resource metadata so that exactly one of each of the following properties is required with range value as per Resource requirements: name, description, created & modified. The particular validator violated here is for name.
This profile implements no shapes for Concept but inherits those of the VocPub Profile of SKOS
This profile implements no shapes for ConceptScheme but inherits those of the VocPub Profile of SKOS
Req R5: Each Resource instance, if it is not a Catalog instance MUST, and if it is a Catalog instance MAY, indicate that it is within at least one Catalog instance with an in-bound hasPart property from a Catalog instance.
Req AG2: (organization-email) Each Agent instance MUST be described with at least the schema:name property and, if an schema:Organization, also an schema:url property with a xsd:anyURI value or, if a schema:Person, an schema:email property with a xsd:anyURI value.
Req AG2: (person-email) Each Agent instance MUST be described with at least the schema:name property and, if an schema:Organization, also an schema:url property with a xsd:anyURI value or, if a schema:Person, an schema:email property with a xsd:anyURI value.
Link to the repository where the un-compiled, human readable code and related code is located (SVN, GitHub, CodePlex).
The creator/author of this CreativeWork. This is the same as the Author property for CreativeWork.
The date on which the CreativeWork was created or the item was added to a DataFeed.
The date on which the CreativeWork was most recently modified or when the item's entry was modified within a DataFeed.
Indicates an item or CreativeWork that is part of this item, or CreativeWork (in some sense).
The version of the CreativeWork embodied by a specified resource.
A body of structured information describing some topic(s) of interest.
An organization that this person is affiliated with. For example, a school/university, a club, or a team.
An organization such as a school, NGO, corporation, club, etc.
A person (alive, dead, undead, or fictional).
A license document that applies to this content, typically indicated by URL.
Indicates an item or CreativeWork that this item, or CreativeWork (in some sense), is part of.
A citation or reference to another creative work, such as another publication, web page, scholarly article, etc.
The model of the product. Use with the URL of a ProductModel or a textual representation of the model identifier. The URL of the ProductModel can be from an external source. It is recommended to additionally provide strong product identifiers via the gtin8/gtin13/gtin14 and mpn properties.
An enterprise (potentially individual but typically collaborative), planned to achieve a particular aim. Use properties from Organization, subOrganization/parentOrganization to indicate project sub-structures.
The "spatial" property can be used in cases when more specific properties (e.g. locationCreated, spatialCoverage, contentLocation) are not known to be appropriate.
The serial number or any alphanumeric identifier of a particular product. When attached to an offer, it is a shortcut for the serial number of the product included in the offer.
The most generic kind of creative work, including books, movies, photographs, software programs, etc.
Keywords or tags used to describe some item. Multiple textual entries in a keywords list are typically delimited by commas, or by repeating the property.
The schema.org usageInfo property indicates further information about a CreativeWork. This property is applicable both to works that are freely available and to those that require payment or other transactions. It can reference additional information, e.g. community expectations on preferred linking and citation conventions, as well as purchasing details. For something that can be commercially licensed, usageInfo can provide detailed, resource-specific information about licensing options. This property can be used alongside the license property which indicates license(s) applicable to some piece of content. The usageInfo property can provide information about other licensing options, e.g. acquiring commercial usage rights for an image that is also available under non-commercial creative commons licenses.
The party holding the legal copyright to the CreativeWork.
A secondary contributor to the CreativeWork or Event.
The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See [background notes](/docs/datamodel.html#identifierBg) for more details.
The larger organization that this organization is a subOrganization of, if any.
A relationship between two organizations where the first includes the second, e.g., as a subsidiary. See also: the more specific 'department' property.
The year during which the claimed copyright for the CreativeWork was first asserted.
The location depicted or described in the content. For example, the location in a photograph or painting.
Indicates the primary entity described in some page or other CreativeWork.
An Organization (or ProgramMembership) to which this Person or Organization belongs.
Text of a notice appropriate for describing the copyright aspects of this Creative Work, ideally indicating the owner of the copyright for the Work.
2026-02 NJC: Added the ontology declaration
Schema.org is a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet.
Approximate or typical time it usually takes to work with or through the content of this work for the typical or target audience.
An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. Typically the value is a URI-identified RDF class, and in this case corresponds to the use of rdf:type in RDF. Text values can be used sparingly, for cases where useful information can be added without their being an appropriate schema to reference. In the case of text values, the class label should follow the schema.org style guide.
Relates a property to a class that is (one of) the type(s) the property is expected to be used on.
Relates a property to a class that constitutes (one of) the expected type(s) for values of the property.
An action performed by a direct agent and indirect participants upon a direct object. Optionally happens at a location with the help of an inanimate instrument. The execution of the action may produce a result. Specific action sub-type documentation specifies the exact expectation of each argument/role.\n\nSee also [blog post](http://blog.schema.org/2014/04/announcing-schemaorg-actions.html) and [Actions overview document](https://schema.org/docs/actions.html).
A 3D model represents some kind of 3D content, which may have encodings in one or more MediaObjects. Many 3D formats are available (e.g. see [Wikipedia](https://en.wikipedia.org/wiki/Category:3D_graphics_file_formats)); specific encoding formats can be represented using the encodingFormat property applied to the relevant MediaObject. For the case of a single file published after Zip compression, the convention of appending '+zip' to the encodingFormat can be used. Geospatial, AR/VR, artistic/animation, gaming, engineering and scientific content can all be represented using 3DModel.
A media object, such as an image, video, audio, or text object embedded in a web page or a downloadable dataset i.e. DataDownload. Note that a creative work may have many media objects associated with it on the same web page. For example, a page about a single song (MusicRecording) may have a music video (VideoObject), and a high and low bandwidth audio stream (2 AudioObject's).
A unique instance of a radio BroadcastService on a CableOrSatelliteService lineup.
Reference documentation for application programming interfaces (APIs).
A technical article - Example: How-to (task) topics, step-by-step, procedural troubleshooting, specifications, etc.
A web page. Every web page is implicitly assumed to be declared to be of type WebPage, so the various properties about that webpage, such as breadcrumb may be used. We recommend explicit declaration if these properties are specified, but if they are found outside of an itemscope, they will be assumed to be about the page.
The act of committing to/adopting an object.\n\nRelated actions:\n\n* RejectAction: The antonym of AcceptAction.
The act of organizing tasks/objects/events by associating resources to it.
An accommodation is a place that can accommodate human beings, e.g. a hotel room, a camping pitch, or a meeting room. Many accommodations are for overnight stays, but this is not a mandatory requirement. For more specific types of accommodations not defined in schema.org, one can use additionalType with external vocabularies. See also the dedicated document on the use of schema.org for marking up hotels and other forms of accommodations.
Entities that have a somewhat fixed, physical extension.
Accountancy business.\n\nAs a LocalBusiness it can be described as a provider of one or more Service\(s).
The act of accomplishing something via previous efforts. It is an instantaneous action rather than an ongoing process.
A set of requirements that must be fulfilled in order to perform an Action.
A utility class that serves as the umbrella for a number of 'intangible' things such as quantities, structured values, etc.
Lists or enumerations dealing with status types.
The act of starting or activating a device or application (e.g. starting a timer or turning on a flashlight).
An agent controls a device or application.
The act of editing by adding an object to a collection.
The act of managing by changing/editing the state of the object.
A geographical region, typically under the jurisdiction of a particular government.
Enumeration of considerations that make a product relevant or potentially restricted for adults only.
Lists or enumerations—for example, a list of cuisines or music genres, etc.
An Article that an external entity has paid to place or to produce to its specifications. Includes [advertorials](https://en.wikipedia.org/wiki/Advertorial), sponsored content, native advertising and other paid content.
An article, such as a news article or piece of investigative report. Newspapers and magazines have articles of many different types and this is intended to cover them all.\n\nSee also [blog post](http://blog.schema.org/2014/09/schemaorg-support-for-bibliographic_2.html).
When a single product is associated with multiple offers (for example, the same pair of shoes is offered by different merchants), then AggregateOffer can be used.\n\nNote: AggregateOffers are normally expected to associate multiple offers that all share the same defined businessFunction value, or default to http://purl.org/goodrelations/v1#Sell if businessFunction is not explicitly defined.
An offer to transfer some rights to an item or to provide a service — for example, an offer to sell tickets to an event, to rent the DVD of a movie, to stream a TV show over the internet, to repair a motorcycle, or to loan a book.\n\nNote: As the businessFunction property, which identifies the form of offer (e.g. sell, lease, repair, dispose), defaults to http://purl.org/goodrelations/v1#Sell; an Offer without a defined businessFunction value can be assumed to be an offer to sell.\n\nFor [GTIN](http://www.gs1.org/barcodes/technical/idkeys/gtin)-related fields, see [Check Digit calculator](http://www.gs1.org/barcodes/support/check_digit_calculator) and [validation guide](http://www.gs1us.org/resources/standards/gtin-validation-guide) from [GS1](http://www.gs1.org/).
The average rating based on multiple ratings or reviews.
A rating is an evaluation on a numeric scale, such as 1 to 5 stars.
The act of expressing a consistency of opinion with the object. An agent agrees to/about an object (a proposition, topic or theme) with participants.
The act of responding instinctively and emotionally to an object, expressing a sentiment.
An organization that provides flights for passengers.
A public structure, such as a town hall or concert hall.
An intangible item that describes an alignment between a learning resource and a node in an educational framework. Should not be used where the nature of the alignment can be described using a simple property, for example to express that a resource teaches or assesses a competency.
The act of manipulating/administering/supervising/controlling one or more objects.
A creative work with a visual storytelling format intended to be viewed online, particularly on mobile devices.
An AnalysisNewsArticle is a NewsArticle that, while based on factual reporting, incorporates the expertise of the author/producer, offering interpretations and conclusions.
A NewsArticle is an article whose content reports news, or provides background context and supporting materials for understanding the news. A more detailed overview of [schema.org News markup](/docs/news.html) is also available.
Any part of the human body, typically a component of an anatomical system. Organs, tissues, and cells are all anatomical structures.
The most generic type of entity related to health and the practice of medicine.
An anatomical system is a group of anatomical structures that work together to perform a certain task. Anatomical systems, such as organ systems, are one organizing principle of anatomy, and can include circulatory, digestive, endocrine, integumentary, immune, lymphatic, muscular, nervous, reproductive, respiratory, skeletal, urinary, vestibular, and other systems.
A particular physical business or branch of an organization. Examples of LocalBusiness include a restaurant, a particular branch of a restaurant chain, a branch of a bank, a medical practice, a club, a bowling alley, etc.
An answer offered to a question; perhaps correct, perhaps opinionated or wrong.
A comment on an item - for example, a comment on a blog post. The comment's content is expressed via the text property, and its topic via about, properties shared with all CreativeWorks.
An apartment (in American English) or flat (in British English) is a self-contained housing unit (a type of residential real estate) that occupies only part of a building (source: Wikipedia, the free encyclopedia, see http://en.wikipedia.org/wiki/Apartment).
The act of inserting at the end if an ordered collection.
The act of adding at a specific location in an ordered collection.
The act of registering to an organization/service without the guarantee to receive it.\n\nRelated actions:\n\n* RegisterAction: Unlike RegisterAction, ApplyAction has no guarantees that the application will be accepted.
An indication for a medical therapy that has been formally specified or approved by a regulatory body that regulates use of the therapy; for example, the US FDA approves indications for most drugs in the US.
A condition or factor that indicates use of a medical therapy, including signs, symptoms, risk factors, anatomical states, etc.
An intangible type to be applied to any archive content, carrying with it a set of properties required to describe archival items and collections.
ArchiveComponent
An organization with archival holdings. An organization which keeps and preserves archival material and typically makes it accessible to the public.
ArchiveOrganization
The act of arriving at a place. An agent arrives at a destination from a fromLocation, optionally with participants.
The act of an agent relocating to a place.\n\nRelated actions:\n\n* TransferAction: Unlike TransferAction, the subject of the move is a living Person or Organization rather than an inanimate object.
A type of blood vessel that specifically carries blood away from the heart.
A component of the human body circulatory system comprised of an intricate network of hollow tubes that transport blood throughout the entire body.
The act of posing a question / favor to someone.\n\nRelated actions:\n\n* ReplyAction: Appears generally as a response to AskAction.
The act of conveying information to another person via a communication medium (instrument) such as speech, email, or telephone conversation.
A NewsArticle expressing an open call by a NewsMediaOrganization asking the public for input, insights, clarifications, anecdotes, documentation, etc., on an issue, for reporting purposes.
The act of forming one's opinion, reaction or sentiment.
The act of allocating an action/event/task to some destination (someone or something).
A collection or bound volume of maps, charts, plates or tables, physical or in media form illustrating any subject.
Professional service: Attorney. \n\nThis type is deprecated - LegalService is more inclusive and less ambiguous.
A LegalService is a business that provides legally-oriented services, advice and representation, e.g. law firms.\n\nAs a LocalBusiness it can be described as a provider of one or more Service\(s).
Intended audience for an item, i.e. the group for whom the item was created.
A specific and exact (byte-for-byte) version of an AudioObject. Two byte-for-byte identical files, for the purposes of this type, considered identical. If they have different embedded metadata the files will differ. Different external facts about the files, e.g. creator or dateCreated that aren't represented in their actual content, do not affect this notion of identity.
The act of granting permission to an object.
A NewsArticle providing historical context, definition and detail on a specific topic (aka "explainer" or "backgrounder"). For example, an in-depth article or frequently-asked-questions ([FAQ](https://en.wikipedia.org/wiki/FAQ)) document on topics such as Climate Change or the European Union. Other kinds of background material from a non-news setting are often described using Book or Article, in particular ScholarlyArticle. See also NewsArticle for related vocabulary from a learning/education perspective.
A product or service offered by a bank whereby one may deposit, withdraw or transfer money and in some cases be paid interest.
A product provided to consumers and businesses by financial institutions such as banks, insurance companies, brokerage firms, consumer finance companies, and investment companies which comprise the financial services industry.
An image of a visual machine-readable code such as a barcode or QR code.
Bed and breakfast. See also the dedicated document on the use of schema.org for marking up hotels and other forms of accommodations.
A lodging business, such as a motel, hotel, or inn.
An entity holding detailed information about the available bed types, e.g. the quantity of twin beds for a hotel room. For the single case of just one bed of a certain type, you can use bed directly with a text. See also BedType (under development).
A type of bed. This is used for indicating the bed or beds available in an accommodation.
A predefined value for a product characteristic, e.g. the power cord plug type 'US' or the garment sizes 'S', 'M', 'L', and 'XL'.
The act of forming a personal connection with someone (object) mutually/bidirectionally/symmetrically.\n\nRelated actions:\n\n* FollowAction: Unlike FollowAction, BefriendAction implies that the connection is reciprocal.
The act of interacting with another person or organization.
Any biological, chemical, or biochemical thing. For example: a protein; a gene; a chemical; a synthetic chemical.
A [blog](https://en.wikipedia.org/wiki/Blog), sometimes known as a "weblog". Note that the individual posts (BlogPostings) in a Blog are often colloquially referred to by the same term.
A post to a social media platform, including blog posts, tweets, Facebook posts, etc.
A medical test performed on a sample of a patient's blood.
Any medical test, typically performed for diagnostic purposes.
A type of boarding policy used by an airline.
A reservation for boat travel. Note: This type is for information about actual reservations, e.g. in confirmation emails or HTML pages with individual confirmations of reservations. For offers of tickets, use Offer.
Describes a reservation for travel, dining or an event. Some reservations require tickets. \n\nNote: This type is for information about actual reservations, e.g. in confirmation emails or HTML pages with individual confirmations of reservations. For offers of tickets, restaurant reservations, flights, or rental cars, use Offer.
A terminal for boats, ships, and other water vessels.
A trip or journey. An itinerary of visits to one or more places.
Enumerates types (or dimensions) of a person's body measurements, for example for fitting of clothes.
Enumeration of common measurement types (or dimensions), for example "chest" for a person, "inseam" for pants, "gauge" for screws, or "wheel" for bicycles.
A body of water, such as a sea, ocean, or lake.
A landform or physical feature. Landform elements include mountains, plains, lakes, rivers, seascape and oceanic waterbody interface features such as bays, peninsulas, seas and so forth, including sub-aqueous terrain features such as submersed mountain ranges, volcanoes, and the great ocean basins.
Rigid connective tissue that comprises up the skeletal structure of the human body.
A series of books. Included books can be indicated with the hasPart property.
A CreativeWorkSeries in schema.org is a group of related items, typically but not necessarily of the same kind. CreativeWorkSeries are usually organized into some order, often chronological. Unlike ItemList which is a general purpose data structure for lists of things, the emphasis with CreativeWorkSeries is on published materials (written e.g. books and periodicals, or media such as TV, radio and games).\n\nSpecific subtypes are available for describing TVSeries, RadioSeries, MovieSeries, BookSeries, Periodical and VideoGameSeries. In each case, the hasPart / isPartOf properties can be used to relate the CreativeWorkSeries to its parts. The general CreativeWorkSeries type serves largely just to organize these more specific and practical subtypes.\n\nIt is common for properties applicable to an item from the series to be usefully applied to the containing group. Schema.org attempts to anticipate some of these cases, but publishers should be free to apply properties of the series parts to the series as a whole wherever they seem appropriate.
An agent bookmarks/flags/labels/tags/marks an object.
The basic data types such as Integers, Strings, etc.
The act of obtaining an object under an agreement to return it at a later date. Reciprocal of LendAction.\n\nRelated actions:\n\n* LendAction: Reciprocal of BorrowAction.
The act of transferring/moving (abstract or concrete) animate or inanimate objects from one place to another.
A sports location, such as a playing field.
Any anatomical structure which pertains to the soft nervous tissue functioning as the coordinating center of sensation and intellectual and nervous activity.
A brand is a name used by an organization or business person for labeling a product, product group, or similar.
A BreadcrumbList is an ItemList consisting of a chain of linked Web pages, typically described using at least their URL and their name, and typically ending with the current page.\n\nThe position property is used to reconstruct the order of the items in a BreadcrumbList. The convention is that a breadcrumb list has an itemListOrder of ItemListOrderAscending (lower values listed first), and that the first items in this list correspond to the "top" or beginning of the breadcrumb trail, e.g. with a site or section homepage. The specific values of 'position' are not assigned meaning for a BreadcrumbList, but they should be integers, e.g. beginning with '1' for the first item in the list.
A list of items of any sort—for example, Top 10 Movies About Weathermen, or Top 100 Party Songs. Not to be confused with HTML lists, which are often used only for formatting.
A unique instance of a BroadcastService on a CableOrSatelliteService lineup.
An over the air or online broadcast event.
A PublicationEvent corresponds indifferently to the event of publication for a CreativeWork of any type, e.g. a broadcast event, an on-demand event, a book/journal publication via a variety of delivery media.
The frequency in MHz and the modulation used for a particular BroadcastService.
A delivery service through which content is provided via broadcast over the air or online.
A service provided by an organization, e.g. delivery service, print services, etc.
An account that allows an investor to deposit funds and place investment orders with a licensed broker or brokerage firm.
A type of financial product that typically requires the client to transfer funds to a financial service in return for potential beneficial financial return.
Place of worship, such as a church, synagogue, or mosque.
A bus (also omnibus or autobus) is a road vehicle designed to carry passengers. Coaches are luxury buses, usually in service for long distance travel.
A vehicle is a device that is designed or used to transport people or cargo over land, water, air, or through space.
A reservation for bus travel. \n\nNote: This type is for information about actual reservations, e.g. in confirmation emails or HTML pages with individual confirmations of reservations. For offers of tickets, use Offer.
A set of characteristics belonging to businesses, e.g. who compose an item's target audience.
A business entity type is a conceptual entity representing the legal form, the size, the main line of business, the position in the value chain, or any combination thereof, of an organization or business person.\n\nCommonly used values:\n\n* http://purl.org/goodrelations/v1#Business\n* http://purl.org/goodrelations/v1#Enduser\n* http://purl.org/goodrelations/v1#PublicInstitution\n* http://purl.org/goodrelations/v1#Reseller
An event happening at a certain time and location, such as a concert, lecture, or festival. Ticketing information may be added via the offers property. Repeated events may be structured as separate Event objects.
The business function specifies the type of activity or access (i.e., the bundle of rights) offered by the organization or business person through the offer. Typical are sell, rental or lease, maintenance or repair, manufacture / produce, recycle / dispose, engineering / construction, or installation. Proprietary specifications of access rights are also instances of this class.\n\nCommonly used values:\n\n* http://purl.org/goodrelations/v1#ConstructionInstallation\n* http://purl.org/goodrelations/v1#Dispose\n* http://purl.org/goodrelations/v1#LeaseOut\n* http://purl.org/goodrelations/v1#Maintain\n* http://purl.org/goodrelations/v1#ProvideService\n* http://purl.org/goodrelations/v1#Repair\n* http://purl.org/goodrelations/v1#Sell\n* http://purl.org/goodrelations/v1#Buy
The act of giving money to a seller in exchange for goods or services rendered. An agent buys an object, product, or service from a seller for a price. Reciprocal of SellAction.
The act of participating in an exchange of goods and services for monetary compensation. An agent trades an object, product or service with a participant in exchange for a one time or periodic payment.
A CDCPMDRecord is a data structure representing a record in a CDC tabular data format used for hospital data reporting. See [documentation](/docs/cdc-covid.html) for details, and the linked CDC materials for authoritative definitions used as the source here.
Structured values are used when the value of a property has a more complex structure than simply being a textual value or a reference to another thing.
A service which provides access to media programming like TV or radio. Access may be via cable or satellite.
A camping site, campsite, or Campground is a place used for overnight stay in the outdoors, typically containing individual CampingPitch locations. \n\n In British English a campsite is an area, usually divided into a number of pitches, where people can camp overnight using tents or camper vans or caravans; this British English use of the word is synonymous with the American English expression campground. In American English the term campsite generally means an area where an individual, family, group, or military unit can pitch a tent or park a camper; a campground may contain many campsites (source: Wikipedia, see [https://en.wikipedia.org/wiki/Campsite](https://en.wikipedia.org/wiki/Campsite)).\n\n See also the dedicated [document on the use of schema.org for marking up hotels and other forms of accommodations](/docs/hotels.html).
A CampingPitch is an individual place for overnight stay in the outdoors, typically being part of a larger camping site, or Campground.\n\n In British English a campsite, or campground, is an area, usually divided into a number of pitches, where people can camp overnight using tents or camper vans or caravans; this British English use of the word is synonymous with the American English expression campground. In American English the term campsite generally means an area where an individual, family, group, or military unit can pitch a tent or park a camper; a campground may contain many campsites. (Source: Wikipedia, see [https://en.wikipedia.org/wiki/Campsite](https://en.wikipedia.org/wiki/Campsite).)\n\n See also the dedicated [document on the use of schema.org for marking up hotels and other forms of accommodations](/docs/hotels.html).
The act of asserting that a future event/action is no longer going to happen.\n\nRelated actions:\n\n* ConfirmAction: The antonym of CancelAction.
The act of planning the execution of an event/task/action/reservation/plan to a future date.
A car is a wheeled, self-powered motor vehicle used for transportation.
A value indicating a special usage of a car, e.g. commercial rental, driving school, or as a taxi.
A word, name, acronym, phrase, etc. with a formal definition. Often used in the context of category or subject classification, glossaries or dictionaries, product or creative work types, etc. Use the name property for the term being defined, use termCode if the term has an alpha-numeric code allocated, use description to provide the definition of the term.
A set of defined terms, for example a set of categories or a classification scheme, a glossary, dictionary or enumeration.
A Certification is an official and authoritative statement about a subject, for example a product, service, person, or organization. A certification is typically issued by an indendent certification body, for example a professional organization or government. It formally attests certain characteristics about the subject, for example Organizations can be ISO certified, Food products can be certified Organic or Vegan, a Person can be a certified professional, a Place can be certified for food processing. There are certifications for many domains: regulatory, organizational, recycling, food, efficiency, educational, ecological, etc. A certification is a form of credential, as are accreditations and licenses. Mapped from the [gs1:CertificationDetails](https://www.gs1.org/voc/CertificationDetails) class in the GS1 Web Vocabulary.
Enumerates the different statuses of a Certification (Active and Inactive).
One of the sections into which a book is divided. A chapter usually has a section number or a name.
An agent inspects, determines, investigates, inquires, or examines an object's accuracy, quality, condition, or state.
The act of finding an object.\n\nRelated actions:\n\n* SearchAction: FindAction is generally lead by a SearchAction, but not necessarily.
The act of an agent communicating (service provider, social media, etc) their arrival by registering/confirming for a previously reserved service (e.g. flight check-in) or at a place (e.g. hotel), possibly resulting in a result (boarding pass, etc).\n\nRelated actions:\n\n* CheckOutAction: The antonym of CheckInAction.\n* ArriveAction: Unlike ArriveAction, CheckInAction implies that the agent is informing/confirming the start of a previously reserved service.\n* ConfirmAction: Unlike ConfirmAction, CheckInAction implies that the agent is informing/confirming the *start* of a previously reserved service rather than its validity/existence.
The act of an agent communicating (service provider, social media, etc) their departure of a previously reserved service (e.g. flight check-in) or place (e.g. hotel).\n\nRelated actions:\n\n* CheckInAction: The antonym of CheckOutAction.\n* DepartAction: Unlike DepartAction, CheckOutAction implies that the agent is informing/confirming the end of a previously reserved service.\n* CancelAction: Unlike CancelAction, CheckOutAction implies that the agent is informing/confirming the end of a previously reserved service.
A chemical substance is 'a portion of matter of constant composition, composed of molecular entities of the same type or of different types' (source: [ChEBI:59999](https://www.ebi.ac.uk/chebi/searchId.do?chebiId=59999)).
The act of expressing a preference from a set of options or a large or unbounded set of choices/options.
A Claim in Schema.org represents a specific, factually-oriented claim that could be the itemReviewed in a ClaimReview. The content of a claim can be summarized with the text property. Variations on well known claims can have their common identity indicated via sameAs links, and summarized with a name. Ideally, a Claim description includes enough contextual information to minimize the risk of ambiguity or inclarity. In practice, many claims are better understood in the context in which they appear or the interpretations provided by claim reviews. Beyond ClaimReview, the Claim type can be associated with related creative works - for example a ScholarlyArticle or Question might be about some Claim. At this time, Schema.org does not define any types of relationship between claims. This is a natural area for future exploration.
A fact-checking review of claims made (or reported) in some creative work (referenced via itemReviewed).
A review of an item - for example, of a restaurant, movie, or store.
A class, also often called a 'Type'; equivalent to rdfs:Class.
A short TV or radio program or a segment/part of a program.
Computer programming source code. Example: Full (compile ready) solutions, code snippet samples, scripts, templates.
Relates a term (i.e. a property, class or enumeration) to one that supersedes it.
A collection of items, e.g. creative works or products.
A college, university, or other third-level educational institution.
The term "story" is any indivisible, re-printable unit of a comic, including the interior stories, covers, and backmatter. Most comics have at least two stories: a cover (ComicCoverArt) and an interior story.
The artwork on the outer surface of a CreativeWork.
Individual comic issues are serially published as part of a larger series. For the sake of consistency, even one-shot issues belong to a series comprised of a single issue. All comic issues can be uniquely identified by: the combination of the name and volume number of the series to which the issue belongs; the issue number; and the variant description of the issue (if any).
A part of a successively published publication such as a periodical or publication volume, often numbered, usually containing a grouping of works such as articles.\n\nSee also [blog post](http://blog.schema.org/2014/09/schemaorg-support-for-bibliographic_2.html).
A sequential publication of comic stories under a unifying title, for example "The Amazing Spider-Man" or "Groo the Wanderer".
A publication in any medium issued in successive parts bearing numerical or chronological designations and intended to continue indefinitely, such as a magazine, scholarly journal, or newspaper.\n\nSee also [blog post](http://blog.schema.org/2014/09/schemaorg-support-for-bibliographic_2.html).
The act of generating a comment about a subject.
A CompleteDataFeed is a DataFeed whose standard representation includes content for every item currently in the feed. This is the equivalent of Atom's element as defined in Feed Paging and Archiving [RFC 5005](https://tools.ietf.org/html/rfc5005), for example (and as defined for Atom), when using data from a feed that represents a collection of items that varies over time (e.g. "Top Twenty Records") there is no need to have newer entries mixed in alongside older, obsolete entries. By marking this feed as a CompleteDataFeed, old entries can be safely discarded when the feed is refreshed, since we can assume the feed has provided descriptions for all current items.
A single feed providing structured information about one or more entities or topics.
A compound price specification is one that bundles multiple prices that all apply in combination for different dimensions of consumption. Use the name property of the attached unit price specification for indicating the dimension of a price component (e.g. "electricity" or "final cleaning").
A structured value representing a price or price range. Typically, only the subclasses of this type are used for markup. It is recommended to use MonetaryAmount to describe independent amounts of money such as a salary, credit card limits, etc.
This type covers computer programming languages such as Scheme and Lisp, as well as other language-like computer representations. Natural languages are best represented with the Language type.
The act of notifying someone that a future event/action is going to happen as expected.\n\nRelated actions:\n\n* CancelAction: The antonym of ConfirmAction.
The act of notifying someone of information pertinent to them, with no expectation of a response.
A Consortium is a membership Organization whose members are typically Organizations.
The ConstraintNode type is provided to support usecases in which a node in a structured data graph is described with properties which appear to describe a single entity, but are being used in a situation where they serve a more abstract purpose. A ConstraintNode can be described using constraintProperty and numConstraints. These constraint properties can serve a variety of purposes, and their values may sometimes be understood to indicate sets of possible values rather than single, exact and specific values.
The act of ingesting information/resources/food.
A contact point—for example, a Customer Complaints department.
Enumerated options related to a ContactPoint.
One of the continents (for example, Europe or Africa).
One or more messages between organizations or people on a particular topic. Individual messages can be linked to the conversation with isPartOf or hasPart properties.
The act of deliberately creating/producing/generating/building a result out of the agent.
A comment that corrects CreativeWork.
A description of an educational course which may be offered as distinct instances which take place at different times or take place at different locations, or be offered through different media or modes of study. An educational course is a sequence of one or more educational events and/or creative works which aims to build knowledge, competence or ability of learners.
The LearningResource type can be used to indicate CreativeWorks (whether physical or digital) that have a particular and explicit orientation towards learning, education, skill acquisition, and other educational purposes. LearningResource is expected to be used as an addition to a primary type such as Book, VideoObject, Product etc. EducationEvent serves a similar purpose for event-like things (e.g. a Trip). A LearningResource may be created as a result of an EducationEvent, for example by recording one.
An instance of a Course which is distinct from other instances because it is offered at a different time or location or through different media or modes of study or to a specific section of students.
A work of art that is primarily visual in character.
A CovidTestingFacility is a MedicalClinic where testing for the COVID-19 Coronavirus disease is available. If the facility is being made available from an established Pharmacy, Hotel, or other non-medical organization, multiple types can be listed. This makes it easier to re-use existing schema.org information about that place, e.g. contact info, address, opening hours. Note that in an emergency, such information may not always be reliable.
A facility, often associated with a hospital or medical school, that is devoted to the specific diagnosis and/or healthcare. Previously limited to outpatients but with evolution it may be open to inpatients as well.
A media season, e.g. TV, radio, video game etc.
A Series in schema.org is a group of related items, typically but not necessarily of the same kind. See also CreativeWorkSeries, EventSeries.
A card payment method of a particular brand or name. Used to mark up a particular payment method and/or the financial product/service that supplies the card account.\n\nCommonly used values:\n\n* http://purl.org/goodrelations/v1#AmericanExpress\n* http://purl.org/goodrelations/v1#DinersClub\n* http://purl.org/goodrelations/v1#Discover\n* http://purl.org/goodrelations/v1#JCB\n* http://purl.org/goodrelations/v1#MasterCard\n* http://purl.org/goodrelations/v1#VISA
A financial product for the loaning of an amount of money, or line of credit, under agreed terms and charges.
A payment method using a credit, debit, store or other card to associate the payment with an account.
A CriticReview is a more specialized form of Review written or published by a source that is recognized for its reviewing activities. These can include online columns, travel and food guides, TV and radio shows, blogs and other independent Web sites. CriticReviews are typically more in-depth and professionally written. For simpler, casually written user/visitor/viewer/customer reviews, it is more appropriate to use the UserReview type. Review aggregator sites such as Metacritic already separate out the site's user reviews from selected critic reviews that originate from third-party sources.
A service to convert funds from one currency to another currency.
An alternative, closely-related condition typically considered later in the differential diagnosis process along with the signs that are used to distinguish it.
A utility class that serves as the umbrella for a number of 'intangible' things in the medical space.
A dance group—for example, the Alvin Ailey Dance Theater or Riverdance.
A performance group, such as a band, an orchestra, or a circus.
All or part of a Dataset in downloadable form.
A single item within a larger data feed.
A date value in [ISO 8601 date format](http://en.wikipedia.org/wiki/ISO_8601).
A combination of date and time of day in the form [-]CCYY-MM-DDThh:mm:ss[Z|(+|-)hh:mm] (see Chapter 5.4 of ISO 8601).
A DatedMoneySpecification represents monetary values with optional start and end dates. For example, this could represent an employee's salary over a specific period of time. __Note:__ This type has been superseded by MonetaryAmount, use of that type is recommended.
A monetary value or range. This type can be used to describe an amount of money such as $50 USD, or a range as in describing a bank account being suitable for a balance between £1,000 and £1,000,000 GBP, or the value of a salary, etc. It is recommended to use PriceSpecification Types to describe the price of an Offer, Invoice, etc.
The day of the week, e.g. used to specify to which day the opening hours of an OpeningHoursSpecification refer. Originally, URLs from [GoodRelations](http://purl.org/goodrelations/v1) were used (for Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday plus a special entry for PublicHolidays); these have now been integrated directly into schema.org.
The act of stopping or deactivating a device or application (e.g. stopping a timer or turning off a flashlight).
A defence establishment, such as an army or navy base.
A DefinedRegion is a geographic area defined by potentially arbitrary (rather than political, administrative or natural geographical) criteria. Properties are provided for defining a region by reference to sets of postal codes. Examples: a delivery destination when shopping. Region where regional pricing is configured. Requirement 1: Country: US States: "NY", "CA" Requirement 2: Country: US PostalCode Set: { [94000-94585], [97000, 97999], [13000, 13599]} { [12345, 12345], [78945, 78945], } Region = state, canton, prefecture, autonomous community...
The act of editing a recipient by removing one of its objects.
The price for the delivery of an offer using a particular delivery method.
An event involving the delivery of an item.
A delivery method is a standardized procedure for transferring the product or service to the destination of fulfillment chosen by the customer. Delivery methods are characterized by the means of transportation used, and by the organization or group that is the contracting party for the sending organization or person.\n\nCommonly used values:\n\n* http://purl.org/goodrelations/v1#DeliveryModeDirectDownload\n* http://purl.org/goodrelations/v1#DeliveryModeFreight\n* http://purl.org/goodrelations/v1#DeliveryModeMail\n* http://purl.org/goodrelations/v1#DeliveryModeOwnFleet\n* http://purl.org/goodrelations/v1#DeliveryModePickUp\n* http://purl.org/goodrelations/v1#DHL\n* http://purl.org/goodrelations/v1#FederalExpress\n* http://purl.org/goodrelations/v1#UPS
A DeliveryTimeSettings represents re-usable pieces of shipping information, relating to timing. It is designed for publication on an URL that may be referenced via the shippingSettingsLink property of an OfferShippingDetails. Several occurrences can be published, distinguished (and identified/referenced) by their different values for transitTimeLabel.
A demand entity represents the public, not necessarily binding, not necessarily exclusive, announcement by an organization or person to seek a certain type of goods or services. For describing demand using this type, the very same properties used for Offer apply.
A particular physical or virtual business of an organization for medical purposes. Examples of MedicalBusiness include different businesses run by health professionals.
A medical organization (physical or not), such as hospital, institution or clinic.
The act of departing from a place. An agent departs from a fromLocation for a destination, optionally with participants.
A type of Bank Account with a main purpose of depositing funds to gain interest or other benefits.
A medical laboratory that offers on-site or off-site diagnostic services.
A medical procedure intended primarily for diagnostic, as opposed to therapeutic, purposes.
A process of care used in either a diagnostic, therapeutic, preventive or palliative capacity that relies on invasive (surgical), non-invasive, or other techniques.
A strategy of regulating the intake of food to achieve or maintain a specific health-related goal.
A process of care involving exercise, changes to diet, fitness routines, and other lifestyle changes aimed at improving a health condition.
A product taken by mouth that contains a dietary ingredient intended to supplement the diet. Dietary ingredients may include vitamins, minerals, herbs or other botanicals, amino acids, and substances such as enzymes, organ tissues, glandulars and metabolites.
Any offered product or service. For example: a pair of shoes; a concert ticket; the rental of a car; a haircut; or an episode of a TV show streamed online.
Any matter of defined composition that has discrete existence, whose origin may be biological, mineral or chemical.
A permission for a particular person or group to access a particular file.
A type of permission which can be granted for accessing a digital document.
Enumerates some common technology platforms, for use with properties such as actionPlatform. It is not supposed to be comprehensive - when a suitable code is not enumerated here, textual or URL values can be used instead. These codes are at a fairly high level and do not deal with versioning and other nuance. Additional codes can be suggested [in github](https://github.com/schemaorg/schemaorg/issues/3057).
The act of expressing a difference of opinion with the object. An agent disagrees to/about an object (a proposition, topic or theme) with participants.
The act of discovering/finding an object.
The act of expressing a negative sentiment about the object. An agent dislikes an object (a proposition, topic or theme) with participants.
Properties that take Distances as values are of the form '<Number> <Length unit of measure>'. E.g., '7 ft'.
Quantities such as distance, time, mass, weight, etc. Particular instances of say Mass are entities like '3 kg' or '4 milligrams'.
The act of providing goods, services, or money without compensation, often for philanthropic reasons.
A specific dosing schedule for a drug or supplement.
The act of producing a visual/graphical representation of an object, typically with a pen/pencil and paper as instruments.
A picture or diagram made with a pencil, pen, or crayon rather than paint.
A value indicating which roadwheels will receive torque.
A chemical or biologic substance, used as a medical therapy, that has a physiological effect on an organism. Here the term drug is used interchangeably with the term medicine although clinical knowledge makes a clear difference between them.
A class of medical drugs, e.g., statins. Classes can represent general pharmacological class, common mechanisms of action, common physiological effects, etc.
The cost per unit of a medical drug. Note that this type is not meant to represent the price in an offer of a drug for sale; see the Offer type for that. This type will typically be used to tag wholesale or average retail cost of a drug, or maximum reimbursable cost. Costs of medical drugs vary widely depending on how and where they are paid for, so while this type captures some of the variables, costs should be used with caution by consumers of this schema's markup.
Enumerated categories of medical drug costs.
Enumerations related to health and the practice of medicine: A concept that is used to attribute a quality to another concept, as a qualifier, a collection of items or a listing of all of the elements of a set in medicine practice.
The legal availability status of a medical drug.
Categories that represent an assessment of the risk of fetal injury due to a drug or pharmaceutical used as directed by the mother during pregnancy.
Indicates whether this drug is available by prescription or over-the-counter.
A specific strength in which a medical drug is available in a specific country.
Quantity: Duration (use [ISO 8601 duration format](http://en.wikipedia.org/wiki/ISO_8601)).
Enumerates the EU energy efficiency classes A-G as well as A+, A++, and A+++ as defined in EU directive 2017/1369.
Enumerates energy efficiency levels (also known as "classes" or "ratings") and certifications that are part of several international energy efficiency standards.
An educational or occupational credential. A diploma, academic degree, certification, qualification, badge, etc., that may be awarded to a person or other entity that meets the requirements defined by the credentialer.
A program offered by an institution which determines the learning progress to achieve an outcome, usually a credential like a degree or certificate. This would define a discrete set of opportunities (e.g., job, courses) that together constitute a program with a clear start, end, set of requirements, and transition to a new occupational opportunity (e.g., a job), or sometimes a higher educational opportunity (e.g., an advanced degree).
A construction business.\n\nA HomeAndConstructionBusiness is a LocalBusiness that provides services around homes and buildings.\n\nAs a LocalBusiness it can be described as a provider of one or more Service\(s).
A single message from a sender to one or more organizations or people.
An emergency service, such as a fire station or ER.
A subclass of OrganizationRole used to describe employee relationships.
A subclass of Role used to describe roles within organizations.
An aggregate rating of an Organization related to its role as an employer.
An EmployerReview is a review of an Organization regarding its role as an employer, written by a current or former employee of that organization.
An agent approves/certifies/likes/supports/sanctions an object.
An EndorsementRating is a rating that expresses some level of endorsement, for example inclusion in a "critic's pick" blog, a "Like" or "+1" on a social network. It can be considered the result of an EndorseAction in which the object of the action is rated positively by some agent. As is common elsewhere in schema.org, it is sometimes more useful to describe the results of such an action without explicitly describing the Action. An EndorsementRating may be part of a numeric scale or organized system, but this is not required: having an explicit type for indicating a positive, endorsement rating is particularly useful in the absence of numeric scales as it helps consumers understand that the rating is broadly positive.
Properties that take Energy as values are of the form '<Number> <Energy unit of measure>'.
EnergyConsumptionDetails represents information related to the energy efficiency of a product that consumes energy. The information that can be provided is based on international regulations such as for example [EU directive 2017/1369](https://eur-lex.europa.eu/eli/reg/2017/1369/oj) for energy labeling and the [Energy labeling rule](https://www.ftc.gov/enforcement/rules/rulemaking-regulatory-reform-proceedings/energy-water-use-labeling-consumer) under the Energy Policy and Conservation Act (EPCA) in the US.
Used to indicate whether a product is EnergyStar certified.
Energy Star Energy Efficiency Enumeration
Information about the engine of the vehicle. A vehicle can have multiple engines represented by multiple engine specification entities.
An entry point, within some Web-based protocol.
A media episode (e.g. TV, radio, video game) which can be part of a series or season.
An EventAttendanceModeEnumeration value is one of potentially several modes of organising an event, relating to whether it is online or offline.
A reservation for an event like a concert, sporting event, or lecture.\n\nNote: This type is for information about actual reservations, e.g. in confirmation emails or HTML pages with individual confirmations of reservations. For offers of tickets, use Offer.
A series of Events. Included events can relate with the series using the superEvent property. An EventSeries is a collection of events that share some unifying characteristic. For example, "The Olympic Games" is a series, which is repeated regularly. The "2012 London Olympics" can be presented both as an Event in the series "Olympic Games", and as an EventSeries that included a number of sporting competitions as Events. The nature of the association between the events in an EventSeries can vary, but typical examples could include a thematic event series (e.g. topical meetups or classes), or a series of regular events that share a location, attendee group and/or organizers. EventSeries has been defined as a kind of Event to make it easy for publishers to use it in an Event context without worrying about which kinds of series are really event-like enough to call an Event. In general an EventSeries may seem more Event-like when the period of time is compact and when aspects such as location are fixed, but it may also sometimes prove useful to describe a longer-term series as an Event.
EventStatusType is an enumeration type whose instances represent several states that an Event may be in.
A structured value representing exchange rate.
The act of participating in exertive activity for the purposes of improving health and fitness.
The act of playing/exercising/training/performing for enjoyment, leisure, recreation, competition or exercise.\n\nRelated actions:\n\n* ListenAction: Unlike ListenAction (which is under ConsumeAction), PlayAction refers to performing for an audience or at an event, rather than consuming music.\n* WatchAction: Unlike WatchAction (which is under ConsumeAction), PlayAction refers to showing/displaying for an audience or at an event, rather than consuming visual content.
Fitness-related activity designed for a specific health-related purpose, including defined exercise routines as well as activity prescribed by a clinician.
Any bodily activity that enhances or maintains physical fitness and overall health and wellness. Includes activity that is part of daily living and routine, structured exercise, and exercise prescribed as part of a medical treatment or recovery plan.
Event type: Exhibition event, e.g. at a museum, library, archive, tradeshow, ...
A FAQPage is a WebPage presenting one or more "[Frequently asked questions](https://en.wikipedia.org/wiki/FAQ)" (see also QAPage).
The act of capturing sound and moving images on film, video, or digitally.
A reservation for air travel.\n\nNote: This type is for information about actual reservations, e.g. in confirmation emails or HTML pages with individual confirmations of reservations. For offers of tickets, use Offer.
Data type: Number.\n\nUsage guidelines:\n\n* Use values from 0123456789 (Unicode 'DIGIT ZERO' (U+0030) to 'DIGIT NINE' (U+0039)) rather than superficially similar Unicode symbols.\n* Use '.' (Unicode 'FULL STOP' (U+002E)) rather than ',' to indicate a decimal point. Avoid using these symbols as a readability separator.
A FloorPlan is an explicit representation of a collection of similar accommodations, allowing the provision of common information (room counts, sizes, layout diagrams) and offers for rental or sale. In typical use, some ApartmentComplex has an accommodationFloorPlan which is a FloorPlan. A FloorPlan is always in the context of a particular place, either a larger ApartmentComplex or a single Apartment. The visual/spatial aspects of a floor plan (i.e. room layout, [see wikipedia](https://en.wikipedia.org/wiki/Floor_plan)) can be indicated using image.
The act of forming a personal connection with someone/something (object) unidirectionally/asymmetrically to get updates polled from.\n\nRelated actions:\n\n* BefriendAction: Unlike BefriendAction, FollowAction implies that the connection is *not* necessarily reciprocal.\n* SubscribeAction: Unlike SubscribeAction, FollowAction implies that the follower acts as an active agent constantly/actively polling for updates.\n* RegisterAction: Unlike RegisterAction, FollowAction implies that the agent is interested in continuing receiving updates from the object.\n* JoinAction: Unlike JoinAction, FollowAction implies that the agent is interested in getting updates from the object.\n* TrackAction: Unlike TrackAction, FollowAction refers to the polling of updates of all aspects of animate objects rather than the location of inanimate objects (e.g. you track a package, but you don't follow it).
A reservation to dine at a food-related business.\n\nNote: This type is for information about actual reservations, e.g. in confirmation emails or HTML pages with individual confirmations of reservations.
A food service, like breakfast, lunch, or dinner.
A FundingAgency is an organization that implements one or more FundingSchemes and manages the granting process (via Grants, typically MonetaryGrants). A funding agency is not always required for grant funding, e.g. philanthropic giving, corporate sponsorship etc. Examples of funding agencies include ERC, REA, NIH, Bill and Melinda Gates Foundation, ...
A FundingScheme combines organizational, project and policy aspects of grant-based funding that sets guidelines, principles and mechanisms to support other kinds of projects and activities. Funding is typically organized via Grant funding. Examples of funding schemes: Swiss Priority Programmes (SPPs); EU Framework 7 (FP7); Horizon 2020; the NIH-R01 Grant Program; Wellcome institutional strategic support fund. For large scale public sector funding, the management and administration of grant awards is often handled by other, dedicated, organizations - FundingAgencys such as ERC, REA, ...
The Game type represents things which are games. These are typically rule-governed recreational activities, e.g. role-playing games in which players assume the role of characters in a fictional setting.
For a VideoGame, such as used with a PlayGameAction, an enumeration of the kind of game availability offered.
Indicates whether this game is multi-player, co-op or single-player.
Server that provides game interaction in a multiplayer game.
A discrete unit of inheritance which affects one or more biological traits (Source: [https://en.wikipedia.org/wiki/Gene](https://en.wikipedia.org/wiki/Gene)). Examples include FOXP2 (Forkhead box protein P2), SCARNA21 (small Cajal body-specific RNA 21), A- (agouti genotype).
A GeoCircle is a GeoShape representing a circular geographic area. As it is a GeoShape it provides the simple textual property 'circle', but also allows the combination of postalCode alongside geoRadius. The center of the circle can be indicated via the 'geoMidpoint' property, or more approximately using 'address', 'postalCode'.
The geographic shape of a place. A GeoShape can be described using several properties whose values are based on latitude/longitude pairs. Either whitespace or commas can be used to separate latitude and longitude; whitespace should be used when writing a list of several such points.
The geographic coordinates of a place or event.
(Eventually to be defined as) a supertype of GeoShape designed to accommodate definitions from Geo-Spatial best practices.
The act of transferring ownership of an object to a destination. Reciprocal of TakeAction.\n\nRelated actions:\n\n* TakeAction: Reciprocal of GiveAction.\n* SendAction: Unlike SendAction, GiveAction implies that ownership is being transferred (e.g. I may send my laptop to you, but that doesn't mean I'm giving it to you).
GovernmentBenefitsType enumerates several kinds of government benefits to support the COVID-19 situation. Note that this structure may not capture all benefits offered.
A government office—for example, an IRS or DMV office.
A permit issued by an organization, e.g. a parking pass.
A service provided by a government organization, e.g. food stamps, veterans benefits, etc.
A grant, typically financial or otherwise quantifiable, of resources. Typically a funder sponsors some MonetaryAmount to an Organization or Person, sometimes not necessarily via a dedicated or long-lived Project, resulting in one or more outputs, or fundedItems. For financial sponsorship, indicate the funder of a MonetaryGrant. For non-financial support, indicate sponsor of Grants of resources (e.g. office space). Grants support activities directed towards some agreed collective goals, often but not always organized as Projects. Long-lived projects are sometimes sponsored by a variety of grants over time, but it is also common for a project to be associated with a single grant. The amount of a Grant is represented using amount as a MonetaryAmount.
Guide is a page or article that recommends specific products or services, or aspects of a thing for a user to consider. A Guide may represent a Buying Guide and detail aspects of products or services for a user to consider. A Guide may represent a Product Guide and recommend specific products or services. A Guide may represent a Ranked List and recommend specific products or services with ranking.
A business that provides Heating, Ventilation and Air Conditioning services.
A [hackathon](https://en.wikipedia.org/wiki/Hackathon) event.
HealthAspectEnumeration enumerates several aspects of health content online, each of which might be described using hasHealthAspect and HealthTopicContent.
A US-style health insurance plan, including PPOs, EPOs, and HMOs.
A description of costs to the patient under a given network or formulary.
For a given health insurance plan, the specification for costs and coverage of prescription drugs.
A US-style health insurance plan network.
HealthTopicContent is WebContent that is about some aspect of a health topic, e.g. a condition, its symptoms or treatments. Such content may be comprised of several parts or sections and use different types of media. Multiple instances of WebContent (and hence HealthTopicContent) can be related using hasPart / isPartOf where there is some kind of content hierarchy, and their content described with about and mentions e.g. building upon the existing MedicalCondition vocabulary.
WebContent is a type representing all WebPage, WebSite and WebPageElement content. It is sometimes the case that detailed distinctions between Web pages, sites and their parts are not always important or obvious. The WebContent type makes it easier to describe Web-addressable content without requiring such distinctions to always be stated. (The intent is that the existing types WebPage, WebSite and WebPageElement will eventually be declared as subtypes of WebContent.)
A store that sells materials useful or necessary for various hobbies.
A hostel - cheap accommodation, often in shared dormitories. See also the dedicated document on the use of schema.org for marking up hotels and other forms of accommodations.
A hotel is an establishment that provides lodging paid on a short-term basis (source: Wikipedia, the free encyclopedia, see http://en.wikipedia.org/wiki/Hotel). See also the dedicated document on the use of schema.org for marking up hotels and other forms of accommodations.
A hotel room is a single room in a hotel. See also the dedicated document on the use of schema.org for marking up hotels and other forms of accommodations.
A room is a distinguishable space within a structure, usually separated from other spaces by interior walls (source: Wikipedia, the free encyclopedia, see http://en.wikipedia.org/wiki/Room). See also the dedicated document on the use of schema.org for marking up hotels and other forms of accommodations.
A house is a building or structure that has the ability to be occupied for habitation by humans or other creatures (source: Wikipedia, the free encyclopedia, see http://en.wikipedia.org/wiki/House).
Instructions that explain how to achieve a result by performing a sequence of steps.
A direction indicating a single action to do in the instructions for how to achieve a result.
An list item, e.g. a step in a checklist or how-to description.
An item used as either a tool or supply when performing the instructions for how to achieve a result.
A sub-grouping of steps in the instructions for how to achieve a result (e.g. steps for making a pie crust within a pie recipe).
A step in the instructions for how to achieve a result. It is an ordered list with HowToDirection and/or HowToTip items.
A supply consumed when performing the instructions for how to achieve a result.
An explanation in the instructions for how to achieve a result. It provides supplementary information about a technique, supply, author's preference, etc. It can explain what could be done, or what should not be done, but doesn't specify what should be done (see HowToDirection).
A tool used (but not consumed) when performing instructions for how to achieve a result.
A HyperToc represents a hypertext table of contents for complex media objects, such as VideoObject, AudioObject. Items in the table of contents are indicated using the tocEntry property, and typed HyperTocEntry. For cases where the same larger work is split into multiple files, associatedMedia can be used on individual HyperTocEntry items.
A HyperToEntry is an item within a HyperToc, which represents a hypertext table of contents for complex media objects, such as VideoObject, AudioObject. The media object itself is indicated using associatedMedia. Each section of interest within that content can be described with a HyperTocEntry, with associated startOffset and endOffset. When several entries are all from the same file, associatedMedia is used on the overarching HyperTocEntry; if the content has been split into multiple files, they can be referenced using associatedMedia on each HyperTocEntry.
IPTC "Digital Source" codes for use with the digitalSourceType property, providing information about the source for a digital media object. In general these codes are not declared here to be mutually exclusive, although some combinations would be contradictory if applied simultaneously, or might be considered mutually incompatible by upstream maintainers of the definitions. See the IPTC documentation for detailed definitions of all terms.
MediaEnumeration enumerations are lists of codes, labels etc. useful for describing media objects. They may be reflections of externally developed lists, or created at schema.org, or a combination.
The act of intentionally disregarding the object. An agent ignores an object.
Web page type: Media gallery page. A mixed-media page that can contain media such as images, videos, and other multimedia.
A specific and exact (byte-for-byte) version of an ImageObject. Two byte-for-byte identical files, for the purposes of this type, considered identical. If they have different embedded metadata (e.g. XMP, EXIF) the files will differ. Different external facts about the files, e.g. creator or dateCreated that aren't represented in their actual content, do not affect this notion of identity.
Any medical imaging modality typically used for diagnostic purposes.
An individual medical practitioner. For their official address use address, for affiliations to hospitals use hospitalAffiliation. The practicesAt property can be used to indicate MedicalOrganization hospitals, clinics, pharmacies etc. where this physician practices.
An individual physician or a physician's office considered as a MedicalOrganization.
A single, identifiable product instance (e.g. a laptop with a particular serial number).
Classes of agents or pathogens that transmit infectious diseases. Enumerated type.
An infectious disease is a clinically evident human disease resulting from the presence of pathogenic microbial agents, like pathogenic viruses, pathogenic bacteria, fungi, protozoa, multicellular parasites, and prions. To be considered an infectious disease, such pathogens are known to be able to cause this disease.
Any condition of the human body that affects the normal functioning of a person, whether physically or mentally. Includes diseases, injuries, disabilities, disorders, syndromes, etc.
A summary of how users have interacted with this CreativeWork. In most cases, authors will use a subtype to specify the specific type of interaction.
A company or fund that gathers capital from a number of investors to create a pool of money that is then re-invested into stocks, bonds and other assets.
The act of asking someone to attend an event. Reciprocal of RsvpAction.
A statement of the money due for goods or services; a bill.
A list of possible product availability options.
Enumerated for values for itemListOrder for indicating how an ordered ItemList is organized.
A page devoted to a single item, such as a particular product or hotel.
A listing that describes a job opening in a certain organization.
An agent joins an event/group with participants/friends at a location.\n\nRelated actions:\n\n* RegisterAction: Unlike RegisterAction, JoinAction refers to joining a group/team of people.\n* SubscribeAction: Unlike SubscribeAction, JoinAction does not imply that you'll be receiving updates.\n* FollowAction: Unlike FollowAction, JoinAction does not imply that you'll be polling for updates.
The anatomical location at which two or more bones make contact.
Natural languages such as Spanish, Tamil, Hindi, English, etc. Formal language code tags expressed in [BCP 47](https://en.wikipedia.org/wiki/IETF_language_tag) can be used via the alternateName property. The Language type previously also covered programming languages such as Scheme and Lisp, which are now best represented using ComputerLanguage.
An agent leaves an event / group with participants/friends at a location.\n\nRelated actions:\n\n* JoinAction: The antonym of LeaveAction.\n* UnRegisterAction: Unlike UnRegisterAction, LeaveAction implies leaving a group/team of people rather than a service.
A list of possible statuses for the legal force of a legislation.
A list of possible levels for the legal validity of a legislation.
A legal document such as an act, decree, bill, etc. (enforceable or not) or a component of a legal act (like an article).
A specific object or file containing a Legislation. Note that the same Legislation can be published in multiple files. For example, a digitally signed PDF, a plain PDF and an HTML version.
A legislative building—for example, the state capitol.
The act of providing an object under an agreement that it will be returned at a later date. Reciprocal of BorrowAction.\n\nRelated actions:\n\n* BorrowAction: Reciprocal of LendAction.
A LibrarySystem is a collaborative system amongst several libraries.
A short band of tough, flexible, fibrous connective tissue that functions to connect multiple bones, cartilages, and structurally support joints.
The act of expressing a positive sentiment about the object. An agent likes an object (a proposition, topic or theme) with participants.
A Role that represents a Web link, e.g. as expressed via the 'url' property. Its linkRelationship property can indicate URL-based and plain textual link types, e.g. those in IANA link registry or others such as 'amphtml'. This structure provides a placeholder where details from HTML's link element can be represented outside of HTML, e.g. in JSON-LD feeds.
Represents additional information about a relationship or property. For example a Role can be used to say that a 'member' role linking some SportsTeam to a player occurred during a particular time period. Or that a Person's 'actor' role in a Movie was for some particular characterName. Such properties can be attached to a Role entity, which is then associated with the main entities using ordinary properties like 'member' or 'actor'.\n\nSee also [blog post](http://blog.schema.org/2014/06/introducing-role.html).
A shop that sells alcoholic drinks such as wine, beer, whisky and other spirits.
A LiveBlogPosting is a BlogPosting intended to provide a rolling textual coverage of an ongoing event through continuous updates.
Specifies a location feature by providing a structured value representing a feature of an accommodation as a property-value pair of varying degrees of formality.
A property-value pair, e.g. representing a feature of a product or place. Use the 'name' property for the name of the property. If there is an additional human-readable version of the value, put that into the 'description' property.\n\n Always use specific schema.org properties when a) they exist and b) you can populate them. Using PropertyValue as a substitute will typically not trigger the same effect as using the original, specific property.
A reservation for lodging at a hotel, motel, inn, etc.\n\nNote: This type is for information about actual reservations, e.g. in confirmation emails or HTML pages with individual confirmations of reservations.
The act of being defeated in a competitive activity.
A type of blood vessel that specifically carries lymph fluid unidirectionally toward the heart.
A book, document, or piece of music written by hand rather than typed or printed.
Properties that take Mass as values are of the form '<Number> <Mass unit of measure>'. E.g., '7 kg'.
A math solver which is capable of solving a subset of mathematical problems.
The maximum dosing schedule considered safe for a drug or supplement as recommended by an authority or by the drug/supplement's manufacturer. Capture the recommending authority in the recognizingAuthority property of MedicalEntity.
Enumeration(s) for use with measurementMethod.
Codes for use with the mediaAuthenticityCategory property, indicating the authenticity of a media object (in the context of how it was published or shared). In general these codes are not mutually exclusive, although some combinations (such as 'original' versus 'transformed', 'edited' and 'staged') would be contradictory if applied in the same MediaReview. Note that the application of these codes is with regard to a piece of media shared or published in a particular context.
A MediaReview is a more specialized form of Review dedicated to the evaluation of media content online, typically in the context of fact-checking and misinformation. For more general reviews of media in the broader sense, use UserReview, CriticReview or other Review types. This definition is a work in progress. While the MediaManipulationRatingEnumeration list reflects significant community review amongst fact-checkers and others working to combat misinformation, the specific structures for representing media objects, their versions and publication context, are still evolving. Similarly, best practices for the relationship between MediaReview and ClaimReview markup have not yet been finalized.
Represents an item or group of closely related items treated as a unit for the sake of evaluation in a MediaReview. Authorship etc. apply to the items rather than to the curation/grouping or reviewing party.
A subscription which allows a user to access media including audio, video, books, etc.
A set of characteristics belonging to people, e.g. who compose an item's target audience.
Target audiences types for medical web pages. Enumerated type.
The causative agent(s) that are responsible for the pathophysiologic process that eventually results in a medical condition, symptom or sign. In this schema, unless otherwise specified this is meant to be the proximate cause of the medical condition, symptom or sign. The proximate cause is defined as the causative agent that most directly results in the medical condition, symptom or sign. For example, the HIV virus could be considered a cause of AIDS. Or in a diagnostic context, if a patient fell and sustained a hip fracture and two days later sustained a pulmonary embolism which eventuated in a cardiac arrest, the cause of the cardiac arrest (the proximate cause) would be the pulmonary embolism and not the fall. Medical causes can include cardiovascular, chemical, dermatologic, endocrine, environmental, gastroenterologic, genetic, hematologic, gynecologic, iatrogenic, infectious, musculoskeletal, neurologic, nutritional, obstetric, oncologic, otolaryngologic, pharmacologic, psychiatric, pulmonary, renal, rheumatologic, toxic, traumatic, or urologic causes; medical conditions can be causes as well.
A stage of a medical condition, such as 'Stage IIIa'.
A condition or factor that serves as a reason to withhold a certain medical therapy. Contraindications can be absolute (there are no reasonable circumstances for undertaking a course of action) or relative (the patient is at higher risk of complications, but these risks may be outweighed by other considerations or mitigated by other measures).
Any object used in a medical capacity, such as to diagnose or treat a patient.
Categories of medical devices, organized by the purpose or intended use of the device.
Level of evidence for a medical guideline. Enumerated type.
Any recommendation made by a standard society (e.g. ACC/AHA) or consensus statement that denotes how to diagnose and treat a particular condition. Note: this type should be used to tag the actual guideline recommendation; if the guideline recommendation occurs in a larger scholarly article, use MedicalScholarlyArticle to tag the overall article, not this type. Note also: the organization making the recommendation should be captured in the recognizingAuthority base property of MedicalEntity.
A guideline contraindication that designates a process as harmful and where quality of the data supporting the contraindication is sound.
A guideline recommendation that is regarded as efficacious and where quality of the data supporting the recommendation is sound.
Any medical imaging modality typically used for diagnostic purposes. Enumerated type.
An observational study is a type of medical study that attempts to infer the possible effect of a treatment through observation of a cohort of subjects over a period of time. In an observational study, the assignment of subjects into treatment groups versus control groups is outside the control of the investigator. This is in contrast with controlled studies, such as the randomized controlled trials represented by MedicalTrial, where each subject is randomly assigned to a treatment group or a control group before the start of the treatment.
A medical study is an umbrella type covering all kinds of research studies relating to human medicine or health, including observational studies and interventional trials and registries, randomized, controlled or not. When the specific type of study is known, use one of the extensions of this type, such as MedicalTrial or MedicalObservationalStudy. Also, note that this type should be used to mark up data that describes the study itself; to tag an article that publishes the results of a study, use MedicalScholarlyArticle. Note: use the code property of MedicalEntity to store study IDs, e.g. clinicaltrials.gov ID.
Design models for observational medical studies. Enumerated type.
An enumeration that describes different types of medical procedures.
A complex mathematical calculation requiring an online calculator, used to assess prognosis. Note: use the url property of Thing to record any URLs for online calculators.
Any rule set or interactive tool for estimating the risk of developing a complication or condition.
A risk factor is anything that increases a person's likelihood of developing or contracting a disease, medical condition, or complication.
A simple system that adds up the number of risk factors to yield a score that is associated with prognosis, e.g. CHAD score, TIMI risk score.
A scholarly article in the medical domain.
Any physical manifestation of a person's medical condition discoverable by objective diagnostic tests or physical examination.
Any feature associated or not with a medical condition. In medicine a symptom is generally subjective while a sign is objective.
Any specific branch of medical science or practice. Medical specialities include clinical specialties that pertain to particular organ systems and their respective disease states, as well as allied health specialties. Enumerated type.
Any branch of a field in which people typically develop specific expertise, usually after significant study, time, and effort.
The status of a medical study. Enumerated type.
Any complaint sensed and expressed by the patient (therefore defined as subjective) like stomachache, lower-back pain, or fatigue.
Any collection of tests commonly ordered together.
Any medical intervention designed to prevent, treat, and cure human diseases and medical conditions, including both curative and palliative therapies. Medical therapies are typically processes of care relying upon pharmacotherapy, behavioral therapy, supportive therapy (with fluid or nutrition for example), or detoxification (e.g. hemodialysis) aimed at improving or preventing a health condition.
A medical procedure intended primarily for therapeutic purposes, aimed at improving a health condition.
A medical trial is a type of medical study that uses a scientific process to compare the safety and efficacy of medical therapies or medical procedures. In general, medical trials are controlled and subjects are allocated at random to the different treatment and/or control groups.
Design models for medical trials. Enumerated type.
A web page that provides medical information.
A meeting room, conference room, or conference hall is a room provided for singular events such as business conferences and meetings (source: Wikipedia, the free encyclopedia, see http://en.wikipedia.org/wiki/Conference_hall). See also the dedicated document on the use of schema.org for marking up hotels and other forms of accommodations.
A MemberProgram defines a loyalty (or membership) program that provides its members with certain benefits, for example better pricing, free shipping or returns, or the ability to earn loyalty points. Member programs may have multiple tiers, for example silver and gold members, each with different benefits.
A MemberProgramTier specifies a tier under a loyalty (member) program, for example "gold".
A structured representation of food or drink items available from a FoodEstablishment.
A food or drink item listed in a menu or menu section.
A sub-grouping of food or drink items in a menu. E.g. courses (such as 'Dinner', 'Breakfast', etc.), specific type of dishes (such as 'Meat', 'Vegan', 'Drinks', etc.), or some other classification made by the menu provider.
Enumerates several kinds of product return policies.
A MerchantReturnPolicy provides information about product return policies associated with an Organization, Product, or Offer.
A seasonal override of a return policy, for example used for holidays.
Merchant Return Policy Seasonal Override
A middle school (typically for children aged around 11-14, although this varies somewhat).
A software application designed specifically to work well on a mobile device such as a telephone.
A store that sells mobile phones and related accessories.
Any constitutionally or isotopically distinct atom, molecule, ion, ion pair, radical, radical ion, complex, conformer etc., identifiable as a separately distinguishable entity.
A statistical distribution of monetary amounts.
The act of transferring money from one place to another place. This may occur electronically or physically.
A loan in which property or real estate is used as collateral. (A loan securitized against some real estate.)
A motel. See also the dedicated document on the use of schema.org for marking up hotels and other forms of accommodations.
A motorcycle or motorbike is a single-track, two-wheeled motor vehicle.
A motorized bicycle is a bicycle with an attached motor used to power the vehicle, or to assist with pedaling.
A mountain, like Mount Whitney or Mount Everest.
A series of movies. Included movies can be indicated with the hasPart property.
A muscle is an anatomical structure consisting of a contractile form of tissue that animals use to effect movement.
A collection of music tracks in playlist form.
Classification of the album by its type of content: soundtrack, live album, studio album, etc.
The kind of release which this album is: single, EP or album.
A musical group, such as a band, an orchestra, or a choir. Can also be a solo musician.
A music recording (track), usually a single song.
A MusicRelease is a specific release of a music album.
Format of this release (the type of recording media used, i.e. compact disc, digital media, LP, etc.).
Organization: Non-governmental Organization.
NLNonprofitType: Non-profit organization type originating from the Netherlands.
NonprofitType enumerates several kinds of official non-profit types of which a non-profit organization can be.
A common pathway for the electrochemical nerve impulses that are transmitted along each of the axons.
A News/Media organization such as a newspaper or TV station.
A publication containing information about varied topics that are pertinent to general information, a geographic area, or a specific subject matter (i.e. business, culture, education). Often published daily.
A file containing a note, primarily for the author.
Nutritional information about the recipe.
Instances of the class Observation are used to specify observations about an entity at a particular time. The principal properties of an Observation are observationAbout, measuredProperty, statType, [[value] and observationDate and measuredProperty. Some but not all Observations represent a QuantitativeValue. Quantitative observations can be about a StatisticalVariable, which is an abstract specification about which we can make observations that are grounded at a particular location and time. Observations can also encode a subset of simple RDF-like statements (its observationAbout, a StatisticalVariable, defining the measuredPoperty; its observationAbout property indicating the entity the statement is about, and value ) In the context of a quantitative knowledge graph, typical properties could include measuredProperty, observationAbout, observationDate, value, unitCode, unitText, measurementMethod.
A point value or interval for product characteristics and other purposes.
A profession, may involve prolonged training and/or a formal qualification.
Indicates employment-related experience requirements, e.g. monthsOfExperience.
A treatment of people with physical, emotional, or social problems, using purposeful activity to help them overcome or learn to deal with their problems.
An OfferCatalog is an ItemList that contains related Offers and/or further OfferCatalogs that are offeredBy the same provider.
An OfferForLease in Schema.org represents an Offer to lease out something, i.e. an Offer whose businessFunction is [lease out](http://purl.org/goodrelations/v1#LeaseOut.). See [Good Relations](https://en.wikipedia.org/wiki/GoodRelations) for background on the underlying concepts.
An OfferForPurchase in Schema.org represents an Offer to sell something, i.e. an Offer whose businessFunction is [sell](http://purl.org/goodrelations/v1#Sell.). See [Good Relations](https://en.wikipedia.org/wiki/GoodRelations) for background on the underlying concepts.
A list of possible conditions for the item.
OfferShippingDetails represents information about shipping destinations. Multiple of these entities can be used to represent different shipping rates for different destinations: One entity for Alaska/Hawaii. A different one for continental US. A different one for all France. Multiple of these entities can be used to represent different shipping costs and delivery times. Two entities that are identical but differ in rate and time: E.g. Cheaper and slower: $5 in 5-7 days or Fast and expensive: $15 in 1-2 days.
A publication event, e.g. catch-up TV or radio podcast, during which a program is available on-demand.
A particular online business, either standalone or the online part of a broader organization. Examples include an eCommerce site, an online travel booking site, an online learning site, an online logistics and shipping provider, an online (virtual) doctor, etc.
A structured value providing information about the opening hours of a place or a certain service inside a place.\n\nThe place is __open__ if the opens property is specified, and __closed__ otherwise.\n\nIf the value for the closes property is less than the value for the opens property then the hour range is assumed to span over the next day.
An OpinionNewsArticle is a NewsArticle that primarily expresses opinions rather than journalistic reporting of news and events. For example, a NewsArticle consisting of a column or Blog/BlogPosting entry in the Opinions section of a news publication.
A store that sells reading glasses and similar devices for improving vision.
An order is a confirmation of a transaction (a receipt), which can contain multiple line items, each represented by an Offer that has been accepted by the customer.
An agent orders an object/product/service to be delivered/sent.
An order item is a line of an order. It includes the quantity and shipping details of a bought offer.
A structured value providing information about when a certain organization or person owned a certain product.
The act of producing a painting, typically with paint and canvas as instruments.
A medical procedure intended primarily for palliative purposes, aimed at relieving the symptoms of an underlying health condition.
The delivery of a parcel either via the postal service or a commercial service.
A set of characteristics describing parents, who can be interested in viewing some content.
A parking lot or other parking facility.
A medical test performed by a laboratory that typically involves examination of a tissue sample by a pathologist.
A patient is any person recipient of health care services.
A shop that will buy, or lend money against the security of, personal possessions.
A payment method is a standardized procedure for transferring the monetary amount for a purchase. Payment methods are characterized by the legal and technical structures used, and by the organization or group carrying out the transaction. The following legacy values should be accepted: \n\n* http://purl.org/goodrelations/v1#ByBankTransferInAdvance\n* http://purl.org/goodrelations/v1#ByInvoice\n* http://purl.org/goodrelations/v1#Cash\n* http://purl.org/goodrelations/v1#CheckInAdvance\n* http://purl.org/goodrelations/v1#COD\n* http://purl.org/goodrelations/v1#DirectDebit\n* http://purl.org/goodrelations/v1#GoogleCheckout\n* http://purl.org/goodrelations/v1#PayPal\n* http://purl.org/goodrelations/v1#PaySwarm\n\nStructured values are recommended for newer payment methods.
The costs of settling the payment using a particular payment method.
The type of payment method, only for generic payment types, specific forms of payments, like card payment should be expressed using subclasses of PaymentMethod.
A Service to transfer funds from a person or organization to a beneficiary person or organization.
A specific payment status. For example, PaymentDue, PaymentComplete, etc.
The act of participating in performance arts.
A PerformanceRole is a Role that some entity places with regard to a theatrical performance, e.g. in a Movie, TVSeries etc.
A theater or other performing art center.
The act of capturing still images of objects using a camera.
Categories of physical activity, organized by physiologic classification.
A type of physical examination of a patient performed by a physician.
A process of progressive physical care and rehabilitation aimed at improving a health condition.
A play is a form of literature, usually consisting of dialogue between characters, intended for theatrical performance rather than just reading. Note: A performance of a Play would be a TheaterEvent or BroadcastEvent - the *Play* being the workPerformed.
A single season of a podcast. Many podcasts do not break down into separate seasons. In that case, PodcastSeries should be used.
A podcast is an episodic series of digital audio or video files which a user can download and listen to.
Indicates a range of postal codes, usually defined as the set of valid codes between postalCodeBegin and postalCodeEnd, inclusively.
A large, usually printed placard, bill, or announcement, often illustrated, that is posted to advertise or publicize something.
An agent orders a (not yet released) object/product/service to be delivered/sent.
The act of inserting at the beginning if an ordered collection.
A file containing slides or used for a presentation.
An indication for preventing an underlying condition, symptom, etc.
Enumerates different price components that together make up the total price for an offered product.
Enumerates different price types, for example list price, invoice price, and sale price.
A set of products (either ProductGroups or specific variants) that are listed together e.g. in an Offer.
A ProductGroup represents a group of Products that vary only in certain well-described ways, such as by size, color, material etc. While a ProductGroup itself is not directly offered for sale, the various varying products that it represents can be. The ProductGroup serves as a prototype or template, standing in for all of the products who have an isVariantOf relationship to it. As such, properties (including additional types) can be applied to the ProductGroup to represent characteristics shared by each of the (possibly very many) variants. Properties that reference a ProductGroup are not included in this mechanism; neither are the following specific properties variesBy, hasVariant, url.
A datasheet or vendor specification of a product (in the sense of a prototypical description).
Original definition: "provider of professional services."\n\nThe general ProfessionalService type for local businesses was deprecated due to confusion with Service. For reference, the types that it included were: Dentist, AccountingService, Attorney, Notary, as well as types for several kinds of HomeAndConstructionBusiness: Electrician, GeneralContractor, HousePainter, Locksmith, Plumber, RoofingContractor. LegalService was introduced as a more inclusive supertype of Attorney.
Used to describe membership in a loyalty programs (e.g. "StarAliance"), traveler clubs (e.g. "AAA"), purchase clubs ("Safeway Club"), etc.
A property, used to indicate attributes and relationships of some Thing; equivalent to rdf:Property.
Protein is here used in its widest possible definition, as classes of amino acid based molecules. Amyloid-beta Protein in human (UniProt P05067), eukaryota (e.g. an OrthoDB group) or even a single molecule that one can point to are all of type :Protein. A protein can thus be a subclass of another protein, e.g. :Protein as a UniProt record can have multiple isoforms inside it which would also be :Protein. They can be imagined, synthetic, hypothetical or naturally occurring.
A process of care relying upon counseling, dialogue and communication aimed at improving a mental health condition without use of drugs.
A public toilet is a room or small building containing one or more toilets (and possibly also urinals) which is available for use by the general public, or by customers or employees of certain businesses.
A part of a successively published publication such as a periodical or multi-volume work, often numbered. It may represent a time span, such as a year.\n\nSee also [blog post](http://blog.schema.org/2014/09/schemaorg-support-for-bibliographic_2.html).
A QAPage is a WebPage focussed on a specific Question and its Answer(s), e.g. in a question answering site or documenting Frequently Asked Questions (FAQs).
A specific question - e.g. from a user seeking answers online, or collected in a Frequently Asked Questions (FAQ) document.
Quiz: A test of knowledge, skills and abilities.
A quotation. Often but not necessarily from some written work, attributable to a real world author and - if associated with a fictional character - to any fictional Person. Use isBasedOn to link to source/origin. The recordedIn property can be used to reference a Quotation from an Event.
An agent quotes/estimates/appraises an object/product/service with a price at a location/store.
A place offering space for "Recreational Vehicles", Caravans, mobile homes and the like.
A process of care using radiation aimed at improving a health condition.
A delivery service through which radio content is provided via broadcast over the air or online.
A short radio program or a segment/part of a radio program.
A radio episode which can be part of a series or season.
Season dedicated to radio broadcast and associated online delivery.
CreativeWorkSeries dedicated to radio broadcast and associated online delivery.
A RealEstateListing is a listing that describes one or more real-estate Offers (whose businessFunction is typically to lease out, or to sell). The RealEstateListing type itself represents the overall listing, as manifested in some WebPage.
The act of physically/electronically taking delivery of an object that has been transferred from an origin to a destination. Reciprocal of SendAction.\n\nRelated actions:\n\n* SendAction: The reciprocal of ReceiveAction.\n* TakeAction: Unlike TakeAction, ReceiveAction does not imply that the ownership has been transferred (e.g. I can receive a package, but it does not mean the package is now mine).
A recipe. For dietary restrictions covered by the recipe, a few common restrictions are enumerated via suitableForDiet. The keywords property can also be used to add more detail.
Recommendation is a type of Review that suggests or proposes something as the best option or best course of action. Recommendations may be for products or services, or other concrete things, as in the case of a ranked list or product guide. A Guide may list multiple recommendations for different categories. For example, in a Guide about which TVs to buy, the author may have several Recommendations.
A recommended dosing schedule for a drug or supplement as prescribed or recommended by an authority or by the drug/supplement's manufacturer. Capture the recommending authority in the recognizingAuthority property of MedicalEntity.
Enumerates several kinds of product return refund types.
The act of registering to be a user of a service, product or web page.\n\nRelated actions:\n\n* JoinAction: Unlike JoinAction, RegisterAction implies you are registering to be a user of a service, *not* a group/team of people.\n* FollowAction: Unlike FollowAction, RegisterAction doesn't imply that the agent is expecting to poll for updates from the object.\n* SubscribeAction: Unlike SubscribeAction, RegisterAction doesn't imply that the agent is expecting updates from the object.
The act of rejecting to/adopting an object.\n\nRelated actions:\n\n* AcceptAction: The antonym of RejectAction.
The act of giving money in return for temporary use, but not ownership, of an object such as a vehicle or property. For example, an agent rents a property from a landlord in exchange for a periodic payment.
A reservation for a rental car.\n\nNote: This type is for information about actual reservations, e.g. in confirmation emails or HTML pages with individual confirmations of reservations.
A structured value representing repayment.
The act of editing a recipient by replacing an old object with a new object.
The act of responding to a question/message asked/sent by the object. Related to AskAction.\n\nRelated actions:\n\n* AskAction: Appears generally as an origin of a ReplyAction.
A Report generated by governmental or non-governmental organization.
The ReportageNewsArticle type is a subtype of NewsArticle representing news articles which are the result of journalistic news reporting conventions. In practice many news publishers produce a wide variety of article types, many of which might be considered a NewsArticle but not a ReportageNewsArticle. For example, opinion pieces, reviews, analysis, sponsored or satirical articles, or articles that combine several of these elements. The ReportageNewsArticle type is based on a stricter ideal for "news" as a work of journalism, with articles based on factual information either observed or verified by the author, or reported and verified from knowledgeable sources. This often includes perspectives from multiple viewpoints on a particular issue (distinguishing news reports from public relations or propaganda). News reports in the ReportageNewsArticle sense de-emphasize the opinion of the author, with commentary and value judgements typically expressed elsewhere. A ReportageNewsArticle which goes deeper into analysis can also be marked with an additional type of AnalysisNewsArticle.
A patient-reported or observed dosing schedule for a drug or supplement.
A Research Organization (e.g. scientific institute, research company).
A group of multiple reservations with common values for all sub-reservations.
Enumerated status values for Reservation.
Reserving a concrete object.\n\nRelated actions:\n\n* ScheduleAction: Unlike ScheduleAction, ReserveAction reserves concrete objects (e.g. a table, a hotel) towards a time slot / spatial allocation.
A reservoir of water, typically an artificially created lake, like the Lake Kariba reservoir.
A resort is a place used for relaxation or recreation, attracting visitors for holidays or vacations. Resorts are places, towns or sometimes commercial establishments operated by a single company (source: Wikipedia, the free encyclopedia, see http://en.wikipedia.org/wiki/Resort). See also the dedicated document on the use of schema.org for marking up hotels and other forms of accommodations.
A diet restricted to certain foods or preparations for cultural, religious, health or lifestyle reasons.
The act of resuming a device or application which was formerly paused (e.g. resume music playback or resume a timer).
The act of returning to the origin that which was previously received (concrete objects) or taken (ownership).
Enumerates several kinds of policies for product return fees.
Enumerates several types of return labels for product returns.
Enumerates several types of product return methods.
The act of producing a balanced opinion about the object for an audience. An agent reviews an object with participants resulting in a review.
A NewsArticle and CriticReview providing a professional critic's assessment of a service, product, performance, or artistic or literary work.
A river (for example, the broad majestic Shannon).
The act of notifying an event organizer as to whether you expect to attend the event.
RsvpResponseType is an enumeration type whose instances represent responding to an RSVP request.
An Article whose content is primarily satirical(https://en.wikipedia.org/wiki/Satire) in nature, i.e. unlikely to be literally true. A satirical article is sometimes but not necessarily also a NewsArticle. ScholarlyArticles are also sometimes satirized.
A schedule defines a repeating time period used to describe a regularly occurring Event. At a minimum a schedule will specify repeatFrequency which describes the interval between occurrences of the event. Additional information can be provided to specify the schedule more precisely. This includes identifying the day(s) of the week or month when the recurring event will take place, in addition to its start and end time. Schedules may also have start and end dates to indicate when they are active, e.g. to define a limited calendar of events.
Scheduling future actions, events, or tasks.\n\nRelated actions:\n\n* ReserveAction: Unlike ReserveAction, ScheduleAction allocates future actions (e.g. an event, a task, etc) towards a time slot / spatial allocation.
A School District is an administrative area for the administration of schools.
The act of searching for an object.\n\nRelated actions:\n\n* FindAction: SearchAction generally leads to a FindAction, but not necessarily.
A Search and Rescue organization of some kind.
Used to describe a seat, such as a reserved seat in an event reservation.
This is the Action of navigating to a specific startOffset timestamp within a VideoObject, typically represented with a URL template structure.
The act of taking money from a buyer in exchange for goods or services rendered. An agent sells an object, product, or service to a buyer for a price. Reciprocal of BuyAction.
The act of physically/electronically dispatching an object for transfer from an origin to a destination. Related actions:\n\n* ReceiveAction: The reciprocal of SendAction.\n* GiveAction: Unlike GiveAction, SendAction does not imply the transfer of ownership (e.g. I can send you my laptop, but I'm not necessarily giving it to you).
A means for accessing a service, e.g. a government office location, web site, or phone number.
The act of distributing content to people for their amusement or edification.
Printed music, as opposed to performed or recorded music.
ShippingDeliveryTime provides various pieces of information about delivery times for shipping.
A ShippingRateSettings represents re-usable pieces of shipping information. It is designed for publication on an URL that may be referenced via the shippingSettingsLink property of an OfferShippingDetails. Several occurrences can be published, distinguished and matched (i.e. identified/referenced) by their different values for shippingLabel.
Short story or tale. A brief work of literature, usually written in narrative prose.
A web page element, like a table or an image.
Enumerates common size groups for various product categories.
Size related properties of a product, typically a size code (name) and optionally a sizeSystem, sizeGroup, and product measurements (hasMeasurement). In addition, the intended audience can be defined through suggestedAge, suggestedGender, and suggested body measurements (suggestedMeasurement).
Enumerates common size systems for different categories of products, for example "EN-13402" or "UK" for wearables or "Imperial" for screws.
The action that takes in a math expression and directs users to a page potentially capable of solving/simplifying that expression.
A placeholder for multiple similar products of the same kind.
A SpeakableSpecification indicates (typically via xpath or cssSelector) sections of a document that are highlighted as particularly speakable. Instances of this type are expected to be used primarily as values of the speakable property.
A SpecialAnnouncement combines a simple date-stamped textual information update with contextualized Web links and other structured data. It represents an information update made by a locally-oriented organization, for example schools, pharmacies, healthcare providers, community groups, police, local government. For work in progress guidelines on Coronavirus-related markup see [this doc](https://docs.google.com/document/d/14ikaGCKxo50rRM7nvKSlbUpjyIk2WMQd3IkB1lItlrM/edit#). The motivating scenario for SpecialAnnouncement is the [Coronavirus pandemic](https://en.wikipedia.org/wiki/2019%E2%80%9320_coronavirus_pandemic), and the initial vocabulary is oriented to this urgent situation. Schema.org expect to improve the markup iteratively as it is deployed and as feedback emerges from use. In addition to our usual [Github entry](https://github.com/schemaorg/schemaorg/issues/2490), feedback comments can also be provided in [this document](https://docs.google.com/document/d/1fpdFFxk8s87CWwACs53SGkYv3aafSxz_DTtOQxMrBJQ/edit#). While this schema is designed to communicate urgent crisis-related information, it is not the same as an emergency warning technology like [CAP](https://en.wikipedia.org/wiki/Common_Alerting_Protocol), although there may be overlaps. The intent is to cover the kinds of everyday practical information being posted to existing websites during an emergency situation. Several kinds of information can be provided: We encourage the provision of "name", "text", "datePosted", "expires" (if appropriate), "category" and "url" as a simple baseline. It is important to provide a value for "category" where possible, most ideally as a well known URL from Wikipedia or Wikidata. In the case of the 2019-2020 Coronavirus pandemic, this should be "https://en.wikipedia.org/w/index.php?title=2019-20\_coronavirus\_pandemic" or "https://www.wikidata.org/wiki/Q81068910". For many of the possible properties, values can either be simple links or an inline description, depending on whether a summary is available. For a link, provide just the URL of the appropriate page as the property's value. For an inline description, use a WebContent type, and provide the url as a property of that, alongside at least a simple "text" summary of the page. It is unlikely that a single SpecialAnnouncement will need all of the possible properties simultaneously. We expect that in many cases the page referenced might contain more specialized structured data, e.g. contact info, openingHours, Event, FAQPage etc. By linking to those pages from a SpecialAnnouncement you can help make it clearer that the events are related to the situation (e.g. Coronavirus) indicated by the category property of the SpecialAnnouncement. Many SpecialAnnouncements will relate to particular regions and to identifiable local organizations. Use spatialCoverage for the region, and announcementLocation to indicate specific LocalBusinesses and CivicStructures. If the announcement affects both a particular region and a specific location (for example, a library closure that serves an entire region), use both spatialCoverage and announcementLocation. The about property can be used to indicate entities that are the focus of the announcement. We now recommend using about only for representing non-location entities (e.g. a Course or a RadioStation). For places, use announcementLocation and spatialCoverage. Consumers of this markup should be aware that the initial design encouraged the use of about for locations too. The basic content of SpecialAnnouncement is similar to that of an [RSS](https://en.wikipedia.org/wiki/RSS) or [Atom](https://en.wikipedia.org/wiki/Atom_(Web_standard)) feed. For publishers without such feeds, basic feed-like information can be shared by posting SpecialAnnouncement updates in a page, e.g. using JSON-LD. For sites with Atom/RSS functionality, you can point to a feed with the webFeed property. This can be a simple URL, or an inline DataFeed object, with encodingFormat providing media type information, e.g. "application/rss+xml" or "application/atom+xml".
Represents the collection of all sports organizations, including sports teams, governing bodies, and sports associations.
A statement about something, for example a fun or interesting fact. If known, the main entity this statement is about can be indicated using mainEntity. For more formal claims (e.g. in Fact Checking), consider using Claim instead. Use the text property to capture the text of the statement.
A StatisticalPopulation is a set of instances of a certain given type that satisfy some set of constraints. The property populationType is used to specify the type. Any property that can be used on instances of that type can appear on the statistical population. For example, a StatisticalPopulation representing all Persons with a homeLocation of East Podunk California would be described by applying the appropriate homeLocation and populationType properties to a StatisticalPopulation item that stands for that set of people. The properties numConstraints and constraintProperty are used to specify which of the populations properties are used to specify the population. Note that the sense of "population" used here is the general sense of a statistical population, and does not imply that the population consists of people. For example, a populationType of Event or NewsArticle could be used. See also Observation, where a populationType such as Person or Event can be indicated directly. In most cases it may be better to use StatisticalVariable instead of StatisticalPopulation.
StatisticalVariable represents any type of statistical metric that can be measured at a place and time. The usage pattern for StatisticalVariable is typically expressed using Observation with an explicit populationType, which is a type, typically drawn from Schema.org. Each StatisticalVariable is marked as a ConstraintNode, meaning that some properties (those listed using constraintProperty) serve in this setting solely to define the statistical variable rather than literally describe a specific person, place or thing. For example, a StatisticalVariable Median_Height_Person_Female representing the median height of women, could be written as follows: the population type is Person; the measuredProperty height; the statType median; the gender Female. It is important to note that there are many kinds of scientific quantitative observation which are not fully, perfectly or unambiguously described following this pattern, or with solely Schema.org terminology. The approach taken here is designed to allow partial, incremental or minimal description of StatisticalVariables, and the use of detailed sets of entity and property IDs from external repositories. The measurementMethod, unitCode and unitText properties can also be used to clarify the specific nature and notation of an observed measurement.
The act of forming a personal connection with someone/something (object) unidirectionally/asymmetrically to get updates pushed to.\n\nRelated actions:\n\n* FollowAction: Unlike FollowAction, SubscribeAction implies that the subscriber acts as a passive agent being constantly/actively pushed for updates.\n* RegisterAction: Unlike RegisterAction, SubscribeAction implies that the agent is interested in continuing receiving updates from the object.\n* JoinAction: Unlike JoinAction, SubscribeAction implies that the agent is interested in continuing receiving updates from the object.
A suite in a hotel or other public accommodation, denotes a class of luxury accommodations, the key feature of which is multiple rooms (source: Wikipedia, the free encyclopedia, see http://en.wikipedia.org/wiki/Suite_(hotel)). See also the dedicated document on the use of schema.org for marking up hotels and other forms of accommodations.
Anatomical features that can be observed by sight (without dissection), including the form and proportions of the human body as well as surface landmarks that correspond to deeper subcutaneous structures. Superficial anatomy plays an important role in sports medicine, phlebotomy, and other medical specialties as underlying anatomical structures can be identified through surface palpation. For example, during back surgery, superficial anatomy can be used to palpate and count vertebrae to find the site of incision. Or in phlebotomy, superficial anatomy can be used to locate an underlying vein; for example, the median cubital vein can be located by palpating the borders of the cubital fossa (such as the epicondyles of the humerus) and then looking for the superficial signs of the vein, such as size, prominence, ability to refill after depression, and feel of surrounding tissue support. As another example, in a subluxation (dislocation) of the glenohumeral joint, the bony structure becomes pronounced with the deltoid muscle failing to cover the glenohumeral joint allowing the edges of the scapula to be superficially visible. Here, the superficial anatomy is the visible edges of the scapula, implying the underlying dislocation of the joint (the related anatomical structure).
A medical procedure involving an incision with instruments; performed for diagnose, or therapeutic purposes.
The act of momentarily pausing a device or application (e.g. pause music playback or pause a timer).
A syllabus that describes the material covered in a course, often with several such sections per Course so that a distinct timeRequired can be provided for that section of the Course.
A short TV program or a segment/part of a TV program.
A TV episode which can be part of a series or season.
Season dedicated to TV broadcast and associated online delivery.
CreativeWorkSeries dedicated to TV broadcast and associated online delivery.
The act of gaining ownership of an object from an origin. Reciprocal of GiveAction.\n\nRelated actions:\n\n* GiveAction: The reciprocal of TakeAction.\n* ReceiveAction: Unlike ReceiveAction, TakeAction implies that ownership has been transferred.
A service for a vehicle for hire with a driver for local travel. Fares are usually calculated based on distance traveled.
A reservation for a taxi.\n\nNote: This type is for information about actual reservations, e.g. in confirmation emails or HTML pages with individual confirmations of reservations. For offers of tickets, use Offer.
A set of organisms asserted to represent a natural cohesive biological unit.
A unique instance of a television BroadcastService on a CableOrSatelliteService lineup.
A text file. The text can be unformatted or contain markup, html, etc.
A theater group or company, for example, the Royal Shakespeare Company or Druid Theatre.
A thesis or dissertation document submitted in support of candidature for an academic degree or professional qualification.
Used to describe a ticket to an event, a flight, a bus ride, etc.
The act of reaching a draw in a competitive activity.
An enumeration of possible benefits as part of a loyalty (members) program.
A point in time recurring on multiple days in the form hh:mm:ss[Z|(+|-)hh:mm] (see [XML schema for details](http://www.w3.org/TR/xmlschema-2/#time)).
The act of giving money voluntarily to a beneficiary in recognition of services rendered.
A tourist attraction. In principle any Thing can be a TouristAttraction, from a Mountain and LandmarksOrHistoricalBuildings to a LocalBusiness. This Type can be used on its own to describe a general TouristAttraction, or be used as an additionalType to add tourist attraction properties to any other type. (See examples below)
A tourist destination. In principle any Place can be a TouristDestination from a City, Region or Country to an AmusementPark or Hotel. This Type can be used on its own to describe a general TouristDestination, or be used as an additionalType to add tourist relevant properties to any other Place. A TouristDestination is defined as a Place that contains, or is colocated with, one or more TouristAttractions, often linked by a similar theme or interest to a particular touristType. The [UNWTO](http://www2.unwto.org/) defines Destination (main destination of a tourism trip) as the place visited that is central to the decision to take the trip. (See examples below.)
A tourist trip. A created itinerary of visits to one or more places of interest (TouristAttraction/TouristDestination) often linked by a similar theme, geographic area, or interest to a particular touristType. The [UNWTO](http://www2.unwto.org/) defines tourism trip as the Trip taken by visitors. (See examples below.)
An agent tracks an object for updates.\n\nRelated actions:\n\n* FollowAction: Unlike FollowAction, TrackAction refers to the interest on the location of innanimates objects.\n* SubscribeAction: Unlike SubscribeAction, TrackAction refers to the interest on the location of innanimate objects.
A reservation for train travel.\n\nNote: This type is for information about actual reservations, e.g. in confirmation emails or HTML pages with individual confirmations of reservations. For offers of tickets, use Offer.
The act of traveling from a fromLocation to a destination by a specified mode of transport, optionally with participants.
An indication for treating an underlying condition, symptom, etc.
A structured value indicating the quantity, unit of measurement, and business function of goods included in a bundle offer.
UKNonprofitType: Non-profit organization type originating from the United Kingdom.
USNonprofitType: Non-profit organization type originating from the United States.
The act of un-registering from a service.\n\nRelated actions:\n\n* RegisterAction: antonym of UnRegisterAction.\n* LeaveAction: Unlike LeaveAction, UnRegisterAction implies that you are unregistering from a service you were previously registered, rather than leaving a team/group of people.
The price asked for a given offer by the respective organization or person.
The act of applying an object to its intended purpose.
UserInteraction and its subtypes is an old way of talking about users interacting with pages. It is generally better to use Action-based vocabulary, alongside types such as Comment.
A review created by an end-user (e.g. consumer, purchaser, attendee etc.), in contrast with CriticReview.
A kind of lodging business that focuses on renting single properties for limited time.
A type of blood vessel that specifically carries blood to the heart.
A video game is an electronic game that involves human interaction with a user interface to generate visual feedback on a video device.
A specific and exact (byte-for-byte) version of a VideoObject. Two byte-for-byte identical files, for the purposes of this type, considered identical. If they have different embedded metadata the files will differ. Different external facts about the files, e.g. creator or dateCreated that aren't represented in their actual content, do not affect this notion of identity.
The act of consuming static visual content.
An online or virtual location for attending events. For example, one may attend an online seminar or educational event. While a virtual location may be used as the location of an event, virtual locations should not be confused with physical locations in the real world.
Vital signs are measures of various physiological functions in order to assess the most basic body functions.
The act of expressing a preference from a fixed/finite/structured set of choices/options.
The act of expressing a desire about the object. An agent wants an object.
A structured value representing the duration and scope of services that will be provided to a customer free of charge in case of a defect or malfunction of a product.
A range of services that will be provided to a customer free of charge in case of a defect or malfunction of a product.\n\nCommonly used values:\n\n* http://purl.org/goodrelations/v1#Labor-BringIn\n* http://purl.org/goodrelations/v1#PartsAndLabor-BringIn\n* http://purl.org/goodrelations/v1#PartsAndLabor-PickUp
The act of consuming dynamic/moving visual content.
The act of dressing oneself in clothing.
Enumerates common types of measurement for wearables products.
Enumerates common size groups (also known as "size types") for wearable products.
Enumerates common size systems specific for wearable products.
An application programming interface accessible over Web/Internet technologies.
A WebSite is a set of related web pages and other items typically served from a single web domain and accessible via URLs.
The act of achieving victory in a competitive activity.
A program with both an educational and employment component. Typically based at a workplace and structured around work-based learning, with the aim of instilling competencies related to an occupation. WorkBasedProgram is used to distinguish programs such as apprenticeships from school, college or other classroom based educational programs.
A Workers Union (also known as a Labor Union, Labour Union, or Trade Union) is an organization that promotes the interests of its worker members by collectively bargaining with management, organizing, and political lobbying.
The act of authoring written creative content.
Text representing an XPath (typically but not necessarily version 1.0).
Represents the activation fee part of the total price for an offered product, for example a cellphone contract.
An in-progress action (e.g., while watching the movie, or driving to a location).
Active, but not recruiting new participants.
Physical activity of relatively low intensity that depends primarily on the aerobic energy-generating process; during activity, the aerobic metabolism uses oxygen to adequately meet energy demands during exercise.
Item contains alcohol or promotes alcohol consumption.
Content coded as 'algorithmic media' using the IPTC digital source type vocabulary.
Content coded as 'algorithmically enhanced' using the IPTC digital source type vocabulary.
All-wheel Drive is a transmission layout where the engine drives all four wheels.
Content about the allergy-related aspects of a health topic.
Physical activity that is of high-intensity which utilizes the anaerobic metabolism of the body.
Represents the broad notion of Android-based operating systems.
A specific branch of medical science that pertains to study of anesthetics and their application.
Appearance assessment with clinical examination.
Book format: Audiobook. This is an enumerated value for use with the bookFormat property. There is also a type 'Audiobook' in the bib extension which includes Audiobook specific properties.
Indicates that the publisher gives some special status to the publication of the document. ("The Queens Printer" version of a UK Act of Parliament, or the PDF version of a Directive published by the EU Office of Publications.) Something "Authoritative" is considered to be also OfficialLegalValue.
A system of medicine that originated in India over thousands of years and that focuses on integrating and balancing the body, mind, and spirit.
Indicates that the item is available on back order.
Pathogenic bacteria that cause bacterial infection.
Physical activity that is engaged to help maintain posture and balance.
BasicIncome: this is a benefit for basic income.
Content about the benefits and advantages of usage or utilization of topic.
Arm length (measured between arms/shoulder line intersection and the prominent wrist bone). Used, for example, to fit shirts.
Maximum girth of bust. Used, for example, to fit women's suits.
Maximum girth of chest. Used, for example, to fit men's suits.
Foot length (measured between end of the most prominent toe and the most prominent part of the heel). Used, for example, to measure socks.
Maximum hand girth (measured over the knuckles of the open right hand excluding thumb, fingers together). Used, for example, to fit gloves.
Maximum girth of head above the ears. Used, for example, to fit hats.
Body height (measured between crown of head and soles of feet). Used, for example, to fit jackets.
Girth of hips (measured around the buttocks). Used, for example, to fit skirts.
Inside leg (measured between crotch and soles of feet). Used, for example, to fit pants.
Girth of neck. Used, for example, to fit shirts.
Girth of body just below the bust. Used, for example, to fit women's swimwear.
Girth of natural waistline (between hip bones and lower ribs). Used, for example, to fit pants.
Body weight. Used, for example, to measure pantyhose.
BusinessSupport: this is a benefit for supporting businesses.
Payment in advance by bank transfer, equivalent to http://purl.org/goodrelations/v1#ByBankTransferInAdvance.
Payment by invoice, typically after the goods were delivered, equivalent to http://purl.org/goodrelations/v1#ByInvoice.
Cash on Delivery (COD) payment, equivalent to http://purl.org/goodrelations/v1#COD.
A specific branch of medical science that pertains to diagnosis and treatment of disorders of heart and vasculature.
Cardiovascular system assessment with clinical examination.
A case series (also known as a clinical series) is a medical research study that tracks patients with a known exposure given similar treatment or examines their medical records for exposure and outcome. A case series can be retrospective or prospective and usually involves a smaller number of patients than the more powerful case-control studies or randomized controlled trials. Case series may be consecutive or non-consecutive, depending on whether all cases presenting to the reporting authors over a period of time were included, or only a selection.
Payment using cash, on premises, equivalent to http://purl.org/goodrelations/v1#Cash.
Information about the causes and main actions that gave rise to the topic.
Specifies that a certification is active.
Specifies that a certification is inactive (no longer in effect).
CharitableIncorporatedOrganization: Non-profit type referring to a Charitable Incorporated Organization (UK).
Payment in advance by sending a check, equivalent to http://purl.org/goodrelations/v1#CheckInAdvance.
A system of medicine focused on the relationship between the body's structure, mainly the spine, and its functioning.
Represents the cleaning fee part of the total price for an offered product, for example a vacation rental.
Medical clinicians, including practicing physicians and other medical professionals involved in clinical practice.
Play mode: CoOp. Co-operative games, where you play on the same team with friends.
Also known as a panel study. A cohort study is a form of longitudinal study used in medicine and social science. It is one type of study design and should be compared with a cross-sectional study. A cohort is a group of people who share a common characteristic or experience within a defined period (e.g., are born, leave school, lose their job, are exposed to a drug or a vaccine, etc.). The comparison group may be the general population from which the cohort is drawn, or it may be another cohort of persons thought to have had little or no exposure to the substance under investigation, but otherwise similar. Alternatively, subgroups within the cohort may be compared with each other.
Permission to add comments to the document.
A field of public health focusing on improving health characteristics of a defined population in relation with their geographical or environment areas.
Content coded as 'composite capture' using the IPTC digital source type vocabulary.
Content coded as 'composite synthetic' using the IPTC digital source type vocabulary.
Content coded as 'composite with trained algorithmic media' using the IPTC digital source type vocabulary.
Composite With Trained Algorithmic Media Digital Source
Content about contagion mechanisms and contagiousness information over the topic.
Studies carried out on pre-existing data (usually from 'snapshot' surveys), such as that collected by the Census Bureau. Sometimes called Prevalence Studies.
The item is dangerous and requires careful handling and/or special training of the user. See also the [UN Model Classification](https://unece.org/DAM/trans/danger/publi/unrec/rev17/English/02EREv17_Part2.pdf) defining the 9 classes of dangerous goods such as explosives, gases, flammables, and more.
Content coded as 'data driven media' using the IPTC digital source type vocabulary.
Content coded 'missing context' in a MediaReview, considered in the context of how it was published or shared. For a VideoObject to be 'missing context': Presenting unaltered video in an inaccurate manner that misrepresents the footage. For example, using incorrect dates or locations, altering the transcript or sharing brief clips from a longer video to mislead viewers. (A video rated 'original' can also be missing context.) For an ImageObject to be 'missing context': Presenting unaltered images in an inaccurate manner to misrepresent the image and mislead the viewer. For example, a common tactic is using an unaltered image but saying it came from a different time or place. (An image rated 'original' can also be missing context.) For an ImageObject with embedded text to be 'missing context': An unaltered image presented in an inaccurate manner to misrepresent the image and mislead the viewer. For example, a common tactic is using an unaltered image but saying it came from a different time or place. (An 'original' image with inaccurate text would generally fall in this category.) For an AudioObject to be 'missing context': Unaltered audio presented in an inaccurate manner that misrepresents it. For example, using incorrect dates or locations, or sharing brief clips from a longer recording to mislead viewers. (Audio rated “originalâ€ can also be missing context.)
Indicates a document for which the text is conclusively what the law says and is legally binding. (E.g. the digitally signed version of an Official Journal.) Something "Definitive" is considered to be also AuthoritativeLegalValue.
Indicates demo game availability, i.e. a somehow limited demonstration of the full game.
A branch of medicine that is involved in the dental care.
Something relating to or practicing dermatology.
A specific branch of medical science that pertains to diagnosis and treatment of disorders of skin.
Represents the broad notion of 'desktop' browsers as a Web Platform.
A diet appropriate for people with diabetes.
A medical device used for diagnostic purposes.
Dietetics and nutrition as a medical specialty.
Content coded as 'digital art' using the IPTC digital source type vocabulary.
Content coded as 'digital capture' using the IPTC digital source type vocabulary.
Payment in advance by direct debit from the bank, equivalent to http://purl.org/goodrelations/v1#DirectDebit.
DisabilitySupport: this is a benefit for disability support.
Indicates that the item has been discontinued.
Represents the distance fee (e.g., price per km or mile) part of the total price for an offered product, for example a car rental.
A trial design in which neither the researcher nor the patient knows the details of the treatment the patient was randomly assigned to.
Represents the downpayment (up-front payment) price component of the total price for an offered product that has additional installment payments.
Indicates the usage of the vehicle for driving school.
Represents EU Energy Efficiency Class A as defined in EU energy labeling regulations.
Represents EU Energy Efficiency Class A+ as defined in EU energy labeling regulations.
Represents EU Energy Efficiency Class A++ as defined in EU energy labeling regulations.
Represents EU Energy Efficiency Class A+++ as defined in EU energy labeling regulations.
Represents EU Energy Efficiency Class B as defined in EU energy labeling regulations.
Represents EU Energy Efficiency Class C as defined in EU energy labeling regulations.
Represents EU Energy Efficiency Class D as defined in EU energy labeling regulations.
Represents EU Energy Efficiency Class E as defined in EU energy labeling regulations.
Represents EU Energy Efficiency Class F as defined in EU energy labeling regulations.
Represents EU Energy Efficiency Class G as defined in EU energy labeling regulations.
Ear function assessment with clinical examination.
Content coded 'edited or cropped content' in a MediaReview, considered in the context of how it was published or shared. For a VideoObject to be 'edited or cropped content': The video has been edited or rearranged. This category applies to time edits, including editing multiple videos together to alter the story being told or editing out large portions from a video. For an ImageObject to be 'edited or cropped content': Presenting a part of an image from a larger whole to mislead the viewer. For an ImageObject with embedded text to be 'edited or cropped content': Presenting a part of an image from a larger whole to mislead the viewer. For an AudioObject to be 'edited or cropped content': The audio has been edited or rearranged. This category applies to time edits, including editing multiple audio clips together to alter the story being told or editing out large portions from the recording.
Content about the effectiveness-related aspects of a health topic.
A specific branch of medical science that deals with the evaluation and initial treatment of medical conditions caused by trauma or sudden illness.
A specific branch of medical science that pertains to diagnosis and treatment of disorders of endocrine glands and their secretions.
Enrolling participants by invitation only.
The event has been cancelled. If the event has multiple startDate values, all are assumed to be cancelled. Either startDate or previousStartDate may be used to specify the event's cancelled date(s).
Indicates that the event was changed to allow online participation. See eventAttendanceMode for specifics of whether it is now fully or partially online.
The event has been postponed and no new date has been set. The event's previousStartDate should be set.
The event has been rescheduled. The event's previousStartDate should be set to the old date and the startDate should be set to the event's new date. (If the event has been rescheduled multiple times, the previousStartDate property may be repeated.)
The event is taking place or has taken place on the startDate as scheduled. Use of this value is optional, as it is assumed by default.
Data derived from multiple randomized clinical trials or meta-analyses.
Data derived from a single randomized trial, or nonrandomized studies.
Only consensus opinion of experts, case studies, or standard-of-care.
An example MeasurementMethodEnum (to remove when real enums are added).
Specifies that a refund can be done as an exchange for the same product.
Eye or ophthalmological function assessment with clinical examination.
A designation by the US FDA signifying that adequate and well-controlled studies have failed to demonstrate a risk to the fetus in the first trimester of pregnancy (and there is no evidence of risk in later trimesters).
A designation by the US FDA signifying that animal reproduction studies have failed to demonstrate a risk to the fetus and there are no adequate and well-controlled studies in pregnant women.
A designation by the US FDA signifying that animal reproduction studies have shown an adverse effect on the fetus and there are no adequate and well-controlled studies in humans, but potential benefits may warrant use of the drug in pregnant women despite potential risks.
A designation by the US FDA signifying that there is positive evidence of human fetal risk based on adverse reaction data from investigational or marketing experience or studies in humans, but potential benefits may warrant use of the drug in pregnant women despite potential risks.
A designation by the US FDA signifying that studies in animals or humans have demonstrated fetal abnormalities and/or there is positive evidence of human fetal risk based on adverse reaction data from investigational or marketing experience, and the risks involved in use of the drug in pregnant women clearly outweigh potential benefits.
A designation that the drug in question has not been assigned a pregnancy category designation by the US FDA.
An action that failed to complete. The action's error property and the HTTP return code contain more information about the failure.
Physical activity that is engaged in to improve joint and muscle flexibility.
Four-wheel drive is a transmission layout where the engine primarily drives two wheels with a part-time four-wheel drive capability.
Specifies that product returns are free of charge for the customer.
The day of the week between Thursday and Saturday.
URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Wikidata entry, or official website.
Front-wheel drive is a transmission layout where the engine drives the front wheels.
Specifies that a refund can be done in the full amount the customer paid for the product.
A specific branch of medical science that pertains to diagnosis and treatment of disorders of digestive system.
Represents the generic notion of the Web Platform. More specific codes include MobileWebPlatform and DesktopWebPlatform, as an incomplete list.
A specific branch of medical science that pertains to hereditary transmission and the variation of inherited characteristics and disorders.
Genitourinary system function assessment with clinical examination.
A specific branch of medical science that is concerned with the diagnosis and treatment of diseases, debilities and provision of care to the aged.
Content that discusses practical and policy aspects for getting access to specific kinds of healthcare (e.g. distribution mechanisms for vaccines).
Book format: GraphicNovel. May represent a bound collection of ComicIssue instances.
The airline boards by groups based on check-in time, priority, etc.
A specific branch of medical science that pertains to the health care of women, particularly in the diagnosis and treatment of disorders affecting the female reproductive system.
A diet conforming to Islamic dietary practices.
Head assessment with clinical examination.
HealthCare: this is a benefit for health care.
Item is a pharmaceutical (e.g., a prescription or OTC drug) or a restricted medical device.
Uses devices to support users with hearing impairments.
A specific branch of medical science that pertains to diagnosis and treatment of disorders of blood and blood producing organs.
A diet conforming to Hindu dietary practices, in particular, beef-free.
A system of medicine based on the principle that a disease can be cured by a substance that produces similar symptoms in healthy people.
Content that discusses and explains how a particular health-related topic works, e.g. in terms of mechanisms and underlying science.
Information about how or where to find a topic. Also may contain location data that can be used for where to look for help if the topic is observed.
Represents the broad notion of iOS-based operating systems.
Indicates that a legislation is in force.
Indicates that the item is available only at physical locations.
Payment in advance in some form of shop or kiosk for goods purchased online.
Something in medical science that pertains to infectious diseases, i.e. caused by bacterial, viral, fungal or parasitic infections.
Content discussing ingredients-related aspects of a health topic.
Represents the installment pricing component of the total price for an offered product.
Represents the invoice price of an offered product.
An ItemList ordered with lower values listed first.
An ItemList ordered with higher values listed first.
An ItemList ordered with no explicit order.
Specifies that the consumer can keep the product, even when receiving a refund or store credit.
A diet conforming to Jewish dietary practices.
A medical science pertaining to chemical, hematological, immunologic, microscopic, or bacteriological diagnostic analyses or research.
The steering position is on the left side of the vehicle (viewed from the main direction of driving).
Any physical activity engaged in for recreational purposes. Examples may include ballroom dancing, roller skating, canoeing, fishing, etc.
Indicates that the item has limited availability.
LimitedByGuaranteeCharity: Non-profit type referring to a charitable company that is limited by guarantee (UK).
Represents the list price of an offered product.
Information about coping or life related to the topic.
A DeliveryMethod in which an item is made available via locker.
Unlike cross-sectional studies, longitudinal studies track the same people, and therefore the differences observed in those people are less likely to be the result of cultural differences across generations. Longitudinal studies are also used in medicine to uncover predictors of certain diseases.
A diet focused on reduced calorie intake.
A diet focused on reduced fat and cholesterol intake.
A diet appropriate for people with lactose intolerance.
A diet focused on reduced sodium intake.
Lung and respiratory system clinical examination.
Represents the manufacturer suggested retail price ("MSRP") of an offered product.
Indicates that the item is made to order (custom made).
Related topics may be treated by a Topic.
Specifies that there is a finite window for product returns.
Specifies that product returns are not permitted.
Specifies that there is an unlimited window for product returns.
Specifies that a product return policy is not provided.
A nurse-like health profession that deals with pregnancy, childbirth, and the postpartum period (including care of the newborn), besides sexual and reproductive health of women throughout their lives.
Represents the minimum advertised price ("MAP") (as dictated by the manufacturer) of an offered product.
Content coded as 'minor human edits' using the IPTC digital source type vocabulary.
Content about common misconceptions and myths that are related to a topic.
MixedEventAttendanceMode - an event that is conducted as a combination of both offline and online modes.
Represents the broad notion of 'mobile' browsers as a Web Platform.
The day of the week between Sunday and Tuesday.
A trial that takes place at multiple centers.
Play mode: MultiPlayer. Requiring or allowing multiple human players to play simultaneously.
Multicellular parasite that causes an infection.
A specific branch of medical science that pertains to diagnosis and treatment of disorders of muscles, ligaments and skeletal system.
Musculoskeletal system clinical examination.
Item is a narcotic as defined by the [1961 UN convention](https://www.incb.org/incb/en/narcotic-drugs/Yellowlist/yellow-list.html), for example marijuana or heroin.
Neck assessment with clinical examination.
Content coded as 'negative film' using the IPTC digital source type vocabulary.
Neurological system clinical examination.
A specific branch of medical science that studies the nerves and nervous system and its respective disease states.
A type of medical procedure that involves noninvasive techniques.
Nonprofit501a: Non-profit type referring to Farmers’ Cooperative Associations.
Nonprofit501c1: Non-profit type referring to Corporations Organized Under Act of Congress, including Federal Credit Unions and National Farm Loan Associations.
Nonprofit501c10: Non-profit type referring to Domestic Fraternal Societies and Associations.
Nonprofit501c11: Non-profit type referring to Teachers' Retirement Fund Associations.
Nonprofit501c12: Non-profit type referring to Benevolent Life Insurance Associations, Mutual Ditch or Irrigation Companies, Mutual or Cooperative Telephone Companies.
Nonprofit501c13: Non-profit type referring to Cemetery Companies.
Nonprofit501c14: Non-profit type referring to State-Chartered Credit Unions, Mutual Reserve Funds.
Nonprofit501c15: Non-profit type referring to Mutual Insurance Companies or Associations.
Nonprofit501c16: Non-profit type referring to Cooperative Organizations to Finance Crop Operations.
Nonprofit501c17: Non-profit type referring to Supplemental Unemployment Benefit Trusts.
Nonprofit501c18: Non-profit type referring to Employee Funded Pension Trust (created before 25 June 1959).
Nonprofit501c19: Non-profit type referring to Post or Organization of Past or Present Members of the Armed Forces.
Nonprofit501c2: Non-profit type referring to Title-holding Corporations for Exempt Organizations.
Nonprofit501c20: Non-profit type referring to Group Legal Services Plan Organizations.
Nonprofit501c21: Non-profit type referring to Black Lung Benefit Trusts.
Nonprofit501c22: Non-profit type referring to Withdrawal Liability Payment Funds.
Nonprofit501c23: Non-profit type referring to Veterans Organizations.
Nonprofit501c24: Non-profit type referring to Section 4049 ERISA Trusts.
Nonprofit501c25: Non-profit type referring to Real Property Title-Holding Corporations or Trusts with Multiple Parents.
Nonprofit501c26: Non-profit type referring to State-Sponsored Organizations Providing Health Coverage for High-Risk Individuals.
Nonprofit501c27: Non-profit type referring to State-Sponsored Workers' Compensation Reinsurance Organizations.
Nonprofit501c28: Non-profit type referring to National Railroad Retirement Investment Trusts.
Nonprofit501c3: Non-profit type referring to Religious, Educational, Charitable, Scientific, Literary, Testing for Public Safety, Fostering National or International Amateur Sports Competition, or Prevention of Cruelty to Children or Animals Organizations.
Nonprofit501c4: Non-profit type referring to Civic Leagues, Social Welfare Organizations, and Local Associations of Employees.
Nonprofit501c5: Non-profit type referring to Labor, Agricultural and Horticultural Organizations.
Nonprofit501c6: Non-profit type referring to Business Leagues, Chambers of Commerce, Real Estate Boards.
Nonprofit501c7: Non-profit type referring to Social and Recreational Clubs.
Nonprofit501c8: Non-profit type referring to Fraternal Beneficiary Societies and Associations.
Nonprofit501c9: Non-profit type referring to Voluntary Employee Beneficiary Associations.
Nonprofit501d: Non-profit type referring to Religious and Apostolic Associations.
Nonprofit501e: Non-profit type referring to Cooperative Hospital Service Organizations.
Nonprofit501f: Non-profit type referring to Cooperative Service Organizations.
Nonprofit501k: Non-profit type referring to Child Care Organizations.
Nonprofit501n: Non-profit type referring to Charitable Risk Pools.
Nonprofit501q: Non-profit type referring to Credit Counseling Organizations.
Nonprofit527: Non-profit type referring to political organizations.
NonprofitANBI: Non-profit type referring to a Public Benefit Organization (NL).
NonprofitSBBI: Non-profit type referring to a Social Interest Promoting Institution (NL).
Nose function assessment with clinical examination.
Indicates that a legislation is currently not in force.
A health profession of a person formally educated and trained in the care of the sick or infirm person.
The character of a medical substance, typically a medicine, of being available over the counter or not.
A specific branch of medical science that specializes in the care of women during the prenatal and postnatal care and with the delivery of the child.
Any physical activity engaged in for job-related purposes. Examples may include waiting tables, maid service, carrying a mailbag, picking fruits or vegetables, construction work, etc.
All the documents published by an official publisher should have at least the legal value level "OfficialLegalValue". This indicates that the document was published by an organisation with the public task of making it available (e.g. a consolidated version of an EU directive published by the EU Office of Publications).
OfflineEventAttendanceMode - an event that is primarily conducted offline.
Game server status: OfflinePermanently. Server is offline and not available.
Game server status: OfflineTemporarily. Server is offline now but it can be online soon.
A DeliveryMethod in which an item is collected on site, e.g. in a store or at a box office.
A specific branch of medical science that deals with benign and malignant tumors, including the study of their development, diagnosis, treatment and prevention.
OneTimePayments: this is a benefit for one-time payments for individuals.
Game server status: Online. Server is available.
OnlineEventAttendanceMode - an event that is primarily conducted online.
Game server status: OnlineFull. Server is online but unavailable. The maximum number of players has reached.
Indicates that the item is available only online.
A trial design in which the researcher knows the full details of the treatment, and so does the patient.
The science or practice of testing visual acuity and prescribing corrective lenses.
OrderStatus representing cancellation of an order.
OrderStatus representing successful delivery of an order.
OrderStatus representing that an order is in transit.
OrderStatus representing that payment is due on an order.
OrderStatus representing availability of an order for pickup.
OrderStatus representing that there is a problem with the order.
OrderStatus representing that an order is being processed.
OrderStatus representing that an order has been returned.
Content coded 'as original media content' in a MediaReview, considered in the context of how it was published or shared. For a VideoObject to be 'original': No evidence the footage has been misleadingly altered or manipulated, though it may contain false or misleading claims. For an ImageObject to be 'original': No evidence the image has been misleadingly altered or manipulated, though it may still contain false or misleading claims. For an ImageObject with embedded text to be 'original': No evidence the image has been misleadingly altered or manipulated, though it may still contain false or misleading claims. For an AudioObject to be 'original': No evidence the audio has been misleadingly altered or manipulated, though it may contain false or misleading claims.
Specifies that the customer must pay the original shipping costs when returning a product.
A system of medicine focused on promoting the body's innate ability to heal itself.
A specific branch of medical science that is concerned with the ear, nose and throat and their respective disease states.
Indicates that the item is out of stock.
Overview of the content. Contains a summarized view of the topic with the most relevant information for an introduction.
PaidLeave: this is a benefit for paid leave.
A private parcel service as the delivery mode available for a certain offer.\n\nCommonly used values:\n\n* http://purl.org/goodrelations/v1#DHL\n* http://purl.org/goodrelations/v1#FederalExpress\n* http://purl.org/goodrelations/v1#UPS
ParentalSupport: this is a benefit for parental support.
Indicates that parts of the legislation are in force, and parts are not.
A specific branch of medical science that is concerned with the study of the cause, origin and nature of a disease state, including its consequences as a result of manifestation of the disease. In clinical care, the term is used to designate a branch of medicine using laboratory tests to diagnose and determine the prognostic significance of illness.
Content about the real life experience of patients or people that have lived a similar experience about the topic. May be forums, topics, Q-and-A and related material.
An automatic payment system is in place and will be used.
The payment has been received and processed.
The payee received the payment, but it was declined for some reason.
The payment is due, but still within an acceptable time to be received.
A specific branch of medical science that specializes in the care of infants, children and adolescents.
A type of medical procedure that involves percutaneous techniques, where access to organs or tissue is achieved via needle-puncture of the skin. For example, catheter-based procedures like stent delivery.
The practice or art and science of preparing and dispensing drugs and medicines.
Payment by billing via the phone carrier.
The practice of treatment of disease, injury, or deformity by physical methods such as massage, heat treatment, and exercise rather than by drugs or surgery.
A specific branch of medical science that pertains to therapeutic or cosmetic repair or re-formation of missing, injured or malformed tissues or body parts by manual and instrumental means.
Podiatry is the care of the human foot, especially the diagnosis and treatment of foot disorders.
Content coded as 'positive film' using the IPTC digital source type vocabulary.
A description of an action that is supported.
Indicates that the item is available for pre-order.
Indicates that the item is available for ordering and delivery before general availability.
Content discussing pregnancy-related aspects of a health topic.
Information about actions or measures that can be taken to avoid getting the topic or reaching a critical situation related to the topic.
The medical care by a physician, or other health-care professional, who is the patient's first contact with the health-care system and who may recommend a specialist if necessary.
Content coded as 'print' using the IPTC digital source type vocabulary.
A prion is an infectious agent composed of protein in a misfolded form.
Typical progression and happenings of life course of the topic.
Single-celled organism that causes an infection.
A specific branch of medical science that is concerned with the study, treatment, and prevention of mental illness, using both medical and psychological therapies.
Branch of medicine that pertains to the health services to improve and protect community health, especially epidemiology, sanitation, immunization, and preventive medicine.
This stands for any day that is a public holiday; it is a placeholder for all official public holidays in some particular location. While not technically a "day of the week", it can be used with OpeningHoursSpecification. In the context of an opening hours specification it can be used to indicate opening hours on public holidays, overriding general opening hours for the day of the week on which a public holiday occurs.
A specific branch of medical science that pertains to the study of the respiratory system and its respective disease states.
Radiography is an imaging technique that uses electromagnetic radiation other than visible light, especially X-rays, to view the internal structure of a non-uniformly composed and opaque object such as the human body.
Permission to read or view the document.
Real-wheel drive is a transmission layout where the engine drives the rear wheels.
A general code for cases where relevance to children is reduced, e.g. adult education, mortgages, retirement-related products, etc.
Reduced Relevance For Children Consideration
Represents the regular price (typically the previous advertised price before a sale) of an offered product. Often displayed as a strike-through price.
The drug's cost represents the maximum reimbursement paid by an insurer for the drug.
Other prominent or relevant topics tied to the main topic.
A specific branch of medical science that pertains to the study of the kidneys and its respective disease states.
Indicates the usage of the vehicle as a rental car.
The status for a previously confirmed reservation that is now cancelled.
The status of a reservation on hold pending an update like credit card number or flight changes.
The status of a reservation when a request has been sent, but not confirmed.
Indicates that the item is reserved and therefore not available.
The therapy that is concerned with the maintenance or improvement of respiratory function (as in patients with pulmonary disease).
Specifies that the customer must pay a restocking fee when returning a product.
The drug's cost represents the retail cost of the drug.
Specifies that product returns must be made at a kiosk.
Specifies that product returns must be done by mail.
Specifies that product returns must be paid for, and are the responsibility of, the customer.
Specifies that product returns must be made in a store.
Indicated that creating a return label is the responsibility of the customer.
Indicated that a return label must be downloaded and printed by the customer.
Specifies that a return label will be provided by the seller in the shipping box.
Specifies that the customer must pay the return shipping costs when returning a product.
A specific branch of medical science that deals with the study and treatment of rheumatic, autoimmune or joint diseases.
The steering position is on the right side of the vehicle (viewed from the main direction of driving).
Information about the risk factors and possible complications that may follow a topic.
Represents the suggested retail price ("SRP") of an offered product.
Content about the safety-related aspects of a health topic.
Represents a sale price (usually active for a limited period) of an offered product.
Content coded 'satire or parody content' in a MediaReview, considered in the context of how it was published or shared. For a VideoObject to be 'satire or parody content': A video that was created as political or humorous commentary and is presented in that context. (Reshares of satire/parody content that do not include relevant context are more likely to fall under the “missing contextâ€ rating.) For an ImageObject to be 'satire or parody content': An image that was created as political or humorous commentary and is presented in that context. (Reshares of satire/parody content that do not include relevant context are more likely to fall under the “missing contextâ€ rating.) For an ImageObject with embedded text to be 'satire or parody content': An image that was created as political or humorous commentary and is presented in that context. (Reshares of satire/parody content that do not include relevant context are more likely to fall under the “missing contextâ€ rating.) For an AudioObject to be 'satire or parody content': Audio that was created as political or humorous commentary and is presented in that context. (Reshares of satire/parody content that do not include relevant context are more likely to fall under the “missing contextâ€ rating.)
The day of the week between Friday and Sunday.
Content about how to screen or further filter a topic.
Information about questions that may be asked, when to see a professional, measures before seeing a doctor or content about the first consultation.
Self care actions or measures that can be taken to sooth, health or avoid a topic. This may be carried at home and can be carried/managed by the person itself.
The item contains sexually oriented content such as nudity, suggestive or explicit material, or related online services, or is intended to enhance sexual activity. Examples: Erotic videos or magazine, sexual enhancement devices, sex toys.
Side effects that can be observed from the usage of the topic.
A trial design in which the researcher knows which treatment the patient was randomly assigned to but the patient does not.
A trial that takes place at a single center.
Play mode: SinglePlayer. Which is played by a lone player.
Skin assessment with clinical examination.
The scientific study and treatment of defects, disorders, and malfunctions of speech and voice, as stuttering, lisping, or lalling, and of language disturbances, as aphasia or delayed language acquisition.
Content coded 'staged content' in a MediaReview, considered in the context of how it was published or shared. For a VideoObject to be 'staged content': A video that has been created using actors or similarly contrived. For an ImageObject to be 'staged content': An image that was created using actors or similarly contrived, such as a screenshot of a fake tweet. For an ImageObject with embedded text to be 'staged content': An image that was created using actors or similarly contrived, such as a screenshot of a fake tweet. For an AudioObject to be 'staged content': Audio that has been created using actors or similarly contrived.
Stages that can be observed from a topic.
Specifies that the customer receives a store credit as refund when returning a product.
Physical activity that is engaged in to improve muscle and bone strength. Also referred to as resistance training.
Represents the subscription pricing component of the total price for an offered product.
The day of the week between Saturday and Monday.
A specific branch of medical science that pertains to treating diseases, injuries and deformities by manual and instrumental means.
Symptoms or related symptoms of a Topic.
Indicates the usage of the car as a taxi.
A medical device used for therapeutic purposes.
Throat assessment with clinical examination.
The day of the week between Wednesday and Friday.
Benefit of the tier is earning of loyalty points.
Benefit of the tier is a members-only price.
Benefit of the tier is members-only returns, for example free unlimited returns.
Benefit of the tier is a members-only shipping price or speed (for example free shipping or 1-day shipping).
Item contains tobacco and/or nicotine, for example cigars, cigarettes, chewing tobacco, e-cigarettes, or hookahs.
The associated telephone number is toll free.
A specific branch of medical science that is concerned with poisons, their nature, effects and detection and involved in the treatment of poisoning.
A system of medicine based on common theoretical concepts that originated in China and evolved over thousands of years, that uses herbs, acupuncture, exercise, massage, dietary therapy, and other methods to treat a wide range of conditions.
Content coded as 'trained algorithmic media' using the IPTC digital source type vocabulary.
Trained Algorithmic Media Digital Source
Content coded 'transformed content' in a MediaReview, considered in the context of how it was published or shared. For a VideoObject to be 'transformed content': or all of the video has been manipulated to transform the footage itself. This category includes using tools like the Adobe Suite to change the speed of the video, add or remove visual elements or dub audio. Deepfakes are also a subset of transformation. For an ImageObject to be 'transformed content': Adding or deleting visual elements to give the image a different meaning with the intention to mislead. For an ImageObject with embedded text to be 'transformed content': Adding or deleting visual elements to give the image a different meaning with the intention to mislead. For an AudioObject to be 'transformed content': Part or all of the audio has been manipulated to alter the words or sounds, or the audio has been synthetically generated, such as to create a sound-alike voice.
Treatments or related therapies for a Topic.
A trial design in which neither the researcher, the person administering the therapy nor the patient knows the details of the treatment the patient was randomly assigned to.
The day of the week between Monday and Wednesday.
Categorization and other types related to a topic.
UKTrust: Non-profit type referring to a UK trust.
The item is suitable only for adults, without indicating why. Due to widespread use of "adult" as a euphemism for "sexual", many such items are likely suited also for the SexualContentConsideration code.
UnemploymentSupport: this is a benefit for unemployment support.
UnincorporatedAssociationCharity: Non-profit type referring to a charitable company that is not incorporated (UK).
Indicates that a document has no particular or special standing (e.g. a republication of a law by a private publisher).
A specific branch of medical science that is concerned with the diagnosis and treatment of diseases pertaining to the urinary tract and the urogenital system.
Content about how, when, frequency and dosage of a topic.
A diet exclusive of all animal products.
A venue map (e.g. for malls, auditoriums, museums, etc.).
Content coded as 'virtual recording' using the IPTC digital source type vocabulary.
Pathogenic virus that causes viral infection.
The item is intended to induce bodily harm, for example guns, mace, combat knives, brass knuckles, nail or other bombs, and spears.
Measurement of the back section, for example of a jacket.
Measurement of the chest/bust section, for example of a suit.
Measurement of the collar, for example of a shirt.
Measurement of the cup, for example of a bra.
Measurement of the height, for example the heel height of a shoe.
Measurement of the hip section, for example of a skirt.
Measurement of the inseam, for example of pants.
Represents the length, for example of a dress.
Measurement of the outside leg, for example of pants.
Measurement of the sleeve length, for example of a shirt.
Measurement of the waist section, for example of pants.
Measurement of the width, for example of shoes.
Size group "Husky" (or "Stocky") for wearables.
Size group "Misses" (also known as "Missy") for wearables.
EN 13402 (joint European standard for size labelling of clothes).
GS1 (formerly NRF) size system for wearables.
United Kingdom size system for wearables.
United States size system for wearables.
The day of the week between Tuesday and Thursday.
The conventional Western system of medicine, that aims to apply the best available evidence gained from the scientific method to clinical decision making. Also known as conventional or Western medicine.
The drug's cost represents the wholesale acquisition cost of the drug.
Permission to write or edit the document.
The airline boards by zones of the plane.
Indicates whether the book is an abridged edition.
An abstract is a short description that summarizes a CreativeWork.
The time needed to accelerate the vehicle from a given start velocity to a given target velocity.\n\nTypical unit code(s): SEC for seconds\n\n* Note: There are unfortunately no standard unit codes for seconds/0..100 km/h or seconds/0..60 mph. Simply use "SEC" for seconds and indicate the velocities in the name of the QuantitativeValue, or use valueReference with a QuantitativeValue of 0..60 mph or 0..100 km/h to specify the reference speeds.
The answer(s) that has been accepted as best, typically on a Question/Answer site. Sites vary in their selection mechanisms, e.g. drawing on community opinion and/or the view of the Question author.
An answer (possibly one of several, possibly incorrect) to a Question, e.g. on a Question/Answer site.
The offer(s) -- e.g., product, quantity and price combinations -- included in the order.
The payment method(s) that are accepted in general by an organization, or for some specific demand or offer.
Indicates whether a FoodEstablishment accepts reservations. Values can be Boolean, an URL at which reservations can be made or (for backwards compatibility) the strings ```Yes``` or ```No```.
Password, PIN, or access code needed for delivery (e.g. from a locker).
The human sensory perceptual system or cognitive faculty through which a person may process or perceive information. Values should be drawn from the [approved vocabulary](https://www.w3.org/2021/a11y-discov-vocab/latest/#accessMode-vocabulary).
A list of single or combined accessModes that are sufficient to understand all the intellectual content of a resource. Values should be drawn from the [approved vocabulary](https://www.w3.org/2021/a11y-discov-vocab/latest/#accessModeSufficient-vocabulary).
Indicates that the resource is compatible with the referenced accessibility API. Values should be drawn from the [approved vocabulary](https://www.w3.org/2021/a11y-discov-vocab/latest/#accessibilityAPI-vocabulary).
Identifies input methods that are sufficient to fully control the described resource. Values should be drawn from the [approved vocabulary](https://www.w3.org/2021/a11y-discov-vocab/latest/#accessibilityControl-vocabulary).
Content features of the resource, such as accessible media, alternatives and supported enhancements for accessibility. Values should be drawn from the [approved vocabulary](https://www.w3.org/2021/a11y-discov-vocab/latest/#accessibilityFeature-vocabulary).
A characteristic of the described resource that is physiologically dangerous to some users. Related to WCAG 2.0 guideline 2.3. Values should be drawn from the [approved vocabulary](https://www.w3.org/2021/a11y-discov-vocab/latest/#accessibilityHazard-vocabulary).
A human-readable summary of specific accessibility features or deficiencies, consistent with the other accessibility metadata but expressing subtleties such as "short descriptions are present but long descriptions will be needed for non-visual users" or "short descriptions are present and no long descriptions are needed".
Category of an Accommodation, following real estate conventions, e.g. RESO (see [PropertySubType](https://ddwiki.reso.org/display/DDW17/PropertySubType+Field), and [PropertyType](https://ddwiki.reso.org/display/DDW17/PropertyType+Field) fields for suggested values).
A category for the item. Greater signs or slashes can be used to informally indicate a category hierarchy.
The identifier for the account the payment will be applied to.
A minimum amount that has to be paid in every month.
An overdraft is an extension of credit from a lending institution when an account reaches zero. An overdraft allows the individual to continue withdrawing money even if the account has no funds in it. Basically the bank allows people to borrow a set amount of money.
Specifies the Person that is legally accountable for the CreativeWork.
Indicates a page documenting how licenses can be purchased or otherwise acquired, for the current item.
The organization or person from which the product was acquired.
The ACRISS Car Classification Code is a code used by many car rental companies, for classifying vehicles. ACRISS stands for Association of Car Rental Industry Systems and Standards.
A set of requirements that must be fulfilled in order to perform an Action. If more than one value is specified, fulfilling one set of requirements will allow the Action to be performed.
The high level platform(s) where the Action can be performed for the given URL. To specify a specific application or operating system instance, use actionApplication.
Indicates the current disposition of the Action.
For a NewsMediaOrganization or other news-related Organization, a statement about public engagement activities (for news media, the newsroom’s), including involving the public - digitally or otherwise -- in coverage decisions, reporting and activities after publication.
The publishingPrinciples property indicates (typically via URL) a document describing the editorial principles of an Organization (or individual, e.g. a Person writing a blog) that relate to their activities as a publisher, e.g. ethics or diversity policies. When applied to a CreativeWork (e.g. NewsArticle) the principles are those of the party primarily responsible for the creation of the CreativeWork. While such policies are most typically expressed in natural language, sometimes related information (e.g. indicating a funder) can be expressed using schema.org terminology.
An active ingredient, typically chemical compounds and/or biologic substances.
Length of time to engage in the activity.
How often one should engage in the activity.
An actor, e.g. in TV, radio, movie, video games etc. Actors can be associated with individual items or with a series, episode, clip.
An actor, e.g. in TV, radio, movie, video games etc., or in an event. Actors can be associated with individual items or with a series, episode, clip.
An additional offer that can only be obtained in combination with the first base offer (e.g. supplements and extensions that are available for a surcharge).
An additional name for a Person, can be used for a middle name.
If responding yes, the number of guests who will attend in addition to the invitee.
A property-value pair representing an additional characteristic of the entity, e.g. a product feature or another characteristic for which there is no matching property in schema.org.\n\nNote: Publishers should be aware that applications designed to use specific schema.org properties (e.g. https://schema.org/width, https://schema.org/color, https://schema.org/gtin13, ...) will typically expect such data to be provided using those properties, rather than using the generic property/value mechanism.
Any additional component of the exercise prescription that may need to be articulated to the patient. This may include the order of exercises, the number of repetitions of movement, quantitative distance, progressions over time, etc.
The country. For example, USA. You can also provide the two-letter [ISO 3166-1 alpha-2 country code](http://en.wikipedia.org/wiki/ISO_3166-1).
The locality in which the street address is, and which is in the region. For example, Mountain View.
The region in which the locality is, and which is in the country. For example, California or another appropriate first-level [Administrative division](https://en.wikipedia.org/wiki/List_of_administrative_divisions_by_country).
A route by which this drug may be administered, e.g. 'oral'.
The amount of time that is required between accepting the offer and the actual usage of the resource or service.
A possible complication and/or side effect of this therapy. If it is known that an adverse outcome is serious (resulting in death, disability, or permanent damage; requiring hospitalization; or otherwise life-threatening or requiring immediate medical attention), tag it as a seriousAdverseOutcome instead.
A media object representing the circumstances after performing this direction.
The direct performer or driver of the action (animate or inanimate). E.g. *John* wrote a book.
The number of completed interactions for this entity, in a particular role (the 'agent'), in a particular action (indicated in the statistic), and in a particular context (i.e. interactionService).
The overall rating, based on a collection of reviews or ratings, of the item.
The kind of aircraft (e.g., "Boeing 747").
Any precaution, guidance, contraindication, etc. related to consumption of alcohol while taking this drug.
The algorithm or rules to follow to compute the score.
A category of alignment between the learning resource and the framework node. Recommended values include: 'requires', 'textComplexity', 'readingLevel', and 'educationalSubject'.
Another gene which is a variation of this one.
An amenity feature (e.g. a characteristic or service) of the Accommodation. This generic property does not make a statement about whether the feature is included in an offer for the main accommodation or available at extra costs.
The quantity of the goods included in the offer.
Indicates a specific CivicStructure or LocalBusiness associated with the SpecialAnnouncement. For example, a specific testing facility or business with special opening hours. For a larger geographic region like a quarantine of an entire region, use spatialCoverage.
The spatialCoverage of a CreativeWork indicates the place(s) which are the focus of the content. It is a subproperty of contentLocation intended primarily for more technical and detailed materials. For example with a Dataset, it indicates areas that the dataset describes: a dataset of New York weather would have spatialCoverage which was the place: the state of New York.
The annual rate that is charged for borrowing (or made by investing), expressed as a single percentage number that represents the actual yearly cost of funds over the term of a loan. This includes any fees or additional costs associated with the transaction.
The number of answers this question has received.
A step-by-step or full explanation about Answer. Can outline how this Answer was achieved or contain more broad clarification or statement about it.
The muscle whose action counteracts the specified muscle.
Indicates an occurrence of a Claim in some CreativeWork.
Example/instance/realization/derivation of the concept of this creative work. E.g. the paperback edition, first edition, or e-book.
A country where a particular merchant return policy applies to, for example the two-letter ISO 3166-1 alpha-2 country code.
The location in which the status applies.
The location(s) applicants can apply from. This is usually used for telecommuting jobs where the applicant does not need to be in a physical office. Note: This should not be used for citizenship or work visa requirements.
An application that can complete the request.
Type of software application, e.g. 'Game, Multimedia'.
Contact details for further information relevant to this job posting.
The date at which the program stops collecting applications for the next enrollment cycle.
The date at which the program begins collecting applications for the next enrollment cycle.
Subcategory of the application, e.g. 'Arcade Game'.
The name of the application suite to which the application belongs (e.g. Excel belongs to Office).
The delivery method(s) to which the delivery charge or payment charge specification applies.
The payment method(s) to which the payment charge specification applies.
Indicates a page or other link involved in archival of a CreativeWork. In the case of MediaReview, the items in a MediaReviewItem may often become inaccessible, but be archived by archival, journalistic, activist, or law enforcement organizations. In such cases, the referenced page may not directly publish the content.
The area within which users can expect to reach the broadcast service.
The geographic area where the service is provided.
The airport where the flight terminates.
The terminal or port from which the boat arrives.
The stop or station from which the bus arrives.
Identifier of the flight's arrival gate.
Identifier of the flight's arrival terminal.
The number of copies when multiple copies of a piece of artwork are produced - e.g. for a limited edition of 20 prints, 'artEdition' refers to the total number of copies (in this example "20").
The material used. (E.g. Oil, Watercolour, Acrylic, Linoprint, Marble, Cyanotype, Digital, Lithograph, DryPoint, Intaglio, Pastel, Woodcut, Pencil, Mixed Media, etc.)
A material that something is made from, e.g. leather, wool, cotton, paper.
e.g. Painting, Drawing, Sculpture, Print, Photograph, Assemblage, Collage, etc.
Articles may belong to one or more 'sections' in a magazine or newspaper, such as Sports, Lifestyle, etc.
The primary artist for a work in a medium other than pencils or digital line art--for example, if the primary artwork is done in watercolors or digital paints.
An Amazon Standard Identification Number (ASIN) is a 10-character alphanumeric unique identifier assigned by Amazon.com and its partners for product identification within the Amazon organization (summary from [Wikipedia](https://en.wikipedia.org/wiki/Amazon_Standard_Identification_Number)'s article). Note also that this is a definition for how to include ASINs in Schema.org data, and not a definition of ASINs in general - see documentation from Amazon for authoritative details. ASINs are most commonly encoded as text strings, but the [asin] property supports URL/URI as potential values too.
An aspect of medical practice that is considered on the page, such as 'diagnosis', 'treatment', 'causes', 'prognosis', 'etiology', 'epidemiology', etc.
Indicates if this web page element is the main subject of the page.
Library file name, e.g., mscorlib.dll, system.web.dll.
Associated product/technology version. E.g., .NET Framework 4.5.
The item being described is intended to assess the competency or learning outcome defined by the referenced term.
The anatomy of the underlying organ system or structures associated with this entity.
A NewsArticle associated with the Media Object.
An associated ClaimReview, related by specific common content, topic or claim. The expectation is that this property would be most typically used in cases where a single activity is conducting both claim reviews and media reviews, in which case relatedMediaReview would commonly be used on a ClaimReview, while relatedClaimReview would be used on MediaReview.
Disease associated to this BioChemEntity. Such disease can be a MedicalCondition or a URL. If you want to add an evidence supporting the association, please use PropertyValue.
A media object that encodes this CreativeWork. This property is a synonym for encoding.
An associated MediaReview, related by specific common content, topic or claim. The expectation is that this property would be most typically used in cases where a single activity is conducting both claim reviews and media reviews, in which case relatedMediaReview would commonly be used on a ClaimReview, while relatedClaimReview would be used on MediaReview.
If applicable, a description of the pathophysiology associated with the anatomical system, including potential abnormal changes in the mechanical, physical, and biochemical functions of the system.
A person that acts as performing member of a sports team; a player as opposed to a coach.
A person or organization attending the event.
The target group associated with a given audience (e.g. veterans, car owners, musicians, etc.).
Date when a certification was last audited. See also [gs1:certificationAuditDate](https://www.gs1.org/voc/certificationAuditDate).
The Organization responsible for authenticating the user's subscription. For example, many media apps require a cable/satellite provider to authenticate your subscription before playing media.
The author of this content or rating. Please note that author is special in that HTML 5 provides a special mechanism for indicating authorship via the rel tag. That is equivalent to this and may be used interchangeably.
The availability of this item—for example In stock, Out of stock, Pre-order, etc.
The end of the availability of the product or service included in the offer.
The beginning of the availability of the product or service included in the offer.
The place(s) from which the offer can be obtained (e.g. store locations).
The geographic area where a service or offered item is provided.
A means of accessing the service (e.g. a phone bank, a web site, a location, etc.).
The delivery method(s) available for this offer.
When the item is available for pickup from the store, locker, etc.
The location in which the strength is available.
A language someone may use with or at the item, service or place. Please use one of the language codes from the [IETF BCP 47 standard](http://tools.ietf.org/html/bcp47). See also inLanguage.
A medical service available from this provider.
An available dosage strength for the drug.
A diagnostic test or procedure offered by this lab.
After this date, the item will no longer be available for pickup.
For an Article, typically a NewsArticle, the backstory property provides a textual summary giving a brief explanation of why and how an article was created. In a journalistic setting this could include information about reporting process, methods, interviews, data sources, etc.
The base salary of the job or of an employee in an EmployeeRole.
A sub property of recipient. The recipient blind copied on a message.
A sub property of participant. The participant who is at the receiving end of the action.
The type of bed or beds included in the accommodation. For the single case of just one bed of a certain type, you use bed directly with a text. If you want to indicate the quantity of a certain kind of bed, use an instance of BedDetails. For more detailed information, use the amenityFeature property.
A media object representing the circumstances before performing this direction.
A bank or bank’s branch, financial institution or international financial institution operating the beneficiary’s bank account or releasing funds for the beneficiary.
Description of benefits associated with the job.
The URL that goes directly to the summary of benefits and coverage for the specific standard plan or plan variation.
The highest value allowed in this rating system.
Specifies for how long this price (or price component) will be billed. Can be used, for example, to model the contractual duration of a subscription or payment plan. Type can be either a Duration or a Number (in which case the unit of measurement, for example month, is specified by the unitCode property).
This property specifies the minimal quantity and rounding increment that will be the basis for the billing. The unit of measurement is specified by the unitCode property.
The time interval used to compute the invoice.
Specifies after how much time this price (or price component) becomes valid and billing starts. Can be used, for example, to model a price increase after the first year of a subscription. The unit of measurement is specified by the unitCode property.
A BioChemEntity that is known to interact with this item.
A similar BioChemEntity, e.g., obtained by fingerprint similarity algorithms.
A role played by the BioChemEntity within a biological context.
The biomechanical properties of the bone.
Indicates a post that is part of a Blog. Note that historically, what we term a "Blog" was once known as a "weblog", and that what we term a "BlogPosting" is now often colloquially referred to as a "blog".
The blood vessel that carries blood from the heart to the muscle.
The airline-specific indicator of boarding order / preference.
The type of boarding policy used by the airline (e.g. zone-based or group-based).
Location in the body of the anatomical structure.
Indicates the design and body style of the vehicle (e.g. station wagon, hatchback, etc.).
'bookingAgent' is an out-dated term indicating a 'broker' that serves as a booking agent.
An entity that arranges for an exchange between a buyer and a seller. In most cases a broker never acquires or releases ownership of a product or service involved in an exchange. If it is not clear whether an entity is a broker, seller, or buyer, the latter two terms are preferred.
The date and time the reservation was booked.
A sub property of participant. The person that borrows the object being lent.
Other co-agents that participated in the action indirectly. E.g. John wrote a book with *Steve*.
A box is the area enclosed by the rectangle formed by two points. The first point is the lower corner, the second point is the upper corner. A box is expressed as two points separated by a space character.
The branches that delineate from the nerve bundle. Not to be confused with branchOf.
The branches that comprise the arterial structure.
A short textual code (also called "store code") that uniquely identifies a place of business. The code is typically assigned by the parentOrganization and used in structured URLs.\n\nFor example, in the URL http://www.starbucks.co.uk/store-locator/etc/detail/3047 the code "3047" is a branchCode for a particular branch.
The larger organization that this local business is a branch of, if any. Not to be confused with (anatomical) branch.
The brand(s) associated with a product or service, or the brand(s) maintained by an organization or business person.
A set of links that can help a user understand and navigate a website hierarchy.
Any precaution, guidance, contraindication, etc. related to this drug's use by breastfeeding mothers.
The media network(s) whose content is broadcast on this station.
The unique address by which the BroadcastService can be identified in a provider lineup. In US, this is typically a number.
The name displayed in the channel guide. For many US affiliates, it is the network name.
The frequency used for over-the-air broadcasts. Numeric values or simple ranges, e.g. 87-99. In addition a shortcut idiom is supported for frequencies of AM and FM radio channels, e.g. "87 FM".
The frequency in MHz for a particular broadcast.
The event being broadcast such as a sporting event or awards ceremony.
The type of service required to have access to the channel (e.g. Standard or Premium).
The modulation (e.g. FM, AM, etc) used by a particular broadcast service.
The timezone in [ISO 8601 format](http://en.wikipedia.org/wiki/ISO_8601) for which the service bases its broadcasts.
The organization owning or operating the broadcast service.
Specifies browser requirements in human-readable text. For example, 'requires HTML5 support'.
The name of the bus (e.g. Bolt Express).
Days of the week when the merchant typically operates, indicated via opening hours markup.
The business function (e.g. sell, lease, repair, dispose) of the offer or component of a bundle (TypeAndQuantityNode). The default is http://purl.org/goodrelations/v1#Sell.
A sub property of participant. The participant/person/organization that bought the object.
The artist that performed this album or recording.
Defines the day(s) of the week on which a recurring Event takes place. May be specified using either DayOfWeek, or alternatively Text conforming to iCal's syntax for byDay recurrence rules.
Defines the month(s) of the year on which a recurring Event takes place. Specified as an Integer between 1-12. January is 1.
Defines the day(s) of the month on which a recurring Event takes place. Specified as an Integer between 1-31.
Defines the week(s) of the month on which a recurring Event takes place. Specified as an Integer between 1-5. For clarity, byMonthWeek is best used in conjunction with byDay to indicate concepts like the first and third Mondays of a month.
A [callsign](https://en.wikipedia.org/wiki/Call_sign), as used in broadcasting and radio communications to identify people, radio and TV stations, or vehicles.
A sub property of object. The candidate subject of this action.
The object upon which the action is carried out, whose state is kept intact or changed. Also known as the semantic roles patient, affected or undergoer (which change their state) or theme (which doesn't). E.g. John read *a book*.
The available volume for cargo or luggage. For automobiles, this is usually the trunk volume.\n\nTypical unit code(s): LTR for liters, FTQ for cubic foot/feet\n\nNote: You can use minValue and maxValue to indicate ranges.
'carrier' is an out-dated term indicating the 'provider' for parcel delivery and flights.
The service provider, service operator, or service performer; the goods producer. Another party (a seller) may offer those services or goods on behalf of the provider. A provider may also serve as the seller.
Specifies specific carrier(s) requirements for the application (e.g. an application may only work on a specific carrier network).
A cardholder benefit that pays the cardholder a small percentage of their net expenditures.
A data catalog which contains this dataset.
The condition, complication, symptom, sign, etc. caused.
A sub property of recipient. The recipient copied on a message.
Identifier of a certification instance (as registered with an independent certification body). Typically this identifier can be used to consult and verify the certification instance. See also [gs1:certificationIdentification](https://www.gs1.org/voc/certificationIdentification).
Rating of a certification instance (as defined by an independent certification body). Typically this rating can be used to rate the level to which the requirements of the certification instance are fulfilled. See also [gs1:certificationValue](https://www.gs1.org/voc/certificationValue).
Indicates the current status of a certification: active or inactive. See also [gs1:certificationStatus](https://www.gs1.org/voc/certificationStatus).
Fictional person connected with a creative work.
A piece of data that represents a particular aspect of a fictional character (skill, power, character points, advantage, disadvantage).
The name of a character played in some acting or performing role, i.e. in a PerformanceRole.
The earliest someone may check into a lodging establishment.
A URL template (RFC 6570) for a checkout page for an offer. This approach allows merchants to specify a URL for online checkout of the offered product, by interpolating parameters such as the logged in user ID, product ID, quantity, discount code etc. Parameter naming and standardization are not specified here.
The latest someone may check out of a lodging establishment.
The chemical composition describes the identity and relative ratio of the chemical elements that make up the substance.
A role played by the BioChemEntity within a chemical context.
The number of milligrams of cholesterol.
A circle is the circular region of a specified radius centered at a specified latitude and longitude. A circle is expressed as a pair followed by a radius in meters.
For a Claim interpreted from MediaObject content, the interpretedAsClaim property can be used to indicate a claim contained, implied or refined from the content of a MediaObject.
A short summary of the specific claims reviewed in a ClaimReview.
Description of the absorption and elimination of drugs, including their concentration (pharmacokinetics, pK) and biological effects (pharmacodynamics, pD).
Position of the clip within an ordered group of clips.
The position of an item in a series or sequence of items.
The closing hour of the place or service on the given day(s) of the week.
A person that acts in a coaching role for a sports team.
A medical code for the entity, taken from a controlled vocabulary or ontology such as ICD-9, DiseasesDB, MeSH, SNOMED-CT, RxNorm, etc.
A short textual code that uniquely identifies the value.
A code that identifies this DefinedTerm within a DefinedTermSet.
A sub property of object. The collection target of the action.
The number of items in the Collection.
collectionsize
A color swatch image, visualizing the color of a Product. Should match the textual description specified in the color property. This can be a URL or a fully described ImageObject.
An image of the item. This can be a URL or a fully described ImageObject.
The individual who adds color to inked drawings.
The number of comments this CreativeWork (e.g. Article, Question or Answer) has received. This is most applicable to works published in Web sites with commenting system; additional comments may exist elsewhere.
The time at which the UserComment was made.
Knowledge, skill, ability or personal attribute that must be demonstrated by a person or other entity in order to do something such as earn an Educational Occupational Credential or understand a LearningResource.
The person or organization who wrote a composition, or who is the composer of a work performed at some event.
Specifying something physically contained by something else. Typically used here for the underlying anatomical structures, such as organs, that comprise the anatomical system.
Conditions that affect the availability of, or method(s) of access to, an item. Typically used for real world items such as an ArchiveComponent held by an ArchiveOrganization. This property is not suitable for use as a general Web access control mechanism. It is expressed only in natural language.\n\nFor example "Available by appointment from the Reading Room" or "Accessible only from logged-in accounts ".
A number that confirms the given order or payment has been received.
Other anatomical structures to which this structure is connected.
Indicates a property used as a constraint. For example, in the definition of a StatisticalVariable. The value is a property, either from within Schema.org or from other compatible (e.g. RDF) systems such as DataCommons.org or Wikidata.org.
An option available on this contact point (e.g. a toll-free number or support for hearing-impaired callers).
A contact point for a person or organization.
A person or organization can have different contact points, for different purposes. For example, a sales contact point, a PR contact point and so on. This property is used to specify the kind of contact point.
A secure method for consumers to purchase products or services via debit, credit or smartcards by using RFID or NFC technology.
The basic containment relation between a place and one that contains it.
Official rating of a piece of content—for example, 'MPAA PG-13'.
The specific time described by a creative work, for works (e.g. articles, video objects etc.) that emphasise a particular moment within an Event.
The supported content type(s) for an EntryPoint response.
Actual bytes of the media object, for example the image file or video file.
The time it takes to actually cook the dish, in [ISO 8601 duration format](http://en.wikipedia.org/wiki/ISO_8601).
The length of time it takes to perform instructions or a direction (not including time to prepare the supplies), in [ISO 8601 duration format](http://en.wikipedia.org/wiki/ISO_8601).
The method of cooking, such as Frying, Steaming, ...
Indicates a correction to a CreativeWork, either via a CorrectionComment, textually or in another document.
For an Organization (e.g. NewsMediaOrganization), a statement describing (in news media, the newsroom’s) disclosure and correction policy for errors.
The category of cost, such as wholesale, retail, reimbursement cap, etc.
The currency (in 3-letter) of the drug cost. See: http://en.wikipedia.org/wiki/ISO_4217.
Additional details to capture the origin of the cost data. For example, 'Medicare Part B'.
Countries for which the application is not supported. You can also provide the two-letter ISO 3166-1 alpha-2 country code.
Countries for which the application is supported. You can also provide the two-letter ISO 3166-1 alpha-2 country code.
The place where the product was assembled.
The place where the item (typically Product) was last processed and tested before importation.
The country of origin of something, including products as well as creative works such as movie and TV content. In the case of TV and movie, this would be the country of the principle offices of the production company or individual responsible for the movie. For other kinds of CreativeWork it is difficult to provide fully general guidance, and properties such as contentLocation and locationCreated may be more applicable. In the case of products, the country of origin of the product. The exact interpretation of this may vary by context and product type, and cannot be fully enumerated here.
A sub property of location. The course where this action was taken.
The location of, for example, where an event is happening, where an organization is located, or where an action takes place.
The identifier for the Course used by the course provider (e.g. CS101 or 6.001).
The medium or means of delivery of the course instance or the mode of study, either as a text label (e.g. "online", "onsite" or "blended"; "synchronous" or "asynchronous"; "full-time" or "part-time") or as a URL reference to a term from a controlled vocabulary (e.g. https://ceds.ed.gov/element/001311#Asynchronous).
Requirements for taking the Course. May be completion of another Course or a textual description like "permission of instructor". Requirements may be a pre-requisite competency, referenced using AlignmentObject.
Represents the length and pace of a course, expressed as a Schedule.
The amount of work expected of students taking the course, often provided as a figure per week or per month, and may be broken down by type. For example, "2 hours of lectures, 1 hour of lab work and 3 hours of independent study per week".
The time when the live blog will stop covering the Event. Note that coverage may continue after the Event concludes.
The time when the live blog will begin covering the Event. Note that coverage may begin before the Event's start time. The LiveBlogPosting may also be created before coverage begins.
The status of a creative work in terms of its stage in a lifecycle. Example terms include Incomplete, Draft, Published, Obsolete. Some organizations define a set of terms for the stages of their publication lifecycle.
The category or type of credential being described, for example "degreeâ€, “certificateâ€, “badgeâ€, or more specific term.
Text that can be used to credit person(s) and/or organization(s) associated with a published Creative Work.
The group the release is credited to if different than the byArtist. For example, Red and Blue is credited to "Stefani Germanotta Band", but by Lady Gaga.
A CSS selector, e.g. of a SpeakableSpecification or WebPageElement. In the latter case, multiple matches within a page can constitute a single conceptual "Web page element".
The currency accepted.\n\nUse standard formats: [ISO 4217 currency format](http://en.wikipedia.org/wiki/ISO_4217), e.g. "USD"; [Ticker symbol](https://en.wikipedia.org/wiki/List_of_cryptocurrencies) for cryptocurrencies, e.g. "BTC"; well known names for [Local Exchange Trading Systems](https://en.wikipedia.org/wiki/Local_exchange_trading_system) (LETS) and other currency types, e.g. "Ithaca HOUR".
The currency in which the monetary amount is expressed.\n\nUse standard formats: [ISO 4217 currency format](http://en.wikipedia.org/wiki/ISO_4217), e.g. "USD"; [Ticker symbol](https://en.wikipedia.org/wiki/List_of_cryptocurrencies) for cryptocurrencies, e.g. "BTC"; well known names for [Local Exchange Trading Systems](https://en.wikipedia.org/wiki/Local_exchange_trading_system) (LETS) and other currency types, e.g. "Ithaca HOUR".
Party placing the order or paying the invoice.
The type of return fees if the product is returned due to customer remorse.
The method (from an enumeration) by which the customer obtains a return shipping label for a product returned due to customer remorse.
The amount of shipping costs if a product is returned due to customer remorse. Applicable when property customerRemorseReturnFees equals ReturnShippingFees.
customer remorse return shipping fees amount
Order cutoff time allows merchants to describe the time after which they will no longer process orders received on that day. For orders processed after cutoff time, one day gets added to the delivery time estimate. This property is expected to be most typically used via the ShippingRateSettings publication pattern. The time is indicated using the ISO-8601 Time format, e.g. "23:30:00-05:00" would represent 6:30 pm Eastern Standard Time (EST) which is 5 hours behind Coordinated Universal Time (UTC).
collectiondate - Date for which patient counts are reported.
Name of the County of the NHSN facility that this data record applies to. Use cvdFacilityId to identify the facility. To provide other details, healthcareReportingData can be used on a Hospital entry.
Identifier of the NHSN facility that this data record applies to. Use cvdFacilityCounty to indicate the county. To provide other details, healthcareReportingData can be used on a Hospital entry.
numbeds - HOSPITAL INPATIENT BEDS: Inpatient beds, including all staffed, licensed, and overflow (surge) beds used for inpatients.
numbedsocc - HOSPITAL INPATIENT BED OCCUPANCY: Total number of staffed inpatient beds that are occupied.
numc19died - DEATHS: Patients with suspected or confirmed COVID-19 who died in the hospital, ED, or any overflow location.
numc19hopats - HOSPITAL ONSET: Patients hospitalized in an NHSN inpatient care location with onset of suspected or confirmed COVID-19 14 or more days after hospitalization.
numc19hosppats - HOSPITALIZED: Patients currently hospitalized in an inpatient care location who have suspected or confirmed COVID-19.
numc19mechventpats - HOSPITALIZED and VENTILATED: Patients hospitalized in an NHSN inpatient care location who have suspected or confirmed COVID-19 and are on a mechanical ventilator.
numc19ofmechventpats - ED/OVERFLOW and VENTILATED: Patients with suspected or confirmed COVID-19 who are in the ED or any overflow location awaiting an inpatient bed and on a mechanical ventilator.
numc19overflowpats - ED/OVERFLOW: Patients with suspected or confirmed COVID-19 who are in the ED or any overflow location awaiting an inpatient bed.
numicubeds - ICU BEDS: Total number of staffed inpatient intensive care unit (ICU) beds.
numicubedsocc - ICU BED OCCUPANCY: Total number of staffed inpatient ICU beds that are occupied.
numtotbeds - ALL HOSPITAL BEDS: Total number of all inpatient and outpatient beds, including all staffed, ICU, licensed, and overflow (surge) beds used for inpatients or outpatients.
numvent - MECHANICAL VENTILATORS: Total number of ventilators available.
numventuse - MECHANICAL VENTILATORS IN USE: Total number of ventilators in use.
An item within a data feed. Data feeds may have many elements.
The range of temporal applicability of a dataset, e.g. for a 2011 census dataset, the year 2011 (in ISO 8601 time interval format).
The temporalCoverage of a CreativeWork indicates the period that the content applies to, i.e. that it describes, either as a DateTime or as a textual string indicating a time period in [ISO 8601 time interval format](https://en.wikipedia.org/wiki/ISO_8601#Time_intervals). In the case of a Dataset it will typically indicate the relevant time period in a precise notation (e.g. for a 2011 census dataset, the year 2011 would be written "2011/2012"). Other forms of content, e.g. ScholarlyArticle, Book, TVSeries or TVEpisode, may indicate their temporalCoverage in broader terms - textually or via well-known URL. Written works such as books may sometimes have precise temporal coverage too, e.g. a work set in 1939 - 1945 can be indicated in ISO 8601 interval format format via "1939/1945". Open-ended date ranges can be written with ".." in place of the end date. For example, "2015-11/.." indicates a range beginning in November 2015 and with no specified final date. This is tentative and might be updated in future when ISO 8601 is officially updated.
The datetime the item was removed from the DataFeed.
Date of first publication or broadcast. For example the date a CreativeWork was broadcast or a Certification was issued.
The date/time at which the message has been read by the recipient if a single recipient exists.
The date/time the message was received if a single recipient exists.
The date/time at which the message was sent.
The date of the first registration of the vehicle with the respective public authorities.
A [dateline](https://en.wikipedia.org/wiki/Dateline) is a brief piece of text included in news articles that describes where and when the story was written or filed though the date is often omitted. Sometimes only a placename is provided. Structured representations of dateline-related information can also be expressed more explicitly using locationCreated (which represents where a work was created, e.g. where a news report was written). For location depicted or described in the content, use contentLocation. Dateline summaries are oriented more towards human readers than towards automated processing, and can vary substantially. Some examples: "BEIRUT, Lebanon, June 2.", "Paris, France", "December 19, 2017 11:43AM Reporting from Washington", "Beijing/Moscow", "QUEZON CITY, Philippines".
The day of the week for which these opening hours are valid.
The default value of the input. For properties that expect a literal, the default is a literal value, for properties that expect an object, it's an ID reference to one of the current values.
The typical delay between the receipt of the order and the goods either leaving the warehouse or being prepared for pickup, in case the delivery method is on site pickup.
A sub property of instrument. The method of delivery.
The object that helped the agent perform the action. E.g. John wrote a book with *a pen*.
New entry added as the package passes through each leg of its journey (from shipment to final delivery).
The total delay between the receipt of the order and the goods reaching the final customer.
A relationship between an organization and a department of that organization, also described as an organization (allowing different urls, logos, opening hours). For example: a store with a pharmacy, or a bakery with a cafe.
The airport where the flight originates.
The terminal or port from which the boat departs.
The stop or station from which the bus departs.
Identifier of the flight's departure gate.
The platform from which the train departs.
The station from which the train departs.
Identifier of the flight's departure terminal.
Prerequisites needed to fulfill steps in article.
Device required to run the application. Used in cases where a specific make/model is required to run the application.
One or more alternative conditions considered in the differential diagnosis process as output of a diagnosis process.
An image containing a diagram that illustrates the structure and/or its component substructures and/or connections with other structures.
A sub property of instrument. The diet used in this action.
Nutritional information specific to the dietary plan. May include dietary recommendations on what foods to avoid, what foods to consume, and specific alterations/deviations from the USDA or other regulatory body's approved dietary guidelines.
One of a set of differential diagnoses for the condition. Specifically, a closely-related or competing diagnosis typically considered later in the cognitive process whereby this medical condition is distinguished from others most likely responsible for a similar collection of signs and symptoms to reach the most parsimonious diagnosis or diagnoses in a patient.
Indicates an IPTCDigitalSourceEnumeration code indicating the nature of the digital source(s) for some CreativeWork.
Indicates whether an url that is associated with a JobPosting enables direct application for the job, via the posting website. A job posting is considered to have directApply of True if an application process for the specified job can be directly initiated via the url(s) given (noting that e.g. multiple internet domains might nevertheless be involved at an implementation level). A value of False is appropriate if there is no clear path to applying directly online for the specified job, navigating directly from the JobPosting url(s) supplied.
A director of e.g. TV, radio, movie, video games etc. content. Directors can be associated with individual items or with a series, episode, clip.
A director of e.g. TV, radio, movie, video gaming etc. content, or of an event. Directors can be associated with individual items or with a series, episode, clip.
A sub property of description. A short description of the item used to disambiguate from other, similar items. Information from other properties (in particular, name) may be necessary for the description to be useful for disambiguation.
The currency of the discount.\n\nUse standard formats: [ISO 4217 currency format](http://en.wikipedia.org/wiki/ISO_4217), e.g. "USD"; [Ticker symbol](https://en.wikipedia.org/wiki/List_of_cryptocurrencies) for cryptocurrencies, e.g. "BTC"; well known names for [Local Exchange Trading Systems](https://en.wikipedia.org/wiki/Local_exchange_trading_system) (LETS) and other currency types, e.g. "Ithaca HOUR".
Specifies the CreativeWork associated with the UserComment.
A link to the page containing the comments of the CreativeWork.
Statistical information about the spread of a disease, either as WebContent, or described directly as a Dataset, or the specific Observations in the dataset. When a WebContent URL is provided, the page indicated might also contain more such markup.
The date that this organization was dissolved.
The distance travelled, e.g. exercising or travelling.
One of a set of signs and symptoms that can be used to distinguish this diagnosis from others in the differential diagnosis.
A downloadable form of this dataset, at a specific location, in a specific format. This property can be repeated if different variations are available. There is no expectation that different downloadable distributions must contain exactly equivalent information (see also [DCAT](https://www.w3.org/TR/vocab-dcat-3/#Class:Distribution) on this point). Different distributions might include or exclude different subsets of the entire dataset, for example.
Statement on diversity policy by an Organization e.g. a NewsMediaOrganization. For a NewsMediaOrganization, a statement describing the newsroom’s diversity policy on both staffing and sources, typically providing staffing data.
For an Organization (often but not necessarily a NewsMediaOrganization), a report on staffing diversity issues. In a news context this might be for example ASNE or RTDNA (US) reports, or self-reported.
Further documentation describing the Web API in more detail.
Indicates when shipping to a particular shippingDestination is not available.
Whether borrower is a resident of the jurisdiction where the property is located.
A dosage form in which this drug/supplement is available, e.g. 'tablet', 'suspension', 'injection'.
A dosing schedule for the drug for a given population, either observed, recommended, or maximum dose based on the type used.
a type of payment made in cash during the onset of the purchase of an expensive good/service. The payment typically represents only a percentage of the full purchase price.
If the file can be downloaded, URL to download the binary.
The number of downvotes this question, answer or comment has received from the community.
The vasculature that the vein drains into.
The drive wheel configuration, i.e. which roadwheels will receive torque from the vehicle's engine via the drivetrain.
Specifying a drug or medicine used in a medication procedure.
The class of drug this belongs to (e.g., statins).
The unit in which the drug is measured, e.g. '5 mg tablet'.
The Dun & Bradstreet DUNS number for identifying an organization or business person.
A therapy that duplicates or overlaps this one.
The duration of the warranty promise. Common unitCode values are ANN for year, MON for months, or DAY for days.
A media object representing the circumstances while performing this direction.
The amount to be paid as a penalty in the event of early payment of the loan.
An [EIDR](https://eidr.org/) (Entertainment Identifier Registry) identifier representing a specific edit / edition for a work of film or television. For example, the motion picture known as "Ghostbusters" whose titleEIDR is "10.5240/7EC7-228A-510A-053E-CBB8-J" has several edits, e.g. "10.5240/1F2A-E1C5-680A-14C6-E76B-I" and "10.5240/8A35-3BEE-6497-5D12-9E4F-3". Since schema.org types like Movie and TVEpisode can be used for both works and their multiple expressions, it is possible to use titleEIDR alone (for a general description), or alongside editEIDR for a more edit-specific description.
Specifies the Person who edited the CreativeWork.
For questions that are part of learning resources (e.g. Quiz), eduQuestionType indicates the format of question being given. Example: "Multiple choice", "Open ended", "Flashcard".
Educational background needed for the position or Occupation.
An alignment to an established educational framework. This property should not be used where the nature of the alignment can be described using a simple property, for example to express that a resource teaches or assesses a competency.
A description of the qualification, award, certificate, diploma or other educational credential awarded as a consequence of successful completion of this course or program.
The framework to which the resource being described is aligned.
The level in terms of progression through an educational or training context. Examples of educational levels include 'beginner', 'intermediate' or 'advanced', and formal sets of level indicators.
Similar to courseMode, the medium or means of delivery of the program as a whole. The value may either be a text label (e.g. "online", "onsite" or "blended"; "synchronous" or "asynchronous"; "full-time" or "part-time") or a URL reference to a term from a controlled vocabulary (e.g. https://ceds.ed.gov/element/001311#Asynchronous ).
An educationalRole of an EducationalAudience.
The purpose of a work in the context of education; for example, 'assignment', 'group work'.
The elevation of a location ([WGS 84](https://en.wikipedia.org/wiki/World_Geodetic_System)). Values may be of the form 'NUMBER UNIT\_OF\_MEASUREMENT' (e.g., '1,000 m', '3,200 ft') while numbers alone should be assumed to be a value in meters.
The legal requirements such as citizenship, visa and other documentation required for an applicant to this job.
The type(s) of customers for which the given offer is valid.
The duration for which the given offer is valid.
The interval and unit of measurement of ordering quantities for which the offer or price specification is valid. This allows e.g. specifying that a certain freight charge is valid only for a certain quantity.
The ISO 3166-1 (ISO 3166-1 alpha-2) or ISO 3166-2 code, the place, or the GeoShape for the geo-political region(s) for which the offer or delivery charge specification is valid.\n\nSee also ineligibleRegion.
The transaction volume, in a monetary unit, for which the offer or price specification is valid, e.g. for indicating a minimal purchasing volume, to express free shipping above a certain order volume, or to limit the acceptance of credit cards to purchases to a certain minimal amount.
A URL pointing to a player for a specific video. In general, this is the information in the ```src``` element of an ```embed``` tag and should not be the same as the content of the ```loc``` tag.
Represents textual captioning from a MediaObject, e.g. text of a 'meme'.
The caption for this object. For downloadable machine formats (closed caption, subtitles etc.) use MediaObject and indicate the encodingFormat.
The CO2 emissions in g/km. When used in combination with a QuantitativeValue, put "g/km" into the unitText property of that value, since there is no UN/CEFACT Common Code for "g/km".
A description of the employer, career opportunities and work environment for this position.
Type of employment (e.g. full-time, part-time, contract, temporary, seasonal, internship).
Indicates the department, unit and/or facility where the employee reports and/or in which the job is to be performed.
The supported encoding type(s) for an EntryPoint request.
A media object that encodes this CreativeWork.
A media object that encodes this CreativeWork. This property is a synonym for associatedMedia.
The end date and time of the item (in [ISO 8601 date format](http://en.wikipedia.org/wiki/ISO_8601)).
The end time of the clip expressed as the number of seconds from the beginning of the work.
The endTime of something. For a reserved event or service (e.g. FoodEstablishmentReservation), the time that it is expected to end. For actions that span a period of time, when the action was performed. E.g. John wrote a book from January to *December*. For media, including audio and video, it's the time offset of the end of a clip within a larger file.\n\nNote that Event uses startDate/endDate instead of startTime/endTime, even when describing dates with times. This situation may be clarified in future revisions.
A sub property of participant. The person/organization being supported.
People or organizations that endorse the plan.
Specifies the most energy efficient class on the regulated EU energy consumption scale for the product category a product belongs to. For example, energy consumption for televisions placed on the market after January 1, 2020 is scaled from D to A+++.
Specifies the least energy efficient class on the regulated EU energy consumption scale for the product category a product belongs to. For example, energy consumption for televisions placed on the market after January 1, 2020 is scaled from D to A+++.
The volume swept by all of the pistons inside the cylinders of an internal combustion engine in a single movement. \n\nTypical unit code(s): CMQ for cubic centimeter, LTR for liters, INQ for cubic inches\n* Note 1: You can link to information about how the given value has been determined using the valueReference property.\n* Note 2: You can use minValue and maxValue to indicate ranges.
The power of the vehicle's engine. Typical unit code(s): KWT for kilowatt, BHP for brake horsepower, N12 for metric horsepower (PS, with 1 PS = 735,49875 W)\n\n* Note 1: There are many different ways of measuring an engine's power. For an overview, see [http://en.wikipedia.org/wiki/Horsepower#Engine\_power\_test\_codes](http://en.wikipedia.org/wiki/Horsepower#Engine_power_test_codes).\n* Note 2: You can link to information about how the given value has been determined using the valueReference property.\n* Note 3: You can use minValue and maxValue to indicate ranges.
The type of engine or engines powering the vehicle.
A sub property of location. The entertainment business where the action occurred.
The characteristics of associated patients, such as age, gender, race etc.
Position of the episode within an ordered group of episodes.
An episode of a TV/radio series or season.
An episode of a TV, radio or game media within a series or season.
This ordering relation for qualitative values indicates that the subject is equal to the object.
For failed actions, more information on the cause of the failure.
The estimated cost of the supply or supplies consumed when performing instructions.
The estimated time the flight will take.
An estimated salary for a job posting or occupation, based on a variety of variables including, but not limited to industry, job title, and location. Estimated salaries are often computed by outside organizations rather than the hiring organization, who may not have committed to the estimated value.
The condition, complication, or symptom whose risk is being estimated.
Statement about ethics policy, e.g. of a NewsMediaOrganization regarding journalistic and publishing practices, or of a Restaurant, a page describing food source policies. In the case of a NewsMediaOrganization, an ethicsPolicy is typically a statement describing the personal, organizational, and corporate standards of behavior expected by the organization.
The eventAttendanceMode of an event indicates whether it occurs online, offline, or a mix.
Associates an Event with a Schedule. There are circumstances where it is preferable to share a schedule for a series of repeating events rather than data on the individual events themselves. For example, a website or application might prefer to publish a schedule for a weekly gym class rather than provide data on every event. A schedule could be processed by applications to add forthcoming events to a calendar. An Event that is associated with a Schedule using this property should not have startDate or endDate properties. These are instead defined within the associated Schedule, this avoids any ambiguity for clients using the data. The property might have repeated values to specify different schedules, e.g. for different months or seasons.
An eventStatus of an event represents its status; particularly useful when an event is cancelled or rescheduled.
Upcoming or past events associated with this place or organization.
Upcoming or past event associated with this place, organization, or action.
Strength of evidence of the data used to formulate the guideline (enumerated).
Source of the data used to formulate the guidance, e.g. RCT, consensus opinion, etc.
Defines a Date or DateTime during which a scheduled Event will not take place. The property allows exceptions to a Schedule to be specified. If an exception is specified as a DateTime then only the event that would have started at that specific date and time should be excluded from the schedule. If an exception is specified as a Date then any event that is scheduled for that 24 hour period should be excluded from the schedule. This allows a whole day to be excluded from the schedule without having to itemise every scheduled event.
The difference between the price at which a broker or other intermediary buys and sells foreign currency.
A sub property of instrument. The exercise plan used on this action.
Type(s) of exercise or activity, such as strength training, flexibility training, aerobics, cardiac rehabilitation, etc.
The earliest date the package may arrive.
The likely outcome in either the short term or long term of the medical condition.
An Offer which must be accepted before the user can perform the Action. For example, the user may need to buy a movie before being able to watch it.
Indicates whether a JobPosting will accept experience (as indicated by OccupationalExperienceRequirements) in place of its formal educational qualifications (as indicated by educationRequirements). If true, indicates that satisfying one of these requirements is sufficient.
Description of skills and experience needed for the position or Occupation.
Medical expert advice related to the plan.
Date the content expires and is no longer useful or available. For example a VideoObject or NewsArticle whose availability or relevance is time-limited, a ClaimReview fact check whose publisher wants to indicate that it may no longer be relevant (or helpful to highlight) after some date, or a Certification the validity has expired.
Tissue, organ, biological sample, etc in which activity of this gene has been observed experimentally. For example brain, digestive system.
Family name. In the U.S., the last name of a Person.
Features or modules provided by this application (and possibly required by other applications).
Description of fees, commissions, and other terms applied either to a class of financial product, or by a financial service organization.
Media type, typically MIME format (see [IANA site](http://www.iana.org/assignments/media-types/media-types.xhtml)) of the content, e.g. application/zip of a SoftwareApplication binary. In cases where a CreativeWork has several media type representations, 'encoding' can be used to indicate each MediaObject alongside particular fileFormat information. Unregistered or niche file formats can be indicated instead via the most appropriate URL, e.g. defining Web page or a Wikipedia entry.
Media type typically expressed using a MIME format (see [IANA site](http://www.iana.org/assignments/media-types/media-types.xhtml) and [MDN reference](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types)), e.g. application/zip for a SoftwareApplication binary, audio/mpeg for .mp3 etc. In cases where a CreativeWork has several media type representations, encoding can be used to indicate each MediaObject alongside particular encodingFormat information. Unregistered or niche encoding and file formats can be indicated instead via the most appropriate URL, e.g. defining Web page or a Wikipedia/Wikidata entry.
Size of the application / package (e.g. 18MB). In the absence of a unit (MB, KB etc.), KB will be assumed.
A financial aid type or program which students may use to pay for tuition or fees associated with the program.
Indicates the first known occurrence of a Claim in some CreativeWork.
The date and place the work was first performed.
The unique identifier for a flight including the airline IATA code. For example, if describing United flight 110, where the IATA code for United is 'UA', the flightNumber is 'UA110'.
The floor level for an Accommodation in a multi-storey building. Since counting systems [vary internationally](https://en.wikipedia.org/wiki/Storey#Consecutive_number_floor_designations), the local system should be used where possible.
A floor limit is the amount of money above which credit card transactions must be authorized.
The size of the accommodation, e.g. in square meter or squarefoot. Typical unit code(s): MTK for square meter, FTK for square foot, or YDK for square yard.
A sub property of object. The person or organization being followed.
The most generic uni-directional social relation.
Typical or recommended followup care after the procedure is performed.
A sub property of location. The specific food establishment where the action occurred.
A sub property of location. The specific food event where the action occurred.
Any precaution, guidance, contraindication, etc. related to consumption of specific foods while taking this drug.
A person or organization who founded this organization.
The date that this organization was founded.
The place where the Organization was founded.
A flag to signal that the item, event, or place is accessible for free.
A monetary value above (or at) which the shipping rate becomes free. Intended to be used via an OfferShippingDetails with shippingSettingsLink matching this ShippingRateSettings.
A sub property of location. The original location of the object or the agent before the action.
The capacity of the fuel tank or in the case of electric cars, the battery. If there are multiple components for storage, this should indicate the total of all storage of the same type.\n\nTypical unit code(s): LTR for liters, GLL of US gallons, GLI for UK / imperial gallons, AMH for ampere-hours (for electrical vehicles).
The amount of fuel consumed for traveling a particular distance or temporal duration with the given vehicle (e.g. liters per 100 km).\n\n* Note 1: There are unfortunately no standard unit codes for liters per 100 km. Use unitText to indicate the unit of measurement, e.g. L/100 km.\n* Note 2: There are two ways of indicating the fuel consumption, fuelConsumption (e.g. 8 liters per 100 km) and fuelEfficiency (e.g. 30 miles per gallon). They are reciprocal.\n* Note 3: Often, the absolute value is useful only when related to driving speed ("at 80 km/h") or usage pattern ("city traffic"). You can use valueReference to link the value for the fuel consumption to another value.
The distance traveled per unit of fuel used; most commonly miles per gallon (mpg) or kilometers per liter (km/L).\n\n* Note 1: There are unfortunately no standard unit codes for miles per gallon or kilometers per liter. Use unitText to indicate the unit of measurement, e.g. mpg or km/L.\n* Note 2: There are two ways of indicating the fuel consumption, fuelConsumption (e.g. 8 liters per 100 km) and fuelEfficiency (e.g. 30 miles per gallon). They are reciprocal.\n* Note 3: Often, the absolute value is useful only when related to driving speed ("at 80 km/h") or usage pattern ("city traffic"). You can use valueReference to link the value for the fuel economy to another value.
The type of fuel suitable for the engine or engines of the vehicle. If the vehicle has only one engine, this property can be attached directly to the vehicle.
The degree of mobility the joint allows.
A person or organization that supports (sponsors) something through some kind of financial contribution.
A person or organization that supports a thing through a pledge, promise, or financial contribution. E.g. a sponsor of a Medical Study or a corporate sponsor of an event.
Indicates the availability type of the game content associated with this action, such as whether it is a full version or a demo.
An item is an object within the game world that can be collected by a player or, occasionally, a non-player character.
Real or fictional location of the game (or part of game).
The electronic systems used to play video games.
Gender of something, typically a Person, but possibly also fictional characters, animals, etc. While https://schema.org/Male and https://schema.org/Female may be used, text strings are also acceptable for people who do not identify as a binary gender. The gender property can also be used in an extended sense to cover e.g. the gender of sports teams. As with the gender of individuals, we do not try to enumerate all possibilities. A mixed-gender SportsTeam can be indicated with a text value of "Mixed".
Represents a relationship between two geometries (or the places they represent), relating a containing geometry to a contained geometry. "a contains b iff no points of b lie in the exterior of a, and at least one point of the interior of b lies in the interior of a". As defined in [DE-9IM](https://en.wikipedia.org/wiki/DE-9IM).
Represents a relationship between two geometries (or the places they represent), relating a geometry to another that covers it. As defined in [DE-9IM](https://en.wikipedia.org/wiki/DE-9IM).
Represents a relationship between two geometries (or the places they represent), relating a covering geometry to a covered geometry. "Every point of b is a point of (the interior or boundary of) a". As defined in [DE-9IM](https://en.wikipedia.org/wiki/DE-9IM).
Represents a relationship between two geometries (or the places they represent), relating a geometry to another that crosses it: "a crosses b: they have some but not all interior points in common, and the dimension of the intersection is less than that of at least one of them". As defined in [DE-9IM](https://en.wikipedia.org/wiki/DE-9IM).
Represents spatial relations in which two geometries (or the places they represent) are topologically disjoint: "they have no point in common. They form a set of disconnected geometries." (A symmetric relationship, as defined in [DE-9IM](https://en.wikipedia.org/wiki/DE-9IM).)
Represents spatial relations in which two geometries (or the places they represent) are topologically equal, as defined in [DE-9IM](https://en.wikipedia.org/wiki/DE-9IM). "Two geometries are topologically equal if their interiors intersect and no part of the interior or boundary of one geometry intersects the exterior of the other" (a symmetric relationship).
Represents spatial relations in which two geometries (or the places they represent) have at least one point in common. As defined in [DE-9IM](https://en.wikipedia.org/wiki/DE-9IM).
Indicates the GeoCoordinates at the centre of a GeoShape, e.g. GeoCircle.
Represents a relationship between two geometries (or the places they represent), relating a geometry to another that geospatially overlaps it, i.e. they have some but not all points in common. As defined in [DE-9IM](https://en.wikipedia.org/wiki/DE-9IM).
Indicates the approximate radius of a GeoCircle (metres unless indicated otherwise via Distance notation).
Represents spatial relations in which two geometries (or the places they represent) touch: "they have at least one boundary point in common, but no interior points." (A symmetric relationship, as defined in [DE-9IM](https://en.wikipedia.org/wiki/DE-9IM).)
Represents a relationship between two geometries (or the places they represent), relating a geometry to one that contains it, i.e. it is inside (i.e. within) its interior. As defined in [DE-9IM](https://en.wikipedia.org/wiki/DE-9IM).
The geographic area associated with the audience.
Information about getting tested (for a MedicalCondition), e.g. in the context of a pandemic.
Given name. In the U.S., the first name of a Person.
The [Global Location Number](http://www.gs1.org/gln) (GLN, sometimes also referred to as International Location Number or ILN) of the respective organization, person, or place. The GLN is a 13-digit number used to identify parties and physical locations.
governmentBenefitsInfo provides information about government benefits associated with a SpecialAnnouncement.
The period of time after any due date that the borrower has to fulfil its obligations before a default (failure to pay) is deemed to have occurred.
The person, organization, contact point, or audience that has been granted this permission.
This ordering relation for qualitative values indicates that the subject is greater than the object.
This ordering relation for qualitative values indicates that the subject is greater than or equal to the object.
The GTIN-12 code of the product, or the product to which the offer refers. The GTIN-12 is the 12-digit GS1 Identification Key composed of a U.P.C. Company Prefix, Item Reference, and Check Digit used to identify trade items. See [GS1 GTIN Summary](http://www.gs1.org/barcodes/technical/idkeys/gtin) for more details.
A Global Trade Item Number ([GTIN](https://www.gs1.org/standards/id-keys/gtin)). GTINs identify trade items, including products and services, using numeric identification codes. A correct gtin value should be a valid GTIN, which means that it should be an all-numeric string of either 8, 12, 13 or 14 digits, or a "GS1 Digital Link" URL based on such a string. The numeric component should also have a [valid GS1 check digit](https://www.gs1.org/services/check-digit-calculator) and meet the other rules for valid GTINs. See also [GS1's GTIN Summary](http://www.gs1.org/barcodes/technical/idkeys/gtin) and [Wikipedia](https://en.wikipedia.org/wiki/Global_Trade_Item_Number) for more details. Left-padding of the gtin values is not required or encouraged. The gtin property generalizes the earlier gtin8, gtin12, gtin13, and gtin14 properties. The GS1 [digital link specifications](https://www.gs1.org/standards/Digital-Link/) expresses GTINs as URLs (URIs, IRIs, etc.). Digital Links should be populated into the hasGS1DigitalLink attribute. Note also that this is a definition for how to include GTINs in Schema.org data, and not a definition of GTINs in general - see the GS1 documentation for authoritative details.
The GTIN-13 code of the product, or the product to which the offer refers. This is equivalent to 13-digit ISBN codes and EAN UCC-13. Former 12-digit UPC codes can be converted into a GTIN-13 code by simply adding a preceding zero. See [GS1 GTIN Summary](http://www.gs1.org/barcodes/technical/idkeys/gtin) for more details.
The GTIN-14 code of the product, or the product to which the offer refers. See [GS1 GTIN Summary](http://www.gs1.org/barcodes/technical/idkeys/gtin) for more details.
The GTIN-8 code of the product, or the product to which the offer refers. This code is also known as EAN/UCC-8 or 8-digit EAN. See [GS1 GTIN Summary](http://www.gs1.org/barcodes/technical/idkeys/gtin) for more details.
A medical guideline related to this entity.
Date on which this guideline's recommendation was made.
The medical conditions, treatments, etc. that are the subject of the guideline.
The typical delay between the receipt of the order and the goods either leaving the warehouse or being prepared for pickup, in case the delivery method is on site pickup. Typical properties: minValue, maxValue, unitCode (d for DAY). This is by common convention assumed to mean business days (if a unitCode is used, coded as "d"), i.e. only counting days when the business normally operates.
Used to tag an item to be intended or suitable for consumption or use by adults only.
A symbolic representation of a BioChemEntity. For example, a nucleotide sequence of a Gene or an amino acid sequence of a Protein.
A common representation such as a protein sequence or chemical structure for this entity. For images use schema.org/image.
A Category code contained in this code set.
A Defined Term contained in this term set.
Certification information about a product, organization, service, place, or person.
A course or class that is one of the learning opportunities that constitute an educational / occupational program. No information is implied about whether the course is mandatory or optional; no guarantee is implied about whether the course will be available to everyone on the program.
An offering of the course at a specific time and place or through specific media or mode of study or to a specific section of students.
A credential awarded to the Person or Organization.
A permission related to the access to this document (e.g. permission to read or write an electronic document). For a public document, specify a grantee with an Audience with audienceType equal to "public".
Indicates whether some facility (e.g. FoodEstablishment, CovidTestingFacility) offers a service that can be used by driving through in a car. In the case of CovidTestingFacility such facilities could potentially help with social distancing from other potentially-infected users.
Defines the energy efficiency Category (also known as "class" or "rating") for a product according to an international energy efficiency standard.
Defines the energy efficiency Category (which could be either a rating out of range of values or a yes/no certification) for a product according to an international energy efficiency standard.
The GS1 digital link associated with the object. This URL should conform to the particular requirements of digital links. The link should only contain the Application Identifiers (AIs) that are relevant for the entity being annotated, for instance a Product or an Organization, and for the correct granularity. In particular, for products: A Digital Link that contains a serial number (AI 21) should only be present on instances of IndividualProduct A Digital Link that contains a lot number (AI 10) should be annotated as SomeProduct if only products from that lot are sold, or IndividualProduct if there is only a specific product. A Digital Link that contains a global model number (AI 8013) should be attached to a Product or a ProductModel. Other item types should be adapted similarly.
Indicates the aspect or aspects specifically addressed in some HealthTopicContent. For example, that the content is an overview, or that it talks about treatment, self-care, treatments or their side-effects.
A measurement of an item, For example, the inseam of pants, the wheel size of a bicycle, the gauge of a screw, or the carbon footprint measured for certification by an authority. Usually an exact measurement, but can also be a range of measurements for adjustable products, for example belts and ski bindings.
MemberProgram offered by an Organization, for example an eCommerce merchant or an airline.
A food or drink item contained in a menu or menu section.
A subgrouping of the menu (by dishes, course, serving time period, etc.).
Specifies a MerchantReturnPolicy that may be applicable.
Molecular function performed by this BioChemEntity; please use PropertyValue if you want to include any evidence.
The Person's occupation. For past professions, use Role for expressing dates.
Indicates an OfferCatalog listing for this Organization, Person, or Service.
Points-of-Sales operated by the organization or person.
A member benefit for a particular tier of a loyalty program.
A requirement for a user to join a membership tier, for example: a CreditCard if the tier requires sign up for a credit card, A UnitPriceSpecification if the user is required to pay a (periodic) fee, or a MonetaryAmount if the user needs to spend a minimum amount to join the tier. If a tier is free to join then this property does not need to be specified.
Specifying the health condition(s) of a patient, medical study, or other target audience.
Whether the coinsurance applies before or after deductible, etc. TODO: Is this a closed set?
The rate of coinsurance expressed as a number between 0.0 and 1.0.
Whether the copay is before or after deductible, etc. TODO: Is this a closed set?
The costs to the patient for services under this network or formulary.
The tier(s) of drugs offered by this formulary or insurance plan.
The 14-character, HIOS-generated Plan ID number. (Plan IDs must be unique, even across different markets.)
The URL that goes directly to the plan brochure for the specific standard plan or plan variation.
Name or unique ID of network. (Networks are often reused across different insurance plans.)
The category or type of pharmacy associated with this cost sharing.
Indicates data describing a hospital, e.g. a CDC CDCPMDRecord or as some kind of Dataset.
The highest price of all offers available.\n\nUsage guidelines:\n\n* Use values from 0123456789 (Unicode 'DIGIT ZERO' (U+0030) to 'DIGIT NINE' (U+0039)) rather than superficially similar Unicode symbols.\n* Use '.' (Unicode 'FULL STOP' (U+002E)) rather than ',' to indicate a decimal point. Avoid using these symbols as a readability separator.
Organization or Person offering the job position.
A contact location for a person's residence.
An honorific prefix preceding a Person's name such as Dr/Mrs/Mr.
An honorific suffix following a Person's name such as M.D./PhD/MSCSW.
A hospital with which the physician or office is affiliated.
The Organization (airline, travelers' club, retailer, etc.) the membership is made with or which offers the MemberProgram.
The hours during which this service or contact is available.
An HTTP method that specifies the appropriate HTTP method for a request to an HTTP EntryPoint. Values are capitalized strings as used in HTTP.
IATA identifier for an airline or airport.
A physical examination that can identify this sign.
A diagnostic test that can identify this sign.
The album to which this recording belongs.
The CableOrSatelliteService offering the channel.
Non-proprietary identifier for molecular entity that can be used in printed and electronic data sources thus enabling easier linking of diverse data compilations.
InChIKey is a hashed version of the full InChI (using the SHA-256 algorithm).
A CategoryCodeSet that contains this category code.
A DefinedTermSet that contains this term.
The playlist to which this recording belongs.
Indicates the productGroupID for a ProductGroup that this product isVariantOf.
Are in-store returns offered? (For more advanced return methods use the returnMethod property.)
Qualification, candidature, degree, application that Thesis supports.
Description of bonus and commission compensation aspects of the job.
Smaller compositions included in this work (e.g. a movement in a symphony).
A data catalog which contains this dataset (this property was previously 'catalog', preferred name is now 'includedInDataCatalog').
The insurance plans that cover this drug.
A modifiable or non-modifiable risk factor included in the calculation, e.g. age, coexisting condition.
This links to a node or nodes indicating the exact quantity of the products included in an Offer or ProductCollection.
The condition, complication, etc. influenced by this factor.
The industry associated with the job position.
The ISO 3166-1 (ISO 3166-1 alpha-2) or ISO 3166-2 code, the place, or the GeoShape for the geo-political region(s) for which the offer or delivery charge specification is not valid, e.g. a region where the transaction is not allowed.\n\nSee also eligibleRegion.
The actual infectious agent, such as a specific bacterium.
The class of infectious agent (bacteria, prion, etc.) that causes the disease.
A single ingredient used in the recipe, e.g. sugar, flour or garlic.
A sub-property of instrument. A supply consumed when performing instructions or a direction.
The individual who traces over the pencil drawings in ink after pencils are complete.
The place of attachment of a muscle, or what the muscle moves.
URL at which the app may be installed, if different from the URL of the item.
A person assigned to instruct or provide instructional assistance for the CourseInstance.
Quantitative measure gauging the degree of force involved in the exercise, for example, heartbeats per minute. May include the velocity of the movement.
Another drug that is known to interact with this drug in a way that impacts the effect of this drug or causes a risk to the patient. Note: disease interactions are typically captured as contraindications.
This property is deprecated, alongside the UserInteraction types on which it depended.
The number of interactions for the CreativeWork using the WebSite or SoftwareApplication. The most specific child type of InteractionCounter should be used.
The WebSite or SoftwareApplication where the interactions took place.
The Action representing the type of interaction. For up votes, +1s, etc. use LikeAction. For down votes use DislikeAction. Otherwise, use the most specific Action.
The predominant mode of learning supported by the learning resource. Acceptable values are 'active', 'expositive', or 'mixed'.
The interest rate, charged or paid, applicable to the financial product. Note: This is different from the calculated annualPercentageRate.
Used to indicate a specific claim contained, implied, translated or refined from the content of a MediaObject or other CreativeWork. The interpreting party can be indicated using claimInterpreter.
The current approximate inventory level for the item or items.
Relates a property to a property that is its inverse. Inverse properties relate the same pairs of items to each other, but in reversed direction. For example, the 'alumni' and 'alumniOf' properties are inverseOf each other. Some properties don't have explicit inverses; in these situations RDFa and JSON-LD syntax for reverse properties can be used.
Whether the provider is accepting new patients.
A pointer to another product (or multiple products) for which this product is an accessory or spare part.
True if the drug is available in a generic form (regardless of name).
A resource that was used in the creation of this resource. This term can be repeated for multiple sources. For example, http://example.com/great-multiplication-intro.html.
A resource from which this work is derived or from which it is a modification or adaptation.
A pointer to another product (or multiple products) for which this product is a consumable.
Indicates whether this content is family friendly.
Indicates whether the offer was accepted as a gift for someone other than the buyer.
Biological process this BioChemEntity is involved in; please use PropertyValue if you want to include any evidence.
True if the broadcast is of a live event.
Subcellular location where this BioChemEntity is located; please use PropertyValue if you want to include any evidence.
Indicates some accommodation that this floor plan describes.
True if this item's name is a proprietary/brand name (vs. generic name).
A pointer to another, somehow related product (or multiple products).
Whether the 3DModel allows resizing. For example, room layout applications often do not allow 3DModel elements to be resized to reflect reality.
A pointer to another, functionally similar product (or multiple products).
This can be marked 'true' to indicate that some published DeliveryTimeSettings or ShippingRateSettings are intended to apply to all OfferShippingDetails published by the same merchant, when referenced by a shippingSettingsLink in those settings. It is not meaningful to use a 'true' value for this property alongside a transitTimeLabel (for DeliveryTimeSettings) or shippingLabel (for ShippingRateSettings), since this property is for use with unlabelled settings.
The International Standard of Industrial Classification of All Economic Activities (ISIC), Revision 4 code for a particular organization, business person, or place.
An organization identifier as defined in [ISO 6523(-1)](https://en.wikipedia.org/wiki/ISO/IEC_6523). The identifier should be in the `XXXX:YYYYYY:ZZZ` or `XXXX:YYYYYY`format. Where `XXXX` is a 4 digit _ICD_ (International Code Designator), `YYYYYY` is an _OID_ (Organization Identifier) with all formatting characters (dots, dashes, spaces) removed with a maximal length of 35 characters, and `ZZZ` is an optional OPI (Organization Part Identifier) with a maximum length of 35 characters. The various components (ICD, OID, OPI) are joined with a colon character (ASCII `0x3a`). Note that many existing organization identifiers defined as attributes like [leiCode](https://schema.org/leiCode) (`0199`), [duns](https://schema.org/duns) (`0060`) or [GLN](https://schema.org/globalLocationNumber) (`0088`) can be expressed using ISO-6523. If possible, ISO-6523 codes should be preferred to populating [vatID](https://schema.org/vatID) or [taxID](https://schema.org/taxID), as ISO identifiers are less ambiguous.
The International Standard Recording Code for the recording.
The International Standard Serial Number (ISSN) that identifies this serial publication. You can repeat this property to identify different formats of, or the linking ISSN (ISSN-L) for, this serial publication.
Identifies the issue of publication; for example, "iii" or "2".
The organization issuing the item, for example a Permit, Ticket, or Certification.
The service through which the permit was granted.
The International Standard Musical Work Code for the composition.
An entity represented by an entry in a list or data feed (e.g. an 'artist' in a list of 'artists').
A predefined value from OfferItemCondition specifying the condition of the product or service, or the products or services included in the offer. Also used for product return policies to specify the condition of products accepted for returns.
The type of return fees for returns of defect products.
The method (from an enumeration) by which the customer obtains a return shipping label for a defect product.
Amount of shipping costs for defect product returns. Applicable when property itemDefectReturnFees equals ReturnShippingFees.
For itemListElement values, you can use simple strings (e.g. "Peter", "Paul", "Mary"), existing entities, or use ListItem.\n\nText values are best if the elements in the list are plain strings. Existing entities are best for a simple, unordered list of existing things in your data. ListItem is used with ordered lists when you want to provide additional context about the element in that list or when the same item might be in different places in different lists.\n\nNote: The order of elements in your mark-up is not sufficient for indicating the order or elements. Use ListItem with a 'position' property in such cases.
Type of ordering (e.g. Ascending, Descending, Unordered).
Current location of the item.
itemlocation
Destination(s) ( Place ) that make up a trip. For a trip where destination order is important use ItemList to specify that order (see examples).
Systematic method of naming chemical compounds as recommended by the International Union of Pure and Applied Chemistry (IUPAC).
An indicator as to whether a position is available for an immediate start.
A (typically single) geographic location associated with the job position.
A description of the job location (e.g. TELECOMMUTE for telecommute jobs).
The date on which a successful applicant for this job would be expected to start work. Choose a specific date in the future or use the jobImmediateStart property to indicate the position is to be filled as soon as possible.
The job title of the person (for example, Financial Manager).
A textual description of known damages, both repaired and unrepaired.
The most generic bi-directional social/work relation.
Of a Person, and less typically of an Organization, to indicate a topic that is known about - suggesting possible expertise but not implying it. We do not distinguish skill levels here, or relate this to educational content, events, objectives or JobPosting descriptions.
Of a Person, and less typically of an Organization, to indicate a known language. We do not distinguish skill levels or reading/writing/speaking/signing here. Use language codes from the [IETF BCP 47 standard](http://tools.ietf.org/html/bcp47).
A sub property of participant. The owner of the real estate property.
A sub property of instrument. The language used on this action.
The language of the content or performance or used in an action. Please use one of the language codes from the [IETF BCP 47 standard](http://tools.ietf.org/html/bcp47). See also availableLanguage.
Date on which the content on this web page was last reviewed for accuracy and/or completeness.
The latitude of a location. For example ```37.42242``` ([WGS 84](https://en.wikipedia.org/wiki/World_Geodetic_System)).
A schematic image showing the floorplan layout.
The predominant type or kind characterizing the learning resource. For example, 'presentation', 'handout'.
Length of the lease for some Accommodation, either particular to some Offer or in some cases intrinsic to the property.
The official name of the organization, e.g. the registered company name.
The drug or supplement's legal status, including any controlled substance schedules that apply.
Another legislation that this legislation changes. This encompasses the notions of amendment, replacement, correction, repeal, or other types of change. This may be a direct change (textual or non-textual amendment) or a consequential or indirect change. The property is to be used to express the existence of a change relationship between two acts rather than the existence of a consolidated version of the text that shows the result of the change. For consolidation relationships, use the legislationConsolidates property.
Indicates another legislation taken into account in this consolidated legislation (which is usually the product of an editorial process that revises the legislation). This property should be used multiple times to refer to both the original version or the previous consolidated version, and to the legislations making the change.
The date of adoption or signature of the legislation. This is the date at which the text is officially aknowledged to be a legislation, even though it might not even be published or in force.
The point-in-time at which the provided description of the legislation is valid (e.g.: when looking at the law on the 2016-04-07 (= dateVersion), I get the consolidation of 2015-04-12 of the "National Insurance Contributions Act 2015")
An identifier for the legislation. This can be either a string-based identifier, like the CELEX at EU level or the NOR in France, or a web-based, URL/URI identifier, like an ELI (European Legislation Identifier) or an URN-Lex.
The jurisdiction from which the legislation originates.
Indicates a legal jurisdiction, e.g. of some legislation, or where some government service is based.
Whether the legislation is currently in force, not in force, or partially in force.
The legal value of this legislation file. The same legislation can be written in multiple files with different legal values. Typically a digitally signed PDF have a "stronger" legal value than the HTML file of the same act.
The person or organization that originally passed or made the law: typically parliament (for primary legislation) or government (for secondary legislation). This indicates the "legal author" of the law, as opposed to its physical author.
An individual or organization that has some kind of responsibility for the legislation. Typically the ministry who is/was in charge of elaborating the legislation, or the adressee for potential questions about the legislation once it is published.
Indicates that this legislation (or part of legislation) fulfills the objectives set by another legislation, by passing appropriate implementation measures. Typically, some legislations of European Union's member states or regions transpose European Directives. This indicates a legally binding link between the 2 legislations.
Indicates that this legislation (or part of a legislation) somehow transfers another legislation in a different legislative context. This is an informative link, and it has no legal value. For legally-binding links of transposition, use the legislationTransposes property. For example an informative consolidated law of a European Union's member state "applies" the consolidated version of the European Directive implemented in it.
The type of the legislation. Examples of values are "law", "act", "directive", "decree", "regulation", "statutory instrument", "loi organique", "règlement grand-ducal", etc., depending on the country.
Genre of the creative work, broadcast channel or group.
An organization identifier that uniquely identifies a legal entity as defined in ISO 17442.
A sub property of participant. The person that lends the object being borrowed.
This ordering relation for qualitative values indicates that the subject is lesser than the object.
This ordering relation for qualitative values indicates that the subject is lesser than or equal to the object.
The individual who adds lettering, including speech balloons and sound effects, to artwork.
A line is a point-to-point path consisting of two or more points. A line is expressed as a series of two or more point objects separated by space.
Indicates the relationship type of a Web link.
Amount of mortgage mandate that can be converted into a proper mortgage at a later stage.
The amount of money to pay in a single payment.
Frequency of payments due, i.e. number of months between payments. This is defined as a frequency, i.e. the reciprocal of a period of time.
A form of paying back money previously borrowed from a lender. Repayment usually takes the form of periodic payments that normally include part principal plus interest in each payment.
The duration of the loan or credit agreement.
The duration of the item (movie, audio recording, event, etc.) in [ISO 8601 duration format](http://en.wikipedia.org/wiki/ISO_8601).
The location where the CreativeWork was created, which may not be the same as the location depicted in the CreativeWork.
Textual description of the unit type (including suite vs. room, size of bed, etc.).
The longitude of a location. For example ```-122.08585``` ([WGS 84](https://en.wikipedia.org/wiki/World_Geodetic_System)).
A sub property of participant. The loser of the action.
The lowest price of all offers available.\n\nUsage guidelines:\n\n* Use values from 0123456789 (Unicode 'DIGIT ZERO' (U+0030) to 'DIGIT NINE' (U+0039)) rather than superficially similar Unicode symbols.\n* Use '.' (Unicode 'FULL STOP' (U+002E)) rather than ',' to indicate a decimal point. Avoid using these symbols as a readability separator.
A maintainer of a Dataset, software package (SoftwareApplication), or other Project. A maintainer is a Person or Organization that manages contributions to, and/or publication of, some (typically complex) artifact. It is common for distributions of software and data to be based on "upstream" sources. When maintainer is applied to a specific version of something e.g. a particular version or packaging of a Dataset, it is always possible that the upstream source has a different maintainer. The isBasedOn property can be used to indicate such relationships between datasets to make the different maintenance roles clear. Similarly in the case of software, a package may have dedicated maintainers working on integration into software distributions such as Ubuntu, as well as upstream maintainers of the underlying work.
Indicates the kind of Map, from the MapCategoryType Enumeration.
A marginOfError for an Observation.
For a NewsMediaOrganization, a link to the masthead page or a page listing top editorial management.
The quantity of the materials being described or an expression of the physical space they occupy.
materialextent
A mathematical expression (e.g. 'x^2-3x=0') that may be solved for a specific variable, simplified, or transformed. This can take many formats, e.g. LaTeX, Ascii-Math, or math as you would write with a keyboard.
The highest price if the price is a range.
The upper value of some characteristic or property.
The total number of individuals that may attend an event or venue.
The maximum number of students who may be enrolled in the program.
Recommended intake of this supplement for a given population as defined by a specific recommending authority.
The maximum physical attendee capacity of an Event whose eventAttendanceMode is OfflineEventAttendanceMode (or the offline aspects, in the case of a MixedEventAttendanceMode).
The maximum virtual attendee capacity of an Event whose eventAttendanceMode is OnlineEventAttendanceMode (or the online aspects, in the case of a MixedEventAttendanceMode).
Description of the meals that will be provided or available for purchase.
The measuredProperty of an Observation, typically via its StatisticalVariable. There are various kinds of applicable Property: a schema.org property, a property from other RDF-compatible systems, e.g. W3C RDF Data Cube, Data Commons, Wikidata, or schema.org extensions such as [GS1's](https://www.gs1.org/voc/?show=properties).
Identifies the denominator variable when an observation represents a ratio or percentage.
A subproperty of measurementTechnique that can be used for specifying specific methods, in particular via MeasurementMethodEnum.
A technique, method or technology used in an Observation, StatisticalVariable or Dataset (or DataDownload, DataCatalog), corresponding to the method used for measuring the corresponding variable(s) (for datasets, described using variableMeasured; for Observation, a StatisticalVariable). Often but not necessarily each variableMeasured will have an explicit representation as (or mapping to) an property such as those defined in Schema.org, or other RDF vocabularies and "knowledge graphs". In that case the subproperty of variableMeasured called measuredProperty is applicable. The measurementTechnique property helps when extra clarification is needed about how a measuredProperty was measured. This is oriented towards scientific and scholarly dataset publication but may have broader applicability; it is not intended as a full representation of measurement, but can often serve as a high level summary for dataset discovery. For example, if variableMeasured is: molecule concentration, measurementTechnique could be: "mass spectrometry" or "nmr spectroscopy" or "colorimetry" or "immunofluorescence". If the variableMeasured is "depression rating", the measurementTechnique could be "Zung Scale" or "HAM-D" or "Beck Depression Inventory". If there are several variableMeasured properties recorded for some given data object, use a PropertyValue for each variableMeasured and attach the corresponding measurementTechnique. The value can also be from an enumeration, organized as a MeasurementMetholdEnumeration.
Provides additional qualification to an observation. For example, a GDP observation measures the Nominal value.
The specific biochemical interaction through which this drug or supplement produces its pharmacological effect.
Indicates a MediaManipulationRatingEnumeration classification of a media object (in the context of how it was published or shared).
In the context of a MediaReview, indicates specific media item(s) that are grouped using a MediaReviewItem.
The system of medicine that includes this MedicalEntity, for example 'evidence-based', 'homeopathic', 'chiropractic', etc.
Indicates that the vehicle meets the respective emission standard.
A member of an Organization or a ProgramMembership. Organizations can be members of organizations; ProgramMembership is typically for individuals.
The number of membership points earned by the member. If necessary, the unitText can be used to express the units the points are issued in. (E.g. stars, miles, etc.)
Indicates that the CreativeWork contains a reference to, but is not necessarily about a concept.
Either the actual menu as a structured representation, as text, or a URL of the menu.
Additional menu item(s) such as a side dish of salad or side order of fries that can be added to this menu item. Additionally it can be a menu section containing allowed add-on menu items for this menu item.
'merchant' is an out-dated term for 'seller'.
An entity which offers (sells / leases / lends / loans) the services / goods. A seller may also be a provider.
Specifies either a fixed return date or the number of days (from the delivery date) that a product can be returned. Used when the returnPolicyCategory property is specified as MerchantReturnFiniteReturnWindow.
Specifies a Web page or service by URL, for product returns.
The total distance travelled by the particular vehicle since its initial production, as read from its odometer.\n\nTypical unit code(s): KMT for kilometers, SMI for statute miles.
The lowest price if the price is a range.
The lower value of some characteristic or property.
The minimum payment required at this time.
For a NewsMediaOrganization, a statement on coverage priorities, including any public agenda or stance on issues.
The mobileUrl property is provided for specific situations in which data consumers need to determine whether one of several provided URLs is a dedicated 'mobile site'. To discourage over-use, and reflecting intial usecases, the property is expected only on Product and Offer, rather than Thing. The general trend in web technology is towards [responsive design](https://en.wikipedia.org/wiki/Responsive_web_design) in which content can be flexibly adapted to a wide range of browsing environments. Pages and sites referenced with the long-established url property should ideally also be usable on a wide variety of devices, including mobile phones. In most cases, it would be pointless and counter productive to attempt to update all url markup to use mobileUrl for more mobile-oriented pages. The property is intended for the case when items (primarily Product and Offer) have extra URLs hosted on an additional "mobile site" alongside the main one. It should not be taken as an endorsement of this publication style.
The release date of a vehicle model (often used to differentiate versions of the same make and model).
The date and time the reservation was modified.
The empirical formula is the simplest whole number ratio of all the atoms in a molecule.
This is the molecular weight of the entity being described, not of the parent. Units should be included in the form '<Number> <unit>', for example '12 amu' or as '<QuantitativeValue>.
The monoisotopic mass is the sum of the masses of the atoms in a molecule using the unbound, ground-state, rest mass of the principal (most abundant) isotope for each element instead of the isotopic average mass. Please include the units in the form '<Number> <unit>', for example '770.230488 g/mol' or as '<QuantitativeValue>.
The minimum payment is the lowest amount of money that one is required to pay on a credit card statement each month.
Indicates the minimal number of months of experience required for a position.
The Manufacturer Part Number (MPN) of the product, or the product to which the offer refers.
Whether multiple values are allowed for the property. Default is false.
An arrangement derived from the composition.
The type of composition (e.g. overture, sonata, symphony, etc.).
A member of a music group—for example, John, Paul, George, or Ringo.
The key, mode, or scale this composition uses.
The North American Industry Classification System (NAICS) code for a particular organization or business person.
A position played, performed or filled by a person or organization, as part of an organization. For example, an athlete in a SportsTeam might play in the position named 'Quarterback'.
A role played, performed or filled by a person or organization. For example, the team of creators for a comic book might fill the roles named 'inker', 'penciller', and 'letterer'; or an athlete in a SportsTeam might play in the position named 'Quarterback'.
The expected progression of the condition if it is not treated and allowed to progress naturally.
Provides negative considerations regarding something, most typically in pro/con lists for reviews (alongside positiveNotes). For symmetry In the case of a Review, the property describes the itemReviewed from the perspective of the review; in the case of a Product, the product itself is being described. Since product descriptions tend to emphasise positive claims, it may be relatively unusual to find negativeNotes used in this way. Nevertheless for the sake of symmetry, negativeNotes can be used on Product. The property values can be expressed either as unstructured text (repeated as necessary), or if ordered, as a list (in which case the most negative is at the beginning of the list).
The underlying innervation associated with the muscle.
The neurological pathway extension that involves muscle control.
The total financial value of the person as calculated by subtracting assets from liabilities.
Indicates a page with news updates and guidelines. This could often be (but is not required to be) the main page containing SpecialAnnouncement markup on a site.
A link to the ListItem that follows the current one.
For a NewsMediaOrganization or other news-related Organization, a statement explaining when authors of articles are not named in bylines.
This ordering relation for qualitative values indicates that the subject is not equal to the object.
The generic name of this drug or supplement.
nonprofitStatus indicates the legal status of a non-profit organization in its primary place of business.
Range of acceptable values for a typical patient, when applicable.
Indicates the [NATO stock number](https://en.wikipedia.org/wiki/NATO_Stock_Number) (nsn) of a Product.
The number of adults staying in the unit.
The number of children staying in the unit.
Indicates the number of constraints property values defined for a particular ConstraintNode such as StatisticalVariable. This helps applications understand if they have access to a sufficiently complete description of a StatisticalVariable or other construct that is defined using properties on template-style nodes.
The number of tracks in this album or playlist.
Indicates the total (available plus unavailable) number of accommodation units in an ApartmentComplex, or the number of accommodation units for a specific FloorPlan (within its specific ApartmentComplex). See also numberOfAvailableAccommodationUnits.
The number or type of airbags in the vehicle.
Indicates the number of available accommodation units in an ApartmentComplex, or the number of accommodation units for a specific FloorPlan (within its specific ApartmentComplex). See also numberOfAccommodationUnits.
The number of axles.\n\nTypical unit code(s): C62.
The total integer number of bathrooms in some Accommodation, following real estate conventions as [documented in RESO](https://ddwiki.reso.org/display/DDW17/BathroomsTotalInteger+Field): "The simple sum of the number of bathrooms. For example for a property with two Full Bathrooms and one Half Bathroom, the Bathrooms Total Integer will be 3.". See also numberOfRooms.
The total integer number of bedrooms in a some Accommodation, ApartmentComplex or FloorPlan.
The quantity of the given bed type available in the HotelRoom, Suite, House, or Apartment.
The number of credits or units awarded by a Course or required to complete an EducationalOccupationalProgram.
The number of doors.\n\nTypical unit code(s): C62.
The number of employees in an organization, e.g. business.
The number of episodes in this season or series.
The total number of forward gears available for the transmission system of the vehicle.\n\nTypical unit code(s): C62.
Number of full bathrooms - The total number of full and ¾ bathrooms in an Accommodation. This corresponds to the [BathroomsFull field in RESO](https://ddwiki.reso.org/display/DDW17/BathroomsFull+Field).
The number of items in an ItemList. Note that some descriptions might not fully describe all items in a list (e.g., multi-page pagination); in such cases, the numberOfItems would be for the entire list.
The number of payments contractually required at origination to repay the loan. For monthly paying loans this is the number of months from the contractual first payment date to the maturity date.
Number of partial bathrooms - The total number of half and ¼ bathrooms in an Accommodation. This corresponds to the [BathroomsPartial field in RESO](https://ddwiki.reso.org/display/DDW17/BathroomsPartial+Field).
Indicate how many people can play this game (minimum, maximum, or range).
The number of owners of the vehicle, including the current one.\n\nTypical unit code(s): C62.
The number of rooms (excluding bathrooms and closets) of the accommodation or lodging business. Typical unit code(s): ROM for room or C62 for no unit. The type of room can be put in the unitText property of the QuantitativeValue.
A number associated with a role in an organization, for example, the number on an athlete's jersey.
Nutrition information about the recipe or menu item.
The observationAbout property identifies an entity, often a Place, associated with an Observation.
The observationDate of an Observation.
The length of time an Observation took place over. The format follows `P[0-9]*[Y|M|D|h|m|s]`. For example, P1Y is Period 1 Year, P3M is Period 3 Months, P3h is Period 3 hours.
The allowed total occupancy for the accommodation in persons (including infants etc). For individual accommodations, this is not necessarily the legal maximum but defines the permitted usage as per the contractual agreement (e.g. a double room used by a single person). Typical unit code(s): C62 for person.
The region/country for which this occupational description is appropriate. Note that educational requirements and qualifications can vary between jurisdictions.
A category describing the job, preferably using a term from a taxonomy such as [BLS O*NET-SOC](http://www.onetcenter.org/taxonomy.html), [ISCO-08](https://www.ilo.org/public/english/bureau/stat/isco/isco08/) or similar, with the property repeated for each applicable value. Ideally the taxonomy should be identified, and both the textual label and formal code for the category should be provided.\n Note: for historical reasons, any textual label and formal code provided as a literal may be assumed to be from O*NET-SOC.
A description of the qualification, award, certificate, diploma or other occupational credential awarded as a consequence of successful completion of this course or program.
Whether prescriptions can be delivered by mail.
The general opening hours for a business. Opening hours can be specified as a weekly time range, starting with days, then times per day. Multiple days can be listed with commas ',' separating each day. Day or time ranges are specified using a hyphen '-'.\n\n* Days are specified using the following two-letter combinations: ```Mo```, ```Tu```, ```We```, ```Th```, ```Fr```, ```Sa```, ```Su```.\n* Times are specified using 24:00 format. For example, 3pm is specified as ```15:00```, 10am as ```10:00```. \n* Here is an example: Tuesdays and Thursdays 4-8pm .\n* If a business is open 7 days a week, then it can be specified as Monday through Sunday, all day .
The opening hour of the place or service on the given day(s) of the week.
Operating systems supported (Windows 7, OS X 10.6, Android 1.6).
A sub property of participant. The opponent on this action.
A sub property of object. The options subject to this action.
The delivery of the parcel related to this order or order item.
The number of the item ordered. If the property is not set, assume the quantity is one.
Describes, in a MediaReview when dealing with DecontextualizedContent, background information that can contribute to better interpretation of the MediaObject.
Link to the page containing an original version of the content, or directly to an online copy of the original MediaObject content, e.g. video file.
The vasculature the lymphatic structure originates, or afferents, from.
Any information related to overdose on a drug, including signs or symptoms, treatments, contact information for emergency response.
The date and time of obtaining the product.
The date and time of giving up ownership on the product.
For an Organization (often but not necessarily a NewsMediaOrganization), a description of organizational ownership structure; funding and grants. In a news/media setting, this is with particular reference to editorial independence. Note that the funder is also available and can be used to make basic funder information machine-readable.
Products owned by the organization or person.
The page on which the work ends; for example "138" or "xvi".
The page on which the work starts; for example "135" or "xiii".
Any description of pages that is not separated into pageStart and pageEnd; for example, "1-6, 9, 55" or "10-12, 46-49".
The parent of a question, answer or item in general. Typically used for Q/A discussion threads e.g. a chain of comments with the first comment being an Article or other CreativeWork. See also comment which points from something to a comment about it.
A broadcast service to which the broadcast service may belong to such as regional variations of a national channel.
The order is being paid as part of the referenced Invoice.
The overall order the items in this delivery were included in.
The season to which this episode belongs.
The anatomical or organ system that this structure is part of.
The TV series to which this episode or season belongs.
The series to which this episode or season belongs.
Number of people the reservation should accommodate.
The priority status assigned to a passenger for security or boarding (e.g. FastTrack or Priority).
The passenger's sequence number as assigned by the airline.
Changes in the normal mechanical, physical, and biochemical functions that are associated with this activity or condition.
A pattern that something has, for example 'polka dot', 'striped', 'Canadian flag'. Values are typically expressed as text, although links to controlled value schemes are also supported.
The permitted weight of passengers and cargo, EXCLUDING the weight of the empty vehicle.\n\nTypical unit code(s): KGM for kilogram, LBR for pound\n\n* Note 1: Many databases specify the permitted TOTAL weight instead, which is the sum of weight and payload\n* Note 2: You can indicate additional information in the name of the QuantitativeValue node.\n* Note 3: You may also link to a QualitativeValue node that provides additional information using valueReference.\n* Note 4: Note that you can use minValue and maxValue to indicate ranges.
Cash, Credit Card, Cryptocurrency, Local Exchange Tradings System, etc.
The name of the credit card or other method of payment for the order.
An identifier for the method of payment used (e.g. the last 4 digits of the credit card).
The status of payment; whether the invoice has been paid or not.
The individual who draws the primary narrative artwork.
Event that this person is a performer or participant in.
The main performer or performers of the event—for example, a presenter, musician, or actor.
A performer at the event—for example, a presenter, musician, musical group or actor.
The type of permission granted the person, organization, or audience.
Permission(s) required to run the app (for example, a mobile app may require full internet access or may run only on wifi).
Indications regarding the permitted usage of the accommodation.
Indicates whether pets are allowed to enter the accommodation or lodging business. More detailed information can be put in a text value.
Representation of a text textValue using the specified speechToTextMarkup. For example the city name of Houston in IPA: /ËˆhjuËstÉ™n/.
A description of the types of physical activity associated with the job. Defined terms such as those in O*net may be used, but note that there is no way to specify the level of ability as well as its nature when using a defined term.
Specific physiologic benefits associated to the plan.
Where a taxi will pick up a passenger or a rental car can be picked up.
When a taxi will pick up a passenger or a rental car can be picked up.
Indicates whether this game is multi-player, co-op or single-player. The game can be marked as multi-player, co-op and single-player at the same time.
Player type required—for example, Flash or Silverlight.
A polygon is the area enclosed by a point-to-point path for which the starting and ending points are the same. A polygon is expressed as a series of four or more space delimited points where the first and final points are identical.
Indicates the populationType common to all members of a StatisticalPopulation or all cases within the scope of a StatisticalVariable.
Provides positive considerations regarding something, for example product highlights or (alongside negativeNotes) pro/con lists for reviews. In the case of a Review, the property describes the itemReviewed from the perspective of the review; in the case of a Product, the product itself is being described. The property values can be expressed either as unstructured text (repeated as necessary), or if ordered, as a list (in which case the most positive is at the beginning of the list).
A possible unexpected and unfavorable evolution of a medical condition. Complications may include worsening of the signs or symptoms of the disease, extension of the condition to other organ systems, etc.
A possible treatment to address this condition, sign or symptom.
The post office box number for PO box addresses.
A description of the postoperative procedures, care, and/or followups for this device.
First postal code in a range (included).
Last postal code in the range (included). Needs to be after postalCodeBegin.
A defined range of postal codes indicated by a common textual prefix. Used for non-numeric systems such as UK.
Indicates a potential Action, which describes an idealized action in which this thing would play an 'object' role.
Intended use of the BioChemEntity by humans.
A MedicalOrganization where the IndividualPhysician practices.
A description of the workup, testing, and other preparations required before implanting this device.
A pointer from a previous, often discontinued variant of the product to its newer variant.
Any precaution, guidance, contraindication, etc. related to this drug's use during pregnancy.
The length of time it takes to prepare the items to be used in instructions or a direction, in [ISO 8601 duration format](http://en.wikipedia.org/wiki/ISO_8601).
Typical preparation that a patient must undergo before having the procedure performed.
Link to prescribing information for the drug.
Indicates the status of drug prescription, e.g. local catalogs classifications or whether the drug is available by prescription or over-the-counter, etc.
A link to the ListItem that precedes the current one.
Used in conjunction with eventStatus for rescheduled or cancelled events. This property contains the previously scheduled start date. For rescheduled events, the startDate property should be used for the newly scheduled start date. In the (rare) case of an event that has been postponed and rescheduled multiple times, this field may be repeated.
The offer price of a product, or of a price component when attached to PriceSpecification and its subtypes.\n\nUsage guidelines:\n\n* Use the priceCurrency property (with standard formats: [ISO 4217 currency format](http://en.wikipedia.org/wiki/ISO_4217), e.g. "USD"; [Ticker symbol](https://en.wikipedia.org/wiki/List_of_cryptocurrencies) for cryptocurrencies, e.g. "BTC"; well known names for [Local Exchange Trading Systems](https://en.wikipedia.org/wiki/Local_exchange_trading_system) (LETS) and other currency types, e.g. "Ithaca HOUR") instead of including [ambiguous symbols](http://en.wikipedia.org/wiki/Dollar_sign#Currencies_that_use_the_dollar_or_peso_sign) such as '$' in the value.\n* Use '.' (Unicode 'FULL STOP' (U+002E)) rather than ',' to indicate a decimal point. Avoid using these symbols as a readability separator.\n* Note that both [RDFa](http://www.w3.org/TR/xhtml-rdfa-primer/#using-the-content-attribute) and Microdata syntax allow the use of a "content=" attribute for publishing simple machine-readable values alongside more human-friendly formatting.\n* Use values from 0123456789 (Unicode 'DIGIT ZERO' (U+0030) to 'DIGIT NINE' (U+0039)) rather than superficially similar Unicode symbols.
This property links to all UnitPriceSpecification nodes that apply in parallel for the CompoundPriceSpecification node.
Identifies a price component (for example, a line item on an invoice), part of the total price for an offer.
The currency of the price, or a price component when attached to PriceSpecification and its subtypes.\n\nUse standard formats: [ISO 4217 currency format](http://en.wikipedia.org/wiki/ISO_4217), e.g. "USD"; [Ticker symbol](https://en.wikipedia.org/wiki/List_of_cryptocurrencies) for cryptocurrencies, e.g. "BTC"; well known names for [Local Exchange Trading Systems](https://en.wikipedia.org/wiki/Local_exchange_trading_system) (LETS) and other currency types, e.g. "Ithaca HOUR".
The price range of the business, for example ```$$$```.
One or more detailed price specifications, indicating the unit price and delivery or payment charges.
Defines the type of a price specified for an offered product, for example a list price, a (temporary) sale price or a manufacturer suggested retail price. If multiple prices are specified for an offer the priceType property can be used to identify the type of each such specified price. The value of priceType can be specified as a value from enumeration PriceTypeEnumeration or as a free form text string for price types that are not already predefined in PriceTypeEnumeration.
The date after which the price is no longer available.
A preventative therapy used to prevent an initial occurrence of the medical condition, such as vaccination.
The number of the column in which the NewsArticle appears in the print edition.
The edition of the print product in which the NewsArticle appears.
If this NewsArticle appears in print, this field indicates the name of the page on which the article is found. Please note that this field is intended for the exact page name (e.g. A5, B18).
If this NewsArticle appears in print, this field indicates the print section in which the article appeared.
A description of the procedure involved in setting up, using, and/or installing the device.
The type of procedure, for example Surgical, Noninvasive, or Percutaneous.
Estimated processing time for the service using this channel.
Processor architecture required to run the application (e.g. IA64).
The person or organization who produced the work (e.g. music album, movie, TV/radio series etc.).
The tangible thing generated by the service, e.g. a passport, permit, etc.
Indicates a textual identifier for a ProductGroup.
The product identifier, such as ISBN. For example: ``` meta itemprop="productID" content="isbn:123-456-789" ```.
The product or service this support contact point is related to (such as product support for a particular product line). This can be a specific product or product line (e.g. "iPhone") or a general category of products or services (e.g. "smartphones").
The production company or studio responsible for the item, e.g. series, video game, episode etc.
The date of production of the item, e.g. vehicle.
Proficiency needed for this content; expected values: 'Beginner', 'Expert'.
The [MemberProgram](https://schema.org/MemberProgram) associated with a [ProgramMembership](https://schema.org/ProgramMembership).
Any membership in a frequent flyer, hotel loyalty program, etc. being applied to the reservation.
The program providing the membership. It is preferable to use [:program](https://schema.org/program) instead.
Prerequisites for enrolling in the program.
The type of educational or occupational program. For example, classroom, internship, alternance, etc.
Indicates whether API is managed or unmanaged.
A commonly used identifier for the characteristic represented by the property, e.g. a manufacturer or a standard code for a property. propertyID can be (1) a prefixed string, mainly meant to be used with standards for product properties; (2) a site-specific, non-prefixed string (e.g. the primary key of the property or the vendor-specific ID of the property), or (3) a URL indicating the type of the property, either pointing to an external vocabulary, or a Web resource that describes the property (e.g. a glossary entry). Standards bodies should promote a standard prefix for the identifiers of properties from their standards.
Proprietary name given to the diet plan, typically by its originator or creator.
Indicates the mobility of a provided service (e.g. 'static', 'dynamic').
A flag to signal that the Place is open to public visitors. If this property is omitted there is no assumed default boolean value.
Information about public transport closures.
A publication event associated with the item.
The type of the medical article, taken from the US NLM MeSH publication type catalog. See also [MeSH documentation](http://www.nlm.nih.gov/mesh/pubtypes.html).
An agent associated with the publication event.
A broadcast service associated with the publication event.
The publishing division which published the comic.
The date the item, e.g. vehicle, was purchased by the current owner.
Specific qualifications required for this role or Occupation.
Guidelines about quarantine rules, e.g. in the context of a pandemic.
A sub property of instrument. The query used on this action.
The task that a player-controlled character, or group of characters may complete in order to gain a reward.
A short explanation (e.g. one to two sentences) providing background context and other information that led to the conclusion expressed in the rating. This is particularly applicable to ratings associated with "fact check" markup using ClaimReview.
The rating for the content.\n\nUsage guidelines:\n\n* Use values from 0123456789 (Unicode 'DIGIT ZERO' (U+0030) to 'DIGIT NINE' (U+0039)) rather than superficially similar Unicode symbols.\n* Use '.' (Unicode 'FULL STOP' (U+002E)) rather than ',' to indicate a decimal point. Avoid using these symbols as a readability separator.
A person who reads (performs) the audiobook.
Whether or not a property is mutable. Default is false. Specifying this for a property that also has a value makes it act similar to a "hidden" input in an HTML form.
A sub property of participant. The real estate agent involved in the action.
A sub property of instrument. The recipe/instructions used to perform the action.
The category of the recipe—for example, appetizer, entree, etc.
The cuisine of the recipe (for example, French or Ethiopian).
A step in making the recipe, in the form of a single item (document, video, etc.) or an ordered list with HowToStep and/or HowToSection items.
A single step item (as HowToStep, text, document, video, etc.) or a HowToSection.
The quantity produced by the recipe (for example, number of people served, number of servings, etc).
The quantity that results by performing instructions. For example, a paper airplane, 10 personalized candles.
An organization that acknowledges the validity, value or utility of a credential. Note: recognition may include a process of quality assurance or accreditation.
If applicable, the organization that officially recognizes this entity as part of its endorsed system of medicine.
Strength of the guideline's recommendation (e.g. 'class I').
The only way you get the money back in the event of default is the security. Recourse is where you still have the opportunity to go back to the borrower for the rest of the money.
The reference quantity for which a certain price applies, e.g. 1 EUR per 4 kWh of electricity. This property is a replacement for unitOfMeasurement for the advanced cases where the price does not relate to a standard unit.
The Order(s) related to this Invoice. One or more Orders may be combined into a single Invoice.
The anatomical or organ system drained by this vessel; generally refers to a specific part of an organ.
The regions where the media is allowed. If not specified, then it's assumed to be allowed everywhere. Specify the countries in [ISO 3166 format](http://en.wikipedia.org/wiki/ISO_3166).
Anatomical systems or structures that relate to the superficial anatomy.
A medical condition associated with this anatomy.
Any other drug related to this one, for example commonly-prescribed alternatives.
A link related to this web page, for example to other related web pages.
Related anatomical structure(s) that are not part of the system but relate or connect to it, such as vascular bundles associated with an organ system.
A medical therapy related to this anatomy.
The release date of a product or product model. This can be used to distinguish the exact variant of a product.
Description of what changed in this version.
The place and time the release was issued, expressed as a PublicationEvent.
If applicable, a medical specialty in which this entity is relevant.
The number of attendee places for an event that remain unallocated.
Whether the terms for payment of interest can be renegotiated during the life of the loan.
Defines the number of times a recurring Event will take place.
Defines the frequency at which Events will occur according to a schedule Schedule. The intervals between events should be defined as a Duration of time.
How often the dose is taken, e.g. 'daily'.
Number of times one should repeat the activity.
A sub property of object. The object that is being replaced.
A sub property of object. The object that replaces.
The URL at which a reply may be posted to the specified UserComment.
The number or other unique designator assigned to a Report by the publishing organization.
Indicates whether this image is representative of the content of the page.
Assets required to secure loan or credit repayments. It may take form of third party pledge, goods, financial instruments (cash, securities, etc.)
Audiences defined by a person's maximum age.
Audiences defined by a person's minimum age.
Component dependency requirements for application. This includes runtime environments and shared libraries that are not included in the application distribution package, but required to run the application (examples: DirectX, Java or .NET runtime).
Indicates if use of the media require a subscription (either paid or free). Allowed values are ```true``` or ```false``` (note that an earlier version had 'yes', 'no').
The thing -- flight, event, restaurant, etc. being reserved.
A unique identifier for the reservation.
A ticket associated with the reservation.
Responsibilities associated with this role or Occupation.
How often one should break from the activity.
Use MonetaryAmount to specify a fixed restocking fee for product returns, or use Number to specify a percentage of the product price paid by the customer.
A sub property of result. The Comment created or sent as a result of this action.
The result produced in the action. E.g. John wrote *a book*.
A sub property of result. The review that resulted in the performing of the action.
The type of return fees for purchased products (for any return reason).
The method (from an enumeration) by which the customer obtains a return shipping label for a product returned for any reason.
The type of return method offered, specified from an enumeration.
Specifies an applicable return policy (from an enumeration).
The country where the product has to be sent to for returns, for example "Ireland" using the name property of Country. You can also provide the two-letter [ISO 3166-1 alpha-2 country code](http://en.wikipedia.org/wiki/ISO_3166-1). Note that this can be different from the country where the product was originally shipped from or sent to.
Amount of shipping costs for product returns (for any reason). Applicable when property returnFees equals ReturnShippingFees.
This Review or Rating is relevant to this part or facet of the itemReviewed.
The rating given in this review. Note that reviews can themselves be rated. The ```reviewRating``` applies to rating given by the review. The aggregateRating property applies to the review itself, as a creative work.
People or organizations that have reviewed the content on this web page for accuracy and/or completeness.
A modifiable or non-modifiable factor that increases the risk of a patient contracting this condition, e.g. age, coexisting condition.
Specific physiologic risks associated to the diet plan.
The permitted total weight of cargo and installations (e.g. a roof rack) on top of the vehicle.\n\nTypical unit code(s): KGM for kilogram, LBR for pound\n\n* Note 1: You can indicate additional information in the name of the QuantitativeValue node.\n* Note 2: You may also link to a QualitativeValue node that provides additional information using valueReference\n* Note 3: Note that you can use minValue and maxValue to indicate ranges.
The response (yes, no, maybe) to the RSVP.
The vasculature the lymphatic structure runs, or efferents, to.
Runtime platform or script interpreter dependencies (example: Java v1, Python 2.3, .NET Framework 3.0).
Any potential safety concern associated with the supplement. May include interactions with other drugs and foods, pregnancy, breastfeeding, known adverse reactions, and documented efficacy of the supplement.
The currency (coded using [ISO 4217](http://en.wikipedia.org/wiki/ISO_4217)) used for the main salary information in this job posting or for this employee.
The expected salary upon completing the training.
What type of code sample: full (compile ready) solution, code snippet, inline code, scripts, template.
Indicates the timezone for which the time(s) indicated in the Schedule are given. The value provided should be among those listed in the IANA Time Zone Database.
The date the invoice is scheduled to be paid.
Indicates (by URL or string) a particular version of a schema used in some CreativeWork. This property was created primarily to indicate the use of a specific schema.org release, e.g. ```10.0``` as a simple string, or more explicitly via URL, ```https://schema.org/docs/releases.html#v10.0```. There may be situations in which other schemas might usefully be referenced this way, e.g. ```http://dublincore.org/specifications/dublin-core/dces/1999-07-02/``` but this has not been carefully explored in the community.
The number of screens in the movie theater.
A link to a screenshot image of the app.
Indicates the date on which the current structured data was generated / published. Typically used alongside sdPublisher.
A license document that applies to this structured data, typically indicated by URL.
Indicates the party responsible for generating and publishing the current structured data markup, typically in cases where the structured data is derived automatically from existing published content but published on a different site. For example, student projects and open data initiatives often re-publish existing content with more explicitly structured metadata. The sdPublisher property helps make such practices more explicit.
Position of the season within an ordered group of seasons.
The location of the reserved seat (e.g., 27).
The row location of the reserved seat (e.g., B).
The section location of the reserved seat (e.g. Orchestra).
The number of persons that can be seated (e.g. in a vehicle), both in terms of the physical space available, and in terms of limitations set by law.\n\nTypical unit code(s): C62 for persons.
A preventative therapy used to prevent reoccurrence of the medical condition after an initial episode of the condition.
A description of any security clearance requirements of the job.
The type of security screening the passenger is subject to.
A pointer to products or services sought by the organization or person (demand).
A sub property of participant. The participant who is at the sending end of the action.
A description of any sensory requirements and levels necessary to function on the job, including hearing and vision. Defined terms such as those in O*net may be used, but note that there is no way to specify the level of ability as well as its nature when using a defined term.
The neurological pathway extension that inputs and sends information to the brain or spinal cord.
A possible serious complication and/or serious side effect of this therapy. Serious adverse outcomes include those that are life-threatening; result in death, disability, or permanent damage; require hospitalization or prolong existing hospitalization; cause congenital anomalies or birth defects; or jeopardize the patient and may require medical or surgical intervention to prevent one of the outcomes in this definition.
An intended audience, i.e. a group for whom something was created.
The location (e.g. civic structure, local business, etc.) where a person can go to access the service.
The operating organization, if different from the provider. This enables the representation of services that are provided by an organization, but operated by another organization like a subcontractor.
The phone number to use to access the service.
The address for accessing the service by mail.
The number to access the service by text message.
The type of service being offered, e.g. veterans' benefits, emergency relief, etc.
The serving size, in terms of the number of volume or mass.
The [SHA-2](https://en.wikipedia.org/wiki/SHA-2) SHA256 hash of the content of the item. For example, a zero-length input has value 'e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855'.
A CreativeWork such as an image, video, or audio clip shared as part of this posting.
indicates (possibly multiple) shipping destinations. These can be defined in several ways, e.g. postalCode ranges.
Indicates information about the shipping policies and options associated with an Offer.
Label to match an OfferShippingDetails with a ShippingRateSettings (within the context of a shippingSettingsLink cross-reference).
Indicates the origin of a shipment, i.e. where it should be coming from.
The shipping rate is the cost of shipping to the specified destination. Typically, the maxValue and currency values (of the MonetaryAmount) are most appropriate.
Link to a page containing ShippingRateSettings and DeliveryTimeSettings details.
A sign or symptom of this condition. Signs are objective or physically observable manifestations of the medical condition while symptoms are the subjective experience of the medical condition.
The significance associated with the superficial anatomy; as an example, how characteristics of the superficial anatomy can suggest underlying medical conditions or courses of treatment.
The most significant URLs on the page. Typically, these are the non-navigation links that are clicked on the most.
One of the more significant URLs on the page. Typically, these are the non-navigation links that are clicked on the most.
A standardized size of a product or creative work, specified either through a simple textual string (for example 'XL', '32Wx34L'), a QuantitativeValue with a unitCode, or a comprehensive and structured SizeSpecification; in other cases, the width, height, depth and weight properties may be more applicable.
The size group (also known as "size type") for a product's size. Size groups are common in the fashion industry to define size segments and suggested audiences for wearable products. Multiple values can be combined, for example "men's big and tall", "petite maternity" or "regular".
The size system used to identify a product's size. Typically either a standard (for example, "GS1" or "ISO-EN13402"), country code (for example "US" or "JP"), or a measuring system (for example "Metric" or "Imperial").
A statement of knowledge, skill, ability, task or any other assertion expressing a competency that is desired or required to fulfill this role or to work in this occupation.
The Stock Keeping Unit (SKU), i.e. a merchant-specific identifier for a product or service, or the product to which the offer refers.
A slogan or motto associated with the item.
A specification in form of a line notation for describing the structure of chemical species using short ASCII strings. Double bond stereochemistry \ indicators may need to be escaped in the string in formats where the backslash is an escape character.
Indicates whether it is allowed to smoke in the place, e.g. in the restaurant, hotel or hotel room.
Additional content for a software application.
The Organization on whose behalf the creator was working.
The neurological pathway that originates the neurons.
Indicates sections of a Web page that are particularly 'speakable' in the sense of being highlighted as being especially appropriate for text-to-speech conversion. Other sections of a page may also be usefully spoken in particular circumstances; the 'speakable' property serves to indicate the parts most likely to be generally useful for speech. The *speakable* property can be repeated an arbitrary number of times, with three kinds of possible 'content-locator' values: 1.) *id-value* URL references - uses *id-value* of an element in the page being annotated. The simplest use of *speakable* has (potentially relative) URL values, referencing identified sections of the document concerned. 2.) CSS Selectors - addresses content in the annotated page, e.g. via class attribute. Use the cssSelector property. 3.) XPaths - addresses content via XPaths (assuming an XML view of the content). Use the xpath property. For more sophisticated markup of speakable sections beyond simple ID references, either CSS selectors or XPath expressions to pick out document section(s) as speakable. For this we define a supporting type, SpeakableSpecification which is defined to be a possible value of the *speakable* property.
Any special commitments associated with this job posting. Valid entries include VeteranCommit, MilitarySpouseCommit, etc.
The special opening hours of a certain place.\n\nUse this to explicitly override general opening hours brought in scope by openingHoursSpecification or openingHours.
One of the domain specialities to which this web page's content applies.
Form of markup used. eg. [SSML](https://www.w3.org/TR/speech-synthesis11) or [IPA](https://www.wikidata.org/wiki/Property:P898).
The speed range of the vehicle. If the vehicle is powered by an engine, the upper limit of the speed range (indicated by maxValue) should be the maximum speed achievable under regular conditions.\n\nTypical unit code(s): KMH for km/h, HM for mile per hour (0.447 04 m/s), KNT for knot\n\n*Note 1: Use minValue and maxValue to indicate the range. Typically, the minimal value is zero.\n* Note 2: There are many different ways of measuring the speed range. You can link to information about how the given value has been determined using the valueReference property.
The (e.g. fictional) character, Person or Organization to whom the quotation is attributed within the containing CreativeWork.
A sub property of location. The sports activity location where this action occurred.
A sub property of location. The sports event where this action occurred.
A sub property of participant. The sports team that participated on this action.
The stage of the condition, if applicable.
The stage represented as a number, e.g. 3.
An official rating for a lodging business or food establishment, e.g. from national associations or standards bodies. Use the author property to indicate the rating organization, e.g. as an Organization with name such as (e.g. HOTREC, DEHOGA, WHR, or Hotelstars).
The start date and time of the item (in [ISO 8601 date format](http://en.wikipedia.org/wiki/ISO_8601)).
The start time of the clip expressed as the number of seconds from the beginning of the work.
The startTime of something. For a reserved event or service (e.g. FoodEstablishmentReservation), the time that it is expected to start. For actions that span a period of time, when the action was performed. E.g. John wrote a book from *January* to December. For media, including audio and video, it's the time offset of the start of a clip within a larger file.\n\nNote that Event uses startDate/endDate instead of startTime/endTime, even when describing dates with times. This situation may be clarified in future revisions.
Indicates the kind of statistic represented by a StatisticalVariable, e.g. mean, count etc. The value of statType is a property, either from within Schema.org (e.g. median, marginOfError, maxValue, minValue) or from other compatible (e.g. RDF) systems such as DataCommons.org or Wikidata.org.
The position of the steering wheel or similar device (mostly for cars).
The stepValue attribute indicates the granularity that is expected (and required) of the value in a PropertyValueSpecification.
A single step item (as HowToStep, text, document, video, etc.) or a HowToSection (originally misnamed 'steps'; 'step' is preferred).
Storage requirements (free space required).
The street address. For example, 1600 Amphitheatre Pkwy.
The units of an active ingredient's strength, e.g. mg.
The value of an active ingredient's strength, e.g. 325.
The name given to how bone physically connects to each other.
A medical study or trial related to this entity.
Specifics about the observational study design (enumerated).
The location in which the study is taking/took place.
A subject of the study, i.e. one of the medical conditions, therapies, devices, drugs, etc. investigated by the study.
Events that are a part of this event. For example, a conference event includes many presentations, each subEvents of the conference.
An Event that is part of this event. For example, a conference event includes many presentations, each of which is a subEvent of the conference.
The individual reservations included in the package. Typically a repeated property.
Component (sub-)structure(s) that comprise this anatomical structure.
Languages in which subtitles/captions are available, in [IETF BCP 47 standard format](http://tools.ietf.org/html/bcp47).
A pointer from a newer variant of a product to its previous, often discontinued predecessor.
The age or age range for the intended audience or person, for example 3-12 months for infants, 1-5 years for toddlers.
The suggested gender of the intended person or audience, for example "male", "female", or "unisex".
Maximum recommended age in years for the audience or user.
A suggested range of body measurements for the intended audience or person, for example inseam between 32 and 34 inches or height between 170 and 190 cm. Typically found on a size chart for wearable products.
Minimum recommended age in years for the audience or user.
Indicates a dietary restriction or guideline for which this recipe or menu item is suitable, e.g. diabetic, halal etc.
The area to which the artery supplies blood.
Supporting data for a SoftwareApplication.
A material used as a surface in some artwork, e.g. Canvas, Paper, Wood, Board, etc.
The supporting materials for the artwork, e.g. Canvas, Paper, Wood, Board, etc.
Indicates (typically several) Syllabus entities that lay out what each section of the overall course will cover.
Indicates a target EntryPoint, or url, for an Action.
The description of a node in an established educational framework.
The name of a node in an established educational framework.
Type of app development: phone, Metro style, desktop, XBox, etc.
Characteristics of the population for which this is intended, or which typically uses it, e.g. 'adults'.
Target Operating System / Product to which the code applies. If applies to several versions, just the product name can be used.
The URL of a node in an established educational framework.
The Tax / Fiscal ID of the organization or person, e.g. the TIN in the US or the CIF/NIF in Spain.
The taxonomic rank of this taxon given preferably as a URI from a controlled vocabulary – typically the ranks from TDWG TaxonRank ontology or equivalent Wikidata URIs.
The taxonomic grouping of the organism that expresses, encodes, or in some way related to the BioChemEntity.
The item being described is intended to help a person learn the competency or learning outcome defined by the referenced term.
The "temporal" property can be used in cases where more specific properties (e.g. temporalCoverage, dateCreated, dateModified, datePublished) are not known to be appropriate.
The amount of time in a term as defined by the institution. A term is a length of time where students take one or more classes. Semesters and quarters are common units for term.
Human-readable terms of service documentation.
The number of times terms of study are offered per year. Semesters and quarters are common units for term. For example, if the student can only take 2 semesters for the program in one year, then termsPerYear should be 2.
The textual content of this CreativeWork.
A thumbnail image relevant to the Thing.
The exchange traded instrument associated with a Corporation object. The tickerSymbol is expressed as an exchange and an instrument name separated by a space character. For the exchange component of the tickerSymbol attribute, we recommend using the controlled vocabulary of Market Identifier Codes (MIC) specified in ISO 15022.
Reference to an asset (e.g., Barcode, QR code image or PDF) usable for entrance.
The time of day the program normally runs. For example, "evenings".
The expected length of time to complete the program if attending full-time.
The type of tissue sample required for the test.
An [EIDR](https://eidr.org/) (Entertainment Identifier Registry) identifier representing at the most general/abstract level, a work of film or television. For example, the motion picture known as "Ghostbusters" has a titleEIDR of "10.5240/7EC7-228A-510A-053E-CBB8-J". This title (or work) may have several variants, which EIDR calls "edits". See editEIDR. Since schema.org types like Movie, TVEpisode, TVSeason, and TVSeries can be used for both works and their multiple expressions, it is possible to use titleEIDR alone (for a general description), or alongside editEIDR for a more edit-specific description.
A sub property of location. The final location of the object or the agent after the action.
A sub property of recipient. The recipient who was directly sent the message.
A HyperTocEntry can have a tocContinuation indicated, which is another HyperTocEntry that would be the default next item to play or render.
Indicates a HyperTocEntry in a HyperToc.
The permitted vertical load (TWR) of a trailer attached to the vehicle. Also referred to as Tongue Load Rating (TLR) or Vertical Load Rating (VLR).\n\nTypical unit code(s): KGM for kilogram, LBR for pound\n\n* Note 1: You can indicate additional information in the name of the QuantitativeValue node.\n* Note 2: You may also link to a QualitativeValue node that provides additional information using valueReference.\n* Note 3: Note that you can use minValue and maxValue to indicate ranges.
A sub property of instrument. An object used (but not consumed) when performing instructions or a direction.
The torque (turning force) of the vehicle's engine.\n\nTypical unit code(s): NU for newton metre (N m), F17 for pound-force per foot, or F48 for pound-force per inch\n\n* Note 1: You can link to information about how the given value has been determined (e.g. reference RPM) using the valueReference property.\n* Note 2: You can use minValue and maxValue to indicate ranges.
The total number of students that have enrolled in the history of the course.
The number of positions open for this job posting. Use a positive integer. Do not use if the number of positions is unclear or not known.
The total price for the reservation or ticket, including applicable taxes, shipping, etc.\n\nUsage guidelines:\n\n* Use values from 0123456789 (Unicode 'DIGIT ZERO' (U+0030) to 'DIGIT NINE' (U+0039)) rather than superficially similar Unicode symbols.\n* Use '.' (Unicode 'FULL STOP' (U+002E)) rather than ',' to indicate a decimal point. Avoid using these symbols as a readability separator.
The total time required to perform instructions or a direction (including time to prepare the supplies), in [ISO 8601 duration format](http://en.wikipedia.org/wiki/ISO_8601).
A page providing information on how to book a tour of some Place, such as an Accommodation or ApartmentComplex in a real estate setting, as well as other kinds of tours as appropriate.
Attraction suitable for type(s) of tourist. E.g. children, visitors from a particular country, etc.
A music recording (track)—usually a single song.
A music recording (track)—usually a single song. If an ItemList is given, the list should contain items of type MusicRecording.
The trailer of a movie or TV/radio series, season, episode, etc.
The permitted weight of a trailer attached to the vehicle.\n\nTypical unit code(s): KGM for kilogram, LBR for pound\n* Note 1: You can indicate additional information in the name of the QuantitativeValue node.\n* Note 2: You may also link to a QualitativeValue node that provides additional information using valueReference.\n* Note 3: Note that you can use minValue and maxValue to indicate ranges.
The name of the train (e.g. The Orient Express).
The estimated salary earned while in the program.
If this MediaObject is an AudioObject or VideoObject, the transcript of that object.
The typical delay the order has been sent for delivery and the goods reach the final customer. Typical properties: minValue, maxValue, unitCode (d for DAY).
Label to match an OfferShippingDetails with a DeliveryTimeSettings (within the context of a shippingSettingsLink cross-reference).
Organization or person who adapts a creative work to different languages, regional differences and technical requirements of a target market, or that translates during some event.
How the disease spreads, either as a route or vector, for example 'direct contact', 'Aedes aegypti', etc.
Information about travel bans, e.g. in the context of a pandemic.
Specifics about the trial design (enumerated).
The anatomical or organ system that the vein flows into; a larger structure that the vein connects to.
The location of origin of the trip, prior to any destination(s).
The type of bed to which the BedDetail refers, i.e. the type of bed available in the quantity indicated by quantity.
The product that this structured value is referring to.
The typical expected age range, e.g. '7-9', '11-'.
The number of credits or units a full-time student would be expected to take in 1 term however 'term' is defined by the institution.
A medical test typically performed given this condition.
The person or organization the reservation or ticket is for.
The unit of measurement given using the UN/CEFACT Common Code (3 characters) or a URL. Other codes than the UN/CEFACT Common Code may be used with a prefix followed by a colon.
A string or text indicating the unit of measurement. Useful if you cannot provide a standard unit code for unitCode.
For an Organization (typically a NewsMediaOrganization), a statement about policy on use of unnamed sources and the decision process required.
Date (including time if available) when this media object was uploaded to this site.
The number of upvotes this question, answer or comment has received from the community.
An url template (RFC6570) that will be used to construct the target of the execution of the action.
A National Provider Identifier (NPI) is a unique 10-digit identification number issued to health care providers in the United States by the Centers for Medicare and Medicaid Services.
A condition the test is used to diagnose.
The number of interactions for the CreativeWork using the WebSite or SoftwareApplication.
The standard for interpreting the Plan ID. The preferred is "HIOS". See the Centers for Medicare & Medicaid Services for more details.
Text of an utterances (spoken words, lyrics etc.) that occurs at a certain section of a media object, represented as a HyperTocEntry.
The duration of validity of a permit or similar thing.
The membership program tier an Offer (or a PriceSpecification, OfferShippingDetails, or MerchantReturnPolicy under an Offer) is valid for.
The geographic area where the item is valid. Applies for example to a Permit, a Certification, or an EducationalOccupationalCredential.
The date after when the item is not valid. For example the end of an offer, salary period, or a period of opening hours.
The date when the item is no longer valid.
The value of a QuantitativeValue (including Observation) or property value node.\n\n* For QuantitativeValue and MonetaryAmount, the recommended type for values is 'Number'.\n* For PropertyValue, it can be 'Text', 'Number', 'Boolean', or 'StructuredValue'.\n* Use values from 0123456789 (Unicode 'DIGIT ZERO' (U+0030) to 'DIGIT NINE' (U+0039)) rather than superficially similar Unicode symbols.\n* Use '.' (Unicode 'FULL STOP' (U+002E)) rather than ',' to indicate a decimal point. Avoid using these symbols as a readability separator.
Specifies whether the applicable value-added tax (VAT) is included in the price specification or not.
Specifies the allowed range for number of characters in a literal value.
Specifies the minimum allowed range for number of characters in a literal value.
Indicates the name of the PropertyValueSpecification to be used in URL templates and form encoding in a manner analogous to HTML's input@name.
Specifies a regular expression for testing literal values according to the HTML spec.
A secondary value that provides additional information on the original value, e.g. a reference temperature or a type of measurement.
Whether the property must be filled in to complete the action. Default is false.
The variableMeasured property can indicate (repeated as necessary) the variables that are measured in some dataset, either described as text or as pairs of identifier and description using PropertyValue, or more explicitly as a StatisticalVariable.
A description of the variant cover for the issue, if the issue is a variant printing. For example, "Bryan Hitch Variant Cover" or "2nd Printing Variant".
Indicates the property or properties by which the variants in a ProductGroup vary, e.g. their size, color etc. Schema.org properties can be referenced by their short name e.g. "color"; terms defined elsewhere can be referenced with their URIs.
The Value-added Tax ID of the organization or person.
A short text indicating the configuration of the vehicle, e.g. '5dr hatchback ST 2.5 MT 225 hp' or 'limited edition'.
Information about the engine or engines of the vehicle.
The Vehicle Identification Number (VIN) is a unique serial number used by the automotive industry to identify individual motor vehicles.
The color or color combination of the interior of the vehicle.
The type or material of the interior of the vehicle (e.g. synthetic fabric, leather, wood, etc.). While most interior types are characterized by the material used, an interior type can also be based on vehicle usage or target audience.
The number of passengers that can be seated in the vehicle, both in terms of the physical space available, and in terms of limitations set by law.\n\nTypical unit code(s): C62 for persons.
Indicates whether the vehicle has been used for special purposes, like commercial rental, driving school, or as a taxi. The legislation in many countries requires this information to be revealed when offering a car for sale.
The type of component used for transmitting the power from a rotating power source to the wheels or other relevant component(s) ("gearbox" for cars).
'vendor' is an earlier term for 'seller'.
Disclosure about verification and fact-checking processes for a NewsMediaOrganization or other fact-checking Organization.
The type of screening or video broadcast used (e.g. IMAX, 3D, SD, HD, etc.).
Identifies the volume of publication or multi-part work; for example, "iii" or "2".
Any FDA or other warnings about the drug (text or URL).
The warranty promise(s) included in the offer.
The time when a passenger can check into the flight online.
The URL for a feed, e.g. associated with a podcast series, blog, or series of date-stamped updates. This is usually RSS or Atom.
The permitted total weight of the loaded vehicle, including passengers and cargo and the weight of the empty vehicle.\n\nTypical unit code(s): KGM for kilogram, LBR for pound\n\n* Note 1: You can indicate additional information in the name of the QuantitativeValue node.\n* Note 2: You may also link to a QualitativeValue node that provides additional information using valueReference.\n* Note 3: Note that you can use minValue and maxValue to indicate ranges.
The distance between the centers of the front and rear wheels.\n\nTypical unit code(s): CMT for centimeters, MTR for meters, INH for inches, FOT for foot/feet.
A sub property of participant. The winner of the action.
The number of words in the text of the Article.
The typical working hours for this job (e.g. 1st shift, night shift, 8am-5pm).
A contact location for a person's place of work.
A work performed in some event, for example a play performed in a TheaterEvent.
A work featured in some event, e.g. exhibited in an ExhibitionEvent. Specific subproperties are available for workPerformed (e.g. a play), or a workPresented (a Movie at a ScreeningEvent).
Quantitative measure of the physiologic output of the exercise; also referred to as energy expenditure.
Organizations that the person works for.
The lowest value allowed in this rating system.
An XPath, e.g. of a SpeakableSpecification or WebPageElement. In the latter case, multiple matches within a page can constitute a single conceptual "Web page element".
The year an Accommodation was constructed. This corresponds to the [YearBuilt field in RESO](https://ddwiki.reso.org/display/DDW17/YearBuilt+Field).
The size of the business in annual revenue.
An organization that the person is an alumni of.
Collection, [fonds](https://en.wikipedia.org/wiki/Fonds), or item held, kept or maintained by an ArchiveOrganization.
archiveheld
ArchiveOrganization that holds, keeps or maintains the ArchiveComponent.
holdingarchive
Closest child taxa of the taxon in question.
Closest parent taxon of the taxon in question.
The basic containment relation between a place and another that it contains.
A season that is part of the media series.
Another BioChemEntity encoded by this one.
Another BioChemEntity encoding by this one.
The CreativeWork encoded by this media object.
A creative work that this work is an example/instance/realization/derivation of.
Indicates something directly or indirectly funded or sponsored through a Grant. See also ownershipFundingInfo.
A Grant that directly or indirectly provide funding or sponsorship for this item. See also ownershipFundingInfo.
Video game which is played on this server.
The server on which it is possible to play the game.
Indicates a BioChemEntity that (in some sense) has this BioChemEntity as a part.
Indicates a BioChemEntity that is (in some sense) a part of this BioChemEntity.
A broadcast channel of a broadcast service.
The BroadcastService offered on this channel.
The member program this tier is a part of.
Indicates a Product that is a member of this ProductGroup (or ProductModel).
Indicates the kind of product that this is a variant of. In the case of ProductModel, this is a pointer (from a ProductModel) to a base product from which this product is a variant. It is safe to infer that the variant inherits all product features from the base model, unless defined locally. This is not transitive. In the case of a ProductGroup, the group description also serves as a template, representing a set of Products that vary on explicitly defined, specific dimensions only (so it defines both a set of variants, as well as which values distinguish amongst those variants). When used with ProductGroup, this property can apply to any Product included in the group.
An item being offered (or demanded). The transactional nature of the offer or demand is documented using businessFunction, e.g. sell, lease etc. While several common expected types are listed explicitly in this definition, others can be used. Using a second type, such as Product or a subtype of Product, can clarify the nature of the offer.
An offer to provide this item—for example, an offer to sell a product, rent the DVD of a movie, perform a service, or give away tickets to an event. Use businessFunction to indicate the kind of transaction offered, i.e. sell, lease, etc. This property can also be used to describe a Demand. While this property is listed as expected on a number of common types, it can be used in others. In that case, using a second type, such as Product or a subtype of Product, can clarify the nature of the offer.
Indicates a page (or other CreativeWork) for which this thing is the main entity being described. See [background notes](/docs/datamodel.html#mainEntityBackground) for details.
A pointer to products or services offered by the organization or person.
A pointer to the organization or person making the offer.
Identifies that this Trip is a subTrip of another Trip. For example Day 1, Day 2, etc. of a multi-day trip.
Identifies a Trip that is a subTrip of this Trip. For example Day 1, Day 2, etc. of a multi-day trip.
The composition this track is a recording of.
The Event where the CreativeWork was recorded. The CreativeWork may capture all or part of the event.
The CreativeWork that captured all or part of this Event.
A CreativeWork or Event about this Thing.
An event that this event is a part of. For example, a collection of individual music performances might each have a music festival as their superEvent.
The work that this work has been translated from. E.g. ç‰©ç§èµ·æº is a translationOf “On the Origin of Speciesâ€.
A work that is a translation of the content of this work. E.g. è¥¿éŠè¨˜ has an English workTranslation “Journey to the Westâ€, a German workTranslation “Monkeys Pilgerfahrtâ€ and a Vietnamese translation Tây du ký bình khảo.
Beynəlxalq Xronostratiqrafik Şkala
Taula Cronoestratigràfica Internacional
Mezinárodní Chronostratigrafická Tabulka
Internationale Chronostratigraphische Tabelle
Tabla Cronoestratigráfica Internacional
Nazioarteko Taula Kronoestratigrafikoa
Kansainvälinen Kronostratigrafinen Taulu
Charte Chronostratigraphique Internationale
Nemzetközi Időrétegtani Táblázat
Bagan Kronostratigrafi Internasional
Scala Cronostratigrafica Internazionale
国際年代層序表
국제지질연대층서표
Tarptautinė Chronostratigrafijos Skalė
Internationale Chronostratigrafische Tabel
Internasjonal Kronostratigrafisk Tabell
Międzynarodowa Tablica Chronostratygraficzna
Tabela Cronoestratigráfica Internacional
Международная Хроностратиграфическая Шкала
Medzinárodná Chronostratigrafická Tabuľka
Uluslararasi Kronostratigrafik Çizelge
国 际 年 代 地 层 表
Qlobal Standard Stratiqrafik Yaşlar (Global Standard Stratigraphic Ages – GSSA) tərəfindən əvvəl təyin edilmiş Arxey və Proterozoy eraları daxil olmaqla, Stratotip Kəsilişlərin Qlobal Sərhədləri və Nöqtələri (Global Boundary Stratotype Section and Points – GSSP) tərəfindən təyin edilən bütün geoxronoloji vahidlərinin alt sərhədləri daimi dəqiqləşdirilir. Təsdiq edilmiş Yarımşöbələr / Yarımepoxalar Ü/G (Üst/Gec), O (Orta) və A/E (Alt/Erkən) olaraq qısaldılmışdır. Kursiv şriftlər qeyri-rəsmi vahidləri və adsız vahidlər üçün istifadə olunan müvəqqəti əvəzediciləri işarələyir. Əvvəlki versiyalar və təsdiqlənmiş GSSP-lər haqqında ətraflı məlumat http://www.stratigraphy.org saytında mövcuddur. Şkalanın keçidi aşağıda göstərilib. Sərhədlərin geoxronoloji yaşları daimi dəqiqləşdirilir və Fanerozoy ilə Ediakaranın bölgü vahidlərini təsdiq etmir, bunu yalnız GSSP edə bilər. Fanerozoyda GSSP tərəfindən təsdiqlənməyən və ya hesablanmış geoxronoloji dəyərləri olmayan sərhədlər üçün təxmini ədəd (~) göstərilir. Yaş dəyərlərinin əksəriyyəti “A Geologic Time Scale 2020”-dən (Gradstein et al., 2020) götürülüb, lakin bəzi yaş vahidləri münasib altkomissiyaların (Timescale Calibration subcommission, ICS subcommissions) tövsiyəsi ilə fərqlənir. Bu yaş vahidləri BSK (ICS) heyəti tərəfindən cari konsensus kimi təsdiqlənmişdir.
Els límits inferiors de les unitats de tots els rangs es troben actualment en procés de ser definits com a Estratotips Globals de Límit (GSSP - Global Boundary Stratotype Section and Point), incloses les de l'Arqueà i el Proterozoic que, per convenció, havien estat definits cronomètricament segons edats numèriques absolutes (GSSA-Global Standard Stratigraphic Ages). Hom pot trobar la taula original i la informació detallada sobre els GSSP ratificats a http://www.stratigraphy.org. Les edats numèriques (Ma) estan subjectes a revisió i no defineixen unitats en el Fanerozoic ni en I’Ediacarià. Això només ho fan els GSSP. Pel que fa als límits d'aquelles unitats del Fanerozoic que encara no tenen un GSSP ratificat, o dels quals no es disposa d'una edat numèrica acotada, la taula dona una edat numèrica aproximada (~). Les Subsèries/Subèpoques ratificades s’abrevien com S/T (Superior/Tardà), M (Mitjà) i I/P (Inferior/Primerenc). Les edats numèriques de tots els sistemes, excepte el Quaternari, el Paleogen superior, el Cretaci, el Juràssic, el Triàsic, el Permià i el Precambrià provenen de “A Geologic Time Scale 2012” de Gradstein et al. (2012). Les del Quaternari, Paleogen superior, Cretaci, Juràssic, Triàsic, Permià, Cambrià i Precambrià són aportacions originals de les subcomissions respectives de la ICS (Int. Commission on Stratigraphy).
Postupně se pracuje na tom, aby všechny jednotky byly definovány svými spodními hranicemi na globálních stratotypech (GSSP - Global Boundary Stratotype Section and Point). To platí i pro jednotky archaika a proterozoika, dosud definované globálním standardním stratigrafickým stářím (GSSA - Global Standard Stratigraphic Age). Neformální jednotky a jednotky doposud nepojmenované jsou psány kurzívou. Další verze tabulky a detailní informace o ratifikovaných GSSP jsou dostupné na webu http://www.stratigraphy.org. URL této tabulky je uveden níže. Absolutní stáří jsou průběžně revidována a nedefinují jednotky ve fanerozoiku a ediakaru, kde jsou rozhodující pouze GSSP. Pro absolutního stáří hranic fanerozoických jednotek bez ratifikovaného GSSP nebo bez přesného absolutního datování je použit symbol (~). Označení schválených pododdělení/podepoch jsou v tabulce zkrácena na sp/sta (spodní/starší), stř (střední) a sv/ml (svrchní/mladší). Absolutní stáří jednotek jsou převzata z Gradstein et al. (2012) ‘A Geologic Time Scale 2012’, s výjimkou kvartéru, svrchního paleogénu, křídy, jurský, triasu, permu a prekambria, pro něž byla data poskytnuta příslušnými ICS subkomisemi.
Einheiten aller hierarchischen Ebenen folgen dem Prinzip der Globalen Grenz-Stratotypprofilen und Punkten (GSSP, Global Boundary Stratotype Section and Points) für die Definition ihrer Untergrenzen, inklusive jener des Archaikum und Proterozoikum, die bisher durch Globale Stratigraphische Standardalter (GSSA) definiert wurden. Ratifizierte Subserien/Subepochen werden duch U/F (Unteres/Frühes), M (Mittel) und O/S (Oberes/Spätes) abgekürzt. Kursive Schrift indiziert informelle oder unbenannte Einheiten. Numerische Alter verändern sich laufend und definieren die Einheiten des Phanerozoikum und des Ediacarium nicht, sondern nur GSSPs. Für nicht ratifizierte Einheiten im Phanerozoikum oder solche ohne numerischen Altern wird ein ungefähres (~) Alter angegeben. Die meisten numerischen Alter stammen aus der Global Time Scale 2020 (Gradstein et al. 2020), jene Alter, die abweichen, folgen der jeweiligen Sukommission der ICS nach Abgleich mit der Subkommission für Kalibrierungder Zeitskala. Diese Alter wurden von der ICS Exekutive anerkannt.
Units of all ranks are in the process of being defined by Global Boundary Stratotype Section and Points (GSSP) for their lower boundaries, including those of the Archean and Proterozoic, long defined by Global Standard Stratigraphic Ages (GSSA). Ratified Subseries/Subepochs are abbreviated as U/L (Upper/Late), M (Middle) and L/E (Lower/Early). Italic fonts indicate informal units and placeholders for unnamed units. Previous versions and detailed information on ratified GSSPs are available at the website http://www.stratigraphy.org. The URL to this chart is provided below. Numerical ages are subject to ongoing revision and do not define units in the Phanerozoic and the Ediacaran; only GSSPs do. For boundaries in the Phanerozoic without ratified GSSPs or without constrained numerical ages, an approximate numerical age (~) is provided. Most numerical ages are taken from ‘A Geologic Time Scale 2020’ by Gradstein et al. (2020), but some ages differ as provided by the relevant ICS subcommissions, with advice from the Timescale Calibration subcommission. These are approved by the ICS executive as the current consensus.
Todas las unidades de esta Tabla, cualquiera que sea su rango, se definen por el Estratotipo Global de Límite (GSSP - Global Boundary Stratotype Section and Point) referido siempre a su límite inferior. Este proceso se halla inacabado e incluirá las unidades del Arcaico y Neoproterozoico, cuyas divisiones se convinieron inicialmente mediante edades numéricas (GSSA - Global Standard Stratigraphic Ages). La posición de los GSSP oficiales se indica en la tabla mediante el símbolo del “Clavo Dorado” (Golden Spike), que los materializa en el terreno. El original de la Tabla en distintos idiomas y formatos, junto con los detalles de los estratotipos globales de límite (criterio de definición de cada uno, localización geográfica y geológica, correlación, etc.), están disponibles en la web www.stratigraphy.org. Las edades absolutas, expresadas en millones de años (Ma), son sólo orientativas, pues las unidades del Fanerozoico y el Ediacárico se definen formalmente por sus correspondientes GSSP. No obstante, para aquellas divisiones que no cuentan aún con un estratotipo global o con edades bien establecidas, se indican las dataciones aproximadas (~ Ma) de sus límites. La mayoría de edades numéricas proceden de Gradstein et al. (A Geologic Time Scale 2020), sumando también las proporcionadas por Subcomisiones relevantes con la opinión favorable de la Subcomisión de Calibración de la Escala de Tiempo y el consenso de la ejecutiva de la Comisión Internacional de Estratigrafía.
La definición del Estratotipo Global de Límite (GSSP–Global Boundary Stratotype Section and Point) para la base de las unidades de los diversos rangos no se ha completado. Esto incluye también los estratotipos de límite correspondientes al Arqueano y Proterozoico, cuyas divisiones han estado tradicionalmente basadas en edades absolutas convencionales conocidas como Edades Estratigráficas Estándar Globales (GSSA–Global Standard Stratigraphic Ages). Las Subseries/Subépocas ratificadas se abrevian como S (Superior/Tardío), M (Medio) e I (Inferior/Temprano). Las unidades indicadas en cursiva corresponden a unidades informales y marcadores de posición para intervalos aún no nombrados. Las versiones anteriores de la tabla y la información detallada sobre los GSSP ratificados están disponibles en el sitio web http://www.stratigraphy.org. La URL para esta Tabla se proporciona más adelante. Las edades numéricas están sujetas a revisión y no definen unidades en el Fanerozoico ni en el Ediacariano; solo los GSSP lo hacen. Para los límites en el Fanerozoico que no tienen un GSSP formal o edades numéricas restringidas, se proporciona una edad numérica aproximada (~). La mayoría de las edades numéricas provienen de ‘A Geologic Time Scale 2020’ de Gradstein et al. (2020), aunque algunas difieren según lo establecido por las subcomisiones correspondientes de la ICS, con el asesoramiento de la Subcomisión de Calibración de la Escala Temporal. Estas edades han sido aprobadas por el comité ejecutivo de la ICS como el consenso vigente.
Kategoria guztietako unitateak definitzeko prozesuan daude beren beheko mugen muga-estratotipo globaleko ebaki eta puntuen bidez (GSSP-Global Boundary Stratotype Section and Point); baita Arkearrekoak eta Proterozoikokoak ere, denbora luzean adin estratigrafiko estandar globalez (GSSA-Global Standard Startigraphic Ages) definituak izan direnak. Taulak eta onetsitako GSSPen informazio xehea ondorengo web orrian eskuragarri daude: http://www.stratigraphy.org. Taula honen URLa behean adierazita dago. Adin numerikoak berrikusi egin daitezke eta ez dute unitaterik definitzen Fanerozoikoan eta Ediacararrean; soilik GSSPek definitzen dituzte unitateak. GSSPrik onetsita edo adin numeriko mugaturik ez duten mugentzako gutxi gorabeharko adin numeriko bat (~) eman da. Sistema guztien adin numerikoak, Behe Pleistozeno, Permiar, Triasiko, Kretazeo eta Kanbriarraurrekoak izan ezik, “A Geological Time Scale 2012” (Gradstein et al., 2012) argitalpenetik hartuak dira; Behe Pleistozeno, Permiar, Triasiko eta Kretazeokoak dagozkien ICSko azpibatzordeek emanak dira.
Kaikkien stratigrafisten tasojen yksiköille määritetään alarajoja Global Boundary Stratotype Section and Points (GSSP) -periaatteen mukaisesti. Tämä koskee myös arkeeisten ja proterotsooisten yksiköiden rajoja, jotka on aikaisemmin määritetty Global Standard Stratigraphic Ages (GSSA) -periaatteen mukaan. Epäviralliset yksiköt on kirjoitettu kursiivilla. Aiemmat versiot ja yksityiskohtaiset tiedot ratifioitujen globaalien stratotyyppileikkausten alakontaktien maantieteellisistä sijainneista (GSSP-kohteista) on saatavana verkkosivustolla http://www.stratigraphy.org. Kaavion verkkosivun URL-osoite on annettu alla. Numeeriset iät saattavat muuttua eikä niillä määritetä fanerotsooisia eikä ediakaran yksiköitä; ne rajautuvat yksinomaan globaalien stratotyyppileikkausten alakontaktien (GSSP:t) perusteella. Fanerotsooisille yksikkörajoille annetaan ikäarvio (~), mikäli rajoilla ei ole ratifioitua GSSP:tä tai vahvistettua numeerista ikää. Ratifioidut sarjojen ja epookkien alajaot on lyhennetty Y/M (ylä-/myöhäis-), K (keski) ja A/V (ala-/varhais-). Kvartääriä, yläpaleogeenia, liitua, triasta, permiä ja prekambria lukuun ottamatta numeeriset iät on esitetty Gradstein et al. (2012) julkaisussa ”A Geologic Time Scale 2012”; kvartäärin, yläpaleogeenin, liidun, jura, triaksen, permin ja prekambrin iät on saatu asianomaisilta ICS:n alakomiteoilta.
La définition de la limite inférieure de chaque unité formelle par un point précis dans la coupe d’un stratotype de limite global (GSSP-Global Boundary Stratotype Section and Points) est encore en cours, y compris celle des unités de l’Archéen et du Protérozoïque, auparavant définie par des âges absolus (GSSA-Global Standard Stratigraphic Ages). Les noms en italique indiquent des unités informelles et l’espace pour des unités à nommer. Les chartes et des informations plus détaillées sur les GSSP sont disponibles sur le site web de l’International Commission on Stratigraphy (ICS) www.stratigraphy.org. Les âges numériques sont sujets à révision et ne définissent pas les unités du Phanérozoïque et de l’Édicarien; seuls les GSSP le font. Pour les limites du Phanérozoïque qui n’ont pas de GSSP ratifiés ou des âges numériques calibrés, un âge numérique approximatif (~) est indiqué. Les sous-séries/- sous-époques ratifiées sont abbrégées par S (Supérieur), M (Moyen) et I (Inférieur). Les âges numériques de tous les systèmes à l’exception du Précambrien, Cambrien, Permien, Trias, Jurassique, Crétacé, Paléogène supérieur et Quaternaire sont tirés du livre A Geologic Time Scale 2012 par Gradstein et al. (2012); ceux Précambrien, Cambrien, Permien, Trias, Jurassique, Crétacé, Paléogène supérieur et Quaternaire ont été définis par les subcommissions de l’ICS.
Bármely rendű egység alsó határának kijelölése globális határsztratotípus-szelvény és pont (GSSP) alapján történik, beleértve az archaikum és proterozoikum egységeit is, bár ezeket sokáig globális standard rétegtani korok (GSSA) útján definiálták. Az informális, valamint a még elnevezésre váró egységeket dőlt betű jelzi. A táblázat különböző verziói és a ratifikált GSSP-kre vonatkozó részletes információk a http://www.stratigraphy.org honlapról érhetők el. E táblázat webcímét lásd alább. A számszerű korok új kormeghatározási eredmények alapján változhatnak, de a fanerozoikum egységeinek és az ediacarainak a definíciójában nincs szerepük. A ratifikált GSSP-vel vagy megbízhatóan meghatározott számszerű korral nem rendelkező fanerozoikumi egységeknél közelítő számszerű kor (~) szerepel. A ratifikált alsorozatok/alkorok rövidítése f/k (felső/késő), k (középső) és a/k (alsó/kora). A számszerű korok forrása Gradstein et al. (2012) „A Geologic Time Scale 2012” c. műve, kivéve a kvarter, felső paleogén, kréta, jura, triász, perm és prekambrium egységeit, melyekhez a Nemzetközi Rétegtani Bizottság illetékes albizottságai szolgáltattak adatot.
Satuan untuk setiap kategori sedang didefinisikan berdasarkan Batas Global Penampang Stratotipe dan Titik (GSSP) untuk batas bawah, termasuk untuk Archean dan Proterozoikum, yang selama ini di definisikan oleh Standard Umur Stratigrafi Global (GSSA). Sub Jenjang/Sub Umur yang sah disingkat menjadi A (Atas/Akhir), T (Tengah) dan B (Bawah/Awal). Huruf miring menandakan satuan informal, dan menjadi tempat untuk memberikan unit yang belum dinamai. Versi lama dan informasi detil yang sah dari GSSP tersedia di website https://www.stratigraphy.org. Tautan untuk bagan ini tersedia di bawah. Angka-angka umur dapat berubah dan tidak mendefinisikan Phanerozoikum dan Ediacaran; hanya GSSP yang mendefinisikan. Batas-batas Phanerozoikum tanpa pengesahan GSSP atau tanpa batasan umur numerik, perkiraan umur numeriknya (~) dicantumkan. Sebagian besar umur-umur diambil dari ‘Skala Watku Geologi 2020’ oleh Gradstein dkk (2020), tetapi beberapa umur berubah karena disediakan oleh subkomisi ICS yang berhubungan, dengan saran dari subkomisi Kalibrasi Skala Umur. Hal ini telah disetujui oleh pimpinan ICS dengan consensus terakhir.
Le unità stratigrafiche del Fanerozoico e dell'Ediacarano, sono state o sono in procinto di essere definite da GSSP (Global Boundary Stratotype Section and Points) tramite il loro limite inferiore. Le unità con età ≥ 1000 Ma, ovvero quelle dell'Archeano e del Proterozoico, sono al momento definite da GSSA (Global Stratigraphic Standard Ages). I nomi in corsivo identificano le unità informali, mentre le unità non ancora definite sono indicate con il nome generico del proprio rango. Schemi aggiornati e informazioni dettagliate sui GSSP ratificati sono disponibili sul sito web http://www.stratigraphy.org. Le datazioni numeriche sono oggetto di revisione e, a differenza dei GSSP, non definiscono unità nel Fanerozoico e nell’Ediacarano. Per le unità del Fanerozoico non definite da GSSP o senza un’età precisa, viene indicata un’età numerica approssimata (~). Le età numeriche per tutti i sistemi eccetto che per il Quaternario, il Paleogene superiore, il Cretacico, il Triassico, il Permiano, il Cambriano e il Precambriano sono prese da “A Geologic Time Scale 2012” di Gradstein et al. (2012), quelle per il Quaternario, il Paleogene superiore, il Cretacico, il Giurassico, il Triassico, il Permiano, il Cambriano e il Precambriano sono state fornite dalle relative sottocommissioni della ICS.
すべての階層の層序区分単位に対して，その下限をGSSPs（国際境界模式層断面とポイント）によって定義する作業が進行中である．これは，長らくGSSA（国際標準層序年代）によって定義されてきた太古（累）界および原生（累）界の下限に対しても同様である．GSSPsに関する図および詳細な情報は，ウェブサイト http://www.stratigraphy.org に掲載されている. 本表に掲載されている年代値は見直されることがあるが，それは顕生（累）界およびエディアカラン系の層序区分単位の定義の変更を伴うものではない．そのような定義の変更は，GSSPsによってのみ可能である．GSSPsにより定義されていない境界や確定した年代値がない顕生（累）界の層序区分単位境界に対しては，おおよその年代値を「~」を付して示した． 第四系，上部古第三系，白亜系，三畳系，ペルム系，カンブリア系，先カンブリア（累）界を除く全ての界の年代値は，Gradstein et al.（2012） の ‘The GeologicTime Scale 2012’による．第四系，上部古第三系，白亜系，三畳系，ペルム系，カンブリア系，先カンブリア（累）界の年代値に関しては，当該問題を扱う国際層序委員会の小委員会による． この日本語版ISC Chart（2023年6月版）は，IUGS（国際地質科学連合）の許諾を得て，日本地質学会が作成した．
오랫동안 국제표준층서연령(GSSA)으로 지정된 시생누대와 원생누대의하부경계를 포함하여, 모든 지질시대의 하부경계에 대한국제표준층서구역(GSSP)을 지정하고 있는 중이다. 이탤릭체는 비공식적인지질시대나 이름이 붙여지지 않은 지질시대를 나타낸다. 이 표의 모든 버전과승인된 GSSP에 대한 자세한 정보는http://www.stratigraphy.org에서 찾아볼 수있다. 이 표의 URL은 아래에 적어 놓았다. 수치연령은 수정될 수 있으며, 현생누대의 지질시대와 에디아카리기는수치연령이 아니라 GSSP에 의해서만 정의된다. GSSP가 승인되지 않았거나범위가 제한된 수치연령이 주어지지 않은 현생누대 지질시대의 경계에는수치연령의 근사값(~)을 적어 놓았다. 대부분의 수치연령은 ‘Gradstein et al. (2020)의 ‘A Geologic Time Scale 2020’로부터 인용하였으나, 몇 개의 수치연령은 지질연대 보정 위원회의 권고에 따라해당 지질시대위원회에서 제공한 것과 다르게 표기되어있다. 국제층서위원회임원들은 이 수치연령을 현재 합의된 것으로 승인하였다.
Visų rangų padaliniai yra apibrėžti Globalinio stratotipo pjūvio apatinės ribos tašku (GSPT), o archėjaus ir proterozojaus padaliniai nusakomi Globalinio stratigrafinio amžiaus standartu (GSAS). Ratifikuotos subserijos/subepochos yra sutrumpintos kaip Ap/An (Apatinis / Ankstyvasis), Vid (Vidurinis) ir Vir/Vėl (Viršutinis / Vėlyvasis). Pasvirieji šriftai nurodo neoficialius padalinius ir laikinus bevardžius vienetus. Ankstesnės versijos ir išsami informacija apie ratifikuotus GSSP yra pateikti svetainėje http://www.stratigraphy.org. Fanerozojaus ir ediakaro absoliūtus amžiai yra nuolat peržiūrimi ir neapibrėžia padalinių; tik GSPT gali tai nustatyti. Apytikslis absoliutus amžius (~) pateikiamas fanerozojaus padalinių riboms be ratifikuotų GSPT arba be tikslaus amžiaus. Absoliutaus amžiaus duomenys paimti iš „Geologinės laiko skalės 2020“ ir kt. (2020 m.), tačiau kai kurie amžiai skiriasi, kaip nurodyta ICS kartu su Laiko skalės kalibracijos pakomisių patarimais. ICS vykdomoji valdžia juos patvirtino pagal dabartinį sutarimą.
De ondergrens van eenheden van verschillende rang, wordt momenteel stapsgewijs gedefinieerd op basis van Global Boundary Stratotype Section and Points (GSSPs), ook die in het Archeïcum en het Proterozoïcum welke vooralsnog als Global Standard Stratigraphic Age (GSSA) vastgesteld zijn. Tabellen en nadere informatie over geratificeerde GSSPs zijn te vinden op www.stratigraphy.org. De URL van deze tabel is hieronder gegeven. Van eenheden met hun door een GSSP gedefinieerde ondergrens, wordt de veronderstelde ouderdom in Ma van tijd tot tijd herzien (naar nieuw inzicht bijgesteld). Voor Fanerozoïsche eenheden waarvoor nog geen GSSP en/of numerieke ouderdom is vastgesteld, is een ouderdom bij benadering gegeven (~). De ouderdommen in Ma zijn overgenomen uit ‘A Geological Time Scale 2012’ door Gradstein et al. (2012), met uitzondering van die voor het Precambrium, Cambrium, Perm, Trias, Jura, Krijt, boven Paleogeen en Kwartair, die afkomstig zijn van de betreffende ICS subcommissies.
De ondergrens van eenheden van verschillende rang, wordt momenteel stapsgewijs gedefinieerd op basis van Global Boundary Stratotype Section and Points (GSSPs), ook die in het Archeïcum en het Proterozoïcum welke vooralsnog als Global Standard Stratigraphic Age (GSSA) vastgesteld zijn. Tabellen en nadere informatie over geratificeerde GSSPs zijn te vinden op www.stratigraphy.org. De URL van deze tabel is hieronder gegeven. Van eenheden met hun door een GSSP gedefinieerde ondergrens, wordt de veronderstelde ouderdom in Ma van tijd tot tijd herzien (naar nieuw inzicht bijgesteld). Voor Fanerozoïsche eenheden waarvoor nog geen GSSP en/of numerieke ouderdom is vastgesteld, is een ouderdom bij benadering gegeven (~). De ouderdommen in Ma zijn overgenomen uit ‘A Geological Time Scale 2012’ door Gradstein et al. (2012), met uitzondering van die voor het Precambrium, Cambrium, Perm, Trias, Jura, Krijt, boven Paleogeen en Quartair, die afkomstig zijn van de betreffende ICS subcommissies.
Det pågår nå en prosess der de nedre grensene for alle enhetene i tabellen defineres med Global Boundary Stratotype Section and Points (GSSP). Dette gjelder også for grensene i arkeikum og proterozoikum som lenge har vært definert med Global Standard Stratigraphical Ages (GSSA). Tabeller og detaljert informasjon om ratifiserte GSSP er tilgjengelig på websiden www.stratigraphy.org. Denne tabellens URL finnes nedenfor. Numeriske aldre underkastes revisjon og definerer ikke enheter i fanerozoikum og ediacara; kun ratifiserte GSSP gjelder. For grenser i fanerozoikum uten ratifisert GSSP eller kalibrerte numeriske aldere, er bare tilnærmete aldre (~) oppgitt. Numeriske aldre for alle systemer unntatt prekambrium, perm, trias, jura, kritt, øvre paleogen og kvartær er hentet fra ‘A Geological Time Scale 2012’ av Gradstein et al. (2012), mens de fra prekambrium, perm, trias, jura, kritt, øvre paleogen og kvartær er fremskaffet av de relevante underkomiteer i ICS.
Jednostki wszystkich rang są w trakcie definiowania przez Globalny Punkt i Przekrój Stratotypu Granicy (GSSP) dla ich dolnych granic, w tym jednostek archajskich i proterozoicznych, długo definiowanych przez Globalne Standardowe Wieki Stratygraficzne (GSSA). Ratyfikowane Podserie/Podepioki są skracane jako G/P (Górny/Późny), Ś (Środkowy) i D/W (Dolny/Wczesny). Kursywa wskazuje jednostki nieformalne i symbole zastępcze dla jednostek nienazwanych. Poprzednie wersje i szczegółowe informacje o ratyfikowanych GSSP są dostępne na stronie http://www.stratigraphy.org. Adres URL do tej tablicy podano poniżej. Wieki numeryczne podlegają bieżącej weryfikacji i nie definiują jednostek w fanerozoiku i ediakaranie; robią to wyłącznie GSSP. Dla granic w fanerozoiku bez ratyfikowanych GSSP lub bez ustalonych wieków numerycznych podano przybliżony wiek numeryczny (~). Większość wieków numerycznych pochodzi z 'A Geologic Time Scale 2020' Gradsteina i in. (2020), jednak niektóre wieki różnią się zgodnie z zaleceniami odpowiednich subkomisji ICS, po konsultacji z subkomisją ds. kalibracji skali czasu. Zostały one zatwierdzone przez zarząd ICS jako aktualny konsensus.
A definição do Estratotipo Global de Limite (GSSP - Global Boundary Stratotype Section and Point) para a base dos diversos andares, séries, sistemas e eratemas, é um processo ainda incompleto. O mesmo ocorre com os estratotipos de limite das unidades do Arqueano e Proterozoico, cuja divisão inicial é fundamentada numa convenção de idades absolutas (GSSA - Global Standard Stratigraphic Ages). Os GSSP oficiais estão assinalados com o símbolo do “Prego Dourado” (Golden Spike), que também os materializa no terreno. A Tabela original e os detalhes sobre os GSSP (critério de definição de cada um, localização geográfica e geológica, correlação, etc.), atualizam-se regularmente na web page: http://www.stratigraphy.org. A datação absoluta em milhões de anos (Ma) para a base do Ediacárico e das restantes unidades do Fanerozoico é apenas orientadora, em especial para os limites sem GSSP formal (~Ma). Estes valores poderão ser revistos no futuro ou serem recalibrados geocronometricamente. Os valores indicados são provenientes de Gradstein et al. (A Geologic Time Scale 2012), excetuando as datações do Pleistoceno, Paleógeno Superior, Cretáceo, Jurássico, Triássico, Permiano e Pré-Cambriano, fornecidas pelas subcomissões respetivas da ICS-IUGS.
A definição do Estratotipo Global de Limite (GSSP - Global Boundary Stratotype Section and Point) para a base dos diversos andares, séries, sistemas e eratemas, é um processo ainda incompleto. O mesmo ocorre com os estratotipos de limite das unidades do Arqueano e Proterozoico, cuja divisão inicial é fundamentada numa convenção de idades absolutas (GSSA - Global Standard Stratigraphic Ages). Os GSSP oficiais estão assinalados com o símbolo do “Prego Dourado” (Golden Spike), que também os materializa no terreno. A Tabela original e os detalhes sobre os GSSP (critério de definição de cada um, localização geográfica e geológica, correlação, etc.), atualizam-se regularmente na web page: http://www.stratigraphy.org. A datação absoluta em milhões de anos (Ma) para a base do Ediacárico e das restantes unidades do Fanerozoico é apenas orientadora, em especial para os limites sem GSSP formal (~Ma). Estes valores poderão ser revistos no futuro ou serem recalibrados geocronometricamente. A maioria dos valores indicados são provenientes de Gradstein et al. (A Geologic Time Scale 2024), embora algumas divirjam conforme estabelecido pelos subcomitês relevantes da ICS, com o parecer do Subcomitê de Calibração da Escala Temporal. Estas idades foram aprovadas pelo ICS como o consenso atual. A tabela é o resultado do esforço coletivo de todos os membros atuais e antigos do ICS.
Нижние границы всех подразделений, определяемые Точкой глобального стратотипа границ (ТГСГ) постоянно уточняются, в том числе подразделения архея и протерозоя, давно определяемые геохронологическими данными (ГССВ /GSSA). Шкалы и подробная информация о ратифицированных GSSP доступна на сайте: http://www.stratigraphy.org. URL-адрес данной шкалы приводится ниже. Геохронологические возрасты границ постоянно уточняются и не определяют поразделения фанерозоя и эдиакария, которые фиксируются только через GSSP. Для границ в фанерозое, которые не имеют ратифицированных GSSP или рассчитанных геохронологических оценок, указано приблизительное значение (~). Оценки возрастов для всех систем, за исключением раннего плейстоцена, мелового, триасового, пермского периодов и докембрия приведены по «A Geologic Time Scale 2012» (Gradstein et al., 2012); а для указанных выше систем представлены соответствующими подкомиссиями ICS.
Spodné hranice všetkých rádov sú definované na základe stratotypových profilov a bodov globálnych hraníc (GSSP) vrátane archaických a peroterozoických, ktoré sú definované na základe globálnych štandardných stratigrafických vekov (GSSA). Názvy písané kurzívou predstavujú neformálne jednotky a miesta pre doteraz nepomenované jednotky. Tabuľky s aktualizovanými verziami a podrobné informácie o ratifikovaných GSSP sú dostupné na webovej stránke http://www.stratigraphy.org URL adresa tejto tabuľky je uvedená dolu. Numerické veky sú predmetom revízie a na rozdiel od GSSP nedefinujú jednotky fanerozoika a ediakaru. Pre hranice fanerozoických stupňov bez ratifikovaných GSSP alebo bez definovaného numerického veku, je použitý približný numerický vek (~). Ratifikované pododdelenia/podepochy sú skrátene označené v./m. (vrchný/mladší), str. (stredný) a sp./st. (spodný/starší). Numerické veky pri všetkých útvaroch okrem kvartéru, vrchného paleogénu, kriedy, triasu, permu a predkambria sú prevzaté z práce Gradstein et al. (2012) A Geologic Time Scale 2012. Kvartérne, vrchnopaleogénne, kriedové, jurský, triasové, permské a predkambrické veky poskytli príslušné subkomisie ICS.
Bütün kademelerin birimlerinin alt sınırları Küresel Stratotip Kesit ve Noktaların Sınırları (GSSP) kapsamında tanımlanmıştır ve buna Küresel Standart Stratigrafik Yaşlar (GSSA) tarafından uzun zamandır tanımlanan Arkeen ile Proterozoyik de dâhildir. Çizelgeler ve tasdikli GSSP’ler hakkında daha detaylı bilgiler http://www.stratigraphy.org sayfasından temin edilebilir. Bu çizelgenin URL’si aşağıda verilmiştir. Sayısal yaş değerleri gözden geçirilmeye açıktır ve Fanerozoyik ile Ediyakaran içindeki birimlerin sınırlanmasını sağlamaz; sadece GSSP ile elde edilmiştir. Tasdikli GSSP’den veya sınırlandırılmış sayısal yaş değerlerinden yoksun Fanerozoyikteki sınırlar için, yaklaşık sayısal değer (~) verilmiştir. Tasdikli Alt Seri/Devreler Ü/G (Üst/Geç), O (Orta) ve A/E (Alt/Erken) olarak kısaltılmıştır. Kuvaterner, Üst Paleojen, Kretase, Jura, Triyas, Permiyen ve Pre-Kambriyen dışında tüm sistemlerin sayısal yaş değerleri “Jeolojik Zaman Tablosu 2012”den alınmıştır (Gradstein vd. 2012); Kuvaterner, Üst Paleojen, Kretase, Jura, Triyas, Permiyen ve Pre-Kambriyen için olan yaşlar, Uluslararası Stratigrafi Komisyonu’nun ilgili alt komisyonları tarafından sağlanmıştır.
所有全球年代地层单位均由其底界的全球界线层型剖面和 点位（GSSP）界定，包括长期由全球标准地层年龄（GSSA） 界定的太古宇和元古宇各单位。斜体代表非正式名称或尚未命 名单位的临时名称。图件及已批准GSSP的详情参见国际地层 委员会官网。本图件的网址见右下角。 年龄值仍在不断修订；显生宇和埃迪卡拉系的单位不能由 年龄界定，而只能由GSSP界定。显生宇中没有确定GSSP或精 确年龄值的单位，则标注了近似年龄值（～）。 已批准的亚统/亚世简写为上/晚、中、下/早；第四系、古 近系上部、白垩系、侏罗系、三叠系、二叠系、寒武系和前寒 武系的年龄值由各分会提供；其他年龄值引自Gradstein等主 编的《地质年代表2012》一书。
This vocabulary uses IRIs originally created for the Geologic Timescale (2020) data (see http://resource.geosciml.org/vocabulary/timescale/)
International Chronostratigraphic Chart
2026-06: Strati2026 version of the Chart with updates indicated in element changeNotes 2024-12: Updated Chart to include: * ratification of the Valanginian GSSP * numeric age of Valanginian updated to 137.05 +/- 0.2 2023-09: updated form of the Geologic Timescale (2020) (see http://resource.geosciml.org/vocabulary/timescale/) to match the 2023-09 Chart, as released at https://stratigraphy.org/chart in late 2023.
(c) Beynəlxalq Stratiqrafiya Komissiyası (International Commission on Stratigraphy), İyun 2026
© Comissió Internacional d’Estratigrafia, 2026
© Mezinárodní stratigrafická komise, září 2026
© International Commission on Stratigraphy, 2026
© Nemzetközi Rétegtani Bizottság, 2026
© 国際層序委員会，2026年12月
© 국제층서위원회, 2026년 12월
© Międzynarodowa Komisja Stratygrafii, 2026
© Международная комиссия по стратиграфии, февраль 20126 г
© Medzinárodná stratigrafická komisia, 2026
© 国际地层委员会，2026年09月（英文版）
Dövrlər
Edats
Věky
Zeitalter
Edades
Aroak
Ajat
Âges
Korok
Zaman
Età
時代
시대
Amžiai
Tijdperken
Tidsaldre
Wieki
Idades
Века
Veky
Çağlar
世代
An age is the smallest hierarchical geochronologic unit and is equivalent to a chronostratigraphic stage. These are thousands to millions of years in length
This Collection was created from the age ranks of the Chart
Ages
Aaleniense
Aalen
Aalénien
aaleni
Alenis
Aaleniano
álen
aalen
Aalenium
Aaleniar
Aalenian
アーレニアン
알렌절
Aalenien
Aaleniaan
Ааленский
Aaleniyen
阿林阶
174.7-dən 170.9 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 174.7 a 170.9 milions d'anys enrere
Časové období od 174.7 do 170.9 milionů let před naším letopočtem
Ein Zeitraum von 174.7 bis 170.9 Millionen Jahren
A time period from 174.7 to 170.9 million years ago
Un período de tiempo de 174.7 a 170.9 millones de años atrás
174.7 eta 170.9 milioi urte arteko denbora-tartea
Aikajakso 174.7–170.9 miljoonaa vuotta sitten
Une période de temps de 174.7 à 170.9 millions d'années
Egy 174.7-tól 170.9 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 174.7 hingga 170.9 juta tahun yang lalu
Un periodo di tempo da 174.7 a 170.9 milioni di anni fa
174.7百万年前から170.9百万年前までの時代
174.7백만 년 전부터 170.9백만 년 전까지의 시기
Laikotarpis nuo 174.7 iki 170.9 milijonų metų prieš dabartį
Een tijdperiode van 174.7 tot 170.9 miljoen jaar geleden
Een tijdsperiode van 174.7 tot 170.9 miljoen jaar geleden
En tidsperiode fra 174.7 til 170.9 millioner år siden
Okres czasu od 174.7 do 170.9 milionów lat temu
Um período de tempo de 174.7 a 170.9 milhões de anos atrás
Временной период от 174.7 до 170.9 миллионов лет назад
Časové obdobie od 174.7 do 170.9 miliónov rokov pred naším letopočtom
174.7 ile 170.9 milyon yıl önce arasındaki zaman dilimi
距今 174.7 至 170.9 百万年前的时期
Aeronium
Aeroniense
Aeron
Aéronien
aeroni
Aeronis
Aeroniano
Aeronià
aeron
Aeroniar
Aeronian
アエロニアン
에어론절
Aeronien
Aeroniaan
Аэронский
Aroniyen
埃隆阶
440.5-dən 438.6 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 440.5 a 438.6 milions d'anys enrere
Časové období od 440.5 do 438.6 milionů let před naším letopočtem
Ein Zeitraum von 440.5 bis 438.6 Millionen Jahren
A time period from 440.5 to 438.6 million years ago
Un período de tiempo de 440.5 a 438.6 millones de años atrás
440.5 eta 438.6 milioi urte arteko denbora-tartea
Aikajakso 440.5–438.6 miljoonaa vuotta sitten
Une période de temps de 440.5 à 438.6 millions d'années
Egy 440.5-tól 438.6 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 440.5 hingga 438.6 juta tahun yang lalu
Un periodo di tempo da 440.5 a 438.6 milioni di anni fa
440.5百万年前から438.6百万年前までの時代
440.5백만 년 전부터 438.6백만 년 전까지의 시기
Laikotarpis nuo 440.5 iki 438.6 milijonų metų prieš dabartį
Een tijdperiode van 440.5 tot 438.6 miljoen jaar geleden
Een tijdsperiode van 440.5 tot 438.6 miljoen jaar geleden
En tidsperiode fra 440.5 til 438.6 millioner år siden
Okres czasu od 440.5 do 438.6 milionów lat temu
Um período de tempo de 440.5 a 438.6 milhões de anos atrás
Временной период от 440.5 до 438.6 миллионов лет назад
Časové obdobie od 440.5 do 438.6 miliónov rokov pred naším letopočtom
440.5 ile 438.6 milyon yıl önce arasındaki zaman dilimi
距今 440.5 至 438.6 百万年前的时期
Albium
Albiense
Albien
albai
Albis
Alb
Albiano
alb
Albià
Albiar
Alba
Albian
アルビアン
알바절
Albiaan
Альбский
Albiyen
阿尔布阶
113.2-dən 100.5 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 113.2 a 100.5 milions d'anys enrere
Časové období od 113.2 do 100.5 milionů let před naším letopočtem
Ein Zeitraum von 113.2 bis 100.5 Millionen Jahren
A time period from 113.2 to 100.5 million years ago
Un período de tiempo de 113.2 a 100.5 millones de años atrás
113.2 eta 100.5 milioi urte arteko denbora-tartea
Aikajakso 113.2–100.5 miljoonaa vuotta sitten
Une période de temps de 113.2 à 100.5 millions d'années
Egy 113.2-tól 100.5 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 113.2 hingga 100.5 juta tahun yang lalu
Un periodo di tempo da 113.2 a 100.5 milioni di anni fa
113.2百万年前から100.5百万年前までの時代
113.2백만 년 전부터 100.5백만 년 전까지의 시기
Laikotarpis nuo 113.2 iki 100.5 milijonų metų prieš dabartį
Een tijdperiode van 113.2 tot 100.5 miljoen jaar geleden
Een tijdsperiode van 113.2 tot 100.5 miljoen jaar geleden
En tidsperiode fra 113.2 til 100.5 millioner år siden
Okres czasu od 113.2 do 100.5 milionów lat temu
Um período de tempo de 113.2 a 100.5 milhões de anos atrás
Временной период от 113.2 до 100.5 миллионов лет назад
Časové obdobie od 113.2 do 100.5 miliónov rokov pred naším letopočtom
113.2 ile 100.5 milyon yıl önce arasındaki zaman dilimi
距今 113.2 至 100.5 百万年前的时期
Anisium
Anisiense
Anis
Anisien
anisusi
Anizis
Anizyk
Anisiano
anis
Aniziy
Anisià
Anisiar
Anisian
Anisico
アニシアン
아니수스절
Anisiaan
Анизийский
Aniziyen
安尼阶
247.0-dən 241.464 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 247.0 a 241.464 milions d'anys enrere
Časové období od 247.0 do 241.464 milionů let před naším letopočtem
Ein Zeitraum von 247.0 bis 241.464 Millionen Jahren
A time period from 247.0 to 241.464 million years ago
Un período de tiempo de 247.0 a 241.464 millones de años atrás
247.0 eta 241.464 milioi urte arteko denbora-tartea
Aikajakso 247.0–241.464 miljoonaa vuotta sitten
Une période de temps de 247.0 à 241.464 millions d'années
Egy 247.0-tól 241.464 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 247.0 hingga 241.464 juta tahun yang lalu
Un periodo di tempo da 247.0 a 241.464 milioni di anni fa
247.0百万年前から241.464百万年前までの時代
247.0백만 년 전부터 241.464백만 년 전까지의 시기
Laikotarpis nuo 247.0 iki 241.464 milijonų metų prieš dabartį
Een tijdperiode van 247.0 tot 241.464 miljoen jaar geleden
Een tijdsperiode van 247.0 tot 241.464 miljoen jaar geleden
En tidsperiode fra 247.0 til 241.464 millioner år siden
Okres czasu od 247.0 do 241.464 milionów lat temu
Um período de tempo de 247.0 a 241.464 milhões de anos atrás
Временной период от 247.0 до 241.464 миллионов лет назад
Časové obdobie od 247.0 do 241.464 miliónov rokov pred naším letopočtom
247.0 ile 241.464 milyon yıl önce arasındaki zaman dilimi
距今 247.0 至 241.464 百万年前的时期
Aptium
Aptiense
Apt
Aptien
apti
Aptis
Aptiano
apt
Aptià
Aptiar
Aptian
アプチアン
압트절
Aptiaan
Аптский
Apsiyen
阿普特阶
121.4-dən 113.2 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 121.4 a 113.2 milions d'anys enrere
Časové období od 121.4 do 113.2 milionů let před naším letopočtem
Ein Zeitraum von 121.4 bis 113.2 Millionen Jahren
A time period from 121.4 to 113.2 million years ago
Un período de tiempo de 121.4 a 113.2 millones de años atrás
121.4 eta 113.2 milioi urte arteko denbora-tartea
Aikajakso 121.4–113.2 miljoonaa vuotta sitten
Une période de temps de 121.4 à 113.2 millions d'années
Egy 121.4-tól 113.2 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 121.4 hingga 113.2 juta tahun yang lalu
Un periodo di tempo da 121.4 a 113.2 milioni di anni fa
121.4百万年前から113.2百万年前までの時代
121.4백만 년 전부터 113.2백만 년 전까지의 시기
Laikotarpis nuo 121.4 iki 113.2 milijonų metų prieš dabartį
Een tijdperiode van 121.4 tot 113.2 miljoen jaar geleden
Een tijdsperiode van 121.4 tot 113.2 miljoen jaar geleden
En tidsperiode fra 121.4 til 113.2 millioner år siden
Okres czasu od 121.4 do 113.2 milionów lat temu
Um período de tempo de 121.4 a 113.2 milhões de anos atrás
Временной период от 121.4 до 113.2 миллионов лет назад
Časové obdobie od 121.4 do 113.2 miliónov rokov pred naším letopočtom
121.4 ile 113.2 milyon yıl önce arasındaki zaman dilimi
距今 121.4 至 113.2 百万年前的时期
Aquitanium
Aquitanien
aquitaniai
Akvitanis
Akwitan
Aquitaniano
akvitán
Akvitan
Aquitanià
Aquitaniense
Aquitaniar
Aquitania
Aquitanian
アキタニアン
아킨텐절
Aquitaniaan
Aquitain
Аквитанский
Akitaniyen
阿基坦阶
23.03-dən 20.45 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 23.03 a 20.45 milions d'anys enrere
Časové období od 23.03 do 20.45 milionů let před naším letopočtem
Ein Zeitraum von 23.03 bis 20.45 Millionen Jahren
A time period from 23.03 to 20.45 million years ago
Un período de tiempo de 23.03 a 20.45 millones de años atrás
23.03 eta 20.45 milioi urte arteko denbora-tartea
Aikajakso 23.03–20.45 miljoonaa vuotta sitten
Une période de temps de 23.03 à 20.45 millions d'années
Egy 23.03-tól 20.45 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 23.03 hingga 20.45 juta tahun yang lalu
Un periodo di tempo da 23.03 a 20.45 milioni di anni fa
23.03百万年前から20.45百万年前までの時代
23.03백만 년 전부터 20.45백만 년 전까지의 시기
Laikotarpis nuo 23.03 iki 20.45 milijonų metų prieš dabartį
Een tijdperiode van 23.03 tot 20.45 miljoen jaar geleden
Een tijdsperiode van 23.03 tot 20.45 miljoen jaar geleden
En tidsperiode fra 23.03 til 20.45 millioner år siden
Okres czasu od 23.03 do 20.45 milionów lat temu
Um período de tempo de 23.03 a 20.45 milhões de anos atrás
Временной период от 23.03 до 20.45 миллионов лет назад
Časové obdobie od 23.03 do 20.45 miliónov rokov pred naším letopočtom
23.03 ile 20.45 milyon yıl önce arasındaki zaman dilimi
距今 23.03 至 20.45 百万年前的时期
Artinskium
Artinskiense
Artinsk
Artinskien
artyinszki
Artinskis
Artinskiano
artinsk
Artin
Artinskià
Artinskiar
Artinskian
アーティンスキアン
아르틴스크절
Artinskiaan
Artynsk
Артинский
Artinskiyen
亚丁斯克阶
290.1-dən 283.3 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 290.1 a 283.3 milions d'anys enrere
Časové období od 290.1 do 283.3 milionů let před naším letopočtem
Ein Zeitraum von 290.1 bis 283.3 Millionen Jahren
A time period from 290.1 to 283.3 million years ago
Un período de tiempo de 290.1 a 283.3 millones de años atrás
290.1 eta 283.3 milioi urte arteko denbora-tartea
Aikajakso 290.1–283.3 miljoonaa vuotta sitten
Une période de temps de 290.1 à 283.3 millions d'années
Egy 290.1-tól 283.3 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 290.1 hingga 283.3 juta tahun yang lalu
Un periodo di tempo da 290.1 a 283.3 milioni di anni fa
290.1百万年前から283.3百万年前までの時代
290.1백만 년 전부터 283.3백만 년 전까지의 시기
Laikotarpis nuo 290.1 iki 283.3 milijonų metų prieš dabartį
Een tijdperiode van 290.1 tot 283.3 miljoen jaar geleden
Een tijdsperiode van 290.1 tot 283.3 miljoen jaar geleden
En tidsperiode fra 290.1 til 283.3 millioner år siden
Okres czasu od 290.1 do 283.3 milionów lat temu
Um período de tempo de 290.1 a 283.3 milhões de anos atrás
Временной период от 290.1 до 283.3 миллионов лет назад
Časové obdobie od 290.1 do 283.3 miliónov rokov pred naším letopočtom
290.1 ile 283.3 milyon yıl önce arasındaki zaman dilimi
距今 290.1 至 283.3 百万年前的时期
Asselium
Asseliense
Assel
Assélien
asszeli
Aselis
Asseliano
assel
Asselià
Asseliar
Asselian
アッセリアン
아셀절
Asselien
Asseliaan
Ассельский
Asseliyen
阿瑟尔阶
298.9-dən 293.52 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 298.9 a 293.52 milions d'anys enrere
Časové období od 298.9 do 293.52 milionů let před naším letopočtem
Ein Zeitraum von 298.9 bis 293.52 Millionen Jahren
A time period from 298.9 to 293.52 million years ago
Un período de tiempo de 298.9 a 293.52 millones de años atrás
298.9 eta 293.52 milioi urte arteko denbora-tartea
Aikajakso 298.9–293.52 miljoonaa vuotta sitten
Une période de temps de 298.9 à 293.52 millions d'années
Egy 298.9-tól 293.52 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 298.9 hingga 293.52 juta tahun yang lalu
Un periodo di tempo da 298.9 a 293.52 milioni di anni fa
298.9百万年前から293.52百万年前までの時代
298.9백만 년 전부터 293.52백만 년 전까지의 시기
Laikotarpis nuo 298.9 iki 293.52 milijonų metų prieš dabartį
Een tijdperiode van 298.9 tot 293.52 miljoen jaar geleden
Een tijdsperiode van 298.9 tot 293.52 miljoen jaar geleden
En tidsperiode fra 298.9 til 293.52 millioner år siden
Okres czasu od 298.9 do 293.52 milionów lat temu
Um período de tempo de 298.9 a 293.52 milhões de anos atrás
Временной период от 298.9 до 293.52 миллионов лет назад
Časové obdobie od 298.9 do 293.52 miliónov rokov pred naším letopočtom
298.9 ile 293.52 milyon yıl önce arasındaki zaman dilimi
距今 298.9 至 293.52 百万年前的时期
Bajocium
Bajociense
Bajoc
Bajocien
bajoci
Bajosis
Bajos
Bajociano
bajok
Bayos
Bajocià
Bajociar
Bajocian
バジョシアン
바조카에절
Bajociaan
Байосский
Bajosiyen
巴柔阶
170.9-dən 168.2 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 170.9 a 168.2 milions d'anys enrere
Časové období od 170.9 do 168.2 milionů let před naším letopočtem
Ein Zeitraum von 170.9 bis 168.2 Millionen Jahren
A time period from 170.9 to 168.2 million years ago
Un período de tiempo de 170.9 a 168.2 millones de años atrás
170.9 eta 168.2 milioi urte arteko denbora-tartea
Aikajakso 170.9–168.2 miljoonaa vuotta sitten
Une période de temps de 170.9 à 168.2 millions d'années
Egy 170.9-tól 168.2 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 170.9 hingga 168.2 juta tahun yang lalu
Un periodo di tempo da 170.9 a 168.2 milioni di anni fa
170.9百万年前から168.2百万年前までの時代
170.9백만 년 전부터 168.2백만 년 전까지의 시기
Laikotarpis nuo 170.9 iki 168.2 milijonų metų prieš dabartį
Een tijdperiode van 170.9 tot 168.2 miljoen jaar geleden
Een tijdsperiode van 170.9 tot 168.2 miljoen jaar geleden
En tidsperiode fra 170.9 til 168.2 millioner år siden
Okres czasu od 170.9 do 168.2 milionów lat temu
Um período de tempo de 170.9 a 168.2 milhões de anos atrás
Временной период от 170.9 до 168.2 миллионов лет назад
Časové obdobie od 170.9 do 168.2 miliónov rokov pred naším letopočtom
170.9 ile 168.2 milyon yıl önce arasındaki zaman dilimi
距今 170.9 至 168.2 百万年前的时期
Barremiense
Barrem
Barrémien
barremi
Baremis
Barremiano
barém
Barremià
barrem
Barremium
Barremiar
Barremian
バレミアン
바렘절
Barremien
Barremiaan
Барремский
Barremiyen
巴雷姆阶
125.77-dən 121.4 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 125.77 a 121.4 milions d'anys enrere
Časové období od 125.77 do 121.4 milionů let před naším letopočtem
Ein Zeitraum von 125.77 bis 121.4 Millionen Jahren
A time period from 125.77 to 121.4 million years ago
Un período de tiempo de 125.77 a 121.4 millones de años atrás
125.77 eta 121.4 milioi urte arteko denbora-tartea
Aikajakso 125.77–121.4 miljoonaa vuotta sitten
Une période de temps de 125.77 à 121.4 millions d'années
Egy 125.77-tól 121.4 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 125.77 hingga 121.4 juta tahun yang lalu
Un periodo di tempo da 125.77 a 121.4 milioni di anni fa
125.77百万年前から121.4百万年前までの時代
125.77백만 년 전부터 121.4백만 년 전까지의 시기
Laikotarpis nuo 125.77 iki 121.4 milijonų metų prieš dabartį
Een tijdperiode van 125.77 tot 121.4 miljoen jaar geleden
Een tijdsperiode van 125.77 tot 121.4 miljoen jaar geleden
En tidsperiode fra 125.77 til 121.4 millioner år siden
Okres czasu od 125.77 do 121.4 milionów lat temu
Um período de tempo de 125.77 a 121.4 milhões de anos atrás
Временной период от 125.77 до 121.4 миллионов лет назад
Časové obdobie od 125.77 do 121.4 miliónov rokov pred naším letopočtom
125.77 ile 121.4 milyon yıl önce arasındaki zaman dilimi
距今 125.77 至 121.4 百万年前的时期
Bartonium
Bartoniense
Barton
Bartonien
bartoni
Bartonis
Bartoniano
bartón
Bartonià
barton
Bartoniar
Bartonian
バートニアン
바턴절
Bartoniaan
Бартонский
Bartoniyen
巴顿阶
41.03-dən 37.71 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 41.03 a 37.71 milions d'anys enrere
Časové období od 41.03 do 37.71 milionů let před naším letopočtem
Ein Zeitraum von 41.03 bis 37.71 Millionen Jahren
A time period from 41.03 to 37.71 million years ago
Un período de tiempo de 41.03 a 37.71 millones de años atrás
41.03 eta 37.71 milioi urte arteko denbora-tartea
Aikajakso 41.03–37.71 miljoonaa vuotta sitten
Une période de temps de 41.03 à 37.71 millions d'années
Egy 41.03-tól 37.71 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 41.03 hingga 37.71 juta tahun yang lalu
Un periodo di tempo da 41.03 a 37.71 milioni di anni fa
41.03百万年前から37.71百万年前までの時代
41.03백만 년 전부터 37.71백만 년 전까지의 시기
Laikotarpis nuo 41.03 iki 37.71 milijonų metų prieš dabartį
Een tijdperiode van 41.03 tot 37.71 miljoen jaar geleden
Een tijdsperiode van 41.03 tot 37.71 miljoen jaar geleden
En tidsperiode fra 41.03 til 37.71 millioner år siden
Okres czasu od 41.03 do 37.71 milionów lat temu
Um período de tempo de 41.03 a 37.71 milhões de anos atrás
Временной период от 41.03 до 37.71 миллионов лет назад
Časové obdobie od 41.03 do 37.71 miliónov rokov pred naším letopočtom
41.03 ile 37.71 milyon yıl önce arasındaki zaman dilimi
距今 41.03 至 37.71 百万年前的时期
Bashkirium
Bashkiriense
Bashkir
Bashkirien
Bashkiriano
baškir
Başgir
Baixkirià
Bashkiriar
baskíri
Bashkirian
バシキリアン
바시키르절
Baškiris
Bashkiriaan
Basjkir
Baszkirian
Башкирский
Başkiriyen
巴什基尔阶
323.4-dən 315.2 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 323.4 a 315.2 milions d'anys enrere
Časové období od 323.4 do 315.2 milionů let před naším letopočtem
Ein Zeitraum von 323.4 bis 315.2 Millionen Jahren
A time period from 323.4 to 315.2 million years ago
Un período de tiempo de 323.4 a 315.2 millones de años atrás
323.4 eta 315.2 milioi urte arteko denbora-tartea
Aikajakso 323.4–315.2 miljoonaa vuotta sitten
Une période de temps de 323.4 à 315.2 millions d'années
Egy 323.4-tól 315.2 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 323.4 hingga 315.2 juta tahun yang lalu
Un periodo di tempo da 323.4 a 315.2 milioni di anni fa
323.4百万年前から315.2百万年前までの時代
323.4백만 년 전부터 315.2백만 년 전까지의 시기
Laikotarpis nuo 323.4 iki 315.2 milijonų metų prieš dabartį
Een tijdperiode van 323.4 tot 315.2 miljoen jaar geleden
Een tijdsperiode van 323.4 tot 315.2 miljoen jaar geleden
En tidsperiode fra 323.4 til 315.2 millioner år siden
Okres czasu od 323.4 do 315.2 milionów lat temu
Um período de tempo de 323.4 a 315.2 milhões de anos atrás
Временной период от 323.4 до 315.2 миллионов лет назад
Časové obdobie od 323.4 do 315.2 miliónov rokov pred naším letopočtom
323.4 ile 315.2 milyon yıl önce arasındaki zaman dilimi
距今 323.4 至 315.2 百万年前的时期
Bathonium
Bathoniense
Bathon
Bathonien
Baton
Bat
Bathonià
bathon
Bathoniano
Bathoniar
bathi
Bathonian
バトニアン
바토니움절
Batis
Bathoniaan
Батский
bat
Batoniyen
巴通阶
168.2-dən 165.3 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 168.2 a 165.3 milions d'anys enrere
Časové období od 168.2 do 165.3 milionů let před naším letopočtem
Ein Zeitraum von 168.2 bis 165.3 Millionen Jahren
A time period from 168.2 to 165.3 million years ago
Un período de tiempo de 168.2 a 165.3 millones de años atrás
168.2 eta 165.3 milioi urte arteko denbora-tartea
Aikajakso 168.2–165.3 miljoonaa vuotta sitten
Une période de temps de 168.2 à 165.3 millions d'années
Egy 168.2-tól 165.3 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 168.2 hingga 165.3 juta tahun yang lalu
Un periodo di tempo da 168.2 a 165.3 milioni di anni fa
168.2百万年前から165.3百万年前までの時代
168.2백만 년 전부터 165.3백만 년 전까지의 시기
Laikotarpis nuo 168.2 iki 165.3 milijonų metų prieš dabartį
Een tijdperiode van 168.2 tot 165.3 miljoen jaar geleden
Een tijdsperiode van 168.2 tot 165.3 miljoen jaar geleden
En tidsperiode fra 168.2 til 165.3 millioner år siden
Okres czasu od 168.2 do 165.3 milionów lat temu
Um período de tempo de 168.2 a 165.3 milhões de anos atrás
Временной период от 168.2 до 165.3 миллионов лет назад
Časové obdobie od 168.2 do 165.3 miliónov rokov pred naším letopočtom
168.2 ile 165.3 milyon yıl önce arasındaki zaman dilimi
距今 168.2 至 165.3 百万年前的时期
Berriasium
Berriasiense
Berrias
Berriasien
berriasi
Beriasis
Berriasiano
berias
Berriasià
berrias
Berriasiar
Berriasian
ベリアシアン
베리아절
Berriasiaan
Берриасский
Berriaziyen
贝里阿斯阶
143.1-dən 137.05 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 143.1 a 137.05 milions d'anys enrere
Časové období od 143.1 do 137.05 milionů let před naším letopočtem
Ein Zeitraum von 143.1 bis 137.05 Millionen Jahren
A time period from 143.1 to 137.05 million years ago
Un período de tiempo de 143.1 a 137.05 millones de años atrás
143.1 eta 137.05 milioi urte arteko denbora-tartea
Aikajakso 143.1–137.05 miljoonaa vuotta sitten
Une période de temps de 143.1 à 137.05 millions d'années
Egy 143.1-tól 137.05 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 143.1 hingga 137.05 juta tahun yang lalu
Un periodo di tempo da 143.1 a 137.05 milioni di anni fa
143.1百万年前から137.05百万年前までの時代
143.1백만 년 전부터 137.05백만 년 전까지의 시기
Laikotarpis nuo 143.1 iki 137.05 milijonų metų prieš dabartį
Een tijdperiode van 143.1 tot 137.05 miljoen jaar geleden
Een tijdsperiode van 143.1 tot 137.05 miljoen jaar geleden
En tidsperiode fra 143.1 til 137.05 millioner år siden
Okres czasu od 143.1 do 137.05 milionów lat temu
Um período de tempo de 143.1 a 137.05 milhões de anos atrás
Временной период от 143.1 до 137.05 миллионов лет назад
Časové obdobie od 143.1 do 137.05 miliónov rokov pred naším letopočtom
143.1 ile 137.05 milyon yıl önce arasındaki zaman dilimi
距今 143.1 至 137.05 百万年前的时期
Burdigalium
Burdigaliense
Burdigalien
burdigaliai
Burdigalis
Burdigaliano
burdigal
Burdiqal
Burdigalià
Burdigaliar
Burdigala
Burdigalian
バーディガリアン
부르디갈라절
Burdigaliaan
Burdigal
Бурдигальский
Burdigaliyen
波尔多阶
20.45-dən 15.98 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 20.45 a 15.98 milions d'anys enrere
Časové období od 20.45 do 15.98 milionů let před naším letopočtem
Ein Zeitraum von 20.45 bis 15.98 Millionen Jahren
A time period from 20.45 to 15.98 million years ago
Un período de tiempo de 20.45 a 15.98 millones de años atrás
20.45 eta 15.98 milioi urte arteko denbora-tartea
Aikajakso 20.45–15.98 miljoonaa vuotta sitten
Une période de temps de 20.45 à 15.98 millions d'années
Egy 20.45-tól 15.98 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 20.45 hingga 15.98 juta tahun yang lalu
Un periodo di tempo da 20.45 a 15.98 milioni di anni fa
20.45百万年前から15.98百万年前までの時代
20.45백만 년 전부터 15.98백만 년 전까지의 시기
Laikotarpis nuo 20.45 iki 15.98 milijonų metų prieš dabartį
Een tijdperiode van 20.45 tot 15.98 miljoen jaar geleden
Een tijdsperiode van 20.45 tot 15.98 miljoen jaar geleden
En tidsperiode fra 20.45 til 15.98 millioner år siden
Okres czasu od 20.45 do 15.98 milionów lat temu
Um período de tempo de 20.45 a 15.98 milhões de anos atrás
Временной период от 20.45 до 15.98 миллионов лет назад
Časové obdobie od 20.45 do 15.98 miliónov rokov pred naším letopočtom
20.45 ile 15.98 milyon yıl önce arasındaki zaman dilimi
距今 20.45 至 15.98 百万年前的时期
Calabrium
Calabriense
Calabria
Calabrien
Kalabris
Calabriano
Kalabriya
Calabrià
kalábr
Calabriar
calabriai
Calabrian
カラブリアン
칼라브리아절
Calabriaan
Kalabryjski
Калабрийский
kaláber
Kalabriyen
卡拉布里雅阶
1.80-dən 0.774 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 1.80 a 0.774 milions d'anys enrere
Časové období od 1.80 do 0.774 milionů let před naším letopočtem
Ein Zeitraum von 1.80 bis 0.774 Millionen Jahren
A time period from 1.80 to 0.774 million years ago
Un período de tiempo de 1.80 a 0.774 millones de años atrás
1.80 eta 0.774 milioi urte arteko denbora-tartea
Aikajakso 1.80–0.774 miljoonaa vuotta sitten
Une période de temps de 1.80 à 0.774 millions d'années
Egy 1.80-tól 0.774 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 1.80 hingga 0.774 juta tahun yang lalu
Un periodo di tempo da 1.80 a 0.774 milioni di anni fa
1.80百万年前から0.774百万年前までの時代
1.80백만 년 전부터 0.774백만 년 전까지의 시기
Laikotarpis nuo 1.80 iki 0.774 milijonų metų prieš dabartį
Een tijdperiode van 1.80 tot 0.774 miljoen jaar geleden
Een tijdsperiode van 1.80 tot 0.774 miljoen jaar geleden
En tidsperiode fra 1.80 til 0.774 millioner år siden
Okres czasu od 1.80 do 0.774 milionów lat temu
Um período de tempo de 1.80 a 0.774 milhões de anos atrás
Временной период от 1.80 до 0.774 миллионов лет назад
Časové obdobie od 1.80 do 0.774 miliónov rokov pred naším letopočtom
1.80 ile 0.774 milyon yıl önce arasındaki zaman dilimi
距今 1.80 至 0.774 百万年前的时期
Callovium
Calloviense
Callov
Callovien
callovi
Kelovėjis
Kelowej
kelovej
Kellovey
Cal·lovià
callovian
Calloviano
Calloviar
Callovian
カロビアン
칼로비움절
Calloviaan
Келловейский
Kalloviyen
卡洛夫阶
165.3-dən 161.5 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 165.3 a 161.5 milions d'anys enrere
Časové období od 165.3 do 161.5 milionů let před naším letopočtem
Ein Zeitraum von 165.3 bis 161.5 Millionen Jahren
A time period from 165.3 to 161.5 million years ago
Un período de tiempo de 165.3 a 161.5 millones de años atrás
165.3 eta 161.5 milioi urte arteko denbora-tartea
Aikajakso 165.3–161.5 miljoonaa vuotta sitten
Une période de temps de 165.3 à 161.5 millions d'années
Egy 165.3-tól 161.5 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 165.3 hingga 161.5 juta tahun yang lalu
Un periodo di tempo da 165.3 a 161.5 milioni di anni fa
165.3百万年前から161.5百万年前までの時代
165.3백만 년 전부터 161.5백만 년 전까지의 시기
Laikotarpis nuo 165.3 iki 161.5 milijonų metų prieš dabartį
Een tijdperiode van 165.3 tot 161.5 miljoen jaar geleden
Een tijdsperiode van 165.3 tot 161.5 miljoen jaar geleden
En tidsperiode fra 165.3 til 161.5 millioner år siden
Okres czasu od 165.3 do 161.5 milionów lat temu
Um período de tempo de 165.3 a 161.5 milhões de anos atrás
Временной период от 165.3 до 161.5 миллионов лет назад
Časové obdobie od 165.3 do 161.5 miliónov rokov pred naším letopočtom
165.3 ile 161.5 milyon yıl önce arasındaki zaman dilimi
距今 165.3 至 161.5 百万年前的时期
Mərtəbə 10
Desè estatge
stupeň 10
Stufe 10
Piso 10
10 Estai
Vaihe 10
Étage 10
10. emelet
Jenjang 10
Piano 10
ステージ 10
제10절
10 aukštas
Etage 10
Etasje 10
Piętro 10
Andar 10
Ярус 10
Kat 10
第十阶
491.0-dən 486.85 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 491.0 a 486.85 milions d'anys enrere
Časové období od 491.0 do 486.85 milionů let před naším letopočtem
Ein Zeitraum von 491.0 bis 486.85 Millionen Jahren
A time period from 491.0 to 486.85 million years ago
Un período de tiempo de 491.0 a 486.85 millones de años atrás
491.0 eta 486.85 milioi urte arteko denbora-tartea
Aikajakso 491.0–486.85 miljoonaa vuotta sitten
Une période de temps de 491.0 à 486.85 millions d'années
Egy 491.0-tól 486.85 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 491.0 hingga 486.85 juta tahun yang lalu
Un periodo di tempo da 491.0 a 486.85 milioni di anni fa
491.0百万年前から486.85百万年前までの時代
491.0백만 년 전부터 486.85백만 년 전까지의 시기
Laikotarpis nuo 491.0 iki 486.85 milijonų metų prieš dabartį
Een tijdperiode van 491.0 tot 486.85 miljoen jaar geleden
Een tijdsperiode van 491.0 tot 486.85 miljoen jaar geleden
En tidsperiode fra 491.0 til 486.85 millioner år siden
Okres czasu od 491.0 do 486.85 milionów lat temu
Um período de tempo de 491.0 a 486.85 milhões de anos atrás
Временной период от 491.0 до 486.85 миллионов лет назад
Časové obdobie od 491.0 do 486.85 miliónov rokov pred naším letopočtom
491.0 ile 486.85 milyon yıl önce arasındaki zaman dilimi
距今 491.0 至 486.85 百万年前的时期
Stage 10
Mərtəbə 2
Segon estatge
stupeň 2
Stufe 2
Piso 2
2 Estai
Vaihe 2
Étage 2
2. emelet
Jenjang 2
Piano 2
ステージ 2
제2절
2 aukštas
Etage 2
Etasje 2
Piętro 2
Andar 2
Ярус 2
Kat 2
第二阶
529.0-dən 521.0 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 529.0 a 521.0 milions d'anys enrere
Časové období od 529.0 do 521.0 milionů let před naším letopočtem
Ein Zeitraum von 529.0 bis 521.0 Millionen Jahren
A time period from 529.0 to 521.0 million years ago
Un período de tiempo de 529.0 a 521.0 millones de años atrás
529.0 eta 521.0 milioi urte arteko denbora-tartea
Aikajakso 529.0–521.0 miljoonaa vuotta sitten
Une période de temps de 529.0 à 521.0 millions d'années
Egy 529.0-tól 521.0 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 529.0 hingga 521.0 juta tahun yang lalu
Un periodo di tempo da 529.0 a 521.0 milioni di anni fa
529.0百万年前から521.0百万年前までの時代
529.0백만 년 전부터 521.0백만 년 전까지의 시기
Laikotarpis nuo 529.0 iki 521.0 milijonų metų prieš dabartį
Een tijdperiode van 529.0 tot 521.0 miljoen jaar geleden
Een tijdsperiode van 529.0 tot 521.0 miljoen jaar geleden
En tidsperiode fra 529.0 til 521.0 millioner år siden
Okres czasu od 529.0 do 521.0 milionów lat temu
Um período de tempo de 529.0 a 521.0 milhões de anos atrás
Временной период от 529.0 до 521.0 миллионов лет назад
Časové obdobie od 529.0 do 521.0 miliónov rokov pred naším letopočtom
529.0 ile 521.0 milyon yıl önce arasındaki zaman dilimi
距今 529.0 至 521.0 百万年前的时期
Stage 2
Mərtəbə 3
Tercer estatge
stupeň 3
Stufe 3
Piso 3
3 Estai
Vaihe 3
Étage 3
3. emelet
Jenjang 3
Piano 3
ステージ 3
제3절
3 aukštas
Etage 3
Etasje 3
Piętro 3
Andar 3
Ярус 3
Kat 3
第三阶
521.0-dən 514.5 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 521.0 a 514.5 milions d'anys enrere
Časové období od 521.0 do 514.5 milionů let před naším letopočtem
Ein Zeitraum von 521.0 bis 514.5 Millionen Jahren
A time period from 521.0 to 514.5 million years ago
Un período de tiempo de 521.0 a 514.5 millones de años atrás
521.0 eta 514.5 milioi urte arteko denbora-tartea
Aikajakso 521.0–514.5 miljoonaa vuotta sitten
Une période de temps de 521.0 à 514.5 millions d'années
Egy 521.0-tól 514.5 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 521.0 hingga 514.5 juta tahun yang lalu
Un periodo di tempo da 521.0 a 514.5 milioni di anni fa
521.0百万年前から514.5百万年前までの時代
521.0백만 년 전부터 514.5백만 년 전까지의 시기
Laikotarpis nuo 521.0 iki 514.5 milijonų metų prieš dabartį
Een tijdperiode van 521.0 tot 514.5 miljoen jaar geleden
Een tijdsperiode van 521.0 tot 514.5 miljoen jaar geleden
En tidsperiode fra 521.0 til 514.5 millioner år siden
Okres czasu od 521.0 do 514.5 milionów lat temu
Um período de tempo de 521.0 a 514.5 milhões de anos atrás
Временной период от 521.0 до 514.5 миллионов лет назад
Časové obdobie od 521.0 do 514.5 miliónov rokov pred naším letopočtom
521.0 ile 514.5 milyon yıl önce arasındaki zaman dilimi
距今 521.0 至 514.5 百万年前的时期
Stage 3
Mərtəbə 4
Quart estatge
stupeň 4
Stufe 4
Piso 4
4 Estai
Vaihe 4
Étage 4
4. emelet
Jenjang 4
Piano 4
ステージ 4
제4절
4 aukštas
Etage 4
Etasje 4
Piętro 4
Andar 4
Ярус 4
Kat 4
第四阶
514.5-dən 506.5 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 514.5 a 506.5 milions d'anys enrere
Časové období od 514.5 do 506.5 milionů let před naším letopočtem
Ein Zeitraum von 514.5 bis 506.5 Millionen Jahren
A time period from 514.5 to 506.5 million years ago
Un período de tiempo de 514.5 a 506.5 millones de años atrás
514.5 eta 506.5 milioi urte arteko denbora-tartea
Aikajakso 514.5–506.5 miljoonaa vuotta sitten
Une période de temps de 514.5 à 506.5 millions d'années
Egy 514.5-tól 506.5 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 514.5 hingga 506.5 juta tahun yang lalu
Un periodo di tempo da 514.5 a 506.5 milioni di anni fa
514.5百万年前から506.5百万年前までの時代
514.5백만 년 전부터 506.5백만 년 전까지의 시기
Laikotarpis nuo 514.5 iki 506.5 milijonų metų prieš dabartį
Een tijdperiode van 514.5 tot 506.5 miljoen jaar geleden
Een tijdsperiode van 514.5 tot 506.5 miljoen jaar geleden
En tidsperiode fra 514.5 til 506.5 millioner år siden
Okres czasu od 514.5 do 506.5 milionów lat temu
Um período de tempo de 514.5 a 506.5 milhões de anos atrás
Временной период от 514.5 до 506.5 миллионов лет назад
Časové obdobie od 514.5 do 506.5 miliónov rokov pred naším letopočtom
514.5 ile 506.5 milyon yıl önce arasındaki zaman dilimi
距今 514.5 至 506.5 百万年前的时期
Stage 4
Campanium
Campaniense
Campanien
Kampanis
Kampan
Campaniano
kampán
Campanià
Campaniar
Campania
campani
Campanian
カンパニアン
캄파이나절
Campaniaan
Campan
Кампанский
Kampaniyen
坎潘阶
83.6-dən 72.2 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 83.6 a 72.2 milions d'anys enrere
Časové období od 83.6 do 72.2 milionů let před naším letopočtem
Ein Zeitraum von 83.6 bis 72.2 Millionen Jahren
A time period from 83.6 to 72.2 million years ago
Un período de tiempo de 83.6 a 72.2 millones de años atrás
83.6 eta 72.2 milioi urte arteko denbora-tartea
Aikajakso 83.6–72.2 miljoonaa vuotta sitten
Une période de temps de 83.6 à 72.2 millions d'années
Egy 83.6-tól 72.2 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 83.6 hingga 72.2 juta tahun yang lalu
Un periodo di tempo da 83.6 a 72.2 milioni di anni fa
83.6百万年前から72.2百万年前までの時代
83.6백만 년 전부터 72.2백만 년 전까지의 시기
Laikotarpis nuo 83.6 iki 72.2 milijonų metų prieš dabartį
Een tijdperiode van 83.6 tot 72.2 miljoen jaar geleden
Een tijdsperiode van 83.6 tot 72.2 miljoen jaar geleden
En tidsperiode fra 83.6 til 72.2 millioner år siden
Okres czasu od 83.6 do 72.2 milionów lat temu
Um período de tempo de 83.6 a 72.2 milhões de anos atrás
Временной период от 83.6 до 72.2 миллионов лет назад
Časové obdobie od 83.6 do 72.2 miliónov rokov pred naším letopočtom
83.6 ile 72.2 milyon yıl önce arasındaki zaman dilimi
距今 83.6 至 72.2 百万年前的时期
Capitanium
Capitaniense
Capitan
Capitanien
capitani
Kapitanis
Kapitan
Capitaniano
Capitanià
capitan
Capitaniar
Capitanian
キャピタニアン
캐피탄절
Capitaniaan
Кептенский
kapitan
Kapitaniyen
卡匹敦阶
264.28-dən 259.857 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 264.28 a 259.857 milions d'anys enrere
Časové období od 264.28 do 259.857 milionů let před naším letopočtem
Ein Zeitraum von 264.28 bis 259.857 Millionen Jahren
A time period from 264.28 to 259.857 million years ago
Un período de tiempo de 264.28 a 259.857 millones de años atrás
264.28 eta 259.857 milioi urte arteko denbora-tartea
Aikajakso 264.28–259.857 miljoonaa vuotta sitten
Une période de temps de 264.28 à 259.857 millions d'années
Egy 264.28-tól 259.857 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 264.28 hingga 259.857 juta tahun yang lalu
Un periodo di tempo da 264.28 a 259.857 milioni di anni fa
264.28百万年前から259.857百万年前までの時代
264.28백만 년 전부터 259.857백만 년 전까지의 시기
Laikotarpis nuo 264.28 iki 259.857 milijonų metų prieš dabartį
Een tijdperiode van 264.28 tot 259.857 miljoen jaar geleden
Een tijdsperiode van 264.28 tot 259.857 miljoen jaar geleden
En tidsperiode fra 264.28 til 259.857 millioner år siden
Okres czasu od 264.28 do 259.857 milionów lat temu
Um período de tempo de 264.28 a 259.857 milhões de anos atrás
Временной период от 264.28 до 259.857 миллионов лет назад
Časové obdobie od 264.28 do 259.857 miliónov rokov pred naším letopočtom
264.28 ile 259.857 milyon yıl önce arasındaki zaman dilimi
距今 264.28 至 259.857 百万年前的时期
Karnium
Carniense
Carn
Carnien
karni
Karnis
Karnik
Carniano
karn
Karniy
Carnià
Carniar
Carnian
Carnico
カーニアン
카닉절
Carniaan
Karn
Карнийский
Karniyen
卡尼阶
237-dən 227.3 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 237 a 227.3 milions d'anys enrere
Časové období od 237 do 227.3 milionů let před naším letopočtem
Ein Zeitraum von 237 bis 227.3 Millionen Jahren
A time period from 237 to 227.3 million years ago
Un período de tiempo de 237 a 227.3 millones de años atrás
237 eta 227.3 milioi urte arteko denbora-tartea
Aikajakso 237–227.3 miljoonaa vuotta sitten
Une période de temps de 237 à 227.3 millions d'années
Egy 237-tól 227.3 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 237 hingga 227.3 juta tahun yang lalu
Un periodo di tempo da 237 a 227.3 milioni di anni fa
237百万年前から227.3百万年前までの時代
237백만 년 전부터 227.3백만 년 전까지의 시기
Laikotarpis nuo 237 iki 227.3 milijonų metų prieš dabartį
Een tijdperiode van 237 tot 227.3 miljoen jaar geleden
Een tijdsperiode van 237 tot 227.3 miljoen jaar geleden
En tidsperiode fra 237 til 227.3 millioner år siden
Okres czasu od 237 do 227.3 milionów lat temu
Um período de tempo de 237 a 227.3 milhões de anos atrás
Временной период от 237 до 227.3 миллионов лет назад
Časové obdobie od 237 do 227.3 miliónov rokov pred naším letopočtom
237 ile 227.3 milyon yıl önce arasındaki zaman dilimi
距今 237 至 227.3 百万年前的时期
Cenomanium
Cenomaniense
Cenoman
Cénomanien
Cenomanis
Cenomaniano
cenoman
Senoman
Cenomanià
Cenomaniar
cenomani
Cenomanian
セノマニアン
세노마눔절
Cenomanien
Cenomaniaan
Сеноманский
Senomaniyen
塞诺曼阶
100.5-dən 93.9 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 100.5 a 93.9 milions d'anys enrere
Časové období od 100.5 do 93.9 milionů let před naším letopočtem
Ein Zeitraum von 100.5 bis 93.9 Millionen Jahren
A time period from 100.5 to 93.9 million years ago
Un período de tiempo de 100.5 a 93.9 millones de años atrás
100.5 eta 93.9 milioi urte arteko denbora-tartea
Aikajakso 100.5–93.9 miljoonaa vuotta sitten
Une période de temps de 100.5 à 93.9 millions d'années
Egy 100.5-tól 93.9 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 100.5 hingga 93.9 juta tahun yang lalu
Un periodo di tempo da 100.5 a 93.9 milioni di anni fa
100.5百万年前から93.9百万年前までの時代
100.5백만 년 전부터 93.9백만 년 전까지의 시기
Laikotarpis nuo 100.5 iki 93.9 milijonų metų prieš dabartį
Een tijdperiode van 100.5 tot 93.9 miljoen jaar geleden
Een tijdsperiode van 100.5 tot 93.9 miljoen jaar geleden
En tidsperiode fra 100.5 til 93.9 millioner år siden
Okres czasu od 100.5 do 93.9 milionów lat temu
Um período de tempo de 100.5 a 93.9 milhões de anos atrás
Временной период от 100.5 до 93.9 миллионов лет назад
Časové obdobie od 100.5 do 93.9 miliónov rokov pred naším letopočtom
100.5 ile 93.9 milyon yıl önce arasındaki zaman dilimi
距今 100.5 至 93.9 百万年前的时期
Changhsingium
Changhsing
Changhsingien
changhsingi
Changhsingiano
Çanqsin
Changxingià
changhsing
Changhsingiense
Changhsingiar
Changhsingian
チャンシンジアン
창싱절
Čiangsingis
Changhsingiaan
Changxing
Чансинский
čchangsing
Çangsingiyen
长兴阶
254.14-dən 251.902 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 254.14 a 251.902 milions d'anys enrere
Časové období od 254.14 do 251.902 milionů let před naším letopočtem
Ein Zeitraum von 254.14 bis 251.902 Millionen Jahren
A time period from 254.14 to 251.902 million years ago
Un período de tiempo de 254.14 a 251.902 millones de años atrás
254.14 eta 251.902 milioi urte arteko denbora-tartea
Aikajakso 254.14–251.902 miljoonaa vuotta sitten
Une période de temps de 254.14 à 251.902 millions d'années
Egy 254.14-tól 251.902 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 254.14 hingga 251.902 juta tahun yang lalu
Un periodo di tempo da 254.14 a 251.902 milioni di anni fa
254.14百万年前から251.902百万年前までの時代
254.14백만 년 전부터 251.902백만 년 전까지의 시기
Laikotarpis nuo 254.14 iki 251.902 milijonų metų prieš dabartį
Een tijdperiode van 254.14 tot 251.902 miljoen jaar geleden
Een tijdsperiode van 254.14 tot 251.902 miljoen jaar geleden
En tidsperiode fra 254.14 til 251.902 millioner år siden
Okres czasu od 254.14 do 251.902 milionów lat temu
Um período de tempo de 254.14 a 251.902 milhões de anos atrás
Временной период от 254.14 до 251.902 миллионов лет назад
Časové obdobie od 254.14 do 251.902 miliónov rokov pred naším letopočtom
254.14 ile 251.902 milyon yıl önce arasındaki zaman dilimi
距今 254.14 至 251.902 百万年前的时期
Chattium
Chattiense
Chatt
Chattien
katti
Chatis
Hat
Catià
chatt
Chattiano
Chattiar
Chattian
Cattiano
チャッティアン
카티절
Chattiaan
Хаттский
chat
Şattiyen
夏特阶
27.30-dən 23.04 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 27.30 a 23.04 milions d'anys enrere
Časové období od 27.30 do 23.04 milionů let před naším letopočtem
Ein Zeitraum von 27.30 bis 23.04 Millionen Jahren
A time period from 27.30 to 23.04 million years ago
Un período de tiempo de 27.30 a 23.04 millones de años atrás
27.30 eta 23.04 milioi urte arteko denbora-tartea
Aikajakso 27.30–23.04 miljoonaa vuotta sitten
Une période de temps de 27.30 à 23.04 millions d'années
Egy 27.30-tól 23.04 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 27.30 hingga 23.04 juta tahun yang lalu
Un periodo di tempo da 27.30 a 23.04 milioni di anni fa
27.30百万年前から23.04百万年前までの時代
27.30백만 년 전부터 23.04백만 년 전까지의 시기
Laikotarpis nuo 27.30 iki 23.04 milijonų metų prieš dabartį
Een tijdperiode van 27.30 tot 23.04 miljoen jaar geleden
Een tijdsperiode van 27.30 tot 23.04 miljoen jaar geleden
En tidsperiode fra 27.30 til 23.04 millioner år siden
Okres czasu od 27.30 do 23.04 milionów lat temu
Um período de tempo de 27.30 a 23.04 milhões de anos atrás
Временной период от 27.30 до 23.04 миллионов лет назад
Časové obdobie od 27.30 do 23.04 miliónov rokov pred naším letopočtom
27.30 ile 23.04 milyon yıl önce arasındaki zaman dilimi
距今 27.30 至 23.04 百万年前的时期
Çiba
Chibanià
chiban
Chibanium
Chibaniense
Chibaniano
Erdi
Chiba
Chibanien
csibai
Chibanian
チバニアン
지바절
Čibanis
Chibaien
Chibaiaan
Chibański
Средний
čiba
Çibaniyen
千叶阶
0.774-dən 0.129 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 0.774 a 0.129 milions d'anys enrere
Časové období od 0.774 do 0.129 milionů let před naším letopočtem
Ein Zeitraum von 0.774 bis 0.129 Millionen Jahren
A time period from 0.774 to 0.129 million years ago
Un período de tiempo de 0.774 a 0.129 millones de años atrás
0.774 eta 0.129 milioi urte arteko denbora-tartea
Aikajakso 0.774–0.129 miljoonaa vuotta sitten
Une période de temps de 0.774 à 0.129 millions d'années
Egy 0.774-tól 0.129 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 0.774 hingga 0.129 juta tahun yang lalu
Un periodo di tempo da 0.774 a 0.129 milioni di anni fa
0.774百万年前から0.129百万年前までの時代
0.774백만 년 전부터 0.129백만 년 전까지의 시기
Laikotarpis nuo 0.774 iki 0.129 milijonų metų prieš dabartį
Een tijdperiode van 0.774 tot 0.129 miljoen jaar geleden
Een tijdsperiode van 0.774 tot 0.129 miljoen jaar geleden
En tidsperiode fra 0.774 til 0.129 millioner år siden
Okres czasu od 0.774 do 0.129 milionów lat temu
Um período de tempo de 0.774 a 0.129 milhões de anos atrás
Временной период от 0.774 до 0.129 миллионов лет назад
Časové obdobie od 0.774 do 0.129 miliónov rokov pred naším letopočtom
0.774 ile 0.129 milyon yıl önce arasındaki zaman dilimi
距今 0.774 至 0.129 百万年前的时期
Coniacium
Coniacien
coniaci
Konjakis
Koniak
Coniaciano
koňak
Konyak
Coniacià
coniak
Coniaciense
Coniaciar
Cognac
Coniacian
コニアシアン
코냑절
Coniaciaan
Coniac
Коньякский
Koniasiyen
康尼亚克阶
89.8-dən 85.7 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 89.8 a 85.7 milions d'anys enrere
Časové období od 89.8 do 85.7 milionů let před naším letopočtem
Ein Zeitraum von 89.8 bis 85.7 Millionen Jahren
A time period from 89.8 to 85.7 million years ago
Un período de tiempo de 89.8 a 85.7 millones de años atrás
89.8 eta 85.7 milioi urte arteko denbora-tartea
Aikajakso 89.8–85.7 miljoonaa vuotta sitten
Une période de temps de 89.8 à 85.7 millions d'années
Egy 89.8-tól 85.7 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 89.8 hingga 85.7 juta tahun yang lalu
Un periodo di tempo da 89.8 a 85.7 milioni di anni fa
89.8百万年前から85.7百万年前までの時代
89.8백만 년 전부터 85.7백만 년 전까지의 시기
Laikotarpis nuo 89.8 iki 85.7 milijonų metų prieš dabartį
Een tijdperiode van 89.8 tot 85.7 miljoen jaar geleden
Een tijdsperiode van 89.8 tot 85.7 miljoen jaar geleden
En tidsperiode fra 89.8 til 85.7 millioner år siden
Okres czasu od 89.8 do 85.7 milionów lat temu
Um período de tempo de 89.8 a 85.7 milhões de anos atrás
Временной период от 89.8 до 85.7 миллионов лет назад
Časové obdobie od 89.8 do 85.7 miliónov rokov pred naším letopočtom
89.8 ile 85.7 milyon yıl önce arasındaki zaman dilimi
距今 89.8 至 85.7 百万年前的时期
Danium
Danien
dániai
Danis
Dan
Daniano
dán
Danimarka
Danià
dan
Daniense
Daniar
Dania
Danian
ダニアン
다니아절
Daniaan
Датский
Daniyen
丹麦阶
66.00-dən 61.66 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 66.00 a 61.66 milions d'anys enrere
Časové období od 66.00 do 61.66 milionů let před naším letopočtem
Ein Zeitraum von 66.00 bis 61.66 Millionen Jahren
A time period from 66.00 to 61.66 million years ago
Un período de tiempo de 66.00 a 61.66 millones de años atrás
66.00 eta 61.66 milioi urte arteko denbora-tartea
Aikajakso 66.00–61.66 miljoonaa vuotta sitten
Une période de temps de 66.00 à 61.66 millions d'années
Egy 66.00-tól 61.66 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 66.00 hingga 61.66 juta tahun yang lalu
Un periodo di tempo da 66.00 a 61.66 milioni di anni fa
66.00百万年前から61.66百万年前までの時代
66.00백만 년 전부터 61.66백만 년 전까지의 시기
Laikotarpis nuo 66.00 iki 61.66 milijonų metų prieš dabartį
Een tijdperiode van 66.00 tot 61.66 miljoen jaar geleden
Een tijdsperiode van 66.00 tot 61.66 miljoen jaar geleden
En tidsperiode fra 66.00 til 61.66 millioner år siden
Okres czasu od 66.00 do 61.66 milionów lat temu
Um período de tempo de 66.00 a 61.66 milhões de anos atrás
Временной период от 66.00 до 61.66 миллионов лет назад
Časové obdobie od 66.00 do 61.66 miliónov rokov pred naším letopočtom
66.00 ile 61.66 milyon yıl önce arasındaki zaman dilimi
距今 66.00 至 61.66 百万年前的时期
Dapingium
Dapingiense
Daping
Dapingien
dapingi
Dapingis
Dapingiano
daping
Dapinq
Dapingià
Dapingiar
Dapingian
ダーピンジアン
다핑절
Dapingiaan
Дапинский
Dapingiyen
大坪阶
471.3-dən 469.4 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 471.3 a 469.4 milions d'anys enrere
Časové období od 471.3 do 469.4 milionů let před naším letopočtem
Ein Zeitraum von 471.3 bis 469.4 Millionen Jahren
A time period from 471.3 to 469.4 million years ago
Un período de tiempo de 471.3 a 469.4 millones de años atrás
471.3 eta 469.4 milioi urte arteko denbora-tartea
Aikajakso 471.3–469.4 miljoonaa vuotta sitten
Une période de temps de 471.3 à 469.4 millions d'années
Egy 471.3-tól 469.4 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 471.3 hingga 469.4 juta tahun yang lalu
Un periodo di tempo da 471.3 a 469.4 milioni di anni fa
471.3百万年前から469.4百万年前までの時代
471.3백만 년 전부터 469.4백만 년 전까지의 시기
Laikotarpis nuo 471.3 iki 469.4 milijonų metų prieš dabartį
Een tijdperiode van 471.3 tot 469.4 miljoen jaar geleden
Een tijdsperiode van 471.3 tot 469.4 miljoen jaar geleden
En tidsperiode fra 471.3 til 469.4 millioner år siden
Okres czasu od 471.3 do 469.4 milionów lat temu
Um período de tempo de 471.3 a 469.4 milhões de anos atrás
Временной период от 471.3 до 469.4 миллионов лет назад
Časové obdobie od 471.3 do 469.4 miliónov rokov pred naším letopočtom
471.3 ile 469.4 milyon yıl önce arasındaki zaman dilimi
距今 471.3 至 469.4 百万年前的时期
Darriwilium
Darriwiliense
Darriwil
Darriwilien
darriwili
Darriwiliano
Darrivil
Darriwilià
darriwil
Darriwiliar
Darriwilian
ダリウィリアン
다리윌절
Darvilis
Darriwiliaan
Дарривильский
dariwil
Darriviliyen
达瑞威尔阶
469.4-dən 458.2 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 469.4 a 458.2 milions d'anys enrere
Časové období od 469.4 do 458.2 milionů let před naším letopočtem
Ein Zeitraum von 469.4 bis 458.2 Millionen Jahren
A time period from 469.4 to 458.2 million years ago
Un período de tiempo de 469.4 a 458.2 millones de años atrás
469.4 eta 458.2 milioi urte arteko denbora-tartea
Aikajakso 469.4–458.2 miljoonaa vuotta sitten
Une période de temps de 469.4 à 458.2 millions d'années
Egy 469.4-tól 458.2 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 469.4 hingga 458.2 juta tahun yang lalu
Un periodo di tempo da 469.4 a 458.2 milioni di anni fa
469.4百万年前から458.2百万年前までの時代
469.4백만 년 전부터 458.2백만 년 전까지의 시기
Laikotarpis nuo 469.4 iki 458.2 milijonų metų prieš dabartį
Een tijdperiode van 469.4 tot 458.2 miljoen jaar geleden
Een tijdsperiode van 469.4 tot 458.2 miljoen jaar geleden
En tidsperiode fra 469.4 til 458.2 millioner år siden
Okres czasu od 469.4 do 458.2 milionów lat temu
Um período de tempo de 469.4 a 458.2 milhões de anos atrás
Временной период от 469.4 до 458.2 миллионов лет назад
Časové obdobie od 469.4 do 458.2 miliónov rokov pred naším letopočtom
469.4 ile 458.2 milyon yıl önce arasındaki zaman dilimi
距今 469.4 至 458.2 百万年前的时期
Drumium
Drumiense
Drum
Drumien
drumi
Drumis
Drumiano
drum
Drumià
Drumiar
Drumian
ドラミアン
드럼절
Drumiaan
Друмский
Drumiyen
鼓山阶
504.5-dən 500.5 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 504.5 a 500.5 milions d'anys enrere
Časové období od 504.5 do 500.5 milionů let před naším letopočtem
Ein Zeitraum von 504.5 bis 500.5 Millionen Jahren
A time period from 504.5 to 500.5 million years ago
Un período de tiempo de 504.5 a 500.5 millones de años atrás
504.5 eta 500.5 milioi urte arteko denbora-tartea
Aikajakso 504.5–500.5 miljoonaa vuotta sitten
Une période de temps de 504.5 à 500.5 millions d'années
Egy 504.5-tól 500.5 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 504.5 hingga 500.5 juta tahun yang lalu
Un periodo di tempo da 504.5 a 500.5 milioni di anni fa
504.5百万年前から500.5百万年前までの時代
504.5백만 년 전부터 500.5백만 년 전까지의 시기
Laikotarpis nuo 504.5 iki 500.5 milijonų metų prieš dabartį
Een tijdperiode van 504.5 tot 500.5 miljoen jaar geleden
Een tijdsperiode van 504.5 tot 500.5 miljoen jaar geleden
En tidsperiode fra 504.5 til 500.5 millioner år siden
Okres czasu od 504.5 do 500.5 milionów lat temu
Um período de tempo de 504.5 a 500.5 milhões de anos atrás
Временной период от 504.5 до 500.5 миллионов лет назад
Časové obdobie od 504.5 do 500.5 miliónov rokov pred naším letopočtom
504.5 ile 500.5 milyon yıl önce arasındaki zaman dilimi
距今 504.5 至 500.5 百万年前的时期
Eifelium
Eifeliense
Eifel
Eifélien
eifeli
Eifelis
Eifeliano
eifel
Eyfel
Eifelià
Eifeliar
Eifelian
アイフェリアン
아이펠절
Eifelien
Eifeliaan
Эйфельский
Eyfeliyen
艾菲尔阶
393.47-dən 387.95 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 393.47 a 387.95 milions d'anys enrere
Časové období od 393.47 do 387.95 milionů let před naším letopočtem
Ein Zeitraum von 393.47 bis 387.95 Millionen Jahren
A time period from 393.47 to 387.95 million years ago
Un período de tiempo de 393.47 a 387.95 millones de años atrás
393.47 eta 387.95 milioi urte arteko denbora-tartea
Aikajakso 393.47–387.95 miljoonaa vuotta sitten
Une période de temps de 393.47 à 387.95 millions d'années
Egy 393.47-tól 387.95 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 393.47 hingga 387.95 juta tahun yang lalu
Un periodo di tempo da 393.47 a 387.95 milioni di anni fa
393.47百万年前から387.95百万年前までの時代
393.47백만 년 전부터 387.95백만 년 전까지의 시기
Laikotarpis nuo 393.47 iki 387.95 milijonų metų prieš dabartį
Een tijdperiode van 393.47 tot 387.95 miljoen jaar geleden
Een tijdsperiode van 393.47 tot 387.95 miljoen jaar geleden
En tidsperiode fra 393.47 til 387.95 millioner år siden
Okres czasu od 393.47 do 387.95 milionów lat temu
Um período de tempo de 393.47 a 387.95 milhões de anos atrás
Временной период от 393.47 до 387.95 миллионов лет назад
Časové obdobie od 393.47 do 387.95 miliónov rokov pred naším letopočtom
393.47 ile 387.95 milyon yıl önce arasındaki zaman dilimi
距今 393.47 至 387.95 百万年前的时期
Emsium
Emsiense
Ems
Emsien
emsi
Emsis
Emsiano
ems
Emsià
Emsiar
Emsian
エムシアン
엠즈절
Emsiaan
Эмсский
Emsiyen
埃姆斯阶
410.62-dən 393.47 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 410.62 a 393.47 milions d'anys enrere
Časové období od 410.62 do 393.47 milionů let před naším letopočtem
Ein Zeitraum von 410.62 bis 393.47 Millionen Jahren
A time period from 410.62 to 393.47 million years ago
Un período de tiempo de 410.62 a 393.47 millones de años atrás
410.62 eta 393.47 milioi urte arteko denbora-tartea
Aikajakso 410.62–393.47 miljoonaa vuotta sitten
Une période de temps de 410.62 à 393.47 millions d'années
Egy 410.62-tól 393.47 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 410.62 hingga 393.47 juta tahun yang lalu
Un periodo di tempo da 410.62 a 393.47 milioni di anni fa
410.62百万年前から393.47百万年前までの時代
410.62백만 년 전부터 393.47백만 년 전까지의 시기
Laikotarpis nuo 410.62 iki 393.47 milijonų metų prieš dabartį
Een tijdperiode van 410.62 tot 393.47 miljoen jaar geleden
Een tijdsperiode van 410.62 tot 393.47 miljoen jaar geleden
En tidsperiode fra 410.62 til 393.47 millioner år siden
Okres czasu od 410.62 do 393.47 milionów lat temu
Um período de tempo de 410.62 a 393.47 milhões de anos atrás
Временной период от 410.62 до 393.47 миллионов лет назад
Časové obdobie od 410.62 do 393.47 miliónov rokov pred naším letopočtom
410.62 ile 393.47 milyon yıl önce arasındaki zaman dilimi
距今 410.62 至 393.47 百万年前的时期
Fameniense
Famennien
famenni
Famenis
Famen
famen
Famennià
Famennium
Famenniano
Famenniar
Famennian
ファメニアン
파멘절
Famenniaan
Famenn
Фаменский
Fameniyen
法门阶
372.15-dən 358.86 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 372.15 a 358.86 milions d'anys enrere
Časové období od 372.15 do 358.86 milionů let před naším letopočtem
Ein Zeitraum von 372.15 bis 358.86 Millionen Jahren
A time period from 372.15 to 358.86 million years ago
Un período de tiempo de 372.15 a 358.86 millones de años atrás
372.15 eta 358.86 milioi urte arteko denbora-tartea
Aikajakso 372.15–358.86 miljoonaa vuotta sitten
Une période de temps de 372.15 à 358.86 millions d'années
Egy 372.15-tól 358.86 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 372.15 hingga 358.86 juta tahun yang lalu
Un periodo di tempo da 372.15 a 358.86 milioni di anni fa
372.15百万年前から358.86百万年前までの時代
372.15백만 년 전부터 358.86백만 년 전까지의 시기
Laikotarpis nuo 372.15 iki 358.86 milijonų metų prieš dabartį
Een tijdperiode van 372.15 tot 358.86 miljoen jaar geleden
Een tijdsperiode van 372.15 tot 358.86 miljoen jaar geleden
En tidsperiode fra 372.15 til 358.86 millioner år siden
Okres czasu od 372.15 do 358.86 milionów lat temu
Um período de tempo de 372.15 a 358.86 milhões de anos atrás
Временной период от 372.15 до 358.86 миллионов лет назад
Časové obdobie od 372.15 do 358.86 miliónov rokov pred naším letopočtom
372.15 ile 358.86 milyon yıl önce arasındaki zaman dilimi
距今 372.15 至 358.86 百万年前的时期
Floium
Floiense
Flo
Floien
floi
Flois
Floiano
flo
Floià
floian
Floiar
Floian
フロイアン
플로절
Floiaan
Flojan
Флоский
Floyen
弗洛阶
477.1-dən 471.3 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 477.1 a 471.3 milions d'anys enrere
Časové období od 477.1 do 471.3 milionů let před naším letopočtem
Ein Zeitraum von 477.1 bis 471.3 Millionen Jahren
A time period from 477.1 to 471.3 million years ago
Un período de tiempo de 477.1 a 471.3 millones de años atrás
477.1 eta 471.3 milioi urte arteko denbora-tartea
Aikajakso 477.1–471.3 miljoonaa vuotta sitten
Une période de temps de 477.1 à 471.3 millions d'années
Egy 477.1-tól 471.3 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 477.1 hingga 471.3 juta tahun yang lalu
Un periodo di tempo da 477.1 a 471.3 milioni di anni fa
477.1百万年前から471.3百万年前までの時代
477.1백만 년 전부터 471.3백만 년 전까지의 시기
Laikotarpis nuo 477.1 iki 471.3 milijonų metų prieš dabartį
Een tijdperiode van 477.1 tot 471.3 miljoen jaar geleden
Een tijdsperiode van 477.1 tot 471.3 miljoen jaar geleden
En tidsperiode fra 477.1 til 471.3 millioner år siden
Okres czasu od 477.1 do 471.3 milionów lat temu
Um período de tempo de 477.1 a 471.3 milhões de anos atrás
Временной период от 477.1 до 471.3 миллионов лет назад
Časové obdobie od 477.1 do 471.3 miliónov rokov pred naším letopočtom
477.1 ile 471.3 milyon yıl önce arasındaki zaman dilimi
距今 477.1 至 471.3 百万年前的时期
Fortunium
Fortuniense
Fortunien
fortuni
Fortunis
Fortuniano
fortun
Fortun
Fortunià
Fortuniar
Fortune
Fortunian
フォーチュニアン
포츈절
Fortuniaan
Фортунский
Fortuniyen
幸运阶
538.8-dən 529.0 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 538.8 a 529.0 milions d'anys enrere
Časové období od 538.8 do 529.0 milionů let před naším letopočtem
Ein Zeitraum von 538.8 bis 529.0 Millionen Jahren
A time period from 538.8 to 529.0 million years ago
Un período de tiempo de 538.8 a 529.0 millones de años atrás
538.8 eta 529.0 milioi urte arteko denbora-tartea
Aikajakso 538.8–529.0 miljoonaa vuotta sitten
Une période de temps de 538.8 à 529.0 millions d'années
Egy 538.8-tól 529.0 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 538.8 hingga 529.0 juta tahun yang lalu
Un periodo di tempo da 538.8 a 529.0 milioni di anni fa
538.8百万年前から529.0百万年前までの時代
538.8백만 년 전부터 529.0백만 년 전까지의 시기
Laikotarpis nuo 538.8 iki 529.0 milijonų metų prieš dabartį
Een tijdperiode van 538.8 tot 529.0 miljoen jaar geleden
Een tijdsperiode van 538.8 tot 529.0 miljoen jaar geleden
En tidsperiode fra 538.8 til 529.0 millioner år siden
Okres czasu od 538.8 do 529.0 milionów lat temu
Um período de tempo de 538.8 a 529.0 milhões de anos atrás
Временной период от 538.8 до 529.0 миллионов лет назад
Časové obdobie od 538.8 do 529.0 miliónov rokov pred naším letopočtom
538.8 ile 529.0 milyon yıl önce arasındaki zaman dilimi
距今 538.8 至 529.0 百万年前的时期
Frasnium
Frasniense
Frasnien
frasni
Franis
Frasniano
Frans
Frasnià
frasn
Frasniar
Frasne
Frasnian
フラニアン
프랜절
Frasniaan
Frasn
Франский
fran
Frasniyen
弗拉阶
382.31-dən 372.15 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 382.31 a 372.15 milions d'anys enrere
Časové období od 382.31 do 372.15 milionů let před naším letopočtem
Ein Zeitraum von 382.31 bis 372.15 Millionen Jahren
A time period from 382.31 to 372.15 million years ago
Un período de tiempo de 382.31 a 372.15 millones de años atrás
382.31 eta 372.15 milioi urte arteko denbora-tartea
Aikajakso 382.31–372.15 miljoonaa vuotta sitten
Une période de temps de 382.31 à 372.15 millions d'années
Egy 382.31-tól 372.15 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 382.31 hingga 372.15 juta tahun yang lalu
Un periodo di tempo da 382.31 a 372.15 milioni di anni fa
382.31百万年前から372.15百万年前までの時代
382.31백만 년 전부터 372.15백만 년 전까지의 시기
Laikotarpis nuo 382.31 iki 372.15 milijonų metų prieš dabartį
Een tijdperiode van 382.31 tot 372.15 miljoen jaar geleden
Een tijdsperiode van 382.31 tot 372.15 miljoen jaar geleden
En tidsperiode fra 382.31 til 372.15 millioner år siden
Okres czasu od 382.31 do 372.15 milionów lat temu
Um período de tempo de 382.31 a 372.15 milhões de anos atrás
Временной период от 382.31 до 372.15 миллионов лет назад
Časové obdobie od 382.31 do 372.15 miliónov rokov pred naším letopočtom
382.31 ile 372.15 milyon yıl önce arasındaki zaman dilimi
距今 382.31 至 372.15 百万年前的时期
Gelasium
Gelasiense
Gelasiano
gelas
Cela
Gelasià
Gelasiar
Gela
Gélasien
gelai
Gelasian
ジェラシアン
젤라절
Gelazis
Gelasien
Gelasiaan
Gelaz
Гелазский
Gelasiyen
杰拉阶
2.58-dən 1.80 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 2.58 a 1.80 milions d'anys enrere
Časové období od 2.58 do 1.80 milionů let před naším letopočtem
Ein Zeitraum von 2.58 bis 1.80 Millionen Jahren
A time period from 2.58 to 1.80 million years ago
Un período de tiempo de 2.58 a 1.80 millones de años atrás
2.58 eta 1.80 milioi urte arteko denbora-tartea
Aikajakso 2.58–1.80 miljoonaa vuotta sitten
Une période de temps de 2.58 à 1.80 millions d'années
Egy 2.58-tól 1.80 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 2.58 hingga 1.80 juta tahun yang lalu
Un periodo di tempo da 2.58 a 1.80 milioni di anni fa
2.58百万年前から1.80百万年前までの時代
2.58백만 년 전부터 1.80백만 년 전까지의 시기
Laikotarpis nuo 2.58 iki 1.80 milijonų metų prieš dabartį
Een tijdperiode van 2.58 tot 1.80 miljoen jaar geleden
Een tijdsperiode van 2.58 tot 1.80 miljoen jaar geleden
En tidsperiode fra 2.58 til 1.80 millioner år siden
Okres czasu od 2.58 do 1.80 milionów lat temu
Um período de tempo de 2.58 a 1.80 milhões de anos atrás
Временной период от 2.58 до 1.80 миллионов лет назад
Časové obdobie od 2.58 do 1.80 miliónov rokov pred naším letopočtom
2.58 ile 1.80 milyon yıl önce arasındaki zaman dilimi
距今 2.58 至 1.80 百万年前的时期
Givetium
Givetiense
Givet
Givétien
giveti
Živetis
Żywet
Givetiano
givet
Jivet
Givetià
Givetiar
Givetian
ジベティアン
지베절
Givetien
Givetiaan
Живетский
Jivesiyen
吉维特阶
387.95-dən 382.31 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 387.95 a 382.31 milions d'anys enrere
Časové období od 387.95 do 382.31 milionů let před naším letopočtem
Ein Zeitraum von 387.95 bis 382.31 Millionen Jahren
A time period from 387.95 to 382.31 million years ago
Un período de tiempo de 387.95 a 382.31 millones de años atrás
387.95 eta 382.31 milioi urte arteko denbora-tartea
Aikajakso 387.95–382.31 miljoonaa vuotta sitten
Une période de temps de 387.95 à 382.31 millions d'années
Egy 387.95-tól 382.31 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 387.95 hingga 382.31 juta tahun yang lalu
Un periodo di tempo da 387.95 a 382.31 milioni di anni fa
387.95百万年前から382.31百万年前までの時代
387.95백만 년 전부터 382.31백만 년 전까지의 시기
Laikotarpis nuo 387.95 iki 382.31 milijonų metų prieš dabartį
Een tijdperiode van 387.95 tot 382.31 miljoen jaar geleden
Een tijdsperiode van 387.95 tot 382.31 miljoen jaar geleden
En tidsperiode fra 387.95 til 382.31 millioner år siden
Okres czasu od 387.95 do 382.31 milionów lat temu
Um período de tempo de 387.95 a 382.31 milhões de anos atrás
Временной период от 387.95 до 382.31 миллионов лет назад
Časové obdobie od 387.95 do 382.31 miliónov rokov pred naším letopočtom
387.95 ile 382.31 milyon yıl önce arasındaki zaman dilimi
距今 387.95 至 382.31 百万年前的时期
Gorstium
Gorstiense
Gorstien
gorsti
Gorstis
Gorst
Gorstiano
gorst
Qorst
Gorstià
Gorstiar
Gorsty
Gorstian
ゴースティアン
고스티절
Gorstiaan
Горстийский
Gorstiyen
高斯特阶
426.7-dən 425.0 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 426.7 a 425.0 milions d'anys enrere
Časové období od 426.7 do 425.0 milionů let před naším letopočtem
Ein Zeitraum von 426.7 bis 425.0 Millionen Jahren
A time period from 426.7 to 425.0 million years ago
Un período de tiempo de 426.7 a 425.0 millones de años atrás
426.7 eta 425.0 milioi urte arteko denbora-tartea
Aikajakso 426.7–425.0 miljoonaa vuotta sitten
Une période de temps de 426.7 à 425.0 millions d'années
Egy 426.7-tól 425.0 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 426.7 hingga 425.0 juta tahun yang lalu
Un periodo di tempo da 426.7 a 425.0 milioni di anni fa
426.7百万年前から425.0百万年前までの時代
426.7백만 년 전부터 425.0백만 년 전까지의 시기
Laikotarpis nuo 426.7 iki 425.0 milijonų metų prieš dabartį
Een tijdperiode van 426.7 tot 425.0 miljoen jaar geleden
Een tijdsperiode van 426.7 tot 425.0 miljoen jaar geleden
En tidsperiode fra 426.7 til 425.0 millioner år siden
Okres czasu od 426.7 do 425.0 milionów lat temu
Um período de tempo de 426.7 a 425.0 milhões de anos atrás
Временной период от 426.7 до 425.0 миллионов лет назад
Časové obdobie od 426.7 do 425.0 miliónov rokov pred naším letopočtom
426.7 ile 425.0 milyon yıl önce arasındaki zaman dilimi
距今 426.7 至 425.0 百万年前的时期
Qrenlandiya
Grenlandià
greenland
Grönlandium
Groenlandiense
Groenlandiano
Greenlandian
Grönlanti
Greenlandien
grönlandi
グリーンランディアン
그린란드절
Grenlandis
Greenlandiaan
Gronland
Grenlandzki
Greenlandiano
grón
Grönlandiyen
格陵兰阶
0.0117-dən 0.0082 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 0.0117 a 0.0082 milions d'anys enrere
Časové období od 0.0117 do 0.0082 milionů let před naším letopočtem
Ein Zeitraum von 0.0117 bis 0.0082 Millionen Jahren
A time period from 0.0117 to 0.0082 million years ago
Un período de tiempo de 0.0117 a 0.0082 millones de años atrás
0.0117 eta 0.0082 milioi urte arteko denbora-tartea
Aikajakso 0.0117–0.0082 miljoonaa vuotta sitten
Une période de temps de 0.0117 à 0.0082 millions d'années
Egy 0.0117-tól 0.0082 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 0.0117 hingga 0.0082 juta tahun yang lalu
Un periodo di tempo da 0.0117 a 0.0082 milioni di anni fa
0.0117百万年前から0.0082百万年前までの時代
0.0117백만 년 전부터 0.0082백만 년 전까지의 시기
Laikotarpis nuo 0.0117 iki 0.0082 milijonų metų prieš dabartį
Een tijdperiode van 0.0117 tot 0.0082 miljoen jaar geleden
Een tijdsperiode van 0.0117 tot 0.0082 miljoen jaar geleden
En tidsperiode fra 0.0117 til 0.0082 millioner år siden
Okres czasu od 0.0117 do 0.0082 milionów lat temu
Um período de tempo de 0.0117 a 0.0082 milhões de anos atrás
Временной период от 0.0117 до 0.0082 миллионов лет назад
Časové obdobie od 0.0117 do 0.0082 miliónov rokov pred naším letopočtom
0.0117 ile 0.0082 milyon yıl önce arasındaki zaman dilimi
距今 0.0117 至 0.0082 百万年前的时期
Guzhangium
Guzhangiense
Guzhang
Guzhangien
guzhangi
Gužangis
Gużang
Guzhangiano
Quzhanq
Guzhanguià
guzhang
Guzhangiar
Guzhangian
ガズハンジアン
구장절
Guzhangiaan
Гужанский
kučang
Guzhangiyen
古丈阶
500.5-dən 497.0 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 500.5 a 497.0 milions d'anys enrere
Časové období od 500.5 do 497.0 milionů let před naším letopočtem
Ein Zeitraum von 500.5 bis 497.0 Millionen Jahren
A time period from 500.5 to 497.0 million years ago
Un período de tiempo de 500.5 a 497.0 millones de años atrás
500.5 eta 497.0 milioi urte arteko denbora-tartea
Aikajakso 500.5–497.0 miljoonaa vuotta sitten
Une période de temps de 500.5 à 497.0 millions d'années
Egy 500.5-tól 497.0 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 500.5 hingga 497.0 juta tahun yang lalu
Un periodo di tempo da 500.5 a 497.0 milioni di anni fa
500.5百万年前から497.0百万年前までの時代
500.5백만 년 전부터 497.0백만 년 전까지의 시기
Laikotarpis nuo 500.5 iki 497.0 milijonų metų prieš dabartį
Een tijdperiode van 500.5 tot 497.0 miljoen jaar geleden
Een tijdsperiode van 500.5 tot 497.0 miljoen jaar geleden
En tidsperiode fra 500.5 til 497.0 millioner år siden
Okres czasu od 500.5 do 497.0 milionów lat temu
Um período de tempo de 500.5 a 497.0 milhões de anos atrás
Временной период от 500.5 до 497.0 миллионов лет назад
Časové obdobie od 500.5 do 497.0 miliónov rokov pred naším letopočtom
500.5 ile 497.0 milyon yıl önce arasındaki zaman dilimi
距今 500.5 至 497.0 百万年前的时期
Gzhelium
Gzhel
Gzhélien
gzseli
Gželis
Gżel
gžel
Qjel
Gjelià
Gzheliense
Gzheliano
Gzheliar
Gzhelian
グゼリアン
그젤절
Gzhelien
Gzheliaan
Гжельский
Gijeliyen
格舍尔阶
303.7-dən 298.9 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 303.7 a 298.9 milions d'anys enrere
Časové období od 303.7 do 298.9 milionů let před naším letopočtem
Ein Zeitraum von 303.7 bis 298.9 Millionen Jahren
A time period from 303.7 to 298.9 million years ago
Un período de tiempo de 303.7 a 298.9 millones de años atrás
303.7 eta 298.9 milioi urte arteko denbora-tartea
Aikajakso 303.7–298.9 miljoonaa vuotta sitten
Une période de temps de 303.7 à 298.9 millions d'années
Egy 303.7-tól 298.9 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 303.7 hingga 298.9 juta tahun yang lalu
Un periodo di tempo da 303.7 a 298.9 milioni di anni fa
303.7百万年前から298.9百万年前までの時代
303.7백만 년 전부터 298.9백만 년 전까지의 시기
Laikotarpis nuo 303.7 iki 298.9 milijonų metų prieš dabartį
Een tijdperiode van 303.7 tot 298.9 miljoen jaar geleden
Een tijdsperiode van 303.7 tot 298.9 miljoen jaar geleden
En tidsperiode fra 303.7 til 298.9 millioner år siden
Okres czasu od 303.7 do 298.9 milionów lat temu
Um período de tempo de 303.7 a 298.9 milhões de anos atrás
Временной период от 303.7 до 298.9 миллионов лет назад
Časové obdobie od 303.7 do 298.9 miliónov rokov pred naším letopočtom
303.7 ile 298.9 milyon yıl önce arasındaki zaman dilimi
距今 303.7 至 298.9 百万年前的时期
Hauterivium
Hauteriv
Hauterivien
hauterivi
Hoterivis
Hoteryw
Hauteriviano
Hoteriv
Hauterivià
hauteriv
Hauteriviense
Hauteriviar
Hauterivian
オーテリビアン
오트리브절
Hauteriviaan
Готеривский
hoteriv
Hotriviyen
欧特里夫阶
132.6-dən 125.77 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 132.6 a 125.77 milions d'anys enrere
Časové období od 132.6 do 125.77 milionů let před naším letopočtem
Ein Zeitraum von 132.6 bis 125.77 Millionen Jahren
A time period from 132.6 to 125.77 million years ago
Un período de tiempo de 132.6 a 125.77 millones de años atrás
132.6 eta 125.77 milioi urte arteko denbora-tartea
Aikajakso 132.6–125.77 miljoonaa vuotta sitten
Une période de temps de 132.6 à 125.77 millions d'années
Egy 132.6-tól 125.77 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 132.6 hingga 125.77 juta tahun yang lalu
Un periodo di tempo da 132.6 a 125.77 milioni di anni fa
132.6百万年前から125.77百万年前までの時代
132.6백만 년 전부터 125.77백만 년 전까지의 시기
Laikotarpis nuo 132.6 iki 125.77 milijonų metų prieš dabartį
Een tijdperiode van 132.6 tot 125.77 miljoen jaar geleden
Een tijdsperiode van 132.6 tot 125.77 miljoen jaar geleden
En tidsperiode fra 132.6 til 125.77 millioner år siden
Okres czasu od 132.6 do 125.77 milionów lat temu
Um período de tempo de 132.6 a 125.77 milhões de anos atrás
Временной период от 132.6 до 125.77 миллионов лет назад
Časové obdobie od 132.6 do 125.77 miliónov rokov pred naším letopočtom
132.6 ile 125.77 milyon yıl önce arasındaki zaman dilimi
距今 132.6 至 125.77 百万年前的时期
Hettangium
Hettangien
hettangi
Hetangis
Hettang
hetanž
Hettanq
Hettangià
hettang
Hettangiense
Hettangiano
Hettangiar
Hettange
Hettangian
ヘッタンジアン
에탕주절
Hettangiaan
Геттангский
Hettanjiyen
赫塘阶
201.4-dən 199.5 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 201.4 a 199.5 milions d'anys enrere
Časové období od 201.4 do 199.5 milionů let před naším letopočtem
Ein Zeitraum von 201.4 bis 199.5 Millionen Jahren
A time period from 201.4 to 199.5 million years ago
Un período de tiempo de 201.4 a 199.5 millones de años atrás
201.4 eta 199.5 milioi urte arteko denbora-tartea
Aikajakso 201.4–199.5 miljoonaa vuotta sitten
Une période de temps de 201.4 à 199.5 millions d'années
Egy 201.4-tól 199.5 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 201.4 hingga 199.5 juta tahun yang lalu
Un periodo di tempo da 201.4 a 199.5 milioni di anni fa
201.4百万年前から199.5百万年前までの時代
201.4백만 년 전부터 199.5백만 년 전까지의 시기
Laikotarpis nuo 201.4 iki 199.5 milijonų metų prieš dabartį
Een tijdperiode van 201.4 tot 199.5 miljoen jaar geleden
Een tijdsperiode van 201.4 tot 199.5 miljoen jaar geleden
En tidsperiode fra 201.4 til 199.5 millioner år siden
Okres czasu od 201.4 do 199.5 milionów lat temu
Um período de tempo de 201.4 a 199.5 milhões de anos atrás
Временной период от 201.4 до 199.5 миллионов лет назад
Časové obdobie od 201.4 do 199.5 miliónov rokov pred naším letopočtom
201.4 ile 199.5 milyon yıl önce arasındaki zaman dilimi
距今 201.4 至 199.5 百万年前的时期
Hirnantium
Hirnantiense
Hirnant
Hirnantien
hirnanti
Hirnantis
Hirnantiano
hirnant
Hirnantià
Hirnantiar
Hirnantian
ヒルナンシアン
허난트절
Hirnantiaan
Hirnantan
Хирнантский
Hirnansiyen
赫南特阶
445.2-dən 443.1 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 445.2 a 443.1 milions d'anys enrere
Časové období od 445.2 do 443.1 milionů let před naším letopočtem
Ein Zeitraum von 445.2 bis 443.1 Millionen Jahren
A time period from 445.2 to 443.1 million years ago
Un período de tiempo de 445.2 a 443.1 millones de años atrás
445.2 eta 443.1 milioi urte arteko denbora-tartea
Aikajakso 445.2–443.1 miljoonaa vuotta sitten
Une période de temps de 445.2 à 443.1 millions d'années
Egy 445.2-tól 443.1 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 445.2 hingga 443.1 juta tahun yang lalu
Un periodo di tempo da 445.2 a 443.1 milioni di anni fa
445.2百万年前から443.1百万年前までの時代
445.2백만 년 전부터 443.1백만 년 전까지의 시기
Laikotarpis nuo 445.2 iki 443.1 milijonų metų prieš dabartį
Een tijdperiode van 445.2 tot 443.1 miljoen jaar geleden
Een tijdsperiode van 445.2 tot 443.1 miljoen jaar geleden
En tidsperiode fra 445.2 til 443.1 millioner år siden
Okres czasu od 445.2 do 443.1 milionów lat temu
Um período de tempo de 445.2 a 443.1 milhões de anos atrás
Временной период от 445.2 до 443.1 миллионов лет назад
Časové obdobie od 445.2 do 443.1 miliónov rokov pred naším letopočtom
445.2 ile 443.1 milyon yıl önce arasındaki zaman dilimi
距今 445.2 至 443.1 百万年前的时期
Homerium
Homeriense
Homer
Homérien
homeri
Homeris
Homeriano
homer
Homerià
Homeriar
Homerian
ホメリアン
호머절
Homerien
Homeriaan
Гомерский
Homeriyen
侯墨阶
430.6-dən 426.7 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 430.6 a 426.7 milions d'anys enrere
Časové období od 430.6 do 426.7 milionů let před naším letopočtem
Ein Zeitraum von 430.6 bis 426.7 Millionen Jahren
A time period from 430.6 to 426.7 million years ago
Un período de tiempo de 430.6 a 426.7 millones de años atrás
430.6 eta 426.7 milioi urte arteko denbora-tartea
Aikajakso 430.6–426.7 miljoonaa vuotta sitten
Une période de temps de 430.6 à 426.7 millions d'années
Egy 430.6-tól 426.7 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 430.6 hingga 426.7 juta tahun yang lalu
Un periodo di tempo da 430.6 a 426.7 milioni di anni fa
430.6百万年前から426.7百万年前までの時代
430.6백만 년 전부터 426.7백만 년 전까지의 시기
Laikotarpis nuo 430.6 iki 426.7 milijonų metų prieš dabartį
Een tijdperiode van 430.6 tot 426.7 miljoen jaar geleden
Een tijdsperiode van 430.6 tot 426.7 miljoen jaar geleden
En tidsperiode fra 430.6 til 426.7 millioner år siden
Okres czasu od 430.6 do 426.7 milionów lat temu
Um período de tempo de 430.6 a 426.7 milhões de anos atrás
Временной период от 430.6 до 426.7 миллионов лет назад
Časové obdobie od 430.6 do 426.7 miliónov rokov pred naším letopočtom
430.6 ile 426.7 milyon yıl önce arasındaki zaman dilimi
距今 430.6 至 426.7 百万年前的时期
Indusium
Induense
Indus
indusi
Indis
Induano
İnd
Indià
ind
Induar
Indusien
Induan
インドゥアン
인더스절
Induen
Induaan
Индский
indus
İnduyen
印度阶
251.902-dən 250.8 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 251.902 a 250.8 milions d'anys enrere
Časové období od 251.902 do 250.8 milionů let před naším letopočtem
Ein Zeitraum von 251.902 bis 250.8 Millionen Jahren
A time period from 251.902 to 250.8 million years ago
Un período de tiempo de 251.902 a 250.8 millones de años atrás
251.902 eta 250.8 milioi urte arteko denbora-tartea
Aikajakso 251.902–250.8 miljoonaa vuotta sitten
Une période de temps de 251.902 à 250.8 millions d'années
Egy 251.902-tól 250.8 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 251.902 hingga 250.8 juta tahun yang lalu
Un periodo di tempo da 251.902 a 250.8 milioni di anni fa
251.902百万年前から250.8百万年前までの時代
251.902백만 년 전부터 250.8백만 년 전까지의 시기
Laikotarpis nuo 251.902 iki 250.8 milijonų metų prieš dabartį
Een tijdperiode van 251.902 tot 250.8 miljoen jaar geleden
Een tijdsperiode van 251.902 tot 250.8 miljoen jaar geleden
En tidsperiode fra 251.902 til 250.8 millioner år siden
Okres czasu od 251.902 do 250.8 milionów lat temu
Um período de tempo de 251.902 a 250.8 milhões de anos atrás
Временной период от 251.902 до 250.8 миллионов лет назад
Časové obdobie od 251.902 do 250.8 miliónov rokov pred naším letopočtom
251.902 ile 250.8 milyon yıl önce arasındaki zaman dilimi
距今 251.902 至 250.8 百万年前的时期
Jianqşan
Jiangshanià
jiangshan
Jiangshanium
Jiangshaniense
Jiangshaniano
Jiangshaniar
Jiangshan
Jiangshanien
jiangshani
Jiangshanian
ジャンシャニアン
지앙샨절
Jiangšanis
Jiangshaniaan
Цзяншаньский
tiangšan
Jiyangşaniyen
江山阶
494.2-dən 491.0 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 494.2 a 491.0 milions d'anys enrere
Časové období od 494.2 do 491.0 milionů let před naším letopočtem
Ein Zeitraum von 494.2 bis 491.0 Millionen Jahren
A time period from 494.2 to 491.0 million years ago
Un período de tiempo de 494.2 a 491.0 millones de años atrás
494.2 eta 491.0 milioi urte arteko denbora-tartea
Aikajakso 494.2–491.0 miljoonaa vuotta sitten
Une période de temps de 494.2 à 491.0 millions d'années
Egy 494.2-tól 491.0 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 494.2 hingga 491.0 juta tahun yang lalu
Un periodo di tempo da 494.2 a 491.0 milioni di anni fa
494.2百万年前から491.0百万年前までの時代
494.2백만 년 전부터 491.0백만 년 전까지의 시기
Laikotarpis nuo 494.2 iki 491.0 milijonų metų prieš dabartį
Een tijdperiode van 494.2 tot 491.0 miljoen jaar geleden
Een tijdsperiode van 494.2 tot 491.0 miljoen jaar geleden
En tidsperiode fra 494.2 til 491.0 millioner år siden
Okres czasu od 494.2 do 491.0 milionów lat temu
Um período de tempo de 494.2 a 491.0 milhões de anos atrás
Временной период от 494.2 до 491.0 миллионов лет назад
Časové obdobie od 494.2 do 491.0 miliónov rokov pred naším letopočtom
494.2 ile 491.0 milyon yıl önce arasındaki zaman dilimi
距今 494.2 至 491.0 百万年前的时期
Kasimovium
Kasimoviense
Kasimov
Kasimovien
kaszimovi
Kasimovis
Kasimoviano
kasimov
Qasımov
Kasimovià
Kasimoviar
Kasimovian
カシモビアン
카시모프절
Kasimoviaan
Kasymow
Касимовский
Kasımoviyen
卡西莫夫阶
307.0-dən 303.7 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 307.0 a 303.7 milions d'anys enrere
Časové období od 307.0 do 303.7 milionů let před naším letopočtem
Ein Zeitraum von 307.0 bis 303.7 Millionen Jahren
A time period from 307.0 to 303.7 million years ago
Un período de tiempo de 307.0 a 303.7 millones de años atrás
307.0 eta 303.7 milioi urte arteko denbora-tartea
Aikajakso 307.0–303.7 miljoonaa vuotta sitten
Une période de temps de 307.0 à 303.7 millions d'années
Egy 307.0-tól 303.7 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 307.0 hingga 303.7 juta tahun yang lalu
Un periodo di tempo da 307.0 a 303.7 milioni di anni fa
307.0百万年前から303.7百万年前までの時代
307.0백만 년 전부터 303.7백만 년 전까지의 시기
Laikotarpis nuo 307.0 iki 303.7 milijonų metų prieš dabartį
Een tijdperiode van 307.0 tot 303.7 miljoen jaar geleden
Een tijdsperiode van 307.0 tot 303.7 miljoen jaar geleden
En tidsperiode fra 307.0 til 303.7 millioner år siden
Okres czasu od 307.0 do 303.7 milionów lat temu
Um período de tempo de 307.0 a 303.7 milhões de anos atrás
Временной период от 307.0 до 303.7 миллионов лет назад
Časové obdobie od 307.0 do 303.7 miliónov rokov pred naším letopočtom
307.0 ile 303.7 milyon yıl önce arasındaki zaman dilimi
距今 307.0 至 303.7 百万年前的时期
Katium
Katiense
Katien
kati
Katis
Katiano
kat
Kati
Katià
katian
Katiar
Katy
Katian
カティアン
케이티절
Katiaan
Katan
Катийский
Katiyen
凯迪阶
452.8-dən 445.2 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 452.8 a 445.2 milions d'anys enrere
Časové období od 452.8 do 445.2 milionů let před naším letopočtem
Ein Zeitraum von 452.8 bis 445.2 Millionen Jahren
A time period from 452.8 to 445.2 million years ago
Un período de tiempo de 452.8 a 445.2 millones de años atrás
452.8 eta 445.2 milioi urte arteko denbora-tartea
Aikajakso 452.8–445.2 miljoonaa vuotta sitten
Une période de temps de 452.8 à 445.2 millions d'années
Egy 452.8-tól 445.2 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 452.8 hingga 445.2 juta tahun yang lalu
Un periodo di tempo da 452.8 a 445.2 milioni di anni fa
452.8百万年前から445.2百万年前までの時代
452.8백만 년 전부터 445.2백만 년 전까지의 시기
Laikotarpis nuo 452.8 iki 445.2 milijonų metų prieš dabartį
Een tijdperiode van 452.8 tot 445.2 miljoen jaar geleden
Een tijdsperiode van 452.8 tot 445.2 miljoen jaar geleden
En tidsperiode fra 452.8 til 445.2 millioner år siden
Okres czasu od 452.8 do 445.2 milionów lat temu
Um período de tempo de 452.8 a 445.2 milhões de anos atrás
Временной период от 452.8 до 445.2 миллионов лет назад
Časové obdobie od 452.8 do 445.2 miliónov rokov pred naším letopočtom
452.8 ile 445.2 milyon yıl önce arasındaki zaman dilimi
距今 452.8 至 445.2 百万年前的时期
Kimmeridgium
Kimmeridgiense
Kimmeridge
Kimméridgien
Kimeridis
kimeridž
Kimeric
Kimmeridgià
kimmeridge
Kimmeridgiano
Kimmeridgiar
kimmeridgi
Kimmeridgian
キンメリッジアン
킴머리지절
Kimmeridgien
Kimmeridgiaan
Kimerydż
Кимериджский
Kimmericiyen
钦莫利阶
154.8-dən 149.2 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 154.8 a 149.2 milions d'anys enrere
Časové období od 154.8 do 149.2 milionů let před naším letopočtem
Ein Zeitraum von 154.8 bis 149.2 Millionen Jahren
A time period from 154.8 to 149.2 million years ago
Un período de tiempo de 154.8 a 149.2 millones de años atrás
154.8 eta 149.2 milioi urte arteko denbora-tartea
Aikajakso 154.8–149.2 miljoonaa vuotta sitten
Une période de temps de 154.8 à 149.2 millions d'années
Egy 154.8-tól 149.2 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 154.8 hingga 149.2 juta tahun yang lalu
Un periodo di tempo da 154.8 a 149.2 milioni di anni fa
154.8百万年前から149.2百万年前までの時代
154.8백만 년 전부터 149.2백만 년 전까지의 시기
Laikotarpis nuo 154.8 iki 149.2 milijonų metų prieš dabartį
Een tijdperiode van 154.8 tot 149.2 miljoen jaar geleden
Een tijdsperiode van 154.8 tot 149.2 miljoen jaar geleden
En tidsperiode fra 154.8 til 149.2 millioner år siden
Okres czasu od 154.8 do 149.2 milionów lat temu
Um período de tempo de 154.8 a 149.2 milhões de anos atrás
Временной период от 154.8 до 149.2 миллионов лет назад
Časové obdobie od 154.8 do 149.2 miliónov rokov pred naším letopočtom
154.8 ile 149.2 milyon yıl önce arasındaki zaman dilimi
距今 154.8 至 149.2 百万年前的时期
Kungurium
Kunguriense
Kungur
kunguri
Kunguris
Kunguriano
kungur
Kunqur
Kungurià
Kunguriar
Koungourien
Kungurian
クングリアン
쿤구르절
Kungurien
Kunguriaan
Кунгурский
Kunguriyen
空谷阶
283.3-dən 274.4 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 283.3 a 274.4 milions d'anys enrere
Časové období od 283.3 do 274.4 milionů let před naším letopočtem
Ein Zeitraum von 283.3 bis 274.4 Millionen Jahren
A time period from 283.3 to 274.4 million years ago
Un período de tiempo de 283.3 a 274.4 millones de años atrás
283.3 eta 274.4 milioi urte arteko denbora-tartea
Aikajakso 283.3–274.4 miljoonaa vuotta sitten
Une période de temps de 283.3 à 274.4 millions d'années
Egy 283.3-tól 274.4 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 283.3 hingga 274.4 juta tahun yang lalu
Un periodo di tempo da 283.3 a 274.4 milioni di anni fa
283.3百万年前から274.4百万年前までの時代
283.3백만 년 전부터 274.4백만 년 전까지의 시기
Laikotarpis nuo 283.3 iki 274.4 milijonų metų prieš dabartį
Een tijdperiode van 283.3 tot 274.4 miljoen jaar geleden
Een tijdsperiode van 283.3 tot 274.4 miljoen jaar geleden
En tidsperiode fra 283.3 til 274.4 millioner år siden
Okres czasu od 283.3 do 274.4 milionów lat temu
Um período de tempo de 283.3 a 274.4 milhões de anos atrás
Временной период от 283.3 до 274.4 миллионов лет назад
Časové obdobie od 283.3 do 274.4 miliónov rokov pred naším letopočtom
283.3 ile 274.4 milyon yıl önce arasındaki zaman dilimi
距今 283.3 至 274.4 百万年前的时期
Ladinium
Ladiniense
Ladin
Ladinien
Ladinis
Ladyn
Ladiniano
ladin
Ladinià
Ladiniar
ladini
Ladinian
Ladinico
ラディニアン
라딘절
Ladiniaan
Ладинский
Ladiniyen
拉丁阶
241.464-dən 237 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 241.464 a 237 milions d'anys enrere
Časové období od 241.464 do 237 milionů let před naším letopočtem
Ein Zeitraum von 241.464 bis 237 Millionen Jahren
A time period from 241.464 to 237 million years ago
Un período de tiempo de 241.464 a 237 millones de años atrás
241.464 eta 237 milioi urte arteko denbora-tartea
Aikajakso 241.464–237 miljoonaa vuotta sitten
Une période de temps de 241.464 à 237 millions d'années
Egy 241.464-tól 237 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 241.464 hingga 237 juta tahun yang lalu
Un periodo di tempo da 241.464 a 237 milioni di anni fa
241.464百万年前から237百万年前までの時代
241.464백만 년 전부터 237백만 년 전까지의 시기
Laikotarpis nuo 241.464 iki 237 milijonų metų prieš dabartį
Een tijdperiode van 241.464 tot 237 miljoen jaar geleden
Een tijdsperiode van 241.464 tot 237 miljoen jaar geleden
En tidsperiode fra 241.464 til 237 millioner år siden
Okres czasu od 241.464 do 237 milionów lat temu
Um período de tempo de 241.464 a 237 milhões de anos atrás
Временной период от 241.464 до 237 миллионов лет назад
Časové obdobie od 241.464 do 237 miliónov rokov pred naším letopočtom
241.464 ile 237 milyon yıl önce arasındaki zaman dilimi
距今 241.464 至 237 百万年前的时期
Langhium
Langhiense
Langhien
langhei
Langis
Langhiano
Lanqiy
Languià
langh
Langhiar
Langhe
Langhian
ランギアン
랑게절
Langhiaan
Langian
Лангийский
lang
Langiyen
兰盖阶
15.98-dən 13.82 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 15.98 a 13.82 milions d'anys enrere
Časové období od 15.98 do 13.82 milionů let před naším letopočtem
Ein Zeitraum von 15.98 bis 13.82 Millionen Jahren
A time period from 15.98 to 13.82 million years ago
Un período de tiempo de 15.98 a 13.82 millones de años atrás
15.98 eta 13.82 milioi urte arteko denbora-tartea
Aikajakso 15.98–13.82 miljoonaa vuotta sitten
Une période de temps de 15.98 à 13.82 millions d'années
Egy 15.98-tól 13.82 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 15.98 hingga 13.82 juta tahun yang lalu
Un periodo di tempo da 15.98 a 13.82 milioni di anni fa
15.98百万年前から13.82百万年前までの時代
15.98백만 년 전부터 13.82백만 년 전까지의 시기
Laikotarpis nuo 15.98 iki 13.82 milijonų metų prieš dabartį
Een tijdperiode van 15.98 tot 13.82 miljoen jaar geleden
Een tijdsperiode van 15.98 tot 13.82 miljoen jaar geleden
En tidsperiode fra 15.98 til 13.82 millioner år siden
Okres czasu od 15.98 do 13.82 milionów lat temu
Um período de tempo de 15.98 a 13.82 milhões de anos atrás
Временной период от 15.98 до 13.82 миллионов лет назад
Časové obdobie od 15.98 do 13.82 miliónov rokov pred naším letopočtom
15.98 ile 13.82 milyon yıl önce arasındaki zaman dilimi
距今 15.98 至 13.82 百万年前的时期
Lochkovium
Lochkoviense
Lochkov
Lochkovien
lochkovi
Lochkovis
Lochkoviano
lochkov
Loxkov
Lochkovià
Lochkoviar
Lochkovian
ロッコヴィアン
로치코프절
Lochkoviaan
Lochków
Лохковский
Lohkoviyen
洛赫考夫阶
419.62-dən 413.02 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 419.62 a 413.02 milions d'anys enrere
Časové období od 419.62 do 413.02 milionů let před naším letopočtem
Ein Zeitraum von 419.62 bis 413.02 Millionen Jahren
A time period from 419.62 to 413.02 million years ago
Un período de tiempo de 419.62 a 413.02 millones de años atrás
419.62 eta 413.02 milioi urte arteko denbora-tartea
Aikajakso 419.62–413.02 miljoonaa vuotta sitten
Une période de temps de 419.62 à 413.02 millions d'années
Egy 419.62-tól 413.02 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 419.62 hingga 413.02 juta tahun yang lalu
Un periodo di tempo da 419.62 a 413.02 milioni di anni fa
419.62百万年前から413.02百万年前までの時代
419.62백만 년 전부터 413.02백만 년 전까지의 시기
Laikotarpis nuo 419.62 iki 413.02 milijonų metų prieš dabartį
Een tijdperiode van 419.62 tot 413.02 miljoen jaar geleden
Een tijdsperiode van 419.62 tot 413.02 miljoen jaar geleden
En tidsperiode fra 419.62 til 413.02 millioner år siden
Okres czasu od 419.62 do 413.02 milionów lat temu
Um período de tempo de 419.62 a 413.02 milhões de anos atrás
Временной период от 419.62 до 413.02 миллионов лет назад
Časové obdobie od 419.62 do 413.02 miliónov rokov pred naším letopočtom
419.62 ile 413.02 milyon yıl önce arasındaki zaman dilimi
距今 419.62 至 413.02 百万年前的时期
Ludfordium
Ludfordiense
Ludford
Ludfordien
ludfordi
Ludfordiano
ludford
Ludfordià
Ludfordiar
Ludfordian
ルドフォーディアン
로드포드절
Ludfordis
Ludfordiaan
Лудфордский
Ludfordiyen
卢德福特阶
425.0-dən 422.7 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 425.0 a 422.7 milions d'anys enrere
Časové období od 425.0 do 422.7 milionů let před naším letopočtem
Ein Zeitraum von 425.0 bis 422.7 Millionen Jahren
A time period from 425.0 to 422.7 million years ago
Un período de tiempo de 425.0 a 422.7 millones de años atrás
425.0 eta 422.7 milioi urte arteko denbora-tartea
Aikajakso 425.0–422.7 miljoonaa vuotta sitten
Une période de temps de 425.0 à 422.7 millions d'années
Egy 425.0-tól 422.7 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 425.0 hingga 422.7 juta tahun yang lalu
Un periodo di tempo da 425.0 a 422.7 milioni di anni fa
425.0百万年前から422.7百万年前までの時代
425.0백만 년 전부터 422.7백만 년 전까지의 시기
Laikotarpis nuo 425.0 iki 422.7 milijonų metų prieš dabartį
Een tijdperiode van 425.0 tot 422.7 miljoen jaar geleden
Een tijdsperiode van 425.0 tot 422.7 miljoen jaar geleden
En tidsperiode fra 425.0 til 422.7 millioner år siden
Okres czasu od 425.0 do 422.7 milionów lat temu
Um período de tempo de 425.0 a 422.7 milhões de anos atrás
Временной период от 425.0 до 422.7 миллионов лет назад
Časové obdobie od 425.0 do 422.7 miliónov rokov pred naším letopočtom
425.0 ile 422.7 milyon yıl önce arasındaki zaman dilimi
距今 425.0 至 422.7 百万年前的时期
Lutetium
Luteciense
Lutétien
lutetiai
Lutet
lutét
Lyutet
Lutecià
lutet
Lutetiano
Lutetiar
Lutetia
Lutetian
Luteziano
ルテシアン
루테티아절
Lutetis
Lutetien
Lutetiaan
Лютетский
Lütesiyen
卢泰特阶
48.07-dən 41.03 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 48.07 a 41.03 milions d'anys enrere
Časové období od 48.07 do 41.03 milionů let před naším letopočtem
Ein Zeitraum von 48.07 bis 41.03 Millionen Jahren
A time period from 48.07 to 41.03 million years ago
Un período de tiempo de 48.07 a 41.03 millones de años atrás
48.07 eta 41.03 milioi urte arteko denbora-tartea
Aikajakso 48.07–41.03 miljoonaa vuotta sitten
Une période de temps de 48.07 à 41.03 millions d'années
Egy 48.07-tól 41.03 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 48.07 hingga 41.03 juta tahun yang lalu
Un periodo di tempo da 48.07 a 41.03 milioni di anni fa
48.07百万年前から41.03百万年前までの時代
48.07백만 년 전부터 41.03백만 년 전까지의 시기
Laikotarpis nuo 48.07 iki 41.03 milijonų metų prieš dabartį
Een tijdperiode van 48.07 tot 41.03 miljoen jaar geleden
Een tijdsperiode van 48.07 tot 41.03 miljoen jaar geleden
En tidsperiode fra 48.07 til 41.03 millioner år siden
Okres czasu od 48.07 do 41.03 milionów lat temu
Um período de tempo de 48.07 a 41.03 milhões de anos atrás
Временной период от 48.07 до 41.03 миллионов лет назад
Časové obdobie od 48.07 do 41.03 miliónov rokov pred naším letopočtom
48.07 ile 41.03 milyon yıl önce arasındaki zaman dilimi
距今 48.07 至 41.03 百万年前的时期
Maastrichtium
Maastrichtiense
Maastricht
Maastrichtien
maastrichti
Mastrichtis
Mastrycht
mástricht
Maastrixt
Maastrichtià
maastricht
Maastrichtiano
Maastrichtiar
Maastrichtian
マーストリヒチアン
마스트리히트절
Maastrichtiaan
Маастрихтский
Maastrihtiyen
马斯特里赫特阶
72.2-dən 66.00 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 72.2 a 66.00 milions d'anys enrere
Časové období od 72.2 do 66.00 milionů let před naším letopočtem
Ein Zeitraum von 72.2 bis 66.00 Millionen Jahren
A time period from 72.2 to 66.00 million years ago
Un período de tiempo de 72.2 a 66.00 millones de años atrás
72.2 eta 66.00 milioi urte arteko denbora-tartea
Aikajakso 72.2–66.00 miljoonaa vuotta sitten
Une période de temps de 72.2 à 66.00 millions d'années
Egy 72.2-tól 66.00 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 72.2 hingga 66.00 juta tahun yang lalu
Un periodo di tempo da 72.2 a 66.00 milioni di anni fa
72.2百万年前から66.00百万年前までの時代
72.2백만 년 전부터 66.00백만 년 전까지의 시기
Laikotarpis nuo 72.2 iki 66.00 milijonų metų prieš dabartį
Een tijdperiode van 72.2 tot 66.00 miljoen jaar geleden
Een tijdsperiode van 72.2 tot 66.00 miljoen jaar geleden
En tidsperiode fra 72.2 til 66.00 millioner år siden
Okres czasu od 72.2 do 66.00 milionów lat temu
Um período de tempo de 72.2 a 66.00 milhões de anos atrás
Временной период от 72.2 до 66.00 миллионов лет назад
Časové obdobie od 72.2 do 66.00 miliónov rokov pred naším letopočtom
72.2 ile 66.00 milyon yıl önce arasındaki zaman dilimi
距今 72.2 至 66.00 百万年前的时期
Meqhalaya
Megalaià
meghalayan
Meghalayum
Megalayense
Megalayiano
Meghalayan
Meghalaya
Meghalayen
meghalayai
Meghalayano
メガラヤン
메갈라야절
Megalajis
Meghalayaan
Megalaya
Megalajski
Megalayano
megalaj
Meghaliyen
梅加拉亚阶
0.0042-dən 0 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 0.0042 a 0 milions d'anys enrere
Časové období od 0.0042 do 0 milionů let před naším letopočtem
Ein Zeitraum von 0.0042 bis 0 Millionen Jahren
A time period from 0.0042 to 0 million years ago
Un período de tiempo de 0.0042 a 0 millones de años atrás
0.0042 eta 0 milioi urte arteko denbora-tartea
Aikajakso 0.0042–0 miljoonaa vuotta sitten
Une période de temps de 0.0042 à 0 millions d'années
Egy 0.0042-tól 0 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 0.0042 hingga 0 juta tahun yang lalu
Un periodo di tempo da 0.0042 a 0 milioni di anni fa
0.0042百万年前から0百万年前までの時代
0.0042백만 년 전부터 0백만 년 전까지의 시기
Laikotarpis nuo 0.0042 iki 0 milijonų metų prieš dabartį
Een tijdperiode van 0.0042 tot 0 miljoen jaar geleden
Een tijdsperiode van 0.0042 tot 0 miljoen jaar geleden
En tidsperiode fra 0.0042 til 0 millioner år siden
Okres czasu od 0.0042 do 0 milionów lat temu
Um período de tempo de 0.0042 a 0 milhões de anos atrás
Временной период от 0.0042 до 0 миллионов лет назад
Časové obdobie od 0.0042 do 0 miliónov rokov pred naším letopočtom
0.0042 ile 0 milyon yıl önce arasındaki zaman dilimi
距今 0.0042 至 0 百万年前的时期
Messinium
Messiniense
Messina
Messinien
messinai
Mesinis
Messiniano
Messin
Messinià
messin
Mesiniano
Messiniar
Messinian
メッシニアン
메시나절
Messiniaan
Mesyn
Мессинский
mesin
Messiniyen
墨西拿阶
7.246-dən 5.333 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 7.246 a 5.333 milions d'anys enrere
Časové období od 7.246 do 5.333 milionů let před naším letopočtem
Ein Zeitraum von 7.246 bis 5.333 Millionen Jahren
A time period from 7.246 to 5.333 million years ago
Un período de tiempo de 7.246 a 5.333 millones de años atrás
7.246 eta 5.333 milioi urte arteko denbora-tartea
Aikajakso 7.246–5.333 miljoonaa vuotta sitten
Une période de temps de 7.246 à 5.333 millions d'années
Egy 7.246-tól 5.333 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 7.246 hingga 5.333 juta tahun yang lalu
Un periodo di tempo da 7.246 a 5.333 milioni di anni fa
7.246百万年前から5.333百万年前までの時代
7.246백만 년 전부터 5.333백만 년 전까지의 시기
Laikotarpis nuo 7.246 iki 5.333 milijonų metų prieš dabartį
Een tijdperiode van 7.246 tot 5.333 miljoen jaar geleden
Een tijdsperiode van 7.246 tot 5.333 miljoen jaar geleden
En tidsperiode fra 7.246 til 5.333 millioner år siden
Okres czasu od 7.246 do 5.333 milionów lat temu
Um período de tempo de 7.246 a 5.333 milhões de anos atrás
Временной период от 7.246 до 5.333 миллионов лет назад
Časové obdobie od 7.246 do 5.333 miliónov rokov pred naším letopočtom
7.246 ile 5.333 milyon yıl önce arasındaki zaman dilimi
距今 7.246 至 5.333 百万年前的时期
Moskovium
Moscoviense
Moskova
Moscovien
moszkvai
Moskow
Moscoviano
moskov
Moskva
Moscovià
Moscoviar
Moscovian
モスコビアン
모스코바절
Moskvis
Moscoviaan
Московский
Moskoviyen
莫斯科阶
315.2-dən 307.0 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 315.2 a 307.0 milions d'anys enrere
Časové období od 315.2 do 307.0 milionů let před naším letopočtem
Ein Zeitraum von 315.2 bis 307.0 Millionen Jahren
A time period from 315.2 to 307.0 million years ago
Un período de tiempo de 315.2 a 307.0 millones de años atrás
315.2 eta 307.0 milioi urte arteko denbora-tartea
Aikajakso 315.2–307.0 miljoonaa vuotta sitten
Une période de temps de 315.2 à 307.0 millions d'années
Egy 315.2-tól 307.0 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 315.2 hingga 307.0 juta tahun yang lalu
Un periodo di tempo da 315.2 a 307.0 milioni di anni fa
315.2百万年前から307.0百万年前までの時代
315.2백만 년 전부터 307.0백만 년 전까지의 시기
Laikotarpis nuo 315.2 iki 307.0 milijonų metų prieš dabartį
Een tijdperiode van 315.2 tot 307.0 miljoen jaar geleden
Een tijdsperiode van 315.2 tot 307.0 miljoen jaar geleden
En tidsperiode fra 315.2 til 307.0 millioner år siden
Okres czasu od 315.2 do 307.0 milionów lat temu
Um período de tempo de 315.2 a 307.0 milhões de anos atrás
Временной период от 315.2 до 307.0 миллионов лет назад
Časové obdobie od 315.2 do 307.0 miliónov rokov pred naším letopočtom
315.2 ile 307.0 milyon yıl önce arasındaki zaman dilimi
距今 315.2 至 307.0 百万年前的时期
Norium
Noriense
Norien
nori
Noris
Nor
Noryk
Noriano
norik
Noriy
Norià
Noriar
Norian
Norico
ノーリアン
노릭절
Noriaan
Норийский
Noriyen
诺利阶
227.3-dən 205.7 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 227.3 a 205.7 milions d'anys enrere
Časové období od 227.3 do 205.7 milionů let před naším letopočtem
Ein Zeitraum von 227.3 bis 205.7 Millionen Jahren
A time period from 227.3 to 205.7 million years ago
Un período de tiempo de 227.3 a 205.7 millones de años atrás
227.3 eta 205.7 milioi urte arteko denbora-tartea
Aikajakso 227.3–205.7 miljoonaa vuotta sitten
Une période de temps de 227.3 à 205.7 millions d'années
Egy 227.3-tól 205.7 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 227.3 hingga 205.7 juta tahun yang lalu
Un periodo di tempo da 227.3 a 205.7 milioni di anni fa
227.3百万年前から205.7百万年前までの時代
227.3백만 년 전부터 205.7백만 년 전까지의 시기
Laikotarpis nuo 227.3 iki 205.7 milijonų metų prieš dabartį
Een tijdperiode van 227.3 tot 205.7 miljoen jaar geleden
Een tijdsperiode van 227.3 tot 205.7 miljoen jaar geleden
En tidsperiode fra 227.3 til 205.7 millioner år siden
Okres czasu od 227.3 do 205.7 milionów lat temu
Um período de tempo de 227.3 a 205.7 milhões de anos atrás
Временной период от 227.3 до 205.7 миллионов лет назад
Časové obdobie od 227.3 do 205.7 miliónov rokov pred naším letopočtom
227.3 ile 205.7 milyon yıl önce arasındaki zaman dilimi
距今 227.3 至 205.7 百万年前的时期
Nortqrip
Norgripià
northgrip
Northgrippium
Norgripiense
Norgripiano
Northgrippian
Northgrip
Northgrippien
northgripi
Nordgrippiano
ノースグリッピアン
노스그립절
Nordgripis
Northgrippiaan
Northgrippski
Northgrippiano
nortgrip
Nortgripiyen
诺斯格瑞比阶
0.0082-dən 0.0042 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 0.0082 a 0.0042 milions d'anys enrere
Časové období od 0.0082 do 0.0042 milionů let před naším letopočtem
Ein Zeitraum von 0.0082 bis 0.0042 Millionen Jahren
A time period from 0.0082 to 0.0042 million years ago
Un período de tiempo de 0.0082 a 0.0042 millones de años atrás
0.0082 eta 0.0042 milioi urte arteko denbora-tartea
Aikajakso 0.0082–0.0042 miljoonaa vuotta sitten
Une période de temps de 0.0082 à 0.0042 millions d'années
Egy 0.0082-tól 0.0042 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 0.0082 hingga 0.0042 juta tahun yang lalu
Un periodo di tempo da 0.0082 a 0.0042 milioni di anni fa
0.0082百万年前から0.0042百万年前までの時代
0.0082백만 년 전부터 0.0042백만 년 전까지의 시기
Laikotarpis nuo 0.0082 iki 0.0042 milijonų metų prieš dabartį
Een tijdperiode van 0.0082 tot 0.0042 miljoen jaar geleden
Een tijdsperiode van 0.0082 tot 0.0042 miljoen jaar geleden
En tidsperiode fra 0.0082 til 0.0042 millioner år siden
Okres czasu od 0.0082 do 0.0042 milionów lat temu
Um período de tempo de 0.0082 a 0.0042 milhões de anos atrás
Временной период от 0.0082 до 0.0042 миллионов лет назад
Časové obdobie od 0.0082 do 0.0042 miliónov rokov pred naším letopočtom
0.0082 ile 0.0042 milyon yıl önce arasındaki zaman dilimi
距今 0.0082 至 0.0042 百万年前的时期
Olenekium
Olenekiense
Olenek
olenyoki
Olenekis
Olenekiano
olenek
Oleniokià
Olenekiar
Olénékien
Olenekian
オレネキアン
올레네크절
Olenekien
Olenekiaan
Оленекский
Olenekiyen
奥伦尼克阶
250.8-dən 247.0 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 250.8 a 247.0 milions d'anys enrere
Časové období od 250.8 do 247.0 milionů let před naším letopočtem
Ein Zeitraum von 250.8 bis 247.0 Millionen Jahren
A time period from 250.8 to 247.0 million years ago
Un período de tiempo de 250.8 a 247.0 millones de años atrás
250.8 eta 247.0 milioi urte arteko denbora-tartea
Aikajakso 250.8–247.0 miljoonaa vuotta sitten
Une période de temps de 250.8 à 247.0 millions d'années
Egy 250.8-tól 247.0 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 250.8 hingga 247.0 juta tahun yang lalu
Un periodo di tempo da 250.8 a 247.0 milioni di anni fa
250.8百万年前から247.0百万年前までの時代
250.8백만 년 전부터 247.0백만 년 전까지의 시기
Laikotarpis nuo 250.8 iki 247.0 milijonų metų prieš dabartį
Een tijdperiode van 250.8 tot 247.0 miljoen jaar geleden
Een tijdsperiode van 250.8 tot 247.0 miljoen jaar geleden
En tidsperiode fra 250.8 til 247.0 millioner år siden
Okres czasu od 250.8 do 247.0 milionów lat temu
Um período de tempo de 250.8 a 247.0 milhões de anos atrás
Временной период от 250.8 до 247.0 миллионов лет назад
Časové obdobie od 250.8 do 247.0 miliónov rokov pred naším letopočtom
250.8 ile 247.0 milyon yıl önce arasındaki zaman dilimi
距今 250.8 至 247.0 百万年前的时期
Oxfordium
Oxfordiense
Oxford
Oxfordien
oxfordi
Oksfordis
Oksford
Oxfordiano
oxford
Oxfordià
Oxfordiar
Oxfordian
オックスフォーディアン
옥스퍼드절
Oxfordiaan
Оксфордский
Oksfordiyen
牛津阶
161.5-dən 154.8 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 161.5 a 154.8 milions d'anys enrere
Časové období od 161.5 do 154.8 milionů let před naším letopočtem
Ein Zeitraum von 161.5 bis 154.8 Millionen Jahren
A time period from 161.5 to 154.8 million years ago
Un período de tiempo de 161.5 a 154.8 millones de años atrás
161.5 eta 154.8 milioi urte arteko denbora-tartea
Aikajakso 161.5–154.8 miljoonaa vuotta sitten
Une période de temps de 161.5 à 154.8 millions d'années
Egy 161.5-tól 154.8 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 161.5 hingga 154.8 juta tahun yang lalu
Un periodo di tempo da 161.5 a 154.8 milioni di anni fa
161.5百万年前から154.8百万年前までの時代
161.5백만 년 전부터 154.8백만 년 전까지의 시기
Laikotarpis nuo 161.5 iki 154.8 milijonų metų prieš dabartį
Een tijdperiode van 161.5 tot 154.8 miljoen jaar geleden
Een tijdsperiode van 161.5 tot 154.8 miljoen jaar geleden
En tidsperiode fra 161.5 til 154.8 millioner år siden
Okres czasu od 161.5 do 154.8 milionów lat temu
Um período de tempo de 161.5 a 154.8 milhões de anos atrás
Временной период от 161.5 до 154.8 миллионов лет назад
Časové obdobie od 161.5 do 154.8 miliónov rokov pred naším letopočtom
161.5 ile 154.8 milyon yıl önce arasındaki zaman dilimi
距今 161.5 至 154.8 百万年前的时期
Paibium
Paibiense
Paibien
paibi
Paibis
Paib
Paibiano
Paibi
Paibià
paibian
Paibiar
Paibian
ペイビアン
파이비절
Paibiaan
Паибский
paib
Payibiyen
排碧阶
497.0-dən 494.2 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 497.0 a 494.2 milions d'anys enrere
Časové období od 497.0 do 494.2 milionů let před naším letopočtem
Ein Zeitraum von 497.0 bis 494.2 Millionen Jahren
A time period from 497.0 to 494.2 million years ago
Un período de tiempo de 497.0 a 494.2 millones de años atrás
497.0 eta 494.2 milioi urte arteko denbora-tartea
Aikajakso 497.0–494.2 miljoonaa vuotta sitten
Une période de temps de 497.0 à 494.2 millions d'années
Egy 497.0-tól 494.2 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 497.0 hingga 494.2 juta tahun yang lalu
Un periodo di tempo da 497.0 a 494.2 milioni di anni fa
497.0百万年前から494.2百万年前までの時代
497.0백만 년 전부터 494.2백만 년 전까지의 시기
Laikotarpis nuo 497.0 iki 494.2 milijonų metų prieš dabartį
Een tijdperiode van 497.0 tot 494.2 miljoen jaar geleden
Een tijdsperiode van 497.0 tot 494.2 miljoen jaar geleden
En tidsperiode fra 497.0 til 494.2 millioner år siden
Okres czasu od 497.0 do 494.2 milionów lat temu
Um período de tempo de 497.0 a 494.2 milhões de anos atrás
Временной период от 497.0 до 494.2 миллионов лет назад
Časové obdobie od 497.0 do 494.2 miliónov rokov pred naším letopočtom
497.0 ile 494.2 milyon yıl önce arasındaki zaman dilimi
距今 497.0 至 494.2 百万年前的时期
Piacenzium
piacenzai
Piacenz
Pyaçens
Plasencià
piacenz
Piacenziense
Piacenziano
Piacenziar
Piacenza
Plaisancien
Piacenzian
ピアセンジアン
피아첸차절
Piačenzis
Piacenzien
Piacenziaan
Пьяченцский
piačenz
Piasenziyen
皮亚琴察阶
3.600-dən 2.58 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 3.600 a 2.58 milions d'anys enrere
Časové období od 3.600 do 2.58 milionů let před naším letopočtem
Ein Zeitraum von 3.600 bis 2.58 Millionen Jahren
A time period from 3.600 to 2.58 million years ago
Un período de tiempo de 3.600 a 2.58 millones de años atrás
3.600 eta 2.58 milioi urte arteko denbora-tartea
Aikajakso 3.600–2.58 miljoonaa vuotta sitten
Une période de temps de 3.600 à 2.58 millions d'années
Egy 3.600-tól 2.58 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 3.600 hingga 2.58 juta tahun yang lalu
Un periodo di tempo da 3.600 a 2.58 milioni di anni fa
3.600百万年前から2.58百万年前までの時代
3.600백만 년 전부터 2.58백만 년 전까지의 시기
Laikotarpis nuo 3.600 iki 2.58 milijonų metų prieš dabartį
Een tijdperiode van 3.600 tot 2.58 miljoen jaar geleden
Een tijdsperiode van 3.600 tot 2.58 miljoen jaar geleden
En tidsperiode fra 3.600 til 2.58 millioner år siden
Okres czasu od 3.600 do 2.58 milionów lat temu
Um período de tempo de 3.600 a 2.58 milhões de anos atrás
Временной период от 3.600 до 2.58 миллионов лет назад
Časové obdobie od 3.600 do 2.58 miliónov rokov pred naším letopočtom
3.600 ile 2.58 milyon yıl önce arasındaki zaman dilimi
距今 3.600 至 2.58 百万年前的时期
Pliensbachium
Pliensbachiense
Pliensbachien
pliensbachi
Plynsbachis
Pliensbach
pliensbach
Plinsbax
Pliensbaquià
Pliensbachiano
Pliensbachiar
Pliensbachian
プリンスバキアン
플린스바흐절
Pliensbachiaan
Плинсбахский
Pliyensbahiyen
普林斯巴阶
192.9-dən 184.2 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 192.9 a 184.2 milions d'anys enrere
Časové období od 192.9 do 184.2 milionů let před naším letopočtem
Ein Zeitraum von 192.9 bis 184.2 Millionen Jahren
A time period from 192.9 to 184.2 million years ago
Un período de tiempo de 192.9 a 184.2 millones de años atrás
192.9 eta 184.2 milioi urte arteko denbora-tartea
Aikajakso 192.9–184.2 miljoonaa vuotta sitten
Une période de temps de 192.9 à 184.2 millions d'années
Egy 192.9-tól 184.2 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 192.9 hingga 184.2 juta tahun yang lalu
Un periodo di tempo da 192.9 a 184.2 milioni di anni fa
192.9百万年前から184.2百万年前までの時代
192.9백만 년 전부터 184.2백만 년 전까지의 시기
Laikotarpis nuo 192.9 iki 184.2 milijonų metų prieš dabartį
Een tijdperiode van 192.9 tot 184.2 miljoen jaar geleden
Een tijdsperiode van 192.9 tot 184.2 miljoen jaar geleden
En tidsperiode fra 192.9 til 184.2 millioner år siden
Okres czasu od 192.9 do 184.2 milionów lat temu
Um período de tempo de 192.9 a 184.2 milhões de anos atrás
Временной период от 192.9 до 184.2 миллионов лет назад
Časové obdobie od 192.9 do 184.2 miliónov rokov pred naším letopočtom
192.9 ile 184.2 milyon yıl önce arasındaki zaman dilimi
距今 192.9 至 184.2 百万年前的时期
Pragium
Praha
prágai
Pragis
Prag
Pragiano
prág
Praqa
Praguià
prag
Pragiense
Pragiar
Pragien
Pragian
プラギアン
프라하절
Pragiaan
Пражский
Pragiyen
布拉格阶
413.02-dən 410.62 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 413.02 a 410.62 milions d'anys enrere
Časové období od 413.02 do 410.62 milionů let před naším letopočtem
Ein Zeitraum von 413.02 bis 410.62 Millionen Jahren
A time period from 413.02 to 410.62 million years ago
Un período de tiempo de 413.02 a 410.62 millones de años atrás
413.02 eta 410.62 milioi urte arteko denbora-tartea
Aikajakso 413.02–410.62 miljoonaa vuotta sitten
Une période de temps de 413.02 à 410.62 millions d'années
Egy 413.02-tól 410.62 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 413.02 hingga 410.62 juta tahun yang lalu
Un periodo di tempo da 413.02 a 410.62 milioni di anni fa
413.02百万年前から410.62百万年前までの時代
413.02백만 년 전부터 410.62백만 년 전까지의 시기
Laikotarpis nuo 413.02 iki 410.62 milijonų metų prieš dabartį
Een tijdperiode van 413.02 tot 410.62 miljoen jaar geleden
Een tijdsperiode van 413.02 tot 410.62 miljoen jaar geleden
En tidsperiode fra 413.02 til 410.62 millioner år siden
Okres czasu od 413.02 do 410.62 milionów lat temu
Um período de tempo de 413.02 a 410.62 milhões de anos atrás
Временной период от 413.02 до 410.62 миллионов лет назад
Časové obdobie od 413.02 do 410.62 miliónov rokov pred naším letopočtom
413.02 ile 410.62 milyon yıl önce arasındaki zaman dilimi
距今 413.02 至 410.62 百万年前的时期
Priabonium
Priaboniense
Priabonien
priabonai
Priabonis
Priabon
Priaboniano
priabón
Priabonià
priabon
Priaboniar
Priabona
Priabonian
プリアボニアン
프리아보나절
Priaboniaan
Приабонский
Priaboniyen
普利亚本阶
37.71-dən 33.9 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 37.71 a 33.9 milions d'anys enrere
Časové období od 37.71 do 33.9 milionů let před naším letopočtem
Ein Zeitraum von 37.71 bis 33.9 Millionen Jahren
A time period from 37.71 to 33.9 million years ago
Un período de tiempo de 37.71 a 33.9 millones de años atrás
37.71 eta 33.9 milioi urte arteko denbora-tartea
Aikajakso 37.71–33.9 miljoonaa vuotta sitten
Une période de temps de 37.71 à 33.9 millions d'années
Egy 37.71-tól 33.9 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 37.71 hingga 33.9 juta tahun yang lalu
Un periodo di tempo da 37.71 a 33.9 milioni di anni fa
37.71百万年前から33.9百万年前までの時代
37.71백만 년 전부터 33.9백만 년 전까지의 시기
Laikotarpis nuo 37.71 iki 33.9 milijonų metų prieš dabartį
Een tijdperiode van 37.71 tot 33.9 miljoen jaar geleden
Een tijdsperiode van 37.71 tot 33.9 miljoen jaar geleden
En tidsperiode fra 37.71 til 33.9 millioner år siden
Okres czasu od 37.71 do 33.9 milionów lat temu
Um período de tempo de 37.71 a 33.9 milhões de anos atrás
Временной период от 37.71 до 33.9 миллионов лет назад
Časové obdobie od 37.71 do 33.9 miliónov rokov pred naším letopočtom
37.71 ile 33.9 milyon yıl önce arasındaki zaman dilimi
距今 37.71 至 33.9 百万年前的时期
Pridoli
Prídoli
pridoli
Pržidolis
Przydol
přídol
Prjidol
Pridolià
přídolí
Pridoliano
プリドリ
프리돌리세
Пржидольский
普里道利统
422.7-dən 419.62 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 422.7 a 419.62 milions d'anys enrere
Časové období od 422.7 do 419.62 milionů let před naším letopočtem
Ein Zeitraum von 422.7 bis 419.62 Millionen Jahren
A time period from 422.7 to 419.62 million years ago
Un período de tiempo de 422.7 a 419.62 millones de años atrás
422.7 eta 419.62 milioi urte arteko denbora-tartea
Aikajakso 422.7–419.62 miljoonaa vuotta sitten
Une période de temps de 422.7 à 419.62 millions d'années
Egy 422.7-tól 419.62 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 422.7 hingga 419.62 juta tahun yang lalu
Un periodo di tempo da 422.7 a 419.62 milioni di anni fa
422.7百万年前から419.62百万年前までの時代
422.7백만 년 전부터 419.62백만 년 전까지의 시기
Laikotarpis nuo 422.7 iki 419.62 milijonų metų prieš dabartį
Een tijdperiode van 422.7 tot 419.62 miljoen jaar geleden
Een tijdsperiode van 422.7 tot 419.62 miljoen jaar geleden
En tidsperiode fra 422.7 til 419.62 millioner år siden
Okres czasu od 422.7 do 419.62 milionów lat temu
Um período de tempo de 422.7 a 419.62 milhões de anos atrás
Временной период от 422.7 до 419.62 миллионов лет назад
Časové obdobie od 422.7 do 419.62 miliónov rokov pred naším letopočtom
422.7 ile 419.62 milyon yıl önce arasındaki zaman dilimi
距今 422.7 至 419.62 百万年前的时期
Rhétien
rhaeti
Retis
Ræt
Retyk
rét
Ret
Retià
rhét
Rhaetium
Rhaetiense
Rhaetiano
Rhaetiar
Reetia
Rhaetian
Retico
レーティアン
래티아절
Rhaetien
Rhaetiaan
Рэтский
Resiyen
瑞替阶
205.7-dən 201.4 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 205.7 a 201.4 milions d'anys enrere
Časové období od 205.7 do 201.4 milionů let před naším letopočtem
Ein Zeitraum von 205.7 bis 201.4 Millionen Jahren
A time period from 205.7 to 201.4 million years ago
Un período de tiempo de 205.7 a 201.4 millones de años atrás
205.7 eta 201.4 milioi urte arteko denbora-tartea
Aikajakso 205.7–201.4 miljoonaa vuotta sitten
Une période de temps de 205.7 à 201.4 millions d'années
Egy 205.7-tól 201.4 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 205.7 hingga 201.4 juta tahun yang lalu
Un periodo di tempo da 205.7 a 201.4 milioni di anni fa
205.7百万年前から201.4百万年前までの時代
205.7백만 년 전부터 201.4백만 년 전까지의 시기
Laikotarpis nuo 205.7 iki 201.4 milijonų metų prieš dabartį
Een tijdperiode van 205.7 tot 201.4 miljoen jaar geleden
Een tijdsperiode van 205.7 tot 201.4 miljoen jaar geleden
En tidsperiode fra 205.7 til 201.4 millioner år siden
Okres czasu od 205.7 do 201.4 milionów lat temu
Um período de tempo de 205.7 a 201.4 milhões de anos atrás
Временной период от 205.7 до 201.4 миллионов лет назад
Časové obdobie od 205.7 do 201.4 miliónov rokov pred naším letopočtom
205.7 ile 201.4 milyon yıl önce arasındaki zaman dilimi
距今 205.7 至 201.4 百万年前的时期
Rhuddanium
Rhuddaniense
Rhuddan
Rhuddanien
rhuddani
Rudanis
Raddan
Rhuddanià
rhuddan
Rhuddaniano
Rhuddaniar
Rhuddanian
ラッダニアン
루단절
Rhuddaniaan
Ruddan
Рудданский
rudan
Ruddaniyen
鲁丹阶
443.1-dən 440.5 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 443.1 a 440.5 milions d'anys enrere
Časové období od 443.1 do 440.5 milionů let před naším letopočtem
Ein Zeitraum von 443.1 bis 440.5 Millionen Jahren
A time period from 443.1 to 440.5 million years ago
Un período de tiempo de 443.1 a 440.5 millones de años atrás
443.1 eta 440.5 milioi urte arteko denbora-tartea
Aikajakso 443.1–440.5 miljoonaa vuotta sitten
Une période de temps de 443.1 à 440.5 millions d'années
Egy 443.1-tól 440.5 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 443.1 hingga 440.5 juta tahun yang lalu
Un periodo di tempo da 443.1 a 440.5 milioni di anni fa
443.1百万年前から440.5百万年前までの時代
443.1백만 년 전부터 440.5백만 년 전까지의 시기
Laikotarpis nuo 443.1 iki 440.5 milijonų metų prieš dabartį
Een tijdperiode van 443.1 tot 440.5 miljoen jaar geleden
Een tijdsperiode van 443.1 tot 440.5 miljoen jaar geleden
En tidsperiode fra 443.1 til 440.5 millioner år siden
Okres czasu od 443.1 do 440.5 milionów lat temu
Um período de tempo de 443.1 a 440.5 milhões de anos atrás
Временной период от 443.1 до 440.5 миллионов лет назад
Časové obdobie od 443.1 do 440.5 miliónov rokov pred naším letopočtom
443.1 ile 440.5 milyon yıl önce arasındaki zaman dilimi
距今 443.1 至 440.5 百万年前的时期
Roadium
Roadiense
Road
Roadien
roadi
Roadis
Roadiano
road
Roadià
Roadiar
Roadian
ローディアン
로드절
Roadiaan
Roadyjski
Роудский
Rodiyen
罗德阶
274.4-dən 266.9 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 274.4 a 266.9 milions d'anys enrere
Časové období od 274.4 do 266.9 milionů let před naším letopočtem
Ein Zeitraum von 274.4 bis 266.9 Millionen Jahren
A time period from 274.4 to 266.9 million years ago
Un período de tiempo de 274.4 a 266.9 millones de años atrás
274.4 eta 266.9 milioi urte arteko denbora-tartea
Aikajakso 274.4–266.9 miljoonaa vuotta sitten
Une période de temps de 274.4 à 266.9 millions d'années
Egy 274.4-tól 266.9 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 274.4 hingga 266.9 juta tahun yang lalu
Un periodo di tempo da 274.4 a 266.9 milioni di anni fa
274.4百万年前から266.9百万年前までの時代
274.4백만 년 전부터 266.9백만 년 전까지의 시기
Laikotarpis nuo 274.4 iki 266.9 milijonų metų prieš dabartį
Een tijdperiode van 274.4 tot 266.9 miljoen jaar geleden
Een tijdsperiode van 274.4 tot 266.9 miljoen jaar geleden
En tidsperiode fra 274.4 til 266.9 millioner år siden
Okres czasu od 274.4 do 266.9 milionów lat temu
Um período de tempo de 274.4 a 266.9 milhões de anos atrás
Временной период от 274.4 до 266.9 миллионов лет назад
Časové obdobie od 274.4 do 266.9 miliónov rokov pred naším letopočtom
274.4 ile 266.9 milyon yıl önce arasındaki zaman dilimi
距今 274.4 至 266.9 百万年前的时期
Rupelium
Rupeliense
Rupel
Rupélien
rupeli
Rupeliano
rupel
Ryupel
Rupelià
Rupeliar
Rupelian
ルペリアン
루펠절
Riupelis
Rupelien
Rupeliaan
Рюпельский
Rupeliyen
吕珀尔阶
33.9-dən 27.30 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 33.9 a 27.30 milions d'anys enrere
Časové období od 33.9 do 27.30 milionů let před naším letopočtem
Ein Zeitraum von 33.9 bis 27.30 Millionen Jahren
A time period from 33.9 to 27.30 million years ago
Un período de tiempo de 33.9 a 27.30 millones de años atrás
33.9 eta 27.30 milioi urte arteko denbora-tartea
Aikajakso 33.9–27.30 miljoonaa vuotta sitten
Une période de temps de 33.9 à 27.30 millions d'années
Egy 33.9-tól 27.30 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 33.9 hingga 27.30 juta tahun yang lalu
Un periodo di tempo da 33.9 a 27.30 milioni di anni fa
33.9百万年前から27.30百万年前までの時代
33.9백만 년 전부터 27.30백만 년 전까지의 시기
Laikotarpis nuo 33.9 iki 27.30 milijonų metų prieš dabartį
Een tijdperiode van 33.9 tot 27.30 miljoen jaar geleden
Een tijdsperiode van 33.9 tot 27.30 miljoen jaar geleden
En tidsperiode fra 33.9 til 27.30 millioner år siden
Okres czasu od 33.9 do 27.30 milionów lat temu
Um período de tempo de 33.9 a 27.30 milhões de anos atrás
Временной период от 33.9 до 27.30 миллионов лет назад
Časové obdobie od 33.9 do 27.30 miliónov rokov pred naším letopočtom
33.9 ile 27.30 milyon yıl önce arasındaki zaman dilimi
距今 33.9 至 27.30 百万年前的时期
Sakmarium
Sakmariense
Sakmarien
szakmarai
Sakmaris
Sakmar
Sakmariano
sakmar
Sakmarià
Sakmariar
Sakmara
Sakmarian
サクマーリアン
사크마라절
Sakmariaan
Сакмарский
Sakmariyen
萨克马尔阶
293.52-dən 290.1 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 293.52 a 290.1 milions d'anys enrere
Časové období od 293.52 do 290.1 milionů let před naším letopočtem
Ein Zeitraum von 293.52 bis 290.1 Millionen Jahren
A time period from 293.52 to 290.1 million years ago
Un período de tiempo de 293.52 a 290.1 millones de años atrás
293.52 eta 290.1 milioi urte arteko denbora-tartea
Aikajakso 293.52–290.1 miljoonaa vuotta sitten
Une période de temps de 293.52 à 290.1 millions d'années
Egy 293.52-tól 290.1 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 293.52 hingga 290.1 juta tahun yang lalu
Un periodo di tempo da 293.52 a 290.1 milioni di anni fa
293.52百万年前から290.1百万年前までの時代
293.52백만 년 전부터 290.1백만 년 전까지의 시기
Laikotarpis nuo 293.52 iki 290.1 milijonų metų prieš dabartį
Een tijdperiode van 293.52 tot 290.1 miljoen jaar geleden
Een tijdsperiode van 293.52 tot 290.1 miljoen jaar geleden
En tidsperiode fra 293.52 til 290.1 millioner år siden
Okres czasu od 293.52 do 290.1 milionów lat temu
Um período de tempo de 293.52 a 290.1 milhões de anos atrás
Временной период от 293.52 до 290.1 миллионов лет назад
Časové obdobie od 293.52 do 290.1 miliónov rokov pred naším letopočtom
293.52 ile 290.1 milyon yıl önce arasındaki zaman dilimi
距今 293.52 至 290.1 百万年前的时期
Sandbium
Sandbiense
Sandbien
sandbi
Sandbis
Sandbiano
Sandbi
Sandbià
sandbian
Sandbiar
Sandby
Sandbian
サンドビアン
샌드비절
Sandbiaan
Сандбийский
sandby
Sandbiyen
桑比阶
458.2-dən 452.8 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 458.2 a 452.8 milions d'anys enrere
Časové období od 458.2 do 452.8 milionů let před naším letopočtem
Ein Zeitraum von 458.2 bis 452.8 Millionen Jahren
A time period from 458.2 to 452.8 million years ago
Un período de tiempo de 458.2 a 452.8 millones de años atrás
458.2 eta 452.8 milioi urte arteko denbora-tartea
Aikajakso 458.2–452.8 miljoonaa vuotta sitten
Une période de temps de 458.2 à 452.8 millions d'années
Egy 458.2-tól 452.8 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 458.2 hingga 452.8 juta tahun yang lalu
Un periodo di tempo da 458.2 a 452.8 milioni di anni fa
458.2百万年前から452.8百万年前までの時代
458.2백만 년 전부터 452.8백만 년 전까지의 시기
Laikotarpis nuo 458.2 iki 452.8 milijonų metų prieš dabartį
Een tijdperiode van 458.2 tot 452.8 miljoen jaar geleden
Een tijdsperiode van 458.2 tot 452.8 miljoen jaar geleden
En tidsperiode fra 458.2 til 452.8 millioner år siden
Okres czasu od 458.2 do 452.8 milionów lat temu
Um período de tempo de 458.2 a 452.8 milhões de anos atrás
Временной период от 458.2 до 452.8 миллионов лет назад
Časové obdobie od 458.2 do 452.8 miliónov rokov pred naším letopočtom
458.2 ile 452.8 milyon yıl önce arasındaki zaman dilimi
距今 458.2 至 452.8 百万年前的时期
Santonium
Santoniense
Santon
Santonien
santoni
Santonis
Santoniano
santón
Santonià
santon
Santoniar
Santonian
サントニアン
산토눔절
Santoniaan
Сантонский
Santoniyen
圣通阶
85.7-dən 83.6 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 85.7 a 83.6 milions d'anys enrere
Časové období od 85.7 do 83.6 milionů let před naším letopočtem
Ein Zeitraum von 85.7 bis 83.6 Millionen Jahren
A time period from 85.7 to 83.6 million years ago
Un período de tiempo de 85.7 a 83.6 millones de años atrás
85.7 eta 83.6 milioi urte arteko denbora-tartea
Aikajakso 85.7–83.6 miljoonaa vuotta sitten
Une période de temps de 85.7 à 83.6 millions d'années
Egy 85.7-tól 83.6 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 85.7 hingga 83.6 juta tahun yang lalu
Un periodo di tempo da 85.7 a 83.6 milioni di anni fa
85.7百万年前から83.6百万年前までの時代
85.7백만 년 전부터 83.6백만 년 전까지의 시기
Laikotarpis nuo 85.7 iki 83.6 milijonų metų prieš dabartį
Een tijdperiode van 85.7 tot 83.6 miljoen jaar geleden
Een tijdsperiode van 85.7 tot 83.6 miljoen jaar geleden
En tidsperiode fra 85.7 til 83.6 millioner år siden
Okres czasu od 85.7 do 83.6 milionów lat temu
Um período de tempo de 85.7 a 83.6 milhões de anos atrás
Временной период от 85.7 до 83.6 миллионов лет назад
Časové obdobie od 85.7 do 83.6 miliónov rokov pred naším letopočtom
85.7 ile 83.6 milyon yıl önce arasındaki zaman dilimi
距今 85.7 至 83.6 百万年前的时期
Selandiense
Sélandien
selandi
Selandiano
seland
Zeland
Selandià
Seelandium
Selandiar
Sjellanti
Selandian
セランディアン
셀란절
Zėladis
Selandien
Selandiaan
Sjælland
Selan
Зеландский
Selandiyen
塞兰特阶
61.66-dən 59.24 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 61.66 a 59.24 milions d'anys enrere
Časové období od 61.66 do 59.24 milionů let před naším letopočtem
Ein Zeitraum von 61.66 bis 59.24 Millionen Jahren
A time period from 61.66 to 59.24 million years ago
Un período de tiempo de 61.66 a 59.24 millones de años atrás
61.66 eta 59.24 milioi urte arteko denbora-tartea
Aikajakso 61.66–59.24 miljoonaa vuotta sitten
Une période de temps de 61.66 à 59.24 millions d'années
Egy 61.66-tól 59.24 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 61.66 hingga 59.24 juta tahun yang lalu
Un periodo di tempo da 61.66 a 59.24 milioni di anni fa
61.66百万年前から59.24百万年前までの時代
61.66백만 년 전부터 59.24백만 년 전까지의 시기
Laikotarpis nuo 61.66 iki 59.24 milijonų metų prieš dabartį
Een tijdperiode van 61.66 tot 59.24 miljoen jaar geleden
Een tijdsperiode van 61.66 tot 59.24 miljoen jaar geleden
En tidsperiode fra 61.66 til 59.24 millioner år siden
Okres czasu od 61.66 do 59.24 milionów lat temu
Um período de tempo de 61.66 a 59.24 milhões de anos atrás
Временной период от 61.66 до 59.24 миллионов лет назад
Časové obdobie od 61.66 do 59.24 miliónov rokov pred naším letopočtom
61.66 ile 59.24 milyon yıl önce arasındaki zaman dilimi
距今 61.66 至 59.24 百万年前的时期
Serpukhovium
Serpukhov
Serpukhovien
szerpuhovi
Serpuchovis
serpuchov
Serpuxov
Serpukhovià
Serpukhoviense
Serpukhoviano
Serpukhoviar
Serpukhovian
サープコビアン
세르푸호프절
Serpukhoviaan
Sierpuchów
Серпуховский
Serpukoviyen
谢尔普霍夫阶
330.3-dən 323.4 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 330.3 a 323.4 milions d'anys enrere
Časové období od 330.3 do 323.4 milionů let před naším letopočtem
Ein Zeitraum von 330.3 bis 323.4 Millionen Jahren
A time period from 330.3 to 323.4 million years ago
Un período de tiempo de 330.3 a 323.4 millones de años atrás
330.3 eta 323.4 milioi urte arteko denbora-tartea
Aikajakso 330.3–323.4 miljoonaa vuotta sitten
Une période de temps de 330.3 à 323.4 millions d'années
Egy 330.3-tól 323.4 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 330.3 hingga 323.4 juta tahun yang lalu
Un periodo di tempo da 330.3 a 323.4 milioni di anni fa
330.3百万年前から323.4百万年前までの時代
330.3백만 년 전부터 323.4백만 년 전까지의 시기
Laikotarpis nuo 330.3 iki 323.4 milijonų metų prieš dabartį
Een tijdperiode van 330.3 tot 323.4 miljoen jaar geleden
Een tijdsperiode van 330.3 tot 323.4 miljoen jaar geleden
En tidsperiode fra 330.3 til 323.4 millioner år siden
Okres czasu od 330.3 do 323.4 milionów lat temu
Um período de tempo de 330.3 a 323.4 milhões de anos atrás
Временной период от 330.3 до 323.4 миллионов лет назад
Časové obdobie od 330.3 do 323.4 miliónov rokov pred naším letopočtom
330.3 ile 323.4 milyon yıl önce arasındaki zaman dilimi
距今 330.3 至 323.4 百万年前的时期
Serravallium
Serravalliense
Serravallien
serravallei
Seravalis
Serraval
Serraval·lià
serravall
Serravaliano
Serravalliar
Serravalle
Serravallian
Serravalliano
サーラバリアン
세라발레절
Serravalliaan
Serawal
Серравальский
seraval
Serravaliyen
塞拉瓦莱阶
13.82-dən 11.63 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 13.82 a 11.63 milions d'anys enrere
Časové období od 13.82 do 11.63 milionů let před naším letopočtem
Ein Zeitraum von 13.82 bis 11.63 Millionen Jahren
A time period from 13.82 to 11.63 million years ago
Un período de tiempo de 13.82 a 11.63 millones de años atrás
13.82 eta 11.63 milioi urte arteko denbora-tartea
Aikajakso 13.82–11.63 miljoonaa vuotta sitten
Une période de temps de 13.82 à 11.63 millions d'années
Egy 13.82-tól 11.63 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 13.82 hingga 11.63 juta tahun yang lalu
Un periodo di tempo da 13.82 a 11.63 milioni di anni fa
13.82百万年前から11.63百万年前までの時代
13.82백만 년 전부터 11.63백만 년 전까지의 시기
Laikotarpis nuo 13.82 iki 11.63 milijonų metų prieš dabartį
Een tijdperiode van 13.82 tot 11.63 miljoen jaar geleden
Een tijdsperiode van 13.82 tot 11.63 miljoen jaar geleden
En tidsperiode fra 13.82 til 11.63 millioner år siden
Okres czasu od 13.82 do 11.63 milionów lat temu
Um período de tempo de 13.82 a 11.63 milhões de anos atrás
Временной период от 13.82 до 11.63 миллионов лет назад
Časové obdobie od 13.82 do 11.63 miliónov rokov pred naším letopočtom
13.82 ile 11.63 milyon yıl önce arasındaki zaman dilimi
距今 13.82 至 11.63 百万年前的时期
Sheinwoodium
Sheinwoodiense
Sheinwood
Sheinwoodien
sheinwoodi
Šeinvudis
Sheinwoodiano
sheinwood
Şeynvud
Sheinwoodià
Sheinwoodiar
Sheinwoodian
シェイウッディアン
셰인우드절
Sheinwoodiaan
Шейнвудский
Şenvudiyen
申伍德阶
432.9-dən 430.6 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 432.9 a 430.6 milions d'anys enrere
Časové období od 432.9 do 430.6 milionů let před naším letopočtem
Ein Zeitraum von 432.9 bis 430.6 Millionen Jahren
A time period from 432.9 to 430.6 million years ago
Un período de tiempo de 432.9 a 430.6 millones de años atrás
432.9 eta 430.6 milioi urte arteko denbora-tartea
Aikajakso 432.9–430.6 miljoonaa vuotta sitten
Une période de temps de 432.9 à 430.6 millions d'années
Egy 432.9-tól 430.6 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 432.9 hingga 430.6 juta tahun yang lalu
Un periodo di tempo da 432.9 a 430.6 milioni di anni fa
432.9百万年前から430.6百万年前までの時代
432.9백만 년 전부터 430.6백만 년 전까지의 시기
Laikotarpis nuo 432.9 iki 430.6 milijonų metų prieš dabartį
Een tijdperiode van 432.9 tot 430.6 miljoen jaar geleden
Een tijdsperiode van 432.9 tot 430.6 miljoen jaar geleden
En tidsperiode fra 432.9 til 430.6 millioner år siden
Okres czasu od 432.9 do 430.6 milionów lat temu
Um período de tempo de 432.9 a 430.6 milhões de anos atrás
Временной период от 432.9 до 430.6 миллионов лет назад
Časové obdobie od 432.9 do 430.6 miliónov rokov pred naším letopočtom
432.9 ile 430.6 milyon yıl önce arasındaki zaman dilimi
距今 432.9 至 430.6 百万年前的时期
Sinemuriense
Sinemur
Sinémurien
sinemuri
Synemur
Sinemuriano
sinemúr
Sinemyur
Sinemurià
sinemur
Sinemurium
Sinemuriar
Sinemurian
シネムリアン
시네무룸절
Sinemiuris
Sinemurien
Sinemuriaan
Синемюрский
Sinemuriyen
辛涅缪尔阶
199.5-dən 192.9 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 199.5 a 192.9 milions d'anys enrere
Časové období od 199.5 do 192.9 milionů let před naším letopočtem
Ein Zeitraum von 199.5 bis 192.9 Millionen Jahren
A time period from 199.5 to 192.9 million years ago
Un período de tiempo de 199.5 a 192.9 millones de años atrás
199.5 eta 192.9 milioi urte arteko denbora-tartea
Aikajakso 199.5–192.9 miljoonaa vuotta sitten
Une période de temps de 199.5 à 192.9 millions d'années
Egy 199.5-tól 192.9 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 199.5 hingga 192.9 juta tahun yang lalu
Un periodo di tempo da 199.5 a 192.9 milioni di anni fa
199.5百万年前から192.9百万年前までの時代
199.5백만 년 전부터 192.9백만 년 전까지의 시기
Laikotarpis nuo 199.5 iki 192.9 milijonų metų prieš dabartį
Een tijdperiode van 199.5 tot 192.9 miljoen jaar geleden
Een tijdsperiode van 199.5 tot 192.9 miljoen jaar geleden
En tidsperiode fra 199.5 til 192.9 millioner år siden
Okres czasu od 199.5 do 192.9 milionów lat temu
Um período de tempo de 199.5 a 192.9 milhões de anos atrás
Временной период от 199.5 до 192.9 миллионов лет назад
Časové obdobie od 199.5 do 192.9 miliónov rokov pred naším letopočtom
199.5 ile 192.9 milyon yıl önce arasındaki zaman dilimi
距今 199.5 至 192.9 百万年前的时期
Telychium
Telychiense
Telych
Télychien
telychi
Telychiano
telych
Teliç
Telychià
Telychiar
Telychian
テリチアン
텔리치절
Telyčis
Telychien
Telychiaan
Теличский
Telisiyen
特列奇阶
438.6-dən 432.9 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 438.6 a 432.9 milions d'anys enrere
Časové období od 438.6 do 432.9 milionů let před naším letopočtem
Ein Zeitraum von 438.6 bis 432.9 Millionen Jahren
A time period from 438.6 to 432.9 million years ago
Un período de tiempo de 438.6 a 432.9 millones de años atrás
438.6 eta 432.9 milioi urte arteko denbora-tartea
Aikajakso 438.6–432.9 miljoonaa vuotta sitten
Une période de temps de 438.6 à 432.9 millions d'années
Egy 438.6-tól 432.9 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 438.6 hingga 432.9 juta tahun yang lalu
Un periodo di tempo da 438.6 a 432.9 milioni di anni fa
438.6百万年前から432.9百万年前までの時代
438.6백만 년 전부터 432.9백만 년 전까지의 시기
Laikotarpis nuo 438.6 iki 432.9 milijonų metų prieš dabartį
Een tijdperiode van 438.6 tot 432.9 miljoen jaar geleden
Een tijdsperiode van 438.6 tot 432.9 miljoen jaar geleden
En tidsperiode fra 438.6 til 432.9 millioner år siden
Okres czasu od 438.6 do 432.9 milionów lat temu
Um período de tempo de 438.6 a 432.9 milhões de anos atrás
Временной период от 438.6 до 432.9 миллионов лет назад
Časové obdobie od 438.6 do 432.9 miliónov rokov pred naším letopočtom
438.6 ile 432.9 milyon yıl önce arasındaki zaman dilimi
距今 438.6 至 432.9 百万年前的时期
Thanetium
Thanetiense
Thanet
Thanétien
thaneti
Tanetis
tanet
Tanet
Thanetià
thanet
Thanetiano
Thanetiar
Thanetian
サネティアン
타넷절
Thanetien
Thanetiaan
Tenet
Танетский
Tanesiyen
坦尼特阶
59.24-dən 56.00 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 59.24 a 56.00 milions d'anys enrere
Časové období od 59.24 do 56.00 milionů let před naším letopočtem
Ein Zeitraum von 59.24 bis 56.00 Millionen Jahren
A time period from 59.24 to 56.00 million years ago
Un período de tiempo de 59.24 a 56.00 millones de años atrás
59.24 eta 56.00 milioi urte arteko denbora-tartea
Aikajakso 59.24–56.00 miljoonaa vuotta sitten
Une période de temps de 59.24 à 56.00 millions d'années
Egy 59.24-tól 56.00 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 59.24 hingga 56.00 juta tahun yang lalu
Un periodo di tempo da 59.24 a 56.00 milioni di anni fa
59.24百万年前から56.00百万年前までの時代
59.24백만 년 전부터 56.00백만 년 전까지의 시기
Laikotarpis nuo 59.24 iki 56.00 milijonų metų prieš dabartį
Een tijdperiode van 59.24 tot 56.00 miljoen jaar geleden
Een tijdsperiode van 59.24 tot 56.00 miljoen jaar geleden
En tidsperiode fra 59.24 til 56.00 millioner år siden
Okres czasu od 59.24 do 56.00 milionów lat temu
Um período de tempo de 59.24 a 56.00 milhões de anos atrás
Временной период от 59.24 до 56.00 миллионов лет назад
Časové obdobie od 59.24 do 56.00 miliónov rokov pred naším letopočtom
59.24 ile 56.00 milyon yıl önce arasındaki zaman dilimi
距今 59.24 至 56.00 百万年前的时期
Tithonium
Tithonien
Titonis
titón
Titon
Titonià
tithon
Titoniense
Titoniano
Tithoniar
tithoni
Tithonian
チトニアン
티토누스절
Tithoniaan
Tithon
Tytoń
Tithoniano
Титонский
Titoniyen
提塘阶
149.2-dən 143.1 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 149.2 a 143.1 milions d'anys enrere
Časové období od 149.2 do 143.1 milionů let před naším letopočtem
Ein Zeitraum von 149.2 bis 143.1 Millionen Jahren
A time period from 149.2 to 143.1 million years ago
Un período de tiempo de 149.2 a 143.1 millones de años atrás
149.2 eta 143.1 milioi urte arteko denbora-tartea
Aikajakso 149.2–143.1 miljoonaa vuotta sitten
Une période de temps de 149.2 à 143.1 millions d'années
Egy 149.2-tól 143.1 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 149.2 hingga 143.1 juta tahun yang lalu
Un periodo di tempo da 149.2 a 143.1 milioni di anni fa
149.2百万年前から143.1百万年前までの時代
149.2백만 년 전부터 143.1백만 년 전까지의 시기
Laikotarpis nuo 149.2 iki 143.1 milijonų metų prieš dabartį
Een tijdperiode van 149.2 tot 143.1 miljoen jaar geleden
Een tijdsperiode van 149.2 tot 143.1 miljoen jaar geleden
En tidsperiode fra 149.2 til 143.1 millioner år siden
Okres czasu od 149.2 do 143.1 milionów lat temu
Um período de tempo de 149.2 a 143.1 milhões de anos atrás
Временной период от 149.2 до 143.1 миллионов лет назад
Časové obdobie od 149.2 do 143.1 miliónov rokov pred naším letopočtom
149.2 ile 143.1 milyon yıl önce arasındaki zaman dilimi
距今 149.2 至 143.1 百万年前的时期
Toarcium
Toarciense
Toarc
Toarcien
toarci
Toaris
Toark
Toarciano
toark
Toar
Toarcià
Toarciar
Toarcian
トアルシアン
토아르시움절
Toarciaan
Тоарский
Toarsiyen
托阿尔阶
184.2-dən 174.7 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 184.2 a 174.7 milions d'anys enrere
Časové období od 184.2 do 174.7 milionů let před naším letopočtem
Ein Zeitraum von 184.2 bis 174.7 Millionen Jahren
A time period from 184.2 to 174.7 million years ago
Un período de tiempo de 184.2 a 174.7 millones de años atrás
184.2 eta 174.7 milioi urte arteko denbora-tartea
Aikajakso 184.2–174.7 miljoonaa vuotta sitten
Une période de temps de 184.2 à 174.7 millions d'années
Egy 184.2-tól 174.7 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 184.2 hingga 174.7 juta tahun yang lalu
Un periodo di tempo da 184.2 a 174.7 milioni di anni fa
184.2百万年前から174.7百万年前までの時代
184.2백만 년 전부터 174.7백만 년 전까지의 시기
Laikotarpis nuo 184.2 iki 174.7 milijonų metų prieš dabartį
Een tijdperiode van 184.2 tot 174.7 miljoen jaar geleden
Een tijdsperiode van 184.2 tot 174.7 miljoen jaar geleden
En tidsperiode fra 184.2 til 174.7 millioner år siden
Okres czasu od 184.2 do 174.7 milionów lat temu
Um período de tempo de 184.2 a 174.7 milhões de anos atrás
Временной период от 184.2 до 174.7 миллионов лет назад
Časové obdobie od 184.2 do 174.7 miliónov rokov pred naším letopočtom
184.2 ile 174.7 milyon yıl önce arasındaki zaman dilimi
距今 184.2 至 174.7 百万年前的时期
Tortonium
Tortoniense
Tortonien
tortonai
Tortonis
Torton
Tortoniano
tortón
Tortonià
torton
Tortoniar
Tortona
Tortonian
トートニアン
토르토나절
Tortoniaan
Тортонский
Tortoniyen
托尔托纳阶
11.63-dən 7.246 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 11.63 a 7.246 milions d'anys enrere
Časové období od 11.63 do 7.246 milionů let před naším letopočtem
Ein Zeitraum von 11.63 bis 7.246 Millionen Jahren
A time period from 11.63 to 7.246 million years ago
Un período de tiempo de 11.63 a 7.246 millones de años atrás
11.63 eta 7.246 milioi urte arteko denbora-tartea
Aikajakso 11.63–7.246 miljoonaa vuotta sitten
Une période de temps de 11.63 à 7.246 millions d'années
Egy 11.63-tól 7.246 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 11.63 hingga 7.246 juta tahun yang lalu
Un periodo di tempo da 11.63 a 7.246 milioni di anni fa
11.63百万年前から7.246百万年前までの時代
11.63백만 년 전부터 7.246백만 년 전까지의 시기
Laikotarpis nuo 11.63 iki 7.246 milijonų metų prieš dabartį
Een tijdperiode van 11.63 tot 7.246 miljoen jaar geleden
Een tijdsperiode van 11.63 tot 7.246 miljoen jaar geleden
En tidsperiode fra 11.63 til 7.246 millioner år siden
Okres czasu od 11.63 do 7.246 milionów lat temu
Um período de tempo de 11.63 a 7.246 milhões de anos atrás
Временной период от 11.63 до 7.246 миллионов лет назад
Časové obdobie od 11.63 do 7.246 miliónov rokov pred naším letopočtom
11.63 ile 7.246 milyon yıl önce arasındaki zaman dilimi
距今 11.63 至 7.246 百万年前的时期
Tournaisium
Tournaisiense
Tournaisien
Turnėjis
Turnej
Turne
Tournaisià
tournai
Tournaisiano
Tournaisiar
Tournai
Tournaisian
トルネーシアン
투르네절
Tournaisiaan
Турнейский
turné
Turneziyen
杜内阶
358.86-dən 346.7 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 358.86 a 346.7 milions d'anys enrere
Časové období od 358.86 do 346.7 milionů let před naším letopočtem
Ein Zeitraum von 358.86 bis 346.7 Millionen Jahren
A time period from 358.86 to 346.7 million years ago
Un período de tiempo de 358.86 a 346.7 millones de años atrás
358.86 eta 346.7 milioi urte arteko denbora-tartea
Aikajakso 358.86–346.7 miljoonaa vuotta sitten
Une période de temps de 358.86 à 346.7 millions d'années
Egy 358.86-tól 346.7 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 358.86 hingga 346.7 juta tahun yang lalu
Un periodo di tempo da 358.86 a 346.7 milioni di anni fa
358.86百万年前から346.7百万年前までの時代
358.86백만 년 전부터 346.7백만 년 전까지의 시기
Laikotarpis nuo 358.86 iki 346.7 milijonų metų prieš dabartį
Een tijdperiode van 358.86 tot 346.7 miljoen jaar geleden
Een tijdsperiode van 358.86 tot 346.7 miljoen jaar geleden
En tidsperiode fra 358.86 til 346.7 millioner år siden
Okres czasu od 358.86 do 346.7 milionów lat temu
Um período de tempo de 358.86 a 346.7 milhões de anos atrás
Временной период от 358.86 до 346.7 миллионов лет назад
Časové obdobie od 358.86 do 346.7 miliónov rokov pred naším letopočtom
358.86 ile 346.7 milyon yıl önce arasındaki zaman dilimi
距今 358.86 至 346.7 百万年前的时期
Tremadocium
Tremadociense
Tremadoc
Trémadocien
tremadoci
Tremadokis
Tremadok
Tremadociano
tremadok
Tremadocià
Tremadociar
Tremadocian
トレマドキアン
트레마독절
Tremadocien
Tremadociaan
Тремадокский
Tremadosiyen
特马豆克阶
486.85-dən 477.1 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 486.85 a 477.1 milions d'anys enrere
Časové období od 486.85 do 477.1 milionů let před naším letopočtem
Ein Zeitraum von 486.85 bis 477.1 Millionen Jahren
A time period from 486.85 to 477.1 million years ago
Un período de tiempo de 486.85 a 477.1 millones de años atrás
486.85 eta 477.1 milioi urte arteko denbora-tartea
Aikajakso 486.85–477.1 miljoonaa vuotta sitten
Une période de temps de 486.85 à 477.1 millions d'années
Egy 486.85-tól 477.1 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 486.85 hingga 477.1 juta tahun yang lalu
Un periodo di tempo da 486.85 a 477.1 milioni di anni fa
486.85百万年前から477.1百万年前までの時代
486.85백만 년 전부터 477.1백만 년 전까지의 시기
Laikotarpis nuo 486.85 iki 477.1 milijonų metų prieš dabartį
Een tijdperiode van 486.85 tot 477.1 miljoen jaar geleden
Een tijdsperiode van 486.85 tot 477.1 miljoen jaar geleden
En tidsperiode fra 486.85 til 477.1 millioner år siden
Okres czasu od 486.85 do 477.1 milionów lat temu
Um período de tempo de 486.85 a 477.1 milhões de anos atrás
Временной период от 486.85 до 477.1 миллионов лет назад
Časové obdobie od 486.85 do 477.1 miliónov rokov pred naším letopočtom
486.85 ile 477.1 milyon yıl önce arasındaki zaman dilimi
距今 486.85 至 477.1 百万年前的时期
Turonium
Turoniense
Turonien
Turonis
Turon
Turoniano
turón
Turonià
turon
Turoniar
Turonia
turoni
Turonian
チューロニアン
투로니아절
Turoniaan
Туронский
Turoniyen
土伦阶
93.9-dən 89.8 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 93.9 a 89.8 milions d'anys enrere
Časové období od 93.9 do 89.8 milionů let před naším letopočtem
Ein Zeitraum von 93.9 bis 89.8 Millionen Jahren
A time period from 93.9 to 89.8 million years ago
Un período de tiempo de 93.9 a 89.8 millones de años atrás
93.9 eta 89.8 milioi urte arteko denbora-tartea
Aikajakso 93.9–89.8 miljoonaa vuotta sitten
Une période de temps de 93.9 à 89.8 millions d'années
Egy 93.9-tól 89.8 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 93.9 hingga 89.8 juta tahun yang lalu
Un periodo di tempo da 93.9 a 89.8 milioni di anni fa
93.9百万年前から89.8百万年前までの時代
93.9백만 년 전부터 89.8백만 년 전까지의 시기
Laikotarpis nuo 93.9 iki 89.8 milijonų metų prieš dabartį
Een tijdperiode van 93.9 tot 89.8 miljoen jaar geleden
Een tijdsperiode van 93.9 tot 89.8 miljoen jaar geleden
En tidsperiode fra 93.9 til 89.8 millioner år siden
Okres czasu od 93.9 do 89.8 milionów lat temu
Um período de tempo de 93.9 a 89.8 milhões de anos atrás
Временной период от 93.9 до 89.8 миллионов лет назад
Časové obdobie od 93.9 do 89.8 miliónov rokov pred naším letopočtom
93.9 ile 89.8 milyon yıl önce arasındaki zaman dilimi
距今 93.9 至 89.8 百万年前的时期
Üst Pleystosen
Superior Plistocè
svrchní pleistocén
Obere Pleistozän
Superior Pleistocene
Superior Pleistoceno
Goi Pleistozeno
Ylä Pleistoseeni
Supérieur Pléistocène
felső/késő pleisztocén
Atas Pleistosen
Superiore Pleistocene
上部／後期 更新統／世
높은 플라이스토세
Viršutinė Pleistocenas
Boven Pleistoceen
Øvre Pleistocen
Górny Plejstocen
Верхний Плейстоцен
vrchná pleistocén
Üst Pleyistosen
上侏罗统 更新统
0.129-dən 0.0117 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 0.129 a 0.0117 milions d'anys enrere
Časové období od 0.129 do 0.0117 milionů let před naším letopočtem
Ein Zeitraum von 0.129 bis 0.0117 Millionen Jahren
A time period from 0.129 to 0.0117 million years ago
Un período de tiempo de 0.129 a 0.0117 millones de años atrás
0.129 eta 0.0117 milioi urte arteko denbora-tartea
Aikajakso 0.129–0.0117 miljoonaa vuotta sitten
Une période de temps de 0.129 à 0.0117 millions d'années
Egy 0.129-tól 0.0117 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 0.129 hingga 0.0117 juta tahun yang lalu
Un periodo di tempo da 0.129 a 0.0117 milioni di anni fa
0.129百万年前から0.0117百万年前までの時代
0.129백만 년 전부터 0.0117백만 년 전까지의 시기
Laikotarpis nuo 0.129 iki 0.0117 milijonų metų prieš dabartį
Een tijdperiode van 0.129 tot 0.0117 miljoen jaar geleden
Een tijdsperiode van 0.129 tot 0.0117 miljoen jaar geleden
En tidsperiode fra 0.129 til 0.0117 millioner år siden
Okres czasu od 0.129 do 0.0117 milionów lat temu
Um período de tempo de 0.129 a 0.0117 milhões de anos atrás
Временной период от 0.129 до 0.0117 миллионов лет назад
Časové obdobie od 0.129 do 0.0117 miliónov rokov pred naším letopočtom
0.129 ile 0.0117 milyon yıl önce arasındaki zaman dilimi
距今 0.129 至 0.0117 百万年前的时期
Upper Pleistocene
Valanginium
Valanginiense
Valangin
Valanginien
valangini
Valendis
Walanżyn
Valanginiano
valanžin
Valanjin
Valanginià
valangin
Valanginiar
Valanginian
バランジニアン
발랑절
Valanginiaan
Валанжинский
Valanjiniyen
瓦兰今阶
137.05-dən 132.6 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 137.05 a 132.6 milions d'anys enrere
Časové období od 137.05 do 132.6 milionů let před naším letopočtem
Ein Zeitraum von 137.05 bis 132.6 Millionen Jahren
A time period from 137.05 to 132.6 million years ago
Un período de tiempo de 137.05 a 132.6 millones de años atrás
137.05 eta 132.6 milioi urte arteko denbora-tartea
Aikajakso 137.05–132.6 miljoonaa vuotta sitten
Une période de temps de 137.05 à 132.6 millions d'années
Egy 137.05-tól 132.6 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 137.05 hingga 132.6 juta tahun yang lalu
Un periodo di tempo da 137.05 a 132.6 milioni di anni fa
137.05百万年前から132.6百万年前までの時代
137.05백만 년 전부터 132.6백만 년 전까지의 시기
Laikotarpis nuo 137.05 iki 132.6 milijonų metų prieš dabartį
Een tijdperiode van 137.05 tot 132.6 miljoen jaar geleden
Een tijdsperiode van 137.05 tot 132.6 miljoen jaar geleden
En tidsperiode fra 137.05 til 132.6 millioner år siden
Okres czasu od 137.05 do 132.6 milionów lat temu
Um período de tempo de 137.05 a 132.6 milhões de anos atrás
Временной период от 137.05 до 132.6 миллионов лет назад
Časové obdobie od 137.05 do 132.6 miliónov rokov pred naším letopočtom
137.05 ile 132.6 milyon yıl önce arasındaki zaman dilimi
距今 137.05 至 132.6 百万年前的时期
Viseum
Viseense
Viséen
viséi
Wizen
Viseano
Vize
Viseà
visé
Visear
Vise
Visean
ビゼーアン
비제절
Vizėjis
Viseaan
Visé
Визейский
Vizeyen
维宪阶
346.7-dən 330.3 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 346.7 a 330.3 milions d'anys enrere
Časové období od 346.7 do 330.3 milionů let před naším letopočtem
Ein Zeitraum von 346.7 bis 330.3 Millionen Jahren
A time period from 346.7 to 330.3 million years ago
Un período de tiempo de 346.7 a 330.3 millones de años atrás
346.7 eta 330.3 milioi urte arteko denbora-tartea
Aikajakso 346.7–330.3 miljoonaa vuotta sitten
Une période de temps de 346.7 à 330.3 millions d'années
Egy 346.7-tól 330.3 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 346.7 hingga 330.3 juta tahun yang lalu
Un periodo di tempo da 346.7 a 330.3 milioni di anni fa
346.7百万年前から330.3百万年前までの時代
346.7백만 년 전부터 330.3백만 년 전까지의 시기
Laikotarpis nuo 346.7 iki 330.3 milijonų metų prieš dabartį
Een tijdperiode van 346.7 tot 330.3 miljoen jaar geleden
Een tijdsperiode van 346.7 tot 330.3 miljoen jaar geleden
En tidsperiode fra 346.7 til 330.3 millioner år siden
Okres czasu od 346.7 do 330.3 milionów lat temu
Um período de tempo de 346.7 a 330.3 milhões de anos atrás
Временной период от 346.7 до 330.3 миллионов лет назад
Časové obdobie od 346.7 do 330.3 miliónov rokov pred naším letopočtom
346.7 ile 330.3 milyon yıl önce arasındaki zaman dilimi
距今 346.7 至 330.3 百万年前的时期
Wordium
Wordiense
Word
Wordien
wordi
Vordis
Wordiano
word
Vord
Wordià
Wordiar
Wordian
ウォーディアン
워드절
Wordiaan
Вордский
Vordiyen
沃德阶
266.9-dən 264.28 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 266.9 a 264.28 milions d'anys enrere
Časové období od 266.9 do 264.28 milionů let před naším letopočtem
Ein Zeitraum von 266.9 bis 264.28 Millionen Jahren
A time period from 266.9 to 264.28 million years ago
Un período de tiempo de 266.9 a 264.28 millones de años atrás
266.9 eta 264.28 milioi urte arteko denbora-tartea
Aikajakso 266.9–264.28 miljoonaa vuotta sitten
Une période de temps de 266.9 à 264.28 millions d'années
Egy 266.9-tól 264.28 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 266.9 hingga 264.28 juta tahun yang lalu
Un periodo di tempo da 266.9 a 264.28 milioni di anni fa
266.9百万年前から264.28百万年前までの時代
266.9백만 년 전부터 264.28백만 년 전까지의 시기
Laikotarpis nuo 266.9 iki 264.28 milijonų metų prieš dabartį
Een tijdperiode van 266.9 tot 264.28 miljoen jaar geleden
Een tijdsperiode van 266.9 tot 264.28 miljoen jaar geleden
En tidsperiode fra 266.9 til 264.28 millioner år siden
Okres czasu od 266.9 do 264.28 milionów lat temu
Um período de tempo de 266.9 a 264.28 milhões de anos atrás
Временной период от 266.9 до 264.28 миллионов лет назад
Časové obdobie od 266.9 do 264.28 miliónov rokov pred naším letopočtom
266.9 ile 264.28 milyon yıl önce arasındaki zaman dilimi
距今 266.9 至 264.28 百万年前的时期
Wuchiapingium
Wuchiapingiense
Wuchiapingien
wuchiapingi
Wuchiaping
Wuchiapingiano
Vuçiapinq
Wuchiapingià
wuchiaping
Wuchiapingiar
Wuchiapingian
ウーチャーピンジアン
우지아핑절
Vučiapingis
Wuchiapingiaan
Wujiaping
Вучапинский
wutiapching
Vuçepingiyen
吴家坪阶
259.857-dən 254.14 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 259.857 a 254.14 milions d'anys enrere
Časové období od 259.857 do 254.14 milionů let před naším letopočtem
Ein Zeitraum von 259.857 bis 254.14 Millionen Jahren
A time period from 259.857 to 254.14 million years ago
Un período de tiempo de 259.857 a 254.14 millones de años atrás
259.857 eta 254.14 milioi urte arteko denbora-tartea
Aikajakso 259.857–254.14 miljoonaa vuotta sitten
Une période de temps de 259.857 à 254.14 millions d'années
Egy 259.857-tól 254.14 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 259.857 hingga 254.14 juta tahun yang lalu
Un periodo di tempo da 259.857 a 254.14 milioni di anni fa
259.857百万年前から254.14百万年前までの時代
259.857백만 년 전부터 254.14백만 년 전까지의 시기
Laikotarpis nuo 259.857 iki 254.14 milijonų metų prieš dabartį
Een tijdperiode van 259.857 tot 254.14 miljoen jaar geleden
Een tijdsperiode van 259.857 tot 254.14 miljoen jaar geleden
En tidsperiode fra 259.857 til 254.14 millioner år siden
Okres czasu od 259.857 do 254.14 milionów lat temu
Um período de tempo de 259.857 a 254.14 milhões de anos atrás
Временной период от 259.857 до 254.14 миллионов лет назад
Časové obdobie od 259.857 do 254.14 miliónov rokov pred naším letopočtom
259.857 ile 254.14 milyon yıl önce arasındaki zaman dilimi
距今 259.857 至 254.14 百万年前的时期
Vuliu
Wuliuà
wuliuan
Stufe 5
Wuliuense
Wuliuano
5 Estai
Wuliu
Wuliuen
wuliui
Wuliuan
ウリューアン
울리우절
Vulujis
Wuliuien
Wuliuaan
Ярус 5
wuliu
Vuliuyan
乌溜阶
506.5-dən 504.5 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 506.5 a 504.5 milions d'anys enrere
Časové období od 506.5 do 504.5 milionů let před naším letopočtem
Ein Zeitraum von 506.5 bis 504.5 Millionen Jahren
A time period from 506.5 to 504.5 million years ago
Un período de tiempo de 506.5 a 504.5 millones de años atrás
506.5 eta 504.5 milioi urte arteko denbora-tartea
Aikajakso 506.5–504.5 miljoonaa vuotta sitten
Une période de temps de 506.5 à 504.5 millions d'années
Egy 506.5-tól 504.5 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 506.5 hingga 504.5 juta tahun yang lalu
Un periodo di tempo da 506.5 a 504.5 milioni di anni fa
506.5百万年前から504.5百万年前までの時代
506.5백만 년 전부터 504.5백만 년 전까지의 시기
Laikotarpis nuo 506.5 iki 504.5 milijonų metų prieš dabartį
Een tijdperiode van 506.5 tot 504.5 miljoen jaar geleden
Een tijdsperiode van 506.5 tot 504.5 miljoen jaar geleden
En tidsperiode fra 506.5 til 504.5 millioner år siden
Okres czasu od 506.5 do 504.5 milionów lat temu
Um período de tempo de 506.5 a 504.5 milhões de anos atrás
Временной период от 506.5 до 504.5 миллионов лет назад
Časové obdobie od 506.5 do 504.5 miliónov rokov pred naším letopočtom
506.5 ile 504.5 milyon yıl önce arasındaki zaman dilimi
距今 506.5 至 504.5 百万年前的时期
Ypresiense
Ypres
Yprésien
ypresi
Ypris
ypres
İpr
Ipresià
Ypresium
Ypresiano
Ypresiar
Ypresian
イプレシアン
이퍼르절
Ypresien
Ypresiaan
Ипрский
İpresiyen
伊普里斯阶
56.00-dən 48.07 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 56.00 a 48.07 milions d'anys enrere
Časové období od 56.00 do 48.07 milionů let před naším letopočtem
Ein Zeitraum von 56.00 bis 48.07 Millionen Jahren
A time period from 56.00 to 48.07 million years ago
Un período de tiempo de 56.00 a 48.07 millones de años atrás
56.00 eta 48.07 milioi urte arteko denbora-tartea
Aikajakso 56.00–48.07 miljoonaa vuotta sitten
Une période de temps de 56.00 à 48.07 millions d'années
Egy 56.00-tól 48.07 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 56.00 hingga 48.07 juta tahun yang lalu
Un periodo di tempo da 56.00 a 48.07 milioni di anni fa
56.00百万年前から48.07百万年前までの時代
56.00백만 년 전부터 48.07백만 년 전까지의 시기
Laikotarpis nuo 56.00 iki 48.07 milijonų metų prieš dabartį
Een tijdperiode van 56.00 tot 48.07 miljoen jaar geleden
Een tijdsperiode van 56.00 tot 48.07 miljoen jaar geleden
En tidsperiode fra 56.00 til 48.07 millioner år siden
Okres czasu od 56.00 do 48.07 milionów lat temu
Um período de tempo de 56.00 a 48.07 milhões de anos atrás
Временной период от 56.00 до 48.07 миллионов лет назад
Časové obdobie od 56.00 do 48.07 miliónov rokov pred naším letopočtom
56.00 ile 48.07 milyon yıl önce arasındaki zaman dilimi
距今 56.00 至 48.07 百万年前的时期
Zancléen
Zanklis
Zancleano
Zankl
Zanclià
zancl
Zancleum
Zancliense
Zancliano
Zanclear
Zancle
zanclei
Zanclean
ザンクリアン
장클레절
Zancleaan
Zanklean
Занклский
zankl
Zankliyen
赞克勒阶
5.333-dən 3.600 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 5.333 a 3.600 milions d'anys enrere
Časové období od 5.333 do 3.600 milionů let před naším letopočtem
Ein Zeitraum von 5.333 bis 3.600 Millionen Jahren
A time period from 5.333 to 3.600 million years ago
Un período de tiempo de 5.333 a 3.600 millones de años atrás
5.333 eta 3.600 milioi urte arteko denbora-tartea
Aikajakso 5.333–3.600 miljoonaa vuotta sitten
Une période de temps de 5.333 à 3.600 millions d'années
Egy 5.333-tól 3.600 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 5.333 hingga 3.600 juta tahun yang lalu
Un periodo di tempo da 5.333 a 3.600 milioni di anni fa
5.333百万年前から3.600百万年前までの時代
5.333백만 년 전부터 3.600백만 년 전까지의 시기
Laikotarpis nuo 5.333 iki 3.600 milijonų metų prieš dabartį
Een tijdperiode van 5.333 tot 3.600 miljoen jaar geleden
Een tijdsperiode van 5.333 tot 3.600 miljoen jaar geleden
En tidsperiode fra 5.333 til 3.600 millioner år siden
Okres czasu od 5.333 do 3.600 milionów lat temu
Um período de tempo de 5.333 a 3.600 milhões de anos atrás
Временной период от 5.333 до 3.600 миллионов лет назад
Časové obdobie od 5.333 do 3.600 miliónov rokov pred naším letopočtom
5.333 ile 3.600 milyon yıl önce arasındaki zaman dilimi
距今 5.333 至 3.600 百万年前的时期
Eonlar
Eons
Eony
Äonen
Eones
Eoiak
Eonit
Éons
Eonok
Eon
Eoni
累代
누대
Eonai
Eonen
Eoner
Эоны
Eóny
An eon is the largest formal geochronologic time unit and is equivalent to a chronostratigraphic eonothem. These are several hundred million years to two billion years in length
Archaikum
Arcaico
Archéen
archaikum
Arkeikum
Archaik
Hadeano
Arxey
Arqueà
Arkear
Arkeeinen
Archean
Archeano
太古（累）界／代（始生（累）界／代）
시 생 누 대
Archėjus
Archeïcum
Archeaan
Arqueano
Архейская
Arkeen
太 古 宇
4031-dən 2500 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 4031 a 2500 milions d'anys enrere
Časové období od 4031 do 2500 milionů let před naším letopočtem
Ein Zeitraum von 4031 bis 2500 Millionen Jahren
A time period from 4031 to 2500 million years ago
Un período de tiempo de 4031 a 2500 millones de años atrás
4031 eta 2500 milioi urte arteko denbora-tartea
Aikajakso 4031–2500 miljoonaa vuotta sitten
Une période de temps de 4031 à 2500 millions d'années
Egy 4031-tól 2500 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 4031 hingga 2500 juta tahun yang lalu
Un periodo di tempo da 4031 a 2500 milioni di anni fa
4031百万年前から2500百万年前までの時代
4031백만 년 전부터 2500백만 년 전까지의 시기
Laikotarpis nuo 4031 iki 2500 milijonų metų prieš dabartį
Een tijdperiode van 4031 tot 2500 miljoen jaar geleden
Een tijdsperiode van 4031 tot 2500 miljoen jaar geleden
En tidsperiode fra 4031 til 2500 millioner år siden
Okres czasu od 4031 do 2500 milionów lat temu
Um período de tempo de 4031 a 2500 milhões de anos atrás
Временной период от 4031 до 2500 миллионов лет назад
Časové obdobie od 4031 do 2500 miliónov rokov pred naším letopočtom
4031 ile 2500 milyon yıl önce arasındaki zaman dilimi
距今 4031 至 2500 百万年前的时期
Hadaikum
Hadéen
Hadeïcum
Hadeikum
Hade
Hadeà
hadaikum
Hádico
Hadear
Haades
hadeikum
Hadean
Adeano
冥王界／代
명왕누대
Hadas
Hadeaan
Hadeik
Хaдейская
hadean
Hadeen
冥古宇
4567-dən 4031 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 4567 a 4031 milions d'anys enrere
Časové období od 4567 do 4031 milionů let před naším letopočtem
Ein Zeitraum von 4567 bis 4031 Millionen Jahren
A time period from 4567 to 4031 million years ago
Un período de tiempo de 4567 a 4031 millones de años atrás
4567 eta 4031 milioi urte arteko denbora-tartea
Aikajakso 4567–4031 miljoonaa vuotta sitten
Une période de temps de 4567 à 4031 millions d'années
Egy 4567-tól 4031 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 4567 hingga 4031 juta tahun yang lalu
Un periodo di tempo da 4567 a 4031 milioni di anni fa
4567百万年前から4031百万年前までの時代
4567백만 년 전부터 4031백만 년 전까지의 시기
Laikotarpis nuo 4567 iki 4031 milijonų metų prieš dabartį
Een tijdperiode van 4567 tot 4031 miljoen jaar geleden
Een tijdsperiode van 4567 tot 4031 miljoen jaar geleden
En tidsperiode fra 4567 til 4031 millioner år siden
Okres czasu od 4567 do 4031 milionów lat temu
Um período de tempo de 4567 a 4031 milhões de anos atrás
Временной период от 4567 до 4031 миллионов лет назад
Časové obdobie od 4567 do 4031 miliónov rokov pred naším letopočtom
4567 ile 4031 milyon yıl önce arasındaki zaman dilimi
距今 4567 至 4031 百万年前的时期
Phanerozoikum
Fanerozoico
Phanérozoïque
fanerozoikum
Fanerozojus
Fanerozoikum
Fanerozoik
Fanerozoy
Fanerozoic
Fanerozoiko
Fanerotsooinen
顕生（累）界／代
현생누대
Fanerozoïcum
Фанерозойская
Fanerozoyik
显 生 宇
538.8-dən 0 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 538.8 a 0 milions d'anys enrere
Časové období od 538.8 do 0 milionů let před naším letopočtem
Ein Zeitraum von 538.8 bis 0 Millionen Jahren
A time period from 538.8 to 0 million years ago
Un período de tiempo de 538.8 a 0 millones de años atrás
538.8 eta 0 milioi urte arteko denbora-tartea
Aikajakso 538.8–0 miljoonaa vuotta sitten
Une période de temps de 538.8 à 0 millions d'années
Egy 538.8-tól 0 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 538.8 hingga 0 juta tahun yang lalu
Un periodo di tempo da 538.8 a 0 milioni di anni fa
538.8百万年前から0百万年前までの時代
538.8백만 년 전부터 0백만 년 전까지의 시기
Laikotarpis nuo 538.8 iki 0 milijonų metų prieš dabartį
Een tijdperiode van 538.8 tot 0 miljoen jaar geleden
Een tijdsperiode van 538.8 tot 0 miljoen jaar geleden
En tidsperiode fra 538.8 til 0 millioner år siden
Okres czasu od 538.8 do 0 milionów lat temu
Um período de tempo de 538.8 a 0 milhões de anos atrás
Временной период от 538.8 до 0 миллионов лет назад
Časové obdobie od 538.8 do 0 miliónov rokov pred naším letopočtom
538.8 ile 0 milyon yıl önce arasındaki zaman dilimi
距今 538.8 至 0 百万年前的时期
Phanerozoic
Proterozoikum
Proterozoico
Proterozojus
Proterozoïcum
Proterozoik
proterozoikum
Proterozoy
Proterozoic
Proterozoiko
Proterotsooinen
Protéozoïque
原生（累）界／代
원생누대
Протерозойская
Proterozoyik
元 古 宇
2500-dən 538.8 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 2500 a 538.8 milions d'anys enrere
Časové období od 2500 do 538.8 milionů let před naším letopočtem
Ein Zeitraum von 2500 bis 538.8 Millionen Jahren
A time period from 2500 to 538.8 million years ago
Un período de tiempo de 2500 a 538.8 millones de años atrás
2500 eta 538.8 milioi urte arteko denbora-tartea
Aikajakso 2500–538.8 miljoonaa vuotta sitten
Une période de temps de 2500 à 538.8 millions d'années
Egy 2500-tól 538.8 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 2500 hingga 538.8 juta tahun yang lalu
Un periodo di tempo da 2500 a 538.8 milioni di anni fa
2500百万年前から538.8百万年前までの時代
2500백만 년 전부터 538.8백만 년 전까지의 시기
Laikotarpis nuo 2500 iki 538.8 milijonų metų prieš dabartį
Een tijdperiode van 2500 tot 538.8 miljoen jaar geleden
Een tijdsperiode van 2500 tot 538.8 miljoen jaar geleden
En tidsperiode fra 2500 til 538.8 millioner år siden
Okres czasu od 2500 do 538.8 milionów lat temu
Um período de tempo de 2500 a 538.8 milhões de anos atrás
Временной период от 2500 до 538.8 миллионов лет назад
Časové obdobie od 2500 do 538.8 miliónov rokov pred naším letopočtom
2500 ile 538.8 milyon yıl önce arasındaki zaman dilimi
距今 2500 至 538.8 百万年前的时期
Epoxalar
Èpoques
Epochy
Epochen
Épocas
Epokak
Epookit
Époques
Epochák
Kala
Epoche
Epochos
Epoches
Epoker
Epoki
Эпохи
Epoklar
An epoch is the second smallest geochronologic unit. It is equivalent to a chronostratigraphic series. These are hundreds of thousands to tens of millions of years length
Epochs
Şöbə 2
Segona sèrie
oddělení 2
Serie 2
2 Serie
Sarja 2
Séries 2
2. sorozat
Seri 2
シリーズ 2
제2세
2 skyrius
Seria 2
Série 2
Отдел 2
séria 2
第二统
521.0-dən 506.5 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 521.0 a 506.5 milions d'anys enrere
Časové období od 521.0 do 506.5 milionů let před naším letopočtem
Ein Zeitraum von 521.0 bis 506.5 Millionen Jahren
A time period from 521.0 to 506.5 million years ago
Un período de tiempo de 521.0 a 506.5 millones de años atrás
521.0 eta 506.5 milioi urte arteko denbora-tartea
Aikajakso 521.0–506.5 miljoonaa vuotta sitten
Une période de temps de 521.0 à 506.5 millions d'années
Egy 521.0-tól 506.5 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 521.0 hingga 506.5 juta tahun yang lalu
Un periodo di tempo da 521.0 a 506.5 milioni di anni fa
521.0百万年前から506.5百万年前までの時代
521.0백만 년 전부터 506.5백만 년 전까지의 시기
Laikotarpis nuo 521.0 iki 506.5 milijonų metų prieš dabartį
Een tijdperiode van 521.0 tot 506.5 miljoen jaar geleden
Een tijdsperiode van 521.0 tot 506.5 miljoen jaar geleden
En tidsperiode fra 521.0 til 506.5 millioner år siden
Okres czasu od 521.0 do 506.5 milionów lat temu
Um período de tempo de 521.0 a 506.5 milhões de anos atrás
Временной период от 521.0 до 506.5 миллионов лет назад
Časové obdobie od 521.0 do 506.5 miliónov rokov pred naším letopočtom
521.0 ile 506.5 milyon yıl önce arasındaki zaman dilimi
距今 521.0 至 506.5 百万年前的时期
Series 2
Cisuralium
Cisuraliense
Cisural
Cisuralien
Cisuraliano
cisural
Cisuralià
Cisuraliar
ciszuráli
Cisuralian
シスウラリアン
시스우랄세
Cisuraliaan
Приуральский
Sisuraliyen
乌拉尔统
298.9-dən 274.4 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 298.9 a 274.4 milions d'anys enrere
Časové období od 298.9 do 274.4 milionů let před naším letopočtem
Ein Zeitraum von 298.9 bis 274.4 Millionen Jahren
A time period from 298.9 to 274.4 million years ago
Un período de tiempo de 298.9 a 274.4 millones de años atrás
298.9 eta 274.4 milioi urte arteko denbora-tartea
Aikajakso 298.9–274.4 miljoonaa vuotta sitten
Une période de temps de 298.9 à 274.4 millions d'années
Egy 298.9-tól 274.4 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 298.9 hingga 274.4 juta tahun yang lalu
Un periodo di tempo da 298.9 a 274.4 milioni di anni fa
298.9百万年前から274.4百万年前までの時代
298.9백만 년 전부터 274.4백만 년 전까지의 시기
Laikotarpis nuo 298.9 iki 274.4 milijonų metų prieš dabartį
Een tijdperiode van 298.9 tot 274.4 miljoen jaar geleden
Een tijdsperiode van 298.9 tot 274.4 miljoen jaar geleden
En tidsperiode fra 298.9 til 274.4 millioner år siden
Okres czasu od 298.9 do 274.4 milionów lat temu
Um período de tempo de 298.9 a 274.4 milhões de anos atrás
Временной период от 298.9 до 274.4 миллионов лет назад
Časové obdobie od 298.9 do 274.4 miliónov rokov pred naším letopočtom
298.9 ile 274.4 milyon yıl önce arasındaki zaman dilimi
距今 298.9 至 274.4 百万年前的时期
Eozän
Eoceno
Eoseeni
eocén
Eocenas
Eoceen
Eocen
Eosen
Eocè
Eozeno
Éocène
Eocene
始新統／世
에오세
Эоцен
始新统
56.00-dən 33.9 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 56.00 a 33.9 milions d'anys enrere
Časové období od 56.00 do 33.9 milionů let před naším letopočtem
Ein Zeitraum von 56.00 bis 33.9 Millionen Jahren
A time period from 56.00 to 33.9 million years ago
Un período de tiempo de 56.00 a 33.9 millones de años atrás
56.00 eta 33.9 milioi urte arteko denbora-tartea
Aikajakso 56.00–33.9 miljoonaa vuotta sitten
Une période de temps de 56.00 à 33.9 millions d'années
Egy 56.00-tól 33.9 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 56.00 hingga 33.9 juta tahun yang lalu
Un periodo di tempo da 56.00 a 33.9 milioni di anni fa
56.00百万年前から33.9百万年前までの時代
56.00백만 년 전부터 33.9백만 년 전까지의 시기
Laikotarpis nuo 56.00 iki 33.9 milijonų metų prieš dabartį
Een tijdperiode van 56.00 tot 33.9 miljoen jaar geleden
Een tijdsperiode van 56.00 tot 33.9 miljoen jaar geleden
En tidsperiode fra 56.00 til 33.9 millioner år siden
Okres czasu od 56.00 do 33.9 milionów lat temu
Um período de tempo de 56.00 a 33.9 milhões de anos atrás
Временной период от 56.00 до 33.9 миллионов лет назад
Časové obdobie od 56.00 do 33.9 miliónov rokov pred naším letopočtom
56.00 ile 33.9 milyon yıl önce arasındaki zaman dilimi
距今 56.00 至 33.9 百万年前的时期
Furongium
Furong
Furongien
furongi
Furongis
Furongiano
furong
Furonq
Furongià
Furongiense
Furongiar
Furongian
フロンギアン
푸롱세
Furongiaan
Фуронгский
Frongiyen
芙蓉统
497.0-dən 486.85 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 497.0 a 486.85 milions d'anys enrere
Časové období od 497.0 do 486.85 milionů let před naším letopočtem
Ein Zeitraum von 497.0 bis 486.85 Millionen Jahren
A time period from 497.0 to 486.85 million years ago
Un período de tiempo de 497.0 a 486.85 millones de años atrás
497.0 eta 486.85 milioi urte arteko denbora-tartea
Aikajakso 497.0–486.85 miljoonaa vuotta sitten
Une période de temps de 497.0 à 486.85 millions d'années
Egy 497.0-tól 486.85 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 497.0 hingga 486.85 juta tahun yang lalu
Un periodo di tempo da 497.0 a 486.85 milioni di anni fa
497.0百万年前から486.85百万年前までの時代
497.0백만 년 전부터 486.85백만 년 전까지의 시기
Laikotarpis nuo 497.0 iki 486.85 milijonų metų prieš dabartį
Een tijdperiode van 497.0 tot 486.85 miljoen jaar geleden
Een tijdsperiode van 497.0 tot 486.85 miljoen jaar geleden
En tidsperiode fra 497.0 til 486.85 millioner år siden
Okres czasu od 497.0 do 486.85 milionów lat temu
Um período de tempo de 497.0 a 486.85 milhões de anos atrás
Временной период от 497.0 до 486.85 миллионов лет назад
Časové obdobie od 497.0 do 486.85 miliónov rokov pred naším letopočtom
497.0 ile 486.85 milyon yıl önce arasındaki zaman dilimi
距今 497.0 至 486.85 百万年前的时期
Guadalupium
Guadalupiense
Guadalupiano
guadalup
Qvadelupa
Guadalupià
Guadalupiar
Guadalupe
Guadalupien
guadalupi
Guadalupian
グアダルピアン
과달루페세
Guadalupiaan
Guadalup
Gwadalup
Гваделупский
Guadalupiyen
瓜德鲁普统
274.4-dən 259.857 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 274.4 a 259.857 milions d'anys enrere
Časové období od 274.4 do 259.857 milionů let před naším letopočtem
Ein Zeitraum von 274.4 bis 259.857 Millionen Jahren
A time period from 274.4 to 259.857 million years ago
Un período de tiempo de 274.4 a 259.857 millones de años atrás
274.4 eta 259.857 milioi urte arteko denbora-tartea
Aikajakso 274.4–259.857 miljoonaa vuotta sitten
Une période de temps de 274.4 à 259.857 millions d'années
Egy 274.4-tól 259.857 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 274.4 hingga 259.857 juta tahun yang lalu
Un periodo di tempo da 274.4 a 259.857 milioni di anni fa
274.4百万年前から259.857百万年前までの時代
274.4백만 년 전부터 259.857백만 년 전까지의 시기
Laikotarpis nuo 274.4 iki 259.857 milijonų metų prieš dabartį
Een tijdperiode van 274.4 tot 259.857 miljoen jaar geleden
Een tijdsperiode van 274.4 tot 259.857 miljoen jaar geleden
En tidsperiode fra 274.4 til 259.857 millioner år siden
Okres czasu od 274.4 do 259.857 milionów lat temu
Um período de tempo de 274.4 a 259.857 milhões de anos atrás
Временной период от 274.4 до 259.857 миллионов лет назад
Časové obdobie od 274.4 do 259.857 miliónov rokov pred naším letopočtom
274.4 ile 259.857 milyon yıl önce arasındaki zaman dilimi
距今 274.4 至 259.857 百万年前的时期
Holozän
Holoceno
Holoseeni
Holocène
holocén
Holocenas
Holoceen
Holocen
Holosen
Holocè
Holozeno
Olocene
完新統／世
홀로세
Holocene
Голоцен
全新统
0.0117-dən 0 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 0.0117 a 0 milions d'anys enrere
Časové období od 0.0117 do 0 milionů let před naším letopočtem
Ein Zeitraum von 0.0117 bis 0 Millionen Jahren
A time period from 0.0117 to 0 million years ago
Un período de tiempo de 0.0117 a 0 millones de años atrás
0.0117 eta 0 milioi urte arteko denbora-tartea
Aikajakso 0.0117–0 miljoonaa vuotta sitten
Une période de temps de 0.0117 à 0 millions d'années
Egy 0.0117-tól 0 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 0.0117 hingga 0 juta tahun yang lalu
Un periodo di tempo da 0.0117 a 0 milioni di anni fa
0.0117百万年前から0百万年前までの時代
0.0117백만 년 전부터 0백만 년 전까지의 시기
Laikotarpis nuo 0.0117 iki 0 milijonų metų prieš dabartį
Een tijdperiode van 0.0117 tot 0 miljoen jaar geleden
Een tijdsperiode van 0.0117 tot 0 miljoen jaar geleden
En tidsperiode fra 0.0117 til 0 millioner år siden
Okres czasu od 0.0117 do 0 milionów lat temu
Um período de tempo de 0.0117 a 0 milhões de anos atrás
Временной период от 0.0117 до 0 миллионов лет назад
Časové obdobie od 0.0117 do 0 miliónov rokov pred naším letopočtom
0.0117 ile 0 milyon yıl önce arasındaki zaman dilimi
距今 0.0117 至 0 百万年前的时期
Llandovery
llandoveryi
Landoveris
Landower
Landoveriy
Llandoverià
llandovery
Llandoveriano
ランドベリ
란도베리세
Лландоверийский
landover
Landoveri
兰多维列统
443.1-dən 432.9 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 443.1 a 432.9 milions d'anys enrere
Časové období od 443.1 do 432.9 milionů let před naším letopočtem
Ein Zeitraum von 443.1 bis 432.9 Millionen Jahren
A time period from 443.1 to 432.9 million years ago
Un período de tiempo de 443.1 a 432.9 millones de años atrás
443.1 eta 432.9 milioi urte arteko denbora-tartea
Aikajakso 443.1–432.9 miljoonaa vuotta sitten
Une période de temps de 443.1 à 432.9 millions d'années
Egy 443.1-tól 432.9 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 443.1 hingga 432.9 juta tahun yang lalu
Un periodo di tempo da 443.1 a 432.9 milioni di anni fa
443.1百万年前から432.9百万年前までの時代
443.1백만 년 전부터 432.9백만 년 전까지의 시기
Laikotarpis nuo 443.1 iki 432.9 milijonų metų prieš dabartį
Een tijdperiode van 443.1 tot 432.9 miljoen jaar geleden
Een tijdsperiode van 443.1 tot 432.9 miljoen jaar geleden
En tidsperiode fra 443.1 til 432.9 millioner år siden
Okres czasu od 443.1 do 432.9 milionów lat temu
Um período de tempo de 443.1 a 432.9 milhões de anos atrás
Временной период от 443.1 до 432.9 миллионов лет назад
Časové obdobie od 443.1 do 432.9 miliónov rokov pred naším letopočtom
443.1 ile 432.9 milyon yıl önce arasındaki zaman dilimi
距今 443.1 至 432.9 百万年前的时期
Lopingium
Lopingiense
Loping
Lopingien
lopingi
Lopingiano
loping
Lepinq
Lopingià
Lopingiar
Lopingian
ローピンジアン
러핑세
Lopingiaan
Лопинский
Lopingiyen
乐平统
259.857-dən 251.902 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 259.857 a 251.902 milions d'anys enrere
Časové období od 259.857 do 251.902 milionů let před naším letopočtem
Ein Zeitraum von 259.857 bis 251.902 Millionen Jahren
A time period from 259.857 to 251.902 million years ago
Un período de tiempo de 259.857 a 251.902 millones de años atrás
259.857 eta 251.902 milioi urte arteko denbora-tartea
Aikajakso 259.857–251.902 miljoonaa vuotta sitten
Une période de temps de 259.857 à 251.902 millions d'années
Egy 259.857-tól 251.902 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 259.857 hingga 251.902 juta tahun yang lalu
Un periodo di tempo da 259.857 a 251.902 milioni di anni fa
259.857百万年前から251.902百万年前までの時代
259.857백만 년 전부터 251.902백만 년 전까지의 시기
Laikotarpis nuo 259.857 iki 251.902 milijonų metų prieš dabartį
Een tijdperiode van 259.857 tot 251.902 miljoen jaar geleden
Een tijdsperiode van 259.857 tot 251.902 miljoen jaar geleden
En tidsperiode fra 259.857 til 251.902 millioner år siden
Okres czasu od 259.857 do 251.902 milionów lat temu
Um período de tempo de 259.857 a 251.902 milhões de anos atrás
Временной период от 259.857 до 251.902 миллионов лет назад
Časové obdobie od 259.857 do 251.902 miliónov rokov pred naším letopočtom
259.857 ile 251.902 milyon yıl önce arasındaki zaman dilimi
距今 259.857 至 251.902 百万年前的时期
spodní křída
Onder Krijt
Alt Təbaşir
Inferior Cretaci
Untere Kreide
Inferior Cretácico
Behe Kretazeo
Ala Liitu
Inférieur Crétacé
alsó/kora kréta
Lebih rendah Kapur
Inferiore Cretacico
下部／前期 白亜系／紀
낮추다 백악기
Žemutinis Kreida
Undre Kritt
Dolny Kreda
Inferior Cretáceo
Нижний Меловая
spodná krieda
Alt Kretase
下侏罗统 白 垩系
143.1-dən 100.5 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 143.1 a 100.5 milions d'anys enrere
Časové období od 143.1 do 100.5 milionů let před naším letopočtem
Ein Zeitraum von 143.1 bis 100.5 Millionen Jahren
A time period from 143.1 to 100.5 million years ago
Un período de tiempo de 143.1 a 100.5 millones de años atrás
143.1 eta 100.5 milioi urte arteko denbora-tartea
Aikajakso 143.1–100.5 miljoonaa vuotta sitten
Une période de temps de 143.1 à 100.5 millions d'années
Egy 143.1-tól 100.5 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 143.1 hingga 100.5 juta tahun yang lalu
Un periodo di tempo da 143.1 a 100.5 milioni di anni fa
143.1百万年前から100.5百万年前までの時代
143.1백만 년 전부터 100.5백만 년 전까지의 시기
Laikotarpis nuo 143.1 iki 100.5 milijonų metų prieš dabartį
Een tijdperiode van 143.1 tot 100.5 miljoen jaar geleden
Een tijdsperiode van 143.1 tot 100.5 miljoen jaar geleden
En tidsperiode fra 143.1 til 100.5 millioner år siden
Okres czasu od 143.1 do 100.5 milionów lat temu
Um período de tempo de 143.1 a 100.5 milhões de anos atrás
Временной период от 143.1 до 100.5 миллионов лет назад
Časové obdobie od 143.1 do 100.5 miliónov rokov pred naším letopočtom
143.1 ile 100.5 milyon yıl önce arasındaki zaman dilimi
距今 143.1 至 100.5 百万年前的时期
Lower Cretaceous
spodní devon
Onder Devoon
Alt Devon
Inferior Devonià
Untere Devon
Inferior Devónico
Behe Devoniar
Ala Devoni
Inférieur Dévonien
alsó/kora devon
Lebih rendah Devon
Inferiore Devoniano
下部／前期 デボン系／紀
낮추다 데본기
Žemutinis Devonas
Undre Devon
Dolny Dewon
Inferior Devoniano
Нижний Девонская
spodná devón
Alt Devoniyen
下侏罗统 泥 盆 系
419.62-dən 393.47 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 419.62 a 393.47 milions d'anys enrere
Časové období od 419.62 do 393.47 milionů let před naším letopočtem
Ein Zeitraum von 419.62 bis 393.47 Millionen Jahren
A time period from 419.62 to 393.47 million years ago
Un período de tiempo de 419.62 a 393.47 millones de años atrás
419.62 eta 393.47 milioi urte arteko denbora-tartea
Aikajakso 419.62–393.47 miljoonaa vuotta sitten
Une période de temps de 419.62 à 393.47 millions d'années
Egy 419.62-tól 393.47 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 419.62 hingga 393.47 juta tahun yang lalu
Un periodo di tempo da 419.62 a 393.47 milioni di anni fa
419.62百万年前から393.47百万年前までの時代
419.62백만 년 전부터 393.47백만 년 전까지의 시기
Laikotarpis nuo 419.62 iki 393.47 milijonų metų prieš dabartį
Een tijdperiode van 419.62 tot 393.47 miljoen jaar geleden
Een tijdsperiode van 419.62 tot 393.47 miljoen jaar geleden
En tidsperiode fra 419.62 til 393.47 millioner år siden
Okres czasu od 419.62 do 393.47 milionów lat temu
Um período de tempo de 419.62 a 393.47 milhões de anos atrás
Временной период от 419.62 до 393.47 миллионов лет назад
Časové obdobie od 419.62 do 393.47 miliónov rokov pred naším letopočtom
419.62 ile 393.47 milyon yıl önce arasındaki zaman dilimi
距今 419.62 至 393.47 百万年前的时期
Lower Devonian
spodní jura
Onder Jura
Alt Yura
Inferior Juràssic
Untere Jura
Inferior Jurásico
Behe Jurasiko
Ala Jura
Inférieur Jurassique
alsó/kora jura
Lebih rendah Jura
Inferiore Giurassico
下部／前期 ジュラ系／紀
낮추다 쥐라기
Žemutinis Jura
Undre Jura
Dolny Jura
Inferior Jurássico
Нижний Юрская
spodná jura
Alt Jura
下侏罗统 侏罗 系
201.4-dən 174.7 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 201.4 a 174.7 milions d'anys enrere
Časové období od 201.4 do 174.7 milionů let před naším letopočtem
Ein Zeitraum von 201.4 bis 174.7 Millionen Jahren
A time period from 201.4 to 174.7 million years ago
Un período de tiempo de 201.4 a 174.7 millones de años atrás
201.4 eta 174.7 milioi urte arteko denbora-tartea
Aikajakso 201.4–174.7 miljoonaa vuotta sitten
Une période de temps de 201.4 à 174.7 millions d'années
Egy 201.4-tól 174.7 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 201.4 hingga 174.7 juta tahun yang lalu
Un periodo di tempo da 201.4 a 174.7 milioni di anni fa
201.4百万年前から174.7百万年前までの時代
201.4백만 년 전부터 174.7백만 년 전까지의 시기
Laikotarpis nuo 201.4 iki 174.7 milijonų metų prieš dabartį
Een tijdperiode van 201.4 tot 174.7 miljoen jaar geleden
Een tijdsperiode van 201.4 tot 174.7 miljoen jaar geleden
En tidsperiode fra 201.4 til 174.7 millioner år siden
Okres czasu od 201.4 do 174.7 milionów lat temu
Um período de tempo de 201.4 a 174.7 milhões de anos atrás
Временной период от 201.4 до 174.7 миллионов лет назад
Časové obdobie od 201.4 do 174.7 miliónov rokov pred naším letopočtom
201.4 ile 174.7 milyon yıl önce arasındaki zaman dilimi
距今 201.4 至 174.7 百万年前的时期
Lower Jurassic
Alt Missisipi
Inferior Mississippià
spodní mississipp
Untere Mississippium
Inferior Misisípico
Inferior Misisipiano
Behe Mississippiar
Ala Mississippi
Inférieur Mississippien
alsó/kora mississippi
Lebih rendah Mississippian
Inferiore Mississippiano
下部／前期 ミシシッピアン 亜系／亜紀
낮추다 기 미시시피아기
Žemutinis Misisipas
Onder Mississippien
Onder Mississippiaan
Undre Mississippi
Dolny Missisipi
Inferior Mississíppico
Нижний Мисиссипская
spodná misisip
Alt Misisipiyen
下侏罗统 密 西 西 比 亚 系
Lower Mississippian
spodní ordovik
Onder Ordovicium
spodná ordovik
Alt Ordovik
Inferior Ordovicià
Untere Ordovizium
Inferior Ordovícico
Behe Ordoviziar
Ala Ordoviikki
Inférieur Ordovicien
alsó/kora ordovícium
Lebih rendah Ordovisiu
Inferiore Ordoviciano
下部／前期 オルドビス系／紀
낮추다 오르도비스기
Žemutinis Ordovikas
Undre Ordovicium
Dolny Ordowik
Inferior Ordoviciano
Нижний Ордовикская
Alt Ordovisiyen
下侏罗统 奥 陶 系
486.85-dən 471.3 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 486.85 a 471.3 milions d'anys enrere
Časové období od 486.85 do 471.3 milionů let před naším letopočtem
Ein Zeitraum von 486.85 bis 471.3 Millionen Jahren
A time period from 486.85 to 471.3 million years ago
Un período de tiempo de 486.85 a 471.3 millones de años atrás
486.85 eta 471.3 milioi urte arteko denbora-tartea
Aikajakso 486.85–471.3 miljoonaa vuotta sitten
Une période de temps de 486.85 à 471.3 millions d'années
Egy 486.85-tól 471.3 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 486.85 hingga 471.3 juta tahun yang lalu
Un periodo di tempo da 486.85 a 471.3 milioni di anni fa
486.85百万年前から471.3百万年前までの時代
486.85백만 년 전부터 471.3백만 년 전까지의 시기
Laikotarpis nuo 486.85 iki 471.3 milijonų metų prieš dabartį
Een tijdperiode van 486.85 tot 471.3 miljoen jaar geleden
Een tijdsperiode van 486.85 tot 471.3 miljoen jaar geleden
En tidsperiode fra 486.85 til 471.3 millioner år siden
Okres czasu od 486.85 do 471.3 milionów lat temu
Um período de tempo de 486.85 a 471.3 milhões de anos atrás
Временной период от 486.85 до 471.3 миллионов лет назад
Časové obdobie od 486.85 do 471.3 miliónov rokov pred naším letopočtom
486.85 ile 471.3 milyon yıl önce arasındaki zaman dilimi
距今 486.85 至 471.3 百万年前的时期
Lower Ordovician
Alt Pensilvaniya
Inferior Pennsylvanià
spodní pennsylvan
Untere Pennsylvanium
Inferior Pensilvánico
Inferior Pensilvaniano
Behe Pennsylvaniar
Ala Pennsylvania
Inférieur Pennsylvanie
alsó/kora pennsylvaniai
Lebih rendah Pennsylvanian
Inferiore Pennsylvaniano
下部／前期 ペンシルバニアン 亜系／亜紀
낮추다 펜실베니아아기
Žemutinis Pensilvanas
Onder Pennsylvanien
Onder Pennsylvaniaan
Undre Pennsylvania
Dolny Pensylwan
Inferior Pennsylvánico
Нижний Пенсильванская
spodná pensylván
Alt Pensilvaniyen
下侏罗统 宾 夕 法 尼 亚 亚 系
Lower Pennsylvanian
spodní trias
Onder Trias
spodná trias
Alt Trias
Inferior Triàsic
Untere Trias
Inferior Triásico
Behe Triasiko
Ala Trias
Inférieur Trias
alsó/kora triász
Lebih rendah Trias
Inferiore Triassico
下部／前期 三畳系／紀
낮추다 트라이아스기
Žemutinis Triasas
Undre Trias
Dolny Trias
Inferior Triássico
Нижний Триасовая
Alt Triyas
下侏罗统 三 叠 系
251.902-dən 247.0 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 251.902 a 247.0 milions d'anys enrere
Časové období od 251.902 do 247.0 milionů let před naším letopočtem
Ein Zeitraum von 251.902 bis 247.0 Millionen Jahren
A time period from 251.902 to 247.0 million years ago
Un período de tiempo de 251.902 a 247.0 millones de años atrás
251.902 eta 247.0 milioi urte arteko denbora-tartea
Aikajakso 251.902–247.0 miljoonaa vuotta sitten
Une période de temps de 251.902 à 247.0 millions d'années
Egy 251.902-tól 247.0 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 251.902 hingga 247.0 juta tahun yang lalu
Un periodo di tempo da 251.902 a 247.0 milioni di anni fa
251.902百万年前から247.0百万年前までの時代
251.902백만 년 전부터 247.0백만 년 전까지의 시기
Laikotarpis nuo 251.902 iki 247.0 milijonų metų prieš dabartį
Een tijdperiode van 251.902 tot 247.0 miljoen jaar geleden
Een tijdsperiode van 251.902 tot 247.0 miljoen jaar geleden
En tidsperiode fra 251.902 til 247.0 millioner år siden
Okres czasu od 251.902 do 247.0 milionów lat temu
Um período de tempo de 251.902 a 247.0 milhões de anos atrás
Временной период от 251.902 до 247.0 миллионов лет назад
Časové obdobie od 251.902 do 247.0 miliónov rokov pred naším letopočtom
251.902 ile 247.0 milyon yıl önce arasındaki zaman dilimi
距今 251.902 至 247.0 百万年前的时期
Lower Triassic
Ludlow
ludlowi
Ludlovis
Ludlov
Ludlowià
ludlow
Ludloviano
ラドロー
러들로세
Лудловский
ludlov
罗德洛统
426.7-dən 419.62 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 426.7 a 419.62 milions d'anys enrere
Časové období od 426.7 do 419.62 milionů let před naším letopočtem
Ein Zeitraum von 426.7 bis 419.62 Millionen Jahren
A time period from 426.7 to 419.62 million years ago
Un período de tiempo de 426.7 a 419.62 millones de años atrás
426.7 eta 419.62 milioi urte arteko denbora-tartea
Aikajakso 426.7–419.62 miljoonaa vuotta sitten
Une période de temps de 426.7 à 419.62 millions d'années
Egy 426.7-tól 419.62 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 426.7 hingga 419.62 juta tahun yang lalu
Un periodo di tempo da 426.7 a 419.62 milioni di anni fa
426.7百万年前から419.62百万年前までの時代
426.7백만 년 전부터 419.62백만 년 전까지의 시기
Laikotarpis nuo 426.7 iki 419.62 milijonų metų prieš dabartį
Een tijdperiode van 426.7 tot 419.62 miljoen jaar geleden
Een tijdsperiode van 426.7 tot 419.62 miljoen jaar geleden
En tidsperiode fra 426.7 til 419.62 millioner år siden
Okres czasu od 426.7 do 419.62 milionów lat temu
Um período de tempo de 426.7 a 419.62 milhões de anos atrás
Временной период от 426.7 до 419.62 миллионов лет назад
Časové obdobie od 426.7 do 419.62 miliónov rokov pred naším letopočtom
426.7 ile 419.62 milyon yıl önce arasındaki zaman dilimi
距今 426.7 至 419.62 百万年前的时期
Miaolinq
Miaolingià
miaoling
Serie 3
Miaolingiense
Miaolingiano
3 Serie
Miaoling
Miaolingien
miaolingi
Miaolingian
ミャオリンギアン
미아오링세
Miaolingis
Miaolingiaan
Отдел 3
Miaolingiyen
苗岭统
506.5-dən 497.0 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 506.5 a 497.0 milions d'anys enrere
Časové období od 506.5 do 497.0 milionů let před naším letopočtem
Ein Zeitraum von 506.5 bis 497.0 Millionen Jahren
A time period from 506.5 to 497.0 million years ago
Un período de tiempo de 506.5 a 497.0 millones de años atrás
506.5 eta 497.0 milioi urte arteko denbora-tartea
Aikajakso 506.5–497.0 miljoonaa vuotta sitten
Une période de temps de 506.5 à 497.0 millions d'années
Egy 506.5-tól 497.0 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 506.5 hingga 497.0 juta tahun yang lalu
Un periodo di tempo da 506.5 a 497.0 milioni di anni fa
506.5百万年前から497.0百万年前までの時代
506.5백만 년 전부터 497.0백만 년 전까지의 시기
Laikotarpis nuo 506.5 iki 497.0 milijonų metų prieš dabartį
Een tijdperiode van 506.5 tot 497.0 miljoen jaar geleden
Een tijdsperiode van 506.5 tot 497.0 miljoen jaar geleden
En tidsperiode fra 506.5 til 497.0 millioner år siden
Okres czasu od 506.5 do 497.0 milionów lat temu
Um período de tempo de 506.5 a 497.0 milhões de anos atrás
Временной период от 506.5 до 497.0 миллионов лет назад
Časové obdobie od 506.5 do 497.0 miliónov rokov pred naším letopočtom
506.5 ile 497.0 milyon yıl önce arasındaki zaman dilimi
距今 506.5 至 497.0 百万年前的时期
Midden Devoon
Środkowy Dewon
Orta Devon
Mitjà Devonià
střední devon
Mitte Devon
Medio Devónico
Erdi Devoniar
Keski Devoni
Moyen Dévonien
középső devon
Tengah Devon
Medio Devoniano
中部／中期 デボン系／紀
가운데 데본기
Vidurys Devonas
Midtre Devon
Médio Devoniano
Средний Девонская
stredná devón
Orta Devoniyen
中侏罗统 泥 盆 系
393.47-dən 382.31 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 393.47 a 382.31 milions d'anys enrere
Časové období od 393.47 do 382.31 milionů let před naším letopočtem
Ein Zeitraum von 393.47 bis 382.31 Millionen Jahren
A time period from 393.47 to 382.31 million years ago
Un período de tiempo de 393.47 a 382.31 millones de años atrás
393.47 eta 382.31 milioi urte arteko denbora-tartea
Aikajakso 393.47–382.31 miljoonaa vuotta sitten
Une période de temps de 393.47 à 382.31 millions d'années
Egy 393.47-tól 382.31 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 393.47 hingga 382.31 juta tahun yang lalu
Un periodo di tempo da 393.47 a 382.31 milioni di anni fa
393.47百万年前から382.31百万年前までの時代
393.47백만 년 전부터 382.31백만 년 전까지의 시기
Laikotarpis nuo 393.47 iki 382.31 milijonų metų prieš dabartį
Een tijdperiode van 393.47 tot 382.31 miljoen jaar geleden
Een tijdsperiode van 393.47 tot 382.31 miljoen jaar geleden
En tidsperiode fra 393.47 til 382.31 millioner år siden
Okres czasu od 393.47 do 382.31 milionów lat temu
Um período de tempo de 393.47 a 382.31 milhões de anos atrás
Временной период от 393.47 до 382.31 миллионов лет назад
Časové obdobie od 393.47 do 382.31 miliónov rokov pred naším letopočtom
393.47 ile 382.31 milyon yıl önce arasındaki zaman dilimi
距今 393.47 至 382.31 百万年前的时期
Middle Devonian
Midden Jura
stredná jura
Orta Yura
Mitjà Juràssic
střední jura
Mitte Jura
Medio Jurásico
Erdi Jurasiko
Keski Jura
Moyen Jurassique
középső jura
Tengah Jura
Medio Giurassico
中部／中期 ジュラ系／紀
가운데 쥐라기
Vidurys Jura
Midtre Jura
Środkowy Jura
Médio Jurássico
Средний Юрская
Orta Jura
中侏罗统 侏罗 系
174.7-dən 161.5 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 174.7 a 161.5 milions d'anys enrere
Časové období od 174.7 do 161.5 milionů let před naším letopočtem
Ein Zeitraum von 174.7 bis 161.5 Millionen Jahren
A time period from 174.7 to 161.5 million years ago
Un período de tiempo de 174.7 a 161.5 millones de años atrás
174.7 eta 161.5 milioi urte arteko denbora-tartea
Aikajakso 174.7–161.5 miljoonaa vuotta sitten
Une période de temps de 174.7 à 161.5 millions d'années
Egy 174.7-tól 161.5 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 174.7 hingga 161.5 juta tahun yang lalu
Un periodo di tempo da 174.7 a 161.5 milioni di anni fa
174.7百万年前から161.5百万年前までの時代
174.7백만 년 전부터 161.5백만 년 전까지의 시기
Laikotarpis nuo 174.7 iki 161.5 milijonų metų prieš dabartį
Een tijdperiode van 174.7 tot 161.5 miljoen jaar geleden
Een tijdsperiode van 174.7 tot 161.5 miljoen jaar geleden
En tidsperiode fra 174.7 til 161.5 millioner år siden
Okres czasu od 174.7 do 161.5 milionów lat temu
Um período de tempo de 174.7 a 161.5 milhões de anos atrás
Временной период от 174.7 до 161.5 миллионов лет назад
Časové obdobie od 174.7 do 161.5 miliónov rokov pred naším letopočtom
174.7 ile 161.5 milyon yıl önce arasındaki zaman dilimi
距今 174.7 至 161.5 百万年前的时期
Middle Jurassic
Orta Missisipi
Mitjà Mississippià
střední mississipp
Mitte Mississippium
Medio Misisípico
Medio Misisipiano
Erdi Mississippiar
Keski Mississippi
Moyen Mississippien
középső mississippi
Tengah Mississippian
Medio Mississippiano
中部／中期 ミシシッピアン 亜系／亜紀
가운데 기 미시시피아기
Vidurys Misisipas
Midden Mississippien
Midden Mississippiaan
Midtre Mississippi
Środkowy Missisipi
Médio Mississíppico
Средний Мисиссипская
stredná misisip
Orta Misisipiyen
中侏罗统 密 西 西 比 亚 系
Middle Mississippian
Midden Ordovicium
Środkowy Ordowik
Orta Ordovik
Mitjà Ordovicià
střední ordovik
Mitte Ordovizium
Medio Ordovícico
Erdi Ordoviziar
Keski Ordoviikki
Moyen Ordovicien
középső ordovícium
Tengah Ordovisiu
Medio Ordoviciano
中部／中期 オルドビス系／紀
가운데 오르도비스기
Vidurys Ordovikas
Midtre Ordovicium
Médio Ordoviciano
Средний Ордовикская
stredná ordovik
Orta Ordovisiyen
中侏罗统 奥 陶 系
471.3-dən 458.2 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 471.3 a 458.2 milions d'anys enrere
Časové období od 471.3 do 458.2 milionů let před naším letopočtem
Ein Zeitraum von 471.3 bis 458.2 Millionen Jahren
A time period from 471.3 to 458.2 million years ago
Un período de tiempo de 471.3 a 458.2 millones de años atrás
471.3 eta 458.2 milioi urte arteko denbora-tartea
Aikajakso 471.3–458.2 miljoonaa vuotta sitten
Une période de temps de 471.3 à 458.2 millions d'années
Egy 471.3-tól 458.2 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 471.3 hingga 458.2 juta tahun yang lalu
Un periodo di tempo da 471.3 a 458.2 milioni di anni fa
471.3百万年前から458.2百万年前までの時代
471.3백만 년 전부터 458.2백만 년 전까지의 시기
Laikotarpis nuo 471.3 iki 458.2 milijonų metų prieš dabartį
Een tijdperiode van 471.3 tot 458.2 miljoen jaar geleden
Een tijdsperiode van 471.3 tot 458.2 miljoen jaar geleden
En tidsperiode fra 471.3 til 458.2 millioner år siden
Okres czasu od 471.3 do 458.2 milionów lat temu
Um período de tempo de 471.3 a 458.2 milhões de anos atrás
Временной период от 471.3 до 458.2 миллионов лет назад
Časové obdobie od 471.3 do 458.2 miliónov rokov pred naším letopočtom
471.3 ile 458.2 milyon yıl önce arasındaki zaman dilimi
距今 471.3 至 458.2 百万年前的时期
Middle Ordovician
Orta Pensilvaniya
Mitjà Pennsylvanià
střední pennsylvan
Mitte Pennsylvanium
Medio Pensilvánico
Medio Pensilvaniano
Erdi Pennsylvaniar
Keski Pennsylvania
Moyen Pennsylvanie
középső pennsylvaniai
Tengah Pennsylvanian
Medio Pennsylvaniano
中部／中期 ペンシルバニアン 亜系／亜紀
가운데 펜실베니아아기
Vidurys Pensilvanas
Midden Pennsylvanien
Midden Pennsylvaniaan
Midtre Pennsylvania
Środkowy Pensylwan
Médio Pennsylvánico
Средний Пенсильванская
stredná pensylván
Orta Pensilvaniyen
中侏罗统 宾 夕 法 尼 亚 亚 系
Middle Pennsylvanian
Midden Trias
Środkowy Trias
Orta Trias
Mitjà Triàsic
střední trias
Mitte Trias
Medio Triásico
Erdi Triasiko
Keski Trias
Moyen Trias
középső triász
Tengah Trias
Medio Triassico
中部／中期 三畳系／紀
가운데 트라이아스기
Vidurys Triasas
Midtre Trias
Médio Triássico
Средний Триасовая
stredná trias
Orta Triyas
中侏罗统 三 叠 系
247.0-dən 237 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 247.0 a 237 milions d'anys enrere
Časové období od 247.0 do 237 milionů let před naším letopočtem
Ein Zeitraum von 247.0 bis 237 Millionen Jahren
A time period from 247.0 to 237 million years ago
Un período de tiempo de 247.0 a 237 millones de años atrás
247.0 eta 237 milioi urte arteko denbora-tartea
Aikajakso 247.0–237 miljoonaa vuotta sitten
Une période de temps de 247.0 à 237 millions d'années
Egy 247.0-tól 237 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 247.0 hingga 237 juta tahun yang lalu
Un periodo di tempo da 247.0 a 237 milioni di anni fa
247.0百万年前から237百万年前までの時代
247.0백만 년 전부터 237백만 년 전까지의 시기
Laikotarpis nuo 247.0 iki 237 milijonų metų prieš dabartį
Een tijdperiode van 247.0 tot 237 miljoen jaar geleden
Een tijdsperiode van 247.0 tot 237 miljoen jaar geleden
En tidsperiode fra 247.0 til 237 millioner år siden
Okres czasu od 247.0 do 237 milionów lat temu
Um período de tempo de 247.0 a 237 milhões de anos atrás
Временной период от 247.0 до 237 миллионов лет назад
Časové obdobie od 247.0 do 237 miliónov rokov pred naším letopočtom
247.0 ile 237 milyon yıl önce arasındaki zaman dilimi
距今 247.0 至 237 百万年前的时期
Middle Triassic
Miozän
Mioceno
Mioseeni
Miocène
miocén
Miocenas
Mioceen
Miocen
Miosen
Miocè
Miozeno
Miocene
中新統／世
마이오세
Миоцен
Miyosen
中新统
23.04-dən 5.333 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 23.04 a 5.333 milions d'anys enrere
Časové období od 23.04 do 5.333 milionů let před naším letopočtem
Ein Zeitraum von 23.04 bis 5.333 Millionen Jahren
A time period from 23.04 to 5.333 million years ago
Un período de tiempo de 23.04 a 5.333 millones de años atrás
23.04 eta 5.333 milioi urte arteko denbora-tartea
Aikajakso 23.04–5.333 miljoonaa vuotta sitten
Une période de temps de 23.04 à 5.333 millions d'années
Egy 23.04-tól 5.333 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 23.04 hingga 5.333 juta tahun yang lalu
Un periodo di tempo da 23.04 a 5.333 milioni di anni fa
23.04百万年前から5.333百万年前までの時代
23.04백만 년 전부터 5.333백만 년 전까지의 시기
Laikotarpis nuo 23.04 iki 5.333 milijonų metų prieš dabartį
Een tijdperiode van 23.04 tot 5.333 miljoen jaar geleden
Een tijdsperiode van 23.04 tot 5.333 miljoen jaar geleden
En tidsperiode fra 23.04 til 5.333 millioner år siden
Okres czasu od 23.04 do 5.333 milionów lat temu
Um período de tempo de 23.04 a 5.333 milhões de anos atrás
Временной период от 23.04 до 5.333 миллионов лет назад
Časové obdobie od 23.04 do 5.333 miliónov rokov pred naším letopočtom
23.04 ile 5.333 milyon yıl önce arasındaki zaman dilimi
距今 23.04 至 5.333 百万年前的时期
Oligozän
Oligoceno
Oligoseeni
Oligocène
oligocén
Oligocenas
Oligocen
Oliqosen
Oligocè
Oligozeno
Oligosen
Oligocene
漸新統／世
올리고세
Oligoceen
Олигоцен
渐新统
33.9-dən 23.04 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 33.9 a 23.04 milions d'anys enrere
Časové období od 33.9 do 23.04 milionů let před naším letopočtem
Ein Zeitraum von 33.9 bis 23.04 Millionen Jahren
A time period from 33.9 to 23.04 million years ago
Un período de tiempo de 33.9 a 23.04 millones de años atrás
33.9 eta 23.04 milioi urte arteko denbora-tartea
Aikajakso 33.9–23.04 miljoonaa vuotta sitten
Une période de temps de 33.9 à 23.04 millions d'années
Egy 33.9-tól 23.04 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 33.9 hingga 23.04 juta tahun yang lalu
Un periodo di tempo da 33.9 a 23.04 milioni di anni fa
33.9百万年前から23.04百万年前までの時代
33.9백만 년 전부터 23.04백만 년 전까지의 시기
Laikotarpis nuo 33.9 iki 23.04 milijonų metų prieš dabartį
Een tijdperiode van 33.9 tot 23.04 miljoen jaar geleden
Een tijdsperiode van 33.9 tot 23.04 miljoen jaar geleden
En tidsperiode fra 33.9 til 23.04 millioner år siden
Okres czasu od 33.9 do 23.04 milionów lat temu
Um período de tempo de 33.9 a 23.04 milhões de anos atrás
Временной период от 33.9 до 23.04 миллионов лет назад
Časové obdobie od 33.9 do 23.04 miliónov rokov pred naším letopočtom
33.9 ile 23.04 milyon yıl önce arasındaki zaman dilimi
距今 33.9 至 23.04 百万年前的时期
Paläozän
Paleoceno
Paleoseeni
Paléocène
paleocén
Paleocenas
Paleoceen
Paleocen
Paleosen
Paleocè
Paleozeno
Paleocene
暁新統／世
팔레오세
Палео- цен
古新统
66.00-dən 56.00 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 66.00 a 56.00 milions d'anys enrere
Časové období od 66.00 do 56.00 milionů let před naším letopočtem
Ein Zeitraum von 66.00 bis 56.00 Millionen Jahren
A time period from 66.00 to 56.00 million years ago
Un período de tiempo de 66.00 a 56.00 millones de años atrás
66.00 eta 56.00 milioi urte arteko denbora-tartea
Aikajakso 66.00–56.00 miljoonaa vuotta sitten
Une période de temps de 66.00 à 56.00 millions d'années
Egy 66.00-tól 56.00 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 66.00 hingga 56.00 juta tahun yang lalu
Un periodo di tempo da 66.00 a 56.00 milioni di anni fa
66.00百万年前から56.00百万年前までの時代
66.00백만 년 전부터 56.00백만 년 전까지의 시기
Laikotarpis nuo 66.00 iki 56.00 milijonų metų prieš dabartį
Een tijdperiode van 66.00 tot 56.00 miljoen jaar geleden
Een tijdsperiode van 66.00 tot 56.00 miljoen jaar geleden
En tidsperiode fra 66.00 til 56.00 millioner år siden
Okres czasu od 66.00 do 56.00 milionów lat temu
Um período de tempo de 66.00 a 56.00 milhões de anos atrás
Временной период от 66.00 до 56.00 миллионов лет назад
Časové obdobie od 66.00 do 56.00 miliónov rokov pred naším letopočtom
66.00 ile 56.00 milyon yıl önce arasındaki zaman dilimi
距今 66.00 至 56.00 百万年前的时期
Pleistozän
Pleistoseeni
Pléistocène
pleisztocén
Pleistocenas
Pleistoceen
Pleistocen
Plejstocen
pleistocén
Pleystosen
Plistocè
Pleistocene
Pleistoceno
Pleistozeno
Pleistosen
更新統／世
플라이스토세
Плейстоцен
Pleyistosen
更新统
2.58-dən 0.0117 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 2.58 a 0.0117 milions d'anys enrere
Časové období od 2.58 do 0.0117 milionů let před naším letopočtem
Ein Zeitraum von 2.58 bis 0.0117 Millionen Jahren
A time period from 2.58 to 0.0117 million years ago
Un período de tiempo de 2.58 a 0.0117 millones de años atrás
2.58 eta 0.0117 milioi urte arteko denbora-tartea
Aikajakso 2.58–0.0117 miljoonaa vuotta sitten
Une période de temps de 2.58 à 0.0117 millions d'années
Egy 2.58-tól 0.0117 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 2.58 hingga 0.0117 juta tahun yang lalu
Un periodo di tempo da 2.58 a 0.0117 milioni di anni fa
2.58百万年前から0.0117百万年前までの時代
2.58백만 년 전부터 0.0117백만 년 전까지의 시기
Laikotarpis nuo 2.58 iki 0.0117 milijonų metų prieš dabartį
Een tijdperiode van 2.58 tot 0.0117 miljoen jaar geleden
Een tijdsperiode van 2.58 tot 0.0117 miljoen jaar geleden
En tidsperiode fra 2.58 til 0.0117 millioner år siden
Okres czasu od 2.58 do 0.0117 milionów lat temu
Um período de tempo de 2.58 a 0.0117 milhões de anos atrás
Временной период от 2.58 до 0.0117 миллионов лет назад
Časové obdobie od 2.58 do 0.0117 miliónov rokov pred naším letopočtom
2.58 ile 0.0117 milyon yıl önce arasındaki zaman dilimi
距今 2.58 至 0.0117 百万年前的时期
Pliozän
Plioseeni
Pliocène
pliocén
Pliocenas
Plioceen
Pliocen
Pliosen
Pliocè
Plioceno
Pliozeno
Pliocene
鮮新統／世
플라이오세
Плиоцен
Pliyosen
上新统
5.333-dən 2.58 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 5.333 a 2.58 milions d'anys enrere
Časové období od 5.333 do 2.58 milionů let před naším letopočtem
Ein Zeitraum von 5.333 bis 2.58 Millionen Jahren
A time period from 5.333 to 2.58 million years ago
Un período de tiempo de 5.333 a 2.58 millones de años atrás
5.333 eta 2.58 milioi urte arteko denbora-tartea
Aikajakso 5.333–2.58 miljoonaa vuotta sitten
Une période de temps de 5.333 à 2.58 millions d'années
Egy 5.333-tól 2.58 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 5.333 hingga 2.58 juta tahun yang lalu
Un periodo di tempo da 5.333 a 2.58 milioni di anni fa
5.333百万年前から2.58百万年前までの時代
5.333백만 년 전부터 2.58백만 년 전까지의 시기
Laikotarpis nuo 5.333 iki 2.58 milijonų metų prieš dabartį
Een tijdperiode van 5.333 tot 2.58 miljoen jaar geleden
Een tijdsperiode van 5.333 tot 2.58 miljoen jaar geleden
En tidsperiode fra 5.333 til 2.58 millioner år siden
Okres czasu od 5.333 do 2.58 milionów lat temu
Um período de tempo de 5.333 a 2.58 milhões de anos atrás
Временной период от 5.333 до 2.58 миллионов лет назад
Časové obdobie od 5.333 do 2.58 miliónov rokov pred naším letopočtom
5.333 ile 2.58 milyon yıl önce arasındaki zaman dilimi
距今 5.333 至 2.58 百万年前的时期
Terreneuvium
Terreneuviense
Terreneuvien
terreneuvi
Terreneuviano
Terrenev
Terranovià
terreneuv
Terreneuviar
Terreneuve
Terreneuvian
テレニュービアン
테레누브세
Tereneuvis
Terreneuviaan
Terreneuv
Terreneuwiański
Терреновский
ternév
Terrenöviyen
纽芬兰统
538.8-dən 521.0 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 538.8 a 521.0 milions d'anys enrere
Časové období od 538.8 do 521.0 milionů let před naším letopočtem
Ein Zeitraum von 538.8 bis 521.0 Millionen Jahren
A time period from 538.8 to 521.0 million years ago
Un período de tiempo de 538.8 a 521.0 millones de años atrás
538.8 eta 521.0 milioi urte arteko denbora-tartea
Aikajakso 538.8–521.0 miljoonaa vuotta sitten
Une période de temps de 538.8 à 521.0 millions d'années
Egy 538.8-tól 521.0 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 538.8 hingga 521.0 juta tahun yang lalu
Un periodo di tempo da 538.8 a 521.0 milioni di anni fa
538.8百万年前から521.0百万年前までの時代
538.8백만 년 전부터 521.0백만 년 전까지의 시기
Laikotarpis nuo 538.8 iki 521.0 milijonų metų prieš dabartį
Een tijdperiode van 538.8 tot 521.0 miljoen jaar geleden
Een tijdsperiode van 538.8 tot 521.0 miljoen jaar geleden
En tidsperiode fra 538.8 til 521.0 millioner år siden
Okres czasu od 538.8 do 521.0 milionów lat temu
Um período de tempo de 538.8 a 521.0 milhões de anos atrás
Временной период от 538.8 до 521.0 миллионов лет назад
Časové obdobie od 538.8 do 521.0 miliónov rokov pred naším letopočtom
538.8 ile 521.0 milyon yıl önce arasındaki zaman dilimi
距今 538.8 至 521.0 百万年前的时期
Üst Təbaşir
Superior Cretaci
svrchní křída
Obere Kreide
Superior Cretácico
Goi Kretazeo
Ylä Liitu
Supérieur Crétacé
felső/késő kréta
Atas Kapur
Superiore Cretacico
上部／後期 白亜系／紀
높은 백악기
Viršutinė Kreida
Boven Krijt
Øvre Kritt
Górny Kreda
Superior Cretáceo
Верхний Меловая
vrchná krieda
Üst Kretase
上侏罗统 白 垩系
100.5-dən 66.00 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 100.5 a 66.00 milions d'anys enrere
Časové období od 100.5 do 66.00 milionů let před naším letopočtem
Ein Zeitraum von 100.5 bis 66.00 Millionen Jahren
A time period from 100.5 to 66.00 million years ago
Un período de tiempo de 100.5 a 66.00 millones de años atrás
100.5 eta 66.00 milioi urte arteko denbora-tartea
Aikajakso 100.5–66.00 miljoonaa vuotta sitten
Une période de temps de 100.5 à 66.00 millions d'années
Egy 100.5-tól 66.00 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 100.5 hingga 66.00 juta tahun yang lalu
Un periodo di tempo da 100.5 a 66.00 milioni di anni fa
100.5百万年前から66.00百万年前までの時代
100.5백만 년 전부터 66.00백만 년 전까지의 시기
Laikotarpis nuo 100.5 iki 66.00 milijonų metų prieš dabartį
Een tijdperiode van 100.5 tot 66.00 miljoen jaar geleden
Een tijdsperiode van 100.5 tot 66.00 miljoen jaar geleden
En tidsperiode fra 100.5 til 66.00 millioner år siden
Okres czasu od 100.5 do 66.00 milionów lat temu
Um período de tempo de 100.5 a 66.00 milhões de anos atrás
Временной период от 100.5 до 66.00 миллионов лет назад
Časové obdobie od 100.5 do 66.00 miliónov rokov pred naším letopočtom
100.5 ile 66.00 milyon yıl önce arasındaki zaman dilimi
距今 100.5 至 66.00 百万年前的时期
Upper Cretaceous
Üst Devon
Superior Devonià
svrchní devon
Obere Devon
Superior Devónico
Goi Devoniar
Ylä Devoni
Supérieur Dévonien
felső/késő devon
Atas Devon
Superiore Devoniano
上部／後期 デボン系／紀
높은 데본기
Viršutinė Devonas
Boven Devoon
Øvre Devon
Górny Dewon
Superior Devoniano
Верхний Девонская
vrchná devón
Üst Devoniyen
上侏罗统 泥 盆 系
382.31-dən 358.86 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 382.31 a 358.86 milions d'anys enrere
Časové období od 382.31 do 358.86 milionů let před naším letopočtem
Ein Zeitraum von 382.31 bis 358.86 Millionen Jahren
A time period from 382.31 to 358.86 million years ago
Un período de tiempo de 382.31 a 358.86 millones de años atrás
382.31 eta 358.86 milioi urte arteko denbora-tartea
Aikajakso 382.31–358.86 miljoonaa vuotta sitten
Une période de temps de 382.31 à 358.86 millions d'années
Egy 382.31-tól 358.86 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 382.31 hingga 358.86 juta tahun yang lalu
Un periodo di tempo da 382.31 a 358.86 milioni di anni fa
382.31百万年前から358.86百万年前までの時代
382.31백만 년 전부터 358.86백만 년 전까지의 시기
Laikotarpis nuo 382.31 iki 358.86 milijonų metų prieš dabartį
Een tijdperiode van 382.31 tot 358.86 miljoen jaar geleden
Een tijdsperiode van 382.31 tot 358.86 miljoen jaar geleden
En tidsperiode fra 382.31 til 358.86 millioner år siden
Okres czasu od 382.31 do 358.86 milionów lat temu
Um período de tempo de 382.31 a 358.86 milhões de anos atrás
Временной период от 382.31 до 358.86 миллионов лет назад
Časové obdobie od 382.31 do 358.86 miliónov rokov pred naším letopočtom
382.31 ile 358.86 milyon yıl önce arasındaki zaman dilimi
距今 382.31 至 358.86 百万年前的时期
Upper Devonian
Üst Yura
Superior Juràssic
svrchní jura
Obere Jura
Superior Jurásico
Goi Jurasiko
Ylä Jura
Supérieur Jurassique
felső/késő jura
Atas Jura
Superiore Giurassico
上部／後期 ジュラ系／紀
높은 쥐라기
Viršutinė Jura
Boven Jura
Øvre Jura
Górny Jura
Superior Jurássico
Верхний Юрская
vrchná jura
Üst Jura
上侏罗统 侏罗 系
161.5-dən 143.1 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 161.5 a 143.1 milions d'anys enrere
Časové období od 161.5 do 143.1 milionů let před naším letopočtem
Ein Zeitraum von 161.5 bis 143.1 Millionen Jahren
A time period from 161.5 to 143.1 million years ago
Un período de tiempo de 161.5 a 143.1 millones de años atrás
161.5 eta 143.1 milioi urte arteko denbora-tartea
Aikajakso 161.5–143.1 miljoonaa vuotta sitten
Une période de temps de 161.5 à 143.1 millions d'années
Egy 161.5-tól 143.1 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 161.5 hingga 143.1 juta tahun yang lalu
Un periodo di tempo da 161.5 a 143.1 milioni di anni fa
161.5百万年前から143.1百万年前までの時代
161.5백만 년 전부터 143.1백만 년 전까지의 시기
Laikotarpis nuo 161.5 iki 143.1 milijonų metų prieš dabartį
Een tijdperiode van 161.5 tot 143.1 miljoen jaar geleden
Een tijdsperiode van 161.5 tot 143.1 miljoen jaar geleden
En tidsperiode fra 161.5 til 143.1 millioner år siden
Okres czasu od 161.5 do 143.1 milionów lat temu
Um período de tempo de 161.5 a 143.1 milhões de anos atrás
Временной период от 161.5 до 143.1 миллионов лет назад
Časové obdobie od 161.5 do 143.1 miliónov rokov pred naším letopočtom
161.5 ile 143.1 milyon yıl önce arasındaki zaman dilimi
距今 161.5 至 143.1 百万年前的时期
Upper Jurassic
Üst Missisipi
Superior Mississippià
svrchní mississipp
Obere Mississippium
Superior Misisípico
Superior Misisipiano
Goi Mississippiar
Ylä Mississippi
Supérieur Mississippien
felső/késő mississippi
Atas Mississippian
Superiore Mississippiano
上部／後期 ミシシッピアン 亜系／亜紀
높은 기 미시시피아기
Viršutinė Misisipas
Boven Mississippien
Boven Mississippiaan
Øvre Mississippi
Górny Missisipi
Superior Mississíppico
Верхний Мисиссипская
vrchná misisip
Üst Misisipiyen
上侏罗统 密 西 西 比 亚 系
Upper Mississippian
Üst Ordovik
Superior Ordovicià
svrchní ordovik
Obere Ordovizium
Superior Ordovícico
Goi Ordoviziar
Ylä Ordoviikki
Supérieur Ordovicien
felső/késő ordovícium
Atas Ordovisiu
Superiore Ordoviciano
上部／後期 オルドビス系／紀
높은 오르도비스기
Viršutinė Ordovikas
Boven Ordovicium
Øvre Ordovicium
Górny Ordowik
Superior Ordoviciano
Верхний Ордовикская
vrchná ordovik
Üst Ordovisiyen
上侏罗统 奥 陶 系
458.2-dən 443.1 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 458.2 a 443.1 milions d'anys enrere
Časové období od 458.2 do 443.1 milionů let před naším letopočtem
Ein Zeitraum von 458.2 bis 443.1 Millionen Jahren
A time period from 458.2 to 443.1 million years ago
Un período de tiempo de 458.2 a 443.1 millones de años atrás
458.2 eta 443.1 milioi urte arteko denbora-tartea
Aikajakso 458.2–443.1 miljoonaa vuotta sitten
Une période de temps de 458.2 à 443.1 millions d'années
Egy 458.2-tól 443.1 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 458.2 hingga 443.1 juta tahun yang lalu
Un periodo di tempo da 458.2 a 443.1 milioni di anni fa
458.2百万年前から443.1百万年前までの時代
458.2백만 년 전부터 443.1백만 년 전까지의 시기
Laikotarpis nuo 458.2 iki 443.1 milijonų metų prieš dabartį
Een tijdperiode van 458.2 tot 443.1 miljoen jaar geleden
Een tijdsperiode van 458.2 tot 443.1 miljoen jaar geleden
En tidsperiode fra 458.2 til 443.1 millioner år siden
Okres czasu od 458.2 do 443.1 milionów lat temu
Um período de tempo de 458.2 a 443.1 milhões de anos atrás
Временной период от 458.2 до 443.1 миллионов лет назад
Časové obdobie od 458.2 do 443.1 miliónov rokov pred naším letopočtom
458.2 ile 443.1 milyon yıl önce arasındaki zaman dilimi
距今 458.2 至 443.1 百万年前的时期
Upper Ordovician
Üst Pensilvaniya
Superior Pennsylvanià
svrchní pennsylvan
Obere Pennsylvanium
Superior Pensilvánico
Superior Pensilvaniano
Goi Pennsylvaniar
Ylä Pennsylvania
Supérieur Pennsylvanie
felső/késő pennsylvaniai
Atas Pennsylvanian
Superiore Pennsylvaniano
上部／後期 ペンシルバニアン 亜系／亜紀
높은 펜실베니아아기
Viršutinė Pensilvanas
Boven Pennsylvanien
Boven Pennsylvaniaan
Øvre Pennsylvania
Górny Pensylwan
Superior Pennsylvánico
Верхний Пенсильванская
vrchná pensylván
Üst Pensilvaniyen
上侏罗统 宾 夕 法 尼 亚 亚 系
307.0-dən 298.9 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 307.0 a 298.9 milions d'anys enrere
Časové období od 307.0 do 298.9 milionů let před naším letopočtem
Ein Zeitraum von 307.0 bis 298.9 Millionen Jahren
A time period from 307.0 to 298.9 million years ago
Un período de tiempo de 307.0 a 298.9 millones de años atrás
307.0 eta 298.9 milioi urte arteko denbora-tartea
Aikajakso 307.0–298.9 miljoonaa vuotta sitten
Une période de temps de 307.0 à 298.9 millions d'années
Egy 307.0-tól 298.9 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 307.0 hingga 298.9 juta tahun yang lalu
Un periodo di tempo da 307.0 a 298.9 milioni di anni fa
307.0百万年前から298.9百万年前までの時代
307.0백만 년 전부터 298.9백만 년 전까지의 시기
Laikotarpis nuo 307.0 iki 298.9 milijonų metų prieš dabartį
Een tijdperiode van 307.0 tot 298.9 miljoen jaar geleden
Een tijdsperiode van 307.0 tot 298.9 miljoen jaar geleden
En tidsperiode fra 307.0 til 298.9 millioner år siden
Okres czasu od 307.0 do 298.9 milionów lat temu
Um período de tempo de 307.0 a 298.9 milhões de anos atrás
Временной период от 307.0 до 298.9 миллионов лет назад
Časové obdobie od 307.0 do 298.9 miliónov rokov pred naším letopočtom
307.0 ile 298.9 milyon yıl önce arasındaki zaman dilimi
距今 307.0 至 298.9 百万年前的时期
Upper Pennsylvanian
Üst Trias
Superior Triàsic
svrchní trias
Obere Trias
Superior Triásico
Goi Triasiko
Ylä Trias
Supérieur Trias
felső/késő triász
Atas Trias
Superiore Triassico
上部／後期 三畳系／紀
높은 트라이아스기
Viršutinė Triasas
Boven Trias
Øvre Trias
Górny Trias
Superior Triássico
Верхний Триасовая
vrchná trias
Üst Triyas
上侏罗统 三 叠 系
237-dən 201.4 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 237 a 201.4 milions d'anys enrere
Časové období od 237 do 201.4 milionů let před naším letopočtem
Ein Zeitraum von 237 bis 201.4 Millionen Jahren
A time period from 237 to 201.4 million years ago
Un período de tiempo de 237 a 201.4 millones de años atrás
237 eta 201.4 milioi urte arteko denbora-tartea
Aikajakso 237–201.4 miljoonaa vuotta sitten
Une période de temps de 237 à 201.4 millions d'années
Egy 237-tól 201.4 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 237 hingga 201.4 juta tahun yang lalu
Un periodo di tempo da 237 a 201.4 milioni di anni fa
237百万年前から201.4百万年前までの時代
237백만 년 전부터 201.4백만 년 전까지의 시기
Laikotarpis nuo 237 iki 201.4 milijonų metų prieš dabartį
Een tijdperiode van 237 tot 201.4 miljoen jaar geleden
Een tijdsperiode van 237 tot 201.4 miljoen jaar geleden
En tidsperiode fra 237 til 201.4 millioner år siden
Okres czasu od 237 do 201.4 milionów lat temu
Um período de tempo de 237 a 201.4 milhões de anos atrás
Временной период от 237 до 201.4 миллионов лет назад
Časové obdobie od 237 do 201.4 miliónov rokov pred naším letopočtom
237 ile 201.4 milyon yıl önce arasındaki zaman dilimi
距今 237 至 201.4 百万年前的时期
Upper Triassic
Wenlock
wenlocki
Uenlokis
Venlok
Wenlockià
wenlock
Wenlockiano
ウェンロック
웬록세
Венлокский
venlok
温洛克统
432.9-dən 426.7 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 432.9 a 426.7 milions d'anys enrere
Časové období od 432.9 do 426.7 milionů let před naším letopočtem
Ein Zeitraum von 432.9 bis 426.7 Millionen Jahren
A time period from 432.9 to 426.7 million years ago
Un período de tiempo de 432.9 a 426.7 millones de años atrás
432.9 eta 426.7 milioi urte arteko denbora-tartea
Aikajakso 432.9–426.7 miljoonaa vuotta sitten
Une période de temps de 432.9 à 426.7 millions d'années
Egy 432.9-tól 426.7 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 432.9 hingga 426.7 juta tahun yang lalu
Un periodo di tempo da 432.9 a 426.7 milioni di anni fa
432.9百万年前から426.7百万年前までの時代
432.9백만 년 전부터 426.7백만 년 전까지의 시기
Laikotarpis nuo 432.9 iki 426.7 milijonų metų prieš dabartį
Een tijdperiode van 432.9 tot 426.7 miljoen jaar geleden
Een tijdsperiode van 432.9 tot 426.7 miljoen jaar geleden
En tidsperiode fra 432.9 til 426.7 millioner år siden
Okres czasu od 432.9 do 426.7 milionów lat temu
Um período de tempo de 432.9 a 426.7 milhões de anos atrás
Временной период от 432.9 до 426.7 миллионов лет назад
Časové obdobie od 432.9 do 426.7 miliónov rokov pred naším letopočtom
432.9 ile 426.7 milyon yıl önce arasındaki zaman dilimi
距今 432.9 至 426.7 百万年前的时期
Eralar
Eres
Éry
Ären
Eras
Erak
Erat
Ères
Érák
Era
Ere
Eros
Era’s
Æraer
Ery
Эры
An era is the second largest geochronologic time unit and is equivalent to a chronostratigraphic erathem. These are tens to hundreds of millions of years in length
Känozoikum
Cenozoico
Cénozoïque
kainozoikum
Kenozoikum
Kenozoik
kenozoikum
Kaynozoy
Cenozoic
Zenozoiko
Kenotsooinen
新生界／代
생대
Kainozojus
Kenozoïcum
Cenozoïcum
Кайнозойская
Senozoyik
新 生界
66.00-dən 0 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 66.00 a 0 milions d'anys enrere
Časové období od 66.00 do 0 milionů let před naším letopočtem
Ein Zeitraum von 66.00 bis 0 Millionen Jahren
A time period from 66.00 to 0 million years ago
Un período de tiempo de 66.00 a 0 millones de años atrás
66.00 eta 0 milioi urte arteko denbora-tartea
Aikajakso 66.00–0 miljoonaa vuotta sitten
Une période de temps de 66.00 à 0 millions d'années
Egy 66.00-tól 0 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 66.00 hingga 0 juta tahun yang lalu
Un periodo di tempo da 66.00 a 0 milioni di anni fa
66.00百万年前から0百万年前までの時代
66.00백만 년 전부터 0백만 년 전까지의 시기
Laikotarpis nuo 66.00 iki 0 milijonų metų prieš dabartį
Een tijdperiode van 66.00 tot 0 miljoen jaar geleden
Een tijdsperiode van 66.00 tot 0 miljoen jaar geleden
En tidsperiode fra 66.00 til 0 millioner år siden
Okres czasu od 66.00 do 0 milionów lat temu
Um período de tempo de 66.00 a 0 milhões de anos atrás
Временной период от 66.00 до 0 миллионов лет назад
Časové obdobie od 66.00 do 0 miliónov rokov pred naším letopočtom
66.00 ile 0 milyon yıl önce arasındaki zaman dilimi
距今 66.00 至 0 百万年前的时期
Eoarchaikum
Eoarcaico
eoarchaikum
Eoarkeikum
Eoarchaik
Eoarxey
Eoarqueà
Eoarqueano
Eoarkear
Eoarkeeinen
Éoarchéen
Eoarchean
Eoarcheano
原太古界／代（原始生界／代）
초시생대
Eoarchėjus
Eoarcheïcum
Eoarcheaan
Эоархейская
Eo arkeen
始太古界
4031-dən 3600 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 4031 a 3600 milions d'anys enrere
Časové období od 4031 do 3600 milionů let před naším letopočtem
Ein Zeitraum von 4031 bis 3600 Millionen Jahren
A time period from 4031 to 3600 million years ago
Un período de tiempo de 4031 a 3600 millones de años atrás
4031 eta 3600 milioi urte arteko denbora-tartea
Aikajakso 4031–3600 miljoonaa vuotta sitten
Une période de temps de 4031 à 3600 millions d'années
Egy 4031-tól 3600 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 4031 hingga 3600 juta tahun yang lalu
Un periodo di tempo da 4031 a 3600 milioni di anni fa
4031百万年前から3600百万年前までの時代
4031백만 년 전부터 3600백만 년 전까지의 시기
Laikotarpis nuo 4031 iki 3600 milijonų metų prieš dabartį
Een tijdperiode van 4031 tot 3600 miljoen jaar geleden
Een tijdsperiode van 4031 tot 3600 miljoen jaar geleden
En tidsperiode fra 4031 til 3600 millioner år siden
Okres czasu od 4031 do 3600 milionów lat temu
Um período de tempo de 4031 a 3600 milhões de anos atrás
Временной период от 4031 до 3600 миллионов лет назад
Časové obdobie od 4031 do 3600 miliónov rokov pred naším letopočtom
4031 ile 3600 milyon yıl önce arasındaki zaman dilimi
距今 4031 至 3600 百万年前的时期
Mesoarchaikum
Mesoarcaico
Mésoarchéen
Mesoarkeikum
Mezoarchaik
mezoarchaikum
Mezoarxey
Mesoarqueà
mesoarchaikum
Mesoarqueano
Mesoarkear
Mesoarkeeinen
Mesoarchean
Mesoarcheano
中太古界／代 （中始生界／代）
중시생대
Mezoarchėjus
Mesoarcheïcum
Mesoarcheaan
Мезоархейская
Meso arkeen
中太古界
3200-dən 2800 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 3200 a 2800 milions d'anys enrere
Časové období od 3200 do 2800 milionů let před naším letopočtem
Ein Zeitraum von 3200 bis 2800 Millionen Jahren
A time period from 3200 to 2800 million years ago
Un período de tiempo de 3200 a 2800 millones de años atrás
3200 eta 2800 milioi urte arteko denbora-tartea
Aikajakso 3200–2800 miljoonaa vuotta sitten
Une période de temps de 3200 à 2800 millions d'années
Egy 3200-tól 2800 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 3200 hingga 2800 juta tahun yang lalu
Un periodo di tempo da 3200 a 2800 milioni di anni fa
3200百万年前から2800百万年前までの時代
3200백만 년 전부터 2800백만 년 전까지의 시기
Laikotarpis nuo 3200 iki 2800 milijonų metų prieš dabartį
Een tijdperiode van 3200 tot 2800 miljoen jaar geleden
Een tijdsperiode van 3200 tot 2800 miljoen jaar geleden
En tidsperiode fra 3200 til 2800 millioner år siden
Okres czasu od 3200 do 2800 milionów lat temu
Um período de tempo de 3200 a 2800 milhões de anos atrás
Временной период от 3200 до 2800 миллионов лет назад
Časové obdobie od 3200 do 2800 miliónov rokov pred naším letopočtom
3200 ile 2800 milyon yıl önce arasındaki zaman dilimi
距今 3200 至 2800 百万年前的时期
Mesoproterozoikum
Mesoproterozoico
Mésoprotérozoïque
mezoproterozoikum
Mezoproterozojus
Mesoproterozoïcum
Mezoproterozoik
Mezoproterozoy
Mesoproterozoic
mesoproterozoikum
Mesoproterozoiko
Mesoproterotsooinen
中原生界／代
중원생대
Мезопротерозойская
Mezo proterozoyik
中元古界
1600-dən 1000 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 1600 a 1000 milions d'anys enrere
Časové období od 1600 do 1000 milionů let před naším letopočtem
Ein Zeitraum von 1600 bis 1000 Millionen Jahren
A time period from 1600 to 1000 million years ago
Un período de tiempo de 1600 a 1000 millones de años atrás
1600 eta 1000 milioi urte arteko denbora-tartea
Aikajakso 1600–1000 miljoonaa vuotta sitten
Une période de temps de 1600 à 1000 millions d'années
Egy 1600-tól 1000 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 1600 hingga 1000 juta tahun yang lalu
Un periodo di tempo da 1600 a 1000 milioni di anni fa
1600百万年前から1000百万年前までの時代
1600백만 년 전부터 1000백만 년 전까지의 시기
Laikotarpis nuo 1600 iki 1000 milijonų metų prieš dabartį
Een tijdperiode van 1600 tot 1000 miljoen jaar geleden
Een tijdsperiode van 1600 tot 1000 miljoen jaar geleden
En tidsperiode fra 1600 til 1000 millioner år siden
Okres czasu od 1600 do 1000 milionów lat temu
Um período de tempo de 1600 a 1000 milhões de anos atrás
Временной период от 1600 до 1000 миллионов лет назад
Časové obdobie od 1600 do 1000 miliónov rokov pred naším letopočtom
1600 ile 1000 milyon yıl önce arasındaki zaman dilimi
距今 1600 至 1000 百万年前的时期
Mesozoikum
Mesozoico
Mésozoïque
mezozoikum
Mezozojus
Mesozoïcum
Mezozoik
Mezozoy
Mesozoic
mesozoikum
Mesozoiko
Mesotsooinen
中生界／代
중생대
Мезозойская
Mezozoyik
中 生 界
251.902-dən 66.00 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 251.902 a 66.00 milions d'anys enrere
Časové období od 251.902 do 66.00 milionů let před naším letopočtem
Ein Zeitraum von 251.902 bis 66.00 Millionen Jahren
A time period from 251.902 to 66.00 million years ago
Un período de tiempo de 251.902 a 66.00 millones de años atrás
251.902 eta 66.00 milioi urte arteko denbora-tartea
Aikajakso 251.902–66.00 miljoonaa vuotta sitten
Une période de temps de 251.902 à 66.00 millions d'années
Egy 251.902-tól 66.00 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 251.902 hingga 66.00 juta tahun yang lalu
Un periodo di tempo da 251.902 a 66.00 milioni di anni fa
251.902百万年前から66.00百万年前までの時代
251.902백만 년 전부터 66.00백만 년 전까지의 시기
Laikotarpis nuo 251.902 iki 66.00 milijonų metų prieš dabartį
Een tijdperiode van 251.902 tot 66.00 miljoen jaar geleden
Een tijdsperiode van 251.902 tot 66.00 miljoen jaar geleden
En tidsperiode fra 251.902 til 66.00 millioner år siden
Okres czasu od 251.902 do 66.00 milionów lat temu
Um período de tempo de 251.902 a 66.00 milhões de anos atrás
Временной период от 251.902 до 66.00 миллионов лет назад
Časové obdobie od 251.902 do 66.00 miliónov rokov pred naším letopočtom
251.902 ile 66.00 milyon yıl önce arasındaki zaman dilimi
距今 251.902 至 66.00 百万年前的时期
Neoarchaikum
Neoarcaico
Néoarchéen
neoarchaikum
Neoarkeikum
Neoarchaik
Neoarxey
Neoarqueà
Neoarqueano
Neoarkear
Neoarkeeinen
Neoarchean
Neoarcheano
新太古界／代 （新始生界／代）
신시생대
Neoarchėjus
Neoarcheïcum
Neoarcheaan
Неоархейская
Neo arkeen
新太古界
2800-dən 2500 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 2800 a 2500 milions d'anys enrere
Časové období od 2800 do 2500 milionů let před naším letopočtem
Ein Zeitraum von 2800 bis 2500 Millionen Jahren
A time period from 2800 to 2500 million years ago
Un período de tiempo de 2800 a 2500 millones de años atrás
2800 eta 2500 milioi urte arteko denbora-tartea
Aikajakso 2800–2500 miljoonaa vuotta sitten
Une période de temps de 2800 à 2500 millions d'années
Egy 2800-tól 2500 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 2800 hingga 2500 juta tahun yang lalu
Un periodo di tempo da 2800 a 2500 milioni di anni fa
2800百万年前から2500百万年前までの時代
2800백만 년 전부터 2500백만 년 전까지의 시기
Laikotarpis nuo 2800 iki 2500 milijonų metų prieš dabartį
Een tijdperiode van 2800 tot 2500 miljoen jaar geleden
Een tijdsperiode van 2800 tot 2500 miljoen jaar geleden
En tidsperiode fra 2800 til 2500 millioner år siden
Okres czasu od 2800 do 2500 milionów lat temu
Um período de tempo de 2800 a 2500 milhões de anos atrás
Временной период от 2800 до 2500 миллионов лет назад
Časové obdobie od 2800 do 2500 miliónov rokov pred naším letopočtom
2800 ile 2500 milyon yıl önce arasındaki zaman dilimi
距今 2800 至 2500 百万年前的时期
Neoproterozoikum
Néoprotérozoïque
neoproterozoikum
Neoproterozojus
Neoproterozoïcum
Neoproterozoik
Neoproterozoy
Neoproterozoic
Neoproterozoico
Neoproterozoiko
Neoproterotsooinen
新原生界／代
신원생대
Неопротерозойская
Neo proterozoyik
新元古界
1000-dən 538.8 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 1000 a 538.8 milions d'anys enrere
Časové období od 1000 do 538.8 milionů let před naším letopočtem
Ein Zeitraum von 1000 bis 538.8 Millionen Jahren
A time period from 1000 to 538.8 million years ago
Un período de tiempo de 1000 a 538.8 millones de años atrás
1000 eta 538.8 milioi urte arteko denbora-tartea
Aikajakso 1000–538.8 miljoonaa vuotta sitten
Une période de temps de 1000 à 538.8 millions d'années
Egy 1000-tól 538.8 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 1000 hingga 538.8 juta tahun yang lalu
Un periodo di tempo da 1000 a 538.8 milioni di anni fa
1000百万年前から538.8百万年前までの時代
1000백만 년 전부터 538.8백만 년 전까지의 시기
Laikotarpis nuo 1000 iki 538.8 milijonų metų prieš dabartį
Een tijdperiode van 1000 tot 538.8 miljoen jaar geleden
Een tijdsperiode van 1000 tot 538.8 miljoen jaar geleden
En tidsperiode fra 1000 til 538.8 millioner år siden
Okres czasu od 1000 do 538.8 milionów lat temu
Um período de tempo de 1000 a 538.8 milhões de anos atrás
Временной период от 1000 до 538.8 миллионов лет назад
Časové obdobie od 1000 do 538.8 miliónov rokov pred naším letopočtom
1000 ile 538.8 milyon yıl önce arasındaki zaman dilimi
距今 1000 至 538.8 百万年前的时期
Paläoarchaikum
Paleoarcaico
Paléoarchéen
Paleoarkeikum
Paleoarchaik
paleoarchaikum
Paleoarxey
Paleoarqueà
Paleoarqueano
Paleoarkear
Paleoarkeeinen
Paleoarchean
Paleoarcheano
古太古界／代 （古始生界／代）
고시생대
Paleoarchėjus
Paleoarcheïcum
Paleoarcheaan
Палеоархейская
Paleo arkeen
古太古界
3600-dən 3200 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 3600 a 3200 milions d'anys enrere
Časové období od 3600 do 3200 milionů let před naším letopočtem
Ein Zeitraum von 3600 bis 3200 Millionen Jahren
A time period from 3600 to 3200 million years ago
Un período de tiempo de 3600 a 3200 millones de años atrás
3600 eta 3200 milioi urte arteko denbora-tartea
Aikajakso 3600–3200 miljoonaa vuotta sitten
Une période de temps de 3600 à 3200 millions d'années
Egy 3600-tól 3200 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 3600 hingga 3200 juta tahun yang lalu
Un periodo di tempo da 3600 a 3200 milioni di anni fa
3600百万年前から3200百万年前までの時代
3600백만 년 전부터 3200백만 년 전까지의 시기
Laikotarpis nuo 3600 iki 3200 milijonų metų prieš dabartį
Een tijdperiode van 3600 tot 3200 miljoen jaar geleden
Een tijdsperiode van 3600 tot 3200 miljoen jaar geleden
En tidsperiode fra 3600 til 3200 millioner år siden
Okres czasu od 3600 do 3200 milionów lat temu
Um período de tempo de 3600 a 3200 milhões de anos atrás
Временной период от 3600 до 3200 миллионов лет назад
Časové obdobie od 3600 do 3200 miliónov rokov pred naším letopočtom
3600 ile 3200 milyon yıl önce arasındaki zaman dilimi
距今 3600 至 3200 百万年前的时期
Paleoproterozoico
Paléoprotérozoïque
Paleoproterozojus
Paleoproterozoikum
Paleoproterozoik
paleoproterozoikum
Paleoproterozoy
Paleoproterozoic
Paläoproterozoikum
Paleoproterozoiko
Paleoproterotsooinen
古原生界／代
고원생대
Paleoproterozoïcum
Палеопротерозойская
Paleo proterozoyik
古元古界
2500-dən 1600 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 2500 a 1600 milions d'anys enrere
Časové období od 2500 do 1600 milionů let před naším letopočtem
Ein Zeitraum von 2500 bis 1600 Millionen Jahren
A time period from 2500 to 1600 million years ago
Un período de tiempo de 2500 a 1600 millones de años atrás
2500 eta 1600 milioi urte arteko denbora-tartea
Aikajakso 2500–1600 miljoonaa vuotta sitten
Une période de temps de 2500 à 1600 millions d'années
Egy 2500-tól 1600 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 2500 hingga 1600 juta tahun yang lalu
Un periodo di tempo da 2500 a 1600 milioni di anni fa
2500百万年前から1600百万年前までの時代
2500백만 년 전부터 1600백만 년 전까지의 시기
Laikotarpis nuo 2500 iki 1600 milijonų metų prieš dabartį
Een tijdperiode van 2500 tot 1600 miljoen jaar geleden
Een tijdsperiode van 2500 tot 1600 miljoen jaar geleden
En tidsperiode fra 2500 til 1600 millioner år siden
Okres czasu od 2500 do 1600 milionów lat temu
Um período de tempo de 2500 a 1600 milhões de anos atrás
Временной период от 2500 до 1600 миллионов лет назад
Časové obdobie od 2500 do 1600 miliónov rokov pred naším letopočtom
2500 ile 1600 milyon yıl önce arasındaki zaman dilimi
距今 2500 至 1600 百万年前的时期
Paläozoikum
Paléozoïque
paleozoikum
Paleozojus
Paleozoïcum
Paleozoikum
Paleozoik
Paleozoy
Paleozoic
Paleozoico
Paleozoiko
Paleotsooinen
古生界／代
고생대
Палеозойская
Paleozoyik
古 生 界
538.8-dən 251.902 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 538.8 a 251.902 milions d'anys enrere
Časové období od 538.8 do 251.902 milionů let před naším letopočtem
Ein Zeitraum von 538.8 bis 251.902 Millionen Jahren
A time period from 538.8 to 251.902 million years ago
Un período de tiempo de 538.8 a 251.902 millones de años atrás
538.8 eta 251.902 milioi urte arteko denbora-tartea
Aikajakso 538.8–251.902 miljoonaa vuotta sitten
Une période de temps de 538.8 à 251.902 millions d'années
Egy 538.8-tól 251.902 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 538.8 hingga 251.902 juta tahun yang lalu
Un periodo di tempo da 538.8 a 251.902 milioni di anni fa
538.8百万年前から251.902百万年前までの時代
538.8백만 년 전부터 251.902백만 년 전까지의 시기
Laikotarpis nuo 538.8 iki 251.902 milijonų metų prieš dabartį
Een tijdperiode van 538.8 tot 251.902 miljoen jaar geleden
Een tijdsperiode van 538.8 tot 251.902 miljoen jaar geleden
En tidsperiode fra 538.8 til 251.902 millioner år siden
Okres czasu od 538.8 do 251.902 milionów lat temu
Um período de tempo de 538.8 a 251.902 milhões de anos atrás
Временной период от 538.8 до 251.902 миллионов лет назад
Časové obdobie od 538.8 do 251.902 miliónov rokov pred naším letopočtom
538.8 ile 251.902 milyon yıl önce arasındaki zaman dilimi
距今 538.8 至 251.902 百万年前的时期
Periodlar
Períodes
Periody
Perioden
Períodos
Periodoak
Periodit
Périodes
Időszakok
Periode
Periodi
Periodai
Perioder
Okresy
Периоды
Periódy
Periyotlar
A period is equivalent to a chronostratigraphic system. These are millions to tens of millions of years in length
Periods
Calymmium
Calymmien
calymmi
Kalim
Calimmià
calymm
Calímico
Calymmiano
Calymmiar
Kalym
Calymmian
Calimmiano
カリミアン
칼리마기
Kalymas
Calymmiaan
Kalymian
Калиммская
kalym
Kalimiyen
盖层系
1600-dən 1400 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 1600 a 1400 milions d'anys enrere
Časové období od 1600 do 1400 milionů let před naším letopočtem
Ein Zeitraum von 1600 bis 1400 Millionen Jahren
A time period from 1600 to 1400 million years ago
Un período de tiempo de 1600 a 1400 millones de años atrás
1600 eta 1400 milioi urte arteko denbora-tartea
Aikajakso 1600–1400 miljoonaa vuotta sitten
Une période de temps de 1600 à 1400 millions d'années
Egy 1600-tól 1400 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 1600 hingga 1400 juta tahun yang lalu
Un periodo di tempo da 1600 a 1400 milioni di anni fa
1600百万年前から1400百万年前までの時代
1600백만 년 전부터 1400백만 년 전까지의 시기
Laikotarpis nuo 1600 iki 1400 milijonų metų prieš dabartį
Een tijdperiode van 1600 tot 1400 miljoen jaar geleden
Een tijdsperiode van 1600 tot 1400 miljoen jaar geleden
En tidsperiode fra 1600 til 1400 millioner år siden
Okres czasu od 1600 do 1400 milionów lat temu
Um período de tempo de 1600 a 1400 milhões de anos atrás
Временной период от 1600 до 1400 миллионов лет назад
Časové obdobie od 1600 do 1400 miliónov rokov pred naším letopočtom
1600 ile 1400 milyon yıl önce arasındaki zaman dilimi
距今 1600 至 1400 百万年前的时期
Kambrium
Cámbrico
Kambri
Cambrien
Kambras
Cambrium
Kambr
kambrium
Kembri
Cambrià
Kanbriar
Cambriano
カンブリア系／紀
캄브리아기
Кембрийская
Kambriyen
寒 武 系
538.8-dən 486.85 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 538.8 a 486.85 milions d'anys enrere
Časové období od 538.8 do 486.85 milionů let před naším letopočtem
Ein Zeitraum von 538.8 bis 486.85 Millionen Jahren
A time period from 538.8 to 486.85 million years ago
Un período de tiempo de 538.8 a 486.85 millones de años atrás
538.8 eta 486.85 milioi urte arteko denbora-tartea
Aikajakso 538.8–486.85 miljoonaa vuotta sitten
Une période de temps de 538.8 à 486.85 millions d'années
Egy 538.8-tól 486.85 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 538.8 hingga 486.85 juta tahun yang lalu
Un periodo di tempo da 538.8 a 486.85 milioni di anni fa
538.8百万年前から486.85百万年前までの時代
538.8백만 년 전부터 486.85백만 년 전까지의 시기
Laikotarpis nuo 538.8 iki 486.85 milijonų metų prieš dabartį
Een tijdperiode van 538.8 tot 486.85 miljoen jaar geleden
Een tijdsperiode van 538.8 tot 486.85 miljoen jaar geleden
En tidsperiode fra 538.8 til 486.85 millioner år siden
Okres czasu od 538.8 do 486.85 milionów lat temu
Um período de tempo de 538.8 a 486.85 milhões de anos atrás
Временной период от 538.8 до 486.85 миллионов лет назад
Časové obdobie od 538.8 do 486.85 miliónov rokov pred naším letopočtom
538.8 ile 486.85 milyon yıl önce arasındaki zaman dilimi
距今 538.8 至 486.85 百万年前的时期
Cambrian
Karbon
Carbonífero
Kivihiili
Carbonifère
karbon
Karbonas
Carboon
karbón
Karbon (Daş kömür)
Carbonífer
Karbonifero
Carbonifero
石炭系／紀
석탄기
Каменноугольная
Karbonifer
石 炭 系
358.86-dən 298.9 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 358.86 a 298.9 milions d'anys enrere
Časové období od 358.86 do 298.9 milionů let před naším letopočtem
Ein Zeitraum von 358.86 bis 298.9 Millionen Jahren
A time period from 358.86 to 298.9 million years ago
Un período de tiempo de 358.86 a 298.9 millones de años atrás
358.86 eta 298.9 milioi urte arteko denbora-tartea
Aikajakso 358.86–298.9 miljoonaa vuotta sitten
Une période de temps de 358.86 à 298.9 millions d'années
Egy 358.86-tól 298.9 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 358.86 hingga 298.9 juta tahun yang lalu
Un periodo di tempo da 358.86 a 298.9 milioni di anni fa
358.86百万年前から298.9百万年前までの時代
358.86백만 년 전부터 298.9백만 년 전까지의 시기
Laikotarpis nuo 358.86 iki 298.9 milijonų metų prieš dabartį
Een tijdperiode van 358.86 tot 298.9 miljoen jaar geleden
Een tijdsperiode van 358.86 tot 298.9 miljoen jaar geleden
En tidsperiode fra 358.86 til 298.9 millioner år siden
Okres czasu od 358.86 do 298.9 milionów lat temu
Um período de tempo de 358.86 a 298.9 milhões de anos atrás
Временной период от 358.86 до 298.9 миллионов лет назад
Časové obdobie od 358.86 do 298.9 miliónov rokov pred naším letopočtom
358.86 ile 298.9 milyon yıl önce arasındaki zaman dilimi
距今 358.86 至 298.9 百万年前的时期
Carboniferous
Kreide
Cretácico
Liitu
Crétacé
kréta
Kreida
Krijt
Kritt
Kreda
krieda
Təbaşir
Cretaci
křída
Kretazeo
Kapur
Cretacico
白亜系／紀
백악기
Cretáceo
Меловая
Kretase
白 垩系
143.1-dən 66.00 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 143.1 a 66.00 milions d'anys enrere
Časové období od 143.1 do 66.00 milionů let před naším letopočtem
Ein Zeitraum von 143.1 bis 66.00 Millionen Jahren
A time period from 143.1 to 66.00 million years ago
Un período de tiempo de 143.1 a 66.00 millones de años atrás
143.1 eta 66.00 milioi urte arteko denbora-tartea
Aikajakso 143.1–66.00 miljoonaa vuotta sitten
Une période de temps de 143.1 à 66.00 millions d'années
Egy 143.1-tól 66.00 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 143.1 hingga 66.00 juta tahun yang lalu
Un periodo di tempo da 143.1 a 66.00 milioni di anni fa
143.1百万年前から66.00百万年前までの時代
143.1백만 년 전부터 66.00백만 년 전까지의 시기
Laikotarpis nuo 143.1 iki 66.00 milijonų metų prieš dabartį
Een tijdperiode van 143.1 tot 66.00 miljoen jaar geleden
Een tijdsperiode van 143.1 tot 66.00 miljoen jaar geleden
En tidsperiode fra 143.1 til 66.00 millioner år siden
Okres czasu od 143.1 do 66.00 milionów lat temu
Um período de tempo de 143.1 a 66.00 milhões de anos atrás
Временной период от 143.1 до 66.00 миллионов лет назад
Časové obdobie od 143.1 do 66.00 miliónov rokov pred naším letopočtom
143.1 ile 66.00 milyon yıl önce arasındaki zaman dilimi
距今 143.1 至 66.00 百万年前的时期
Cretaceous
Cryogénien
kryogén
Kriogen
Criogenià
Cryogenium
Criogénico
Criogeniano
Cryogeniar
Kryogeeni
kriogéni
Cryogenian
クライオジェニアン
크리오스진기
Kriogenas
Cryogeniaan
Kryogen
Kriogenian
Cryogeniano
Криогенская
Kriyojeniyen
成冰系
720-dən 635 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 720 a 635 milions d'anys enrere
Časové období od 720 do 635 milionů let před naším letopočtem
Ein Zeitraum von 720 bis 635 Millionen Jahren
A time period from 720 to 635 million years ago
Un período de tiempo de 720 a 635 millones de años atrás
720 eta 635 milioi urte arteko denbora-tartea
Aikajakso 720–635 miljoonaa vuotta sitten
Une période de temps de 720 à 635 millions d'années
Egy 720-tól 635 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 720 hingga 635 juta tahun yang lalu
Un periodo di tempo da 720 a 635 milioni di anni fa
720百万年前から635百万年前までの時代
720백만 년 전부터 635백만 년 전까지의 시기
Laikotarpis nuo 720 iki 635 milijonų metų prieš dabartį
Een tijdperiode van 720 tot 635 miljoen jaar geleden
Een tijdsperiode van 720 tot 635 miljoen jaar geleden
En tidsperiode fra 720 til 635 millioner år siden
Okres czasu od 720 do 635 milionów lat temu
Um período de tempo de 720 a 635 milhões de anos atrás
Временной период от 720 до 635 миллионов лет назад
Časové obdobie od 720 do 635 miliónov rokov pred naším letopočtom
720 ile 635 milyon yıl önce arasındaki zaman dilimi
距今 720 至 635 百万年前的时期
Devon
Devónico
Devoni
Dévonien
devon
Devonas
Devoon
Dewon
devón
Devonià
Devoniar
Devoniano
デボン系／紀
데본기
Девонская
Devoniyen
泥 盆 系
419.62-dən 358.86 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 419.62 a 358.86 milions d'anys enrere
Časové období od 419.62 do 358.86 milionů let před naším letopočtem
Ein Zeitraum von 419.62 bis 358.86 Millionen Jahren
A time period from 419.62 to 358.86 million years ago
Un período de tiempo de 419.62 a 358.86 millones de años atrás
419.62 eta 358.86 milioi urte arteko denbora-tartea
Aikajakso 419.62–358.86 miljoonaa vuotta sitten
Une période de temps de 419.62 à 358.86 millions d'années
Egy 419.62-tól 358.86 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 419.62 hingga 358.86 juta tahun yang lalu
Un periodo di tempo da 419.62 a 358.86 milioni di anni fa
419.62百万年前から358.86百万年前までの時代
419.62백만 년 전부터 358.86백만 년 전까지의 시기
Laikotarpis nuo 419.62 iki 358.86 milijonų metų prieš dabartį
Een tijdperiode van 419.62 tot 358.86 miljoen jaar geleden
Een tijdsperiode van 419.62 tot 358.86 miljoen jaar geleden
En tidsperiode fra 419.62 til 358.86 millioner år siden
Okres czasu od 419.62 do 358.86 milionów lat temu
Um período de tempo de 419.62 a 358.86 milhões de anos atrás
Временной период от 419.62 до 358.86 миллионов лет назад
Časové obdobie od 419.62 do 358.86 miliónov rokov pred naším letopočtom
419.62 ile 358.86 milyon yıl önce arasındaki zaman dilimi
距今 419.62 至 358.86 百万年前的时期
Devonian
Ectasium
Ectas
Ectasien
ectasi
Ectasiano
Ektaz
Ectasià
ectas
Ectásico
Ectasiar
Ectasian
エクタシアン
엑타시스기
Ektasas
Ectasiaan
Ektas
Ektazjan
Эктазская
ektas
Ektasiyen
延展系
1400-dən 1200 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 1400 a 1200 milions d'anys enrere
Časové období od 1400 do 1200 milionů let před naším letopočtem
Ein Zeitraum von 1400 bis 1200 Millionen Jahren
A time period from 1400 to 1200 million years ago
Un período de tiempo de 1400 a 1200 millones de años atrás
1400 eta 1200 milioi urte arteko denbora-tartea
Aikajakso 1400–1200 miljoonaa vuotta sitten
Une période de temps de 1400 à 1200 millions d'années
Egy 1400-tól 1200 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 1400 hingga 1200 juta tahun yang lalu
Un periodo di tempo da 1400 a 1200 milioni di anni fa
1400百万年前から1200百万年前までの時代
1400백만 년 전부터 1200백만 년 전까지의 시기
Laikotarpis nuo 1400 iki 1200 milijonų metų prieš dabartį
Een tijdperiode van 1400 tot 1200 miljoen jaar geleden
Een tijdsperiode van 1400 tot 1200 miljoen jaar geleden
En tidsperiode fra 1400 til 1200 millioner år siden
Okres czasu od 1400 do 1200 milionów lat temu
Um período de tempo de 1400 a 1200 milhões de anos atrás
Временной период от 1400 до 1200 миллионов лет назад
Časové obdobie od 1400 do 1200 miliónov rokov pred naším letopočtom
1400 ile 1200 milyon yıl önce arasındaki zaman dilimi
距今 1400 至 1200 百万年前的时期
Ediacarium
Ediakaras
Ediacara
Ediakar
Ediacariano
Ediacarià
ediakar
Ediacárico
Ediacarar
Ediakara
Édiacarien
ediacarai
Ediacaran
Ediacarano
エディアカラン
에디아카라기
Ediacaraan
Эдиакарская
Ediyakaran
埃迪卡拉系
635-dən 538.8 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 635 a 538.8 milions d'anys enrere
Časové období od 635 do 538.8 milionů let před naším letopočtem
Ein Zeitraum von 635 bis 538.8 Millionen Jahren
A time period from 635 to 538.8 million years ago
Un período de tiempo de 635 a 538.8 millones de años atrás
635 eta 538.8 milioi urte arteko denbora-tartea
Aikajakso 635–538.8 miljoonaa vuotta sitten
Une période de temps de 635 à 538.8 millions d'années
Egy 635-tól 538.8 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 635 hingga 538.8 juta tahun yang lalu
Un periodo di tempo da 635 a 538.8 milioni di anni fa
635百万年前から538.8百万年前までの時代
635백만 년 전부터 538.8백만 년 전까지의 시기
Laikotarpis nuo 635 iki 538.8 milijonų metų prieš dabartį
Een tijdperiode van 635 tot 538.8 miljoen jaar geleden
Een tijdsperiode van 635 tot 538.8 miljoen jaar geleden
En tidsperiode fra 635 til 538.8 millioner år siden
Okres czasu od 635 do 538.8 milionów lat temu
Um período de tempo de 635 a 538.8 milhões de anos atrás
Временной период от 635 до 538.8 миллионов лет назад
Časové obdobie od 635 do 538.8 miliónov rokov pred naším letopočtom
635 ile 538.8 milyon yıl önce arasındaki zaman dilimi
距今 635 至 538.8 百万年前的时期
Jura
Jurásico
Jurassique
jura
Jurássico
Yura
Juràssic
Jurasiko
Giurassico
ジュラ系／紀
쥐라기
Юрская
侏罗 系
201.4-dən 143.1 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 201.4 a 143.1 milions d'anys enrere
Časové období od 201.4 do 143.1 milionů let před naším letopočtem
Ein Zeitraum von 201.4 bis 143.1 Millionen Jahren
A time period from 201.4 to 143.1 million years ago
Un período de tiempo de 201.4 a 143.1 millones de años atrás
201.4 eta 143.1 milioi urte arteko denbora-tartea
Aikajakso 201.4–143.1 miljoonaa vuotta sitten
Une période de temps de 201.4 à 143.1 millions d'années
Egy 201.4-tól 143.1 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 201.4 hingga 143.1 juta tahun yang lalu
Un periodo di tempo da 201.4 a 143.1 milioni di anni fa
201.4百万年前から143.1百万年前までの時代
201.4백만 년 전부터 143.1백만 년 전까지의 시기
Laikotarpis nuo 201.4 iki 143.1 milijonų metų prieš dabartį
Een tijdperiode van 201.4 tot 143.1 miljoen jaar geleden
Een tijdsperiode van 201.4 tot 143.1 miljoen jaar geleden
En tidsperiode fra 201.4 til 143.1 millioner år siden
Okres czasu od 201.4 do 143.1 milionów lat temu
Um período de tempo de 201.4 a 143.1 milhões de anos atrás
Временной период от 201.4 до 143.1 миллионов лет назад
Časové obdobie od 201.4 do 143.1 miliónov rokov pred naším letopočtom
201.4 ile 143.1 milyon yıl önce arasındaki zaman dilimi
距今 201.4 至 143.1 百万年前的时期
Jurassic
Neogen
Neógeno
Neogeeni
Néogène
neogén
Neogenas
Neogeen
Neogeno
Neogene
新第三系／紀
신진기
Неогеновая
Neojen
新 近 系
23.04-dən 2.58 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 23.04 a 2.58 milions d'anys enrere
Časové období od 23.04 do 2.58 milionů let před naším letopočtem
Ein Zeitraum von 23.04 bis 2.58 Millionen Jahren
A time period from 23.04 to 2.58 million years ago
Un período de tiempo de 23.04 a 2.58 millones de años atrás
23.04 eta 2.58 milioi urte arteko denbora-tartea
Aikajakso 23.04–2.58 miljoonaa vuotta sitten
Une période de temps de 23.04 à 2.58 millions d'années
Egy 23.04-tól 2.58 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 23.04 hingga 2.58 juta tahun yang lalu
Un periodo di tempo da 23.04 a 2.58 milioni di anni fa
23.04百万年前から2.58百万年前までの時代
23.04백만 년 전부터 2.58백만 년 전까지의 시기
Laikotarpis nuo 23.04 iki 2.58 milijonų metų prieš dabartį
Een tijdperiode van 23.04 tot 2.58 miljoen jaar geleden
Een tijdsperiode van 23.04 tot 2.58 miljoen jaar geleden
En tidsperiode fra 23.04 til 2.58 millioner år siden
Okres czasu od 23.04 do 2.58 milionów lat temu
Um período de tempo de 23.04 a 2.58 milhões de anos atrás
Временной период от 23.04 до 2.58 миллионов лет назад
Časové obdobie od 23.04 do 2.58 miliónov rokov pred naším letopočtom
23.04 ile 2.58 milyon yıl önce arasındaki zaman dilimi
距今 23.04 至 2.58 百万年前的时期
Ordovizium
Ordovícico
Ordoviikki
Ordovicien
ordovícium
Ordovikas
Ordovicium
Ordowik
ordovik
Ordovik
Ordovicià
Ordoviziar
Ordovisiu
Ordoviciano
オルドビス系／紀
오르도비스기
Ордовикская
Ordovisiyen
奥 陶 系
486.85-dən 443.1 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 486.85 a 443.1 milions d'anys enrere
Časové období od 486.85 do 443.1 milionů let před naším letopočtem
Ein Zeitraum von 486.85 bis 443.1 Millionen Jahren
A time period from 486.85 to 443.1 million years ago
Un período de tiempo de 486.85 a 443.1 millones de años atrás
486.85 eta 443.1 milioi urte arteko denbora-tartea
Aikajakso 486.85–443.1 miljoonaa vuotta sitten
Une période de temps de 486.85 à 443.1 millions d'années
Egy 486.85-tól 443.1 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 486.85 hingga 443.1 juta tahun yang lalu
Un periodo di tempo da 486.85 a 443.1 milioni di anni fa
486.85百万年前から443.1百万年前までの時代
486.85백만 년 전부터 443.1백만 년 전까지의 시기
Laikotarpis nuo 486.85 iki 443.1 milijonų metų prieš dabartį
Een tijdperiode van 486.85 tot 443.1 miljoen jaar geleden
Een tijdsperiode van 486.85 tot 443.1 miljoen jaar geleden
En tidsperiode fra 486.85 til 443.1 millioner år siden
Okres czasu od 486.85 do 443.1 milionów lat temu
Um período de tempo de 486.85 a 443.1 milhões de anos atrás
Временной период от 486.85 до 443.1 миллионов лет назад
Časové obdobie od 486.85 do 443.1 miliónov rokov pred naším letopočtom
486.85 ile 443.1 milyon yıl önce arasındaki zaman dilimi
距今 486.85 至 443.1 百万年前的时期
Ordovician
Orosirium
Orosir
Orosirien
orosiri
Orosiriano
Orozir
Orosirià
orosir
Orosírico
Orosiriar
Orosirian
オロシリアン
오로세이라기
Orosiras
Orosiriaan
Orozoirian
Орозирская
Orosiriyen
造山系
2050-dən 1800 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 2050 a 1800 milions d'anys enrere
Časové období od 2050 do 1800 milionů let před naším letopočtem
Ein Zeitraum von 2050 bis 1800 Millionen Jahren
A time period from 2050 to 1800 million years ago
Un período de tiempo de 2050 a 1800 millones de años atrás
2050 eta 1800 milioi urte arteko denbora-tartea
Aikajakso 2050–1800 miljoonaa vuotta sitten
Une période de temps de 2050 à 1800 millions d'années
Egy 2050-tól 1800 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 2050 hingga 1800 juta tahun yang lalu
Un periodo di tempo da 2050 a 1800 milioni di anni fa
2050百万年前から1800百万年前までの時代
2050백만 년 전부터 1800백만 년 전까지의 시기
Laikotarpis nuo 2050 iki 1800 milijonų metų prieš dabartį
Een tijdperiode van 2050 tot 1800 miljoen jaar geleden
Een tijdsperiode van 2050 tot 1800 miljoen jaar geleden
En tidsperiode fra 2050 til 1800 millioner år siden
Okres czasu od 2050 do 1800 milionów lat temu
Um período de tempo de 2050 a 1800 milhões de anos atrás
Временной период от 2050 до 1800 миллионов лет назад
Časové obdobie od 2050 do 1800 miliónov rokov pred naším letopočtom
2050 ile 1800 milyon yıl önce arasındaki zaman dilimi
距今 2050 至 1800 百万年前的时期
Paläogen
Paleógeno
Paleogeeni
Paléogène
paleogén
Paleogenas
Paleogeen
Paleogen
Paleogeno
Paleogene
古第三系／紀
고진기
Палеогеновая
Paleojen
古 近 系
66.00-dən 23.04 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 66.00 a 23.04 milions d'anys enrere
Časové období od 66.00 do 23.04 milionů let před naším letopočtem
Ein Zeitraum von 66.00 bis 23.04 Millionen Jahren
A time period from 66.00 to 23.04 million years ago
Un período de tiempo de 66.00 a 23.04 millones de años atrás
66.00 eta 23.04 milioi urte arteko denbora-tartea
Aikajakso 66.00–23.04 miljoonaa vuotta sitten
Une période de temps de 66.00 à 23.04 millions d'années
Egy 66.00-tól 23.04 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 66.00 hingga 23.04 juta tahun yang lalu
Un periodo di tempo da 66.00 a 23.04 milioni di anni fa
66.00百万年前から23.04百万年前までの時代
66.00백만 년 전부터 23.04백만 년 전까지의 시기
Laikotarpis nuo 66.00 iki 23.04 milijonų metų prieš dabartį
Een tijdperiode van 66.00 tot 23.04 miljoen jaar geleden
Een tijdsperiode van 66.00 tot 23.04 miljoen jaar geleden
En tidsperiode fra 66.00 til 23.04 millioner år siden
Okres czasu od 66.00 do 23.04 milionów lat temu
Um período de tempo de 66.00 a 23.04 milhões de anos atrás
Временной период от 66.00 до 23.04 миллионов лет назад
Časové obdobie od 66.00 do 23.04 miliónov rokov pred naším letopočtom
66.00 ile 23.04 milyon yıl önce arasındaki zaman dilimi
距今 66.00 至 23.04 百万年前的时期
Perm
Pérmico
Permi
Permien
perm
Permas
Permià
Permiar
Perem
Permiano
ペルム系／紀
페름기
Пермская
Permiyen
二 叠 系
298.9-dən 251.902 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 298.9 a 251.902 milions d'anys enrere
Časové období od 298.9 do 251.902 milionů let před naším letopočtem
Ein Zeitraum von 298.9 bis 251.902 Millionen Jahren
A time period from 298.9 to 251.902 million years ago
Un período de tiempo de 298.9 a 251.902 millones de años atrás
298.9 eta 251.902 milioi urte arteko denbora-tartea
Aikajakso 298.9–251.902 miljoonaa vuotta sitten
Une période de temps de 298.9 à 251.902 millions d'années
Egy 298.9-tól 251.902 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 298.9 hingga 251.902 juta tahun yang lalu
Un periodo di tempo da 298.9 a 251.902 milioni di anni fa
298.9百万年前から251.902百万年前までの時代
298.9백만 년 전부터 251.902백만 년 전까지의 시기
Laikotarpis nuo 298.9 iki 251.902 milijonų metų prieš dabartį
Een tijdperiode van 298.9 tot 251.902 miljoen jaar geleden
Een tijdsperiode van 298.9 tot 251.902 miljoen jaar geleden
En tidsperiode fra 298.9 til 251.902 millioner år siden
Okres czasu od 298.9 do 251.902 milionów lat temu
Um período de tempo de 298.9 a 251.902 milhões de anos atrás
Временной период от 298.9 до 251.902 миллионов лет назад
Časové obdobie od 298.9 do 251.902 miliónov rokov pred naším letopočtom
298.9 ile 251.902 milyon yıl önce arasındaki zaman dilimi
距今 298.9 至 251.902 百万年前的时期
Permian
Quartär
Cuaternario
Kvartääri
Quaternaire
Kvarteras
Kwartair
Kvartær
Czwartorzęd
Quaternário
kvartér
Dördüncü dövr
Quaternari
Kuaternario
kvarter
Kuarter
Quaternario
第四系／紀
제4기
Quartair
Четвертичная
Kuvaterner
第 四 系
2.58-dən 0 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 2.58 a 0 milions d'anys enrere
Časové období od 2.58 do 0 milionů let před naším letopočtem
Ein Zeitraum von 2.58 bis 0 Millionen Jahren
A time period from 2.58 to 0 million years ago
Un período de tiempo de 2.58 a 0 millones de años atrás
2.58 eta 0 milioi urte arteko denbora-tartea
Aikajakso 2.58–0 miljoonaa vuotta sitten
Une période de temps de 2.58 à 0 millions d'années
Egy 2.58-tól 0 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 2.58 hingga 0 juta tahun yang lalu
Un periodo di tempo da 2.58 a 0 milioni di anni fa
2.58百万年前から0百万年前までの時代
2.58백만 년 전부터 0백만 년 전까지의 시기
Laikotarpis nuo 2.58 iki 0 milijonų metų prieš dabartį
Een tijdperiode van 2.58 tot 0 miljoen jaar geleden
Een tijdsperiode van 2.58 tot 0 miljoen jaar geleden
En tidsperiode fra 2.58 til 0 millioner år siden
Okres czasu od 2.58 do 0 milionów lat temu
Um período de tempo de 2.58 a 0 milhões de anos atrás
Временной период от 2.58 до 0 миллионов лет назад
Časové obdobie od 2.58 do 0 miliónov rokov pred naším letopočtom
2.58 ile 0 milyon yıl önce arasındaki zaman dilimi
距今 2.58 至 0 百万年前的时期
Quaternary
Rhyacium
Rhyacien
rhyaci
Rias
Riacià
rhyak
Riácico
Rhyaciano
Rhyaciar
Ryax
Rhyacian
Riaciano
リィアキアン
라이악스기
Ryakas
Rhyaciaan
Riacjan
Ряская
ryak
Riyasiyen
层侵系
2300-dən 2050 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 2300 a 2050 milions d'anys enrere
Časové období od 2300 do 2050 milionů let před naším letopočtem
Ein Zeitraum von 2300 bis 2050 Millionen Jahren
A time period from 2300 to 2050 million years ago
Un período de tiempo de 2300 a 2050 millones de años atrás
2300 eta 2050 milioi urte arteko denbora-tartea
Aikajakso 2300–2050 miljoonaa vuotta sitten
Une période de temps de 2300 à 2050 millions d'années
Egy 2300-tól 2050 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 2300 hingga 2050 juta tahun yang lalu
Un periodo di tempo da 2300 a 2050 milioni di anni fa
2300百万年前から2050百万年前までの時代
2300백만 년 전부터 2050백만 년 전까지의 시기
Laikotarpis nuo 2300 iki 2050 milijonų metų prieš dabartį
Een tijdperiode van 2300 tot 2050 miljoen jaar geleden
Een tijdsperiode van 2300 tot 2050 miljoen jaar geleden
En tidsperiode fra 2300 til 2050 millioner år siden
Okres czasu od 2300 do 2050 milionów lat temu
Um período de tempo de 2300 a 2050 milhões de anos atrás
Временной период от 2300 до 2050 миллионов лет назад
Časové obdobie od 2300 do 2050 miliónov rokov pred naším letopočtom
2300 ile 2050 milyon yıl önce arasındaki zaman dilimi
距今 2300 至 2050 百万年前的时期
Siderium
Sider
Sidérien
sideri
Sideriano
Siderià
sider
Sidérico
Sideriar
Siderian
シデリアン
시데로스기
Sideras
Sideriaan
Syderyjski
Сидерская
sidér
Sideriyen
成铁系
2500-dən 2300 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 2500 a 2300 milions d'anys enrere
Časové období od 2500 do 2300 milionů let před naším letopočtem
Ein Zeitraum von 2500 bis 2300 Millionen Jahren
A time period from 2500 to 2300 million years ago
Un período de tiempo de 2500 a 2300 millones de años atrás
2500 eta 2300 milioi urte arteko denbora-tartea
Aikajakso 2500–2300 miljoonaa vuotta sitten
Une période de temps de 2500 à 2300 millions d'années
Egy 2500-tól 2300 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 2500 hingga 2300 juta tahun yang lalu
Un periodo di tempo da 2500 a 2300 milioni di anni fa
2500百万年前から2300百万年前までの時代
2500백만 년 전부터 2300백만 년 전까지의 시기
Laikotarpis nuo 2500 iki 2300 milijonų metų prieš dabartį
Een tijdperiode van 2500 tot 2300 miljoen jaar geleden
Een tijdsperiode van 2500 tot 2300 miljoen jaar geleden
En tidsperiode fra 2500 til 2300 millioner år siden
Okres czasu od 2500 do 2300 milionów lat temu
Um período de tempo de 2500 a 2300 milhões de anos atrás
Временной период от 2500 до 2300 миллионов лет назад
Časové obdobie od 2500 do 2300 miliónov rokov pred naším letopočtom
2500 ile 2300 milyon yıl önce arasındaki zaman dilimi
距今 2500 至 2300 百万年前的时期
Silur
Siluuri
Silurien
szilur
Silūras
Siluur
Sylur
silúr
Silurià
silur
Silúrico
Siluriar
Siluriano
シルル系／紀
실루리아기
Силурийская
Siluriyen
志 留 系
443.1-dən 419.62 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 443.1 a 419.62 milions d'anys enrere
Časové období od 443.1 do 419.62 milionů let před naším letopočtem
Ein Zeitraum von 443.1 bis 419.62 Millionen Jahren
A time period from 443.1 to 419.62 million years ago
Un período de tiempo de 443.1 a 419.62 millones de años atrás
443.1 eta 419.62 milioi urte arteko denbora-tartea
Aikajakso 443.1–419.62 miljoonaa vuotta sitten
Une période de temps de 443.1 à 419.62 millions d'années
Egy 443.1-tól 419.62 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 443.1 hingga 419.62 juta tahun yang lalu
Un periodo di tempo da 443.1 a 419.62 milioni di anni fa
443.1百万年前から419.62百万年前までの時代
443.1백만 년 전부터 419.62백만 년 전까지의 시기
Laikotarpis nuo 443.1 iki 419.62 milijonų metų prieš dabartį
Een tijdperiode van 443.1 tot 419.62 miljoen jaar geleden
Een tijdsperiode van 443.1 tot 419.62 miljoen jaar geleden
En tidsperiode fra 443.1 til 419.62 millioner år siden
Okres czasu od 443.1 do 419.62 milionów lat temu
Um período de tempo de 443.1 a 419.62 milhões de anos atrás
Временной период от 443.1 до 419.62 миллионов лет назад
Časové obdobie od 443.1 do 419.62 miliónov rokov pred naším letopočtom
443.1 ile 419.62 milyon yıl önce arasındaki zaman dilimi
距今 443.1 至 419.62 百万年前的时期
Silurian
Statherium
Stather
Stathérien
statheri
Stater
Estaterià
stather
Estatérico
Statheriano
Statheriar
Statherian
スタテリアン
스타테로스기
Stateras
Statheriaan
Staterian
Staheriano
Статерская
statér
Stateriyen
固结系
1800-dən 1600 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 1800 a 1600 milions d'anys enrere
Časové období od 1800 do 1600 milionů let před naším letopočtem
Ein Zeitraum von 1800 bis 1600 Millionen Jahren
A time period from 1800 to 1600 million years ago
Un período de tiempo de 1800 a 1600 millones de años atrás
1800 eta 1600 milioi urte arteko denbora-tartea
Aikajakso 1800–1600 miljoonaa vuotta sitten
Une période de temps de 1800 à 1600 millions d'années
Egy 1800-tól 1600 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 1800 hingga 1600 juta tahun yang lalu
Un periodo di tempo da 1800 a 1600 milioni di anni fa
1800百万年前から1600百万年前までの時代
1800백만 년 전부터 1600백만 년 전까지의 시기
Laikotarpis nuo 1800 iki 1600 milijonų metų prieš dabartį
Een tijdperiode van 1800 tot 1600 miljoen jaar geleden
Een tijdsperiode van 1800 tot 1600 miljoen jaar geleden
En tidsperiode fra 1800 til 1600 millioner år siden
Okres czasu od 1800 do 1600 milionów lat temu
Um período de tempo de 1800 a 1600 milhões de anos atrás
Временной период от 1800 до 1600 миллионов лет назад
Časové obdobie od 1800 do 1600 miliónov rokov pred naším letopočtom
1800 ile 1600 milyon yıl önce arasındaki zaman dilimi
距今 1800 至 1600 百万年前的时期
Stenium
Sten
Sténien
steni
Steniano
Estenià
sten
Esténico
Steniar
Stenian
ステニアン
스테노스기
Stenas
Steniaan
Стенская
stén
Steniyen
狭带系
1200-dən 1000 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 1200 a 1000 milions d'anys enrere
Časové období od 1200 do 1000 milionů let před naším letopočtem
Ein Zeitraum von 1200 bis 1000 Millionen Jahren
A time period from 1200 to 1000 million years ago
Un período de tiempo de 1200 a 1000 millones de años atrás
1200 eta 1000 milioi urte arteko denbora-tartea
Aikajakso 1200–1000 miljoonaa vuotta sitten
Une période de temps de 1200 à 1000 millions d'années
Egy 1200-tól 1000 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 1200 hingga 1000 juta tahun yang lalu
Un periodo di tempo da 1200 a 1000 milioni di anni fa
1200百万年前から1000百万年前までの時代
1200백만 년 전부터 1000백만 년 전까지의 시기
Laikotarpis nuo 1200 iki 1000 milijonų metų prieš dabartį
Een tijdperiode van 1200 tot 1000 miljoen jaar geleden
Een tijdsperiode van 1200 tot 1000 miljoen jaar geleden
En tidsperiode fra 1200 til 1000 millioner år siden
Okres czasu od 1200 do 1000 milionów lat temu
Um período de tempo de 1200 a 1000 milhões de anos atrás
Временной период от 1200 до 1000 миллионов лет назад
Časové obdobie od 1200 do 1000 miliónov rokov pred naším letopočtom
1200 ile 1000 milyon yıl önce arasındaki zaman dilimi
距今 1200 至 1000 百万年前的时期
Tonium
Ton
Tonien
toni
Toniano
Toni
Tonià
ton
Tónico
Toniar
Tonian
トニアン
토노스기
Tonas
Toniaan
Тонская
tón
Toniyen
拉伸系
1000-dən 720 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 1000 a 720 milions d'anys enrere
Časové období od 1000 do 720 milionů let před naším letopočtem
Ein Zeitraum von 1000 bis 720 Millionen Jahren
A time period from 1000 to 720 million years ago
Un período de tiempo de 1000 a 720 millones de años atrás
1000 eta 720 milioi urte arteko denbora-tartea
Aikajakso 1000–720 miljoonaa vuotta sitten
Une période de temps de 1000 à 720 millions d'années
Egy 1000-tól 720 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 1000 hingga 720 juta tahun yang lalu
Un periodo di tempo da 1000 a 720 milioni di anni fa
1000百万年前から720百万年前までの時代
1000백만 년 전부터 720백만 년 전까지의 시기
Laikotarpis nuo 1000 iki 720 milijonų metų prieš dabartį
Een tijdperiode van 1000 tot 720 miljoen jaar geleden
Een tijdsperiode van 1000 tot 720 miljoen jaar geleden
En tidsperiode fra 1000 til 720 millioner år siden
Okres czasu od 1000 do 720 milionów lat temu
Um período de tempo de 1000 a 720 milhões de anos atrás
Временной период от 1000 до 720 миллионов лет назад
Časové obdobie od 1000 do 720 miliónov rokov pred naším letopočtom
1000 ile 720 milyon yıl önce arasındaki zaman dilimi
距今 1000 至 720 百万年前的时期
Trias
Triásico
triász
Triasas
trias
Triàsic
Triasiko
Triassico
三畳系／紀
트라이아스기
Triássico
Триасовая
Triyas
三 叠 系
251.902-dən 201.4 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 251.902 a 201.4 milions d'anys enrere
Časové období od 251.902 do 201.4 milionů let před naším letopočtem
Ein Zeitraum von 251.902 bis 201.4 Millionen Jahren
A time period from 251.902 to 201.4 million years ago
Un período de tiempo de 251.902 a 201.4 millones de años atrás
251.902 eta 201.4 milioi urte arteko denbora-tartea
Aikajakso 251.902–201.4 miljoonaa vuotta sitten
Une période de temps de 251.902 à 201.4 millions d'années
Egy 251.902-tól 201.4 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 251.902 hingga 201.4 juta tahun yang lalu
Un periodo di tempo da 251.902 a 201.4 milioni di anni fa
251.902百万年前から201.4百万年前までの時代
251.902백만 년 전부터 201.4백만 년 전까지의 시기
Laikotarpis nuo 251.902 iki 201.4 milijonų metų prieš dabartį
Een tijdperiode van 251.902 tot 201.4 miljoen jaar geleden
Een tijdsperiode van 251.902 tot 201.4 miljoen jaar geleden
En tidsperiode fra 251.902 til 201.4 millioner år siden
Okres czasu od 251.902 do 201.4 milionów lat temu
Um período de tempo de 251.902 a 201.4 milhões de anos atrás
Временной период от 251.902 до 201.4 миллионов лет назад
Časové obdobie od 251.902 do 201.4 miliónov rokov pred naším letopočtom
251.902 ile 201.4 milyon yıl önce arasındaki zaman dilimi
距今 251.902 至 201.4 百万年前的时期
Triassic
An 8-bit per channel, hexidecimal representation of RGB colours. This datatype uses a microformat of "#{R}{G}{B}" with hexidecimal value for {R}, {G} & {B} between 00 and FF.
Alt periodlar
Subperíodes
Podperiody
Unterperioden
Subperíodos
Azpiperiodoak
Alaperiodit
Sous-périodes
Alidőszakok
Subperiode
Sotto-periodi
亜紀
아기
Subperiodai
Subperioden
Underperioder
Podokresy
Подпериоды
Podperiódy
Alt periyotlar
亚纪
A sub-period an informal geochronologic time unit that is only defined for the Carboniferous Period. the two instances are tens of millions of years in length
Sub Periods
Mississippium
Mississippi
Mississippien
mississippi
Missisipi
Mississippià
mississipp
Misisípico
Misisipiano
Mississippiar
Mississippian
Mississippiano
ミシシッピアン 亜系／亜紀
기 미시시피아기
Misisipas
Mississippiaan
Mississíppico
Мисиссипская
misisip
Misisipiyen
密 西 西 比 亚 系
358.86-dən 323.4 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 358.86 a 323.4 milions d'anys enrere
Časové období od 358.86 do 323.4 milionů let před naším letopočtem
Ein Zeitraum von 358.86 bis 323.4 Millionen Jahren
A time period from 358.86 to 323.4 million years ago
Un período de tiempo de 358.86 a 323.4 millones de años atrás
358.86 eta 323.4 milioi urte arteko denbora-tartea
Aikajakso 358.86–323.4 miljoonaa vuotta sitten
Une période de temps de 358.86 à 323.4 millions d'années
Egy 358.86-tól 323.4 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 358.86 hingga 323.4 juta tahun yang lalu
Un periodo di tempo da 358.86 a 323.4 milioni di anni fa
358.86百万年前から323.4百万年前までの時代
358.86백만 년 전부터 323.4백만 년 전까지의 시기
Laikotarpis nuo 358.86 iki 323.4 milijonų metų prieš dabartį
Een tijdperiode van 358.86 tot 323.4 miljoen jaar geleden
Een tijdsperiode van 358.86 tot 323.4 miljoen jaar geleden
En tidsperiode fra 358.86 til 323.4 millioner år siden
Okres czasu od 358.86 do 323.4 milionów lat temu
Um período de tempo de 358.86 a 323.4 milhões de anos atrás
Временной период от 358.86 до 323.4 миллионов лет назад
Časové obdobie od 358.86 do 323.4 miliónov rokov pred naším letopočtom
358.86 ile 323.4 milyon yıl önce arasındaki zaman dilimi
距今 358.86 至 323.4 百万年前的时期
Pennsylvanium
Pennsylvania
pennsylvaniai
Pensylwan
Pensilvaniya
Pennsylvanià
pennsylvan
Pensilvánico
Pensilvaniano
Pennsylvaniar
Pennsylvanie
Pennsylvanian
Pennsylvaniano
ペンシルバニアン 亜系／亜紀
펜실베니아아기
Pensilvanas
Pennsylvanien
Pennsylvaniaan
Pennsylvánico
Пенсильванская
pensylván
Pensilvaniyen
宾 夕 法 尼 亚 亚 系
323.4-dən 298.9 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 323.4 a 298.9 milions d'anys enrere
Časové období od 323.4 do 298.9 milionů let před naším letopočtem
Ein Zeitraum von 323.4 bis 298.9 Millionen Jahren
A time period from 323.4 to 298.9 million years ago
Un período de tiempo de 323.4 a 298.9 millones de años atrás
323.4 eta 298.9 milioi urte arteko denbora-tartea
Aikajakso 323.4–298.9 miljoonaa vuotta sitten
Une période de temps de 323.4 à 298.9 millions d'années
Egy 323.4-tól 298.9 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 323.4 hingga 298.9 juta tahun yang lalu
Un periodo di tempo da 323.4 a 298.9 milioni di anni fa
323.4百万年前から298.9百万年前までの時代
323.4백만 년 전부터 298.9백만 년 전까지의 시기
Laikotarpis nuo 323.4 iki 298.9 milijonų metų prieš dabartį
Een tijdperiode van 323.4 tot 298.9 miljoen jaar geleden
Een tijdsperiode van 323.4 tot 298.9 miljoen jaar geleden
En tidsperiode fra 323.4 til 298.9 millioner år siden
Okres czasu od 323.4 do 298.9 milionów lat temu
Um período de tempo de 323.4 a 298.9 milhões de anos atrás
Временной период от 323.4 до 298.9 миллионов лет назад
Časové obdobie od 323.4 do 298.9 miliónov rokov pred naším letopočtom
323.4 ile 298.9 milyon yıl önce arasındaki zaman dilimi
距今 323.4 至 298.9 百万年前的时期
Super eonlar
Supereons
Supereony
Superäonen
Supereones
Supereoiak
Supereonit
Superéons
Szupereonok
Supereon
Super-eoni
超累代
초누대
Supereonai
Supereonen
Supereoner
Суперэоны
Supereóny
Süper eonlar
超宙
A super eon is an informal time unit that contains all of the eons before any evidence of life. The sole supereon is about two billion years in length
Super Eons
Präkambrium
Precámbrico
Prekambri
Précambrien
prekambrium
Prekambras
Precambrium
Prekambrium
Prekambr
Kembriyəqədər
Precambrià
Kanbriarraurre
Precambriano
先カンブリア（累）界／時代
선 캄 브 리 아 시 대
Pré-Cambriano
Докембрийская
predkambrium
Pre-Kambriyen
前 寒 武 系
4567-dən 538.8 milyon il əvvələ qədər olan zaman dövrü
Un període de temps de 4567 a 538.8 milions d'anys enrere
Časové období od 4567 do 538.8 milionů let před naším letopočtem
Ein Zeitraum von 4567 bis 538.8 Millionen Jahren
A time period from 4567 to 538.8 million years ago
Un período de tiempo de 4567 a 538.8 millones de años atrás
4567 eta 538.8 milioi urte arteko denbora-tartea
Aikajakso 4567–538.8 miljoonaa vuotta sitten
Une période de temps de 4567 à 538.8 millions d'années
Egy 4567-tól 538.8 millió évig tartó időszak ezelőtt
Suatu periode waktu dari 4567 hingga 538.8 juta tahun yang lalu
Un periodo di tempo da 4567 a 538.8 milioni di anni fa
4567百万年前から538.8百万年前までの時代
4567백만 년 전부터 538.8백만 년 전까지의 시기
Laikotarpis nuo 4567 iki 538.8 milijonų metų prieš dabartį
Een tijdperiode van 4567 tot 538.8 miljoen jaar geleden
Een tijdsperiode van 4567 tot 538.8 miljoen jaar geleden
En tidsperiode fra 4567 til 538.8 millioner år siden
Okres czasu od 4567 do 538.8 milionów lat temu
Um período de tempo de 4567 a 538.8 milhões de anos atrás
Временной период от 4567 до 538.8 миллионов лет назад
Časové obdobie od 4567 do 538.8 miliónov rokov pred naším letopočtom
4567 ile 538.8 milyon yıl önce arasındaki zaman dilimi
距今 4567 至 538.8 百万年前的时期
Precambrian
The expression of a time instant millions of years before the present as a floating point number.
International Commission on Stratigraphy
Beynəlxalq Stratiqrafiya Komissiyası
Comissió Internacional de Estratigrafia
Mezinárodní stratigrafická komise
Internationale Kommission für Stratigraphie
Comisión Internacional de Estratigrafía
Stratigrafia Nazioarteko Batzordea
Kansainvälinen Stratigrafiakomissio
Commission Internationale de Stratigraphie
Nemzetközi Sztratigráfiai Bizottság
Komisi Internasional Stratigrafi
Commissione Internazionale di Stratigrafia
国際層序委員会
국제 층서 위원회
Tarptautinė stratigrafijos komisija
Internationale Commissie voor Stratigrafie
Den internasjonale stratigrafikommisjonen
Międzynarodowa Komisja Stratygrafii
Comissão Internacional de Estratigrafia
Международная комиссия по стратиграфии
Medzinárodná stratigrafická komisia
Uluslararası Stratigrafi Komisyonu
国际地层学委员会
TERN's ecologists have determined the feature type is _plant community_ or _plant population_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/ea3a4c64-dac3-4660-809a-8ad5ced8997b[`plant community`] or http://linked.data.gov.au/def/tern-cv/ae71c3f6-d430-400f-a1d4-97a333b4ee02[`plant population`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/f437f23a-7965-4bae-9dc3-2aead06786ec>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
Observations following the Basal wedge protocol are made in the context of a site visit.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/f437f23a-7965-4bae-9dc3-2aead06786ec>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
Result value's unit of measure _MUST_ have the value `unit:M2-PER-HA`.
The result _MUST_ have `unit:M2-PER-HA` as the value for `tern:unit`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/f437f23a-7965-4bae-9dc3-2aead06786ec> ; sosa:hasResult ?this . }
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/a7d605e0-7d90-473e-aac0-21cdf380576f>`. `<https://linked.data.gov.au/def/nrm/a7d605e0-7d90-473e-aac0-21cdf380576f>` is the IRI for "Basal wedge protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/a7d605e0-7d90-473e-aac0-21cdf380576f`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/f437f23a-7965-4bae-9dc3-2aead06786ec>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
The result _MUST_ have a positive value.
TERN's ecologists have determined the feature type is _plant population_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/ae71c3f6-d430-400f-a1d4-97a333b4ee02[`plant population`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/36580cad-0509-4642-a450-47f3433ad244>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/36580cad-0509-4642-a450-47f3433ad244> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/36580cad-0509-4642-a450-47f3433ad244>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/36580cad-0509-4642-a450-47f3433ad244>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
The result _MUST_ have a non-negative value.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/36580cad-0509-4642-a450-47f3433ad244> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8fea241f-8e98-4814-b9b9-db1bd5446910>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/8fea241f-8e98-4814-b9b9-db1bd5446910> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8fea241f-8e98-4814-b9b9-db1bd5446910>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8fea241f-8e98-4814-b9b9-db1bd5446910>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/8fea241f-8e98-4814-b9b9-db1bd5446910> ; sosa:hasResult ?this . }
Observations following the DBH protocol are made in the context of a site visit.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/5a00862b-a885-472e-8bee-561ec502653f>`. `<https://linked.data.gov.au/def/nrm/5a00862b-a885-472e-8bee-561ec502653f>` is the IRI for "DBH protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/5a00862b-a885-472e-8bee-561ec502653f`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/bf1a9efa-a3f8-4fdb-a981-02a7b49a66cc>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/bf1a9efa-a3f8-4fdb-a981-02a7b49a66cc>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/bf1a9efa-a3f8-4fdb-a981-02a7b49a66cc> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/bf1a9efa-a3f8-4fdb-a981-02a7b49a66cc>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
The result _MUST_ be be greater than 15.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6e1c8b97-3655-4a22-9647-02f2c756e789>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6e1c8b97-3655-4a22-9647-02f2c756e789>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/6e1c8b97-3655-4a22-9647-02f2c756e789> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6e1c8b97-3655-4a22-9647-02f2c756e789>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be greater than or equal to 5.
The result _MUST_ be greater than or equal to 5.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3da2a8ca-c0a3-4761-8736-507255eeee68>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Tree trunk types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Tree trunk types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3da2a8ca-c0a3-4761-8736-507255eeee68> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'9282400b-56c3-49a9-bb82-87ef74914690'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3da2a8ca-c0a3-4761-8736-507255eeee68> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3da2a8ca-c0a3-4761-8736-507255eeee68>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3da2a8ca-c0a3-4761-8736-507255eeee68>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/9282400b-56c3-49a9-bb82-87ef74914690>`. `<https://linked.data.gov.au/def/nrm/9282400b-56c3-49a9-bb82-87ef74914690>` is the IRI for "Tree trunk types".
The value of `tern:vocabulary` _MUST_ match the pattern `9282400b-56c3-49a9-bb82-87ef74914690$`.
A catalogue of reference Semantic Web ontologies used by KurrawongAI
1.0.1 2026-04: made ValPub valid 1.0 2017: As released with the initial SHACL publication
This shapes graph can be used to validate SHACL shapes graphs against a subset of the syntax rules.
A shape that can be used to validate syntax rules for other shapes.
A shape that can be used to validate the syntax rules of well-formed SHACL paths.
Each list member (including this node) must be have the shape shsh:ListNodeShape.
A shape describing well-formed RDF lists. Currently does not check for non-recursion. This could be expressed using SHACL-SPARQL.
The Standard Identifiers Scheme lists standard number or code systems and assigns a URI to each database or publication that defines or contains the identifiers. The purpose of these source codes is to enable the type of standard numbers or codes in resource descriptions to be indicated by URI.
2025-12-11: Last Record Update Latest date a member of this scheme was updated
Standard Identifiers
AGORHA (Accès global et organisé aux ressources en histoire de l'art)
AGROVOC multilingual agricultural thesaurus
American National Standards Institute and National Information Standards Organisation number for an ANSI or ANSI/NISO standard
Australian registered body number (ABRN)
Australian standards (Standards Australia)
BALaT (Belgian art links and tools) People & institutions
Biographical directory of the United States Congress
Biographies of the entomologists of the world
Большая российская энциклопедия = Bolʹshai︠a︡ rossiĭskai︠a︡ ėnt︠s︡iklopedii︠a︡ (Great Russian Encyclopedia)
Biografisch Portaal van Nederland = Biography portal of the Netherlands
CANTIC (Catàleg d'autoritats de noms i títols de Catalunya)
Congress.gov congressional committee codes
ELSST thesaurus - European language social science thesaurus
Digital platform for manuscript material from Swiss libraries and archives
The platform for digitized rare books from Swiss institutions
FAST: faceted application of subject terminology
Global agricultural concept space (GACS)
Getty thesaurus of geographic names online
Geographic names information system (GNIS)
Gemeenschappelijke Thesaurus voor Audiovisuele Archieven
Global trade identification number 14 (EAN/UCC-128 or ITF-14)
International standard book number (the actionable ISBN)
ISBN (International Standard Book Number) registrant element
ISIL (International standard identifier for libraries and related organizations)
International Organization for Standardization number for an ISO standard
Linking International standard serial number
International standard musical work code
ITAR (Importtjeneste og autoritetsregistre)
Researcher Number of the Grants-in-Aid for Scientific Research (KAKENHI) Program
Russian National Heritage Registry for Books
Author ID of the Union Catalogue Database of Japanese Texts
Work ID of the Union Catalogue Database of Japanese Texts
Library of Congress Manuscript Division field of history codes
Musée d'Orsay Catalogue des oeuvres fiche oeuvre
Musée d'Orsay Répertoire des artistes notice artiste
U.S. National Gazetteer Feature Name Identifier
NIPO (Número de Identificación de las Publicaciones Oficiales)
Open researcher and contributor identifier
Pacific Coast Architecture Database - buildings list
Pacific Coast Architecture Database - persons list
Pacific Coast Architecture Database - practices and firms
Personen uit de Nederlandse Thesaurus van Auteursnamen
Repertoire International des Sources Musicale (RISM)
S2A3 biographical database of southern African science
Publisher, distributor, or vendor stock number
Standard-Thesaurus Wirtschaft = STW thesaurus for economics
Tesauros del Patrimonio Cultural de España
UNESCO thesaurus = Thésaurus de l'UNESCO = Tesauro de la UNESCO
Verzeichnis der Drucke des 16. Jahrhunderts
Verzeichnis der Drucke des 17. Jahrhunderts
Verzeichnis der Drucke des 18. Jahrhunderts
Virtual International Authority File number
Publisher-assigned videorecording number
This vocabulary is a test vocabulary showing the use of images within Concept definitions
The default model for the content. Must be a set of SHACL Shapes
The default model for the container and the content. Must be a set of SHACL Shapes
Data for the container, usually a Catalogue, including the identity of it and each item of content
The default model for the container. Must be a set of SHACL Shapes
All the labels - possibly including names, descriptions & seeAlso links - for the Catalogue and Resource objects
Some of the labels - possibly including names, descriptions & seeAlso links - for the Catalogue and Resource objects
Incomplete Catalogue and Resource Labels
Ecological Data Exchange Specification Shapes Graph
Vocabulary for describing organizational structures, specializable to a broad variety of types of organization.
An Organization which is recognized in the world at large, in particular in legal jurisdictions, with associated rights and responsibilities. Examples include a Corporation, Charity, Government or Church. Note that this is a super class of `gr:BusinessEntity` and it is recommended to use the GoodRelations vocabulary to denote Business classifications such as DUNS or NAICS.
A role corresponding to the `org:headOf` property
Denotes a role that a Person or other Agent can take in an organization. Instances of this class describe the abstract role; to denote a specific instance of a person playing that role in a specific organization use an instance of `org:Membership`. It is common for roles to be arranged in some taxonomic structure and we use SKOS to represent that. The normal SKOS lexical properties should be used when labelling the Role. Additional descriptive properties for the Role, such as a Salary band, may be added by extension vocabularies.
This is a metalevel property which is used to annotate an `org:Role` instance with a sub-property of `org:memberOf` that can be used to directly indicate the role for easy of query. The intended semantics is a Membership relation involving the Role implies the existence of a direct property relationship through an inference rule of the form: `{ [] org:member ?p; org:organization ?o; org:role [org:roleProperty ?r] } -> {?p ?r ?o}`.
Indicates that a person is the leader or formal head of the Organization. This will normally mean that they are the root of the `org:reportsTo` (acyclic) graph, though an organization may have more than one head.
A collaboration between two or more Organizations such as a project. It meets the criteria for being an Organization in that it has an identity and defining purpose independent of its particular members but is neither a formally recognized legal entity nor a sub-unit within some larger organization. Might typically have a shorter lifetime than the Organizations within it, but not necessarily. All members are `org:Organization`s rather than individuals and those Organizations can play particular roles within the venture. Alternative names: _Project_ _Venture_ _Endeavour_ _Consortium_ _Endeavour_
Represents a collection of people organized together into a community or other social, commercial or political structure. The group has some common purpose or reason for existence which goes beyond the set of people belonging to it and can act as an Agent. Organizations are often decomposable into hierarchical structures. It is recommended that SKOS lexical labels should be used to label the Organization. In particular `skos:prefLabel` for the primary (possibly legally recognized name), `skos:altLabel` for alternative names (trading names, colloquial names) and `skos:notation` to denote a code from a code list. Alternative names: _Collective_ _Body_ _Org_ _Group_
Indicates a person who is a member of the subject Organization. Inverse of `org:memberOf`, see that property for further clarification. Provided for compatibility with `foaf:member`.
Indicates the site at which a person is based. We do not restrict the possibility that a person is based at multiple sites.
An office or other premise at which the organization is located. Many organizations are spread across multiple sites and many sites will host multiple locations. In most cases a Site will be a physical location. However, we don't exclude the possibility of non-physical sites such as a virtual office with an associated post box and phone reception service. Extensions may provide subclasses to denote particular types of site.
Indicates a classification for this Organization within some classification scheme. Extension vocabularies may wish to specialize this property to have a range corresponding to a specific `skos:ConceptScheme`. This property is under discussion and may be revised or removed - in many cases organizations are best categorized by defining a sub-class hierarchy in an extension vocabulary.
Indicates the legally registered site for the organization, in many legal jurisdictions there is a requirement that FormalOrganizations such as Companies or Charities have such a primary designed site.
Indicates a primary site for the Organization, this is the default means by which an Organization can be contacted and is not necessarily the formal headquarters.
A Post represents some position within an organization that exists independently of the person or persons filling it. Posts may be used to represent situations where a person is a member of an organization ex officio (for example the Secretary of State for Scotland is part of UK Cabinet by virtue of being Secretary of State for Scotland, not as an individual person). A post can be held by multiple people and hence can be treated as a organization in its own right.
Indicates an arbitrary relationship between two organizations. Specializations of this can be used to, for example, denote funding or supply chain relationships.
Gives a location description for a person within the organization, for example a _Mail Stop_ for internal posting purposes.
Optional property to indicate the interval for which the membership is/was valid.
Indicates the nature of an Agent's membership of an organization. Represents an n-ary relation between an Agent, an Organization and a Role. It is possible to directly indicate membership, independent of the specific Role, through use of the `org:memberOf` property.
Indicates Organization in which the Agent is a member.
Indicates the Organization in which the Post exists.
Indicates a Post which exists within the Organization.
Indicates the purpose of this Organization. There can be many purposes at different levels of abstraction but the nature of an organization is to have a reason for existence and this property is a means to document that reason. An Organization may have multiple purposes. It is recommended that the purpose be denoted by a controlled term or code list, ideally a `skos:Concept`. However, the range is left open to allow for other types of descriptive schemes. It is expected that specializations or application profiles of this vocabulary will constrain the range of the purpose. Alternative names: _remit_ _responsibility_ (esp. if applied to OrganizationalUnits such as Government Departments).
Indicates a salary or other reward associated with the role. Typically this will be denoted using an existing representation scheme such as `gr:PriceSpecification` but the range is left open to allow applications to specialize it (e.g. to remunerationInGBP).
Indicates a reporting relationship as might be depicted on an organizational chart. The precise semantics of the reporting relationship will vary by organization but is intended to encompass both direct supervisory relationships (e.g. carrying objective and salary setting authority) and more general reporting or accountability relationships (e.g. so called _dotted line_ reporting).
Indicates the Role that the Agent plays in a Membership relationship with an Organization.
Indicates an address for the site in a suitable encoding. Use of vCard (using the http://www.w3.org/TR/vcard-rdf/ vocabulary) is encouraged but the range is left open to allow other encodings to be used. The address may include email, telephone, and geo-location information and is not restricted to a physical address.
Indicates an event which resulted in this organization. Inverse of `org:resultingOrganization`.
Indicates one or more organizations that existed before the change event. Depending on the event they may or may not have continued to exist after the event. Inverse of `org:changedBy`.
Indicates a change event which resulted in a change to this organization. Depending on the event the organization may or may not have continued to exist after the event. Inverse of `org:originalOrganization`.
Represents an event which resulted in a major change to an organization such as a merger or complete restructuring. It is intended for situations where the resulting organization is sufficient distinct from the original organizations that it has a distinct identity and distinct URI. Extension vocabularies should define sub-classes of this to denote particular categories of event. The instant or interval at which the event occurred should be given by `prov:startAtTime` and `prov:endedAtTime`, a description should be given by `dct:description`.
Indicates a membership relationship that the Agent plays. Inverse of `org:member`.
Indicates the Person (or other Agent including Organization) involved in the Membership relationship. Inverse of `org:hasMembership`
Indicates a site at which the Organization has some presence even if only indirect (e.g. virtual office or a professional service which is acting as the registered address for a company). Inverse of `org:siteOf`.
Indicates a unit which is part of this Organization, e.g. a Department within a larger FormalOrganization. Inverse of `org:unitOf`.
An Organization such as a University Support Unit which is part of some larger FormalOrganization and only has full recognition within the context of that FormalOrganization, it is not a Legal Entity in its own right. Units can be large and complex containing other Units and even FormalOrganizations. Alternative names: _OU_ _Unit_ _Department_
Represents hierarchical containment of Organizations or Organizational Units; indicates an organization which is a sub-part or child of this organization. Inverse of `org:subOrganizationOf`.
Indicates an Organization of which this Unit is a part, e.g. a Department within a larger FormalOrganization. This is the inverse of `org:hasUnit`.
Indicates that a person is a member of the Organization with no indication of the nature of that membership or the role played. Note that the choice of property name is not meant to limit the property to only formal membership arrangements, it is also indended to cover related concepts such as affilliation or other involvement in the organization. Extensions can specialize this relationship to indicate particular roles within the organization or more nuanced relationships to the organization. Has an optional inverse, `org:hasmember`.
Gives an identifier, such as a company registration number, that can be used to used to uniquely identify the organization. Many different national and international identier schemes are available. The org ontology is neutral to which schemes are used. The particular identifier scheme should be indicated by the datatype of the identifier value. Using datatypes to distinguish the notation scheme used is consistent with recommended best practice for `skos:notation` of which this property is a specialization.
Indicates an organization which was created or changed as a result of the event. Inverse of `org:resultedFrom`.
Indicates an Organization which has some presence at the given site. This is the inverse of `org:hasSite`.
The transitive closure of subOrganizationOf, giving a representation of all organizations that contain this one. Note that technically this is a super property of the transitive closure so it could contain additional assertions but such usage is discouraged.
Represents hierarchical containment of Organizations or OrganizationalUnits; indicates an Organization which contains this Organization. Inverse of `org:hasSubOrganization`.
Contributor: W3C Permissions & Obligations Expression Working Group
The ODRL Vocabulary and Expression defines a set of concepts and terms (the vocabulary) and encoding mechanism (the expression) for permissions and obligations statements describing digital content usage based on the ODRL Information Model.
ODRL Version 2.2
ODRL Core Vocabulary Terms
Action
An operation on an Asset.
Actions may be allowed by Permissions, disallowed by Prohibitions, or made mandatory by Duties.
The operation relating to the Asset for which the Rule is being subjected.
Has Action
An Action asserts that another Action is not prohibited to enable its operational semantics.
The property asserts that an instance of Action entails that the other instance of Action is not prohibited.
Implies
An Action transitively asserts that another Action that encompasses its operational semantics.
The purpose is to explicitly assert that the semantics of the referenced instance of an other Action encompasses (includes) the semantics of this instance of Action. The includedIn property is transitive, and as such, the Actions form ancestor relationships.
Included In
Actions for Rules
To transfer the ownership of the Asset in perpetuity.
Transfer Ownership
To use the Asset
Use is the most generic action for all non-third-party usage. More specific types of the use action can be expressed by more targetted actions.
Use
ODRL Common Vocabulary Terms
Credit be given to copyright holder and/or author.
This term is defined by Creative Commons.
Non-Normative
Attribution
Exercising rights for commercial purposes.
Commercial Use
Distribution of derivative works.
Derivative Works
Distribution, public display, and publicly performance.
Distribution
Copyright and license notices be kept intact.
Notice
Making multiple copies.
Reproduction
Derivative works be licensed under the same terms or compatible terms as the original work.
Share Alike
Permits commercial derivatives, but only non-commercial distribution.
Sharing
Source code (the preferred form for making modifications) must be provided when exercising some rights granted by the license.
Source Code
To accept that the use of the Asset may be tracked.
The collected information may be tracked by the Assigner, or may link to a Party with the role 'trackingParty' function.
Accept Tracking
To use the Asset or parts of it as part of a composite collection.
Aggregate
To add explanatory notations/commentaries to the Asset without modifying the Asset in any other way.
Annotate
To anonymize all or parts of the Asset.
For example, to remove identifying particulars for statistical or for other comparable purposes, or to use the Asset without stating the author/source.
Anonymize
To store the Asset (in a non-transient form).
Temporal constraints may be used for temporal conditions.
Archive
To attribute the use of the Asset.
May link to an Asset with the attribution information. May link to a Party with the role “attributedParty” function.
Attribute
To compensate by transfer of some amount of value, if defined, for using or selling the Asset.
The compensation may use different types of things with a value: (i) the thing is expressed by the value (term) of the Constraint name; (b) the value is expressed by operator, rightOperand, dataType and unit. Typically the assignee will compensate the assigner, but other compensation party roles may be used.
Compensate
To create multiple copies of the Asset that are being concurrently used.
Concurrent Use
To permanently remove all copies of the Asset after it has been used.
Use a constraint to define under which conditions the Asset must be deleted.
Delete
To create a new derivative Asset from this Asset and to edit or modify the derivative.
A new asset is created and may have significant overlaps with the original Asset. (Note that the notion of whether or not the change is significant enough to qualify as a new asset is subjective). To the derived Asset a next policy may be applied.
Derive
To produce a digital copy of (or otherwise digitize) the Asset from its analogue form.
Digitize
To create a static and transient rendition of an Asset.
For example, displaying an image on a screen. If the action is to be performed to a wider audience than just the Assignees, then the Recipient constraint is recommended to be used.
Display
To supply the Asset to third-parties.
It is recommended to use nextPolicy to express the allowable usages by third-parties.
Distribute
To ensure that the Rule on the Asset is exclusive.
If used as a Duty, the assignee should be explicitly indicated as the party that is ensuring the exclusivity of the Rule.
Ensure Exclusivity
To run the computer program Asset.
For example, machine executable code or Java such as a game or application.
Execute
To extract parts of the Asset and to use it as a new Asset.
A new asset is created and may have very little in common with the original Asset. (Note that the notion of whether or not the change is significant enough to qualify as a new asset is subjective). To the extracted Asset a next policy may be applied.
Extract
To transfer the ownership of the Asset to a third party without compensation and while deleting the original asset.
Give
To grant the use of the Asset to third parties.
This action enables the assignee to create policies for the use of the Asset for third parties. The nextPolicy is recommended to be agreed with the third party. Use of temporal constraints is recommended.
Grant Use
To include other related assets in the Asset.
For example: bio picture must be included in the attribution. Use of a relation sub-property is required for the related assets.
Include
To record the Asset in an index.
For example, to include a link to the Asset in a search engine database.
Index
To inform that an action has been performed on or in relation to the Asset.
May link to a Party with the role 'informedParty' function.
Inform
To load the computer program Asset onto a storage device which allows operating or running the Asset.
Install
To change existing content of the Asset. A new asset is not created by this action.
This action will modify an asset which is typically updated from time to time without creating a new asset. If the result from modifying the asset should be a new asset the actions derive or extract should be used. (Note that the notion of whether or not the change is significant enough to qualify as a new asset is subjective).
Modify
To move the Asset from one digital location to another including deleting the original copy.
After the Asset has been moved, the original copy must be deleted.
Move
To grant the specified Policy to a third party for their use of the Asset.
Useful for downstream policies.
Next Policy
To obtain verifiable consent to perform the requested action in relation to the Asset.
May be used as a Duty to ensure that the Assigner or a Party is authorized to approve such actions on a case-by-case basis. May link to a Party with the role “consentingParty” function.
Obtain Consent
To create a sequential and transient rendition of an Asset.
For example, to play a video or audio track. If the action is to be performed to a wider audience than just the Assignees, then the Recipient constraint is recommended to be used.
Play
To publicly perform the Asset.
The asset can be performed (or communicated) in public.
Present
To create a tangible and permanent rendition of an Asset.
For example, creating a permanent, fixed (static), and directly perceivable representation of the Asset, such as printing onto paper.
Print
To obtain data from the Asset.
For example, the ability to read a record from a database (the Asset).
Read
To make duplicate copies the Asset in any material form.
Reproduce
To review the Policy applicable to the Asset.
Used when human intervention is required to review the Policy. May link to an Asset which represents the full Policy information.
Review Policy
To transfer the ownership of the Asset to a third party with compensation and while deleting the original asset.
Sell
To deliver the Asset in real-time.
The Asset maybe utilised in real-time as it is being delivered. If the action is to be performed to a wider audience than just the Assignees, then the Recipient constraint is recommended to be used.
Stream
To use the Asset in timed relations with media (audio/visual) elements of another Asset.
Synchronize
To have a text Asset read out loud.
If the action is to be performed to a wider audience than just the Assignees, then the recipient constraint is recommended to be used.
Text-to-speech
To convert the Asset into a different format.
Typically used to convert the Asset into a different format for consumption on/transfer to a third party system.
Transform
To translate the original natural language of an Asset into another natural language.
A new derivative Asset is created by that action.
Translate
To unload and delete the computer program Asset from a storage device and disable its readiness for operation.
The Asset is no longer accessible to the assignees after it has been used.
Uninstall
To apply a watermark to the Asset.
Watermark
Asset
A resource or a collection of resources that are the subject of a Rule.
The Asset entity can be any form of identifiable resource, such as data/information, content/media, applications, or services. Furthermore, it can be used to represent other Asset entities that are needed to undertake the Policy expression, such as with the Duty entity. To describe more details about the Asset, it is recommended to use Dublin Core dcterms elements or other content metadata.
An Asset that is collection of individual resources
Asset Collection
Asset and Party
Identifies an Asset/PartyCollection that the Asset/Party is a member of.
Part Of
Reference to a Asset/PartyCollection
Used by AssetCollection and PartyCollection when constraints are applied.
Source
Asset Relations
Identifies an ODRL Policy for which the identified Asset is the target Asset to all the Rules.
The Asset being identified MUST be inferred to be the target Asset of all of the Rules of the Policy.
Target Policy
The target property indicates the Asset that is the primary subject to which the Rule action directly applies.
Target
The output property specifies the Asset which is created from the output of the Action.
Output
Policy Conflict Strategy
Used to establish strategies to resolve conflicts that arise from the merging of Policies or conflicts between Permissions and Prohibitions in the same Policy.
Instances of ConflictTerm describe strategies for resolving conflicts.
Conflict Strategy Preference
The conflict-resolution strategy for a Policy.
If no strategy is specified, the default is invalid.
Handle Policy Conflicts
The policy is void.
Used to indicate the policy is void for Conflict Strategy.
Void Policy
Permissions take preference over prohibitions.
Used to determine policy conflict outcomes.
Prefer Permissions
Prohibitions take preference over permissions.
Prefer Prohibitions
Constraint Left Operands
A point in space or time defined with absolute coordinates for the positioning of the target Asset.
Example: The upper left corner of a picture may be constrained to a specific position of the canvas rendering it.
Absolute Asset Position
Measure(s) of one or two axes for 2D-objects or measure(s) of one to tree axes for 3D-objects of the target Asset.
Example: The image can be resized in width to a maximum of 1000px.
Absolute Asset Size
The absolute spatial positions of four corners of a rectangle on a 2D-canvas or the eight corners of a cuboid in a 3D-space for the target Asset to fit.
Example: The upper left corner of a picture may be constrained to a specific position of the canvas rendering it. Note: see also the Left Operand Relative Spatial Asset Position.
Absolute Spatial Asset Position
The absolute temporal positions in a media stream the target Asset has to fit.
Use with Actions including the target Asset in a larger media stream. The fragment part of a Media Fragment URI (https://www.w3.org/TR/media-frags/) may be used for the right operand. See the Left Operand realativeTemporalPosition. Example: The MP3 music file must be positioned between second 192 and 250 of the temporal length of a stream.
Absolute Temporal Asset Position
Numeric count of executions of the action of the Rule.
Count
The date (and optional time and timezone) of exercising the action of the Rule. Right operand value MUST be an xsd:date or xsd:dateTime as defined by xmlschema11-2.
The use of Timezone information is strongly recommended. The Rule may be exercised before (with operator lt/lteq) or after (with operator gt/gteq) the date(time) defined by the Right operand. Example: dateTime gteq 2017-12-31T06:00Z means the Rule can only be exercised after (and including) 6:00AM on the 31st Decemeber 2017 UTC time.
Datetime
A time delay period prior to exercising the action of the Rule. The point in time triggering this period MAY be defined by another temporal Constraint combined by a Logical Constraint (utilising the odrl:andSequence operand). Right operand value MUST be an xsd:duration as defined by xmlschema11-2.
Only the eq, gt, gteq operators SHOULD be used. Example: delayPeriod eq P60M indicates a delay of 60 Minutes before exercising the action.
Delay Period
The delivery channel used for exercising the action of the Rule.
Example: the asset may be distributed only on mobile networks.
Delivery Channel
A continuous elapsed time period which may be used for exercising of the action of the Rule. Right operand value MUST be an xsd:duration as defined by xmlschema11-2.
Only the eq, lt, lteq operators SHOULD be used. See also Metered Time. Example: elpasedTime eq P60M indicates a total elapsed time of 60 Minutes.
Elapsed Time
An identified event setting a context for exercising the action of the Rule.
Events are temporal periods of time, and operators can be used to signal before (lt), during (eq) or after (gt) the event. Example: May be taken during the “FIFA World Cup 2020” only.
Event
A transformed file format of the target Asset.
Example: An asset may be transformed into JPEG format.
File Format
A defined industry sector setting a context for exercising the action of the Rule.
Example: publishing or financial industry.
Industry Context
A natural language used by the target Asset.
Example: the asset can only be translated into Greek. Must use bcp47 codes for language values.
Language
Category of a media asset setting a context for exercising the action of the Rule.
Example media types: electronic, print, advertising, marketing. Note: The used type should not be an IANA MediaType as they are focused on technical characteristics.
Media Context
An accumulated amount of one to many metered time periods which were used for exercising the action of the Rule. Right operand value MUST be an xsd:duration as defined by xmlschema11-2.
Only the eq, lt, lteq operators SHOULD be used. See also Elapsed Time. Example: meteredTime lteq P60M indicates an accumulated period of 60 Minutes or less.
Metered Time
The amount of a financial payment. Right operand value MUST be an xsd:decimal.
Can be used for compensation duties with the unit property indicating the currency of the payment.
Payment Amount
A percentage amount of the target Asset relevant for exercising the action of the Rule. Right operand value MUST be an xsd:decimal from 0 to 100.
Example: Extract less than or equal to 50%.
Asset Percentage
Category of product or service setting a context for exercising the action of the Rule.
Example: May only be used in the XYZ Magazine.
Product Context
A defined purpose for exercising the action of the Rule.
Example: Educational use.
Purpose
The party receiving the result/outcome of exercising the action of the Rule.
The Right Operand must identify one or more specific Parties or category/ies of the Party.
Recipient
A point in space or time defined with coordinates relative to full measures the positioning of the target Asset.
Relative Asset Position
Measure(s) of one or two axes for 2D-objects or measure(s) of one to tree axes for 3D-objects - expressed as percentages of full values - of the target Asset.
Example: The image can be resized in width to a maximum of 200%. Note: See the Left Operand absoluteSize.
Relative Asset Size
The relative spatial positions - expressed as percentages of full values - of four corners of a rectangle on a 2D-canvas or the eight corners of a cuboid in a 3D-space of the target Asset.
See also Absolute Spatial Asset Position.
Relative Spatial Asset Position
See also Absolute Temporal Asset Position. Example: The MP3 music file must be positioned between the positions at 33% and 48% of the temporal length of a stream.
Relative Temporal Asset Position
Resolution of the rendition of the target Asset.
Example: the image may be printed at 1200dpi.
Rendition Resolution
A named and identified geospatial area with defined borders which is used for exercising the action of the Rule. An IRI MUST be used to represent this value.
A code value for the area and source of the code must be presented in the Right Operand. Example: the iso3166 Country Codes or the Getty Thesaurus of Geographic Names.
Geospatial Named Area
A set of coordinates setting the borders of a geospatial area used for exercising the action of the Rule. The coordinates MUST include longitude and latitude, they MAY include altitude and the geodetic datum.
The default values are the altitude of earth's surface at this location and the WGS 84 datum.
Geospatial Coordinates
An identified computing system or computing device used for exercising the action of the Rule.
Example: The system device can be identified by a unique code created from the used hardware.
System Device
A recurring period of time before the next execution of the action of the Rule. Right operand value MUST be an xsd:duration as defined by xmlschema11-2.
Only the eq operator SHOULD be used. Example: timeInterval eq P7D indicates a recurring 7 day period.
Recurring Time Interval
The unit of measure used for counting the executions of the action of the Rule.
Note: Typically used with Duties to indicate the unit entity to be counted of the Action. Example: A duty to compensate and a unitOfCount constraint of 'perUser' would indicate that the compensation by multiplied by the 'number of users'.
Unit Of Count
The version of the target Asset.
Example: Single Paperback or Multiple Issues or version 2.0 or higher.
Version
An identified location of the IT communication space which is relevant for exercising the action of the Rule.
Example: an Internet domain or IP address range.
Virtual IT Communication Location
Logical Constraint Operands
The relation is satisfied when all of the Constraints are satisfied.
This property MUST only be used for Logical Constraints, and the list of operand values MUST be Constraint instances.
And
The relation is satisfied when each of the Constraints are satisfied in the order specified.
This property MUST only be used for Logical Constraints, and the list of operand values MUST be Constraint instances. The order of the list MUST be preserved. The andSequence operator is an example where there may be temporal conditional requirements between the operands. This may lead to situations where the outcome is unresolvable, such as deadlock if one of the Constraints is unable to be satisfied. ODRL Processing systems SHOULD plan for these scenarios and implement mechanisms to resolve them.
And Sequence
The relation is satisfied when at least one of the Constraints is satisfied.
The relation is satisfied when only one, and not more, of the Constaints is satisfied
Only One
Constraint Operators
Indicating that a given value equals the right operand of the Constraint.
Equal to
Indicating that a given value is greater than the right operand of the Constraint.
Greater than
Indicating that a given value is greater than or equal to the right operand of the Constraint.
Greater than or equal to
A set-based operator indicating that a given value contains the right operand of the Constraint.
Has part
A set-based operator indicating that a given value is an instance of the right operand of the Constraint.
Is a
A set-based operator indicating that a given value is all of the right operand of the Constraint.
Is all of
A set-based operator indicating that a given value is any of the right operand of the Constraint.
Is any of
A set-based operator indicating that a given value is none of the right operand of the Constraint.
Is none of
A set-based operator indicating that a given value is contained by the right operand of the Constraint.
Is part of
Indicating that a given value is less than the right operand of the Constraint.
Less than
Indicating that a given value is less than or equal to the right operand of the Constraint.
Less than or equal to
Indicating that a given value is not equal to the right operand of the Constraint.
Not equal to
Constraint Right Operands
Indicates the actual datetime the action of the Rule was exercised.
This can be used to express constraints with a LeftOperand relative to the time the rule is exercised. Operators indicate before (lt, lteq), during (eq) or after (gt, gteq) the usage of the rule. Example: event lt policyUsage expresses that the identified event must have happened before the action of the rule is exercised.
Policy Rule Usage
Constraint
A boolean expression that refines the semantics of an Action and Party/Asset Collection or declare the conditions applicable to a Rule.
Left operand for a constraint expression.
Instances of the LeftOperand class are used as the leftOperand of a Constraint.
Left Operand
Operator for constraint expression.
Instances of the Operator class representing relational operators.
Operator
Right operand for constraint expression.
Instances of the RightOperand class are used as the rightOperand of a Constraint.
Right Operand
Constraint applied to a Rule
Constraints on Rules are used to determine if a rule is Active or not. Example: the Permission rule is only active during the year 2018.
Has Constraint
The datatype of the value of the rightOperand or rightOperandReference of a Constraint.
In RDF encodings, use of the rdf:datatype MUST be used. In JSON-LD encoding, the use of @type MUST be used.
Datatype
The left operand in a constraint expression.
Has Left Operand
The operator function applied to operands of a Constraint
Has Operator
Constraint used to refine the semantics of an Action, or Party/Asset Collection
Example: the Action print is only permitted on 50% of the asset.
Refinement
The value of the right operand in a constraint expression.
When used with set-based operators, a list of values may be used.
Has Right Operand
A reference to a web resource providing the value for the right operand of a Constraint.
An IRI that MUST be dereferenced to obtain the actual right operand value. When used with set-based operators, a list of IRIs may be used
Has Right Operand Reference
the value generated from the leftOperand action or a value related to the leftOperand set as the reference for the comparison.
Status
The unit of measurement of the value of the rightOperand or rightOperandReference of a Constraint.
Unit
Identifier for the ODRL Core Profile
ODRL Core Profile
Deprecated Terms
Specifies that the scope of the relationship is all of the collective individuals within a context.
For example, may be used to indicate all the users of a specific social network the party is a member of. Note that “group” scope is also assumed.
All
Specifies that the scope of the relationship is all of the second-level connections to the Party.
For example, may be used to indicate all “friends of friends” of the Party. Note that “group” scope is also assumed.
All Second-level Connections
Specifies that the scope of the relationship is all of the first-level connections of the Party.
For example, may be used to indicate all “friends” of the Party. Note that “group” scope is also assumed.
All First-Level Connections
Specifies that the scope of the relationship is all of the group connections of the Party.
For example, may be used to indicate all groups that the Party is a member of. Note that “group” scope is also assumed.
All Group Connections
Scopes for Asset Scope expressions.
Instances of the AssetScope class represent the terms for the scope property of Assets.
Asset Scope
Specifies that the scope of the relationship is the defined group with multiple individual members.
Group
Specifies that the scope of the relationship is the single Party individual.
Individual
Scopes for Party Scope expressions.
Instances of the PartyScope class represent the terms for the scope property of Parties.
Party Scope
Is used to indicate how to support Actions that are not part of any vocabulary or profile in the policy expression system.
Instances of UndefinedTerm describe strategies for processing unsupported actions.
Undefined Term
The act of sharing the asset to parties in close proximity to the owner.
This original term and URI from the OMA specification should be used: http://www.openmobilealliance.com/oma-dd/adhoc-share .
Ad-hoc sharing
The act of adding to the end of an asset.
Append
The act of appending data to the Asset without modifying the Asset in any other way.
Append To
The act of keeping the policy notice with the asset.
Attach policy
The act of attaching the source of the asset and its derivatives.
Attach source
The act of using the asset in a business environment.
Commercialize
The act of making an exact reproduction of the asset.
Copy
An identified device used for exercising the action of the Rule.
Device
The act of transforming the asset into a new form.
Export
The act of extracting (replicating) unchanged characters from the asset.
This original term and URI from the ONIX specification should be used: http://www.editeur.org/onix-pl/extract-char .
Extract character
The act of extracting (replicating) unchanged pages from the asset.
This original term and URI from the ONIX specification should be used: http://www.editeur.org/onix-pl/extract-page .
Extract page
The act of extracting (replicating) unchanged words from the asset.
This original term and URI from the ONIX specification should be used: http://www.editeur.org/onix-pl/extract-word .
Extract word
The Action is to be ignored and is not part of the policy – and the policy remains valid.
Used to support actions not known to the policy system.
Ignore Undefined Actions
Indicates if the Policy entity can be inherited.
A boolean value.
Inheritance Allowed
Indentifies the type of inheritance.
For example, this may indicate the business scenario, such as subscription, or prior arrangements between the parties (that are not machine representable).
Inherit Relation
The act of making available the asset to a third-party for a fixed period of time with exchange of value.
Lease
The act of making available the asset to a third-party for a fixed period of time without exchange of value.
Lend
The act of granting the right to use the asset to a third-party.
License
The act of paying a financial amount to a party for use of the asset.
Pay
The Party is the recipient of the payment.
Payee Party
The act of providing a short preview of the asset.
Use a time constraint with the appropriate action.
Preview
An value indicating the closeness or nearness.
This original term and URI from the OMA specification should be used: http://www.openmobilealliance.com/oma-dd/proximity .
proximity
The identifier of a scope that provides context to the extent of the entity.
Used to define scopes for Assets and Parties.
Scope
The act of using the asset for a purpose other than the purpose it was intended for.
Secondary Use
The act of the non-commercial reproduction and distribution of the asset to third-parties.
Share
The act of distributing any derivative asset under the same terms as the original asset.
Share-alike
The Action is to be supported as part of the policy – and the policy remains valid.
Support Undefined Actions
An identified computing system used for exercising the action of the Rule.
System
The number of seconds after which timed metering use of the asset begins.
This original term and URI from the OMA specification should be used: http://www.openmobilealliance.com/oma-dd/timed-count .
Timed Count
Relates the strategy used for handling undefined actions to a Policy.
Handle Undefined Term
The act of writing to the Asset.
Write
The act of adding data to the Asset.
Write to
Duty
The obligation to perform an Action
Relates a Duty to another Duty, the latter being a consequence of not fulfilling the former.
The consequence property is utilised to express the repercussions of not fulfilling an agreed Policy obligation or duty for a Permission. If either of these fails to be fulfilled, then this will result in the consequence Duty also becoming a new requirement, meaning that the original obligation or duty, as well as the consequence Duty must all be fulfilled
Consequence
Relates an individual Duty to a Permission.
A Duty is a pre-condition which must be fulfilled in order to receive the Permission.
Has Duty
Relates an individual Duty to a Policy.
The Duty is a requirement which must be fulfilled.
Obligation
Relates an individual remedy Duty to a Prohibition.
The remedy property expresses an agreed Duty that must be fulfilled in case that a Prohibition has been violated by being exercised.
Remedy
Logical Constraint
A logical expression that refines the semantics of an Action and Party/Asset Collection or declare the conditions applicable to a Rule.
Operand is an abstract property for a logical relationship.
Sub-properties of operand are used for Logical Constraints.
Operand
Party
An entity or a collection of entities that undertake Roles in a Rule.
The Party entity could be a person, group of people, organisation, or agent. An agent is a person or thing that takes an active role or produces a specified effect. To describe more details about the Party, it is recommended to use W3C vCard Ontology vcard-rdf or FOAF Vocabulary foaf.
A Party that is a group of individual entities
Party Collection
Party Functions
The Party is the recipient of the Rule.
Assignee
Identifies an ODRL Policy for which the identified Party undertakes the assignee functional role.
When assigneeOf has been asserted between a metadata expression and an ODRL Policy, the Party being identified MUST be inferred to undertake the assignee functional role of all the Rules of that Policy.
Assignee Of
The Party is the issuer of the Rule.
Assigner
Identifies an ODRL Policy for which the identified Party undertakes the assigner functional role.
When assignerOf has been asserted between a metadata expression and an ODRL Policy, the Party being identified MUST be inferred to undertake the assigner functional role of all the Rules of that Policy.
Assigner Of
The Party to be attributed.
Maybe specified as part of the attribute action.
Attributed Party
The Party who undertakes the attribution.
Attributing Party
The Party is the recipient of the compensation.
Maybe specified as part of the compensate duty action.
Compensated Party
The Party that is the provider of the compensation.
Compensating Party
The Party who obtains the consent.
Maybe specified as part of the obtainConsent action.
Consented Party
The Party to obtain consent from.
Consenting Party
The Party who is being contracted.
Contracted Party
The Party who is offering the contract.
Contracting Party
The Party to be informed of all uses.
Maybe specified as part of the inform action.
Informed Party
The Party who provides the inform use data.
Informing Party
The Party whose usage is being tracked.
May be specified as part of the acceptTracking action.
Tracked Party
The Party who is tracking usage.
Tracking Party
Permission
The ability to perform an Action over an Asset.
Relates an individual Permission to a Policy.
Has Permission
Policy
A non-empty group of Permissions and/or Prohibitions.
A Policy may contain multiple Rules.
Relates a (child) policy to another (parent) policy from which terms are inherited.
The child policy will inherit Rules from the parent policy
Inherits From
The identifier(s) of an ODRL Profile that the Policy conforms to.
The profile property is mandatory if the Policy is using an ODRL Profile.
Profile
An unambiguous identifier
Used by the Policy, Rule, Asset, Party, Constraint, and Logical Constraint Classes.
Unique Identifier
Policy Subclasses
A Policy that grants the assignee a Rule over an Asset from an assigner.
An Agreement Policy MUST contain at least one Permission or Prohibition rule, a Party with Assigner function, and a Party with Assignee function (in the same Permission or Prohibition). The Agreement Policy will grant the terms of the Policy from the Assigner to the Assignee.
Agreement
A Policy that proposes a Rule over an Asset from an assigner.
An Offer Policy MUST contain at least one Permission or Prohibition rule and a Party with Assigner function (in the same Permission or Prohibition). The Offer Policy MAY contain a Party with Assignee function, but MUST not grant any privileges to that Party.
Offer
A Policy that expresses a Rule over an Asset.
A Set Policy MUST contain a target Asset, and at least one Rule. A Set Policy is the default Policy subclass. The Set is aimed at scenarios where there is an open criteria for the semantics of the policy expressions and typically refined by other systems/profiles that process the information at a later time. No privileges are granted to any Party (if defined).
Set
A Policy that asserts a Rule over an Asset from parties.
For example, a party (an assignee or assigner) can claim what terms they have over an Asset. An Assertion Policy does not grant such permissions/prohibitions but only asserts the parties claims. An Assetion Policy MUST contain a target Asset, a Party with any functional role, and at least one of a Permission or Prohibition rule.
Assertion
A Policy that expresses a Rule over an Asset containing personal information.
A Privacy Policy MUST contain a target Asset, a Party with Assigner is, a Party with Assignee function, and at least one of a Permission or Prohibition rule that MUST include a Duty. The target Asset SHOULD contain or relate to personal information about the Assignee. The Duty MUST describe obligations on the Assigner about managing the Asset. The Assignee is being granted the terms of the Privacy policy from the Assigner.
Privacy Policy
A Policy that proposes a Rule over an Asset from an assignee.
A Request Policy MUST contain a target Asset, a Party with Assignee function, and at least one of a Permission or Prohibition rule. The Request MAY also contain the Party with Assigner function if this is known. No privileges are granted to any Party.
Request
A Policy that grants the holder a Rule over an Asset from an assigner.
A Ticket Policy MUST contain a target Asset and at least one of a Permission or Prohibition rule. The Ticket MAY contain the Party with Assigner function and MUST NOT contain an Assignee. The Ticket Policy will grant the terms of the Policy to the holder of that Ticket. The holder of the Ticket MAY remain unknown or MAY have to be identified at some later stage.
Ticket
Prohibition
The inability to perform an Action over an Asset.
Relates an individual Prohibition to a Policy.
Has Prohibition
Rule
An abstract concept that represents the common characteristics of Permissions, Prohibitions, and Duties.
Rule is an abstract concept.
Failure is an abstract property that defines the violation (or unmet) relationship between Rules.
The parent property to sub-properties that express explicit failure contexts.
Failure
Function is an abstract property whose sub-properties define the functional roles which may be fulfilled by a party in relation to a Rule.
Function
Relation is an abstract property which creates an explicit link between an Action and an Asset.
Sub-properties of relation are used to define the nature of that link.
Relation
The rest of the subject RDF list after the first item.
The empty list, with no items in it. If the rest of a list is nil then the list has no more items in it.
The datatype of language-tagged string values
Idiomatic property used for structured values.
This is the RDF Schema for the RDF vocabulary terms in the RDF Namespace, defined in RDF 1.1 Concepts.
The datatype of RDF literals storing fragments of HTML content
The class of containers of alternatives.
A class representing a compound literal.
The datatype of RDF literals storing JSON content.
The class of plain (i.e. untyped) literal values, as used in RIF and OWL 2
The base direction component of a CompoundLiteral.
The language component of a CompoundLiteral.
The object of the subject RDF statement.
The predicate of the subject RDF statement.
The subject of the subject RDF statement.
A unit of measure, or unit, is a particular quantity value that has been chosen as a scale for measuring other quantities the same kind (more generally of equivalent dimension). For example, the meter is a quantity of length that has been rigorously defined and standardized by the BIPM (International Board of Weights and Measures). Any measurement of the length can be expressed as a number multiplied by the unit meter. More formally, the value of a physical quantity Q with respect to a unit (U) is expressed as the scalar multiple of a real number (n) and U, as \(Q = nU\).
maxExclusive is the exclusive upper bound of the value space for a datatype with the ordered property. The value of maxExclusive must be in the value space of the base type or be equal to {value} in {base type definition}.
maxInclusive is the inclusive upper bound of the value space for a datatype with the ordered property. The value of maxInclusive must be in the value space of the base type.
minExclusive is the exclusive lower bound of the value space for a datatype with the ordered property. The value of minExclusive must be in the value space of the base type or be equal to {value} in {base type definition}.
minInclusive is the inclusive lower bound of the value space for a datatype with the ordered property. The value of minInclusive must be in the value space of the base type.
A _Dimension_ expresses a magnitude for a base quantity kind such as mass, length and time. DEPRECATED - each exponent is expressed as a property. Keep until a validation of this has been done.
Provides a way to reference a source that provided useful but non-normative information.
A Quantity Kind is any observable property that can be measured and quantified numerically. Familiar examples include physical properties such as length, mass, time, force, energy, power, electric charge, etc. Less familiar examples include currency, interest rate, price to earning ratio, and information capacity.
A big-endian system stores the most significant byte of a word at the smallest memory address and the least significant byte at the largest.
In computing, endianness is the ordering used to represent some kind of data as a sequence of smaller units. Typical cases are the order in which integer values are stored as bytes in computer memory (relative to a given memory addressing scheme) and the transmission order over a network or other medium. When specifically talking about bytes, endianness is also referred to simply as byte order. Most computer processors simply store integers as sequences of bytes, so that, conceptually, the encoded value can be obtained by simple concatenation. For an 'n-byte' integer value this allows 'n!' (n factorial) possible representations (one for each byte permutation). The two most common of them are: increasing numeric significance with increasing memory addresses, known as little-endian, and its opposite, called big-endian.
A _Binary Prefix_ is a prefix for multiples of units in data processing, data transmission, and digital information, notably the bit and the byte, to indicate multiplication by a power of 2.
Any set with cardinality greater than that of the natural numbers, or \(| X | \; > \; | \mathbb N | \), for example \(| R| \; = \; c \; > |\mathbb N |\), is said to be uncountable.
In mathematics, the cardinality of a set is a measure of the number of elements of the set. For example, the set 'A = {2, 4, 6}' contains 3 elements, and therefore 'A' has a cardinality of 3. There are two approaches to cardinality – one which compares sets directly using bijections and injections, and another which uses cardinal numbers.
In mathematics, the cardinality of a set is a measure of the number of elements of the set. For example, the set \(A = {2, 4, 6}\) contains 3 elements, and therefore \(A\) has a cardinality of 3. There are two approaches to cardinality – one which compares sets directly using bijections and injections, and another which uses cardinal numbers.
Provides a simple way of making citations.
Used to specify the values of a constant.
A Quantity Value expresses the magnitude and kind of a quantity and is given by the product of a numerical value n and a unit of measure U. The number multiplying the unit is referred to as the numerical value of the quantity expressed in that unit. Refer to NIST SP 811 section 7 for more on quantity values.
Used for all units that express counts. Examples are Atomic Number, Number, Number per Year, Percent and Sample per Second.
A Dimensionless Unit is a quantity for which all the exponents of the factors corresponding to the base quantities in its quantity dimension are zero.
Currency Units have their own subclass of unit because: (a) they have additonal properites such as 'country' and (b) their URIs do not conform to the same rules as other units.
Used for all units that express currency.
A _Decimal Prefix_ is a prefix for multiples of units that are powers of 10.
A DerivedUnit is a type specification for units that are derived from other units.
An enumeration is a set of literals from which a single value is selected. Each literal can have a tag as an integer within a standard encoding appropriate to the range of integer values. Consistency of enumeration types will allow them, and the enumerated values, to be referred to unambiguously either through symbolic name or encoding. Enumerated values are also controlled vocabularies and as such need to be standardized. Without this consistency enumeration literals can be stated differently and result in data conflicts and misinterpretations. The tags are a set of positive whole numbers, not necessarily contiguous and having no numerical significance, each corresponding to the associated literal identifier. An order attribute can also be given on the enumeration elements. An enumeration can itself be a member of an enumeration. This allows enumerations to be enumerated in a selection. Enumerations are also subclasses of _Scalar Datatype_. This allows them to be used as the reference of a datatype specification.
This class is for all enumerated and/or coded values. For example, it contains the dimension objects that are the basis elements in some abstract vector space associated with a quantity kind system. Another use is for the base dimensions for quantity systems. Each quantity kind system that defines a base set has a corresponding ordered enumeration whose elements are the dimension objects for the base quantity kinds. The order of the dimensions in the enumeration determines the canonical order of the basis elements in the corresponding abstract vector space. An enumeration is a set of literals from which a single value is selected. Each literal can have a tag as an integer within a standard encoding appropriate to the range of integer values. Consistency of enumeration types will allow them, and the enumerated values, to be referred to unambiguously either through symbolic name or encoding. Enumerated values are also controlled vocabularies and as such need to be standardized. Without this consistency enumeration literals can be stated differently and result in data conflicts and misinterpretations. The tags are a set of positive whole numbers, not necessarily contiguous and having no numerical significance, each corresponding to the associated literal identifier. An order attribute can also be given on the enumeration elements. An enumeration can itself be a member of an enumeration. This allows enumerations to be enumerated in a selection. Enumerations are also subclasses of Scalar Datatype. This allows them to be used as the reference of a datatype specification.
Scales (also called "scales of measurement" or "levels of measurement") are expressions that typically refer to the theory of scale types.
Date Time encodings are logical encodings for expressing date/time quantities as strings by applying unambiguous formatting and parsing rules.
Logarithmic units are abstract mathematical units that can be used to express any quantities (physical or mathematical) that are defined on a logarithmic scale, that is, as being proportional to the value of a logarithm function. Examples of logarithmic units include common units of information and entropy, such as the bit, and the byte, as well as units of relative signal strength magnitude such as the decibel.
National Institute of Standards and Technology (NIST) Special Publication 811 Comments on some quantities and their units
All units relating to specification of angles.
A _CGS EMU Dimension Vector_ is used to specify the dimensions for EMU C.G.S. quantity kind.
A _CGS Dimension Vector_ is used to specify the dimensions for a C.G.S. quantity kind.
A _CGS ESU Dimension Vector_ is used to specify the dimensions for ESU C.G.S. quantity kind.
A _CGS GAUSS Dimension Vector_ is used to specify the dimensions for Gaussioan C.G.S. quantity kind.
A _CGS LH Dimension Vector_ is used to specify the dimensions for Lorentz-Heaviside C.G.S. quantity kind.
A _Quantity Kind Dimension Vector_ describes the dimensionality of a quantity kind in the context of a system of units. In the SI system of units, the dimensions of a quantity kind are expressed as a product of the basic physical dimensions mass (\(M\)), length (\(L\)), time (\(T\)) current (\(I\)), amount of substance (\(N\)), luminous intensity (\(J\)) and absolute temperature (\(\theta\)) as \(dim \, Q = L^{\alpha} \, M^{\beta} \, T^{\gamma} \, I ^{\delta} \, \theta ^{\epsilon} \, N^{\eta} \, J ^{\nu}\). The rational powers of the dimensional exponents, \(\alpha, \, \beta, \, \gamma, \, \delta, \, \epsilon, \, \eta, \, \nu\), are positive, negative, or zero. For example, the dimension of the physical quantity kind \(\it{speed}\) is \(\boxed{length/time}\), \(L/T\) or \(LT^{-1}\), and the dimension of the physical quantity kind force is \(\boxed{mass \times acceleration}\) or \(\boxed{mass \times (length/time)/time}\), \(ML/T^2\) or \(MLT^{-2}\) respectively.
\(\textit{Quantity Type}\) is an enumeration of quanity kinds. It specializes \(\boxed{dtype:EnumeratedValue}\) by constrinaing \(\boxed{dtype:value}\) to instances of \(\boxed{qudt:QuantityKind}\).
Scalar data types are those that have a single value. The permissible values are defined over a domain that may be integers, float, character or boolean. Often a scalar data type is referred to as a primitive data type.
A data type is a definition of a set of values (for example, "all integers between 0 and 10"), and the allowable operations on those values; the meaning of the data; and the way values of that type can be stored. Some types are primitive - built-in to the language, with no visible internal structure - e.g. Boolean; others are composite - constructed from one or more other types (of either kind) - e.g. lists, arrays, structures, unions. Object-oriented programming extends this with classes which encapsulate both the structure of a type and the operations that can be performed on it. Some languages provide strong typing, others allow implicit type conversion and/or explicit type conversion.
The solid angle subtended by a surface S is defined as the surface area of a unit sphere covered by the surface S's projection onto the sphere. A solid angle is related to the surface of a sphere in the same way an ordinary angle is related to the circumference of a circle. Since the total surface area of the unit sphere is 4*pi, the measure of solid angle will always be between 0 and 4*pi.
A "Structured Datatype", in contrast to scalar data types, is used to characterize classes of more complex data structures, such as linked or indexed lists, trees, ordered trees, and multi-dimensional file formats.
Lexical pattern for the case-insensitive version of UCUM code
Lexical pattern for the terminal symbols in the case-insensitive version of UCUM code
A "Encoding" with the following instance(s): "UTF-16 String", "UTF-8 Encoding".
This property relates a unit of measure with a unit system that does not define the unit, but allows its use within the system. An allowed unit must be convertible to some dimensionally eqiuvalent unit that is defined by the system.
This property relates a unit of measure with a unit system that may or may not define the unit, but within which the unit is compatible.
This property relates a unit of measure with a system of units that either a) defines the unit or b) allows the unit to be used within the system.
This property relates a unit system with a unit of measure that is not defined by or part of the system, but is allowed for use within the system. An allowed unit must be convertible to some dimensionally equivalent unit that is defined by the system.
A system of quantity kinds is a set of one or more quantity kinds together with a set of zero or more algebraic equations that define relationships between quantity kinds in the set. In the physical sciences, the equations relating quantity kinds are typically physical laws and definitional relations, and constants of proportionality. Examples include Newton’s First Law of Motion, Coulomb’s Law, and the definition of velocity as the instantaneous change in position. In almost all cases, the system identifies a subset of base quantity kinds. The base set is chosen so that all other quantity kinds of interest can be derived from the base quantity kinds and the algebraic equations. If the unit system is explicitly associated with a quantity kind system, then the unit system must define at least one unit for each quantity kind. From a scientific point of view, the division of quantities into base quantities and derived quantities is a matter of convention.
Used to provide an annotation for an informative reference.
A plain text description is used to provide a description with only simple ASCII characters for cases where LaTeX , HTML or other markup would not be appropriate.
A code is a string that uniquely identifies a QUDT concept. The use of this property has been deprecated.
A system of units is coherent with respect to a system of quantities and equations if the system of units is chosen in such a way that the equations between numerical values have exactly the same form (including the numerical factors) as the corresponding equations between the quantities. In such a coherent system, no numerical factor other than the number 1 ever occurs in the expressions for the derived units in terms of the base units. For example, the \(newton\) and the \(joule\). These two are, respectively, the force that causes one kilogram to be accelerated at 1 metre per (1) second per (1) second, and the work done by 1 newton acting over 1 metre. Being coherent refers to this consistent use of 1. In the old c.g.s. system , with its base units the centimetre and the gram, the corresponding coherent units were the dyne and the erg, respectively the force that causes 1 gram to be accelerated at 1 centimetre per (1) second per (1) second, and the work done by 1 dyne acting over 1 centimetre. So \(1\,newton = 10^5 dyne\), \(1 joule = 10^7 erg\), making each of the four compatible in a decimal sense within its respective other system, but not coherent therein.
Alphabetic Currency Code as defined by ISO 4217. For example, US Dollar has the code 'USD'.
The currency exponent indicates the number of decimal places between a major currency unit and its minor currency unit. For example, the US dollar is the major currency unit of the United States, and the US cent is the minor currency unit. Since one cent is 1/100 of a dollar, the US dollar has a currency exponent of 2. However, the Japanese Yen has no minor currency units, so the yen has a currency exponent of 0.
Numeric currency Code as defined by ISO 4217. For example, US Dollar has the number 840.
A field code is a generic property for representing unique codes that make up other identifers. For example each QuantityKind class caries a domain code as its field code.
has quantity kind dimension vector denominator part
A coherent unit of measurement for a unit system is a defined unit that may be expressed as a product of powers of the system's base units with the proportionality factor of one.
This property relates a unit system with a unit of measure that is defined by the system.
A coherent unit of measurement for a unit system is a defined unit that may be expressed as a product of powers of the system's base units with the proportionality factor of one. A system of units is coherent with respect to a system of quantities and equations if the system of units is chosen in such a way that the equations between numerical values have exactly the same form (including the numerical factors) as the corresponding equations between the quantities. For example, the 'newton' and the 'joule'. These two are, respectively, the force that causes one kilogram to be accelerated at 1 metre per second per second, and the work done by 1 newton acting over 1 metre. Being coherent refers to this consistent use of 1. In the old c.g.s. system , with its base units the centimetre and the gram, the corresponding coherent units were the dyne and the erg, respectively the force that causes 1 gram to be accelerated at 1 centimetre per second per second, and the work done by 1 dyne acting over 1 centimetre. So \(1 newton = 10^5\,dyne\), \(1 joule = 10^7\,erg\), making each of the four compatible in a decimal sense within its respective other system, but not coherent therein.
has quantity kind dimension vector numerator part
A quantity is the measurement of an observable property of a particular object, event, or physical system. A quantity is always associated with the context of measurement (i.e. the thing measured, the measured value, the accuracy of measurement, etc.) whereas the underlying quantity kind is independent of any particular measurement. Thus, length is a quantity kind while the height of a rocket is a specific quantity of length; its magnitude that may be expressed in meters, feet, inches, etc. Examples of physical quantities include physical constants, such as the speed of light in a vacuum, Planck's constant, the electric permittivity of free space, and the fine structure constant. In other words, quantities are quantifiable aspects of the world, such as the duration of a movie, the distance between two points, velocity of a car, the pressure of the atmosphere, and a person's weight; and units are used to describe their numerical measure. Many quantity kinds are related to each other by various physical laws, and as a result, the associated units of some quantity kinds can be expressed as products (or ratios) of powers of other quantity kinds (e.g., momentum is mass times velocity and velocity is defined as distance divided by time). In this way, some quantities can be calculated from other measured quantities using their associations to the quantity kinds in these expressions. These quantity kind relationships are also discussed in dimensional analysis. Those that cannot be so expressed can be regarded as "fundamental" in this sense. A quantity is distinguished from a "quantity kind" in that the former carries a value and the latter is a type specifier.
Used to relate a class to one or more graphs where vocabularies for the class are defined.
A negative change limit between consecutive sample values for a parameter. The Negative Delta may be the encoded value or engineering units value depending on whether or not a Calibrator is defined.
A positive change limit between consecutive sample values for a parameter. The Positive Delta may be the encoded value or engineering units value depending on whether or not a Calibrator is defined.
Associates a unit with the appropriate prefix, if any.
a property to relate an observable thing with a quantity (qud:Quantity)
This property is used for qudt:Discipline instances to identify the Unit instances that are used within a given discipline.
_ucumCode_ associates a QUDT unit with a UCUM case-insensitive code.
_ucumCode_ associates a QUDT unit with its UCUM code (case-sensitive). In SHACL the values are derived from specific ucum properties using 'sh:values'.
_ucumCode_ associates a QUDT unit with with a UCUM case-sensitive code.
A datatype that is the union of numeric xsd data types. "numericUnion" is equivalent to the xsd specification that uses an xsd:union of memberTypes="xsd:decimal xsd:double xsd:float xsd:integer".
A bit encoding is a correspondence between the two possible values of a bit, 0 or 1, and some interpretation. For example, in a boolean encoding, a bit denotes a truth value, where 0 corresponds to False and 1 corresponds to True.
An encoding is a rule or algorithm that is used to convert data from a native, or unspecified form into a specific form that satisfies the encoding rules. Examples of encodings include character encodings, such as UTF-8.
This class contains the various ways that information may be encoded into bytes.
A set of numbers is called countably infinite if there is a way to enumerate them. Formally this is done with a bijection function that associates each number in the set with exactly one of the positive integers. The set of all fractions is also countably infinite. In other words, any set \(X\) that has the same cardinality as the set of the natural numbers, or \(| X | \; = \; | \mathbb N | \; = \; \aleph0\), is said to be a countably infinite set.
Any set \(X\) with cardinality less than that of the natural numbers, or \(| X | \\; < \; | \\mathbb N | \), is said to be a finite set.
The class of all character encoding schemes, each of which defines a rule or algorithm for encoding character data as a sequence of bits or bytes.
An aspect class that holds properties that provide external knowledge and specifications of a given resource.
A "Encoding" with the following instance(s): "Double Precision Encoding", "Single Precision Real Encoding".
Describes how a data or information structure is ordered.
A physical constant is a physical quantity that is generally believed to be both universal in nature and constant in time. It can be contrasted with a mathematical constant, which is a fixed numerical value but does not directly involve any physical measurement. There are many physical constants in science, some of the most widely recognized being the speed of light in vacuum c, Newton's gravitational constant G, Planck's constant h, the electric permittivity of free space ε0, and the elementary charge e. Physical constants can take many dimensional forms, or may be dimensionless depending on the system of quantities and units used.
The symbol is a glyph that is used to represent some concept, typically a unit or a quantity, in a compact form. For example, the symbol for an Ohm is \(ohm\). This contrasts with 'unit:abbreviation', which gives a short alphanumeric abbreviation for the unit, 'ohm' for Ohm.
The 'qudt:example' property is used to annotate an instance of a class with a reference to a concept that is an example. The type of this property is 'rdf:Property'. This allows both scalar and object ranges.
Specifics whether a value should be signed or unsigned.
Scales, or scales of measurement (or categorization) provide ways of quantifying measurements, values and other enumerated values according to a normative frame of reference. Four different types of scales are typically used. These are interval, nominal, ordinal and ratio scales.
This property relates a unit of measure to the system of units in which it is defined as a base unit for the system. The base units of a system are used to define the derived units of the system by expressing the derived units as products of the base units raised to a rational power.
This property relates a system of units to a base unit defined within the system. The base units of a system are used to define the derived units of the system by expressing the derived units as products of the base units raised to a rational power.
Byte order is an enumeration of two values: 'Big Endian' and 'Little Endian' and is used to denote whether the most significant byte is either first or last, respectively.
Datatype name in the C programming language
This property relates a unit of measure with the unit system that defines the unit.
This property relates a unit of measure to the unit system in which the unit is derived from the system's base units with a proportionality constant of one.
This property relates a unit of measure to the system of units in which it is defined as a derived unit. That is, the derived unit is defined as a product of the base units for the system raised to some rational power.
This property relates a unit of measure to the unit system in which the unit is derived from the system's base units without proportionality constant of one.
A system of units is a set of units which are chosen as the reference scales for some set of quantity kinds together with the definitions of each unit. Units may be defined by experimental observation or by proportion to another unit not included in the system. If the unit system is explicitly associated with a quantity kind system, then the unit system must define at least one unit for each quantity kind.
dimension exponent for amount of substance
dimension exponent for luminous intensity
dimension exponent for thermodynamic temperature
This property relates a system of units to a unit of measure that is defined within the system in terms of the base units for the system. That is, the derived unit is defined as a product of the base units for the system raised to some rational power.
This property is used to identify a Quantity instance that is a measure of a change, or interval, of some property, rather than a measure of its absolute value. This is important for measurements such as temperature differences where the conversion among units would be calculated differently because of offsets.
OLE DB (Object Linking and Embedding, Database, sometimes written as OLEDB or OLE-DB), an API designed by Microsoft, allows accessing data from a variety of sources in a uniform manner. The API provides a set of interfaces implemented using the Component Object Model (COM); it is otherwise unrelated to OLE.
This property relates a quantity kind to its specialization(s). For example, linear velocity and angular velocity are both specializations of velocity.
This property relates a quantity kind to its generalization. A quantity kind, PARENT, is a generalization of the quantity kind CHILD only if: 1. PARENT and CHILD have the same dimensions in every system of quantities; 2. Every unit that is a measure of quantities of kind CHILD is also a valid measure of quantities of kind PARENT.
The UDUNITS package supports units of physical quantities. Its C library provides for arithmetic manipulation of units and for conversion of numeric values between compatible units. The package contains an extensive unit database, which is in XML format and user-extendable. The package also contains a command-line utility for investigating units and converting values.
The UN/CEFACT Recommendation 20 provides three character alphabetic and alphanumeric codes for representing units of measurement for length, area, volume/capacity, mass (weight), time, and other quantities used in international trade. The codes are intended for use in manual and/or automated systems for the exchange of information between participants in international trade.
A reference to the unit of measure of a quantity (variable or constant) of interest.
A property to relate an observable thing with a value of any kind
Quantities, Units, Dimensions and Types (QUDT) Schema - Version 2.1.27
Specifies the schema for quantities, units and dimensions. Types are defined in other schemas.
This product includes all or a portion of the UCUM table, UCUM codes, and UCUM definitions or is derived from it, subject to a license from Regenstrief Institute, Inc. and The UCUM Organization. Your use of the UCUM table, UCUM codes, UCUM definitions also is subject to this license, a copy of which is available at http://unitsofmeasure.org. The current complete UCUM table, UCUM Specification are available for download at ​http://unitsofmeasure.org. The UCUM table and UCUM codes are copyright © 1995-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. THE UCUM TABLE (IN ALL FORMATS), UCUM DEFINITIONS, AND SPECIFICATION ARE PROVIDED 'AS IS.' ANY EXPRESS OR IMPLIED WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
The QUDT, or "Quantity, Unit, Dimension and Type" schema defines the base classes properties, and restrictions used for modeling physical quantities, units of measure, and their dimensions in various measurement systems. The goal of the QUDT ontology is to provide a unified model of, measurable quantities, units for measuring different kinds of quantities, the numerical values of quantities in different units of measure and the data structures and data types used to store and manipulate these objects in software. Except for unit prefixes, all units are specified in separate vocabularies. Descriptions are provided in both HTML and LaTeX formats. A quantity is a measure of an observable phenomenon, that, when associated with something, becomes a property of that thing; a particular object, event, or physical system. A quantity has meaning in the context of a measurement (i.e. the thing measured, the measured value, the accuracy of measurement, etc.) whereas the underlying quantity kind is independent of any particular measurement. Thus, length is a quantity kind while the height of a rocket is a specific quantity of length; its magnitude that may be expressed in meters, feet, inches, etc. Or, as stated at Wikipedia, in the language of measurement, quantities are quantifiable aspects of the world, such as time, distance, velocity, mass, momentum, energy, and weight, and units are used to describe their measure. Many of these quantities are related to each other by various physical laws, and as a result the units of some of the quantities can be expressed as products (or ratios) of powers of other units (e.g., momentum is mass times velocity and velocity is measured in distance divided by time).
The QUDT Ontologies are issued under a Creative Commons Attribution 4.0 International License (CC BY 4.0), available at https://creativecommons.org/licenses/by/4.0/. Attribution should be made to QUDT.org
QUDT is a non-profit organization that governs the QUDT ontologies.
_Data Encoding_ expresses the properties that specify how data is represented at the bit and byte level. These properties are applicable to describing raw data.
An aspect is an abstract type class that defines properties that can be reused.
A type of string in which some characters may be wrapped with '\(' and '\) characters for LaTeX rendering.
_Quantifiable_ ascribes to some thing the capability of being measured, observed, or counted.
The standard uncertainty of a quantity is the estimated standard deviation of the mean taken from a series of measurements.
The relative standard uncertainty of a measurement is the (absolute) standard uncertainty divided by the magnitude of the exact value.
This property relates a system of units with a unit of measure that is either a) defined by the system, or b) accepted for use by the system and is convertible to a unit of equivalent dimension that is defined by the system. Systems of units may distinguish between base and derived units. Base units are the units which measure the base quantities for the corresponding system of quantities. The base units are used to define units for all other quantities as products of powers of the base units. Such units are called derived units for the system.
This property associates a system of quantities with an enumeration that enumerates the base dimensions of the system in canonical order.
Lexical pattern for the case-sensitive version of UCUM code
Lexical pattern for the terminal symbols in the case-sensitive version of UCUM code
An 'expression' is a finite combination of symbols that are well-formed according to rules that apply to units of measure, quantity kinds and their dimensions.
The "qudt:id" is an identifier string that uniquely identifies a QUDT concept. The identifier is constructed using a prefix. For example, units are coded using the pattern: "UCCCENNNN", where "CCC" is a numeric code or a category and "NNNN" is a digit string for a member element of that category. For scaled units there may be an addition field that has the format "QNN" where "NN" is a digit string representing an exponent power, and "Q" is a qualifier that indicates with the code "P" that the power is a positive decimal exponent, or the code "N" for a negative decimal exponent, or the code "B" for binary positive exponents.
Provides a way to reference the ISO unit definition.
Provides a way to reference information that is an authoritative source providing a standard definition
The interval type allows for the degree of difference between items, but not the ratio between them. Examples include temperature with the Celsius scale, which has two defined points (the freezing and boiling point of water at specific conditions) and then separated into 100 intervals, date when measured from an arbitrary epoch (such as AD), percentage such as a percentage return on a stock,[16] location in Cartesian coordinates, and direction measured in degrees from true or magnetic north. Ratios are not meaningful since 20 °C cannot be said to be "twice as hot" as 10 °C, nor can multiplication/division be carried out between any two dates directly. However, ratios of differences can be expressed; for example, one difference can be twice another. Interval type variables are sometimes also called "scaled variables", but the formal mathematical term is an affine space (in this case an affine line). Characteristics: median, percentile & Monotonic increasing (order (<) & totally ordered set
A nominal scale differentiates between items or subjects based only on their names or (meta-)categories and other qualitative classifications they belong to; thus dichotomous data involves the construction of classifications as well as the classification of items. Discovery of an exception to a classification can be viewed as progress. Numbers may be used to represent the variables but the numbers do not have numerical value or relationship: For example, a Globally unique identifier. Examples of these classifications include gender, nationality, ethnicity, language, genre, style, biological species, and form. In a university one could also use hall of affiliation as an example.
The ordinal type allows for rank order (1st, 2nd, 3rd, etc.) by which data can be sorted, but still does not allow for relative degree of difference between them. Examples include, on one hand, dichotomous data with dichotomous (or dichotomized) values such as 'sick' vs. 'healthy' when measuring health, 'guilty' vs. 'innocent' when making judgments in courts, 'wrong/false' vs. 'right/true' when measuring truth value, and, on the other hand, non-dichotomous data consisting of a spectrum of values, such as 'completely agree', 'mostly agree', 'mostly disagree', 'completely disagree' when measuring opinion.
The ratio type takes its name from the fact that measurement is the estimation of the ratio between a magnitude of a continuous quantity and a unit magnitude of the same kind (Michell, 1997, 1999). A ratio scale possesses a meaningful (unique and non-arbitrary) zero value. Most measurement in the physical sciences and engineering is done on ratio scales. Examples include mass, length, duration, plane angle, energy and electric charge. In contrast to interval scales, ratios are now meaningful because having a non-arbitrary zero point makes it meaningful to say, for example, that one object has "twice the length" of another (= is "twice as long"). Very informally, many ratio scales can be described as specifying "how much" of something (i.e. an amount or magnitude) or "how many" (a count). The Kelvin temperature scale is a ratio scale because it has a unique, non-arbitrary zero point called absolute zero.
An abbreviation for a unit is a short ASCII string that is used in place of the full name for the unit in contexts where non-ASCII characters would be problematic, or where using the abbreviation will enhance readability. When a power of abase unit needs to be expressed, such as squares this can be done using abbreviations rather than symbols. For example, _sq ft_ means _square foot_, and _cu ft_ means _cubic foot_.
Barry Smith and Pierre Grenon: "The Cornucopia of Formal Ontological Relations"
Barry Smith: "Basic Tools of Formal Ontology"
Barry Smith: "Beyond Concepts: Ontology as Reality Representation"
Pierre Grenon and Barry Smith: "SNAP and SPAN: Towards Geospatial Dynamics"
Pierre Grenon, Barry Smith and Louis Goldberg: "Biodynamic Ontology: Applying BFO in the Biomedical Domain"
Pierre Grenon: "BFO in a Nutshell: A Bi-categorial Axiomatization of BFO and Comparison with DOLCE"
Pierre Grenon: "Nuts in BFO's Nutshell: Revisions to the Bi-categorial Axiomatization of BFO"
Pierre Grenon: "Spatio-temporality in Basic Formal Ontology: SNAP and SPAN, Upper-Level Ontology, and Framework for Formalization"
Institute for Formal Ontology and Medical Information Science (IFOMIS)
An entity that exists in full at any time in which it exists at all, persists through time while maintaining its identity and has no temporal parts.
the lawn and atmosphere in front of our building
An entity that has temporal parts and that happens, unfolds or develops through time. Sometimes also called perdurants.
the most interesting part of Van Gogh's life
a surgical operation as processual context for a nosocomical infection
the spatiotemporal context occupied by a process of cellular meiosis
the spatiotemporal region occupied by the development of a cancer tumor
A realizable entity that essentially causes a specific process or transformation in the object in which it inheres, under specific circumstances and in conjunction with the laws of nature. A general formula for dispositions is: X (object has the disposition D to (transform, initiate a process) R under conditions C.
the disposition of a patient with a weakened immune system to contract disease
the disposition of a vase to brake if dropped
the disposition of metal to conduct electricity
the disposition of vegetables to decay when not refrigerated
If a realizable entity inheres in a continuant , this does not imply that it is actually realized.
A specifically dependent continuant that inheres in continuant entities and are not exhibited in full at every time in which it inheres in an entity or group of entities. The exhibition or actualization of a realizable entity is a particular manifestation, functioning or process that occurs under certain circumstances.
A realizable entity the manifestation of which is an essentially end-directed activity of a continuant entity in virtue of that continuant entity being a specific kind of entity in the kind or kinds of contexts that it is made for.
the digestive function of the stomach to nutriate the body
the function of a birth canal to enable transport
the function of a computer program to compute mathematical equations
the function of a hammer to drive in nails
the function of a judge in a court of law
the function of an automobile to provide transportation
the function of reproduction in the transmission of genetic material
the function of the heart in the body: to pump blood, to receive de-oxygenated and oxygenated blood, etc.
A realizable entity the manifestation of which brings about some result or end that is not essential to a continuant in virtue of the kind of thing that it is but that can be served or participated in by that kind of continuant in some kinds of natural, social or institutional contexts.
the role of a biological grandfather as legal guardian in the context of asystem of laws
the role of a chemical compound in an experiment
the role of a patient relative as defined by a hospital administrative form
the role of a woman as a legal mother in the context of system of laws
the role of ingested matter in digestion
A continuant that is dependent on one or other independent continuant bearers. For every instance of A requires some instance of (an independent continuant type) B but which instance of B serves can change from time to time.
a certain PDF file that exists in different and in several hard drives
A continuant that is either dependent on one or other independent continuant bearers or inheres in or is borne by other entities.
A continuant that inheres in or is borne by other entities. Every instance of A requires some specific instance of B which must always be the same.
A specifically dependent continuant that is exhibited if it inheres in an entity or entities at all (a categorical property).
A space time region that has spatial and temporal dimensions and every spatial and temporal point of which is not connected with every other spatial and temporal point of which.
the space and time occupied by the individual games of the World Cup
the space and time occupied by the individual liaisons in a romantic affair
All instances of occurrent are spatiotemporal entities, that is, they enter in the relation of (spatiotemporal) location with spatiotemporal region entities. As a particular case, the exact spatiotemporal location of a spatiotemporal region is this region itself.
An instance of the spatiotemporal region is a part of spacetime. All parts of spacetime are spatiotemporal region entities and only spatiotemporal region entities are parts of spacetime. In particular, neither spatial region entities nor temporal region entities are in BFO parts of spacetime. Spacetime is the entire extent of the spatiotemporal universe, a designated individual, which is thus itself a spatiotemporal region . Spacetime is among occurrents the analogous of space among continuant entities.
Spacetime and spatiotemporal region entities are entities in their own rights which exist independently of any entities which can be located at them. This view of spacetime can be called "absolutist" or "the container view". In BFO, the class processual context allows for a so-called relational view of spacetime, that is to say, a view according to which spatiotemporality is a matter of relative location between entities and not a matter of being tied to spacetime. In BFO, the bridge between these two views is secured through the fact that instances of processual context are too spatiotemporal entities.
An occurrent at or in which processual entity entities can be located.
the spatiotemporal region occupied by a human life
Union of SpatiotemporalInstant & SpatiotemporalInterval
A space time region that has temporal and spatial dimensions such that all points within the spatiotemporal region are mediately or immediately connected to all other points within the same space time region .
the spatial and temporal location of an individual organism's life
the spatial and temporal location of the development of a fetus
A temporal region every point of which is not mediately or immediately connected with every other point of which.
the time occupied by the individual games of the World Cup
the time occupied by the individual liaisons in a romantic affair
All instances of occurrent are temporal entities, that is, they enter in the relation of (temporal) location with temporal region entities. As a particular case, the exact spatiotemporal location of a temporal region is this region itself. Continuant entities are not temporal entities in the technical sense just explained; they are related to time in a different way, not through temporal location but through a relation of existence at a time or during a period of time (see continuant .
An instance of temporal region is a part of time. All parts of time are temporal region entities and only temporal region entities are parts of time. Time is the entire extent of the temporal universe, a designated individual, which is thus a temporal region itself.
Time and temporal region entities are entities in their own rights which exist independently of any entities which can be located at them. This view of time can be called "absolutist" or "the container view" in analogy to what is traditionally the case with space (see spatial region .
An occurrent that is part of time.
A temporal region every point of which is mediately or immediately connected with every other point of which.
the time from the beginning to the end of a heart attack
A connected space time region at a specific moment.
the space time region occupied by a single instantaneous temporalslice (part) of a process
A connected space time region that endures for more than a single moment of time.
the space time region occupied by a process or by a fiat processual part
A connected temporal region comprising a single moment of time.
the moment at which a finger is detached in an industrial accident
A connected temporal region lasting for more than a single moment of time.
any continuous temporal duration during which a process occurs
A spatial region with one dimension.
the part of space that is a line stretching from one end of absolute spaceto the other
All instances of continuant are spatial entities, that is, they enter in the relation of (spatial) location with spatial region entities. As a particular case, the exact spatial location of a spatial region is this region itself.
An instance of spatial region is a part of space. All parts of space are spatial region entities and only spatial region entities are parts of space. Space is the entire extent of the spatial universe, a designated individual, which is thus itself a spatial region .
Space and spatial region entities are entities in their own rights which exist independently of any entities which can be located at them. This view of space is sometimes called "absolutist" or "the container view". In BFO, the class site allows for a so-called relational view of space, that is to say, a view according to which spatiality is a matter of relative location between entities and not a matter of being tied to space. The bridge between these two views is secured through the fact that while instances of site are not spatial region entities, they are nevertheless spatial entities.
A continuant that is neither bearer of quality entities nor inheres in any other entities.
parts of the sum total of all space in the universe
the sum total of all space in the universe
A spatial region with three dimensions.
A spatial region with two dimensions.
the surface of a cube-shaped part of space
the surface of a rectilinear planar figure-shaped part of space
the surface of a sphere-shaped part of space
A spatial region with no dimensions.
A continuant that is a bearer of quality and realizable entity entities, in which other entities inhere and which itself cannot inhere in anything.
the bottom right portion of a human torso
An independent continuant that is part of an object but is not demarcated by any physical discontinuities.
the dorsal and ventral surfaces of the body
the lower right portion of a human torso
the upper and lower lobes of the left lung
An independent continuant that is spatially extended, maximally self-connected and self-contained (the parts of a substance are not separated from each other by spatial gaps) and possesses an internal unity. The identity of substantial object entities is independent of that of other entities and can be maintained through time.
An independent continuant that is a mereological sum of separate object entities and possesses non-connected boundaries.
Boundaries are theoretically difficult entities to account for, however the intuitive notion of a physical boundary as a surface of some sort (whether inside or outside of a thing) will generally serve as a good guide for the use of this universal.
An independent continuant that is a lower dimensional part of a spatial entity, normally a closed two-dimensional surface. Boundaries are those privileged parts of object entities that exist at exactly the point where the object is separated off from the rest of the existing entities in the world.
the outer surface of a cell or cell wall
the surface of the interior of the stomach
An instance of Site is a mixture of independent continuant entities which act as surrounding environments for other independent continuant entities, most importantly for instances of object . A site is typically made of object or fiat object part entities and a surrounding medium in which is found an object occupying the site . Independent continuant entities may be associated with others (which, then, are sites) through a relation of "occupation". That relation is connected to, but distinct from, the relation of spatial location. Site entities are not to be confused with spatial region entities. In BFO, site allows for a so-called relational view of space which is different from the view corresponding to the class spatial region (see the comment on this class).
An independent continuant consisting of a characteristic spatial shape in relation to some arrangement of other continuant entities and of the medium which is enclosed in whole or in part by this characteristic spatial shape. Site entities are entities that can be occupied by other continuant entities.
Maria's nostril or her intestines for a variety of bacteria
a particular room in a particular hospital
A processual entity that is part of a process but that does not have bona fide beginnings and endings corresponding to real discontinuities.
An occurrent that exists in time by occurring or happening, has temporal parts and always involves and depends on some entity.
A processual entity that is a maximally connected spatiotemporal whole and has bona fide beginnings and endings corresponding to real discontinuities.
A processual entity that is a mereological sum of process entities and possesses non-connected boundaries.
a process of digestion and a process of thinking taken together
the beating of the hearts of each of seven individuals in the room
the playing of each of the members of an orchestra
A processual entity that is the fiat or bona fide instantaneous temporal process boundary.
the detaching of a finger in an industrial accident
the final separation of two cells at the end of cell-division
the incision at the beginning of a surgery
An instance of a processual context is a mixture of processual entity which stand as surrounding environments for other processual entity entities. The class processual context is the analogous among occurrent entities to the class site among continuant entities.
The processual context for a given manipulation occurring as part of an experiment is made of processual entities which occur in parallel, are not necessarily all parts of the experiment themselves and may involve continuant entities which are in the spatial vicinity of the participants in the experiment.
An occurrent consisting of a characteristic spatial shape inhering in some arrangement of other occurrent entities. processual context entities are characteristically entities at or in which other occurrent entities can be located or occur.
1.1 2026-04 simplified imports 1.0 First version
SHACL validator for the Australian Biodiveristy Information Standard, ABIS
Checks the Observation Sollection's members
Each Observation Collection must have at least one Observation indicated via sosa:member
ObservationCollection's Observations property
EDES Coarse Woody Debris Protocol Shapes Graph
TERN's ecologists have determined the feature type is _dead wood_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/a8b1a7fb-b479-48ff-b706-b3cc4691710b[`dead wood`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/fa986148-e44a-4cd3-8ac3-17748eb013f3>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Coarse Woody Debris decay classes controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Coarse Woody Debris decay classes controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/fa986148-e44a-4cd3-8ac3-17748eb013f3> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'b5180d8a-75b6-4bca-9413-0e507e910387'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/fa986148-e44a-4cd3-8ac3-17748eb013f3> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
Observations following the Coarse Woody Debris Module are made in the context of a site visit.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/fa986148-e44a-4cd3-8ac3-17748eb013f3>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/0d8b47b4-1ca8-4c76-8329-0eb781a823a2>`. `<https://linked.data.gov.au/def/nrm/0d8b47b4-1ca8-4c76-8329-0eb781a823a2>` is the IRI for "Coarse Woody Debris Module".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/0d8b47b4-1ca8-4c76-8329-0eb781a823a2`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/fa986148-e44a-4cd3-8ac3-17748eb013f3>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/b5180d8a-75b6-4bca-9413-0e507e910387>`. `<https://linked.data.gov.au/def/nrm/b5180d8a-75b6-4bca-9413-0e507e910387>` is the IRI for "Coarse Woody Debris decay classes".
The value of `tern:vocabulary` _MUST_ match the pattern `b5180d8a-75b6-4bca-9413-0e507e910387$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b15f883b-c2e7-408e-8146-3754bbd5693f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b15f883b-c2e7-408e-8146-3754bbd5693f>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/b15f883b-c2e7-408e-8146-3754bbd5693f> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b15f883b-c2e7-408e-8146-3754bbd5693f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
The result _MUST_ have a value greater than or equal to 0.1.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e73af424-f20d-49b8-81e3-cd30afb5b267>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e73af424-f20d-49b8-81e3-cd30afb5b267>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/e73af424-f20d-49b8-81e3-cd30afb5b267> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e73af424-f20d-49b8-81e3-cd30afb5b267>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
The result _MUST_ have a value greater than or equal to 5.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ee4d10cb-4245-496c-a72c-0696e2014f90>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ee4d10cb-4245-496c-a72c-0696e2014f90>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/ee4d10cb-4245-496c-a72c-0696e2014f90> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ee4d10cb-4245-496c-a72c-0696e2014f90>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
The result _MUST_ have a value greater than or equal to 10.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/00c4a64a-0411-533d-a742-7f08232c24b7> ; sosa:hasResult ?this . }
TERN's ecologists have determined the feature type is _tree stump_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/9f0ed180-2b85-4efa-b09f-9e20caf1d069[`tree stump`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/00c4a64a-0411-533d-a742-7f08232c24b7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/00c4a64a-0411-533d-a742-7f08232c24b7> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/00c4a64a-0411-533d-a742-7f08232c24b7>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/00c4a64a-0411-533d-a742-7f08232c24b7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/9e087f2d-7bdb-4043-98c1-dd663431ec37>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/9e087f2d-7bdb-4043-98c1-dd663431ec37> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/9e087f2d-7bdb-4043-98c1-dd663431ec37> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/9e087f2d-7bdb-4043-98c1-dd663431ec37>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/9e087f2d-7bdb-4043-98c1-dd663431ec37>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c4c43448-bc52-47d4-bd1a-0d3faeeb61f1>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c4c43448-bc52-47d4-bd1a-0d3faeeb61f1>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/c4c43448-bc52-47d4-bd1a-0d3faeeb61f1> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c4c43448-bc52-47d4-bd1a-0d3faeeb61f1>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
The result _MUST_ have a value greater than or equal to 2.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/aea144cc-7a52-4718-a5b1-58a8edc57ffb>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/aea144cc-7a52-4718-a5b1-58a8edc57ffb>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/aea144cc-7a52-4718-a5b1-58a8edc57ffb> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/aea144cc-7a52-4718-a5b1-58a8edc57ffb>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PAV supplies terms for distinguishing between the different roles of the agents contributing content in current web based systems: contributors, authors, curators and digital artifact creators. The ontology also provides terms for tracking provenance of digital entities that are published on the web and then accessed, transformed and consumed. In order to support broader interoperability, PAV specializes the general purpose W3C PROV provenance model (PROV-O). PAV distinguishes between the data related to the digital artifact - named Provenance - and those related to the actual knowledge creation and therefore to the intellectual property aspects – named Authoring. The Versioning axis describes the evolution of digital entities in time. Using PAV, descriptions can define the authors that originate or gave existence to the work that is expressed in the digital resource (pav:authoredBy); curators (pav:curatedBy) who are content specialists responsible for shaping the expression in an appropriate format, and contributors (super-property pav:contributedBy) that provided some help in conceiving the resource or in the expressed knowledge creation/extraction. These provenance aspects can be detailed with dates using pav:curatedOn, pav:authoredOn, etc. Further details about the creation activities, such as different authors contributing specific parts of the resource at different dates are out of scope for PAV and should be defined using vocabularies like PROV-O and additional intermediate entities to describe the different states. For resources based on other resources, PAV allows specification of direct retrieval (pav:retrievedFrom), import through transformations (pav:importedFrom) and sources that were merely consulted (pav:sourceAccessedAt). These aspects can also define the agents responsible using pav:retrievedBy, pav:importedBy and pav:sourceAccessedBy. Version number of a resource can be given with pav:version, the previous version of the resource with pav:previousVersion, and any other earlier versions with pav:hasEarlierVersion. Unversioned, 'mutable' resources can specify their current version as a snapshot resource using pav:hasCurrentVersion and list the earlier versions using pav:hasVersion. The creation of the digital representation (e.g. an RDF graph or a .docx file) can in many cases be different from the authorship of the content/knowledge, and in PAV this digital creation is specified using pav:createdBy, pav:createdWith and pav:createdOn. PAV specializes terms from W3C PROV-O (prov:) and DC Terms (dcterms:), however these ontologies are not OWL imported as PAV can be used independently. The "is defined by" links indicate where those terms are included from. See http://www.w3.org/TR/prov-o and http://dublincore.org/documents/2012/06/14/dcmi-terms/ for more details. See http://purl.org/pav/mapping/dcterms For a comprehensive SKOS mapping to DC Terms. PAV 2 is based on PAV 1.2 but in a different namespace ( http://purl.org/pav/ ). Terms compatible with 1.2 are indicated in this ontology using owl:equivalentProperty. The ontology IRI http://purl.org/pav/ always resolve to the latest version of PAV 2. Particular versionIRIs such as http://purl.org/pav/2.1 can be used by clients to force imports of a particular version - note however that all terms are defined directly in the http://purl.org/pav/ namespace. The goal of PAV is to provide a lightweight, straight forward way to give the essential information about authorship, provenance and versioning, and therefore these properties are described directly on the published resource. As such, PAV does not define any classes or restrict domain/ranges, as all properties are applicable to any online resource. -- Copyright 2008-2014 Massachusetts General Hospital; Harvard Medical School; Balboa Systems; University of Manchester Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
PAV is a lightweight ontology for tracking Provenance, Authoring and Versioning. PAV specializes the W3C provenance ontology PROV-O in order to describe authorship, curation and digital creation of online resources. This ontology describes the defined PAV properties and their usage. Note that PAV does not define any explicit classes or domain/ranges, as every property is meant to be used directly on the described online resource. Cite as: Paolo Ciccarese, Stian Soiland-Reyes, Khalid Belhajjame, Alasdair JG Gray, Carole Goble, Tim Clark (2013): PAV ontology: provenance, authoring and versioning. Journal of biomedical semantics 4 (1), 37. doi:10.1186/2041-1480-4-37
PAV - Provenance, Authoring and Versioning
The software/tool used by the creator (pav:createdBy) when making the digital resource, for instance a word processor or an annotation tool. A more independent software agent that creates the resource without direct interaction by a human creator should instead should instead by indicated using pav:createdBy.
An agent primary responsible for making the digital artifact or resource representation. This property is distinct from forming the content, which is indicated with pav:contributedBy or its subproperties; pav:authoredBy, which identifies who authored the knowledge expressed by this resource; and pav:curatedBy, which identifies who curated the knowledge into its current form. pav:createdBy is more specific than its superproperty dct:creator - which might or might not be interpreted to cover this creator. For instance, the author wrote 'this species has bigger wings than normal' in his log book. The curator, going through the log book and identifying important knowledge, formalizes this as 'locus perculus has wingspan > 0.5m'. The creator enters this knowledge as a digital resource in the knowledge system, thus creating the digital artifact (say as JSON, RDF, XML or HTML). A different example is a news article. pav:authoredBy indicates the journalist who wrote the article. pav:contributedBy can indicate the artist who added an illustration. pav:curatedBy can indicate the editor who made the article conform to the news paper's style. pav:createdBy can indicate who put the article on the web site. The software tool used by the creator to make the digital resource (say Protege, Wordpress or OpenOffice) can be indicated with pav:createdWith. The date the digital resource was created can be indicated with pav:createdOn. The location the agent was at when creating the digital resource can be made using pav:createdAt.
Provided for backwards compatibility. Use instead the inverse pav:curatedBy.
Specifies an agent specialist responsible for shaping the expression in an appropriate format. Often the primary agent responsible for ensuring the quality of the representation. The curator may be different from the author (pav:authoredBy) and creator of the digital resource (pav:createdBy). The curator may in some cases be a software agent, for instance text mining software which adds hyperlinks for recognized genome names. The date of curating can be expressed using pav:curatedOn - note however in the case of multiple curators that there is no relationship in PAV identifying which agent contributed when or what. If capturing such lineage is desired, it should be additionally expressed using PROV relationships like prov:qualifiedAttribution or prov:wasGeneratedBy.
The date of the last re-import of the resource. This property is used in addition to pav:importedOn if this version has been updated due to a re-import. If the re-import created a new resource rather than refreshing an existing resource, then instead use pav:importedOn together with pav:previousVersion. This property is normally used in a functional way, although PAV does not formally restrict this. The value is of type xsd:dateTime, for instance "2013-03-26T14:49:00+01:00"^^xsd:dateTime. The timezone information (Z for UTC, +01:00 for UTC+1, etc) SHOULD be included unless unknown. If the time (or parts of time) is unknown, use 00:00:00Z. If the day/month is unknown, use 01-01, for instance, if we only know September 1983, then use "1983-09-01T00:00:00Z"^^xsd:dateTime.
An entity responsible for importing the data. The importer is usually a software entity which has done the transcription from the original source. Note that pav:importedBy may overlap with pav:createdWith. The source for the import should be given with pav:importedFrom. The time of the import should be given with pav:importedOn. See pav:importedFrom for a discussion of import vs. retrieve vs. derived.
The original source of imported information. Import means that the content has been preserved, but transcribed somehow, for instance to fit a different representation model by converting formats. Examples of import are when the original was JSON and the current resource is RDF, or where the original was an document scan, and this resource is the plain text found through OCR. The imported resource does not have to be complete, but should be consistent with the knowledge conveyed by the original resource. If additional knowledge has been contributed, pav:derivedFrom would be more appropriate. If the resource has been copied verbatim from the original representation (e.g. downloaded), use pav:retrievedFrom. To indicate which agent(s) performed the import, use pav:importedBy. Use pav:importedOn to indicate when it happened.
The date this resource was imported from a source (pav:importedFrom). Note that pav:importedOn may overlap with pav:createdOn, but in cases where they differ, the import time indicates the time of the retrieval and transcription of the original source, while the creation time indicates when the final resource was made, for instance after user approval. This property is normally used in a functional way, indicating the first import date, although PAV does not formally restrict this. If the resource is later reimported, this should instead be indicated with pav:lastRefreshedOn. The source of the import should be given with pav:importedFrom. The agent that performed the import should be given with pav:importedBy. See pav:importedFrom for a discussion about import vs. retrieval. The value is of type xsd:dateTime, for instance "2013-03-26T14:49:00+01:00"^^xsd:dateTime. The timezone information (Z for UTC, +01:00 for UTC+1, etc) SHOULD be included unless unknown. If the time (or parts of time) is unknown, use 00:00:00Z. If the day/month is unknown, use 01-01, for instance, if we only know September 1983, then use "1983-09-01T00:00:00Z"^^xsd:dateTime.
The previous version of a resource in a lineage. For instance a news article updated to correct factual information would point to the previous version of the article with pav:previousVersion. If however the content has significantly changed so that the two resources no longer share lineage (say a new article that talks about the same facts), they can instead be related using pav:derivedFrom. This property is normally used in a functional way, although PAV does not formally restrict this. Earlier versions which are not direct ancestors of this resource may instead be provided using the superproperty pav:hasEarlierVersion. A version number of this resource can be provided using the data property pav:version. To indicate that this version is a snapshot of a more general, non-versioned resource, e.g. "Weather Today" vs. "Weather Today on 2013-12-07", see pav:hasVersion. Note that it might be confusing to indicate pav:previousVersion from a resource that also has pav:hasVersion or pav:hasCurrentVersion relations, as such resources are intended to be a long-living and "unversioned", while pav:previousVersion is intended for use between permalink-like "snapshots" arranged in a linear history.
The date of the last update of the resource. An update is a change which did not warrant making a new resource related using pav:previousVersion, for instance correcting a spelling mistake. This property is normally used in a functional way, although PAV does not formally restrict this. The value is of type xsd:dateTime, for instance "2013-03-26T14:49:00+01:00"^^xsd:dateTime. The timezone information (Z for UTC, +01:00 for UTC+1, etc) SHOULD be included unless unknown. If the time (or parts of time) is unknown, use 00:00:00Z. If the day/month is unknown, use 01-01, for instance, if we only know September 1983, then use "1983-09-01T00:00:00Z"^^xsd:dateTime.
The date of creation of the resource representation. The agents responsible can be indicated with pav:createdBy. This property is normally used in a functional way, indicating the time of creation, although PAV does not formally restrict this. pav:lastUpdateOn can be used to indicate minor updates that did not affect the creating date. The value is of type xsd:dateTime, for instance "2013-03-26T14:49:00+01:00"^^xsd:dateTime. The timezone information (Z for UTC, +01:00 for UTC+1, etc) SHOULD be included unless unknown. If the time (or parts of time) is unknown, use 00:00:00Z. If the day/month is unknown, use 01-01, for instance, if we only know September 1983, then use "1983-09-01T00:00:00Z"^^xsd:dateTime.
The original provider of the encoded information (e.g. PubMed, UniProt, Science Commons). The provider might not coincide with the dct:publisher, which would describe the current publisher of the resource. For instance if the resource was retrieved, imported or derived from a source, that source was published by the original provider. pav:providedBy provides a shortcut to indicate that original provider on the new resource.
The date this resource was authored. pav:authoredBy gives the authoring agent. Note that pav:authoredOn is different from pav:createdOn, although they are often the same. See pav:createdBy for a discussion. This property is normally used in a functional way, indicating the last time of authoring, although PAV does not formally restrict this. The value is of type xsd:dateTime, for instance "2013-03-26T14:49:00+01:00"^^xsd:dateTime. The timezone information (Z for UTC, +01:00 for UTC+1, etc) SHOULD be included unless unknown. If the time (or parts of time) is unknown, use 00:00:00Z. If the day/month is unknown, use 01-01, for instance, if we only know September 1983, then use "1983-09-01T00:00:00Z"^^xsd:dateTime.
An agent that originated or gave existence to the work that is expressed by the digital resource. The author of the content of a resource may be different from the creator of the resource representation (although they are often the same). See pav:createdBy for a discussion. pav:authoredBy is more specific than its superproperty dct:creator - which might or might not be interpreted to also cover the creation of the representation of the artifact. The author is usually not a software agent (which would be indicated with pav:createdWith, pav:createdBy or pav:importedBy), unless the software actually authored the content itself; for instance an artificial intelligence algorithm which authored a piece of music or a machine learning algorithm that authored a classification of a tumor sample. The date of authoring can be expressed using pav:authoredOn - note however in the case of multiple authors that there is no relationship in PAV identifying which agent contributed when or what. If capturing such lineage is desired, it should be additionally expressed using PROV relationships like prov:qualifiedAttribution or prov:wasGeneratedBy.
The date this resource was contributed to. pav:contributedBy provides the agent(s) that contributed. The value is of type xsd:dateTime, for instance "2013-03-26T14:49:00+01:00"^^xsd:dateTime. The timezone information (Z for UTC, +01:00 for UTC+1, etc) SHOULD be included unless unknown. If the time (or parts of time) is unknown, use 00:00:00Z. If the day/month is unknown, use 01-01, for instance, if we only know September 1983, then use "1983-09-01T00:00:00Z"^^xsd:dateTime.
The date this resource was curated. pav:curatedBy gives the agent(s) that performed the curation. This property is normally used in a functional way, indicating the last curation date, although PAV does not formally restrict this. The value is of type xsd:dateTime, for instance "2013-03-26T14:49:00+01:00"^^xsd:dateTime. The timezone information (Z for UTC, +01:00 for UTC+1, etc) SHOULD be included unless unknown. If the time (or parts of time) is unknown, use 00:00:00Z. If the day/month is unknown, use 01-01, for instance, if we only know September 1983, then use "1983-09-01T00:00:00Z"^^xsd:dateTime.
This resource has a more specific, versioned resource with equivalent content. This property is intended for relating a non-versioned or abstract resource to a single snapshot that can be used as a permalink to indicate the current version of the content. For instance, if today is 2013-12-25, then a News page can indicate a corresponding snapshot resource which will refer to the news as they were of 2013-12-25. <http://news.example.com/> pav:hasCurrentVersion <http://news.example.com/2013-12-25/> . "Equivalent content" is a loose definition, for instance the snapshot resource might include additional information to indicate it is a snapshot, and is not required to be immutable. Other versioned resources indicating the content at earlier times MAY be indicated with the superproperty pav:hasVersion, one of which MAY be related to the current version using pav:hasCurrentVersion: <http://news.example.com/2013-12-25/> pav:previousVersion <http://news.example.com/2013-12-24/> . <http://news.example.com/> pav:hasVersion <http://news.example.com/2013-12-23/> . Note that it might be confusing to also indicate pav:previousVersion from a resource that has hasCurrentVersion relations, as such a resource is intended to be a long-living "unversioned" resource. The PAV ontology does however not formally restrict this, to cater for more complex scenarios with multiple abstraction levels. Similarly, it would normally be incorrect to indicate a pav:hasCurrentVersion from an older version; instead the current version would be found by finding the non-versioned resource that the particular resource is a version of, and then its current version. This property is normally used in a functional way, although PAV does not formally restrict this.
This resource has a more specific, versioned resource. This property is intended for relating a non-versioned or abstract resource to several versioned resources, e.g. snapshots. For instance, if there are two snapshots of the News page, made on 23rd and 24th of December, then: <http://news.example.com/> pav:hasVersion <http://news.example.com/2013-12-23/> ; pav:hasVersion <http://news.example.com/2013-12-24/> . If one of the versions has somewhat the equivalent content to this resource (e.g. can be used as a permalink for this resource), then it should instead be indicated with the subproperty pav:hasCurrentVersion: <http://news.example.com/> pav:hasCurrentVersion <http://news.example.com/2013-12-25/> . To order the versions, use pav:previousVersion: <http://news.example.com/2013-12-25/> pav:previousVersion <http://news.example.com/2013-12-24/> . <http://news.example.com/2013-12-24/> pav:previousVersion <http://news.example.com/2013-12-23/> . Note that it might be confusing to also indicate pav:previousVersion from a resource that has pav:hasVersion relations, as such a resource is intended to be a long-living "unversioned" resource. The PAV ontology does however not formally restrict this, to cater for more complex scenarios with multiple abstraction levels. pav:hasVersion is a subproperty of dcterms:hasVersion to more strongly define this hierarchical pattern. It is therefore also a subproperty of pav:generalizationOf (inverse of prov:specializationOf). To indicate the existence of other, non-hierarchical kind of editions and adaptations of this resource that are not versioned snapshots (e.g. Powerpoint slides has a video recording version), use instead dcterms:hasVersion or prov:alternateOf.
This versioned resource has an earlier version. Any earlier version of this resource can be indicated with pav:hasEarlierVersion, e.g.: <http://example.com/v4> pav:hasEarlierVersion <http://example.com/v2> ; pav:hasEarlierVersion <http://example.com/v1> . The subproperty pav:previousVersion SHOULD be used if the earlier version is the direct ancestor of this version. <http://example.com/v4> pav:previousVersion <http://example.com/v3> . This property is transitive, so it should not be necessary to repeat the earlier versions of an earlier version. A chain of previous versions can be declared using the subproperty pav:previousVersion, implying that the previous previous version is also an earlier version. It might however still be useful to declare an earlier version explicitly, for instance because it is an earlier version of high relevance or because the complete chain of pav:previousVersion is not available. To indicate that this version is a snapshot of a more general, non-versioned resource, e.g. "Weather Today" vs. "Weather Today on 2013-12-07", see pav:hasVersion.
The date the source for this resource was retrieved. The source that was retrieved should be indicated with pav:retrievedFrom. The agent that performed the retrieval may be specified with pav:retrievedBy. This property is normally used in a functional way, although PAV does not formally restrict this. The value is of type xsd:dateTime, for instance "2013-03-26T14:49:00+01:00"^^xsd:dateTime. The timezone information (Z for UTC, +01:00 for UTC+1, etc) SHOULD be included unless unknown. If the time (or parts of time) is unknown, use 00:00:00Z. If the day/month is unknown, use 01-01, for instance, if we only know September 1983, then use "1983-09-01T00:00:00Z"^^xsd:dateTime.
An entity responsible for retrieving the data from an external source. The retrieving agent is usually a software entity, which has done the retrieval from the original source without performing any transcription. The source that was retrieved should be given with pav:retrievedFrom. The time of the retrieval should be indicated using pav:retrievedOn. See pav:importedFrom for a discussion of import vs. retrieve vs. derived.
The URI where a resource has been retrieved from. The retrieving agent is usually a software entity, which has done the retrieval from the original source without performing any transcription. Retrieval indicates that this resource has the same representation as the original resource. If the resource has been somewhat transformed, use pav:importedFrom instead. The time of the retrieval should be indicated using pav:retrievedOn. The agent may be indicated with pav:retrievedBy.
The resource is related to a source which was originally accessed or consulted on the given date as part of creating or authoring the resource. The source(s) should be specified using pav:sourceAccessedAt. For instance, if the source accessed described the weather forecast for the next day, the time of source access can be crucial information. This property is normally used in a functional way, although PAV does not formally restrict this. If the source is subsequently checked again (say to verify validity), this should be indicated with pav:sourceLastAccessedOn. In the case multiple sources being accessed at different times or by different agents, PAV does not distinguish who accessed when what. If such details are required, they may be provided by additionally using prov:qualifiedInfluence. The value is of type xsd:dateTime, for instance "2013-03-26T14:49:00+01:00"^^xsd:dateTime. The timezone information (Z for UTC, +01:00 for UTC+1, etc) SHOULD be included unless unknown. If the time (or parts of time) is unknown, use 00:00:00Z. If the day/month is unknown, use 01-01, for instance, if we only know September 1983, then use "1983-09-01T00:00:00Z"^^xsd:dateTime.
The geo-location of the agents when creating the resource (pav:createdBy). For instance a photographer takes a picture of the Eiffel Tower while standing in front of it.
The resource is related to a given source which was accessed or consulted (but not retrieved, imported or derived from). This access can be detailed with pav:sourceAccessedBy and pav:sourceAccessedOn. For instance, a curator (pav:curatedBy) might have consulted figures in a published paper to confirm that a dataset was correctly pav:importedFrom the paper's supplementary CSV file. Another example: I can access the page for tomorrow weather in Boston (http://www.weather.com/weather/tomorrow/Boston+MA+02143) and I can blog ‘tomorrow is going to be nice’. The source does not make any claims about the nice weather, that is my interpretation; therefore the blog post has pav:sourceAccessedAt the weather page.
The resource is related to a source which was accessed or consulted by the given agent. The source(s) should be specified using pav:sourceAccessedAt, and the time with pav:sourceAccessedOn. For instance, the given agent could be a curator (also pav:curatedBy) which consulted figures in a published paper to confirm that a dataset was correctly pav:importedFrom the paper's supplementary CSV file.
The resource is related to a source which was last accessed or consulted on the given date. The source(s) should be specified using pav:sourceAccessedAt. Usage of this property indicates that the source has been checked previously, which the initial time should be indicated with pav:sourceAccessedOn. This property can be useful together with pav:lastRefreshedOn or pav:lastUpdateOn in order to indicate a re-import or update, but could also be used alone, for instance when a source was simply verified and no further action was taken for the resource. This property is normally used in a functional way, although PAV does not formally restrict this. The value is of type xsd:dateTime, for instance "2013-03-26T14:49:00+01:00"^^xsd:dateTime. The timezone information (Z for UTC, +01:00 for UTC+1, etc) SHOULD be included unless unknown. If the time (or parts of time) is unknown, use 00:00:00Z. If the day/month is unknown, use 01-01, for instance, if we only know September 1983, then use "1983-09-01T00:00:00Z"^^xsd:dateTime.
The version number of a resource. This is a freetext string, typical values are "1.5" or "21". The URI identifying the previous version can be provided using prov:previousVersion. This property is normally used in a functional way, although PAV does not formally restrict this.
The resource was contributed to by the given agent. Specifies an agent that provided any sort of help in conceiving the work that is expressed by the digital artifact. Contributions can take many forms, of which PAV define the subproperties pav:authoredBy and pav:curatedBy; however other specific roles could also be specified by pav:contributedBy or custom subproperties, such as illustrating, investigating or managing the underlying data source. Contributions can additionally be expressed in detail using prov:qualifiedAttribution and prov:hadRole. Note that pav:contributedBy identifies only agents that contributed to the work, knowledge or intellectual property, and not agents that made the digital artifact or representation (pav:createdBy), thus the considerations for software agents is similar to for pav:authoredBy and pav:curatedBy. pav:contributedBy is more specific than its superproperty dct:contributor - which might or might not be interpreted to also cover contributions to making the representation of the artifact. The date of contribution can be expressed using pav:contributedOn - note however in the case of multiple contributors that there is no relationship in PAV identifying which agent contributed when or what. If capturing such lineage is desired, it should be additionally expressed using PROV relationships like prov:qualifiedAttribution or prov:wasGeneratedBy.
Derived from a different resource. Derivation conserns itself with derived knowledge. If this resource has the same content as the other resource, but has simply been transcribed to fit a different model (like XML -> RDF or SQL -> CVS), use pav:importedFrom. If a resource was simply retrieved, use pav:retrievedFrom. If the content has however been further refined or modified, pav:derivedFrom should be used. Details about who performed the derivation (e.g. who did the refining or modifications) may be indicated with pav:contributedBy and its subproperties.
1.4 2026-07: differentiation of messages from property and node shapes 1.3 2026-04: Align schema:license allowed types with VocPub 1.2 2026-02: Changes a couple of Violations to Warnings 1.1 2026-02: Made ValPub compliant; move all Property Shapes to IRIs, not BNs 1.0 2025-12: Created based on OntPub Validator & the SHACL Profiling deaft recommendation
SHACL Shapes to validate ontologies of SHACL shapes according to the Validator Publications Profile
Requirement 2.1.4: SHACL ontologies MUST have exactly one title, a text literal, indicated using the skos:prefLabel or the schema:name property
Requirement 2.1.5: SHACL ontologies MUST have exactly one definition, literal text, indicated using either the skos:definition or schema:description property
Requirement 2.1.9: SHACL ontologies SHOULD indicate provenance with at least one of the following properties: skos:historyNote, dcterms:source or prov:wasDerivedFrom.
Requirement 2.2.1: SHACL Shapes MUST have at least one name indicated using either the skos:prefLabel or schema:name property that must be either a string or a language-typed text literal value. Only one value per language is allowed if languages are used.
Requirement 2.2.2: SHACL Shapes MUST have a message value, indicated using sh:message
Requirement 2.2.3: SHACL Shapes provenance, if different from that of the SHACL ontology being validated, SHOULD be indicated by at least one of the following properties: skos:historyNote, dcterms:source or prov:wasDerivedFrom
Requirement 2.1.10: SHACL ontologies SHOULD indicate a version using the property owl:versionIRI with an IRI object.
Requirement 2.1.11: SHACL ontologies SHOULD indicate any online version controlled source code repository storing the ontology and related content with the schema:codeRepository with a xsd:anyURI object.
Requirement 2.1.12a: SHACL ontologies SHOULD present any licence pertaining to its use using the schema:license predicate preferentially indicating the IRI of a license if in RDF form or a literal URL (datatype xsd:anyURI) if online but not in RDF form. If the licence is expressed in text, a literal text field may be indicated.
Requirement 2.1.12b: SHACL ontologies SHOULD present a license for its use indicated with the schema:license use indicating either the literal text of a license or a URL of a license using the datatype xsd:anyURI or they may link to a Semantic Web version of a license via its IRI.
Requirement 2.1.13: SHACL ontologies MAY present usage information alongside license information using the schema:usageInfo property indicating literal text.
Requirement 2.1.14: SHACL ontologies SHOULD present a copyright information for it indicated with properties schema:copyrightHolder, schema:copyrightNotice and schema:copyrightYear. schema:copyrightHolder may be used with a text object or, preferably, an schema:Person or schema:Organization object.
Requirement 2.1.15: SHACL ontologies MUST present at least one sh:NodeShape or sh:PropertyShape within the ontology file
Requirement 2.1.2 SHACL ontologies MUST be presented as a single owl:Ontology object & Requirement 2.1.3 Each SHACL ontology MUST be presented in a single file which does not contain information other than that which is directly part of the ontology and the file is considered the point-of-truth
Requirement 2.1.5 p 1: SHACL ontologies MUST have exactly one definition, literal text, indicated using either the skos:definition or schema:description property
Requirement 2.1.5 p 2: SHACL ontologies MUST have exactly one definition, literal text, indicated using either the skos:definition or schema:description property y
Requirement 2.1.6: SHACL ontologies MUST have exactly one created date, exactly one modified date and exactly one issued date indicated using the schema:dateCreated & schema:dateModified properties respectively that must be either an xsd:date, xsd:dateTime or xsd:dateTimeStamp literal values
Requirement 2.1.7: SHACL ontologies MUST have at least one creator, indicated using schema:creator that must be IRI values indicating agents, that is instances of schema:Person, schema:Organization or a subclass of either
Requirement 2.1.7: SHACL ontologies MUST have at least one publisher, indicated using schema:publisher that must be IRI values indicating agents, that is instances of schema:Person, schema:Organization or a subclass of either
Requirement 2.1.8: SHACL ontologies MAY have at least any number of contributors, indicated using schema:contributor property that must be a IRI value indicating an agent, that is an instance of schema:Person, schema:Organization or a subclass of either
At least 1 prov:wasDerivedFrom must be present
At least 1 dcterms:source value must be present
At least 1 skos:historyNote value must be present
At least 1 schema:citation value must be present
Requirement 2.1.9b: SHACL ontologies MUST NOT use skos:historyNote property more than once on any object.
Requirement 2.1.9c: You MUST NOT use dcterms:source property more than once on any object.
Requirement 2.1.9e: Whenever dcterms:source is used, it must be a datatype property indicating an object of type xsd:anyURI
Requirement 2.2.2: SHACL Shapes MUST have a message value, indicated using sh:message or a description, indicated using schema:description
:0.0.1 Generated by OntoShacl:v0.1.0 <https://github.com/Kurrawong/ontoshacl>
Automatically generated by OntoShacl on 2026-02-03
OntoShacl generated validator for https://www.ica.org/standards/RiC/ontology#
The subject of a rico:relationHasSource statement must be one of: - rico:AccumulationRelation The object of a rico:relationHasSource statement must be one of: - rico:RecordResource - rico:Instantiation The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:AccumulationRelation The object of a rico:relationHasTarget statement must be one of: - rico:Agent The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:accumulationRelation_role statement must be one of: - rico:AccumulationRelation The object of a rico:accumulationRelation_role statement must be one of: - rico:AccumulationRelation
The subject of a rico:activityIsContextOfRelation statement must be one of: - rico:Activity The object of a rico:activityIsContextOfRelation statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b244
The subject of a rico:documentedBy statement must be one of: - rico:Activity The object of a rico:documentedBy statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b297
The subject of a rico:hasActivityType statement must be one of: - rico:Activity The object of a rico:hasActivityType statement must be one of: - rico:ActivityType
The subject of a rico:isOrWasPerformedBy statement must be one of: - rico:Activity The object of a rico:isOrWasPerformedBy statement must be one of: - rico:Agent
ActivityDocumentationRelation validation
The subject of a rico:relationHasSource statement must be one of: - rico:ActivityDocumentationRelation The object of a rico:relationHasSource statement must be one of: - rico:RecordResource - rico:Instantiation The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:ActivityDocumentationRelation The object of a rico:relationHasTarget statement must be one of: - rico:Activity The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:activityDocumentationRelation_role statement must be one of: - rico:ActivityDocumentationRelation The object of a rico:activityDocumentationRelation_role statement must be one of: - rico:ActivityDocumentationRelation
activityDocumentationRelation_role Shape
The subject of a rico:isActivityTypeOf statement must be one of: - rico:ActivityType The object of a rico:isActivityTypeOf statement must be one of: - rico:Activity
The subject of a rico:agentHasOrHadLocation statement must be one of: - rico:Agent The object of a rico:agentHasOrHadLocation statement must be one of: - rico:Place
The subject of a rico:authorizedBy statement must be one of: - rico:Agent The object of a rico:authorizedBy statement must be one of: - rico:Mandate
The subject of a rico:hadSubordinate statement must be one of: - rico:Agent The object of a rico:hadSubordinate statement must be one of: - rico:Agent
The subject of a rico:hasDirectSubordinate statement must be one of: - rico:Agent The object of a rico:hasDirectSubordinate statement must be one of: - rico:Agent
The subject of a rico:hasOrHadAgentName statement must be one of: - rico:Agent The object of a rico:hasOrHadAgentName statement must be one of: - rico:AgentName
The subject of a rico:hasOrHadAuthorityOver statement must be one of: - rico:Agent The object of a rico:hasOrHadAuthorityOver statement must be one of: - rico:Thing
The subject of a rico:hasOrHadController statement must be one of: - rico:Agent The object of a rico:hasOrHadController statement must be one of: - rico:Agent
The subject of a rico:hasOrHadJurisdiction statement must be one of: - rico:Agent The object of a rico:hasOrHadJurisdiction statement must be one of: - rico:Place
The subject of a rico:hasOrHadSubordinate statement must be one of: - rico:Agent The object of a rico:hasOrHadSubordinate statement must be one of: - rico:Agent
The subject of a rico:hasOrHadWorkRelationWith statement must be one of: - rico:Agent The object of a rico:hasOrHadWorkRelationWith statement must be one of: - rico:Agent
The subject of a rico:hasSubordinateTransitive statement must be one of: - rico:Agent The object of a rico:hasSubordinateTransitive statement must be one of: - rico:Agent
The subject of a rico:hasSuccessor statement must be one of: - rico:Agent The object of a rico:hasSuccessor statement must be one of: - rico:Agent
The subject of a rico:isAccumulatorOf statement must be one of: - rico:Agent The object of a rico:isAccumulatorOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1931
The subject of a rico:isAddresseeOf statement must be one of: - rico:Agent The object of a rico:isAddresseeOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b722
The subject of a rico:isAgentAssociatedWithAgent statement must be one of: - rico:Agent The object of a rico:isAgentAssociatedWithAgent statement must be one of: - rico:Agent
The subject of a rico:isAgentAssociatedWithPlace statement must be one of: - rico:Agent The object of a rico:isAgentAssociatedWithPlace statement must be one of: - rico:Place
The subject of a rico:isAuthorizingAgentInMandateRelation statement must be one of: - rico:Agent The object of a rico:isAuthorizingAgentInMandateRelation statement must be one of: - rico:MandateRelation
isAuthorizingAgentInMandateRelation Shape
The subject of a rico:isCollectorOf statement must be one of: - rico:Agent The object of a rico:isCollectorOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b757
The subject of a rico:isCreatorOf statement must be one of: - rico:Agent The object of a rico:isCreatorOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1657
The subject of a rico:isDirectSubordinateTo statement must be one of: - rico:Agent The object of a rico:isDirectSubordinateTo statement must be one of: - rico:Agent
The subject of a rico:isOrWasControllerOf statement must be one of: - rico:Agent The object of a rico:isOrWasControllerOf statement must be one of: - rico:Agent
The subject of a rico:isOrWasHolderOf statement must be one of: - rico:Agent The object of a rico:isOrWasHolderOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b923
The subject of a rico:isOrWasManagerOf statement must be one of: - rico:Agent The object of a rico:isOrWasManagerOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1699
The subject of a rico:isOrWasResponsibleForEnforcing statement must be one of: - rico:Agent The object of a rico:isOrWasResponsibleForEnforcing statement must be one of: - rico:Rule
The subject of a rico:isOrWasSubordinateTo statement must be one of: - rico:Agent The object of a rico:isOrWasSubordinateTo statement must be one of: - rico:Agent
The subject of a rico:isOrganicProvenanceOf statement must be one of: - rico:Agent The object of a rico:isOrganicProvenanceOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b2307
The subject of a rico:isPublisherOf statement must be one of: - rico:Agent The object of a rico:isPublisherOf statement must be one of: - rico:RecordResource
The subject of a rico:isReceiverOf statement must be one of: - rico:Agent The object of a rico:isReceiverOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1077
The subject of a rico:isResponsibleForIssuing statement must be one of: - rico:Agent The object of a rico:isResponsibleForIssuing statement must be one of: - rico:Rule
The subject of a rico:isSenderOf statement must be one of: - rico:Agent The object of a rico:isSenderOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1100
The subject of a rico:isSubordinateToTransitive statement must be one of: - rico:Agent The object of a rico:isSubordinateToTransitive statement must be one of: - rico:Agent
The subject of a rico:isSuccessorOf statement must be one of: - rico:Agent The object of a rico:isSuccessorOf statement must be one of: - rico:Agent
The subject of a rico:performsOrPerformed statement must be one of: - rico:Agent The object of a rico:performsOrPerformed statement must be one of: - rico:Activity
The subject of a rico:wasSubordinateTo statement must be one of: - rico:Agent The object of a rico:wasSubordinateTo statement must be one of: - rico:Agent
The subject of a rico:relationHasSource statement must be one of: - rico:AgentControlRelation The object of a rico:relationHasSource statement must be one of: - rico:Agent The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:AgentControlRelation The object of a rico:relationHasTarget statement must be one of: - rico:Agent The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:agentControlRelation_role statement must be one of: - rico:AgentControlRelation The object of a rico:agentControlRelation_role statement must be one of: - rico:AgentControlRelation
The subject of a rico:relationHasSource statement must be one of: - rico:AgentHierarchicalRelation The object of a rico:relationHasSource statement must be one of: - rico:Agent The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:AgentHierarchicalRelation The object of a rico:relationHasTarget statement must be one of: - rico:Agent The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:agentHierarchicalRelation_role statement must be one of: - rico:AgentHierarchicalRelation The object of a rico:agentHierarchicalRelation_role statement must be one of: - rico:AgentHierarchicalRelation
The subject of a rico:isOrWasAgentNameOf statement must be one of: - rico:AgentName The object of a rico:isOrWasAgentNameOf statement must be one of: - rico:Agent
The subject of a rico:relationHasSource statement must be one of: - rico:AgentTemporalRelation The object of a rico:relationHasSource statement must be one of: - rico:Agent The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:AgentTemporalRelation The object of a rico:relationHasTarget statement must be one of: - rico:Agent The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:agentTemporalRelation_role statement must be one of: - rico:AgentTemporalRelation The object of a rico:agentTemporalRelation_role statement must be one of: - rico:AgentTemporalRelation
The subject of a rico:relationConnects statement must be one of: - rico:AgentToAgentRelation The object of a rico:relationConnects statement must be one of: - rico:Agent The rico:relationConnects property MUST: - Appear at least 2 times
The subject of a rico:agentToAgentRelation_role statement must be one of: - rico:AgentToAgentRelation The object of a rico:agentToAgentRelation_role statement must be one of: - rico:AgentToAgentRelation
The subject of a rico:isOrWasAppellationOf statement must be one of: - rico:Appellation The object of a rico:isOrWasAppellationOf statement must be one of: - rico:Thing
The subject of a rico:wasUsedFromDate statement must be one of: - rico:Appellation The object of a rico:wasUsedFromDate statement must be one of: - rico:Date
The subject of a rico:wasUsedToDate statement must be one of: - rico:Appellation The object of a rico:wasUsedToDate statement must be one of: - rico:Date
The subject of a rico:relationHasSource statement must be one of: - rico:AppellationRelation The object of a rico:relationHasSource statement must be one of: - rico:Appellation
The subject of a rico:relationHasTarget statement must be one of: - rico:AppellationRelation The object of a rico:relationHasTarget statement must be one of: - rico:Thing The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:appellationRelation_role statement must be one of: - rico:AppellationRelation The object of a rico:appellationRelation_role statement must be one of: - rico:AppellationRelation
The subject of a rico:relationHasSource statement must be one of: - rico:AuthorityRelation The object of a rico:relationHasSource statement must be one of: - rico:Agent The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:AuthorityRelation The object of a rico:relationHasTarget statement must be one of: - rico:Thing The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:authorityRelation_role statement must be one of: - rico:AuthorityRelation The object of a rico:authorityRelation_role statement must be one of: - rico:AuthorityRelation
The subject of a rico:relationHasSource statement must be one of: - rico:AuthorshipRelation The object of a rico:relationHasSource statement must be one of: - rico:Record The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:AuthorshipRelation The object of a rico:relationHasTarget statement must be one of: - rico:Person - rico:Group - rico:Position The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:authorshipRelation_role statement must be one of: - rico:AuthorshipRelation The object of a rico:authorshipRelation_role statement must be one of: - rico:AuthorshipRelation
The subject of a rico:isCarrierTypeOf statement must be one of: - rico:CarrierType The object of a rico:isCarrierTypeOf statement must be one of: - rico:Instantiation
The subject of a rico:relationHasSource statement must be one of: - rico:ChildRelation The object of a rico:relationHasSource statement must be one of: - rico:Person The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:ChildRelation The object of a rico:relationHasTarget statement must be one of: - rico:Person The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:childRelation_role statement must be one of: - rico:ChildRelation The object of a rico:childRelation_role statement must be one of: - rico:ChildRelation
The subject of a rico:isContentTypeOf statement must be one of: - rico:ContentType The object of a rico:isContentTypeOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b763
The subject of a rico:isOrWasContentTypeOfAllMembersOf statement must be one of: - rico:ContentType The object of a rico:isOrWasContentTypeOfAllMembersOf statement must be one of: - rico:RecordSet
The subject of a rico:isOrWasContentTypeOfSomeMembersOf statement must be one of: - rico:ContentType The object of a rico:isOrWasContentTypeOfSomeMembersOf statement must be one of: - rico:RecordSet
The subject of a rico:isOrWasCoordinatesOf statement must be one of: - rico:Coordinates The object of a rico:isOrWasCoordinatesOf statement must be one of: - rico:PhysicalLocation
The subject of a rico:hasOrHadCorporateBodyType statement must be one of: - rico:CorporateBody The object of a rico:hasOrHadCorporateBodyType statement must be one of: - rico:CorporateBodyType
The subject of a rico:resultedFromTheMergerOf statement must be one of: - rico:CorporateBody The object of a rico:resultedFromTheMergerOf statement must be one of: - rico:CorporateBody
The subject of a rico:resultedFromTheSplitOf statement must be one of: - rico:CorporateBody The object of a rico:resultedFromTheSplitOf statement must be one of: - rico:CorporateBody
The subject of a rico:wasMergedInto statement must be one of: - rico:CorporateBody The object of a rico:wasMergedInto statement must be one of: - rico:CorporateBody
The subject of a rico:wasSplitInto statement must be one of: - rico:CorporateBody The object of a rico:wasSplitInto statement must be one of: - rico:CorporateBody
The subject of a rico:isOrWasCorporateBodyTypeOf statement must be one of: - rico:CorporateBodyType The object of a rico:isOrWasCorporateBodyTypeOf statement must be one of: - rico:CorporateBody
The subject of a rico:relationConnects statement must be one of: - rico:CorrespondenceRelation The object of a rico:relationConnects statement must be one of: - rico:Person The rico:relationConnects property MUST: - Appear at least 2 times
The subject of a rico:correspondenceRelation_role statement must be one of: - rico:CorrespondenceRelation The object of a rico:correspondenceRelation_role statement must be one of: - rico:CorrespondenceRelation
The subject of a rico:relationHasSource statement must be one of: - rico:CreationRelation The object of a rico:relationHasSource statement must be one of: - rico:RecordResource - rico:Instantiation The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:CreationRelation The object of a rico:relationHasTarget statement must be one of: - rico:Agent The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:creationRelation_role statement must be one of: - rico:CreationRelation The object of a rico:creationRelation_role statement must be one of: - rico:CreationRelation
The subject of a rico:creationWithRole statement must be one of: - rico:CreationRelation The object of a rico:creationWithRole statement must be one of: - rico:RoleType
The subject of a rico:hasDateType statement must be one of: - rico:Date The object of a rico:hasDateType statement must be one of: - rico:DateType
The subject of a rico:hasWithin statement must be one of: - rico:Date The object of a rico:hasWithin statement must be one of: - rico:Date
The subject of a rico:intersects statement must be one of: - rico:Date The object of a rico:intersects statement must be one of: - rico:Date
The subject of a rico:isBeginningDateOf statement must be one of: - rico:Date The object of a rico:isBeginningDateOf statement must be one of: - rico:Thing
The subject of a rico:isBirthDateOf statement must be one of: - rico:Date The object of a rico:isBirthDateOf statement must be one of: - rico:Person
The subject of a rico:isCreationDateOf statement must be one of: - rico:Date The object of a rico:isCreationDateOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b771
The subject of a rico:isDateAssociatedWith statement must be one of: - rico:Date The object of a rico:isDateAssociatedWith statement must be one of: - rico:Thing
The subject of a rico:isDateOfOccurrenceOf statement must be one of: - rico:Date The object of a rico:isDateOfOccurrenceOf statement must be one of: - rico:Event
The subject of a rico:isDeathDateOf statement must be one of: - rico:Date The object of a rico:isDeathDateOf statement must be one of: - rico:Person
The subject of a rico:isDestructionDateOf statement must be one of: - rico:Date The object of a rico:isDestructionDateOf statement must be one of: - rico:Thing
The subject of a rico:isEndDateOf statement must be one of: - rico:Date The object of a rico:isEndDateOf statement must be one of: - rico:Thing
The subject of a rico:isFromUseDateOf statement must be one of: - rico:Date The object of a rico:isFromUseDateOf statement must be one of: - rico:Appellation
The subject of a rico:isLastUpdateDateOf statement must be one of: - rico:Date The object of a rico:isLastUpdateDateOf statement must be one of: - rico:Thing
The subject of a rico:isModificationDateOf statement must be one of: - rico:Date The object of a rico:isModificationDateOf statement must be one of: - rico:Thing
The subject of a rico:isOrWasCreationDateOfAllMembersOf statement must be one of: - rico:Date The object of a rico:isOrWasCreationDateOfAllMembersOf statement must be one of: - rico:RecordSet
The subject of a rico:isOrWasCreationDateOfMostMembersOf statement must be one of: - rico:Date The object of a rico:isOrWasCreationDateOfMostMembersOf statement must be one of: - rico:RecordSet
isOrWasCreationDateOfMostMembersOf Shape
The subject of a rico:isOrWasCreationDateOfSomeMembersOf statement must be one of: - rico:Date The object of a rico:isOrWasCreationDateOfSomeMembersOf statement must be one of: - rico:RecordSet
isOrWasCreationDateOfSomeMembersOf Shape
The subject of a rico:isPublicationDateOf statement must be one of: - rico:Date The object of a rico:isPublicationDateOf statement must be one of: - rico:RecordResource
The subject of a rico:isToUseDateOf statement must be one of: - rico:Date The object of a rico:isToUseDateOf statement must be one of: - rico:Appellation
The subject of a rico:isWithin statement must be one of: - rico:Date The object of a rico:isWithin statement must be one of: - rico:Date
The subject of a rico:isDateTypeOf statement must be one of: - rico:DateType The object of a rico:isDateTypeOf statement must be one of: - rico:Date
The subject of a rico:isOrWasDemographicGroupOf statement must be one of: - rico:DemographicGroup The object of a rico:isOrWasDemographicGroupOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1682
The subject of a rico:relationHasSource statement must be one of: - rico:DerivationRelation The object of a rico:relationHasSource statement must be one of: - rico:Instantiation
The subject of a rico:relationHasTarget statement must be one of: - rico:DerivationRelation The object of a rico:relationHasTarget statement must be one of: - rico:Instantiation The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:derivationRelation_role statement must be one of: - rico:DerivationRelation The object of a rico:derivationRelation_role statement must be one of: - rico:DerivationRelation
The subject of a rico:relationHasSource statement must be one of: - rico:DescendanceRelation The object of a rico:relationHasSource statement must be one of: - rico:Person The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:DescendanceRelation The object of a rico:relationHasTarget statement must be one of: - rico:Person The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:descendanceRelation_role statement must be one of: - rico:DescendanceRelation The object of a rico:descendanceRelation_role statement must be one of: - rico:DescendanceRelation
The subject of a rico:isDocumentaryFormTypeOf statement must be one of: - rico:DocumentaryFormType The object of a rico:isDocumentaryFormTypeOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b823
The subject of a rico:isOrWasDocumentaryFormTypeOfAllMembersOf statement must be one of: - rico:DocumentaryFormType The object of a rico:isOrWasDocumentaryFormTypeOfAllMembersOf statement must be one of: - rico:RecordSet
isOrWasDocumentaryFormTypeOfAllMembersOf Shape
The subject of a rico:isOrWasDocumentaryFormTypeOfSomeMembersOf statement must be one of: - rico:DocumentaryFormType The object of a rico:isOrWasDocumentaryFormTypeOfSomeMembersOf statement must be one of: - rico:RecordSet
isOrWasDocumentaryFormTypeOfSomeMembersOf Shape
The subject of a rico:affectsOrAffected statement must be one of: - rico:Event The object of a rico:affectsOrAffected statement must be one of: - rico:Thing
The subject of a rico:hadSubevent statement must be one of: - rico:Event The object of a rico:hadSubevent statement must be one of: - rico:Event
The subject of a rico:hasDirectSubevent statement must be one of: - rico:Event The object of a rico:hasDirectSubevent statement must be one of: - rico:Event
The subject of a rico:hasEventType statement must be one of: - rico:Event The object of a rico:hasEventType statement must be one of: - rico:EventType
The subject of a rico:hasOrHadParticipant statement must be one of: - rico:Event The object of a rico:hasOrHadParticipant statement must be one of: - rico:Thing
The subject of a rico:hasOrHadSubevent statement must be one of: - rico:Event The object of a rico:hasOrHadSubevent statement must be one of: - rico:Event
The subject of a rico:hasSubeventTransitive statement must be one of: - rico:Event The object of a rico:hasSubeventTransitive statement must be one of: - rico:Event
The subject of a rico:isDirectSubeventOf statement must be one of: - rico:Event The object of a rico:isDirectSubeventOf statement must be one of: - rico:Event
The subject of a rico:isEventAssociatedWith statement must be one of: - rico:Event The object of a rico:isEventAssociatedWith statement must be one of: - rico:Thing
The subject of a rico:isOrWasSubeventOf statement must be one of: - rico:Event The object of a rico:isOrWasSubeventOf statement must be one of: - rico:Event
The subject of a rico:isSubeventOfTransitive statement must be one of: - rico:Event The object of a rico:isSubeventOfTransitive statement must be one of: - rico:Event
The subject of a rico:occurredAtDate statement must be one of: - rico:Event The object of a rico:occurredAtDate statement must be one of: - rico:Date
The subject of a rico:resultsOrResultedIn statement must be one of: - rico:Event The object of a rico:resultsOrResultedIn statement must be one of: - rico:Thing
The subject of a rico:wasSubeventOf statement must be one of: - rico:Event The object of a rico:wasSubeventOf statement must be one of: - rico:Event
The subject of a rico:relationHasSource statement must be one of: - rico:EventRelation The object of a rico:relationHasSource statement must be one of: - rico:Event The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:EventRelation The object of a rico:relationHasTarget statement must be one of: - rico:Thing The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:eventRelation_role statement must be one of: - rico:EventRelation The object of a rico:eventRelation_role statement must be one of: - rico:EventRelation
The subject of a rico:isEventTypeOf statement must be one of: - rico:EventType The object of a rico:isEventTypeOf statement must be one of: - rico:Event
The subject of a rico:hasExtentType statement must be one of: - rico:Extent The object of a rico:hasExtentType statement must be one of: - rico:ExtentType
The subject of a rico:hasUnitOfMeasurement statement must be one of: - rico:Extent The object of a rico:hasUnitOfMeasurement statement must be one of: - rico:UnitOfMeasurement
The subject of a rico:isExtentOf statement must be one of: - rico:Extent The object of a rico:isExtentOf statement must be one of: - rico:Thing
The subject of a rico:isExtentTypeOf statement must be one of: - rico:ExtentType The object of a rico:isExtentTypeOf statement must be one of: - rico:Extent
The subject of a rico:hasFamilyType statement must be one of: - rico:Family The object of a rico:hasFamilyType statement must be one of: - rico:FamilyType
The subject of a rico:relationConnects statement must be one of: - rico:FamilyRelation The object of a rico:relationConnects statement must be one of: - rico:Person The rico:relationConnects property MUST: - Appear at least 2 times
The subject of a rico:familyRelation_role statement must be one of: - rico:FamilyRelation The object of a rico:familyRelation_role statement must be one of: - rico:FamilyRelation
The subject of a rico:isFamilyTypeOf statement must be one of: - rico:FamilyType The object of a rico:isFamilyTypeOf statement must be one of: - rico:Family
FunctionalEquivalenceRelation validation
The subject of a rico:relationConnects statement must be one of: - rico:FunctionalEquivalenceRelation The object of a rico:relationConnects statement must be one of: - rico:Instantiation The rico:relationConnects property MUST: - Appear at least 2 times
The subject of a rico:functionalEquivalenceRelation_role statement must be one of: - rico:FunctionalEquivalenceRelation The object of a rico:functionalEquivalenceRelation_role statement must be one of: - rico:FunctionalEquivalenceRelation
functionalEquivalenceRelation_role Shape
The subject of a rico:hadSubdivision statement must be one of: - rico:Group The object of a rico:hadSubdivision statement must be one of: - rico:Group
The subject of a rico:hasDirectSubdivision statement must be one of: - rico:Group The object of a rico:hasDirectSubdivision statement must be one of: - rico:Group
The subject of a rico:hasOrHadLeader statement must be one of: - rico:Group The object of a rico:hasOrHadLeader statement must be one of: - rico:Person
The subject of a rico:hasOrHadMember statement must be one of: - rico:Group The object of a rico:hasOrHadMember statement must be one of: - rico:Person
The subject of a rico:hasOrHadPosition statement must be one of: - rico:Group The object of a rico:hasOrHadPosition statement must be one of: - rico:Position
The subject of a rico:hasOrHadSubdivision statement must be one of: - rico:Group The object of a rico:hasOrHadSubdivision statement must be one of: - rico:Group
The subject of a rico:hasSubdivisionTransitive statement must be one of: - rico:Group The object of a rico:hasSubdivisionTransitive statement must be one of: - rico:Group
The subject of a rico:isDirectSubdivisionOf statement must be one of: - rico:Group The object of a rico:isDirectSubdivisionOf statement must be one of: - rico:Group
The subject of a rico:isOrWasSubdivisionOf statement must be one of: - rico:Group The object of a rico:isOrWasSubdivisionOf statement must be one of: - rico:Group
The subject of a rico:isSubdivisionOfTransitive statement must be one of: - rico:Group The object of a rico:isSubdivisionOfTransitive statement must be one of: - rico:Group
The subject of a rico:wasSubdivisionOf statement must be one of: - rico:Group The object of a rico:wasSubdivisionOf statement must be one of: - rico:Group
The subject of a rico:relationHasSource statement must be one of: - rico:GroupSubdivisionRelation The object of a rico:relationHasSource statement must be one of: - rico:Group
The subject of a rico:relationHasTarget statement must be one of: - rico:GroupSubdivisionRelation The object of a rico:relationHasTarget statement must be one of: - rico:Group The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:groupSubdivisionRelation_role statement must be one of: - rico:GroupSubdivisionRelation The object of a rico:groupSubdivisionRelation_role statement must be one of: - rico:GroupSubdivisionRelation
The subject of a rico:hasIdentifierType statement must be one of: - rico:Identifier The object of a rico:hasIdentifierType statement must be one of: - rico:IdentifierType
The subject of a rico:isOrWasIdentifierOf statement must be one of: - rico:Identifier The object of a rico:isOrWasIdentifierOf statement must be one of: - rico:Thing
The subject of a rico:isIdentifierTypeOf statement must be one of: - rico:IdentifierType The object of a rico:isIdentifierTypeOf statement must be one of: - rico:Identifier
The subject of a rico:hadComponent statement must be one of: - rico:Instantiation The object of a rico:hadComponent statement must be one of: - rico:Instantiation
The subject of a rico:hasCarrierType statement must be one of: - rico:Instantiation The object of a rico:hasCarrierType statement must be one of: - rico:CarrierType
The subject of a rico:hasComponentTransitive statement must be one of: - rico:Instantiation The object of a rico:hasComponentTransitive statement must be one of: - rico:Instantiation
The subject of a rico:hasDirectComponent statement must be one of: - rico:Instantiation The object of a rico:hasDirectComponent statement must be one of: - rico:Instantiation
The subject of a rico:hasOrHadComponent statement must be one of: - rico:Instantiation The object of a rico:hasOrHadComponent statement must be one of: - rico:Instantiation
The subject of a rico:hasOrHadDerivedInstantiation statement must be one of: - rico:Instantiation The object of a rico:hasOrHadDerivedInstantiation statement must be one of: - rico:Instantiation
The subject of a rico:hasProductionTechniqueType statement must be one of: - rico:Instantiation The object of a rico:hasProductionTechniqueType statement must be one of: - rico:ProductionTechniqueType
The subject of a rico:hasRepresentationType statement must be one of: - rico:Instantiation The object of a rico:hasRepresentationType statement must be one of: - rico:RepresentationType
The subject of a rico:isComponentOfTransitive statement must be one of: - rico:Instantiation The object of a rico:isComponentOfTransitive statement must be one of: - rico:Instantiation
The subject of a rico:isDirectComponentOf statement must be one of: - rico:Instantiation The object of a rico:isDirectComponentOf statement must be one of: - rico:Instantiation
The subject of a rico:isFunctionallyEquivalentTo statement must be one of: - rico:Instantiation The object of a rico:isFunctionallyEquivalentTo statement must be one of: - rico:Instantiation
The subject of a rico:isInstantiationAssociatedWithInstantiation statement must be one of: - rico:Instantiation The object of a rico:isInstantiationAssociatedWithInstantiation statement must be one of: - rico:Instantiation
isInstantiationAssociatedWithInstantiation Shape
The subject of a rico:isOrWasAnalogueInstantiationOf statement must be one of: - rico:Instantiation The object of a rico:isOrWasAnalogueInstantiationOf statement must be one of: - rico:RecordResource
The subject of a rico:isOrWasComponentOf statement must be one of: - rico:Instantiation The object of a rico:isOrWasComponentOf statement must be one of: - rico:Instantiation
The subject of a rico:isOrWasDerivedFromInstantiation statement must be one of: - rico:Instantiation The object of a rico:isOrWasDerivedFromInstantiation statement must be one of: - rico:Instantiation
The subject of a rico:isOrWasDigitalInstantiationOf statement must be one of: - rico:Instantiation The object of a rico:isOrWasDigitalInstantiationOf statement must be one of: - rico:RecordResource
The subject of a rico:isOrWasInstantiationOf statement must be one of: - rico:Instantiation The object of a rico:isOrWasInstantiationOf statement must be one of: - rico:RecordResource
The subject of a rico:migratedFrom statement must be one of: - rico:Instantiation The object of a rico:migratedFrom statement must be one of: - rico:Instantiation
The subject of a rico:migratedInto statement must be one of: - rico:Instantiation The object of a rico:migratedInto statement must be one of: - rico:Instantiation
The subject of a rico:wasComponentOf statement must be one of: - rico:Instantiation The object of a rico:wasComponentOf statement must be one of: - rico:Instantiation
InstantiationToInstantiationRelation validation
InstantiationToInstantiationRelation Shape
The subject of a rico:relationConnects statement must be one of: - rico:InstantiationToInstantiationRelation The object of a rico:relationConnects statement must be one of: - rico:Instantiation The rico:relationConnects property MUST: - Appear at least 2 times
The subject of a rico:instantiationToInstantiationRelation_role statement must be one of: - rico:InstantiationToInstantiationRelation The object of a rico:instantiationToInstantiationRelation_role statement must be one of: - rico:InstantiationToInstantiationRelation
instantiationToInstantiationRelation_role Shape
IntellectualPropertyRightsRelation validation
IntellectualPropertyRightsRelation Shape
The subject of a rico:relationHasSource statement must be one of: - rico:IntellectualPropertyRightsRelation The object of a rico:relationHasSource statement must be one of: - rico:Position - rico:Person - rico:Group The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:IntellectualPropertyRightsRelation The object of a rico:relationHasTarget statement must be one of: - rico:RecordResource - rico:Instantiation The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:intellectualPropertyRightsRelation_role statement must be one of: - rico:IntellectualPropertyRightsRelation The object of a rico:intellectualPropertyRightsRelation_role statement must be one of: - rico:IntellectualPropertyRightsRelation
intellectualPropertyRightsRelation_role Shape
The subject of a rico:relationHasSource statement must be one of: - rico:KnowingOfRelation The object of a rico:relationHasSource statement must be one of: - rico:Person The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:KnowingOfRelation The object of a rico:relationHasTarget statement must be one of: - rico:Person The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:knowingOfRelation_role statement must be one of: - rico:KnowingOfRelation The object of a rico:knowingOfRelation_role statement must be one of: - rico:KnowingOfRelation
The subject of a rico:relationConnects statement must be one of: - rico:KnowingRelation The object of a rico:relationConnects statement must be one of: - rico:Person The rico:relationConnects property MUST: - Appear at least 2 times
The subject of a rico:knowingRelation_role statement must be one of: - rico:KnowingRelation The object of a rico:knowingRelation_role statement must be one of: - rico:KnowingRelation
The subject of a rico:isOrWasLanguageOf statement must be one of: - rico:Language The object of a rico:isOrWasLanguageOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b955
The subject of a rico:isOrWasLanguageOfAllMembersOf statement must be one of: - rico:Language The object of a rico:isOrWasLanguageOfAllMembersOf statement must be one of: - rico:RecordSet
The subject of a rico:isOrWasLanguageOfSomeMembersOf statement must be one of: - rico:Language The object of a rico:isOrWasLanguageOfSomeMembersOf statement must be one of: - rico:RecordSet
The subject of a rico:leadershipWithPosition statement must be one of: - rico:LeadershipRelation The object of a rico:leadershipWithPosition statement must be one of: - rico:Position The rico:leadershipWithPosition property MUST: - Appear no more than 0 times
The subject of a rico:relationHasSource statement must be one of: - rico:LeadershipRelation The object of a rico:relationHasSource statement must be one of: - rico:Person The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:LeadershipRelation The object of a rico:relationHasTarget statement must be one of: - rico:Group The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:leadershipRelation_role statement must be one of: - rico:LeadershipRelation The object of a rico:leadershipRelation_role statement must be one of: - rico:LeadershipRelation
The subject of a rico:leadershipWithPosition statement must be one of: - rico:LeadershipRelation The object of a rico:leadershipWithPosition statement must be one of: - rico:Position
The subject of a rico:isOrWasLegalStatusOf statement must be one of: - rico:LegalStatus The object of a rico:isOrWasLegalStatusOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b975
The subject of a rico:isOrWasLegalStatusOfAllMembersOf statement must be one of: - rico:LegalStatus The object of a rico:isOrWasLegalStatusOfAllMembersOf statement must be one of: - rico:RecordSet
The subject of a rico:isOrWasLegalStatusOfSomeMembersOf statement must be one of: - rico:LegalStatus The object of a rico:isOrWasLegalStatusOfSomeMembersOf statement must be one of: - rico:RecordSet
The subject of a rico:relationHasSource statement must be one of: - rico:ManagementRelation The object of a rico:relationHasSource statement must be one of: - rico:Agent The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:ManagementRelation The object of a rico:relationHasTarget statement must be one of: - rico:Instantiation - rico:RecordResource The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:managementRelation_role statement must be one of: - rico:ManagementRelation The object of a rico:managementRelation_role statement must be one of: - rico:ManagementRelation
The subject of a rico:authorizes statement must be one of: - rico:Mandate The object of a rico:authorizes statement must be one of: - rico:Agent
The subject of a rico:hasOrHadMandateType statement must be one of: - rico:Mandate The object of a rico:hasOrHadMandateType statement must be one of: - rico:MandateType
The subject of a rico:asConcernsActivity statement must be one of: - rico:MandateRelation The object of a rico:asConcernsActivity statement must be one of: - rico:Activity The rico:asConcernsActivity property MUST: - Appear at least 1 times
The subject of a rico:relationHasSource statement must be one of: - rico:MandateRelation The object of a rico:relationHasSource statement must be one of: - rico:Mandate The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:MandateRelation The object of a rico:relationHasTarget statement must be one of: - rico:Agent The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:authorizingAgent statement must be one of: - rico:MandateRelation The object of a rico:authorizingAgent statement must be one of: - rico:Agent
The subject of a rico:mandateRelation_role statement must be one of: - rico:MandateRelation The object of a rico:mandateRelation_role statement must be one of: - rico:MandateRelation
The subject of a rico:isOrWasMandateTypeOf statement must be one of: - rico:MandateType The object of a rico:isOrWasMandateTypeOf statement must be one of: - rico:Mandate
The subject of a rico:membershipWithPosition statement must be one of: - rico:MembershipRelation The object of a rico:membershipWithPosition statement must be one of: - rico:Position The rico:membershipWithPosition property MUST: - Appear no more than 0 times
The subject of a rico:relationHasSource statement must be one of: - rico:MembershipRelation The object of a rico:relationHasSource statement must be one of: - rico:Group
The subject of a rico:relationHasTarget statement must be one of: - rico:MembershipRelation The object of a rico:relationHasTarget statement must be one of: - rico:Person The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:membershipRelation_role statement must be one of: - rico:MembershipRelation The object of a rico:membershipRelation_role statement must be one of: - rico:MembershipRelation
The subject of a rico:membershipWithPosition statement must be one of: - rico:MembershipRelation The object of a rico:membershipWithPosition statement must be one of: - rico:Position
The subject of a rico:relationHasSource statement must be one of: - rico:MigrationRelation The object of a rico:relationHasSource statement must be one of: - rico:Instantiation
The subject of a rico:relationHasTarget statement must be one of: - rico:MigrationRelation The object of a rico:relationHasTarget statement must be one of: - rico:Instantiation The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:migrationRelation_role statement must be one of: - rico:MigrationRelation The object of a rico:migrationRelation_role statement must be one of: - rico:MigrationRelation
The subject of a rico:isOrWasNameOf statement must be one of: - rico:Name The object of a rico:isOrWasNameOf statement must be one of: - rico:Thing
The subject of a rico:isOrWasOccupationTypeOf statement must be one of: - rico:OccupationType The object of a rico:isOrWasOccupationTypeOf statement must be one of: - rico:Person
OrganicOrFunctionalProvenanceRelation validation
OrganicOrFunctionalProvenanceRelation Shape
The subject of a rico:relationHasSource statement must be one of: - rico:OrganicOrFunctionalProvenanceRelation The object of a rico:relationHasSource statement must be one of: - rico:Instantiation - rico:RecordResource The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:OrganicOrFunctionalProvenanceRelation The object of a rico:relationHasTarget statement must be one of: - rico:Agent - rico:Activity The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:organicOrFunctionalProvenanceRelation_role statement must be one of: - rico:OrganicOrFunctionalProvenanceRelation The object of a rico:organicOrFunctionalProvenanceRelation_role statement must be one of: - rico:OrganicOrFunctionalProvenanceRelation
organicOrFunctionalProvenanceRelation_role Shape
The subject of a rico:relationHasSource statement must be one of: - rico:OrganicProvenanceRelation The object of a rico:relationHasSource statement must be one of: - rico:Instantiation - rico:RecordResource The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:OrganicProvenanceRelation The object of a rico:relationHasTarget statement must be one of: - rico:Agent The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:organicProvenanceRelation_role statement must be one of: - rico:OrganicProvenanceRelation The object of a rico:organicProvenanceRelation_role statement must be one of: - rico:OrganicProvenanceRelation
The subject of a rico:relationHasSource statement must be one of: - rico:OwnershipRelation The object of a rico:relationHasSource statement must be one of: - rico:Position - rico:Group - rico:Person The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:OwnershipRelation The object of a rico:relationHasTarget statement must be one of: - rico:Thing The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:ownershipRelation_role statement must be one of: - rico:OwnershipRelation The object of a rico:ownershipRelation_role statement must be one of: - rico:OwnershipRelation
The subject of a rico:relationHasSource statement must be one of: - rico:PerformanceRelation The object of a rico:relationHasSource statement must be one of: - rico:Activity The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:PerformanceRelation The object of a rico:relationHasTarget statement must be one of: - rico:Agent The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:performanceRelation_role statement must be one of: - rico:PerformanceRelation The object of a rico:performanceRelation_role statement must be one of: - rico:PerformanceRelation
The subject of a rico:hasAncestor statement must be one of: - rico:Person The object of a rico:hasAncestor statement must be one of: - rico:Person
The subject of a rico:hasBirthDate statement must be one of: - rico:Person The object of a rico:hasBirthDate statement must be one of: - rico:Date
The subject of a rico:hasBirthPlace statement must be one of: - rico:Person The object of a rico:hasBirthPlace statement must be one of: - rico:Place
The subject of a rico:hasChild statement must be one of: - rico:Person The object of a rico:hasChild statement must be one of: - rico:Person
The subject of a rico:hasDeathDate statement must be one of: - rico:Person The object of a rico:hasDeathDate statement must be one of: - rico:Date
The subject of a rico:hasDeathPlace statement must be one of: - rico:Person The object of a rico:hasDeathPlace statement must be one of: - rico:Place
The subject of a rico:hasDescendant statement must be one of: - rico:Person The object of a rico:hasDescendant statement must be one of: - rico:Person
The subject of a rico:hasFamilyAssociationWith statement must be one of: - rico:Person The object of a rico:hasFamilyAssociationWith statement must be one of: - rico:Person
The subject of a rico:hasOrHadCorrespondent statement must be one of: - rico:Person The object of a rico:hasOrHadCorrespondent statement must be one of: - rico:Person
The subject of a rico:hasOrHadEmployer statement must be one of: - rico:Person The object of a rico:hasOrHadEmployer statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b515
The subject of a rico:hasOrHadOccupationOfType statement must be one of: - rico:Person The object of a rico:hasOrHadOccupationOfType statement must be one of: - rico:OccupationType
The subject of a rico:hasOrHadSpouse statement must be one of: - rico:Person The object of a rico:hasOrHadSpouse statement must be one of: - rico:Person
The subject of a rico:hasOrHadStudent statement must be one of: - rico:Person The object of a rico:hasOrHadStudent statement must be one of: - rico:Person
The subject of a rico:hasOrHadTeacher statement must be one of: - rico:Person The object of a rico:hasOrHadTeacher statement must be one of: - rico:Person
The subject of a rico:hasSibling statement must be one of: - rico:Person The object of a rico:hasSibling statement must be one of: - rico:Person
The subject of a rico:isChildOf statement must be one of: - rico:Person The object of a rico:isChildOf statement must be one of: - rico:Person
The subject of a rico:isOrWasLeaderOf statement must be one of: - rico:Person The object of a rico:isOrWasLeaderOf statement must be one of: - rico:Group
The subject of a rico:isOrWasMemberOf statement must be one of: - rico:Person The object of a rico:isOrWasMemberOf statement must be one of: - rico:Group
The subject of a rico:knownBy statement must be one of: - rico:Person The object of a rico:knownBy statement must be one of: - rico:Person
The subject of a rico:knows statement must be one of: - rico:Person The object of a rico:knows statement must be one of: - rico:Person
The subject of a rico:knowsOf statement must be one of: - rico:Person The object of a rico:knowsOf statement must be one of: - rico:Person
The subject of a rico:occupiesOrOccupied statement must be one of: - rico:Person The object of a rico:occupiesOrOccupied statement must be one of: - rico:Position
The subject of a rico:hasOrHadCoordinates statement must be one of: - rico:PhysicalLocation The object of a rico:hasOrHadCoordinates statement must be one of: - rico:Coordinates
The subject of a rico:isOrWasPhysicalLocationOf statement must be one of: - rico:PhysicalLocation The object of a rico:isOrWasPhysicalLocationOf statement must be one of: - rico:Place
The subject of a rico:contained statement must be one of: - rico:Place The object of a rico:contained statement must be one of: - rico:Place
The subject of a rico:containsOrContained statement must be one of: - rico:Place The object of a rico:containsOrContained statement must be one of: - rico:Place
The subject of a rico:containsTransitive statement must be one of: - rico:Place The object of a rico:containsTransitive statement must be one of: - rico:Place
The subject of a rico:directlyContains statement must be one of: - rico:Place The object of a rico:directlyContains statement must be one of: - rico:Place
The subject of a rico:hasOrHadPhysicalLocation statement must be one of: - rico:Place The object of a rico:hasOrHadPhysicalLocation statement must be one of: - rico:PhysicalLocation
The subject of a rico:hasOrHadPlaceName statement must be one of: - rico:Place The object of a rico:hasOrHadPlaceName statement must be one of: - rico:PlaceName
The subject of a rico:hasOrHadPlaceType statement must be one of: - rico:Place The object of a rico:hasOrHadPlaceType statement must be one of: - rico:PlaceType
The subject of a rico:isBirthPlaceOf statement must be one of: - rico:Place The object of a rico:isBirthPlaceOf statement must be one of: - rico:Person
The subject of a rico:isContainedByTransitive statement must be one of: - rico:Place The object of a rico:isContainedByTransitive statement must be one of: - rico:Place
The subject of a rico:isDeathPlaceOf statement must be one of: - rico:Place The object of a rico:isDeathPlaceOf statement must be one of: - rico:Person
The subject of a rico:isDirectlyContainedBy statement must be one of: - rico:Place The object of a rico:isDirectlyContainedBy statement must be one of: - rico:Place
The subject of a rico:isOrWasAdjacentTo statement must be one of: - rico:Place The object of a rico:isOrWasAdjacentTo statement must be one of: - rico:Place
The subject of a rico:isOrWasContainedBy statement must be one of: - rico:Place The object of a rico:isOrWasContainedBy statement must be one of: - rico:Place
The subject of a rico:isOrWasJurisdictionOf statement must be one of: - rico:Place The object of a rico:isOrWasJurisdictionOf statement must be one of: - rico:Agent
The subject of a rico:isOrWasLocationOf statement must be one of: - rico:Place The object of a rico:isOrWasLocationOf statement must be one of: - rico:Thing
The subject of a rico:isOrWasLocationOfAgent statement must be one of: - rico:Place The object of a rico:isOrWasLocationOfAgent statement must be one of: - rico:Agent
The subject of a rico:isPlaceAssociatedWith statement must be one of: - rico:Place The object of a rico:isPlaceAssociatedWith statement must be one of: - rico:Thing
The subject of a rico:isPlaceAssociatedWithAgent statement must be one of: - rico:Place The object of a rico:isPlaceAssociatedWithAgent statement must be one of: - rico:Agent
The subject of a rico:overlapsOrOverlapped statement must be one of: - rico:Place The object of a rico:overlapsOrOverlapped statement must be one of: - rico:Place
The subject of a rico:wasContainedBy statement must be one of: - rico:Place The object of a rico:wasContainedBy statement must be one of: - rico:Place
The subject of a rico:isOrWasPlaceNameOf statement must be one of: - rico:PlaceName The object of a rico:isOrWasPlaceNameOf statement must be one of: - rico:Place
The subject of a rico:relationHasSource statement must be one of: - rico:PlaceRelation The object of a rico:relationHasSource statement must be one of: - rico:Place
The subject of a rico:relationHasTarget statement must be one of: - rico:PlaceRelation The object of a rico:relationHasTarget statement must be one of: - rico:Thing The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:placeRelation_role statement must be one of: - rico:PlaceRelation The object of a rico:placeRelation_role statement must be one of: - rico:PlaceRelation
The subject of a rico:isOrWasPlaceTypeOf statement must be one of: - rico:PlaceType The object of a rico:isOrWasPlaceTypeOf statement must be one of: - rico:Place
The subject of a rico:existsOrExistedIn statement must be one of: - rico:Position The object of a rico:existsOrExistedIn statement must be one of: - rico:Group
The subject of a rico:isOrWasOccupiedBy statement must be one of: - rico:Position The object of a rico:isOrWasOccupiedBy statement must be one of: - rico:Person
The subject of a rico:positionIsContextOfLeadershipRelation statement must be one of: - rico:Position The object of a rico:positionIsContextOfLeadershipRelation statement must be one of: - rico:LeadershipRelation
positionIsContextOfLeadershipRelation Shape
The subject of a rico:positionIsContextOfMembershipRelation statement must be one of: - rico:Position The object of a rico:positionIsContextOfMembershipRelation statement must be one of: - rico:MembershipRelation
positionIsContextOfMembershipRelation Shape
The subject of a rico:relationHasSource statement must be one of: - rico:PositionHoldingRelation The object of a rico:relationHasSource statement must be one of: - rico:Person The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:PositionHoldingRelation The object of a rico:relationHasTarget statement must be one of: - rico:Position The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:positionHoldingRelation_role statement must be one of: - rico:PositionHoldingRelation The object of a rico:positionHoldingRelation_role statement must be one of: - rico:PositionHoldingRelation
The subject of a rico:relationHasSource statement must be one of: - rico:PositionToGroupRelation The object of a rico:relationHasSource statement must be one of: - rico:Position The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:PositionToGroupRelation The object of a rico:relationHasTarget statement must be one of: - rico:Group
The subject of a rico:positionToGroupRelation_role statement must be one of: - rico:PositionToGroupRelation The object of a rico:positionToGroupRelation_role statement must be one of: - rico:PositionToGroupRelation
The subject of a rico:isProductionTechniqueTypeOf statement must be one of: - rico:ProductionTechniqueType The object of a rico:isProductionTechniqueTypeOf statement must be one of: - rico:Instantiation
The subject of a rico:proxyFor statement must be one of: - rico:Proxy The object of a rico:proxyFor statement must be one of: - rico:RecordResource
The subject of a rico:proxyIn statement must be one of: - rico:Proxy The object of a rico:proxyIn statement must be one of: - rico:RecordSet
The subject of a rico:hasAuthor statement must be one of: - rico:Record The object of a rico:hasAuthor statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b369
The subject of a rico:describesOrDescribed statement must be one of: - rico:RecordResource The object of a rico:describesOrDescribed statement must be one of: - rico:Thing
The subject of a rico:evidences statement must be one of: - rico:RecordResource The object of a rico:evidences statement must be one of: - rico:Relation
The subject of a rico:expressesOrExpressed statement must be one of: - rico:RecordResource The object of a rico:expressesOrExpressed statement must be one of: - rico:Rule
The subject of a rico:hasCopy statement must be one of: - rico:RecordResource The object of a rico:hasCopy statement must be one of: - rico:RecordResource
The subject of a rico:hasGeneticLinkToRecordResource statement must be one of: - rico:RecordResource The object of a rico:hasGeneticLinkToRecordResource statement must be one of: - rico:RecordResource
The subject of a rico:hasOrHadAnalogueInstantiation statement must be one of: - rico:RecordResource The object of a rico:hasOrHadAnalogueInstantiation statement must be one of: - rico:Instantiation
The subject of a rico:hasOrHadDigitalInstantiation statement must be one of: - rico:RecordResource The object of a rico:hasOrHadDigitalInstantiation statement must be one of: - rico:Instantiation
The subject of a rico:hasOrHadInstantiation statement must be one of: - rico:RecordResource The object of a rico:hasOrHadInstantiation statement must be one of: - rico:Instantiation
The subject of a rico:hasOrHadMainSubject statement must be one of: - rico:RecordResource The object of a rico:hasOrHadMainSubject statement must be one of: - rico:Thing
The subject of a rico:hasOrHadSubject statement must be one of: - rico:RecordResource The object of a rico:hasOrHadSubject statement must be one of: - rico:Thing
The subject of a rico:hasPublicationDate statement must be one of: - rico:RecordResource The object of a rico:hasPublicationDate statement must be one of: - rico:Date
The subject of a rico:hasPublisher statement must be one of: - rico:RecordResource The object of a rico:hasPublisher statement must be one of: - rico:Agent
The subject of a rico:hasReply statement must be one of: - rico:RecordResource The object of a rico:hasReply statement must be one of: - rico:RecordResource
The subject of a rico:isCopyOf statement must be one of: - rico:RecordResource The object of a rico:isCopyOf statement must be one of: - rico:RecordResource
The subject of a rico:isRecordResourceAssociatedWithRecordResource statement must be one of: - rico:RecordResource The object of a rico:isRecordResourceAssociatedWithRecordResource statement must be one of: - rico:RecordResource
isRecordResourceAssociatedWithRecordResource Shape
The subject of a rico:isReplyTo statement must be one of: - rico:RecordResource The object of a rico:isReplyTo statement must be one of: - rico:RecordResource
RecordResourceGeneticRelation validation
The subject of a rico:relationConnects statement must be one of: - rico:RecordResourceGeneticRelation The object of a rico:relationConnects statement must be one of: - rico:RecordResource The rico:relationConnects property MUST: - Appear at least 2 times
The subject of a rico:recordResourceGeneticRelation_role statement must be one of: - rico:RecordResourceGeneticRelation The object of a rico:recordResourceGeneticRelation_role statement must be one of: - rico:RecordResourceGeneticRelation
recordResourceGeneticRelation_role Shape
RecordResourceHoldingRelation validation
The subject of a rico:relationHasSource statement must be one of: - rico:RecordResourceHoldingRelation The object of a rico:relationHasSource statement must be one of: - rico:Agent The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:RecordResourceHoldingRelation The object of a rico:relationHasTarget statement must be one of: - rico:RecordResource - rico:Instantiation The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:recordResourceHoldingRelation_role statement must be one of: - rico:RecordResourceHoldingRelation The object of a rico:recordResourceHoldingRelation_role statement must be one of: - rico:RecordResourceHoldingRelation
recordResourceHoldingRelation_role Shape
RecordResourceToInstantiationRelation validation
RecordResourceToInstantiationRelation Shape
The subject of a rico:relationHasSource statement must be one of: - rico:RecordResourceToInstantiationRelation The object of a rico:relationHasSource statement must be one of: - rico:RecordResource
The subject of a rico:relationHasTarget statement must be one of: - rico:RecordResourceToInstantiationRelation The object of a rico:relationHasTarget statement must be one of: - rico:Instantiation The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:recordResourceToInstantiationRelation_role statement must be one of: - rico:RecordResourceToInstantiationRelation The object of a rico:recordResourceToInstantiationRelation_role statement must be one of: - rico:RecordResourceToInstantiationRelation
recordResourceToInstantiationRelation_role Shape
RecordResourceToRecordResourceRelation validation
RecordResourceToRecordResourceRelation Shape
The subject of a rico:relationConnects statement must be one of: - rico:RecordResourceToRecordResourceRelation The object of a rico:relationConnects statement must be one of: - rico:RecordResource The rico:relationConnects property MUST: - Appear at least 2 times
The subject of a rico:recordResourceToRecordResourceRelation_role statement must be one of: - rico:RecordResourceToRecordResourceRelation The object of a rico:recordResourceToRecordResourceRelation_role statement must be one of: - rico:RecordResourceToRecordResourceRelation
recordResourceToRecordResourceRelation_role Shape
The subject of a rico:directlyIncludes statement must be one of: - rico:RecordSet The object of a rico:directlyIncludes statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b287
The subject of a rico:hasOrHadAllMembersWithCategory statement must be one of: - rico:RecordSet The object of a rico:hasOrHadAllMembersWithCategory statement must be one of: - rico:Type
The subject of a rico:hasOrHadAllMembersWithContentType statement must be one of: - rico:RecordSet The object of a rico:hasOrHadAllMembersWithContentType statement must be one of: - rico:ContentType
The subject of a rico:hasOrHadAllMembersWithCreationDate statement must be one of: - rico:RecordSet The object of a rico:hasOrHadAllMembersWithCreationDate statement must be one of: - rico:Date
hasOrHadAllMembersWithCreationDate Shape
The subject of a rico:hasOrHadAllMembersWithDocumentaryFormType statement must be one of: - rico:RecordSet The object of a rico:hasOrHadAllMembersWithDocumentaryFormType statement must be one of: - rico:DocumentaryFormType
hasOrHadAllMembersWithDocumentaryFormType Shape
The subject of a rico:hasOrHadAllMembersWithLanguage statement must be one of: - rico:RecordSet The object of a rico:hasOrHadAllMembersWithLanguage statement must be one of: - rico:Language
The subject of a rico:hasOrHadAllMembersWithLegalStatus statement must be one of: - rico:RecordSet The object of a rico:hasOrHadAllMembersWithLegalStatus statement must be one of: - rico:LegalStatus
The subject of a rico:hasOrHadAllMembersWithRecordState statement must be one of: - rico:RecordSet The object of a rico:hasOrHadAllMembersWithRecordState statement must be one of: - rico:RecordState
The subject of a rico:hasOrHadMostMembersWithCreationDate statement must be one of: - rico:RecordSet The object of a rico:hasOrHadMostMembersWithCreationDate statement must be one of: - rico:Date
hasOrHadMostMembersWithCreationDate Shape
The subject of a rico:hasOrHadSomeMembersWithCategory statement must be one of: - rico:RecordSet The object of a rico:hasOrHadSomeMembersWithCategory statement must be one of: - rico:Type
The subject of a rico:hasOrHadSomeMembersWithContentType statement must be one of: - rico:RecordSet The object of a rico:hasOrHadSomeMembersWithContentType statement must be one of: - rico:ContentType
hasOrHadSomeMembersWithContentType Shape
The subject of a rico:hasOrHadSomeMembersWithCreationDate statement must be one of: - rico:RecordSet The object of a rico:hasOrHadSomeMembersWithCreationDate statement must be one of: - rico:Date
hasOrHadSomeMembersWithCreationDate Shape
The subject of a rico:hasOrHadSomeMembersWithDocumentaryFormType statement must be one of: - rico:RecordSet The object of a rico:hasOrHadSomeMembersWithDocumentaryFormType statement must be one of: - rico:DocumentaryFormType
hasOrHadSomeMembersWithDocumentaryFormType Shape
The subject of a rico:hasOrHadSomeMembersWithLanguage statement must be one of: - rico:RecordSet The object of a rico:hasOrHadSomeMembersWithLanguage statement must be one of: - rico:Language
The subject of a rico:hasOrHadSomeMembersWithLegalStatus statement must be one of: - rico:RecordSet The object of a rico:hasOrHadSomeMembersWithLegalStatus statement must be one of: - rico:LegalStatus
hasOrHadSomeMembersWithLegalStatus Shape
The subject of a rico:hasOrHadSomeMembersWithRecordState statement must be one of: - rico:RecordSet The object of a rico:hasOrHadSomeMembersWithRecordState statement must be one of: - rico:RecordState
hasOrHadSomeMembersWithRecordState Shape
The subject of a rico:hasRecordSetType statement must be one of: - rico:RecordSet The object of a rico:hasRecordSetType statement must be one of: - rico:RecordSetType
The subject of a rico:included statement must be one of: - rico:RecordSet The object of a rico:included statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b713
The subject of a rico:includesOrIncluded statement must be one of: - rico:RecordSet The object of a rico:includesOrIncluded statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1923
The subject of a rico:includesTransitive statement must be one of: - rico:RecordSet The object of a rico:includesTransitive statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1635
The subject of a rico:isRecordSetTypeOf statement must be one of: - rico:RecordSetType The object of a rico:isRecordSetTypeOf statement must be one of: - rico:RecordSet
The subject of a rico:isOrWasRecordStateOfAllMembersOf statement must be one of: - rico:RecordState The object of a rico:isOrWasRecordStateOfAllMembersOf statement must be one of: - rico:RecordSet
The subject of a rico:isOrWasRecordStateOfSomeMembersOf statement must be one of: - rico:RecordState The object of a rico:isOrWasRecordStateOfSomeMembersOf statement must be one of: - rico:RecordSet
The subject of a rico:isRecordStateOf statement must be one of: - rico:RecordState The object of a rico:isRecordStateOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1086
The subject of a rico:isEvidencedBy statement must be one of: - rico:Relation The object of a rico:isEvidencedBy statement must be one of: - rico:RecordResource
The subject of a rico:relationConnects statement must be one of: - rico:Relation The object of a rico:relationConnects statement must be one of: - rico:Thing
The subject of a rico:relationHasContext statement must be one of: - rico:Relation The object of a rico:relationHasContext statement must be one of: - rico:Thing
The subject of a rico:relationHasSource statement must be one of: - rico:Relation The object of a rico:relationHasSource statement must be one of: - rico:Thing
The subject of a rico:relationHasTarget statement must be one of: - rico:Relation The object of a rico:relationHasTarget statement must be one of: - rico:Thing
The subject of a rico:relation_role statement must be one of: - rico:Relation The object of a rico:relation_role statement must be one of: - rico:Relation
The subject of a rico:isRepresentationTypeOf statement must be one of: - rico:RepresentationType The object of a rico:isRepresentationTypeOf statement must be one of: - rico:Instantiation
The subject of a rico:roleIsContextOfCreationRelation statement must be one of: - rico:RoleType The object of a rico:roleIsContextOfCreationRelation statement must be one of: - rico:CreationRelation
The subject of a rico:hasOrHadRuleType statement must be one of: - rico:Rule The object of a rico:hasOrHadRuleType statement must be one of: - rico:RuleType
The subject of a rico:isOrWasEnforcedBy statement must be one of: - rico:Rule The object of a rico:isOrWasEnforcedBy statement must be one of: - rico:Agent
The subject of a rico:isOrWasExpressedBy statement must be one of: - rico:Rule The object of a rico:isOrWasExpressedBy statement must be one of: - rico:RecordResource
The subject of a rico:isRuleAssociatedWith statement must be one of: - rico:Rule The object of a rico:isRuleAssociatedWith statement must be one of: - rico:Thing
The subject of a rico:issuedBy statement must be one of: - rico:Rule The object of a rico:issuedBy statement must be one of: - rico:Agent
The subject of a rico:regulatesOrRegulated statement must be one of: - rico:Rule The object of a rico:regulatesOrRegulated statement must be one of: - rico:Thing
The subject of a rico:relationHasSource statement must be one of: - rico:RuleRelation The object of a rico:relationHasSource statement must be one of: - rico:Rule The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:RuleRelation The object of a rico:relationHasTarget statement must be one of: - rico:Thing The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:ruleRelation_role statement must be one of: - rico:RuleRelation The object of a rico:ruleRelation_role statement must be one of: - rico:RuleRelation
The subject of a rico:isOrWasRuleTypeOf statement must be one of: - rico:RuleType The object of a rico:isOrWasRuleTypeOf statement must be one of: - rico:Rule
The subject of a rico:relationHasSource statement must be one of: - rico:SequentialRelation The object of a rico:relationHasSource statement must be one of: - rico:Thing The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:SequentialRelation The object of a rico:relationHasTarget statement must be one of: - rico:Thing The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:sequentialRelation_role statement must be one of: - rico:SequentialRelation The object of a rico:sequentialRelation_role statement must be one of: - rico:SequentialRelation
The subject of a rico:relationConnects statement must be one of: - rico:SiblingRelation The object of a rico:relationConnects statement must be one of: - rico:Person The rico:relationConnects property MUST: - Appear at least 2 times
The subject of a rico:siblingRelation_role statement must be one of: - rico:SiblingRelation The object of a rico:siblingRelation_role statement must be one of: - rico:SiblingRelation
The subject of a rico:relationConnects statement must be one of: - rico:SpouseRelation The object of a rico:relationConnects statement must be one of: - rico:Person The rico:relationConnects property MUST: - Appear at least 2 times
The subject of a rico:spouseRelation_role statement must be one of: - rico:SpouseRelation The object of a rico:spouseRelation_role statement must be one of: - rico:SpouseRelation
The subject of a rico:relationHasSource statement must be one of: - rico:TeachingRelation The object of a rico:relationHasSource statement must be one of: - rico:Person The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:TeachingRelation The object of a rico:relationHasTarget statement must be one of: - rico:Person The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:teachingRelation_role statement must be one of: - rico:TeachingRelation The object of a rico:teachingRelation_role statement must be one of: - rico:TeachingRelation
The subject of a rico:relationHasSource statement must be one of: - rico:TemporalRelation The object of a rico:relationHasSource statement must be one of: - rico:Thing The rico:relationHasSource property MUST: - Appear at least 1 times
The subject of a rico:relationHasTarget statement must be one of: - rico:TemporalRelation The object of a rico:relationHasTarget statement must be one of: - rico:Thing The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:temporalRelation_role statement must be one of: - rico:TemporalRelation The object of a rico:temporalRelation_role statement must be one of: - rico:TemporalRelation
The subject of a rico:directlyFollowsInSequence statement must be one of: - rico:Thing The object of a rico:directlyFollowsInSequence statement must be one of: - rico:Thing
The subject of a rico:directlyPrecedesInSequence statement must be one of: - rico:Thing The object of a rico:directlyPrecedesInSequence statement must be one of: - rico:Thing
The subject of a rico:followedInSequence statement must be one of: - rico:Thing The object of a rico:followedInSequence statement must be one of: - rico:Thing
The subject of a rico:followsInSequenceTransitive statement must be one of: - rico:Thing The object of a rico:followsInSequenceTransitive statement must be one of: - rico:Thing
The subject of a rico:followsInTime statement must be one of: - rico:Thing The object of a rico:followsInTime statement must be one of: - rico:Thing
The subject of a rico:followsOrFollowed statement must be one of: - rico:Thing The object of a rico:followsOrFollowed statement must be one of: - rico:Thing
The subject of a rico:hadPart statement must be one of: - rico:Thing The object of a rico:hadPart statement must be one of: - rico:Thing
The subject of a rico:hasBeginningDate statement must be one of: - rico:Thing The object of a rico:hasBeginningDate statement must be one of: - rico:Date
The subject of a rico:hasDestructionDate statement must be one of: - rico:Thing The object of a rico:hasDestructionDate statement must be one of: - rico:Date
The subject of a rico:hasDirectPart statement must be one of: - rico:Thing The object of a rico:hasDirectPart statement must be one of: - rico:Thing
The subject of a rico:hasEndDate statement must be one of: - rico:Thing The object of a rico:hasEndDate statement must be one of: - rico:Date
The subject of a rico:hasExtent statement must be one of: - rico:Thing The object of a rico:hasExtent statement must be one of: - rico:Extent
The subject of a rico:hasModificationDate statement must be one of: - rico:Thing The object of a rico:hasModificationDate statement must be one of: - rico:Date
The subject of a rico:hasOrHadAppellation statement must be one of: - rico:Thing The object of a rico:hasOrHadAppellation statement must be one of: - rico:Appellation
The subject of a rico:hasOrHadCategory statement must be one of: - rico:Thing The object of a rico:hasOrHadCategory statement must be one of: - rico:Type
The subject of a rico:hasOrHadIdentifier statement must be one of: - rico:Thing The object of a rico:hasOrHadIdentifier statement must be one of: - rico:Identifier
The subject of a rico:hasOrHadLocation statement must be one of: - rico:Thing The object of a rico:hasOrHadLocation statement must be one of: - rico:Place
The subject of a rico:hasOrHadName statement must be one of: - rico:Thing The object of a rico:hasOrHadName statement must be one of: - rico:Name
The subject of a rico:hasOrHadOwner statement must be one of: - rico:Thing The object of a rico:hasOrHadOwner statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b594
The subject of a rico:hasOrHadPart statement must be one of: - rico:Thing The object of a rico:hasOrHadPart statement must be one of: - rico:Thing
The subject of a rico:hasPartTransitive statement must be one of: - rico:Thing The object of a rico:hasPartTransitive statement must be one of: - rico:Thing
The subject of a rico:isAssociatedWithDate statement must be one of: - rico:Thing The object of a rico:isAssociatedWithDate statement must be one of: - rico:Date
The subject of a rico:isAssociatedWithEvent statement must be one of: - rico:Thing The object of a rico:isAssociatedWithEvent statement must be one of: - rico:Event
The subject of a rico:isAssociatedWithPlace statement must be one of: - rico:Thing The object of a rico:isAssociatedWithPlace statement must be one of: - rico:Place
The subject of a rico:isAssociatedWithRule statement must be one of: - rico:Thing The object of a rico:isAssociatedWithRule statement must be one of: - rico:Rule
The subject of a rico:isDirectPartOf statement must be one of: - rico:Thing The object of a rico:isDirectPartOf statement must be one of: - rico:Thing
The subject of a rico:isEquivalentTo statement must be one of: - rico:Thing The object of a rico:isEquivalentTo statement must be one of: - rico:Thing
The subject of a rico:isOrWasAffectedBy statement must be one of: - rico:Thing The object of a rico:isOrWasAffectedBy statement must be one of: - rico:Event
The subject of a rico:isOrWasDescribedBy statement must be one of: - rico:Thing The object of a rico:isOrWasDescribedBy statement must be one of: - rico:RecordResource
The subject of a rico:isOrWasMainSubjectOf statement must be one of: - rico:Thing The object of a rico:isOrWasMainSubjectOf statement must be one of: - rico:RecordResource
The subject of a rico:isOrWasPartOf statement must be one of: - rico:Thing The object of a rico:isOrWasPartOf statement must be one of: - rico:Thing
The subject of a rico:isOrWasParticipantIn statement must be one of: - rico:Thing The object of a rico:isOrWasParticipantIn statement must be one of: - rico:Event
The subject of a rico:isOrWasRegulatedBy statement must be one of: - rico:Thing The object of a rico:isOrWasRegulatedBy statement must be one of: - rico:Rule
The subject of a rico:isOrWasSubjectOf statement must be one of: - rico:Thing The object of a rico:isOrWasSubjectOf statement must be one of: - rico:RecordResource
The subject of a rico:isOrWasUnderAuthorityOf statement must be one of: - rico:Thing The object of a rico:isOrWasUnderAuthorityOf statement must be one of: - rico:Agent
The subject of a rico:isPartOfTransitive statement must be one of: - rico:Thing The object of a rico:isPartOfTransitive statement must be one of: - rico:Thing
The subject of a rico:isRelatedTo statement must be one of: - rico:Thing The object of a rico:isRelatedTo statement must be one of: - rico:Thing
The subject of a rico:precededInSequence statement must be one of: - rico:Thing The object of a rico:precededInSequence statement must be one of: - rico:Thing
The subject of a rico:precedesInSequenceTransitive statement must be one of: - rico:Thing The object of a rico:precedesInSequenceTransitive statement must be one of: - rico:Thing
The subject of a rico:precedesInTime statement must be one of: - rico:Thing The object of a rico:precedesInTime statement must be one of: - rico:Thing
The subject of a rico:precedesOrPreceded statement must be one of: - rico:Thing The object of a rico:precedesOrPreceded statement must be one of: - rico:Thing
The subject of a rico:resultsOrResultedFrom statement must be one of: - rico:Thing The object of a rico:resultsOrResultedFrom statement must be one of: - rico:Event
The subject of a rico:thingIsConnectedToRelation statement must be one of: - rico:Thing The object of a rico:thingIsConnectedToRelation statement must be one of: - rico:Relation
The subject of a rico:thingIsContextOfRelation statement must be one of: - rico:Thing The object of a rico:thingIsContextOfRelation statement must be one of: - rico:Relation
The subject of a rico:thingIsSourceOfRelation statement must be one of: - rico:Thing The object of a rico:thingIsSourceOfRelation statement must be one of: - rico:Relation
The subject of a rico:thingIsTargetOfRelation statement must be one of: - rico:Thing The object of a rico:thingIsTargetOfRelation statement must be one of: - rico:Relation
The subject of a rico:wasLastUpdatedAtDate statement must be one of: - rico:Thing The object of a rico:wasLastUpdatedAtDate statement must be one of: - rico:Date
The subject of a rico:wasPartOf statement must be one of: - rico:Thing The object of a rico:wasPartOf statement must be one of: - rico:Thing
The subject of a rico:isOrWasTitleOf statement must be one of: - rico:Title The object of a rico:isOrWasTitleOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1053
The subject of a rico:isOrWasCategoryOf statement must be one of: - rico:Type The object of a rico:isOrWasCategoryOf statement must be one of: - rico:Thing
The subject of a rico:isOrWasCategoryOfAllMembersOf statement must be one of: - rico:Type The object of a rico:isOrWasCategoryOfAllMembersOf statement must be one of: - rico:RecordSet
The subject of a rico:isOrWasCategoryOfSomeMembersOf statement must be one of: - rico:Type The object of a rico:isOrWasCategoryOfSomeMembersOf statement must be one of: - rico:RecordSet
The subject of a rico:relationHasSource statement must be one of: - rico:TypeRelation The object of a rico:relationHasSource statement must be one of: - rico:Type
The subject of a rico:relationHasTarget statement must be one of: - rico:TypeRelation The object of a rico:relationHasTarget statement must be one of: - rico:Thing The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:typeRelation_role statement must be one of: - rico:TypeRelation The object of a rico:typeRelation_role statement must be one of: - rico:TypeRelation
The subject of a rico:isUnitOfMeasurementOf statement must be one of: - rico:UnitOfMeasurement The object of a rico:isUnitOfMeasurementOf statement must be one of: - rico:Extent
The subject of a rico:relationHasSource statement must be one of: - rico:WholePartRelation The object of a rico:relationHasSource statement must be one of: - rico:Thing
The subject of a rico:relationHasTarget statement must be one of: - rico:WholePartRelation The object of a rico:relationHasTarget statement must be one of: - rico:Thing The rico:relationHasTarget property MUST: - Appear at least 1 times
The subject of a rico:wholePartRelation_role statement must be one of: - rico:WholePartRelation The object of a rico:wholePartRelation_role statement must be one of: - rico:WholePartRelation
The subject of a rico:relationConnects statement must be one of: - rico:WorkRelation The object of a rico:relationConnects statement must be one of: - rico:Agent The rico:relationConnects property MUST: - Appear at least 2 times
The subject of a rico:workRelation_role statement must be one of: - rico:WorkRelation The object of a rico:workRelation_role statement must be one of: - rico:WorkRelation
The subject of a rico:isOrWasOwnerOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1013 The object of a rico:isOrWasOwnerOf statement must be one of: - rico:Thing
The subject of a rico:isOriginalOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1060 The object of a rico:isOriginalOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1063
The subject of a rico:wasConstituentOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1202 The object of a rico:wasConstituentOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1205
The subject of a rico:wasIncludedIn statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1215 The object of a rico:wasIncludedIn statement must be one of: - rico:RecordSet
The subject of a rico:asConcernsActivity statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1532 The object of a rico:asConcernsActivity statement must be one of: - rico:Activity
The subject of a rico:hasConstituentTransitive statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1560 The object of a rico:hasConstituentTransitive statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1563
The subject of a rico:hasCreator statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1570 The object of a rico:hasCreator statement must be one of: - rico:Agent
The subject of a rico:hasOrHadDemographicGroup statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1594 The object of a rico:hasOrHadDemographicGroup statement must be one of: - rico:DemographicGroup
The subject of a rico:hasOrHadManager statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1610 The object of a rico:hasOrHadManager statement must be one of: - rico:Agent
The subject of a rico:isConstituentOfTransitive statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1644 The object of a rico:isConstituentOfTransitive statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1647
The subject of a rico:isIncludedInTransitive statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1670 The object of a rico:isIncludedInTransitive statement must be one of: - rico:RecordSet
The subject of a rico:hasAccumulator statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1845 The object of a rico:hasAccumulator statement must be one of: - rico:Agent
The subject of a rico:hasOrHadConstituent statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1865 The object of a rico:hasOrHadConstituent statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1868
The subject of a rico:hasOrganicOrFunctionalProvenance statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1909 The object of a rico:hasOrganicOrFunctionalProvenance statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1912
The subject of a rico:isOrWasConstituentOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1952 The object of a rico:isOrWasConstituentOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1955
The subject of a rico:isOrWasIncludedIn statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b1973 The object of a rico:isOrWasIncludedIn statement must be one of: - rico:RecordSet
The subject of a rico:isOrganicOrFunctionalProvenanceOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b2004 The object of a rico:isOrganicOrFunctionalProvenanceOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b2007
The subject of a rico:hasOrganicProvenance statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b2266 The object of a rico:hasOrganicProvenance statement must be one of: - rico:Agent
The subject of a rico:documents statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b308 The object of a rico:documents statement must be one of: - rico:Activity
The subject of a rico:hadConstituent statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b344 The object of a rico:hadConstituent statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b347
The subject of a rico:hasAddressee statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b363 The object of a rico:hasAddressee statement must be one of: - rico:Agent
The subject of a rico:hasCollector statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b397 The object of a rico:hasCollector statement must be one of: - rico:Agent
The subject of a rico:hasContentOfType statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b404 The object of a rico:hasContentOfType statement must be one of: - rico:ContentType
The subject of a rico:hasCreationDate statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b413 The object of a rico:hasCreationDate statement must be one of: - rico:Date
The subject of a rico:hasDirectConstituent statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b434 The object of a rico:hasDirectConstituent statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b437
The subject of a rico:hasDocumentaryFormType statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b450 The object of a rico:hasDocumentaryFormType statement must be one of: - rico:DocumentaryFormType
The subject of a rico:hasDraft statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b457 The object of a rico:hasDraft statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b460
The subject of a rico:hasOrHadHolder statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b522 The object of a rico:hasOrHadHolder statement must be one of: - rico:Agent
The subject of a rico:hasOrHadIntellectualPropertyRightsHolder statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b535 The object of a rico:hasOrHadIntellectualPropertyRightsHolder statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b538
hasOrHadIntellectualPropertyRightsHolder Shape
The subject of a rico:hasOrHadLanguage statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b553 The object of a rico:hasOrHadLanguage statement must be one of: - rico:Language
The subject of a rico:hasOrHadLegalStatus statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b568 The object of a rico:hasOrHadLegalStatus statement must be one of: - rico:LegalStatus
The subject of a rico:hasOrHadTitle statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b654 The object of a rico:hasOrHadTitle statement must be one of: - rico:Title
The subject of a rico:hasOriginal statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b661 The object of a rico:hasOriginal statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b664
The subject of a rico:hasReceiver statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b678 The object of a rico:hasReceiver statement must be one of: - rico:Agent
The subject of a rico:hasRecordState statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b689 The object of a rico:hasRecordState statement must be one of: - rico:RecordState
The subject of a rico:hasSender statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b701 The object of a rico:hasSender statement must be one of: - rico:Agent
The subject of a rico:isAuthorOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b727 The object of a rico:isAuthorOf statement must be one of: - rico:Record
The subject of a rico:isDirectConstituentOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b798 The object of a rico:isDirectConstituentOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b801
The subject of a rico:isDirectlyIncludedIn statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b817 The object of a rico:isDirectlyIncludedIn statement must be one of: - rico:RecordSet
The subject of a rico:isDraftOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b829 The object of a rico:isDraftOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b832
The subject of a rico:isOrWasEmployerOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b911 The object of a rico:isOrWasEmployerOf statement must be one of: - rico:Person
The subject of a rico:isOrWasHolderOfIntellectualPropertyRightsOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b933 The object of a rico:isOrWasHolderOfIntellectualPropertyRightsOf statement must be one of: - _:n659bfbb6d70e4bbdb6de3567758f06b3b937
isOrWasHolderOfIntellectualPropertyRightsOf Shape
Observations following the Recruitment module - Age Structure Protocol are made in the context of a site visit.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/c93922b2-3b0e-4ee1-b1ef-c9719d039f5f>`. `<https://linked.data.gov.au/def/nrm/c93922b2-3b0e-4ee1-b1ef-c9719d039f5f>` is the IRI for "Recruitment module - Age Structure Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/c93922b2-3b0e-4ee1-b1ef-c9719d039f5f`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/fcfda2f7-84f0-4c26-9f80-c051d129a094>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the growth stages controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the growth stages controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/fcfda2f7-84f0-4c26-9f80-c051d129a094> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'096e018a-fb8f-4ba1-9fdc-302164e57682'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/fcfda2f7-84f0-4c26-9f80-c051d129a094> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/fcfda2f7-84f0-4c26-9f80-c051d129a094>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/fcfda2f7-84f0-4c26-9f80-c051d129a094>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/096e018a-fb8f-4ba1-9fdc-302164e57682>`. `<https://linked.data.gov.au/def/nrm/096e018a-fb8f-4ba1-9fdc-302164e57682>` is the IRI for "growth stages".
The value of `tern:vocabulary` _MUST_ match the pattern `096e018a-fb8f-4ba1-9fdc-302164e57682$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a42dbbca-7dbe-469e-adfc-9012d01ff43d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/a42dbbca-7dbe-469e-adfc-9012d01ff43d> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a42dbbca-7dbe-469e-adfc-9012d01ff43d>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a42dbbca-7dbe-469e-adfc-9012d01ff43d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/a42dbbca-7dbe-469e-adfc-9012d01ff43d> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/50239f29-a693-49ef-98e8-4ee11d1758ea>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Fire regeneration statuses controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Fire regeneration statuses controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/50239f29-a693-49ef-98e8-4ee11d1758ea> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'a1b8fc00-5d5f-40f8-a7e1-0b09d4bbba4b'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/50239f29-a693-49ef-98e8-4ee11d1758ea> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/50239f29-a693-49ef-98e8-4ee11d1758ea>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/50239f29-a693-49ef-98e8-4ee11d1758ea>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/a1b8fc00-5d5f-40f8-a7e1-0b09d4bbba4b>`. `<https://linked.data.gov.au/def/nrm/a1b8fc00-5d5f-40f8-a7e1-0b09d4bbba4b>` is the IRI for "Fire regeneration statuses".
The value of `tern:vocabulary` _MUST_ match the pattern `a1b8fc00-5d5f-40f8-a7e1-0b09d4bbba4b$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0f342ac9-800a-4298-a148-ffc953ecd393>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0f342ac9-800a-4298-a148-ffc953ecd393> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0f342ac9-800a-4298-a148-ffc953ecd393>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0f342ac9-800a-4298-a148-ffc953ecd393>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0f342ac9-800a-4298-a148-ffc953ecd393> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b6a5d847-0698-4cce-8a5e-f2719e142208>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/b6a5d847-0698-4cce-8a5e-f2719e142208> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b6a5d847-0698-4cce-8a5e-f2719e142208>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b6a5d847-0698-4cce-8a5e-f2719e142208>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/b6a5d847-0698-4cce-8a5e-f2719e142208> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3311154e-4468-59a8-a77f-d90737a9946d> ; sosa:hasResult ?this . }
TERN's ecologists have determined the feature type is _plant individual_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/60d7edf8-98c6-43e9-841c-e176c334d270[`plant individual`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3311154e-4468-59a8-a77f-d90737a9946d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3311154e-4468-59a8-a77f-d90737a9946d> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
Observations following the Recruitment Module - Survivorship Protocol are made in the context of a site visit.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3311154e-4468-59a8-a77f-d90737a9946d>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/f470e27d-20ed-46dc-b64a-d67b39a9dffc>`. `<https://linked.data.gov.au/def/nrm/f470e27d-20ed-46dc-b64a-d67b39a9dffc>` is the IRI for "Recruitment Module - Survivorship Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/f470e27d-20ed-46dc-b64a-d67b39a9dffc`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3311154e-4468-59a8-a77f-d90737a9946d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/781429ca-2ae5-515c-8f8e-805666af2115> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/781429ca-2ae5-515c-8f8e-805666af2115>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/781429ca-2ae5-515c-8f8e-805666af2115> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/781429ca-2ae5-515c-8f8e-805666af2115>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/781429ca-2ae5-515c-8f8e-805666af2115>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0f2a866b-b54b-596a-9215-33fbf0e19b96> ; sosa:hasResult ?this . }
TERN's ecologists have determined the feature type is _plant disturbance_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/6ac5044b-ffac-4cfb-b135-1983e0ea2f7a[`plant disturbance`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0f2a866b-b54b-596a-9215-33fbf0e19b96>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0f2a866b-b54b-596a-9215-33fbf0e19b96> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0f2a866b-b54b-596a-9215-33fbf0e19b96>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0f2a866b-b54b-596a-9215-33fbf0e19b96>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e0c5ed2e-8de9-5da2-804f-7affbc962a64>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e0c5ed2e-8de9-5da2-804f-7affbc962a64>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/e0c5ed2e-8de9-5da2-804f-7affbc962a64> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e0c5ed2e-8de9-5da2-804f-7affbc962a64>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 0 and 100 inclusive. Datatype should be `xsd:integer`.
The result _MUST_ have a value between 0 and 100 inclusively. Datatype should be `xsd:integer`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5471254f-01e0-4201-8e15-888bb26b8fa5>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5471254f-01e0-4201-8e15-888bb26b8fa5>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/5471254f-01e0-4201-8e15-888bb26b8fa5> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5471254f-01e0-4201-8e15-888bb26b8fa5>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e4b7c6db-1471-558d-9a85-98448fcb2139>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e4b7c6db-1471-558d-9a85-98448fcb2139>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/e4b7c6db-1471-558d-9a85-98448fcb2139> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e4b7c6db-1471-558d-9a85-98448fcb2139>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0b7d0b62-93c9-5ee7-af45-b5dced4d6909>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0b7d0b62-93c9-5ee7-af45-b5dced4d6909> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0b7d0b62-93c9-5ee7-af45-b5dced4d6909>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0b7d0b62-93c9-5ee7-af45-b5dced4d6909>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 0 and 300 inclusive. Datatype should be `xsd:float`.
The result _MUST_ have a value between 0 and 300 inclusively. Datatype should be `xsd:float`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0b7d0b62-93c9-5ee7-af45-b5dced4d6909> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6b170ab3-3a5b-5c6d-9229-4952c0e12876>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6b170ab3-3a5b-5c6d-9229-4952c0e12876>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/6b170ab3-3a5b-5c6d-9229-4952c0e12876> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6b170ab3-3a5b-5c6d-9229-4952c0e12876>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c86df5bf-11c4-5382-822b-0f7b3bc0ec75>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Crown damage types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Crown damage types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/c86df5bf-11c4-5382-822b-0f7b3bc0ec75> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'41afd1b6-bd4d-5419-b571-931b09b61ce8'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/c86df5bf-11c4-5382-822b-0f7b3bc0ec75> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c86df5bf-11c4-5382-822b-0f7b3bc0ec75>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c86df5bf-11c4-5382-822b-0f7b3bc0ec75>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/41afd1b6-bd4d-5419-b571-931b09b61ce8>`. `<https://linked.data.gov.au/def/nrm/41afd1b6-bd4d-5419-b571-931b09b61ce8>` is the IRI for "Crown damage types".
The value of `tern:vocabulary` _MUST_ match the pattern `41afd1b6-bd4d-5419-b571-931b09b61ce8$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/1849d749-8c88-5bf4-a8a5-031bd8de8c9b> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/1849d749-8c88-5bf4-a8a5-031bd8de8c9b>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/1849d749-8c88-5bf4-a8a5-031bd8de8c9b> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/1849d749-8c88-5bf4-a8a5-031bd8de8c9b>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/1849d749-8c88-5bf4-a8a5-031bd8de8c9b>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/46dd6bb1-dd92-5b49-8f85-7d650eeab8f8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Human induced damage types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Human induced damage types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/46dd6bb1-dd92-5b49-8f85-7d650eeab8f8> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'ffe13f4f-3613-430f-a2b5-a46fcb4662c1'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/46dd6bb1-dd92-5b49-8f85-7d650eeab8f8> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/46dd6bb1-dd92-5b49-8f85-7d650eeab8f8>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/46dd6bb1-dd92-5b49-8f85-7d650eeab8f8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/ffe13f4f-3613-430f-a2b5-a46fcb4662c1>`. `<https://linked.data.gov.au/def/nrm/ffe13f4f-3613-430f-a2b5-a46fcb4662c1>` is the IRI for "Human induced damage types".
The value of `tern:vocabulary` _MUST_ match the pattern `ffe13f4f-3613-430f-a2b5-a46fcb4662c1$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/c45bcc9a-7d43-5665-a297-8c3815747aa6> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c45bcc9a-7d43-5665-a297-8c3815747aa6>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/c45bcc9a-7d43-5665-a297-8c3815747aa6> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c45bcc9a-7d43-5665-a297-8c3815747aa6>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c45bcc9a-7d43-5665-a297-8c3815747aa6>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/08d25196-38f2-414e-9517-5a41f8b6935a>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/08d25196-38f2-414e-9517-5a41f8b6935a>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/08d25196-38f2-414e-9517-5a41f8b6935a> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/08d25196-38f2-414e-9517-5a41f8b6935a>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6ac90fd7-0a2c-4ca9-86be-3dabe154ebd1>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6ac90fd7-0a2c-4ca9-86be-3dabe154ebd1>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/6ac90fd7-0a2c-4ca9-86be-3dabe154ebd1> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6ac90fd7-0a2c-4ca9-86be-3dabe154ebd1>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/33e79578-0946-4f21-9607-ca501e1500c7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the insect damage types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the insect damage types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/33e79578-0946-4f21-9607-ca501e1500c7> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'ba3f55eb-5698-4974-8101-da346027a346'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/33e79578-0946-4f21-9607-ca501e1500c7> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/33e79578-0946-4f21-9607-ca501e1500c7>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/33e79578-0946-4f21-9607-ca501e1500c7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/ba3f55eb-5698-4974-8101-da346027a346>`. `<https://linked.data.gov.au/def/nrm/ba3f55eb-5698-4974-8101-da346027a346>` is the IRI for "insect damage types".
The value of `tern:vocabulary` _MUST_ match the pattern `ba3f55eb-5698-4974-8101-da346027a346$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6a1d703f-6622-4804-8b78-4c2ac93c97ba>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/6a1d703f-6622-4804-8b78-4c2ac93c97ba> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6a1d703f-6622-4804-8b78-4c2ac93c97ba>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6a1d703f-6622-4804-8b78-4c2ac93c97ba>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/6a1d703f-6622-4804-8b78-4c2ac93c97ba> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/2567a68b-7466-4481-9e13-3f89ac65125f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/2567a68b-7466-4481-9e13-3f89ac65125f> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/2567a68b-7466-4481-9e13-3f89ac65125f>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/2567a68b-7466-4481-9e13-3f89ac65125f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/2567a68b-7466-4481-9e13-3f89ac65125f> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/e7af31c1-6131-4053-87d4-306275175988> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e7af31c1-6131-4053-87d4-306275175988>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/e7af31c1-6131-4053-87d4-306275175988> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e7af31c1-6131-4053-87d4-306275175988>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e7af31c1-6131-4053-87d4-306275175988>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e3926734-a967-57f9-84b2-580eeb10b1f4>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Tree conditions controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Tree conditions controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/e3926734-a967-57f9-84b2-580eeb10b1f4> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'65a394bf-5362-4174-974e-be6f3964721c'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/e3926734-a967-57f9-84b2-580eeb10b1f4> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e3926734-a967-57f9-84b2-580eeb10b1f4>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e3926734-a967-57f9-84b2-580eeb10b1f4>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/65a394bf-5362-4174-974e-be6f3964721c>`. `<https://linked.data.gov.au/def/nrm/65a394bf-5362-4174-974e-be6f3964721c>` is the IRI for "Tree conditions".
The value of `tern:vocabulary` _MUST_ match the pattern `65a394bf-5362-4174-974e-be6f3964721c$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5998d180-3fe8-5253-8af4-6aab74e87e38>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5998d180-3fe8-5253-8af4-6aab74e87e38>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/5998d180-3fe8-5253-8af4-6aab74e87e38> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5998d180-3fe8-5253-8af4-6aab74e87e38>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a1b6dde1-1655-5be1-9caa-8c40867443a7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a1b6dde1-1655-5be1-9caa-8c40867443a7>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/a1b6dde1-1655-5be1-9caa-8c40867443a7> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a1b6dde1-1655-5be1-9caa-8c40867443a7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/2dd40967-10a8-5882-8cdf-6cfaaae33566>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/2dd40967-10a8-5882-8cdf-6cfaaae33566>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/2dd40967-10a8-5882-8cdf-6cfaaae33566> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/2dd40967-10a8-5882-8cdf-6cfaaae33566>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
CiTO, the Citation Typing Ontology, is an ontology written in OWL 2 DL to enable characterization of the nature or type of citations, both factually and rhetorically, and to permit these descriptions to be published on the Web. The citations characterized may be either direct and explicit (as in the reference list of a journal article), indirect (e.g. a citation to a more recent paper by the same research group on the same topic), or implicit (e.g. as in artistic quotations or parodies, or in cases of plagiarism). CiTO contains the object property cito:cites and its sub-properties, and its inverse property cito:isCitedBy, from the original Citation Typing Ontology, CiTO v1.6. Upon the creation of version 2.0 of CiTO, a number of new sub-properties of cito:cites were added, and the inverse properties of all the sub-properties of cito:cites were created, all of which are sub-properties of cito:isCitedBy. The ontology has also been integrated with the SWAN Discourse Relationships Ontology by making cito:cites a sub-property of http://purl.org/swan/2.0/discourse-relationships/refersTo. Restrictions of domain and range present in the previous version of CiTO were removed from the object properties when creating CiTO v 2.0, permitting its independent use in other contexts, in addition to conventional bibliographic citations. So that they can be used independently, other entities that were previously included in CiTO v1.6 have now been made components of other SPAR ontologies: FaBiO, the FRBR-aligned Bibliographic Ontology; C4O, the Citation Counting and Context Characterization Ontology; and PSO, the Publication Status Ontology. The addition of two new properties:cito:usesConclusionsFrom and its inverse cito:providesConclusionsFor on 09Dec2011 led to a version number increment from v2.0 to v2.1. The addition of two additional properties, cito:compiles and cito:isCompiledBy, previously in the deprecated CiTO4Data ontology, on 03 July 2012 led to a version increment from v2.1 to v2.2. Subsequent expansions include: in versions 2.3 and 2.4 the addition of the object properties cito:citesAsPotentialSolution, cito:citesAsRecommendedReading, cito:repliesTo, cito:retracts, cito:speculates on, and their inverse properties; in v2.5 the addition of cito:CitationAct, cito:hasCitationEvent, cito:hasCitedEntity and cito:hasCitingEntity; in v 2.6: renaming cito:hasCitationEvent to become cito:hasCitationCharacterization; improving definitions of cito:CitationAct, cito:hasCitationCharacterization, cito:hasCitedEntity and cito:hasCitingEntity; revising the definition of cito:isCompiledBy to correct it and bring it into line with the DataCite Metadata Kernel v2.2 definition; changing the definition of cito:sharesAuthorsWith from 'An object property indicating that the citing entity has at least one author in common with the cited entity.' to 'An object property between two entities indicating that they have at least one author in common.' so that it can be used when one entity does not actually cite the other; adding the object properties cito:hasRelatedEntity, cito:sharesFundingAgencyWith and cito:sharesAuthorInstitutionWith; and adding the text 'An object property indicating that . . .' at the beginning of the textual definition (schema:description) for each CiTO object property. in v 2.6.1: Removed text 'An object property indicating that . . .' added in v 2.6 at the beginning of the textual definition (schema:description) for each CiTO object property, so that each definition is just a direct statement of the relationship. Removed the property cito:hasRelatedEntity (in favour of using dcterms:relation). Renamed cito:hasReply to become cito:hasReplyFrom. Improved the textual definitions of cito:derides and its inverse property. in v 2.6.2: Improved definitions of of cito:CitationAct, cito:hasCitationCharacterization, cito:hasCitedEntity and cito:hasCitingEntity. in v 2.6.3: Added examples for each citation type (i.e., all the subproperties of cito:cites). in v 2.6.4: Added alignment with schema:citation. in v 2.7.0: Added new property cito:linksTo, and corrected some property URL. in v 2.7.1 Corrected some typos in property comments. in v 2.7.2 The name of the class cito:CitationAct has been changed to cito:Citation, and its definition has been modified. The property cito:hasCitationTimeSpan has been added. in v 2.7.3 Added the class cito:SelfCitation, i.e. citation in which the citing and the cited entities have at least one author in common. in v 2.8 Renamed the class cito:SelfCitation in cito:AuthorSelfCitation. Created a new class cito:SelfCitation with a more general definition (citation in which the citing and the cited entities have something significant in common with one another), which now includes five subclasses: cito:AuthorSelfCitation, cito:JournalSelfCitation, cito:FunderSelfCitation, cito:AffiliationSelfCitation, cito:AuthorNetworkSelfCitation. The latter class is also accompanied by the new data property cito:hasCoAuthorCitationLevel, which specifies the minimal distance that one of the authors of a citing entity has with regards to one of the authors of a cited entity according to their co-author network. Added the object properties cito:sharesPublicationVenueWith and its subproperty cito:sharesJournalWith. Added the data property cito:hasCitationCreationDate, and changed the domain of cito:hasCitationTimeSpan with xsd:duration. in v 2.8.1 Renamed the property cito:hasCoAuthorCitationLevel in cito:hasCoAuthorshipCitationLevel.
The Citation Typing Ontology (CiTO) is an ontology that enables characterization of the nature or type of citations, both factually and rhetorically. **URL:** http://purl.org/spar/cito **Creators**: [David Shotton](http://orcid.org/0000-0001-5506-523X), [Silvio Peroni](http://orcid.org/0000-0003-0530-4305) **Contributors:** [Paolo Ciccarese](https://orcid.org/0000-0002-5156-2703), [Tim Clark](https://orcid.org/0000-0003-4060-7360) **License:** [Creative Commons Attribution 4.0 International](https://creativecommons.org/licenses/by/4.0/legalcode) **Website:** http://www.sparontologies.net/ontologies/cito **Cite as:** Peroni, S., Shotton, D. (2012). FaBiO and CiTO: ontologies for describing bibliographic resources and citations. In Journal of Web Semantics, 17: 33-43. https://doi.org/10.1016/j.websem.2012.08.001. Open Access at: http://speroni.web.cs.unibo.it/publications/peroni-2012-fabio-cito-ontologies.pdf
This work is distributed under a Creative Commons Attribution License (http://creativecommons.org/licenses/by/3.0/).
A citation in which at least one author from each of the citing and the cited entities is affiliated with the same academic institution. In particular, like the ancestor class cito:Citation, cito:AffiliationSelfCitation and its accompanying object properties cito:hasCitingEntity, cito:hasCitedEntity and cito:hasCitationCharacterization can be employed to reify direct citation statements made using the CiTO citation object property cito:cites or one of its sub-properties, accompanied by an additional statement using cito:sharesAuthorInstitutionWith for linking the citing paper and the cited paper. For example, the following cito:AffiliationSelfCitation resource :thisCitation a cito:AffiliationSelfCitation ; cito:hasCitingEntity :paperA ; cito:hasCitationCharacterization cito:extends ; cito:hasCitedEntity :paperB . can be alternatively described as follows :paperA cito:extends :paperB . :paperA cito:sharesAuthorInstitutionWith :paperB .
A citation in which the citing and the cited entities have something significant in common with one another, over and beyond their subject matter, for example authors, journal, institutional affiliation, or funding agency.
A citation in which the citing and the cited entities have at least one author in common. In particular, like the ancestor class cito:Citation, cito:AuthorSelfCitation and its accompanying object properties cito:hasCitingEntity, cito:hasCitedEntity and cito:hasCitationCharacterization can be employed to reify direct citation statements made using the CiTO citation object property cito:cites or one of its sub-properties, accompanied by an additional statement using cito:sharesAuthorWith for linking the citing paper and the cited paper. For example, the following cito:AuthorSelfCitation resource :thisCitation a cito:AuthorSelfCitation ; cito:hasCitingEntity :paperA ; cito:hasCitationCharacterization cito:extends ; cito:hasCitedEntity :paperB . can be alternatively described as follows :paperA cito:extends :paperB . :paperA cito:sharesAuthorWith :paperB .
Derived from the article 'A Small World of Citations? The Influence of Collaboration Networks on Citation Practices' by Matthew L. Wallace, Vincent Larivière and Yves Gingras, published in PLOS One (https://doi.org/10.1371/journal.pone.0033339).
A citation in which the citing and the cited entities have nothing significant in common with one another (for example authors, journal, institutional affiliation, or funding agency) over and beyond their subject matter.
A citation is a conceptual directional link from a citing entity to a cited entity, created by a human performative act of making a citation, typically instantiated by the inclusion of a bibliographic reference (biro:BibliographicReference) in the reference list of the citing entity, or by the inclusion within the citing entity of a link, in the form of an HTTP Uniform Resource Locator (URL), to a resource on the World Wide Web. The time span of a citation, i.e. the interval between the publication year of the citing entity and the publication year of the cited entity, can be recorded using the data property cito:hasCitationTimeSpan. The nature or type of a citation can be characterized by using CiTO object properties, e.g. http://purl.org/spar/cito/citesAsDataSource (definition: “The citing entity cites the cited entity as a source of data”). This CiTO class cito:Citation and its accompanying object properties cito:hasCitingEntity, cito:hasCitedEntity and cito:hasCitationCharacterization can be employed to reify direct citation statements made using the CiTO citation object property cito:cites or one of its sub-properties. For example, the following RDF statement :paperA cito:extends :paperB . can be alternatively described as follows :thisCitation a cito:Citation ; cito:hasCitingEntity :paperA ; cito:hasCitationCharacterization cito:extends ; cito:hasCitedEntity :paperB . This usage involved OWL2 punning, whereby a CiTO object property, such as the aforementioned cito:extends, is used as the object of the OWL assertion. :thisCitation cito:hasCitationCharacterization cito:extends . Using such OWL2 punning (described at http://www.w3.org/TR/2009/WD-owl2-new-features-20090611/#F12:_Punning), the CiTO object property is considered as a proper named individual of the class owl:Thing. Such reification of citation acts can be very useful, since it permits one to combine these CiTO properties with other vocabularies, or to handle situations in which none of the citation characterizations available in CiTO are applicable. Such situations can be resolved by the creation of a user-defined citation characterization, for example by using the Open Annotation Data Model, as explained at http://semanticpublishing.wordpress.com/2013/07/03/extending-cito-for-open-annotations/.
A citation in which the works reported in the citing and the cited entities were funded by the same funding agency. In particular, like the ancestor class cito:Citation, cito:FunderSelfCitation and its accompanying object properties cito:hasCitingEntity, cito:hasCitedEntity and cito:hasCitationCharacterization can be employed to reify direct citation statements made using the CiTO citation object property cito:cites or one of its sub-properties, accompanied by an additional statement using cito:sharesFundingAgencyWith for linking the citing paper and the cited paper. For example, the following cito:FundingSelfCitation resource :thisCitation a cito:FundingSelfCitation ; cito:hasCitingEntity :paperA ; cito:hasCitationCharacterization cito:extends ; cito:hasCitedEntity :paperB . can be alternatively described as follows :paperA cito:extends :paperB . :paperA cito:sharesFundingAgencyWith :paperB .
Derived from the blog post 'What do we know about journal citation cartels? A call for information' by Philippe Mongeon, Ludo Waltman and Sarah de Rijcke (https://www.cwts.nl/blog?article=n-q2w2b4).
A citation from one journal to another journal which forms one of a very large number of citations from the citing journal to recent articles in the cited journal, possibly undertaken as part of a citation cartel for the purpose of gaming the impact factor of the cited journal.
Derived from the blog post 'Journal self-citations are increasingly biased toward impact factor years' by Ludo Waltman and Caspar Chorus (https://www.cwts.nl/blog?article=n-q2x264).
A citation in which the citing and the cited entities are published in the same journal. In particular, like the ancestor class cito:Citation, cito:JournalSelfCitation and its accompanying object properties cito:hasCitingEntity, cito:hasCitedEntity and cito:hasCitationCharacterization can be employed to reify direct citation statements made using the CiTO citation object property cito:cites or one of its sub-properties, accompanied by an additional statement using cito:sharesJournalWith for linking the citing paper and the cited paper. For example, the following cito:JournalSelfCitation resource :thisCitation a cito:JournalSelfCitation ; cito:hasCitingEntity :paperA ; cito:hasCitationCharacterization cito:extends ; cito:hasCitedEntity :paperB . can be alternatively described as follows :paperA cito:extends :paperB . :paperA cito:sharesJournalWith :paperB .
Example: We share Galileo's opinion: the Earth moves [X].
The citing entity agrees with statements, ideas or conclusions presented in the cited entity.
The citing entity cites the cited entity, either directly and explicitly (as in the reference list of a journal article), indirectly (e.g. by citing a more recent paper by the same group on the same topic), or implicitly (e.g. as in artistic quotations or parodies, or in cases of plagiarism).
The cited entity contains statements, ideas or conclusions with which the citing entity agrees.
Example: Newton asserted that we are like dwarfs standing on the shoulders of giants [X].
The citing entity cites the cited entity as one that provides an authoritative description or definition of the subject under discussion.
The cited entity is cited as providing an authoritative description or definition of the subject under discussion in the citing entity.
Example: Italy has more than ten thousand kilometers of shoreline: see [X].
The citing entity cites the cited entity as source of data.
The cited entity is cited as a data source by the citing entity.
Example: We found an unquestionable demonstration of our hypothesis in [X].
The citing entity cites the cited entity as source of factual evidence for statements it contains.
The cited entity is cited for providing factual evidence to the citing entity.
Example: Basic bibliographic, entity and project metadata relating to this article, recorded in a structured machine-readable form, is available as an additional file [X] accompanying this paper.
The citing entity cites the cited entity as being the container of metadata describing the citing entity.
The cited entity is cited as being the container of metadata relating to the citing entity.
Example: This risk could be avoided using the approach shown in [X].
The citing entity cites the cited entity as providing or containing a possible solution to the issues being discussed.
The cited entity is cited as providing or containing a possible solution to the issues being discussed in the citing entity.
Example: To our knowledge, [X] is the best source of exercises about UML, making it a valuable proposal for beginners.
The citing entity cites the cited entity as an item of recommended reading. This property can be used, for example, to describe references in a lecture reading list, where the cited references are relevant to the general topic of the lecture, but might not be individually cited within the text of the lecture. Similarly, it could be used to describe items in a 'Suggested further reading' list at the end of a book chapter.
The cited entity is cited by the citing entity as an item of recommended reading. This property can be used, for example, to describe references in a lecture reading list, where the cited references are relevant to the general topic of the lecture, but might not be individually cited within the text of the lecture. Similarly, it could be used to describe items in a 'Suggested further reading' list at the end of a book chapter.
Example: An analysis similar to what we proposed here is presented in [X].
The citing entity cites the cited entity as one that is related.
The cited entity is cited as being related to the citing entity.
Example: Several sections of this work are based on our literature review of the topic published as journal article [X].
The citing entity cites the cited entity as being the entity from which the citing entity is derived, or about which the citing entity contains metadata.
The cited entity is cited as being the entity from which the citing entity is derived, or about which the citing entity contains metadata.
Example: The grammar of Pascal was introduced in [X].
The citing entity cites the cited entity as a source of information on the subject under discussion.
The cited entity is cited as a source of information on the subject under discussion in the citing entity.
Example: This book gathers interviews with academic researchers of several disciplines [X].
Note: This property has been imported from the CiTO4Data ontology, usage of which has been deprecated.
The citing entity is used to create or compile the cited entity.
The cited entity is the result of a compile or creation event using the citing entity.
Example: Our findings are similar to those published in [X].
The citing entity confirms facts, ideas or statements presented in the cited entity.
The cited entity presents facts, ideas or statements that are confirmed by the citing entity.
Example: We think that to stand on the top of giants [X] is a valuable principle to follow for our own research.
The citing entity contains a statement of fact or a logical assertion (or a collection of such facts and/or assertions) originally present in the cited entity. This object property is designed to be used to relate a separate abstract, summary or nanopublication to the cited entity upon which it is based.
The cited entity contains and is the original source of a statement of fact or a logical assertion (or a collection of such facts and/or assertions) that is to be found in the citing entity. This inverse object property is designed to be used to relate a cited entity to a separate abstract, summary or nanopublication based upon it.
Example: The result published in [X] is partially wrong, the correct result is 42.
The citing entity corrects statements, ideas or conclusions presented in the cited entity.
The cited entity presents statements, ideas or conclusions that are corrected by the citing entity.
Example: Galileo was the first to observe Jupiter's satellites [X].
The citing entity acknowledges contributions made by the cited entity.
The cited entity makes contributions that are acknowledged by the citing entity.
Example: The ideas presented in [X] are badly substantantiated.
The citing entity critiques statements, ideas or conclusions presented in the cited entity.
The cited entity presents statements, ideas or conclusions that are critiqued by the citing entity.
Example: The ideas published in [X] are incredibly stupid.
The citing entity express derision for the cited entity, or for ideas or conclusions contained within it.
The cited entity contains ideas or conclusions for which the citing entity express derision.
Example: Galileo's book [X] is a dialog among three scientists about Copernicus' eliocentric theory.
The citing entity describes the cited entity.
The cited entity is described by the citing entity.
Example: We do not share Galileo's opinion [X]: the Earth does not move.
The citing entity disagrees with statements, ideas or conclusions presented in the cited entity.
The cited entity presents statements, ideas or conclusions that are disagreed with by the citing entity.
Example: We now examine if Galileo is right when he writes [X] that the Earth moves.
The citing entity discusses statements, ideas or conclusions presented in the cited entity.
The cited entity presents statements, ideas or conclusions that are discussed by the citing entity.
Example: We doubt that Galileo is right when he writes [X] that the Earth moves.
The citing entity disputes statements, ideas or conclusions presented in the cited entity.
The cited entity presents statements, ideas or conclusions that are disputed by the citing entity.
Example: Herein we report in detail the complete set of ontological rules defined in the Overlapping Ontology [X].
The citing entity documents information about the cited entity.
Information about the cited entity is documented by the citing entity.
Example: We add to Galileo's findings concerning the Earth [X] that also the Moon moves.
The citing entity extends facts, ideas or understandings presented in the cited entity.
The cited entity presents facts, ideas or understandings that are extended by the citing entity.
The cited entity provides background information for the citing entity.
The cited entity (the subject of the RDF triple) is cited by the citing entity (the object of the triple).
Example: There is a need for more observational studies and studies using narrative causation to describe the potential contribution of information in problem-solving and decision-making [X]; our work addresses these needs.
The citing entity obtains background information from the cited entity.
The cited entity provides intellectual or factual support for the citing entity.
Example: Our ideas were also shared by Doe et al. [X].
The citing entity obtains intellectual or factual support from the cited entity.
The date on which the citation was created. This has the same numerical value as the publication date of the citing bibliographic resource, but is a property of the citation itself. When combined with the citation time span, it permits that citation to be located in history.
The temporal characteristic of a citation, namely the interval between the publication date of the cited entity and the publication date of the citing entity. Note that when one or both of the publication dates is given as just 'year', then the citation time span is rounded to the nearest year, and when one or both of the publication dates is given as just 'year and month', then the citation time span is rounded to the nearest month, with the inherent inaccuracies that such rounding involves.
The cited entity evokes a reply from the citing entity.
Example: We will not investigate the issues of the approach proposed in [X] here, but rather we introduce yet another alternative.
The citing entity replies to statements, ideas or criticisms presented in the cited entity.
An excerpt is more general than a quotation. It is generally used to indicate a re-published extract from a book, instruction manual, film, radio programme, etc, that need not be what someone said. For example: Oxford 01865 Oxshott 01372 Oxted 01883 Oxton 01578 is an excerpt from the UK Dialling Codes section of the Oxford Telephone Directory.
Example: In her work, the author states that even though most Human Information Behaviour researchers are familiar with the literature related to their studies, it is not uncommon for investigators to fail to see the benefits they may gain from previous mistakes [X].
The citing entity includes one or more excerpts from the cited entity.
The cited entity contains information, usually of a textual nature, that is excerpted by (used as an excerpt within) the citing entity.
A quotation is a repetition of what someone has said, and is presented "within quotation marks", for example: On June 4th 1940, Winston Churchill made a speech on the radio that has since become famous, that included the words: " . . . we shall fight on the beaches, we shall fight on the landing grounds, we shall fight in the fields and in the streets, we shall fight in the hills; we shall never surrender . . ."
Example: As Newton wrote in [X]: "We are like dwarfs standing on the shoulders of giants".
The citing entity includes one or more quotations from the cited entity.
The cited entity contains information, usually of a textual nature, that is quoted by (used as a quotation within) the citing entity.
The cited entity is the target for an HTTP Uniform Resource Locator (URL) link within the citing entity.
Example: The BioSharing registry (https://biosharing.org) can be of use as it describes the standards in detail, including versions where applicable.
The citing entity provides a link, in the form of an HTTP Uniform Resource Locator (URL), to the cited entity.
The characteristic style or content of the cited entity is imitated by the citing entity for comic effect, usually without explicit citation.
Example: We act as giants on the shoulders of dwarfs [X]!
The citing entity imitates the characteristic style or content of the cited entity for comic effect, usually without explicit citation.
The cited entity is plagiarized by the author of the citing entity, who includes within the citing entity textual or other elements from the cited entity without formal acknowledgement of their source. The cited entity is thus not explicitly cited from within the citing entity, according to the norms of scholarly practice, but is cited implicitly.
Example: The conclusion of our dissertation can be summarised by the following motto, we created specifically for this purpose: we are like dwarfs standing on the shoulders of giants.
A property indicating that the author of the citing entity plagiarizes the cited entity, by including textual or other elements from the cited entity without formal acknowledgement of their source. The citing entity thus contains no explicit citation of the cited entity, according to the norms of scholarly practice, but cites it implicitly.
The cited entity presents statements, ideas or conclusions that are qualified or have conditions placed upon them by the citing entity.
Example: Galileo's masterpiece 'Dialogo sopra i due massimi sistemi del mondo' [X] is formally a dialog and substantially a scientific pamphlet.
The citing entity qualifies or places conditions or restrictions upon statements, ideas or conclusions presented in the cited entity.
The cited entity presents statements, ideas or conclusions that are refuted by the citing entity.
Example: We do not think that all their arguments in favour of their own and against the other strategies are equally convincing [X].
The citing entity refutes statements, ideas or conclusions presented in the cited entity.
The cited entity is formally retracted by the citing entity.
Example: We wrote that the Earth moves in [X]; we now retire such statement.
The citing entity constitutes a formal retraction of the cited entity.
The cited entity presents statements, ideas or conclusions that are reviewed by the citing entity.
Example: This paper discusses Toulmin's methodology in modelling argumentation [X], focussing on highlighting advantages and drawbacks of the application of such a methodology in the Social Web.
The citing entity reviews statements, ideas or conclusions presented in the cited entity.
The cited entity or aspects of its contents are ridiculed by the citing entity.
Example: Galileo said that the Earth "moves" [X]; really? And where is it going?
The citing entity ridicules the cited entity or aspects of its contents.
The cited entity is cited because the citing article contains speculations on its content or ideas.
Example: We believe that if Galileo believed that Earth goes around the Sun [X], he also should believe that Moon goes around Earth.
The citing entity speculates on something within or related to the cited entity, without firm evidence.
The cited entity receives intellectual or factual support from the citing entity.
Example: We support Galileo's statement [X], that Earth moves.
The citing entity provides intellectual or factual support for statements, ideas or conclusions presented in the cited entity.
The cited entity presents statements, ideas, hypotheses or understanding that are updated by the cited entity.
Example: Earth moves, said Galileo [X]; in addition, we can say now it moves very fast.
The citing entity updates statements, ideas, hypotheses or understanding presented in the cited entity.
A property that permits you to express appreciation of or interest in something that is the object of the RDF triple, or to express that it is worth thinking about even if you do not agree with its content, enabling social media 'likes' statements to be encoded in RDF. Use of this property does NOT imply the existence of a formal citation of the entity that is 'liked'.
The cited entity presents conclusions that are used in work described in the citing entity.
Example: Building upon Galileo's findings [X], we discovered that all the planets move.
The citing entity describes work that uses conclusions presented in the cited entity.
The cited entity presents data that are used in work described in the citing entity.
Example: Using the information collected from our recent study [X], we can estimate that there are tens of millions of HTML forms with potentially useful deep-web content.
The citing entity describes work that uses data presented in the cited entity.
The cited entity details a method that is used in work described by the citing entity.
Example: We follow [X] in using design patterns for testing.
The citing entity describes work that uses a method detailed in the cited entity.
Each entity has at least one author that shares a common institutional affiliation with an author of the other entity.
Each entity has at least one author in common with the other entity.
The two entities result from activities that have been funded by the same funding agency.
The citing and cited bibliographic resources are published in the same journal.
The citing and cited bibliographic resources are published in same publication venue.
A citation in which at least one author of the citing entity has direct or indirect co-authorship links with one of the authors of the cited entity.
This property specifies the minimal distance that one of the authors of the citing entity has with regards to one of the authors of the cited entity, according to their co-authorship network. For instance, a citation has a co-authorship citation level equal to 1 if at least one author of the citing entity has previously published as co-author with one of the authors of the cited entity. Similarly, we say that a citation has a co-authorship citation level equal to 2 if at least one author of the citing entity has previously published as co-author with someone who him/herself has previously published as co-author with one of the authors of the cited entity. And so on.
A property that links a citation to its characterization made by using a CiTO citation characterization property such as cito:extends. This usage involved OWL2 punning, whenby a CiTO object property, such as the aforementioned cito:extends, is used as the object of an OWL assertion: :thisCitation cito:hasCitationCharacterization cito:extends . In such cases of OWL punning, the CiTO object properties are simultaneously considered both as normal object properties and also as proper named individuals of the class owl:Thing.
A property that relates a citation to the cited entity.
A property that relates a citation to the citing entity.
Use this property to indicate the individual parts of a Compound Name
Indicates a Resource that is part of this item
In this model, name is used to indicate both a literal form of a resource`s name or a CompoundName object
Use this property to indicate the value of a CompoundName, whether it's a literal or a complex object
This ontology was made for the Queensland Department of Resources, Spatial Information unit in 2023 to assist with future Address, Place Names, Roads & Cadastre systems design however it is intended to provide background modelling for all ANZ jurisdictions' foundational spatial data. This model has been made with the FSDF Supermodel in mind (https://linked.data.gov.au/def/fsdf-supermodel) so that is compatible with that, and the Locaiton Index (Loc-I) projects' modelling and goals.
This model allows for the representation of compound names that can be assigned to be assigned to features
Compound Naming Model
See the literals values of '72' and 'Yundah' in the CompoundName example
This class is used to represent the range value of the property :asLiteral. It is not expected to be used directly but instead specialised types of Literal are expected
The class of literal values, eg. textual strings and integer
See the non-literal values for rdf:value in the CompoundName example
This class is used to represent both the things to which CompoundNames can be assigned and also the range value of the property rdf:value. It is not expected to be used directly but instead specialised types of Resource are expected
# An example Compound Name that is an Address, # constructed in the manner of Australian street addresses # and typically rendered for letter sending as: # # 72 Yundah Street # Shorncliffe, QLD, 4017 # Australia # PREFIX : <https://linked.data.gov.au/def/cn/> PREFIX ex: <http://example.com/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> PREFIX schema: <https://schema.org/> ex:72-yundah a :CompoundName ; rdfs:member [ schema:additionalType ex:streetNumber ; rdf:value 72 ; ] , [ schema:additionalType ex:streetName ; rdf:value "Yundah" ; ] , [ schema:additionalType ex:streetType ; rdf:value ex:Street ; ] , [ schema:additionalType ex:locality ; rdf:value ex:Shorncliffe ; ] , [ schema:additionalType ex:state ; rdf:value ex:Queensland ; ] , [ schema:additionalType ex:postCode ; rdf:value 4017 ; ] , [ a :CompoundName ; schema:additionalType ex:country ; rdf:value ex:aus ; schema:name "Australia" ; ] ; . # An example Compound Name that is a Geographical Name, # for an island off the coast of Brisbane, Australia # that may be rendered as either Moreton Island or perhaps # Moreton Is. # ex:moreton a :CompoundName ; rdfs:member [ schema:additionalType ex:geographicalName ; rdf:value "Moreton" ; ] , [ a :CompoundName ; schema:additionalType ex:geographicalName ; rdf:value ex:Island ; schema:name "Island" ; ] ; .
A Compound Name is a literal value, or objects that can be interpreted as literal values, that describe or name a Feature
Compound Name
# Moreton Island is the Compound Name # for a spatial object off the coast of Brisbane, Australia # PREFIX : <https://linked.data.gov.au/def/cn/> PREFIX ex: <http://example.com/> PREFIX geo: <http://www.opengis.net/ont/geosparql#> ex:moreton a :CompoundName ; :isNameFor ex:feature-x ; . ex:feature-x a geo:Feature ; schema:name ex:moreton ; .
Links a name to the thing it is used for
Use this property to indicate the specialised type of a part of a CompoundName
An additional type for the item, typically used for adding more specific types from external vocabularies
Geometry can be used as a representation of the shape, extent or location of a Feature and may exist as a self-contained entity.
A coherent set of direct positions in space. The positions are held within a Spatial Reference System (SRS).
A spatial representation for a given Feature.
The target is a Geometry that defines a rectilinear region whose edges are aligned with the axes of the coordinate reference system, which exactly contains the Feature, for example an instance of http://www.opengis.net/ont/sf#envelope.
The minimum or smallest bounding or enclosing box of a given Feature.
The target Geometry shall describe a point, for example an instance of http://www.opengis.net/ont/sf#Point.
The arithmetic mean position of all the Geometry points of a given Feature.
A Feature represents a uniquely identifiable phenomenon, for example a river or an apple. While such phenomena (and therefore the Features used to represent them) are bounded, their boundaries may be crisp (e.g., the declared boundaries of a state), vague (e.g., the delineation of a valley versus its neighboring mountains), and change with time (e.g., a storm front). While discrete in nature, Features may be created from continuous observations, such as an isochrone that determines the region that can be reached by ambulance within 5 minutes.
A discrete spatial phenomenon in a universe of discourse.
Duplicate properties defaultGeometry and hasDefaultGeometry exist because of an inconsistency between ontology and documentation in GeoSPARQL 1.0. Only hasDefaultGeometry is described in the documention.
The default Geometry to be used in spatial calculations. It is usually the most detailed Geometry.
A Well-known Text serialization of a Geometry object.
An RDF/OWL vocabulary for representing spatial information
States that the subject SpatialObject is spatially within the object SpatialObject. DE-9IM: T*F**F***
The number of measurements or axes needed to describe the position of this Geometry in a coordinate system.
The Discrete Global Grid System (DGGS) serialization of a Geometry
The topological dimension of this geometric object, which must be less than or equal to the coordinate dimension. In non-homogeneous collections, this will return the largest topological dimension of the contained objects.
(true) if this geometric object is the empty Geometry. If true, then this geometric object represents the empty point set for the coordinate space.
(true) if this geometric object has no anomalous geometric points, such as self intersection or self tangency.
The number of measurements or axes needed to describe the spatial position of this Geometry in a coordinate system.
Spatial resolution specifies the level of detail of a Geometry. It the smallest dinstinguishable distance between spatially adjacent coordinates.
The spatial resolution of a Geometry in meters.
Spatial resolution specifies the level of detail of a Geometry. It the smallest distinguishable distance between spatially adjacent coordinates.
Spatial accuracy is applicable when a Geometry is used to represent a Feature. It is expressed as a distance that indicates the truthfullness of the positions (coordinates) that define the Geometry. In this case accuracy defines a zone surrounding each coordinate within wich the real positions are known to be. The accuracy value defines this zone as a distance from the coordinate(s) in all directions (e.g. a line, a circle or a sphere, depending on spatial dimension).
The positional accuracy of the coordinates of a Geometry in meters.
The positional accuracy of the coordinates of a Geometry.
This is the superclass of Feature Collection and Geometry Collection.
A collection of individual Spatial Objects.
Connects a Geometry object with its text-based serialization.
A GML serialization of a Geometry object.
A GeoJSON serialization of a Geometry object.
A KML serialization of a Geometry object.
"<https://w3id.org/dggs/auspix> OrdinateList (R3234)"^^<http://www.opengis.net/ont/geosparql#dggsLiteral>
This datatype is not expected to be used directly but to serve as an abstract datatype for a series of specific DGGS literal types, for specific DGGS implementations
A textual serialization of a Discrete Global Grid (DGGS) Geometry object.
Subclasses of this class are expected to be used for instance data.
Anything spatial (being or having a shape, position or an extent).
States that the subject SpatialObject spatially contains the object SpatialObject. DE-9IM: T*TFF*FF*
States that the subject SpatialObject is spatially covered by the object SpatialObject. DE-9IM: TFF*TFT**
States that the subject SpatialObject spatially covers the object SpatialObject. DE-9IM: T*TFT*FF*
States that the subject SpatialObject is spatially inside the object SpatialObject. DE-9IM: TFF*FFT**
States that the subject SpatialObject spatially overlaps the object SpatialObject. DE-9IM: T*T***T**
The recommended way to specify size is by using a subproperty of hasMetricSize. Subproperties of hasSize can be used if more complex expressions are necessary, for example if the unit of length can not be converted to meter, or if additional data are needed to describe the measurement or estimate.
Subproperties of this property are used to indicate the size of a Spatial Object as a measurement or estimate of one or more dimensions of the Spatial Object's spatial presence.
The area of a Spatial Object in square meters.
Subproperties of this property are used to indicate the size of a Spatial Object, as a measurement or estimate of one or more dimensions of the Spatial Object's spatial presence. Units are always metric (meter, square meter or cubic meter).
The length of a Spatial Object in meters.
The length of the perimeter of a Spatial Object in meters.
The volume of a Spatial Object in cubic meters.
The length of the perimeter of a Spatial Object.
The volume of a three-dimensional Spatial Object.
States that the subject SpatialObject is spatially disjoint from the object SpatialObject. DE-9IM: FFTFFTTTT
States that the subject SpatialObject spatially meets the object SpatialObject. DE-9IM: FFTFTTTTT
States that the subject SpatialObject spatially equals the object SpatialObject. DE-9IM: TFFFTFFFT
States that the subject SpatialObject is spatially inside the object SpatialObject. DE-9IM: TFFTFFTTT
States that the subject SpatialObject spatially contains the object SpatialObject. DE-9IM: TTTFFTFFT
States that the subject SpatialObject spatially overlaps the object SpatialObject. DE-9IM: TTTTTTTTT
States that the subject SpatialObject is spatially covered by the object SpatialObject. DE-9IM: TFFTTFTTT
States that the subject SpatialObject spatially covers the object SpatialObject. DE-9IM: TTTFTTFFT
States that the subject SpatialObject spatially contains the object SpatialObject. DE-9IM: T*****FF*
States that the subject SpatialObject spatially crosses the object SpatialObject. DE-9IM: T*T******
States that the subject SpatialObject is not spatially disjoint from the object SpatialObject. DE-9IM: T******** ^ *T******* ^ ***T***** ^ ****T****
States that the subject SpatialObject is spatially disjoint from the object SpatialObject. DE-9IM: FF*FF****
States that the subject SpatialObject spatially meets the object SpatialObject. DE-9IM: FT******* ^ F**T***** ^ F***T****
States that the subject SpatialObject spatially touches the object SpatialObject. DE-9IM: FT******* ^ F**T***** ^ F***T****
The preferred namespace prefix to use when using terms from this vocabulary in an XML document.
The preferred namespace URI to use when using terms from this vocabulary in an XML document.
This document describes a vocabulary for annotating descriptions of vocabularies with examples and usage notes.
VANN: A vocabulary for annotating vocabulary descriptions
A reference to a resource that describes changes between this version of a vocabulary and the previous.
A reference to a resource that provides an example of how this resource can be used.
A group of related terms in a vocabulary.
A reference to a resource that provides information on how this resource is to be used.
Ontology annotations added for the OGC's Open Science Persistent Demonstrator 2025 project
The wfprov ontology shows how to express minimal provenance information about the execution of a workflow described using the wf ontology. Here the concern is mainly the provenance which affects the research object, so in particular how some ro:Resource's might have been generated or used by the execution of a wfdesc:Workflow. The main class here is a wfprov:WorkflowRun which shows how wfprov:Artifact instances (the data) wfprov:wasOutputFrom a wfprov:ProcessRun for generated artifacts, or wfprov:usedInput for consumed artifacts. The WorkflowRun is also a ProcessRun, and so the overall inputs and outputs of thw workflow execution can be described in the same manner. These provenance details are linked to the corresponding wfdesc descriptions using wfdesc:describedbyProcess, wfdesc:describedByWorkflow and wfdesc:describedByParameter. This ontology can be further linked to more specific provenance ontologies like OPM-V or W3C PROV-O, but this should be done separately.
This object property is used to associate a wfprov:Artifact to the wfdesc:Parameter description.
Artifact is a general concept that represents immutable piece of state, which may have a physical embodiment in a physical object, or a digital representation in a computer system. In the case of wfprov, an artifact is used as input to a process run, or produced by the output of a process run.
This property associates a wfprov:WorkflowRun to its corresponding wfdesc:Workflow description.
A workflow run is a wfprov:ProcessRun which have been enacted by a wfprov:WorkflowEngine, according to a workflow definition (which could be wfdesc:describedByWorkflow a wfdesc:Workflow). Such a process typically contains several subprocesses (wfprov:wasPartOfWorkflowRun) corresponding to wfdesc:Process descriptions
This object property associate a wfprov:Processrun to its wfdesc:Process description .
wfprov:wasEnactedBy associates a wfprov:ProcessRun with a wfprov:WorkflowEngine, specifying that the execution of the process was enacted by the engine.
A process run is a particular execution of a wfdesc:Process description (wfprov:describedByProcess), which can wfprov:usedInput some wfprov:Artifact instances, and produce new artifacts (wfprov:wasOutputFrom). A wfprov:WorkflowRun is a specialisation of this class.
A workflow engine is an foaf:Agent that is responsible for enacting a workflow definition (which could be described in a wfdesc:Workflow). The result of workflow enactment gives rise to a wfprov:WorkflowRun.
This property specifies that a wfprov:ProcessRun was executed as part of a wfprov:WorkflowRun. This typically corresponds to wfdesc:hasSubProcess in the workflow description.
This property specifies that a wfprov:ProcessRun used an wfprov:Artifact as an input
This property specifies that a wfprov:Artifact was generated as an output from a wfprov:ProcessRun
Observations following the Floristics - Enhanced Protocol are made in the context of a site visit.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/35175f0d-bdd7-4e32-908f-17f7239e78fa>`. # `<https://linked.data.gov.au/def/nrm/35175f0d-bdd7-4e32-908f-17f7239e78fa>` is the IRI for "Floristics - Enhanced Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/35175f0d-bdd7-4e32-908f-17f7239e78fa`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/33c1752f-b5f3-4ac9-9090-e9a4dd3096d1>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the phenological stages controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the phenological stages controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/33c1752f-b5f3-4ac9-9090-e9a4dd3096d1> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'110398ca-32fa-4f69-b7bb-5aa69d5a5004'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/33c1752f-b5f3-4ac9-9090-e9a4dd3096d1> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/33c1752f-b5f3-4ac9-9090-e9a4dd3096d1>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/33c1752f-b5f3-4ac9-9090-e9a4dd3096d1>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/110398ca-32fa-4f69-b7bb-5aa69d5a5004>`. `<https://linked.data.gov.au/def/nrm/110398ca-32fa-4f69-b7bb-5aa69d5a5004>` is the IRI for "phenological stages".
The value of `tern:vocabulary` _MUST_ match the pattern `110398ca-32fa-4f69-b7bb-5aa69d5a5004$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/971a9588-8728-4a1d-b694-3492d12351bc>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the plant habit types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the plant habit types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/971a9588-8728-4a1d-b694-3492d12351bc> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'015360a2-1e21-4401-be70-25c581569ba6'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/971a9588-8728-4a1d-b694-3492d12351bc> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/971a9588-8728-4a1d-b694-3492d12351bc>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/971a9588-8728-4a1d-b694-3492d12351bc>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/015360a2-1e21-4401-be70-25c581569ba6>`. `<https://linked.data.gov.au/def/nrm/015360a2-1e21-4401-be70-25c581569ba6>` is the IRI for "plant habit types".
The value of `tern:vocabulary` _MUST_ match the pattern `015360a2-1e21-4401-be70-25c581569ba6$`.
Observations following the Floristics - Standard Protocol are made in the context of a site visit.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/bc2ba93e-43f9-425f-83cd-bbf5c422bdf8>`. # `<https://linked.data.gov.au/def/nrm/bc2ba93e-43f9-425f-83cd-bbf5c422bdf8>` is the IRI for "Floristics - Standard Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/bc2ba93e-43f9-425f-83cd-bbf5c422bdf8`.
This is a [Shapes Constraint Language (SHACL)](https://www.w3.org/TR/shacl/) file that specifies constraints for RDF data. It can be used to test the conformance of data to the GeoSPARQL standard. As of GeoSPARQL 1.1, this validator is not normative, only informative, however this is likely to be the basis of future, normative, validators.
# A valid example: the subject of a geo:coordinateDimension property has no other properties with the same name PREFIX geo: <http://www.opengis.net/ont/geosparql#> <feature-x> geo:hasGeometry [ geo:coordinateDimension 2 ; geo:asWKT "POINT (153.084230 -27.322738)"^^geo:wktLiteral ; ] ; .
# An invalid example: the subject of a geo:coordinateDimension property has also another property with with the same property name but a different value PREFIX geo: <http://www.opengis.net/ont/geosparql#> <feature-y> geo:hasGeometry [ geo:coordinateDimension 2 , 3 ; geo:asWKT "POINT (153.084230 -27.322738)"^^geo:wktLiteral ; ] ; .
A geo:Geometry node should have maximum of one outgoing geo:coordinateDimension property.
# A valid example: incoming into the Geometry Blank Node is geo:hasGeometry, outgoing is one geo:asWKT relation PREFIX geo: <http://www.opengis.net/ont/geosparql#> <feature-x> geo:hasGeometry [ geo:asWKT "POINT (153.084230 -27.322738)"^^geo:wktLiteral ; ] ; .
# A valid example: incoming to the Geometry blank node is geo:hasGeometry, outgoing is one geo:asWKT relation. RDF treats both entries as one triple since they are identical. PREFIX geo: <http://www.opengis.net/ont/geosparql#> <feature-x> geo:hasGeometry [ geo:asWKT "POINT (153.084230 -27.322738)"^^geo:wktLiteral ; geo:asWKT "POINT (153.084230 -27.322738)"^^geo:wktLiteral ; ] ; .
# An invalid example: incoming to the Geometry blank node is geo:hasGeometry, outgoing are two geo:asWKT relations PREFIX geo: <http://www.opengis.net/ont/geosparql#> <feature-x> geo:hasGeometry [ geo:asWKT "POINT (153.084230 -27.322738)"^^geo:wktLiteral ; geo:asWKT "POINT (153.08 -27.32)"^^geo:wktLiteral ; ] ; .
Each Geometry node can have a maximum of one outgoing geo:asWKT relation.
Each Geometry node can have a maximum of one outgoing geo:asGML relation.
Each Geometry node can have a maximum of one outgoing geo:asGeoJSON relation.
Each Geometry node can have a maximum of one outgoing geo:asKML relation.
Each Geometry node can have a maximum of one outgoing geo:asDGGS relation.
A geo:Geometry node should have maximum of one outgoing geo:dimension property.
A geo:Geometry node should have maximum of one outgoing geo:isEmpty property.
A geo:Geometry node should have a maximum one outgoing geo:isSimple property.
A geo:Geometry node should have maximum of one outgoing geo:spatialDimension property.
A geo:Geometry node should have maximum of one outgoing geo:hasMetricSpatialResolution property.
A geo:Geometry node should have maximum of one outgoing geo:hasSpatialResolution property.
A geo:Geometry node should have maximum of one outgoing geo:hasMetricSpatialAccuracy.
A geo:Geometry node should have maximum of one outgoing geo:hasSpatialAccuracy property.
The content of an RDF literal with an incoming geo:asWKT relation must conform to a well-formed WKT string, as defined by its official specification (Simple Features Access).
The content of an RDF literal with an incoming geo:asGML relation must conform to a well-formed GML geometry XML string, as defined by its official specification.
The content of an RDF literal with an incoming geo:asGeoJSON relation must conform to a well-formed GeoJSON geometry string, as defined by its official specification.
The content of an RDF literal with an incoming geo:asKML relation must conform to a well-formed KML geometry XML string, as defined by its official specification.
# A valid example: the Resource instance <resource-x-geom1> has an incoming geo:hasDefaultGeometry property and no outgoing geo:hasGeometry or specialization of it PREFIX geo: <http://www.opengis.net/ont/geosparql#> <resource-x> geo:hasDefaultGeometry <resource-x-geom1> . <resource-x-geom1> geo:asWKT "POINT (153.084230 -27.322738)"^^geo:wktLiteral .
# A valid example: the Resource instance <resource-x-geom1> has an incoming geo:hasGeometry property and no outgoing geo:hasGeometry or specialization of it PREFIX geo: <http://www.opengis.net/ont/geosparql#> <resource-x> geo:hasGeometry <resource-x-geom1> . <resource-x-geom1> geo:asWKT "POINT (153.084230 -27.322738)"^^geo:wktLiteral .
# An invalid example: the Resource instance <resource-x> has an incoming geo:hasDefaultGeometry property and an outgoing geo:hasGeometry (i.e. it's a geo:Feature and a geo:Geometry at the same time) PREFIX geo: <http://www.opengis.net/ont/geosparql#> <resource-y> geo:hasDefaultGeometry <resource-x> ; . <resource-x> geo:asWKT "POINT (153.084232 -27.322734)"^^geo:wktLiteral ; geo:hasGeometry [ geo:asWKT "POINT (153.084230 -27.322738)"^^geo:wktLiteral ; ] ; .
# An invalid example: the Resource instance <resource-x> has both an outgoing and an incoming geo:hasGeometry property (i.e. it's a geo:Feature and a geo:Geometry at the same time) PREFIX geo: <http://www.opengis.net/ont/geosparql#> <resource-y> geo:hasGeometry <resource-x> ; . <resource-x> geo:asWKT "POINT (153.084232 -27.322734)"^^geo:wktLiteral ; geo:hasGeometry [ geo:asWKT "POINT (153.084230 -27.322738)"^^geo:wktLiteral ; ] ; .
A Geometry node cannot have an outgoing geo:hasGeometry property, or a specialization of it, since a geo:Geometry cannot be a geo:Feature and entialment of geo:hasGeometry would make it so.
This shape is deactivated since the precise syntax of DGGS literals is now known
The content of an RDF literal with an incoming geo:asDGGS relation must conform to DGGS literals, as defined by their specifications, however GeoSPARQL requires all DGGS Literals to start by indicating the specific DGGS used with an IRI for that DGGS enclosed n < & >
# A valid example: the geo:dimension has value is 2 while the geo:coordinateDimension has value 2 PREFIX geo: <http://www.opengis.net/ont/geosparql#> <feature-x> geo:hasGeometry <feature-x-geom1> . <feature-x-geom1> geo:dimension 2 ; geo:coordinateDimension 2 ; .
# A valid example: the geo:dimension has value is 2 while there is no geo:coordinateDimension PREFIX geo: <http://www.opengis.net/ont/geosparql#> <feature-x> geo:hasGeometry <feature-x-geom1> . <feature-x-geom1> geo:dimension 2 ; .
# An invalid example: the geo:dimension has value is 3 while the geo:coordinateDimension has value 2 PREFIX geo: <http://www.opengis.net/ont/geosparql#> <feature-x> geo:hasGeometry <feature-x-geom1> . <feature-x-geom1> geo:dimension 3 ; geo:coordinateDimension 2 ; .
If both geo:dimension and geo:coordinateDimension properties are asserted, the value of geo:dimension should be less than or equal to the value of geo:coordinateDimension
PREFIX geo: <http://www.opengis.net/ont/geosparql#> SELECT $this WHERE { $this geo:dimension ?dim ; geo:coordinateDimension ?coordDim . FILTER ( ?dim > ?coordDim ) }
# An invalid example: the geo:FeatureCollection instance node has one outgoing rdfs:member relation to a geo:Feature node and another to a geo:Geometry node PREFIX geo: <http://www.opengis.net/ont/geosparql#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> <featureCollection-x> a geo:FeatureCollection ; rdfs:member <featureCollection-x> , <geometry-x> ; . <feature-x> geo:hasGeometry <feature-x-geom1> . <geometry-x> a geo:Geometry .
# A valid example: the geo:FeatureCollection instance node has one outgoing rdfs:member relation to a geo:Feature node PREFIX geo: <http://www.opengis.net/ont/geosparql#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> <featureCollection-x> a geo:FeatureCollection ; rdfs:member <feature-x> . <feature-x> a geo:Feature ; geo:hasGeometry <feature-x-geom1> ; .
An instance of geo:FeatureCollection should only have outgoing rdfs:member going to geo:Feature instances.
PREFIX geo: <http://www.opengis.net/ont/geosparql#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> SELECT $this WHERE { $this rdfs:member ?feature . FILTER NOT EXISTS { ?feature a geo:Feature . } }
# A valid example: the geo:FeatureCollection instance node has one outgoing rdfs:member relation PREFIX geo: <http://www.opengis.net/ont/geosparql#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> <featureCollection-x> a geo:FeatureCollection ; rdfs:member <feature-x> ; . <feature-x> a geo:Feature ; geo:hasGeometry <feature-x-geom1> ; .
# An invalid example: the geo:FeatureCollection instance node has no outgoing rdfs:member relations PREFIX geo: <http://www.opengis.net/ont/geosparql#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> <featureCollection-x> a geo:FeatureCollection .
An instance of geo:FeatureCollection should have at least one outgoing rdfs:member relation.
# A valid example: the geo:GeometryCollection instance node has one outgoing rdfs:member relation to a geo:Geometry node PREFIX geo: <http://www.opengis.net/ont/geosparql#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> <geometryCollection-x> a geo:GeometryCollection ; rdfs:member <geometry-x> ; . <feature-x> geo:hasGeometry <geometry-x> .
# An invalid example: the geo:GeometryCollection instance node has one outgoing rdfs:member relation to geo:Geometry node and one to a non-geo:Geometry node (a geo:Feature) PREFIX geo: <http://www.opengis.net/ont/geosparql#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> <geometryCollection-x> a geo:GeometryCollection ; rdfs:member <geometry-x> , <feature-x> ; . <feature-x> geo:hasGeometry <geometry-x> .
An instance of geo:GeometryCollection should only have outgoing rdfs:member relations to geo:Geometry instances.
PREFIX geo: <http://www.opengis.net/ont/geosparql#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> SELECT $this WHERE { $this rdfs:member ?geometry . FILTER NOT EXISTS { ?feature geo:hasGeometry ?geometry . } }
# A valid example: the geo:GeometryCollection instance node has one incoming rdfs:member relation PREFIX geo: <http://www.opengis.net/ont/geosparql#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> <geometryCollection-x> a geo:GeometryCollection ; rdfs:member <geometry-x> ; . <feature-x> geo:hasGeometry <geometry-x> .
# An invalid example: the geo:GeometryCollection instance node has no outgoing rdfs:member relations PREFIX geo: <http://www.opengis.net/ont/geosparql#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> <geometryCollection-x> a geo:GeometryCollection .
An instance of geo:GeometryCollection should have at least one outgoing rdfs:member relation.
# A valid example: the geo:SpatialObjectCollection instance node has one outgoing rdfs:member relation to a geo:Geometry node and one to a geo:Feature node PREFIX geo: <http://www.opengis.net/ont/geosparql#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> <spatialObjectCollection-x> a geo:SpatialObjectCollection ; rdfs:member <geometry-x> , <feature-y> ; . <feature-x> geo:hasGeometry <geometry-x> . <feature-y> geo:hasGeometry <geometry-y> .
# An invalid example: the geo:SpatialObjectCollection instance node has one outgoing rdfs:member relation to a geo:Geometry node, one outgoing rdfs:member relation to a geo:Feature node and a third outgoing rdfs:member relation from a node of another type (ex:Thing) PREFIX ex: <http://example.com/> PREFIX geo: <http://www.opengis.net/ont/geosparql#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> <spatialObjectCollection-x> a geo:SpatialObjectCollection ; rdfs:member <geometry-x> , <feature-y> , <thing-x> ; . <thing-x> a ex:Thing . <feature-x> geo:hasGeometry <geometry-x> . <feature-y> geo:hasGeometry <geometry-y> .
An instance of geo:SpatialObjectCollection should only have outgoing rdfs:member relations going to geo:SpatialObject instances, or subclasses of them.
PREFIX geo: <http://www.opengis.net/ont/geosparql#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> SELECT $this WHERE { $this rdfs:member ?spatialObject . FILTER NOT EXISTS { ?spatialObject geo:hasGeometry|^geo:hasGeometry ?geometryOrFeature . } }
# A valid example: the geo:SpatialObjectCollection instance node has one outgoing rdfs:member relation PREFIX geo: <http://www.opengis.net/ont/geosparql#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> <spatialObjectCollection-x> a geo:SpatialObjectCollection ; rdfs:member <feature-x> . <feature-x> geo:hasGeometry <geometry-x> .
# An invalid example: the geo:SpatialObjectCollection instance node has no incoming rdfs:member relations PREFIX geo: <http://www.opengis.net/ont/geosparql#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> <spatialObjectCollection-x> a geo:SpatialObjectCollection ; .
An instance of geo:SpatialObjectCollection should have at least one outgoing rdfs:member relation.
# A valid example: the target of a geo:asWKT property is an RDF literal PREFIX geo: <http://www.opengis.net/ont/geosparql#> <feature-x> geo:hasGeometry [ geo:asWKT "POINT (153.084230 -27.322738)"^^geo:wktLiteral ; ] ; .
# An invalid example: the target of a geo:asWKT property is not an RDF literal PREFIX geo: <http://www.opengis.net/ont/geosparql#> <feature-y> geo:hasGeometry [ geo:asWKT <geometry-serialization-node> ; ] ; .
The target of a geo:hasSerialization property, or a specialization of, it should be an RDF literal.
# A valid example: the target of a geo:asWKT property is an RDF literal with datatype geo:wktLiteral PREFIX geo: <http://www.opengis.net/ont/geosparql#> <feature-x> geo:hasGeometry [ geo:asWKT "POINT (153.084230 -27.322738)"^^geo:wktLiteral ; ] ; .
# An invalid example: the target of a geo:asWKT property is an RDF literal but with the wrong datatype (xsd:string) PREFIX geo: <http://www.opengis.net/ont/geosparql#> <feature-z> geo:hasGeometry [ geo:asWKT "POINT (153.084230 -27.322738)" ; ] ; .
The target of a geo:asWKT property should be an RDF literal with datatype geo:wktLiteral.
The target of a geo:asGML property should be an RDF literal with datatype geo:gmlLiteral.
The target of a geo:asGeoJSON property should be an RDF literal with datatype geo:geoJSONLiteral.
The target of a geo:asKML property should be an RDF literal with datatype geo:kmlLiteral.
The target of a geo:asDGGS property should be an RDF literal with datatype geo:dggsLiteral.
Subjects of olis:hasBaseGraph must be instances of olis:RealGraph.
Objects of olis:hasBaseGraph must be instances of olis:RealGraph.
Subjects of olis:hasGraphRole must be instances of olis:RealGraph.
Subjects of olis:hasRulesGraph must be instances of olis:RealGraph.
Objects of olis:hasRulesGraph must be instances of olis:RealGraph.
Olis Real Graphs MUST NOT also be Virtual Graphs
Olis Real Graphs MUST NOT include other graphs
Olis Virtual Graphs MUST NOT link to other graphs via olis:hasBaseGraph
Olis Virtual Graphs MUST NOT link to other graphs via olis:hasRulesGraph
Olis Virtual Graphs MUST NOT link to other graphs via olis:hasGraphRole
Objects of olis:hasGraphRole must be one of gr:Added, gr:Inferred, gr:Original, gr:Removed, gr:Rules
The Friend of a Friend (FOAF) RDF vocabulary, described using W3C RDF Schema and the Web Ontology Language.
A foaf:LabelProperty is any RDF property with texual values that serve as labels.
Indicates an account held by this agent.
An agent (eg. person, group, software or physical artifact).
Indicates the name (identifier) associated with this online account.
Indicates a homepage of the service provide for this online account.
A short informal nickname characterising an agent (includes login identifiers, IRC and other chat nicknames).
A location that something is based near, for some broadly human notion of near.
The birthday of this Agent, represented in mm-dd string form, eg. '12-31'.
A checksum for the DNA of some thing. Joke.
The underlying or 'focal' entity associated with some SKOS-described concept.
An organization funding a project or person.
A textual geekcode for this person, see http://www.geekcode.com/geek.html
The gender of this Agent (typically but not necessarily 'male' or 'female').
A document that this thing is the primary topic of.
An image that can be used to represent some thing (ie. those depictions which are particularly representative of something, eg. one's photo on a homepage).
A page about a topic of interest to this person.
A person known by this person (indicating some level of reciprocated interaction between the parties).
A personal mailbox, ie. an Internet mailbox associated with exactly one owner, the first owner of this mailbox. This is a 'static inverse functional property', in that there is (across time and change) at most one individual that ever has any particular value for foaf:mbox.
The sha1sum of the URI of an Internet mailbox associated with exactly one owner, the first owner of the mailbox.
Indicates the class of individuals that are a member of a Group
A Myers Briggs (MBTI) personality classification.
A project this person has previously worked on.
A phone, specified using fully qualified tel: URI scheme (refs: http://www.w3.org/Addressing/schemes.html#tel).
A .plan comment, in the tradition of finger and '.plan' files.
A link to the publications of this person.
A homepage of a school attended by the person.
A string expressing what the user is happy for the general public (normally) to know about their current activity.
A tipjar document for this agent, describing means for payment and reward.
A weblog of some thing (whether person, group, company etc.).
A work info homepage of some person; a page about their work for some organization.
A workplace homepage of some person; the homepage of an organization they work for.
A thing depicted in this representation.
The primary topic of some page or document.
A project (a collective endeavour of some kind).
The most recent version of this file will always be in the GitHub repository https://github.com/bfo-ontology/bfo-2020
Contributors: Alan Ruttenberg, Albert Goldfain, Barry Smith, Bill Duncan, Bjoern Peters, Chris Mungall, David Osumi-Sutherland, Fabian Neuhaus, James A. Overton, Janna Hastings, Jie Zheng, Jonathan Bona, Larry Hunter, Leonard Jacuzzo, Ludger Jansen, Mark Ressler, Mathias Brochhausen, Mauricio Almeida, Melanie Courtot, Pierre Grenon, Randall Dipert, Robert Rovetto, Ron Rudnicki, Stefan Schulz, Thomas Bittner, Werner Ceusters, Yongqun "Oliver" He
externally-grounded realizable entity
(Elucidation) b is a role means: b is a realizable entity & b exists because there is some single bearer that is in some special physical, social, or institutional set of circumstances in which this bearer does not have to be & b is not such that, if it ceases to exist, then the physical make-up of the bearer is thereby changed
The priest role, the student role, the role of subject in a clinical trial, the role of a stone in marking a property boundary, the role of a boundary to demarcate two neighbouring administrative territories, the role of a building in serving as a military target.
role
(Elucidation) b is a realizable entity means: b is a specifically dependent continuant that inheres in some independent continuant which is not a spatial region and is of a type some instances of which are realized in processes of a correlated type
The role of being a doctor, the role of this boundary to delineate where Utah and Colorado meet, the function of your reproductive organs, the disposition of your blood to coagulate, the disposition of this piece of metal to conduct electricity.
realizable entity
internally-grounded realizable entity
(Elucidation) b is a disposition means: b is a realizable entity & b is such that if it ceases to exist, then its bearer is physically changed, & b's realization occurs when and because this bearer is in some special physical circumstances, & this realization occurs in virtue of the bearer's physical make-up
An atom of element X has the disposition to decay to an atom of element Y; the cell wall is disposed to transport cellular material through endocytosis and exocytosis; certain people have a predisposition to colon cancer; children are innately disposed to categorize objects in certain ways.
disposition
(Elucidation) a fiat object part b is a material entity which is such that for all times t, if b exists at t then there is some object c such that b is a proper continuant part of c at t and b is demarcated from the remainder of c by one or more fiat surfaces
The upper and lower lobes of the left lung, the dorsal and ventral surfaces of the body, the Western hemisphere of the Earth, the FMA:regional parts of an intact human body.
fiat object part
(Elucidation) A material entity is an independent continuant that at all times at which it exists has some portion of matter as continuant part
A human being, the undetached arm of a human being, an aggregate of human beings.
material entity
(Elucidation) an object aggregate is a material entity consisting exactly of a plurality (≥1) of objects as member parts which together form a unit
The aggregate of the musicians in a symphony orchestra and their instruments, the aggregate of bearings in a constant velocity axle joint, the nitrogen atoms in the atmosphere, a collection of cells in a blood biobank. NOTE 1: 'Exactly' means that there are no parts of the object aggregate other than its member parts. NOTE 2: The unit can, at certain times, consist of exactly one object, for example, when a wolf litter loses all but one of its pups, but it must at some time have a plurality of member parts.
object aggregate
(Elucidation) an object is a material entity which manifests causal unity & is of a type instances of which are maximal relative to the sort of causal unity manifested
An organism, a fish tank, a planet, a laptop, a valve, a block of marble, an ice cube.
object
A description of three primary sorts of causal unity is provided in Basic Formal Ontology 2.0. Specification and User’s Guide
(Elucidation) A function is a disposition that exists in virtue of the bearer's physical make-up and this physical make-up is something the bearer possesses because it came into being either through evolution (in the case of natural biological entities) or through intentional design (in the case of artefacts), in order to realize processes of a certain sort
The function of a hammer to drive in nails, the function of a heart pacemaker to regulate the beating of a heart through electricity.
function
b located in c at all times =Def for all times t, b exists at t implies (b and c are independent continuants and not spatial regions, and the spatial region which b occupies at t is a (proper or improper) continuant part of the spatial region which c occupies at t)
located in at all times
b is an independent continuant =Def b is a continuant which is such that there is no c such that b s-depends on c and no c such that b g-depends on c
An atom, a molecule, an organism, a heart, a chair, the bottom right portion of a human torso, a leg; the interior of your mouth; a spatial region; an orchestra.
independent continuant
(Elucidation) A spatial region is a continuant entity that is a continuant part of the spatial projection of a portion of spacetime at a given time
As for zero-dimensional spatial region, one-dimensional spatial region, two-dimensional spatial region, three-dimensional spatial region.
spatial region
b located in c at some time =Def for some time t (b and c are independent continuants and not spatial regions, and the spatial region which b occupies at t is a (proper or improper) continuant part of the spatial region which c occupies at t)
located in at some time
(Elucidation) exists at is a relation between a particular and some temporal region at which the particular exists
First World War exists at 1914-1916, Mexico exists at January 1, 2000.
exists at
b has proper continuant part c at all times =Def c proper continuant part of b at all times
has proper continuant part at all times
(Elucidation) A continuant is an entity that persists, endures, or continues to exist through time while maintaining its identity
A human being, a tennis ball, a cave, a region of space, someone's temperature.
continuant
b has continuant part c at all times =Def for all times t, b exists at t implies (b and c are continuants & b is a part of c at t)
has continuant part at all times
b has proper continuant part c at some time =Def c proper continuant part of b at some time
has proper continuant part at some time
b has material basis c at all times =Def For all times t, b exists at t implies (b is a disposition & c is a material entity & there is some d bearer of b & c continuant part of d at t & d has disposition b because c continuant part of d at t)
has material basis at all times
b has material basis c at some time =Def For some time t (b is a disposition & c is a material entity & there is some d bearer of b & c continuant part of d at t & d has disposition b because c continuant part of d at t)
has material basis at some time
b proper continuant part of c at all times =Def for all times t, b exists at t implies (b continuant part of c at t & not (c proper continuant part of b at t))
proper continuant part of at all times
b proper continuant part of c at some time =Def for some time t (b continuant part of c at t & not (c continuant part of b at t)
proper continuant part of at some time
b continuant part of c at all times =Def for all times t, (b exists at t, implies b continuant part of c at t & t is a temporal region & b and c are continuants)
Centre of mass of a material entity continuant part of material entity at all times; continuant fiat external boundary of an object continuant part of object at all times.
continuant part of at all times
b is a relational quality =Def b is a quality and there exists c and d such that b and c are not identical, & b s-depends on c & b s-depends on d
A marriage bond, an instance of love, an obligation between one person and another.
relational quality
(Elucidation) a quality is a specifically dependent continuant that, in contrast to roles and dispositions, does not require any further process in order to be realized
The colour of a tomato, the ambient temperature of this portion of air, the length of the circumference of your waist, the shape of your nose, the shape of your nostril, the mass of this piece of gold.
quality
(Elucidation) temporally projects onto is a relation between a spatiotemporal region s and some temporal region which is the temporal extent of s
The world line of a particle temporally projects onto the temporal region extending from the beginning to the end of the existence of the particle.
temporally projects onto
(Elucidation) A spatiotemporal region is an occurrent that is an occurrent part of spacetime
The spatiotemporal region occupied by the development of a cancer tumour, the spatiotemporal region occupied by an orbiting satellite.
spatiotemporal region
'Spacetime' here refers to the maximal instance of the universal spatiotemporal region.
(Elucidation) A temporal region is an occurrent over which processes can unfold
As for zero-dimensional temporal region and one-dimensional temporal region.
temporal region
b material basis of c at all times =Def for all times t, b exists at t implies (c has material basis b at t)
material basis of at all times
b material basis of c at some time =Def at some time t (c has material basis b at t)
material basis of at some time
an s-dependent continuant b concretizes a g-dependent continuant c at all times =Def for all times t, b exists at t implies (c is the pattern or content which b shares at t with actual or potential copies)
concretizes at all times
b is a specifically dependent continuant =Def b is a continuant & there is some independent continuant c which is not a spatial region & which is such that b s-depends on c
(with one bearer) The mass of this tomato, the pink colour of a medium rare piece of grilled filet mignon at its centre, the smell of this portion of mozzarella, the disposition of this fish to decay, the role of being a doctor, the function of this heart: to pump blood, the shape of this hole; (with multiple bearers:) John's love for Mary, the ownership relation between John and this statue, the relation of authority between John and his subordinates.
specifically dependent continuant
On the multiple bearers case, see relational quality.
(Elucidation) p is a process means p is an occurrent that has some temporal proper part and for some time t, p has some material entity as participant at t
An act of selling, the life of an organism, a process of sleeping, a process of cell-division, a beating of the heart, a process of meiosis, the taxiing of an aircraft, the programming of a computer.
process
g-dependent continuant
(Elucidation) a generically dependent continuant is an entity that exists in virtue of the fact that there is at least one of what may be multiple copies; it is the content or the pattern that the multiple copies share
The pdf file on your laptop, the pdf file that is a copy thereof on my laptop; the sequence of this protein molecule; the sequence that is a copy thereof in that protein molecule; the content that is shared by a string of dots and dashes written on a page and the transmitted Morse code signal; the content of a sentence; an engineering blueprint.
generically dependent continuant
an s-dependent continuant b concretizes a g-dependent continuant c at some time =Def for some time t (c is the pattern or content which b shares at t with actual or potential copies)
concretizes at some time
a g-dependent continuant c is concretized by an s-dependent continuant or process b at all times =Def for all times t, b exists at t implies (b concretizes c at t)
is concretized by at all times
a g-dependent continuant c is concretized at some time by an s-dependent continuant or process b =Def for some time t, b concretizes c at t)
is concretized by at some time
b participates in p at all times =Def for all times t, b exists at t implies (p has participant b at t)
participates in at all times
b participates in p at some time =Def for some time t (p has participant b at t)
participates in at some time
p has participant c at all times =Def for all times t, p exists at t implies (p is a process, c is a continuant, and c participates in p some way at t)
has participant at all times
p has participant c at some time =Def for some time t (p is a process, c is a continuant, and c participates in p some way at t)
has participant at some time
b location of c at all times =Def for all times t, b exists at t implies (c located in b at t)
location of at all times
b location of c at some time =Def for some time t (c located in b at t)
location of at some time
b has member part c at all times =Def for all times t, b exists at t implies (c member part b at t)
has member part at all times
b has member part c at some time =Def for some time t (c member part of b at t)
has member part at some time
b member part of c at all times =Def for all times t, b exists at t implies (b is an object & c is an object aggregate & there is at t a mutually exhaustive and pairwise disjoint partition of c into objects x1,..., xn (for some n ≠ 1) with b = xi (for some 1 <= i <= n))
member part of at all times
b member part of c at some time =Def for some time t (b is an object & there is at t a mutually exhaustive and pairwise disjoint partition of c into objects x1, ..., xn (for some n ≠ 1) with b = xi (for some 1 <= i <= n))
member part of at some time
p occupies temporal region t =Def the spatiotemporal region occupied by p temporally projects onto t
The Second World War occupies the temporal region September 1, 1939 - September 2, 1945.
occupies temporal region
p is a process boundary =Def p is a temporal part of a process & p has no proper temporal parts
The boundary between the 2nd and 3rd year of your life.
process boundary
(Elucidation) p occupies spatiotemporal region s is a relation between an occurrent p and the spatiotemporal region s which is its spatiotemporal extent
A particle emitted by a nuclear reactor occupies the spatiotemporal region which is its trajectory.
occupies spatiotemporal region
(Elucidation) a temporal interval is a one-dimensional temporal region that is continuous, thus without gaps or breaks
The year 2018.
temporal interval
A one-dimensional temporal region can include as parts not only temporal intervals but also temporal instants separated from other parts by gaps.
(Elucidation) A one-dimensional temporal region is a temporal region is a whole that has a temporal interval and zero or more temporal intervals and temporal instants as parts
The temporal region during which a process occurs.
one-dimensional temporal region
an independent continuant c that is not a spatial region occupies spatial region r at all times =Def for all times t, b exists at t implies (every continuant part of c occupies some continuant part of r at t and no continuant part of c occupies any spatial region that is not a continuant part of r at t)
occupies spatial region at all times
an independent continuant c that is not a spatial region occupies spatial region r at some time =Def for some time t (every continuant part of c occupies some continuant part of r at t and no continuant part of c occupies any spatial region that is not a continuant part of r at t)
occupies spatial region at some time
b spatially projects onto c at all times =Def for all times t, b exists at t implies (b is a spatiotemporal region and c is a spatial region and c is the spatial extent of b at t)
spatially projects onto at all times
b spatially projects onto c at some time =Def for some time t (b is a spatiotemporal region and c is a spatial region and c is the spatial extent of b at t)
spatially projects onto at some time
g-depends on at all times
a g-dependent continuant b g-depends on an independent continuant c at all times =Def for all times t, b exists at t implies (there inheres in c an s-dependent continuant which concretizes b at t)
generically depends on at all times
g-depends on at some time
a g-dependent continuant b g-depends on an independent continuant c at some time =Def for some time t (there inheres in c an s-dependent continuant which concretizes b at t)
generically depends on at some time
b is carrier of c at all times =Def for all times t, b exists at t implies (c g-depends on b at t)
is carrier of at all times
b is carrier of c at some time =Def for some time t (c g-depends on b at t)
is carrier of at some time
b has realization c =Def c realizes b
As for realizes
has realization
(Elucidation) b realizes c means: b is a process & c is a realizable entity that inheres in d & for all t, if b has participant d at t then c exists at t & the type instantiated by b is correlated with the type instantiated by c
A disposition to go bald is realized in a balding process; a role of student is realized in studying processes; the pumping function of a heart is realized in processes of pumping.
realizes
b preceded by c =Def b precedes c
The temporal region occupied by the second half of the match is preceded by the temporal region occupied by the first half of the match.
preceded by
(Elucidation) An occurrent is an entity that unfolds itself in time or it is the start or end of such an entity or it is a temporal or spatiotemporal region
As for process, history, process boundary, spatiotemporal region, zero-dimensional temporal region, one-dimensional temporal region, temporal interval, temporal instant.
occurrent
(Elucidation) If o, o' are occurrents and t is the temporal extent of o and t' is the temporal extent of o' then o precedes o' means: either last instant of o is before first instant of o' or last instant of o = first instant of o' and neither o nor o' are temporal instants
The temporal region occupied by Mary's birth precedes the temporal region occupied by Mary's death. NOTE 1: Each temporal region is its own temporal extent. The temporal extent of a spatiotemporal region is the temporal region it temporally projects onto. The temporal extent of a process or process boundary that occupies temporal region t is t. NOTE 2: Precedes defines a strict partial order on occurrents.
precedes
b occurs in c =Def b is a process or a process boundary and c is a material entity or immaterial entity & there exists a spatiotemporal region r and b occupies spatiotemporal region r & for all t, if b exists at t then c exists at t & there exist spatial regions s and s' where b spatially projects onto s at t & c occupies spatial region s' at t & s is a continuant part of s' at t
A process of digestion occurs in the interior of an organism, a process of loading artillery rounds into a tank cannon occurs in the interior of the tank.
occurs in
(Elucidation) b is a site means: b is a three-dimensional immaterial entity whose boundaries either (1) (partially or wholly) coincide with the boundaries of one or more material entities or (2) have locations determined in relation to some material entity
A hole in a portion of cheese, a rabbit hole, the Grand Canyon, the Piazza San Marco, the kangaroo-joey-containing hole of a kangaroo pouch, your left nostril (a fiat part - the opening - of your left nasal cavity), the lumen of your gut, the hold of a ship, the interior of the trunk of your car, hole in an engineered floor joist; An air traffic control region of type A is determined in terms of elevation above mean sea level of lower and upper boundaries.
site
b environs c =Def c occurs in b
Mouth environs process of mastication, city environs traffic.
environs
b has proper occurrent part c =Def b has occurrent part c & b and c are not identical
As for has occurrent part.
has proper occurrent part
(Elucidation) b has occurrent part c means: c is a part of b & b and c are occurrents
Mary's life has occurrent part Mary's 5th birthday.
has occurrent part
b proper occurrent part of c =Def b occurrent part of c & b and c are not identical
As for occurrent part of.
proper occurrent part of
b proper temporal part of c =Def b temporal part of c & not (b = c)
As for temporal part of.
proper temporal part of
b temporal part of c =Def b occurrent part of c & either b and c are temporal regions or b and c are spatiotemporal regions & b temporally projects onto an occurrent part of the temporal region that c temporally projects onto or b and c are processes or process boundaries & b occupies a temporal region that is an occurrent part of the temporal region that c occupies
Your heart beating from 4pm to 5pm today is a temporal part of the process of your heart beating; the 4th year of your life is a temporal part of your life, as is the process boundary which separates the 3rd and 4th years of your life; the first quarter of a game of football is a temporal part of the whole game.
temporal part of
b has proper temporal part c =Def c proper temporal part of b
As for has temporal part.
has proper temporal part
(Elucidation) b occurrent part of c =Def c has occurrent part b
Mary's 5th birthday is an occurrent part of Mary's life; the first set of the tennis match is an occurrent part of the tennis match.
occurrent part of
(Elucidation) a fiat surface is a two-dimensional continuant fiat boundary that is self-connected
The surface of the Earth, the plane separating the smoking from the non-smoking zone in a restaurant
fiat surface
(Elucidation) b is a continuant fiat boundary means: b is an immaterial entity that is of zero, one or two dimensions, which is such that there is no time t when b has a spatial region as continuant part at t, and whose location is determined in relation to some material entity
As for fiat point, fiat line, fiat surface.
continuant fiat boundary
b has continuant part c at some time =Def for some time t (b and c are continuants & b is a part of c at t)
has continuant part at some time
b has temporal part c =Def c temporal part of b
Your life has temporal part the first year of your life.
has temporal part
(Elucidation) b history of c if c is a material entity and b is a history that is the unique history of c
This life is the history of this organism.
history of
(Elucidation) A history is a process that is the sum of the totality of processes taking place in the spatiotemporal region occupied by the material part of a material entity
The life of an organism from the beginning to the end of its existence.
history
b has history c =Def c history of b
This organism has history this life.
has history
b bearer of c =Def c inheres in b
A patch of ink is the bearer of a colour quality; an organism is the bearer of a temperature quality.
bearer of
s-depended on by
b s-depended on by c =Def c specifically depends on b
Coloured object s-depended on by colour.
specifically depended on by
b inheres in c =Def b is a specifically dependent continuant & c is an independent continuant that is not a spatial region & b s-depends on c
A shape inheres in a shaped object; a mass inheres in a material entity.
inheres in
s-depends on
(Elucidation) b specifically depends on c means: b and c do not share common parts & b is of a nature such that at all times t it cannot exist at t unless c exists at t & b is not a boundary of c
A shape s-depends on the shaped object, hue, saturation and brightness of a colour sample s-depend on each other.
specifically depends on
The analogue of s-dependence for occurrents is has participant.
temporal instant t first instant of temporal region t' =Def t precedes all temporal parts of t' other than t
An hour starting at midnight yesterday has first instant midnight yesterday.
first instant of
(Elucidation) a temporal instant is a zero-dimensional temporal region that has no proper temporal part
The millennium.
temporal instant
t has first instant t' =Def t' first instant of t
The first hour of a year has first instant midnight on December 31.
has first instant
temporal instant t last instant of temporal region t' =Def all temporal parts of t' other than t precede t
Last midnight is the last instant of yesterday.
last instant of
t has last instant t' =Def t' last instant of t
The last hour of a year has last instant midnight December 31.
has last instant
(Elucidation) An entity is anything that exists or has existed or will exist
Julius Caesar, the Second World War, your body mass index, Verdi's Requiem.
entity
(Elucidation) A two-dimensional spatial region is a spatial region that is a whole consisting of a surface together with zero or more surfaces and/or spatial regions of lower dimension as parts
The surface of a sphere-shaped part of space, an infinitely thin plane in space.
two-dimensional spatial region
(Elucidation) A one-dimensional spatial region is a whole consisting of a line together with zero or more lines and/or points as parts
An edge of a cube-shaped portion of space, a line connecting two points, two parallel lines extended in space.
one-dimensional spatial region
(Elucidation) A zero-dimensional spatial region is one or a collection of more than one spatially disjoint points in space
The spatial region occupied at some time instant by the North Pole.
zero-dimensional spatial region
(Elucidation) A three-dimensional spatial region is a whole consisting of a spatial volume together with zero or more spatial volumes and/or spatial regions of lower dimension as parts
A cube-shaped region of space, a sphere-shaped region of space, the region of space occupied by all and only the planets in the solar system at some point in time.
three-dimensional spatial region
b continuant part of c at some time =Def for some time t (b exists at t and c exists at t and b continuant part of c at t & t is a temporal region & b and c are continuants)
Milk teeth continuant part of human at some time; surgically removed tumour continuant part of organism at some time.
continuant part of at some time
(Elucidation) a fiat line is a one-dimensional continuant fiat boundary that is continuous
The Equator, all geopolitical boundaries, all lines of latitude and longitude, the median sulcus of your tongue, the line separating the outer surface of the mucosa of the lower lip from the outer surface of the skin of the chin.
fiat line
(Elucidation) a fiat point is a zero-dimensional continuant fiat boundary that consists of a single point
The geographic North Pole; the quadripoint where the boundaries of Colorado, Utah, New Mexico and Arizona meet, the point of origin of some spatial coordinate system.
fiat point
a is an immaterial entity =Def a is an independent continuant which is such that there is no time t when it has a material entity as continuant part at t
As for fiat point, fiat line, fiat surface, site.
immaterial entity
(Elucidation) A zero-dimensional temporal region is a temporal region that is a whole consisting of one or more separated temporal instants as parts
A temporal region that is occupied by a process boundary; the moment at which a finger is detached in an industrial accident.
zero-dimensional temporal region
This property is intended to be used with non-literal values. The described resource may be derived from the related resource in whole or in part. Best practice is to identify the related resource by means of a URI or a string conforming to a formal identification system.
A related resource from which the described resource is derived.
Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource.
This property is intended to be used with non-literal values. This property is an inverse property of Is Part Of.
A related resource that is included either physically or logically in the described resource.
This property is intended to be used with non-literal values. This property is an inverse property of Has Part.
A related resource in which the described resource is physically or logically included.
An entity responsible for making the resource available.
Recommended practice is to identify the related resource by means of a URI. If this is not possible or feasible, a string conforming to a formal identification system may be provided.
The guidelines for using names of persons or organizations as creators apply to contributors.
An entity responsible for making contributions to the resource.
Recommended practice is to describe the date, date/time, or period of time as recommended for the property Date, of which this is a subproperty.
Recommended practice is to identify the creator with a URI. If this is not possible or feasible, a literal value that identifies the creator may be provided.
An entity responsible for making the resource.
Date may be used to express temporal information at any level of granularity. Recommended practice is to express the date, date/time, or period of time according to ISO 8601-1 [[ISO 8601-1](https://www.iso.org/iso-8601-date-and-time-format.html)] or a published profile of the ISO standard, such as the W3C Note on Date and Time Formats [[W3CDTF](https://www.w3.org/TR/NOTE-datetime)] or the Extended Date/Time Format Specification [[EDTF](http://www.loc.gov/standards/datetime/)]. If the full date is unknown, month and year (YYYY-MM) or just year (YYYY) may be used. Date ranges may be specified using ISO 8601 period of time specification in which start and end dates are separated by a '/' (slash) character. Either the start or end date may be missing.
A point or period of time associated with an event in the lifecycle of the resource.
Date of formal issuance of the resource.
Recommended practice is to identify the license document with a URI. If this is not possible or feasible, a literal value that identifies the license may be provided.
A legal document giving official permission to do something with the resource.
Recommended practice is to refer to the rights holder with a URI. If this is not possible or feasible, a literal value that identifies the rights holder may be provided.
A person or organization owning or managing rights over the resource.
Recommended practice is to refer to the subject with a URI. If this is not possible or feasible, a literal value that identifies the subject may be provided. Both should preferably refer to a subject in a controlled vocabulary.
Recommended practice is to identify the resource by means of a string conforming to an identification system. Examples include International Standard Book Number (ISBN), Digital Object Identifier (DOI), and Uniform Resource Name (URN). Persistent identifiers should be provided as HTTP URIs.
An unambiguous reference to the resource within a given context.
Recommended practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [[DCMI-TYPE](http://dublincore.org/documents/dcmi-type-vocabulary/)]. To describe the file format, physical medium, or dimensions of the resource, use the property Format.
Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights. Recommended practice is to refer to a rights statement with a URI. If this is not possible or feasible, a literal value (name, label, or short text) may be provided.
Information about rights held in and over the resource.
The statement may include a description of any changes successive custodians made to the resource.
A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation.
Dublin Core Metadata Terms
A resource that acts or has the power to act.
Changes in version imply substantive changes in content rather than differences in format. This property is intended to be used with non-literal values. This property is an inverse property of Is Version Of.
A related resource that is a version, edition, or adaptation of the described resource.
A book, article, or other documentary resource.
The extent or range of judicial, law enforcement, or other authority.
A location, period of time, or jurisdiction.
A legal document giving official permission to do something with a resource.
A statement about the intellectual property rights (IPR) held in or over a resource, a legal document giving official permission to do something with a resource, or a statement about access rights.
Written, spoken, sign, and computer languages are linguistic systems.
A system of signs, symbols, sounds, gestures, or rules used in communication.
A method by which resources are added to a collection.
A process that is used to engender knowledge, attitudes, and skills.
An interval of time that is named or defined by its start and end dates.
A plan or course of action by an authority, intended to influence and determine decisions, actions, and other matters.
Any changes in ownership and custody of a resource since its creation that are significant for its authenticity, integrity, and interpretation.
Examples include a number of pages, a specification of length, width, and breadth, or a period in hours, minutes, and seconds.
A dimension or extent, or a time taken to play or execute.
A reference point against which other things can be evaluated or compared.
The set of regions in space defined by their geographic coordinates according to the DCMI Box Encoding Scheme.
The set of classes specified by the DCMI Type Vocabulary, used to categorize the nature or genre of the resource.
The set of conceptual resources specified by the Dewey Decimal Classification.
The set of media types specified by the Internet Assigned Numbers Authority.
The set of codes listed in ISO 3166-1 for the representation of names of countries.
The three-letter alphabetic codes listed in ISO639-2 for the representation of names of languages.
The set of three-letter codes listed in ISO 639-3 for the representation of names of languages.
The set of conceptual resources specified by the Library of Congress Classification.
The set of labeled concepts specified by the Library of Congress Subject Headings.
The set of labeled concepts specified by the Medical Subject Headings.
The set of conceptual resources specified by the National Library of Medicine Classification.
The set of points in space defined by their geographic coordinates according to the DCMI Point Encoding Scheme.
The set of tags, constructed according to RFC 1766, for the identification of languages.
RFC 3066 has been obsoleted by RFC 4646.
The set of tags constructed according to RFC 3066 for the identification of languages.
The set of tags constructed according to RFC 4646 for the identification of languages.
The set of tags constructed according to RFC 5646 for the identification of languages.
The set of places specified by the Getty Thesaurus of Geographic Names.
The set of conceptual resources specified by the Universal Decimal Classification.
The set of identifiers constructed according to the generic syntax for Uniform Resource Identifiers as specified by the Internet Engineering Task Force.
The set of dates and times constructed according to the W3C Date and Time Formats Specification.
Access Rights may include information regarding access or restrictions based on privacy, security, or other policies.
Information about who access the resource or an indication of its security status.
Recommended practice is to use a value from the Collection Description Accrual Method Vocabulary [[DCMI-ACCRUALMETHOD](https://dublincore.org/groups/collections/accrual-method/)].
The method by which items are added to a collection.
Recommended practice is to use a value from the Collection Description Frequency Vocabulary [[DCMI-COLLFREQ](https://dublincore.org/groups/collections/frequency/)].
The frequency with which items are added to a collection.
Recommended practice is to use a value from the Collection Description Accrual Policy Vocabulary [[DCMI-ACCRUALPOLICY](https://dublincore.org/groups/collections/accrual-policy/)].
The policy governing the addition of items to a collection.
The distinction between titles and alternative titles is application-specific.
Date that the resource became or will become available.
Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.
A bibliographic reference for the resource.
An established standard to which the described resource conforms.
Recommended practice is to describe the date, date/time, or period of time as recommended for the property Date, of which this is a subproperty. Examples of resources to which a date of acceptance may be relevant are a thesis (accepted by a university department) or an article (accepted by a journal).
Typically a year. Recommended practice is to describe the date, date/time, or period of time as recommended for the property Date, of which this is a subproperty.
Recommended practice is to describe the date, date/time, or period of time as recommended for the property Date, of which this is a subproperty. Examples of resources to which a 'Date Submitted' may be relevant include a thesis (submitted to a university department) or an article (submitted to a journal).
A class of agents, defined in terms of progression through an educational or training context, for which the described resource is intended.
Recommended practice is to use this property with non-literal values from a vocabulary of audience types.
A class of agents for whom the resource is intended or useful.
Recommended practice is to specify the file size in megabytes and duration in ISO 8601 format.
Recommended practice is to use a controlled vocabulary where available. For example, for file formats one could use the list of Internet Media Types [[MIME](https://www.iana.org/assignments/media-types/media-types.xhtml)]. Examples of dimensions include size and duration.
The file format, physical medium, or dimensions of the resource.
This property is intended to be used with non-literal values. This property is an inverse property of Is Format Of.
A related resource that is substantially the same as the pre-existing described resource, but in another format.
Instructional Method typically includes ways of presenting instructional materials or conducting instructional activities, patterns of learner-to-learner and learner-to-instructor interactions, and mechanisms by which group and individual levels of learning are measured. Instructional methods include all aspects of the instruction and learning processes from planning and implementation through evaluation and feedback.
A process, used to engender knowledge, attitudes and skills, that the described resource is designed to support.
This property is intended to be used with non-literal values. This property is an inverse property of Has Format.
A pre-existing related resource that is substantially the same as the described resource, but in another format.
This property is intended to be used with non-literal values. This property is an inverse property of References.
A related resource that references, cites, or otherwise points to the described resource.
This property is intended to be used with non-literal values. This property is an inverse property of Replaces.
A related resource that supplants, displaces, or supersedes the described resource.
This property is intended to be used with non-literal values. This property is an inverse property of Requires.
A related resource that requires the described resource to support its function, delivery, or coherence.
Changes in version imply substantive changes in content rather than differences in format. This property is intended to be used with non-literal values. This property is an inverse property of Has Version.
A related resource of which the described resource is a version, edition, or adaptation.
Recommended practice is to use either a non-literal value representing a language from a controlled vocabulary such as ISO 639-2 or ISO 639-3, or a literal value consisting of an IETF Best Current Practice 47 [[IETF-BCP47](https://tools.ietf.org/html/bcp47)] language tag.
In an educational context, a mediator might be a parent, teacher, teaching assistant, or care-giver.
An entity that mediates access to the resource.
The material or physical carrier of the resource.
This property is intended to be used with non-literal values. This property is an inverse property of Is Referenced By.
A related resource that is referenced, cited, or otherwise pointed to by the described resource.
This property is intended to be used with non-literal values. This property is an inverse property of Is Replaced By.
A related resource that is supplanted, displaced, or superseded by the described resource.
This property is intended to be used with non-literal values. This property is an inverse property of Is Required By.
A related resource that is required by the described resource to support its function, delivery, or coherence.
Spatial characteristics of the resource.
Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names [[TGN](https://www.getty.edu/research/tools/vocabulary/tgn/index.html)]. Where appropriate, named places or time periods may be used in preference to numeric identifiers such as sets of coordinates or date ranges. Because coverage is so broadly defined, it is preferable to use the more specific subproperties Temporal Coverage and Spatial Coverage.
The spatial or temporal topic of the resource, spatial applicability of the resource, or jurisdiction under which the resource is relevant.
Temporal characteristics of the resource.
Date (often a range) of validity of a resource.
The set of time intervals defined by their limits according to the DCMI Period Encoding Scheme.
This model was created for Queensland Spatial Information's CAM (Cadastre & Addressing Modernisation) project in 2023.
(c) The State of Queensland (Department of Resources) 2023
This model is for roads information in Queensland, however it is a candidate ANZ model also, and may, in the near future, be expanded with feedback form other jurisdictions and a process through the Inter Governmental Committee on Surveying & Mapping (ICSM) to ensure it covers all ANZ jurisdictions' needs. This model is a stand-alone model for roads information, however it is also designed to work as a Component Model part of an integrative multi-model regime for Spatial Information Queensland known as a Supermodel (see https://linked.data.gov.au/def/qsi-supermodel). The QSI Supermodel aims to integrate cadastre, address, place name, roads and other information.
Intergovernmental Committee on Surveying & Mapping
This validator is a Shapes Constraint Language (SHACL) resource that can be used to check the conformance of RDF data to the Address Model (<https://linked.data.gov.au/def/addr>). It only check for 3 things which are described in individual shapes within this validator
(c) Intergovernmental Committee on Surveying & Mapping 2026
Each Address must have at least one part which must be Compound Names, indicated with schema:hasPart
Each Address must indicate an IRI with the predicate cn:isNameFor
Each Address must indicate at least one Geocode with the predicate addr:hasGeocode
Each Geometry MUST have exactly one geo:wktLiteral value for the predicate geo:asWKT
Each Geocode role MUST be an IRI and within the Geocode Types vocabulary
Each Address MUST have at least one Lifecycle Stage indicated by hasLifecycleStage
Each Lifecycle Stage MUST have exactly one additional type indicating a concept from the Lifecycle Stage Types vocabulary
A derivation is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity.
The more specific subproperties of prov:wasDerivedFrom (i.e., prov:wasQuotedFrom, prov:wasRevisionOf, prov:hadPrimarySource) should be used when applicable.
An activity association is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity.
An instance of prov:Association provides additional descriptions about the binary prov:wasAssociatedWith relation from an prov:Activity to some prov:Agent that had some responsiblity for it. For example, :baking prov:wasAssociatedWith :baker; prov:qualifiedAssociation [ a prov:Association; prov:agent :baker; :foo :bar ].
An instance of prov:Attribution provides additional descriptions about the binary prov:wasAttributedTo relation from an prov:Entity to some prov:Agent that had some responsible for it. For example, :cake prov:wasAttributedTo :baker; prov:qualifiedAttribution [ a prov:Attribution; prov:entity :baker; :foo :bar ].
Attribution is the ascribing of an entity to an agent. When an entity e is attributed to agent ag, entity e was generated by some unspecified activity that in turn was associated to agent ag. Thus, this relation is useful when the activity is not known, or irrelevant.
An agent is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity.
An activity a2 is dependent on or informed by another activity a1, by way of some unspecified entity that is generated by a1 and used by a2.
This property behaves in spirit like rdf:object; it references the object of a prov:wasInfluencedBy triple.
The prov:agent property references an prov:Agent which influenced a resource. This property applies to an prov:AgentInfluence, which is given by a subproperty of prov:qualifiedInfluence from the influenced prov:Entity, prov:Activity or prov:Agent.
The _optional_ Plan adopted by an Agent in Association with some Activity. Plan specifications are out of the scope of this specification.
This property has multiple RDFS domains to suit multiple OWL Profiles. See PROV-O OWL Profile.
prov:hadRole references the Role (i.e. the function of an entity with respect to an activity), in the context of an instantaneous usage, generation, association, start, and end.
The _optional_ Role that an Entity assumed in the context of an Activity. For example, :baking prov:used :spoon; prov:qualified [ a prov:Usage; prov:entity :spoon; prov:hadRole roles:mixing_implement ].
If this Entity prov:wasAttributedTo Agent :ag, then it can qualify how it was influenced using prov:qualifiedAttribution [ a prov:Attribution; prov:agent :ag; :foo :bar ].
Attribution is the ascribing of an entity to an agent.
It is the intent that the property chain holds: (prov:qualifiedEnd o prov:atTime) rdfs:subPropertyOf prov:endedAtTime.
The time at which an activity ended. See also prov:startedAtTime.
It is the intent that the property chain holds: (prov:qualifiedStart o prov:atTime) rdfs:subPropertyOf prov:startedAtTime.
The time at which an activity started. See also prov:endedAtTime.
If this Activity prov:wasAssociatedWith Agent :ag, then it can qualify the Association using prov:qualifiedAssociation [ a prov:Association; prov:agent :ag; :foo :bar ].
An prov:Agent that had some (unspecified) responsibility for the occurrence of this prov:Activity.
If this Entity prov:wasDerivedFrom Entity :e, then it can qualify how it was derived using prov:qualifiedDerivation [ a prov:Derivation; prov:entity :e; :foo :bar ].
The prov:entity property references an prov:Entity which influenced a resource. This property applies to an prov:EntityInfluence, which is given by a subproperty of prov:qualifiedInfluence from the influenced prov:Entity, prov:Activity or prov:Agent.
This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page). If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome.
W3C PROVenance Interchange Ontology (PROV-O)
Two alternate entities present aspects of the same thing. These aspects may be the same or different, and the alternate entities may or may not overlap in time.
The sub-properties of prov:wasInfluencedBy can be elaborated in more detail using the Qualification Pattern. For example, the binary relation :baking prov:used :spoon can be qualified by asserting :baking prov:qualifiedUsage [ a prov:Usage; prov:entity :spoon; prov:atLocation :kitchen ] . Subproperties of prov:wasInfluencedBy may also be asserted directly without being qualified. prov:wasInfluencedBy should not be used without also using one of its subproperties.
Because prov:wasInfluencedBy is a broad relation, its more specific subproperties (e.g. prov:wasInformedBy, prov:actedOnBehalfOf, prov:wasEndedBy, etc.) should be used when applicable.
A revision is a derivation that revises an entity into a revised version.
Indicates a provenance-URI for a resource; the resource identified by this property presents a provenance record about its subject or anchor resource.
An activity is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities.
A collection is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be member of the collections.
Activity that identifies the acceptance of a resource (e.g., an article in a conference)
Activity that identifies the Copyrighting activity associated to a resource.
Activity that identifies the creation of a resource
Activity that identifies any contribution of an agent to a resource.
Role with the function of creating a resource. The Agent assigned to this role is associated with a Create Activity
Role with the function of having responsibility for making contributions to a resource. The Agent assigned to this role is associated with a Modify or Create Activities
Type for a generic provenance query service. Mainly for use in RDF provenance query service descriptions, to facilitate discovery in linked data environments.
Classify prov-o terms into three categories, including 'starting-point', 'qualifed', and 'extended'. This classification is used by the prov-o html document to gently introduce prov-o terms to its users.
An empty dictionary (i.e. has no members).
A dictionary is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be member of the dictionary.
A given dictionary forms a given structure for its members. A different structure (obtained either by insertion or removal of members) constitutes a different dictionary.
This concept allows for the provenance of the dictionary, but also of its constituents to be expressed. Such a notion of dictionary corresponds to a wide variety of concrete data structures, such as a maps or associative arrays.
An empty collection is a collection without members.
Classify prov-o terms into six components according to prov-dm, including 'agents-responsibility', 'alternate', 'annotations', 'collections', 'derivations', and 'entities-activities'. This classification is used so that readers of prov-o specification can find its correspondence with the prov-dm specification.
A reference to the principal section of the PROV-CONSTRAINTS document that describes this concept.
A reference to the principal section of the PROV-DM document that describes this concept.
Activity that identifies the modification of a resource.
An organization is a social or legal institution such as a company, society, etc.
Activity that identifies the publication of a resource
Role with the function of publishing a resource. The Agent assigned to this role is associated with a Publish Activity
A role is the function of an entity or agent with respect to an activity, in the context of a usage, generation, invalidation, association, start, and end.
Activity that identifies the replacement of a resource.
Activity that identifies the rights assignment of a resource.
Role with the function of owning or managing rights over a resource. The Agent assigned to this role is associated with a RightsAssignment Activity
Activity that identifies the issuance (e.g., publication) of a resource.
The prov:activity property references an prov:Activity which influenced a resource. This property applies to an prov:ActivityInfluence, which is given by a subproperty of prov:qualifiedInfluence from the influenced prov:Entity, prov:Activity or prov:Agent.
prov:asInBundle is used to specify which bundle the general entity of a prov:mentionOf property is described. When :x prov:mentionOf :y and :y is described in Bundle :b, the triple :x prov:asInBundle :b is also asserted to cite the Bundle in which :y was described.
An entity is a physical, digital, conceptual, or other kind of thing with some fixed aspects; entities may be real or imaginary.
A bundle is a named set of provenance descriptions, and is itself an Entity, so allowing provenance of provenance to be expressed.
Note that there are kinds of bundles (e.g. handwritten letters, audio recordings, etc.) that are not expressed in PROV-O, but can be still be described by PROV-O.
PROV-O does not define all property inverses. The directionalities defined in PROV-O should be given preference over those not defined. However, if users wish to name the inverse of a PROV-O property, the local name given by prov:inverse should be used.
prov:mentionOf is used to specialize an entity as described in another bundle. It is to be used in conjuction with prov:asInBundle. prov:asInBundle is used to cite the Bundle in which the generalization was mentioned.
relates a generic provenance query service resource (type prov:ServiceDescription) to a specific query service description (e.g. a prov:DirectQueryService or a sd:Service).
A note by the OWL development team about how this term expresses the PROV-DM concept, or how it should be used in context of semantic web or linked data.
When the prov-o term does not have a definition drawn from prov-dm, and the prov-o editor provides one.
End is when an activity is deemed to have ended. An end may refer to an entity, known as trigger, that terminated the activity.
An entity that is a specialization of another shares all aspects of the latter, and additionally presents more specific aspects of the same thing as the latter. In particular, the lifetime of the entity being specialized contains that of any specialization. Examples of aspects include a time period, an abstraction, and a context associated with the entity.
The _optional_ Generation involved in an Entity's Derivation.
An object property to express the accountability of an agent towards another agent. The subordinate agent acted on behalf of the responsible agent in an actual activity.
Describes the key-entity pair that was member of a prov:Dictionary. A dictionary can have multiple members.
A key-entity pair. Part of a prov:Dictionary through prov:hadDictionaryMember. The key is any RDF Literal, the value is a prov:Entity.
This property and its subproperties are used in the same way as the rdf:object property, i.e. to reference the object of an unqualified prov:wasInfluencedBy or prov:influenced triple.
This property is used as part of the qualified influence pattern. Subclasses of prov:Influence use these subproperties to reference the resource (Entity, Agent, or Activity) whose influence is being qualified.
Subproperties of prov:influencer are used to cite the object of an unqualified PROV-O triple whose predicate is a subproperty of prov:wasInfluencedBy (e.g. prov:used, prov:wasGeneratedBy). prov:influencer is used much like rdf:object is used.
Indicates anchor URI for a potentially dynamic resource instance.
Indicates a provenance query service that can access provenance related to its subject or anchor resource.
The naming of prov:atLocation parallels prov:atTime, and is not named prov:hadLocation to avoid conflicting with the convention that prov:had* properties are used on prov:Influence classes.
This property is not functional because the many values could be at a variety of granularies (In this building, in this room, in that chair).
The position that this OWL term should be listed within documentation. The scope of the documentation (e.g., among all terms, among terms within a prov:category, among properties applying to a particular class, etc.) is unspecified.
Relates a resource to a provenance pingback service that may receive additional provenance links about the resource.
Relates a provenance service to a URI template string for constructing provenance-URIs.
If this Activity prov:wasInformedBy Activity :a, then it can qualify how it was influenced using prov:qualifiedCommunication [ a prov:Communication; prov:activity :a; :foo :bar ].
If this Agent prov:actedOnBehalfOf Agent :ag, then it can qualify how with prov:qualifiedResponsibility [ a prov:Responsibility; prov:agent :ag; :foo :bar ].
If this Activity prov:wasEndedBy Entity :e1, then it can qualify how it was ended using prov:qualifiedEnd [ a prov:End; prov:entity :e1; :foo :bar ].
This annotation property links a subproperty of prov:wasInfluencedBy with the subclass of prov:Influence and the qualifying property that are used to qualify it. Example annotation: prov:wasGeneratedBy prov:qualifiedForm prov:qualifiedGeneration, prov:Generation . Then this unqualified assertion: :entity1 prov:wasGeneratedBy :activity1 . can be qualified by adding: :entity1 prov:qualifiedGeneration :entity1Gen . :entity1Gen a prov:Generation, prov:Influence; prov:activity :activity1; :customValue 1337 . Note how the value of the unqualified influence (prov:wasGeneratedBy :activity1) is mirrored as the value of the prov:activity (or prov:entity, or prov:agent) property on the influence class.
If this Activity prov:generated Entity :e, then it can qualify how it performed the Generation using prov:qualifiedGeneration [ a prov:Generation; prov:entity :e; :foo :bar ].
Because prov:qualifiedInfluence is a broad relation, the more specific relations (qualifiedCommunication, qualifiedDelegation, qualifiedEnd, etc.) should be used when applicable.
The dictionary was derived from the other by insertion. prov:qualifiedInsertion shows details of the insertion, in particular the inserted key-entity pairs.
Insertion is a derivation that transforms a dictionary into another, by insertion of one or more key-entity pairs.
If this Entity prov:wasInvalidatedBy Activity :a, then it can qualify how it was invalidated using prov:qualifiedInvalidation [ a prov:Invalidation; prov:activity :a; :foo :bar ].
If this Entity prov:wasQuotedFrom Entity :e, then it can qualify how using prov:qualifiedQuotation [ a prov:Quotation; prov:entity :e; :foo :bar ].
The dictionary was derived from the other by removal. prov:qualifiedRemoval shows details of the removal, in particular the removed keys.
Removal is a derivation that transforms a dictionary into another, by removing one or more key-entity pairs.
If this Entity prov:hadPrimarySource Entity :e, then it can qualify how using prov:qualifiedPrimarySource [ a prov:PrimarySource; prov:entity :e; :foo :bar ].
If this Activity prov:wasStartedBy Entity :e1, then it can qualify how it was started using prov:qualifiedStart [ a prov:Start; prov:entity :e1; :foo :bar ].
If this Activity prov:used Entity :e, then it can qualify how it used it using prov:qualifiedUsage [ a prov:Usage; prov:entity :e; :foo :bar ].
An entity is derived from an original entity by copying, or 'quoting', some or all of it.
If this Entity prov:wasRevisionOf Entity :e, then it can qualify how it was revised using prov:qualifiedRevision [ a prov:Revision; prov:entity :e; :foo :bar ].
Start is when an activity is deemed to have started. A start may refer to an entity, known as trigger, that initiated the activity.
Classes and properties used to qualify relationships are annotated with prov:unqualifiedForm to indicate the property used to assert an unqualified provenance relation.
The editor's definition comes from http://www.w3.org/TR/rdf-primer/#rdfvalue
This property serves the same purpose as rdf:value, but has been reintroduced to avoid some of the definitional ambiguity in the RDF specification (specifically, 'may be used in describing structured values').
Provides a value that is a direct representation of an entity.
The multiple rdfs:domain assertions are intended. One is simpler and works for OWL-RL, the union is more specific but is not recognized by OWL-RL.
The _optional_ Activity of an Influence, which used, generated, invalidated, or was the responsibility of some Entity. This property is _not_ used by ActivityInfluence (use prov:activity instead).
A prov:Entity that was used by this prov:Activity. For example, :baking prov:used :spoon, :egg, :oven .
The _optional_ Usage involved in an Entity's Derivation.
The dictionary was derived from the other by removal. prov:qualifiedRemoval shows details of the removal, in particular the removed key-entity pairs.
An instance of prov:End provides additional descriptions about the binary prov:wasEndedBy relation from some ended prov:Activity to an prov:Entity that ended it. For example, :ball_game prov:wasEndedBy :buzzer; prov:qualifiedEnd [ a prov:End; prov:entity :buzzer; :foo :bar; prov:atTime '2012-03-09T08:05:08-05:00'^^xsd:dateTime ].
End is when an activity is deemed to have been ended by an entity, known as trigger. The activity no longer exists after its end. Any usage, generation, or invalidation involving an activity precedes the activity's end. An end may refer to a trigger entity that terminated the activity, or to an activity, known as ender that generated the trigger.
The time at which an InstantaneousEvent occurred, in the form of xsd:dateTime.
prov:generated is one of few inverse property defined, to allow Activity-oriented assertions in addition to Entity-oriented assertions.
An instance of prov:Generation provides additional descriptions about the binary prov:wasGeneratedBy relation from a generated prov:Entity to the prov:Activity that generated it. For example, :cake prov:wasGeneratedBy :baking; prov:qualifiedGeneration [ a prov:Generation; prov:activity :baking; :foo :bar ].
Generation is the completion of production of a new entity by an activity. This entity did not exist before generation and becomes available for usage after this generation.
It is the intent that the property chain holds: (prov:qualifiedGeneration o prov:atTime) rdfs:subPropertyOf prov:generatedAtTime.
The time at which an entity was completely created and is available for use.
An instance of prov:Derivation provides additional descriptions about the binary prov:wasDerivedFrom relation from some derived prov:Entity to another prov:Entity from which it was derived. For example, :chewed_bubble_gum prov:wasDerivedFrom :unwrapped_bubble_gum; prov:qualifiedDerivation [ a prov:Derivation; prov:entity :unwrapped_bubble_gum; :foo :bar ].
The more specific forms of prov:Derivation (i.e., prov:Revision, prov:Quotation, prov:PrimarySource) should be asserted if they apply.
A plan is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals.
There exist no prescriptive requirement on the nature of plans, their representation, the actions or steps they consist of, or their intended goals. Since plans may evolve over time, it may become necessary to track their provenance, so plans themselves are entities. Representing the plan explicitly in the provenance can be useful for various tasks: for example, to validate the execution as represented in the provenance record, to manage expectation failures, or to provide explanations.
An instance of prov:Usage provides additional descriptions about the binary prov:used relation from some prov:Activity to an prov:Entity that it used. For example, :keynote prov:used :podium; prov:qualifiedUsage [ a prov:Usage; prov:entity :podium; :foo :bar ].
Usage is the beginning of utilizing an entity by an activity. Before usage, the activity had not begun to utilize this entity and could not have been affected by the entity.
An object property to refer to the prov:KeyEntityPair inserted into a prov:Dictionary.
prov:invalidated is one of few inverse property defined, to allow Activity-oriented assertions in addition to Entity-oriented assertions.
An instance of prov:Invalidation provides additional descriptions about the binary prov:wasInvalidatedBy relation from an invalidated prov:Entity to the prov:Activity that invalidated it. For example, :uncracked_egg prov:wasInvalidatedBy :baking; prov:qualifiedInvalidation [ a prov:Invalidation; prov:activity :baking; :foo :bar ].
Invalidation is the start of the destruction, cessation, or expiry of an existing entity by an activity. The entity is no longer available for use (or further invalidation) after invalidation. Any generation or usage of an entity precedes its invalidation.
It is the intent that the property chain holds: (prov:qualifiedInvalidation o prov:atTime) rdfs:subPropertyOf prov:invalidatedAtTime.
The time at which an entity was invalidated (i.e., no longer usable).
The key of a KeyEntityPair, which is an element of a prov:Dictionary.
An instance of prov:Start provides additional descriptions about the binary prov:wasStartedBy relation from some started prov:Activity to an prov:Entity that started it. For example, :foot_race prov:wasStartedBy :bang; prov:qualifiedStart [ a prov:Start; prov:entity :bang; :foo :bar; prov:atTime '2012-03-09T08:05:08-05:00'^^xsd:dateTime ] .
Start is when an activity is deemed to have been started by an entity, known as trigger. The activity did not exist before its start. Any usage, generation, or invalidation involving an activity follows the activity's start. A start may refer to a trigger entity that set off the activity, or to an activity, known as starter, that generated the trigger.
A location can be an identifiable geographic place (ISO 19112), but it can also be a non-geographic place such as a directory, row, or column. As such, there are numerous ways in which location can be expressed, such as by a coordinate, address, landmark, and so forth.
An instantaneous event, or event for short, happens in the world and marks a change in the world, in its activities and in its entities. The term 'event' is commonly used in process algebra with a similar meaning. Events represent communications or interactions; they are assumed to be atomic and instantaneous.
The PROV data model is implicitly based on a notion of instantaneous events (or just events), that mark transitions in the world. Events include generation, usage, or invalidation of entities, as well as starting or ending of activities. This notion of event is not first-class in the data model, but it is useful for explaining its other concepts and its semantics.
The property used by a prov:Insertion and prov:Removal to cite the prov:Dictionary that was prov:derivedByInsertionFrom or prov:derivedByRemovalFrom another dictionary.
An instance of prov:Delegation provides additional descriptions about the binary prov:actedOnBehalfOf relation from a performing prov:Agent to some prov:Agent for whom it was performed. For example, :mixing prov:wasAssociatedWith :toddler . :toddler prov:actedOnBehalfOf :mother; prov:qualifiedDelegation [ a prov:Delegation; prov:entity :mother; :foo :bar ].
Delegation is the assignment of authority and responsibility to an agent (by itself or by another agent) to carry out a specific activity as a delegate or representative, while the agent it acts on behalf of retains some responsibility for the outcome of the delegated work. For example, a student acted on behalf of his supervisor, who acted on behalf of the department chair, who acted on behalf of the university; all those agents are responsible in some way for the activity that took place but we do not say explicitly who bears responsibility and to what degree.
An instance of prov:Influence provides additional descriptions about the binary prov:wasInfluencedBy relation from some influenced Activity, Entity, or Agent to the influencing Activity, Entity, or Agent. For example, :stomach_ache prov:wasInfluencedBy :spoon; prov:qualifiedInfluence [ a prov:Influence; prov:entity :spoon; :foo :bar ] . Because prov:Influence is a broad relation, the more specific relations (Communication, Delegation, End, etc.) should be used when applicable.
Because prov:Influence is a broad relation, its most specific subclasses (e.g. prov:Communication, prov:Delegation, prov:End, prov:Revision, etc.) should be used when applicable.
Influence is the capacity of an entity, activity, or agent to have an effect on the character, development, or behavior of another by means of usage, start, end, generation, invalidation, communication, derivation, attribution, association, or delegation.
Communication is the exchange of an entity by two activities, one activity using the entity generated by the other.
An instance of prov:Communication provides additional descriptions about the binary prov:wasInformedBy relation from an informed prov:Activity to the prov:Activity that informed it. For example, :you_jumping_off_bridge prov:wasInformedBy :everyone_else_jumping_off_bridge; prov:qualifiedCommunication [ a prov:Communication; prov:activity :everyone_else_jumping_off_bridge; :foo :bar ].
AgentInfluence is the capacity of an agent to have an effect on the character, development, or behavior of another by means of attribution, association, delegation, or other.
AgentInfluence provides additional descriptions of an Agent's binary influence upon any other kind of resource. Instances of AgentInfluence use the prov:agent property to cite the influencing Agent.
It is not recommended that the type AgentInfluence be asserted without also asserting one of its more specific subclasses.
A primary source for a topic refers to something produced by some agent with direct experience and knowledge about the topic, at the time of the topic's study, without benefit from hindsight. Because of the directness of primary sources, they 'speak for themselves' in ways that cannot be captured through the filter of secondary sources. As such, it is important for secondary sources to reference those primary sources from which they were derived, so that their reliability can be investigated. A primary source relation is a particular case of derivation of secondary materials from their primary sources. It is recognized that the determination of primary sources can be up to interpretation, and should be done according to conventions accepted within the application's domain.
An instance of prov:PrimarySource provides additional descriptions about the binary prov:hadPrimarySource relation from some secondary prov:Entity to an earlier, primary prov:Entity. For example, :blog prov:hadPrimarySource :newsArticle; prov:qualifiedPrimarySource [ a prov:PrimarySource; prov:entity :newsArticle; :foo :bar ] .
A quotation is the repeat of (some or all of) an entity, such as text or image, by someone who may or may not be its original author. Quotation is a particular case of derivation.
An instance of prov:Quotation provides additional descriptions about the binary prov:wasQuotedFrom relation from some taken prov:Entity from an earlier, larger prov:Entity. For example, :here_is_looking_at_you_kid prov:wasQuotedFrom :casablanca_script; prov:qualifiedQuotation [ a prov:Quotation; prov:entity :casablanca_script; :foo :bar ].
A revision is a derivation for which the resulting entity is a revised version of some original. The implication here is that the resulting entity contains substantial content from the original. Revision is a particular case of derivation.
An instance of prov:Revision provides additional descriptions about the binary prov:wasRevisionOf relation from some newer prov:Entity to an earlier prov:Entity. For example, :draft_2 prov:wasRevisionOf :draft_1; prov:qualifiedRevision [ a prov:Revision; prov:entity :draft_1; :foo :bar ].
ActivitiyInfluence is the capacity of an activity to have an effect on the character, development, or behavior of another by means of generation, invalidation, communication, or other.
ActivityInfluence provides additional descriptions of an Activity's binary influence upon any other kind of resource. Instances of ActivityInfluence use the prov:activity property to cite the influencing Activity.
It is not recommended that the type ActivityInfluence be asserted without also asserting one of its more specific subclasses.
EntityInfluence provides additional descriptions of an Entity's binary influence upon any other kind of resource. Instances of EntityInfluence use the prov:entity property to cite the influencing Entity.
It is not recommended that the type EntityInfluence be asserted without also asserting one of its more specific subclasses.
EntityInfluence is the capacity of an entity to have an effect on the character, development, or behavior of another by means of usage, start, end, derivation, or other.
Quotation is a particular case of derivation (see http://www.w3.org/TR/prov-dm/#term-quotation) in which an entity is derived from an original entity by copying, or "quoting", some or all of it.
influencer: an identifier (o1) for an ancestor entity, activity, or agent that the former depends on;
hadPrimarySource property is a particular case of wasDerivedFrom (see http://www.w3.org/TR/prov-dm/#term-original-source) that aims to give credit to the source that originated some information.
Revision is a derivation (see http://www.w3.org/TR/prov-dm/#term-Revision). Moreover, according to http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#term-Revision 23 April 2012 'wasRevisionOf is a strict sub-relation of wasDerivedFrom since two entities e2 and e1 may satisfy wasDerivedFrom(e2,e1) without being a variant of each other.'
influencee: an identifier (o2) for an entity, activity, or agent;
Derivation is a particular case of trace (see http://www.w3.org/TR/prov-dm/#term-trace), since it links an entity to another entity that contributed to its existence.
Attribution is a particular case of trace (see http://www.w3.org/TR/prov-dm/#concept-trace), in the sense that it links an entity to the agent that ascribed it.
IF wasAttributedTo(e2,ag1,aAttr) holds, THEN wasInfluencedBy(e2,ag1) also holds.
The URIs for resources in this document were assigned in accordance with the OGC Naming policies, overseen by the OGC Naming Authority. They are not otherwise managed as part of a delegated governance via a specific artefact, such as CodeLists from a normative schema.
OGC nils
refactored from original omnibus concept scheme into a separate scheme for reuse
Copyright © 2012 Open Geospatial Consortium, Inc. All Rights Reserved.
Above Detection Range
Value was above the detection range of the instrument used to estimate it.
above detection range
Below Detection Range
Value was below the detection range of the instrument used to estimate it.
below detection range
Inapplicable
There is no value
inapplicable
Missing
The correct value is not readily available to the sender of this data. Furthermore, a correct value may not exist
missing
Template
The value will be available later
template
Unknown
The correct value is not known to, or not computable by, the sender of this data. However, the correct value probably exists
unknown
Withheld
The value is not divulged.
withheld
This ontology ("wfdesc") describes an abstract workflow description structure, which on the top level is defined as a wfdesc:Workflow. A wfdesc:Workflow contains several wfdesc:Process instances, associated using the wfdesc:hasSubProcess property. Each of these (and the workflow itself) wfdesc:hasInput and wfdesc:hasOutput some wfdesc:Parameter (wfdesc:Input or wfdesc:Output). An wfdesc:Artifact is associated with a wfdesc:Parameter using wfdesc:hasArtifact. The wfdesc:Workflow also wfdesc:hasDataLink several wfdesc:DataLink instances, which forms the connection between parameters. Thus this ontology allows the description a direct acyclic graph, or a dataflow. This ontology is meant as an upper ontology for more specific workflow definitions, and as a way to express abstract workflows. The wfprov ontology shows how to link these descriptions to a provenance trace of a workflow execution.
A wfdesc:WorkflowInstance is a specialisation of a wfdesc:Workflow description which defines all data/parameters/settings that are required to form a wfprov:WorkflowRun.
A wfdesc:Workflow is a directed graph in which the nodes are wfdesc:Process instances and the edges (wfdesc:DataLink instances) represent data dependencies between the constituent wfdesc:Process descriptions. A wfdesc:Workflow defines associated wfdesc:Process using wfdesc:hasSubProcess. A specialisation of this property is wfdesc:hasSubWorkflow, signifying that the process is a wfdesc:Workflow itself, which is further described in a similar fashion. As a subclass of wfdesc:Process a wfdesc:Workflow can also define wfdesc:hasInput/wfdesc:hasOutput parameters - these would be inputs taken at workflow execution time, and final outputs of the workflow. (Note: Not all dataflow systems have this concept of workflow parameters) wfdesc:Parameter descriptions are linked using wfdesc:DataLink descriptions associated with the wfdesc:Workflow using wfdesc:hasDataLink. A wfdesc:Parameter defined with wfdesc:hasInput on a wfdesc:Workflow is considered an wfdesc:Input "outside" the workflow (ie. if it is a subworkflow), but an wfdesc:Output "inside" the workflow (where it can be connected to a wfdesc:Input of a wfdesc:Process). Thus such parameters can be linked "through" the workflow without having a "mirrored" port inside. Example: ## @prefix wfdesc: <http://purl.org/wf4ever/wfdesc#> . :outerWorkflow a wfdesc:Workflow ; wfdesc:hasSubWorkflow :innerWorkflow ; wfdesc:hasSubProcess :procA, :procC . :procA a wfdesc:Process ; wfdesc:hasOutput :param1 . :procC a wfdesc:Process ; wfdesc:hasInput :param2 ; wfdesc:hasOutput :param3 . :innerWorkflow a wfdesc:Workflow ; wfdesc:hasInput :param4 ; wfdesc:hasOutput :param5 ; wfdesc:hasProcess :procB . :procB a wfdesc:Process ; wfdesc:hasInput :param6 ; wfdesc:hasOutput :param7 . :innerWorkflow wfdesc:hasDataLink [ wfdesc:hasSource :param4; wfdesc:hasSink :param6 ], [ wfdesc:hasSource :param7; wfdesc:hasSink :param5 ] . :outerWorkflow wfdesc:hasDataLink [ wfdesc:hasSource :param1; wfdesc:hasSink :param4 ], [ wfdesc:hasSource :param5; wfdesc:hasSink :param2 ] . ## In this example :param1 is the output of :procA. :param1 is the source in a datalink that goes to the input :param4 of the :innerWorkflow. :param4 is however also the source of an inner datalink, going to input :param6 of the nested :procB. From this :param4 is both an wfdesc:Input and wfdesc:Output (which is why these two classes are not disjoint)
This property associates a wfdesc:Parameter with an wfdesc:Artifact which can describe the artifact which would be used/generated on execution of the workflow.
This class represent a parameter of a wfdesc:Process. A wfdesc:Parameter must be a wfdesc:Input, a wfdesc:Output, or both. A parameter is both an wfdesc:Input and wfdesc:Output when it is used on both sides of a subworkflow - see wfdesc:Workflow and wfdesc:DataLink for details.
wfdesc:Artifact is used to provide information about a class of artifacts. For example, it can be used to specify the datatype of a dataset or the structure of a document. An wfdesc:Artifact is associated with a wfdesc:Parameter using wfdesc:hasArtifact. The distinction between a parameter and artifact is that the parameter can be customized to describe the particular role the artifact plays with regards to the process (and can be linked using wfdesc:DataLink) - while the wfdesc:Artifact can describe the syntactic and semantic datatype.
This property is used to specify the wfdesc:DataLink instances of a given wfdesc:Workflow.
wfdesc:DataLink is used to represent data dependencies between wfdesc:Process descriptions. It means that the artifact generated at an wfdesc:Output (identified using wfdesc:hasSource) will be used by a wfdescInput (identified using wfdesc:hasSink). The wfdesc:Processes that owns the wfdesc:Parameter instances which are the source and sink of a wfdesc:DataLink must be wfdesc:hasSubProcess of a the same wfdesc:Workflow which wfdesc:hasDataLink the data link, or be be parameters of that same workflow. Thus links can only be made within a wfdesc:Workflow - although ports owned by the workflow itself appear both inside and outside the workflow (in opposite roles).
This object property is used to specify the wfdesc:Input parameter of a given wfdesc:Process.
A wfdesc:Process is used to describe a class of actions that when enacted give rise to processes. A process can have 0 or more wfdesc:Parameter instances associated using wfdesc:hasInput and wfdesc:hasOutput, signifying what kind of parameters the process will require and return. It is out of scope for wfdesc to classify or specify the nature of the process, this should be done by subclassing and additional subproperties, for instance ex:perlScript or ex:restServiceURI
wfdesc:Input represents an input parameter to a wfdesc:Process. This can be compared to a function parameter, command line argument, files read, or parameter set by a user interface. It is out of scope of wfdesc to define the nature or classification of the parameter, such as giving it a name, position or data type. This can be done with subclasses and/or subproperties.
This object property is used to specify the wfdesc:Output parameter of a given wfdesc:Process.
wfdesc:Output represents an output parameter from a wfdesc:Process. This can be compared to functional return values, stdout/stdin, files written, or results shown in a user interface. It is out of scope of wfdesc to define the nature or classification of the parameter, such as giving it a name, position or data type. This can be done with subclasses and/or subproperties.
This property is used to specify the wfdesc:Input parameter that acts as a sink from a given wfdesc:DataLink, consuming data from the link.
This property is used to specify the wfdesc:Output parameter that acts as a source to a given wfdesc:DataLink, providing data into the link.
This object property is used to associate a wfdesc:Workflow description to another wfdesc:Workflow, specifying that the first workflow has the given sub-workflow as a contained process. This is a specialisation of wfdesc:hasSubProcess.
This object property is used to specify that the given workflow contains the given process as part of its definition. Although not a requirement, such sub processes should have wfdesc:DataLink within the containing workflow connecting their parameters with parameters of the containing workflow, or with parameters other contained wfdesc:Process instances. A specialialisation of sub process is wfdesc:hasSubWorkflow where the sub process is a nested wfdesc:Workflow.
Useful when rdfs:subClassOf entailment is enabled and the proximate class type is required to be recorded.
A link to the individual which this attribute and its value is applied to. Inverse property of tern:hasAttribute.
A link to the RDF payload's metadata which this resource was a part of.
The direct link to the value either as an IRI or an RDF literal. The simple value is always equivalent to the value captured in rdf:value of the tern:Value instance.
The identifier of the attribute concept. Attribute concepts are usually described with SKOS. TERN manages a list of attributes at http://linked.data.gov.au/def/tern-cv/dd085299-ae86-4371-ae15-61dfa432f924.
A link to a tern:Value instance which encapsulates the value of this Attribute.
A property-value pair. Same modelling pattern as (https://schema.org/PropertyValue).
Class to encapsulate a true-or-false value
Examples of distributions include a CSV file, a file, a JSON document, or a data-cube, files made accessible according to different profiles, such as XML or JSON schemas or [ShEx] or [SHACL] expressions. In some cases all distributions of a dataset will be fully informationally equivalent, in the sense that lossless transformations between the representations are possible. An example would be different serializations of an RDF graph using RDF/XML [RDF-SYNTAX-GRAMMAR], [Turtle], [N3], [JSON-LD]. However, in other cases the distributions might have different levels of fidelity to the underlying data. For example, a graphical representation about the data on a CSV file may not contain the same total information recorded in the CSV file, but they could be considered as two distributions for the same dataset as they are about the same data. As a counter-example, budget data for different years would usually be modelled as different datasets, each with their own distributions, since all distributions of one dataset should broadly contain the same data. Nevertheless, the question of whether different representations can be understood to be distributions of the same dataset, or distributions of different datasets, is application specific. Judgement about how to describe them is the responsibility of the provider, taking into account their understanding of the expectations of users, and practices in the relevant community.
This represents a general availability of a dataset. It implies no information about the actual access method of the data, i.e. whether by direct download, API, or through a Web page. The use of dcat:downloadURL property indicates directly downloadable distributions.
For example, a temperature Sensor deployed on a wall, or a whole network of Sensors deployed for an Observation campaign.
Describes the Deployment of one or more Systems for a particular purpose. Deployment may be done on a Platform.
The model as defined by the manufacturer.
The measurement or extent of something from side to side.
The dimension of a 2D square or rectangular feature. Example, the dimension of a rectangular plot [Site](#EcologicalSite). This class should perhaps have specialised classes to express not just square or rectangular features but also others such as circular features.
When measuring the height of a tree, the height is the observed ObservableProperty, 20m may be the Result of the Observation, and the tree is the FeatureOfInterest. A window is a FeatureOfInterest for an automatic window control Actuator.
The thing whose property is being estimated or calculated in the course of an Observation to arrive at a Result or whose property is being manipulated by an Actuator, or which is being sampled or transformed in an act of Sampling.
30 Nov 2019 is the date decommisioned of the [Collie flux station](http://ozflux.org.au/monitoringsites/collie/index.html)
Use ISO 8601 international standard for representing dates and times. Missing end date may be set to the end of the month.
The date when, e.g., a [Site](#EcologicalSite) is decommissioned or stopped operating.
The unique identifier for flux towers registered with FLUXNET.
Ausplots Rangelands Site 59858 (Site Name: WAACOO0011)
Use (http://purl.org/dc/terms/hasPart) and (http://purl.org/dc/terms/isPartOf) to model [Site](#EcologicalSite) and [Subsite](#EcologicalSite) relationships. E.g. In TERN, there are SuperSites that contain multiple core 1 ha plots.
Location where observations may be made. This is a subclass of [Sample](#Sample) because a site should be designed to be representative of an environmental system (which may be an ecosystem or bioregion) or zone (which may be a zone such as a parcel or tract).
The geometric center of 1-ha vegetation plot expressed as (https://w3id.org/tern/ontologies/loc/Point).
The centroid point of an object-of-interest.
1 August 2017 is the date commisioned of the [Collie flux station](http://ozflux.org.au/monitoringsites/collie/index.html)
Use ISO 8601 international standard for representing dates and times. Missing start date may be set to the first of the month.
The date when, e.g., a [Site](#EcologicalSite) is ready to commence its operations, after it is successfully installed and tested.
Across the globe, towers stand among the landscape, with sensors monitoring these eddies for carbon dioxide, water vapor and other gasses. These so-called flux towers collect data on carbon dioxide exchange rates between the earth and atmosphere.
A **wedge prism** or **relascope** can be used to estimate the Basal Area per hectare. The number of counted trees and the Basal Area Factor are inputs to estimate the Basal Area.
*Input* - Any information that is provided to a [Procedure](#Procedure) for its use.
A whole organism preserved in a collection. A part of an organism isolated for some purpose. A soil sample. A marine microbial sample.
A physical result of a sampling (or subsampling) event. In biological collections, the material sample is typically collected, and either preserved or destructively processed.
A property that links a concept to a collection containing its categorical values.
A property that links a concept to a parameter.
Describe the instructions of the procedure/method.
We recommend representing the method information following [ISO 9001 Processes, Procedures and Work Instructions](https://3yn1j14c4twk1bmdg82226en-wpengine.netdna-ssl.com/wp-content/uploads/2016/08/iso-9001-procedure.pdf)
Borehole logging is a field method in which in situ physical measurements (e.g., temperature) are made down the length of a borehole by lowering measurement instruments down the borehole via cable. (Credit: PaST Thesaurus)
A Method describes in detailed steps how a workflow, protocol, plan or algorithm is carried out to make an [Observation](#Observation) or a [Sample](#Sample). It explains the steps to be carried out to arrive at reproducible [Result](#Result).
A [FeatureOfInterest's](http://w3.org/ns/sosa/FeatureOfInterest) property or characteristic which an [Observation](#Observation) is measuring using some [Procedure](#Procedure).
Sampling depth, bulk density, pH are examples of properties of a soil sample, and the soil sample is the feature-of-interest, representative of the area from which it is collected.
An observable quality (property, characteristic) of a [FeatureOfInterest](http://w3.org/ns/sosa/FeatureOfInterest). A feature-of-interest refers to a feature whose properties are measured or observed.
The activity of measuring properties such as wind speed and direction by an anemometer sensor. The results of the observation are the measurement values of the properties estimated by the sensor.
Act of carrying out an (Observation) [Procedure](#Procedure) to estimate or calculate a value of a property of a [FeatureOfInterest](http://w3.org/ns/sosa/FeatureOfInterest). Links to a [Sensor](http://w3.org/ns/sosa/Sensor) to describe what made the [Observation](#Observation) and how; links to an [ObservableProperty](#ObservableProperty) to describe what the result is an estimate of, and to a [FeatureOfInterest](http://w3.org/ns/sosa/FeatureOfInterest) to detail what that property was associated with.
Relation linking an Observation to the property that was observed. The ObservableProperty should be a property of the FeatureOfInterest (linked by hasFeatureOfInterest) of this Observation.
link to the ultimate feature of interest of an observation or act of sampling. This is useful when the proximate feature of interest is a sample of the ultimate feature of interest, directly or trasntitively.
The result time is the instant of time when the Observation, Actuation or Sampling activity was completed.
A relation between an Observation and the entity whose quality was observed, or between an Actuation and the entity whose property was modified, or between an act of Sampling and the entity that was sampled.
The time that the Result of an Observation, Actuation, or Sampling applies to the FeatureOfInterest. Not necessarily the same as the resultTime. May be an interval or an instant, or some other compound temporal entity.
A relation to link to a re-usable Procedure used in making an Observation, an Actuation, or a Sample, typically through a Sensor, Actuator or Sampler.
Relation between an Observation and the Sensor which made the Observations.
Link to a member of a collection of observations that share the same value for one or more of the characteristic properties.
Collection of one or more observations, whose members share a common value for one or more property
Ocean buoy is an example of platform that is equipped with an array of sensors such as GPS, current meters, atmospheric sensors and water quality monitors. Sensors measuring weather variables are attached to a weather station (a platform)
An entity that hosts other entities, particularly [Sensors](#Sensor), [Samplers](#Sampler), and other [Platforms](#Platform).
A property that links a concept to a method.
The procedure for collecting photopoints are specified in the [AusPlots Rangelands Survey Protocols Manual](http://dx.doi.org/10.13140/2.1.4287.3607). The DEC Nature Conservation Service Biodiversity have defined (https://www.dpaw.wa.gov.au/images/documents/plants-animals/monitoring/sop/sop_establishingvegetationquadrats_20090818_v1.0.pdf) for establishing quadrats for vegetation sampling.
[Input](#Input) can be used to capture any input values for a procedure, such as the input value of the basal wedge to estimate the basal area per hectare.
A workflow, protocol, plan, algorithm, or computational method specifying how to make an [Observation](#Observation), create a [Sample](#Sample), or make a change to the state of the world (via an [Actuator](http://w3.org/ns/sosa/Actuator). A [Procedure](#Procedure) is re-usable, and might be involved in many [Observations](#Observation), [Samplings](#Sampling), or [Actuations](http://w3.org/ns/sosa/Actuation). it explains the steps to be carried out to arrive at reproducible [Results](#Result).
An entity, such as a person, organisation, or service, that is primarily responsible for creating the dataset. The creator should be described as an RDF resource, rather than just providing the name as a literal.
An entity, such as a person, organisation, or service, that is responsible for making contributions to the dataset. The contributor should be described as an RDF resource, rather than just providing the name as a literal.
A related resource from which the dataset is derived. The source should be described as an RDF resource, rather than as a literal.
The controlled vocabularies used in this RDF dataset.
An entity, such as a person, organisation, or service, that is responsible for making the dataset available. The publisher should be described as an RDF resource, rather than just providing the name as a literal.
Date of formal issuance (e.g., publication) of the dataset. The value should be formatted and datatyped as an xsd:date.
The value 20 as the height of a certain tree together with the unit, e.g., Meter.
The result of an [Observation](#Observation), [Actuation](http://w3.org/ns/sosa/Actuation), or act of [Sampling](#Sampling). To store an observation's simple result value one can use the (http://w3.org/ns/sosa/hasSimpleResult) property.
Plant, animal, soil and water are all examples of samples of some feature of interest.
*A feature which is intended to be representative of a [FeatureOfInterest](http://w3.org/ns/sosa/FeatureOfInterest) on which [Observations](#Observation) may be made. Physical samples are sometimes known as physical specimens.
A ball mill, diamond drill, hammer, hypodermic syringe and needle, image Sensor or a soil auger can all act as sampling devices (i.e., be Samplers). However, sometimes the distinction between the Sampler and the Sensor is not evident, as they are packaged as a unit. A Sampler need not be a physical device.
Sampler - A device that is used by, or implements, a (Sampling) [Procedure](#Procedure) to create or transform one or more samples.
Crushing a rock sample in a ball mill to create sub-samples of the rock. Digging a pit through a soil sequence. Dividing a field site into quadrants. Drawing blood from a patient. Drilling an observation well. Establishing a station for environmental monitoring. Registering an image of the landscape. Sieving a powder to separate the subset finer than 100-mesh. Selecting a subset of a population. Splitting a piece of drill-core to create two new samples. Taking a diamond-drill core from a rock outcrop.
Relation linking an act of Sampling to the Sampler (sampling device or entity) that made it.
An activity of [Sampling](#Sampling) carries out a (Sampling) [Procedure](#Procedure) to create or transform one or more [Samples](#Sample).
Device, agent (including humans), or software (simulation) involved in, or implementing, a Procedure. Sensors respond to a stimulus, e.g., a change in the environment, or input data composed from the results of prior Observations, and generate a Result. Sensors can be hosted by Platforms.
A Site Visit is a discrete time-bounded activity at a [Site](#Site), during which [Sampling](#Sampling) or [Observation](#Observation) activities occur.
The genus Truncorotaloides as published by Bronnimann et al. in 1953 in the Journal of Paleontology Vol. 27(6) p. 817-820.
A group of organisms (sensu http://purl.obolibrary.org/obo/OBI_0100026) considered by taxonomists to form a homogeneous unit.
The feature type of a [Feature of Interest](#FeatureofInterest).
A property that links, e.g., a [SiteVisit](#EcologicalSiteVisit) to a [Site](#EcologicalSite).
Link to a procedure used to obtain the location.
Describes the direction of the transect.
Refers to the (https://w3id.org/tern/ontologies/loc/Point) representing the end of a transect.
Refers to the (https://w3id.org/tern/ontologies/loc/Point) representing the start of a transect.
IGSN:ASR000001 (Resulting URI: http://igsn.org/ASR000001) is a globally unique and persistent identifier of a soil sample.
An identifier for the MaterialSample (as opposed to a particular digital record of the material sample). In the absence of a persistent global unique identifier, construct one from a combination of identifiers in the record that will most closely make the materialSampleID globally unique.
Point to a concept representing the attribute.
A property that links, e.g., a [Site](#EcologicalSite) to a [Site Visit](#EcologicalSiteVisit).
Location description of the AusPlots site NTABRT0004 in the Alice Mulga SuperSite: Pine Hill Station. 25km South East of Ti-Tree. 20km East of Stuart Highway. South west corner of the site is 200m north west of proposed supersite flux tower
Value is usually a summary sentence of the site.
Contextual information is collected at each site. This includes measures of slope an aspect, surface strew and lithology, and information on the grazing and fire history of the site (Credit: TERN AusPlots).
The TERN Ontology comprises a set of vocabularies for representing plot-based ecological data. It was developed primarily based on the SOSA (Sensor, Observation, Sample, and Actuator) ontology. The TERN Ontology's classes and properties have been tailored to describe terrestrial ecology survey data including flora, vegetation and soil, following the methodologies outlined in the Australian Soil and Land Survey Field Handbook.
Class to encapsulate a classifier, usually a value from a controlled vocabulary.
Currently used by the platforms index for SHaRED.
CosmOz is the Australian Cosmic-Ray Neutron Soil Moisture Monitoring Network Beginning in October 2010, CSIRO Land and Water installed cosmic-ray probes at a number of locations around Australia to form the inaugural CosmOz network. These sites were established at instrumented research sites operated by CSIRO and University collaborators to test and validate the operation of this new technology. These novel probes use cosmic rays originating from outer space to measure average soil moisture over an area of about 30 hectares to depths in the soil of between 10 to 50 cm. This constitutes a quantum leap over conventional on-ground soil moisture sensing technology that can only measure soil moisture content within small volumes of soil. Each system is comprised of a data logger, neutron detector, satellite telemetry, tipping bucket rain gauge, temperature humidity and pressure sensors and three surface moisture (TDR) probes. The system requires minimal maintenance and is powered by a solar charging system. The entire system is installed on a single mast. Data is logged and transmitted every 60 minutes to the CosmOz database.
This class describes the actual dataset as published by the dataset provider. In cases where a distinction between the actual dataset and its entry in the catalog is necessary (because metadata such as modification date might differ), the catalog record class can be used for the latter.
A collection of data, published or curated by a single agent, and available for access or download in one or more representations.
Earth observation satellites are satellites specifically designed to observe Earth from orbit, similar to spy satellites but intended for non-military uses such as environmental monitoring, meteorology, map making etc. Source: Wikipedia, http://en.wikipedia.org/wiki/Earth_observation_satellite Group: Platform_Details Entry_ID: Earth Observation satellites Group: Platform_Identification Platform_Category: Earth Observation Satellites Short_Name: Earth Observation Satellites End_Group End_Group
A moving mobile platform on land, in water or in space.
An ecological [Site](#EcologicalSite) that usually hosts a [FluxTower](#FluxTower).
Feature which is managed for TERN purposes
Class to encapsulate a quantitative measure expressed as a percent value.
Class to encapsulate a quantitative range expressed as in percent values.
Class to encapsulate a quantitative range.
The area of the Mitchell Grass Rangeland SuperSite Supersite is approximately 47 M (million) ha.
The extent of a [Site](#EcologicalSite) area, e.g., in m2
The cardinal direction of the *thing* represented as a string and expressed by cardinal and intercardinal points.
Vegetation, soil, disturbance, landform, etc.
The concept dry soil colour is defined in two vocabularies, [CORVEG](http://linked.data.gov.au/def/corveg-cv/1842b772-72a4-430f-a264-dcfd6c2c23b4) and [Ausplots](http://linked.data.gov.au/def/ausplots-cv/aa11e5f7-aec2-4e92-95b8-6332911f0c4e). The property global value is used to map the concept from the two vocabularies to the relevant (http://linked.data.gov.au/def/tern-cv/beceaa5a-a296-4385-a55a-3b8c8d5b2369) specified in the main vocabulary, i.e., TERN Vocabularies.
A property that links a concept from a vocabulary to another concept in an authoritative/endorsed vocabulary.
The global vocabulary refers to the main vocabulary, which takes precedence over other similar vocabularies to promote data harmonisation.
The subject has some environmental characteristic. Points to a set of [Observations](#Observation) within an [EnvironmentalCharacteristic](#EnvironmentalCharacteristic).
Link to an [Observation](#Observation) or [Sampling](#Sampling).
A property that links an activity to its parent activity.
A property that links a [PhysicalSpecimen](#PhysicalSpecimen) to the location [Point](https://w3id.org/tern/ontologies/loc/Point) of where it is stored.
The term used to classify the SoilProfile.
Soil horizon classifier as defined in the Australian Soil and Land Survey Field Handbook on page 148.
Value should be from a controlled vocabulary identified by a URI.
A stratum is a distinct, easily seen, layer of foliage and branches of a measurable height.
Use it to describe an instance of sosa:ObservableProperty and its recommended tern:Value type such as tern:QuantitativeMeasure, tern:Boolean, etc.
Relates a Property to a specialisation of tern:Value.
A device or instrument that is used for making measurements or observations.
Link a concept to an upper concept (in the closed system).
An inverse property of (#globalMatch); Links an upper concept to a concept (in the closed system).
Link to a [Sampling](#Sampling) instance.
A property that links, e.g., a [Sampling](#Sampling) to a [SamplingPoint](#SamplingPoint).
The inverse property (#hasSamplingPoint).
A particular method type used to conduct some survey.
Relation between a Sensor, Actuator, Sampler, or Platform, and the Platform that it is mounted on or hosted by.
Relation linking an Observation or Actuation or act of Sampling and a Result or Sample.
For example, in an Observation of the weight of a person, the FeatureOfInterest is the person and the property is its weight.
Relation between an Observation and the Sensor which made the Observation.
The time that the Result of an Observation, Actuation or Sampling applies to the FeatureOfInterest. Not necessarily the same as the resultTime. May be an Interval or an Instant, or some other compound TemporalEntity.
Relation linking a Result to the Observation or Actuation or act of Sampling that created or caused it.
Relation from a Sample to the FeatureOfInterest that it is intended to be representative of.
Relation between a Sensor and an Observation made by the Sensor.
Relation between a Sensor and an ObservableProperty that it is capable of sensing.
The simple value of an Observation or Actuation or act of Sampling.
A relation between a FeatureOfInterest and an Observation about it, an Actuation acting on it, or an act of Sampling that sampled it.
Relation between a Sampler (sampling device or entity) and the Sampling act it performed.
Relation between a FeatureOfInterest and the Sample used to represent it.
This ontology is based on the SSN Ontology by the W3C Semantic Sensor Networks Incubator Group (SSN-XG), together with considerations from the W3C/OGC Spatial Data on the Web Working Group.
Sensor, Observation, Sample, and Actuator (SOSA) Ontology
An observable quality (property, characteristic) of a FeatureOfInterest.
The height of a tree, the depth of a water body, or the temperature of a surface are examples of observable properties, while the value of a classic car is not (directly) observable but asserted.
An act of Sampling carries out a sampling Procedure to create or transform one or more samples.
Establishing a station for environmental monitoring.
Sieving a powder to separate the subset finer than 100-mesh.
Splitting a piece of drill-core to create two new samples.
Taking a diamond-drill core from a rock outcrop.
A device that is used by, or implements, a Sampling Procedure to create or transform one or more samples.
A workflow, protocol, plan, algorithm, or computational method specifying how to make an Observation, create a Sample, or make a change to the state of the world (via an Actuator). A Procedure is re-usable, and might be involved in many Observations, Samplings, or Actuations. It explains the steps to be carried out to arrive at reproducible results.
The measured wind speed differs depending on the height of the sensor above the surface, e.g., due to friction. Consequently, procedures for measuring wind speed define a standard height for anemometers above ground, typically 10m for meteorological measures and 2m in Agrometeorology. This definition of height, sensor placement, and so forth are defined by the Procedure.
Many observations may be created via the same Procedure, the same way as many tables are assembled using the same instructions (as information objects, not their concrete realization).
Accelerometers, gyroscopes, barometers, magnetometers, and so forth are Sensors that are typically mounted on a modern smart phone (which acts as Platform). Other examples of sensors include the human eyes.
A Platform is an entity that hosts other entities, particularly Sensors, Actuators, Samplers, and other Platforms.
A post, buoy, vehicle, ship, aircraft, satellite, cell-phone, human or animal may act as platforms for (technical or biological) sensors or actuators.
Act of carrying out an (Observation) Procedure to estimate or calculate a value of a property of a FeatureOfInterest. Links to a Sensor to describe what made the Observation and how; links to an ObservableProperty to describe what the result is an estimate of, and to a FeatureOfInterest to detail what that property was associated with.
The activity of estimating the intensity of an Earthquake using the Mercalli intensity scale is an Observation as is measuring the moment magnitude, i.e., the energy released by said earthquake.
Feature which is intended to be representative of a FeatureOfInterest on which Observations may be made.
A 'station' is essentially an identifiable locality where a sensor system or Procedure may be deployed and an observation made. In the context of the observation model, it connotes the 'world in the vicinity of the station', so the observed properties relate to the physical medium at the station, and not to any physical artifact such as a mooring, buoy, benchmark, monument, well, etc.
A statistical sample is often designed to be characteristic of an entire population, so that observations can be made regarding the sample that provide a good estimate of the properties of the population.
A transient sample, such as a ships-track or flight-line, might be identified and described, but is unlikely to be revisited exactly.
A Sample is the result from an act of Sampling.
Physical samples are sometimes known as 'specimens'.
Samples are artifacts of an observational strategy, and have no significant function outside of their role in the observation process. The characteristics of the samples themselves are of little interest, except perhaps to the manager of a sampling campaign. A Sample is intended to sample some FatureOfInterest, so there is an expectation of at least one isSampleOf property. However, in some cases the identity, and even the exact type, of the sampled feature may not be known when observations are made using the sampling features.
An Actuation carries out an (Actuation) Procedure to change the state of the world using an Actuator.
The activity of automatically closing a window if the temperature in a room drops below 20 degree Celsius. The activity is the Actuation and the device that closes the window is the Actuator. The Procedure is the rule, plan, or specification that defines the conditions that triggers the Actuation, here a drop in temperature.
Relation between an Actuation and the property of a FeatureOfInterest it is acting upon.
In the activity (Actuation) of automatically closing a window if the temperature in a room drops below 20 degrees Celsius, the property on which the Actuator acts upon is the state of the window as it changes from being open to being closed.
An actuatable quality (property, characteristic) of a FeatureOfInterest.
A window actuator acts by changing the state between a frame and a window. The ability of the window to be opened and closed is its ActuatableProperty.
Relation between an ActuatableProperty of a FeatureOfInterest and an Actuation changing its state.
The Result of an Observation, Actuation, or act of Sampling. To store an observation's simple result value one can use the hasSimpleResult property.
Relation between a Platform and a Sensor, Actuator, Sampler, or Platform, hosted or mounted on it.
A device that is used by, or implements, an (Actuation) Procedure that changes the state of the world.
A window actuator for automatic window control, i.e., opening or closing the window.
Relation between an ObservableProperty and the Sensor able to observe it.
Relation between an Actuator and the Actuation it has made.
Relation linking an Actuation to the Actuator that made that Actuation.
Created for the MER catalogue upgrade project, 2022
The modes by which one vocabulary may derive from another
Vocabulary Derivation Modes
Derivation with subsetting and extension
Subset & Extension
Use this Concept if the reusing vocabulary both extends and subsets the original vocabulary
Derivation with extension
Extension
Use this Concept if the reusing vocabulary extends the original vocabulary but does not subset it
Derivation with subsetting
Subsetting
Use this Concept if the reusing vocabulary only subsets the original but does not extend it
Derivation without alteration
Direct
Added to this vocabulary for multiple projects in 2023
This vocabulary does not derive from another
None
Use this Concept if the vocabulary is known to not reuse any other vocabularies
Derivation mode is not applicable to this vocabulary
Not Applicable
Use this Concept if the vocabulary is known not to reuse any other vocabularies
Derivation with relabelling
Relabelling
Use this Concept if the reusing vocabulary only relabels Concepts in the original vocabulary but does not alter their place in the Concept hierarchy or their definitions
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/bb4407f3-8e47-46d8-9aa3-179b348a74bb>`. `<https://linked.data.gov.au/def/nrm/bb4407f3-8e47-46d8-9aa3-179b348a74bb>` is the IRI for "Off-plot Belt Transect Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/bb4407f3-8e47-46d8-9aa3-179b348a74bb`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/21859f64-04bb-5fa4-ae99-7184e1b99c4b> ; sosa:hasResult ?this . }
TERN's ecologists have determined the feature type is _quadrat_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/4362c8f2-b3cc-4816-b5a2-fb7bb4c0cff5[`quadrat`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/21859f64-04bb-5fa4-ae99-7184e1b99c4b>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/21859f64-04bb-5fa4-ae99-7184e1b99c4b> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/21859f64-04bb-5fa4-ae99-7184e1b99c4b>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/21859f64-04bb-5fa4-ae99-7184e1b99c4b>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3fd81059-bf41-502d-9b4f-c32e81b8d869>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3fd81059-bf41-502d-9b4f-c32e81b8d869> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3fd81059-bf41-502d-9b4f-c32e81b8d869>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3fd81059-bf41-502d-9b4f-c32e81b8d869> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3fd81059-bf41-502d-9b4f-c32e81b8d869>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Precipitation duration types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Precipitation duration types controlled vocabulary.
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/34789810-a3bc-4def-9ddb-d14ff4ba02ea>`. `<https://linked.data.gov.au/def/nrm/34789810-a3bc-4def-9ddb-d14ff4ba02ea>` is the IRI for "Precipitation duration types".
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Precipitation types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Precipitation types controlled vocabulary.
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/36e4cff5-f238-45e3-85ec-bdd0973f09d7>`. `<https://linked.data.gov.au/def/nrm/36e4cff5-f238-45e3-85ec-bdd0973f09d7>` is the IRI for "Precipitation types".
Observations following the Plot Sign Search Protocol are made in the context of a site visit.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/7347c555-311b-49ed-8928-ab57880a6916>`. `<https://linked.data.gov.au/def/nrm/7347c555-311b-49ed-8928-ab57880a6916>` is the IRI for "Plot Sign Search Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/7347c555-311b-49ed-8928-ab57880a6916`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/eba8654b-1241-4510-8ae9-731589eef4a7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/eba8654b-1241-4510-8ae9-731589eef4a7> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/eba8654b-1241-4510-8ae9-731589eef4a7>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/eba8654b-1241-4510-8ae9-731589eef4a7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/eba8654b-1241-4510-8ae9-731589eef4a7> ; sosa:hasResult ?this . }
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/fff59959-79b9-44f5-916d-16733f58cec5>`. `<https://linked.data.gov.au/def/nrm/fff59959-79b9-44f5-916d-16733f58cec5>` is the IRI for "Track Stations Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/fff59959-79b9-44f5-916d-16733f58cec5`.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/d885edf1-fbdb-47f2-9ddf-098e98fb82fe>`. `<https://linked.data.gov.au/def/nrm/d885edf1-fbdb-47f2-9ddf-098e98fb82fe>` is the IRI for "Vehicle Tracks Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/d885edf1-fbdb-47f2-9ddf-098e98fb82fe`.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/4307974a-f0ea-4d84-abee-de2451eac329>`. `<https://linked.data.gov.au/def/nrm/4307974a-f0ea-4d84-abee-de2451eac329>` is the IRI for "Within-plot Belt Transect Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/4307974a-f0ea-4d84-abee-de2451eac329`.
A note about the past state/use/meaning of a concept.
Contributors: Participants in W3C's Semantic Web Deployment Working Group.
An RDF vocabulary for describing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, 'folksonomies', other types of controlled vocabulary, and also concept schemes embedded in glossaries and terminologies.
A resource has no more than one value of skos:prefLabel per language tag, and no more than one value of skos:prefLabel without language tag.
The range of skos:prefLabel is the class of RDF plain literals.
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties.
The preferred lexical label for a resource, in a given language.
The range of skos:altLabel is the class of RDF plain literals.
Acronyms, abbreviations, spelling variants, and irregular plural/singular forms may be included among the alternative labels for a concept. Mis-spelled terms are normally included as hidden labels (see skos:hiddenLabel).
An alternative lexical label for a resource.
A statement or formal explanation of the meaning of a concept.
This property may be used directly, or as a super-property for more specific note types.
Labelled collections can be used where you would like a set of concepts to be displayed under a 'node label' in the hierarchy.
Thesauri, classification schemes, subject heading lists, taxonomies, 'folksonomies', and other types of controlled vocabulary are all examples of concept schemes. Concept schemes are also embedded in glossaries and terminologies.
A concept scheme may be defined to include concepts from different sources.
A set of concepts, optionally including statements about semantic relationships between those concepts.
A note that helps to clarify the meaning and/or the use of a concept.
skos:exactMatch is disjoint with each of the properties skos:broadMatch and skos:relatedMatch.
skos:exactMatch is used to link two concepts, indicating a high degree of confidence that the concepts can be used interchangeably across a wide range of information retrieval applications. skos:exactMatch is a transitive property, and is a sub-property of skos:closeMatch.
A concept may be a member of more than one concept scheme.
Relates a resource (for example a concept) to a concept scheme in which it is included.
Relates, by convention, a concept scheme to a concept which is topmost in the broader/narrower concept hierarchies for that scheme, providing an entry point to these hierarchies.
Relates a collection to one of its members.
Relates a concept to the concept scheme that it is a top level concept of.
Narrower concepts are typically rendered as children in a concept hierarchy (tree).
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.
Relates a concept to a concept that is more specific in meaning.
Broader concepts are typically rendered as parents in a concept hierarchy (tree).
Relates a concept to a concept that is more general in meaning.
By convention, skos:broaderTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.
skos:broaderTransitive is a transitive superproperty of skos:broader.
By convention, skos:notation is used with a typed literal in the object position of the triple.
A notation, also known as classification code, is a string of characters such as "T58.5" or "303.4833" used to uniquely identify a concept within the scope of a given concept scheme.
By convention, skos:narrowerTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.
skos:narrowerTransitive is a transitive superproperty of skos:narrower.
The range of skos:hiddenLabel is the class of RDF plain literals.
A lexical label for a resource that should be hidden when generating visual displays of the resource, but should still be accessible to free text search operations.
A note for an editor, translator or maintainer of the vocabulary.
skos:relatedMatch is used to state an associative mapping link between two conceptual resources in different concept schemes.
A note about a modification to a concept.
skos:closeMatch is used to link two concepts that are sufficiently similar that they can be used interchangeably in some information retrieval applications. In order to avoid the possibility of "compound errors" when combining mappings across more than two concept schemes, skos:closeMatch is not declared to be a transitive property.
For any resource, every item in the list given as the value of the skos:memberList property is also a value of the skos:member property.
Relates an ordered collection to the RDF list containing its members.
Ordered collections can be used where you would like a set of concepts to be displayed in a specific order, and optionally under a 'node label'.
An ordered collection of concepts, where both the grouping and the ordering are meaningful.
These concept mapping relations mirror semantic relations, and the data model defined below is similar (with the exception of skos:exactMatch) to the data model defined for semantic relations. A distinct vocabulary is provided for concept mapping relations, to provide a convenient way to differentiate links within a concept scheme from links between concept schemes. However, this pattern of usage is not a formal requirement of the SKOS data model, and relies on informal definitions of best practice.
Relates two concepts coming, by convention, from different schemes, and that have comparable meanings
skos:related is disjoint with skos:broaderTransitive
Relates a concept to a concept with which there is an associative semantic relationship.
skos:broadMatch is used to state a hierarchical mapping link between two conceptual resources in different concept schemes.
skos:narrowMatch is used to state a hierarchical mapping link between two conceptual resources in different concept schemes.
This property should not be used directly, but as a super-property for all properties denoting a relationship of meaning between concepts.
Links a concept to a concept related by meaning.
This catalogue was initially produced in late 2025 as the first new wave catalogue of resources within the Semantic Background
A catalogue of reference SHACL validators used by KurrawongAI
A node shape is a shape that specifies constraint that need to be met with respect to focus nodes.
Node shape
Specifies the maximum number of values in the set of value nodes.
max count
A human-readable message (possibly with placeholders for variables) explaining the cause of the result.
message
The type that all value nodes must have.
class
Specifies a list of shapes so that the value nodes must conform to at least one of the shapes.
Specifies the property path of a property shape.
path
Links a shape to its property shapes.
property
Links a shape to a class, indicating that all instances of the class must conform to the shape.
target class
Specifies the minimum number of values in the set of value nodes.
min count
Specifies an RDF datatype that all value nodes must have.
datatype
Human-readable descriptions for the property in the context of the surrounding shape.
description
The (single) value of this property represents an inverse path (object to subject).
inverse path
Links a shape to individual nodes, indicating that these nodes must conform to the shape.
target node
Defines the severity that validation results produced by a shape must have. Defaults to sh:Violation.
severity
The severity for a warning validation result.
Warning
Specifies the node kind (e.g. IRI or literal) each value node.
node kind
The node kind of all IRIs.
IRI
The (single) value of this property must be a list of path elements, representing the elements of alternative paths.
alternative path
A property shape is a shape that specifies constraints on the values of a focus node for a given property or path.
Property shape
Links a shape to a property, indicating that all all objects of triples that have the given property as their predicate must conform to the shape.
target objects of
This vocabulary defines terms used in SHACL, the W3C Shapes Constraint Language.
W3C Shapes Constraint Language (SHACL) Vocabulary
Human-readable labels for the property in the context of the surrounding shape.
name
The node kind of all literals.
Literal
The node kind of all blank nodes.
Blank node
Specifies a list of allowed values so that each value node must be among the members of the given list.
The node kind of all blank nodes or IRIs.
Blank node or IRI
The node kind of all IRIs or literals.
IRI or literal
The (single) value of this property represents a path that is matched zero or more times.
zero or more path
The minimum number of value nodes that must conform to the shape.
qualified min count
The shape that a specified number of values must conform to.
qualified value shape
Specifies a value that must be among the value nodes.
has value
Specifies the node shape that all value nodes must conform to.
node
An RDF node that has caused the result.
value
Specifies whether all node values must have a unique (or no) language tag.
unique languages
Links a shape to a property, indicating that all subjects of triples that have the given property as their predicate must conform to the shape.
target subjects of
If set to true then all nodes conform to this.
deactivated
An optional flag to be used with regular expression pattern matching.
flags
Specifies a regular expression pattern that the string representations of the value nodes must match.
pattern
The SPARQL SELECT query to execute.
select
Links a shape with SPARQL constraints.
constraint (in SPARQL)
Can be used to link to a property group to indicate that a property shape belongs to a group of related property shapes.
group
Specifies the relative order of this compared to its siblings. For example use 0 for the first, 1 for the second.
order
The maximum number of value nodes that can conform to the shape.
qualified max count
Instances of this class represent groups of property shapes that belong together.
Property group
The namespace associated with a prefix in a prefix declaration.
namespace
The prefix of a prefix declaration.
prefix
Links a resource with its namespace prefix declarations.
declare
An entailment regime that indicates what kind of inferencing is required by a shapes graph.
entailment
Shapes graphs that should be used when validating this data graph.
shapes graph
RDF list of shapes to validate the value nodes against.
and
Specifies a list of shapes so that the value nodes must conform to exactly one of the shapes.
exactly one
Specifies a shape that the value nodes must not conform to.
not
Specifies a property that must have smaller values than the value nodes.
less than
Specifies a property that must have smaller or equal values than the value nodes.
less than or equals
If set to true then the shape is closed.
closed
The (single) value of this property represents a path that is matched one or more times.
one or more path
The (single) value of this property represents a path that is matched zero or one times.
zero or one path
An optional RDF list of properties that are also permitted in addition to those explicitly enumerated via sh:property/sh:path.
ignored properties
Specifies a property where the set of values must be disjoint with the value nodes.
disjoint
Specifies a property that must have the same values as the value nodes.
equals
Specifies a list of language tags that all value nodes must have.
language in
Specifies the maximum exclusive value of each value node.
max exclusive
Specifies the maximum inclusive value of each value node.
max inclusive
Specifies the maximum string length of each value node.
max length
Specifies the minimum exclusive value of each value node.
min exclusive
Specifies the minimum inclusive value of each value node.
min inclusive
Specifies the minimum string length of each value node.
min length
The node kind of all blank nodes or literals.
Blank node or literal
Can be used to mark the qualified value shape to be disjoint with its sibling shapes.
qualified value shapes disjoint
The base class of validation results, typically not instantiated directly.
Abstract result
Superclass of components that can take parameters, especially functions and constraint components.
Parameterizable
The class of SPARQL executables that are based on a CONSTRUCT query.
SPARQL CONSTRUCT executable
The class of SPARQL executables based on a SELECT query.
SPARQL SELECT executable
The class of SPARQL executables based on a SPARQL UPDATE.
SPARQL UPDATE executable
The class of SHACL functions.
The class of constraint components.
Constraint component
The class of validators based on SPARQL SELECT queries. The queries are evaluated for each focus node and are supposed to produce bindings for all focus nodes that do not conform.
SPARQL SELECT validator
The prefixes that shall be applied before parsing the associated SPARQL query.
prefixes
The validator(s) used to evaluate a constraint in the context of a node shape.
shape validator
The parameters of a function or constraint component.
parameter
The validator(s) used to evaluate a constraint in the context of a property shape.
property validator
The (meta) class for parameterizable targets that are based on SPARQL queries.
SPARQL target type
The base class of targets such as those based on SPARQL queries.
Outlines how human-readable labels of instances of the associated Parameterizable shall be produced. The values can contain {?paramName} as placeholders for the actual values of the given parameter.
label template
The class of parameter declarations, consisting of a path predicate and (possibly) information about allowed value type, cardinality and other characteristics.
Parameter
The validator(s) used to evaluate constraints of either node or property shapes.
validator
The class of validators, which provide instructions on how to process a constraint definition. This class serves as base class for the SPARQL-based validators and other possible implementations.
The class of validators based on SPARQL ASK queries. The queries are evaluated for each value node and are supposed to return true if the given node conforms.
SPARQL ASK validator
The SPARQL ASK query to execute.
ask
A shape is a collection of constraints that may be targeted for certain nodes.
Shape
The class of validation results.
Validation result
A function backed by a SPARQL query - either ASK or SELECT.
SPARQL function
The expected type of values returned by the associated function.
return type
The class of all node kinds, including sh:BlankNode, sh:IRI, sh:Literal or the combinations of these: sh:BlankNodeOrIRI, sh:BlankNodeOrLiteral, sh:IRIOrLiteral.
Node kind
A constraint component that can be used to verify that each value node is an instance of a given type.
Class constraint component
A constraint component that can be used to indicate that focus nodes must only have values for those properties that have been explicitly enumerated via sh:property/sh:path.
Closed constraint component
A constraint component that can be used to restrict the datatype of all value nodes.
Datatype constraint component
A constraint component that can be used to verify that the set of value nodes is disjoint with the the set of nodes that have the focus node as subject and the value of a given property as predicate.
Disjoint constraint component
A constraint component that can be used to verify that the set of value nodes is equal to the set of nodes that have the focus node as subject and the value of a given property as predicate.
Equals constraint component
A constraint component that can be used to verify that one of the value nodes is a given RDF node.
Has-value constraint component
A constraint component that can be used to exclusively enumerate the permitted value nodes.
In constraint component
A constraint component that can be used to enumerate language tags that all value nodes must have.
Language-in constraint component
A constraint component that can be used to verify that each value node is smaller than all the nodes that have the focus node as subject and the value of a given property as predicate.
Less-than constraint component
A constraint component that can be used to verify that every value node is smaller than all the nodes that have the focus node as subject and the value of a given property as predicate.
less-than-or-equals constraint component
A constraint component that can be used to restrict the maximum number of value nodes.
Max-count constraint component
A constraint component that can be used to restrict the range of value nodes with a maximum exclusive value.
Max-exclusive constraint component
A constraint component that can be used to restrict the range of value nodes with a maximum inclusive value.
Max-inclusive constraint component
A constraint component that can be used to restrict the maximum string length of value nodes.
Max-length constraint component
A constraint component that can be used to restrict the minimum number of value nodes.
Min-count constraint component
A constraint component that can be used to restrict the range of value nodes with a minimum exclusive value.
Min-exclusive constraint component
A constraint component that can be used to restrict the range of value nodes with a minimum inclusive value.
Min-inclusive constraint component
A constraint component that can be used to restrict the minimum string length of value nodes.
Min-length constraint component
A constraint component that can be used to verify that all value nodes conform to the given node shape.
Node constraint component
A constraint component that can be used to restrict the RDF node kind of each value node.
Node-kind constraint component
A constraint component that can be used to verify that value nodes do not conform to a given shape.
Not constraint component
A constraint component that can be used to verify that every value node matches a given regular expression.
Pattern constraint component
A constraint component that can be used to verify that a specified maximum number of value nodes conforms to a given shape.
Qualified-max-count constraint component
A constraint component that can be used to verify that a specified minimum number of value nodes conforms to a given shape.
Qualified-min-count constraint component
The class of SHACL rules. Never instantiated directly.
The class of resources that encapsulate a SPARQL query.
SPARQL executable
The (meta) class for parameterizable targets. Instances of this are instantiated as values of the sh:target property.
Target type
A constraint component that can be used to specify that no pair of value nodes may use the same language tag.
Unique-languages constraint component
The class of validation result severity levels, including violation and warning levels.
Severity
The class of constraints backed by a JavaScript function.
JavaScript-based constraint
Abstract base class of resources that declare an executable JavaScript.
JavaScript executable
The class of SHACL functions that execute a JavaScript function when called.
JavaScript function
Represents a JavaScript library, typically identified by one or more URLs of files to include.
JavaScript library
The class of SHACL rules expressed using JavaScript.
JavaScript rule
The class of targets that are based on JavaScript functions.
JavaScript target
The (meta) class for parameterizable targets that are based on JavaScript functions.
JavaScript target type
A SHACL validator based on JavaScript. This can be used to declare SHACL constraint components that perform JavaScript-based validation when used.
JavaScript validator
The class of prefix declarations, consisting of pairs of a prefix with a namespace.
Prefix declaration
A class of result annotations, which define the rules to derive the values of a given annotation property as extra values for a validation result.
Result annotation
The class of SPARQL executables that are based on an ASK query.
SPARQL ASK executable
The class of constraints based on SPARQL SELECT queries.
SPARQL constraint
The class of SHACL rules based on SPARQL CONSTRUCT queries.
SPARQL CONSTRUCT rule
The class of targets that are based on SPARQL queries.
SPARQL target
A rule based on triple (subject, predicate, object) pattern.
The class of SHACL validation reports.
Validation report
A constraint component that can be used to test whether a value node conforms to all members of a provided list of shapes.
And constraint component
ClosedConstraintComponent ignoredProperties
A constraint component that can be used to verify that a given node expression produces true for all value nodes.
Expression constraint component
ExpressionConstraintComponent expression
The severity for an informational validation result.
Info
A constraint component with the parameter sh:js linking to a sh:JSConstraint containing a sh:script.
JavaScript constraint component
LanguageInConstraintComponent languageIn
LessThanOrEqualsConstraintComponent lessThanOrEquals
MaxExclusiveConstraintComponent maxExclusive
MaxInclusiveConstraintComponent maxInclusive
MinExclusiveConstraintComponent minExclusive
MinInclusiveConstraintComponent minInclusive
A constraint component that can be used to restrict the value nodes so that they conform to at least one out of several provided shapes.
Or constraint component
A constraint component that can be used to verify that all value nodes conform to the given property shape.
Property constraint component
QualifiedMaxCountConstraintComponent qualifiedMaxCount
QualifiedMaxCountConstraintComponent qualifiedValueShape
QualifiedMaxCountConstraintComponent qualifiedValueShapesDisjoint
QualifiedMinCountConstraintComponent qualifiedMinCount
QualifiedMinCountConstraintComponent qualifiedValueShape
QualifiedMinCountConstraintComponent qualifiedValueShapesDisjoint
A constraint component that can be used to define constraints based on SPARQL queries.
SPARQL constraint component
UniqueLangConstraintComponent uniqueLang
The severity for a violation validation result.
Violation
A constraint component that can be used to restrict the value nodes so that they conform to exactly one out of several provided shapes.
Exactly one constraint component
The annotation property that shall be set.
annotation property
The (default) values of the annotation property.
annotation value
The name of the SPARQL variable from the SELECT clause that shall be used for the values.
annotation variable name
The shapes that the focus nodes need to conform to before a rule is executed on them.
condition
True if the validation did not produce any validation results, and false otherwise.
conforms
The SPARQL CONSTRUCT query to execute.
construct
A default value for a property, for example for user interface tools to pre-populate input fields.
default value
Links a result with other results that provide more details, for example to describe violations against nested shapes.
detail
The shape that all input nodes of the expression need to conform to.
filter shape
The focus node that was validated when the result was produced.
focus node
A list of node expressions that shall be intersected.
intersection
The name of the JavaScript function to execute.
JavaScript function name
Declares which JavaScript libraries are needed to execute this.
Declares the URLs of a JavaScript library. This should be the absolute URL of a JavaScript file. Implementations may redirect those to local files.
JavaScript library URL
The node expression producing the input nodes of a filter shape expression.
nodes
An expression producing the nodes that shall be inferred as objects.
Indicates whether a parameter is optional.
optional
An expression producing the properties that shall be inferred as predicates.
predicate
The validation results contained in a validation report.
result
Links a SPARQL validator with zero or more sh:ResultAnnotation instances, defining how to derive additional result properties based on the variables of the SELECT query.
result annotation
Human-readable messages explaining the cause of the result.
result message
The path of a validation result, based on the path of the validated property shape.
result path
The severity of the result, e.g. warning.
result severity
The rules linked to a shape.
rule
If true then the validation engine was certain that the shapes graph has passed all SHACL syntax requirements during the validation process.
shapes graph well-formed
The constraint that was validated when the result was produced.
source constraint
The constraint component that is the source of the result.
source constraint component
The shape that is was validated when the result was produced.
source shape
An expression producing the resources that shall be inferred as subjects.
subject
Suggested shapes graphs for this ontology. The values of this property may be used in the absence of specific sh:shapesGraph statements.
suggested shapes graph
Links a shape to a target specified by an extension language, for example instances of sh:SPARQLTarget.
target
A node expression that represents the current focus node.
this
A list of node expressions that shall be used together.
union
The SPARQL UPDATE to execute.
update
The node expression that must return true for the value nodes.
expression
JavaScript constraint
EDES Vegetation Mapping Protocol Shapes Graph
TERN's ecologists have determined the feature type is _vegetation stratum_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/32834f36-a478-45be-97f4-ff2ff51e9f5c[`vegetation stratum`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/cea92774-6d4b-4880-8d07-1fe23c4a5e16>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/cea92774-6d4b-4880-8d07-1fe23c4a5e16> ; sosa:hasResult ?this . }
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/15361f98-7669-410e-9b04-e9be069c7508>`. `<https://linked.data.gov.au/def/nrm/15361f98-7669-410e-9b04-e9be069c7508>` is the IRI for "Vegetation Mapping Module".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/15361f98-7669-410e-9b04-e9be069c7508`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/cea92774-6d4b-4880-8d07-1fe23c4a5e16>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 0 and 200 inclusive.
The result _MUST_ have a value between 0 and 200 inclusively.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/cea92774-6d4b-4880-8d07-1fe23c4a5e16>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
TERN's ecologists have determined the feature type is _plant specimen_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/2e122e23-881c-43fa-a921-a8745f016ceb[`plant specimen`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/4a550407-5158-497c-982a-9f1b662b73e9>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/4a550407-5158-497c-982a-9f1b662b73e9> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/4a550407-5158-497c-982a-9f1b662b73e9> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/4a550407-5158-497c-982a-9f1b662b73e9>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/4a550407-5158-497c-982a-9f1b662b73e9>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0378976a-0018-4604-826d-1886ca5f38c3>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0378976a-0018-4604-826d-1886ca5f38c3> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0378976a-0018-4604-826d-1886ca5f38c3>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 1 and 100 inclusive.
The result _MUST_ have a value between 1 and 100 inclusively.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0378976a-0018-4604-826d-1886ca5f38c3>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
Value _MUST_ be between 0 exclusive and 1000 inclusive.
The result _MUST_ have a value between 0 exclusively and 1000 inclusively.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/15361f98-7669-410e-9b04-e9be069c7508>`. # `<https://linked.data.gov.au/def/nrm/15361f98-7669-410e-9b04-e9be069c7508>` is the IRI for "Vegetation mapping module".
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Vegetation growth stage types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Vegetation growth stage types controlled vocabulary.
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/30985f0b-095b-50ee-8dfe-f872f73ea5a0>`. `<https://linked.data.gov.au/def/nrm/30985f0b-095b-50ee-8dfe-f872f73ea5a0>` is the IRI for "Vegetation growth stage types".
An RDF/OWL vocabulary defining GML geometry types
SHACL Shapes for the TERN Ontology. The version number of this SHACL file is kept in sync with the main TERN Ontology
A `prov:Association` _MUST_ have exactly 1 `prov:agent` predicate where the value node is an IRI of an individual with the type `prov:Agent`.
Associate a plan to the agent which they use for their role in some activity. This may or may not be the same as the procedure of a `tern:Sampling` or a `tern:Observation` depending on the role of the agent.
A `prov:Association` _MAY_ have some `prov:hadPlan` predicate where the value node is an IRI.
`prov:hadRole` references the Role (i.e. the function of an entity with respect to an activity), in the context of an instantaneous usage, generation, association, start, and end.
A `prov:Association` _MUST_ have exactly 1 `prov:hadRole` predicate where the value node is an IRI of a controlled concept from link:http://def.isotc211.org/iso19115/-1/2018/CitationAndResponsiblePartyInformation/code/CI_RoleCode[ISO 19115-1's CI Role Code].
Useful to capture the proximate class type in situations when link:http://www.w3.org/2000/01/rdf-schema#subClassOf[`rdfs:subClassOf`] entailment is enabled and `rdf:type` is not suitable.
Recommended practice is to use a controlled vocabulary such as the DCMI Type Vocabulary link:http://dublincore.org/documents/dcmi-type-vocabulary/[DCMI-TYPE]. To describe the file format, physical medium, or dimensions of the resource, use the property Format.
A `dcterms:type` predicate _MUST_ have an IRI value.
The identifier of the attribute concept. Attribute concepts are usually described with SKOS controlled vocabularies. TERN manages a list of link:http://linked.data.gov.au/def/tern-cv/dd085299-ae86-4371-ae15-61dfa432f924[attributes].
A `tern:Attribute` _MUST_ have exactly 1 `tern:attribute` predicate where the value node is an IRI.
The direct link to the IRI or RDF literal value. The simple value _MUST_ be the same value captured in `rdf:value` of the `tern:Value` instance.
A `tern:Attribute` _MUST_ have exactly 1 `tern:hasSimpleValue` predicate where the value node is an IRI or literal.
A link to a link:https://w3id.org/tern/ontologies/tern/Value[`tern:Value`] instance which encapsulates the value of this Attribute.
A `tern:Attribute` _MUST_ have exactly 1 `tern:hasValue` predicate where the value node is an IRI.
A link to the individual which this attribute and its value is applied to. Inverse property of link:https://w3id.org/tern/ontologies/tern/hasAttribute[`tern:hasAttribute`].
A `tern:isAttributeOf` _MUST_ have an IRI value.
There _MUST_ exist exactly 1 `void:inDataset` property with an IRI value to a `tern:RDFDataset`.
A `prov:Attribution` _MUST_ have exactly 1 `prov:agent` predicate where the value node is an IRI of an individual with the type `prov:Agent`.
A `prov:Attribution` _MUST_ have exactly 1 `prov:hadRole` predicate where the value node is an IRI of a controlled concept from link:http://def.isotc211.org/iso19115/-1/2018/CitationAndResponsiblePartyInformation/code/CI_RoleCode[ISO 19115-1's CI Role Code].
`tern:Boolean` _MUST_ have exactly 1 `rdf:value` predicate where the value node is a literal with a datatype of `xsd:boolean`.
A `dcterms:description` predicate has a literal value with the datatype `xsd:string`.
A `tern:Survey`, `tern:SiteVisit` or a `tern:Intervention` _MAY_ have a maximum of 1 `prov:endedAtTime` predicate where the value node is a literal with the datatype `xsd:dateTime`.
A `tern:Survey`, `tern:SiteVisit` or a `tern:Intervention` _MUST_ have exactly 1 `prov:startedAtTime` predicate where the value node is a literal with the datatype `xsd:dateTime`.
Exactly 1 `sosa:usedProcedure` _MUST_ exist where the value node is a `tern:Method` or `tern:Procedure`.
Indicates the agent (person, organization, or service) that performed the calibration activity. This property links a Calibration to the responsible agent.
A `tern:calibratedBy` predicate _MUST_ have an IRI value of type `prov:Agent`.
Relation from a calibration activity to a system property that is being calibrated. This property is used to specify which system property is the target of the calibration.
A `tern:calibratesProperty` predicate _MUST_ have an IRI or blank node value of type `ssn-system:SystemProperty`.
Links to the actual measured value obtained during calibration. This represents the value returned by the system or device being calibrated.
A `tern:Calibration` _MAY_ have maximum one `tern:calibrationActualResult` predicate where the value is a blank node or IRI of type `tern:Value`.
Links to a value representing the difference between the reference and actual results during calibration. This offset can be used for measurement corrections.
A `tern:Calibration` _MAY_ have maximum one `tern:calibrationOffset` predicate where the value is a blank node or IRI of type `tern:Value`.
Links to a reference value used during calibration. This represents the known, standard, or expected value against which the actual measurement is compared.
A `tern:Calibration` _MAY_ have maximum one `tern:calibrationReferenceResult` predicate where the value is a blank node or IRI of type `tern:Value`.
Relation from a calibration activity to a system capability that is being verified. This property is used to specify which system capability is being confirmed or validated.
A `tern:verifiesCapability` predicate _MUST_ have an IRI or blank node value of type `ssn-system:SystemCapability`.
A `tern:Dataset` _MAY_ have a `dcat:distribution` predicate with a value of type `tern:Distribution`.
A `tern:Date` _MUST_ have exactly 1 `rdf:value` predicate where the value node is a literal with a datatype of `xsd:date`.
A `tern:DateTime` _MUST_ have exactly 1 `rdf:value` predicate where the value node is a literal with a datatype of `xsd:dateTime`.
A `geo:hasGeometry` predicate _MUST_ have a blank node or IRI value.
A `sdo:spatial` predicate _MUST_ have a blank node or IRI value.
Relation between a Deployment and the Platform on which the Systems are deployed.
A `tern:Deployment` _MAY_ have 1 `ssh:deployedOnPlatform` predicate where the value node is an IRI of type `tern:Platform`.
Relation between a Deployment and a deployed System.
A `tern:Deployment` _MAY_ have one or many `ssn:deployedSystem` predicate where the value node is an IRI of type `tern:System`.
A `tern:DigitalCamera` _MUST_ have at least 1 `schema:model` predicate.
The preferred label for the digital camera.
A `tern:DigitalCamera` _MUST_ have at least 1 `skos:prefLabel` predicate.
The source of information about the digital camera.
A `tern:DigitalCamera` _MUST_ have at least 1 `dcterms:source` predicate with a string value.
A `tern:DigitalCamera` _MUST_ have at least 1 `schema:manufacturer` predicate with a string value.
Alternative labels for the digital camera.
If present, `skos:altLabel` predicates on a `tern:DigitalCamera` _MUST_ have string values.
If present, `skos:definition` predicates on a `tern:DigitalCamera` _MUST_ have string values.
A `tern:Dimension` _MUST_ have exactly 1 `tern:width` predicate with a double or integer value.
The unit of measurement for the dimensions.
A `tern:Dimension` _MUST_ have exactly 1 `tern:unit` predicate with a value of type `qudt:Unit`.
A `tern:Dimension` _MUST_ have exactly 1 `tern:length` predicate with a double or integer value.
Value of a temporal extent expressed as a decimal number scaled by a temporal unit
A `time:Duration` _MUST_ have exactly 1 `time:numericDuration` predicate where the value node is a literal with a datatype of `xsd:decimal`.
The temporal unit which provides the precision of a date-time value or scale of a temporal extent.
A `time:Duration` _MUST_ have exactly 1 `time:unitType` predicate where the value node is an IRI from a controlled list.
The feature type of a `tern:FeatureOfInterest` from a controlled vocabulary.
A `tern:FeatureOfInterest` _MUST_ have exactly 1 `tern:featureType` predicate where the value node is an IRI.
A `prov:qualifiedAttribution` _MUST_ have a blank node or IRI value where the type is `prov:Attribution`.
A `prov:wasAttributedTo` predicate _MUST_ have an IRI value of type `prov:Agent`.
An `rdfs:comment` _MUST_ have a literal value.
A `tern:FeatureOfInterest` _MAY_ have a `sosa:hasSample` predicate where the value node is an IRI of type `tern:Sample`.
A `tern:FeatureOfInterest` _MAY_ have a `sosa:isFeatureOfInterestOf` predicate where the value node is an IRI of type `tern:Observation` or `tern:Sampling`.
A `tern:hasAttribute` predicate _MUST_ have a blank node or an IRI value of type `tern:Attribute`.
A property that links, e.g., a FeatureOfInterest to a Site or Transect.
A `tern:FeatureOfInterest` _MAY_ have a `tern:hasSite` predicate where the value node is an IRI of type `tern:Site` or `tern:Transect`.
A `tern:Float` _MAY_ have 1 `tern:uncertainty` predicate where the value node is a literal with a datatype of `xsd:double` or `xsd:float`.
A `tern:Float` _MUST_ have exactly 1 `rdf:value` where the value node is a literal with a datatype of `xsd:double` or `xsd:float`.
The unit of measure of the value. Recommended best practice is to use the link:http://qudt.org/vocab/unit/[QUDT units of measure vocabulary].
A `tern:unit` predicate _MUST_ have an IRI value.
A `tern:FluxTower` _MAY_ have at most 1 `tern:ozfluxID` predicate with a string value.
A `tern:FluxTower` _MAY_ have at most 1 `tern:igbpCode` predicate with a string value.
If present, `dcterms:description` predicates on a `tern:FluxTower` _MUST_ have string values.
If present, `rdfs:comment` predicates on a `tern:FluxTower` _MUST_ have string values.
The date when the flux tower was decommissioned.
A `tern:FluxTower` _MAY_ have at most 1 `tern:dateDecommissioned` predicate with a date value.
A `tern:FluxTower` _MAY_ have at most 1 `tern:fluxnetID` predicate with a string value.
A `tern:FluxTower` _MAY_ have at most 1 `sosa:isHostedBy` predicate with a value of type `tern:Site`.
A `tern:FluxTower` _MAY_ have at most 1 `tern:purpose` predicate with a string value.
A `tern:FluxTower` _MUST_ have exactly 1 `tern:centroidPoint` predicate with a value of type `sf:Point`.
The date when the flux tower was commissioned.
A `tern:FluxTower` _MUST_ have exactly 1 `tern:dateCommissioned` predicate with a date value.
A `tern:FluxTower` _MUST_ have exactly 1 `rdfs:label` predicate with a string value.
This SHACL shape defines constraints for the `geo:hasGeometry` property. It specifies that values of the `geo:hasGeometry` property of `tern:IGSN` must be IRIs of type `geo:Geometry`. The status of this shape is experimental, indicating that it might be subject to change in the future.
A `tern:IGSN` _MUST_ have at least 1 `geo:hasGeometry` of type `geo:Geometry`.
This SHACL shape defines constraints for the `dcterms:hasPart` property. It specifies that values of the `dcterms:hasPart` property of `tern:IGSN` must be IRIs of type `tern:IGSN`. The status of this shape is experimental, indicating that it might be subject to change in the future.
A `dcterms:hasPart` predicate _MUST_ have an IRI value of type `tern:IGSN`.
This SHACL shape defines constraints for the `dcterms:isPartOf` property. It specifies that values of the `dcterms:isPartOf` property of `tern:IGSN` must be IRIs of type `tern:IGSN`. The status of this shape is experimental, indicating that it might be subject to change in the future.
A `dcterms:isPartOf` predicate _MUST_ have an IRI value of type `tern:IGSN`.
This SHACL shape defines constraints for the `dcterms:publisher` property. It specifies that values of the `dcterms:publisher` property of `tern:IGSN` must be IRIs of specified types. The status of this shape is experimental, indicating that it might be subject to change in the future.
A `dcterms:publisher` predicate _MUST_ have an IRI value of type `tern:IGSN`.
This SHACL shape defines constraints for the `dcterms:relation` property. It specifies that values of the `dcterms:relation` property of `tern:IGSN` must be IRIs of type `tern:IGSN`. The status of this shape is experimental, indicating that it might be subject to change in the future.
A `dcterms:relation` predicate _MUST_ have an IRI value of type `tern:IGSN`.
The sample sub type of a `tern:IGSN` from a controlled vocabulary.
A `tern:IGSN` _MUST_ have exactly 1 `tern:sampleSubType` predicate where the value node is an IRI.
The sample type of a `tern:IGSN` from a controlled vocabulary.
A `tern:IGSN` _MUST_ have exactly 1 `tern:sampleType` predicate where the value node is an IRI.
A `tern:IRI` _MUST_ have exactly 1 `rdf:value` predicate where the value node is an IRI.
If present, `dcterms:description` predicates on a `tern:Input` _MUST_ have string values.
A `tern:Input` _MAY_ have at most 1 `rdf:value` predicate.
A `tern:Input` _MUST_ have exactly 1 `rdfs:label` predicate with a string value.
One or more of [`time:inXSDDate`, `time:inXSDDateTimeStamp`, `time:inXSDgYear`, `time:inXSDgYearMonth`, `time:inTimePosition`, and `time:inDateTime`] _MUST_ be present.
Position of an instant, expressed using a structured description.
Value _MUST_ be a literal with a datatype of `xsd:dateTime`. Maximum of one value is allowed for this property.
Position of a time instant expressed as a `TimePosition`.
Value _MUST_ be an instance of `time:TimePosition`. Maximum of one value is allowed for this property. The value node _MUST_ be a blank node or IRI.
Position of an instant, expressed using `xsd:date`.
Value _MUST_ be a literal with a datatype of `xsd:date`. Maximum of one value is allowed for this property.
Position of an instant, expressed using `xsd:dateTimeStamp`.
Value _MUST_ be a literal with a datatype of `xsd:dateTimeStamp`. Maximum of one value is allowed for this property.
Position of an instant, expressed using `xsd:gYear`.
Value _MUST_ be a literal with a datatype of `xsd:gYear`. Maximum of one value is allowed for this property.
Position of an instant, expressed using `xsd:gYearMonth`.
Value _MUST_ be a literal with a datatype of `xsd:gYearMonth`. Maximum of one value is allowed for this property.
A `tern:Integer` _MAY_ have 1 `tern:uncertainty` predicate where the value node is a literal with a datatype of `xsd:integer`, `xsd:double`, or `xsd:float`.
A `tern:Integer` _MUST_ have exactly 1 `rdf:value` predicate where the value node is a literal with a datatype of `xsd:integer`
A `time:hasBeginning` predicate _MUST_ exist where the value node is a blank node or IRI of type `time:Instant`.
Duration of a temporal entity, event or activity, or thing, expressed as a scaled value.
A `time:hasDuration` _MAY_ exist where the value node is a blank node or IRI of type `time:Duration`.
A `time:hasEnd` predicate _MUST_ exist where the value node is a blank node or IRI of type `time:Instant`.
A `prov:qualifiedAssociation` _MUST_ have a blank node or IRI value of type `prov:Association`.
A `prov:wasAssociatedWith` predicate _MUST_ an IRI value of type `prov:Agent` or `sdo:Person`.
Exactly 1 `sosa:hasFeatureOfInterest` predicate _MUST_ exist_ with an IRI value.
A `tern:Intervention` _MAY_ have a maximum of 1 `tern:interventionType` predicate where the value node is an IRI.
The date when, e.g., a Site is ready to commence its operations, after it is successfully installed and tested.
A managed feature _MUST_ have exactly 1 `tern:dateCommissioned` predicate where the value node is a literal with the datatype `xsd:date`.
The date when, e.g., a Site is decommissioned or stopped operating.
A managed feature _MAY_ have a maximum of 1 `tern:dateDecommissioned` predicate where the value node is a literal with the datatype `xsd:date`.
A `dwc:materialSampleID` predicate _MUST_ have a literal value or IRI value.
A `tern:Sample` or `tern:MaterialSample` _MUST_ have exactly 1 `tern:hasIGSN` predicate where the value node is an IRI of type `tern:IGSN`.
The exclusive upper bound of the measurement range. This value represents the value just above the maximum that can be measured by the sensor.
A `qudt:maxExclusive` predicate _MAY_ have maximum one literal value representing the exclusive upper bound of the measurement range.
The inclusive upper bound of the measurement range. This value represents the maximum value that can be measured by the sensor.
A `qudt:maxInclusive` predicate _MAY_ have maximum one literal value representing the upper bound of the measurement range.
The exclusive lower bound of the measurement range. This value represents the value just below the minimum that can be measured by the sensor.
A `qudt:minExclusive` predicate _MAY_ have maximum one literal value representing the exclusive lower bound of the measurement range.
The inclusive lower bound of the measurement range. This value represents the minimum value that can be measured by the sensor.
A `qudt:minInclusive` predicate _MAY_ have maximum one literal value representing the lower bound of the measurement range.
A `tern:Method` _MAY_ have at most 1 `schema:timeRequired` predicate with a string value.
If present, `skos:note` predicates on a `tern:Method` _MUST_ have string values.
The categorical collection of the method.
If present, `tern:hasCategoricalCollection` predicates on a `tern:Method` _MUST_ have values of type `skos:Collection`.
If present, `tern:hasParameter` predicates on a `tern:Method` _MUST_ have values of type `skos:Concept`.
If present, `dcterms:source` predicates on a `tern:Method` _MUST_ have string or URI values.
A `tern:Method` _MAY_ have at most 1 `tern:instructions` predicate with a value of type `rdf:Seq`.
A `tern:Method` _MAY_ have at most 1 `skos:definition` predicate with a string value.
A `tern:Method` _MAY_ have at most 1 `tern:equipment` predicate with a value of type `skos:Concept`.
A `tern:Method` _MAY_ have at most 1 `tern:purpose` predicate with a string value.
A `tern:Method` _MAY_ have at most 1 `tern:scope` predicate with a string value.
A `tern:Method` _MUST_ have exactly 1 `skos:prefLabel` predicate with a string value.
A `tern:undertakenAfter` predicate _MUST_ have an IRI value of type `tern:Method`.
A `tern:undertakenBefore` predicate _MUST_ have an IRI value of type `tern:Method`.
A `tern:undertakenComplementarily` predicate _MUST_ have an IRI value of type `tern:Method`.
A `tern:undertakenConcurrently` predicate _MUST_ have an IRI value of type `tern:Method`.
The local value of the observable property.
A `tern:ObservableProperty` _MAY_ have at most 1 `tern:localValue` predicate with a value of type `skos:Concept`.
The parameter value of the observable property.
A `tern:ObservableProperty` _MUST_ have exactly 1 `rdf:value` predicate with a value of type `tern:Parameter`.
The local vocabulary of the observable property.
A `tern:ObservableProperty` _MAY_ have at most 1 `tern:localVocabulary` predicate with a value of type `skos:ConceptScheme`, `skos:Collection`, or `owl:Ontology`.
The vocabulary of the observable property.
A `tern:ObservableProperty` _MUST_ have exactly 1 `tern:vocabulary` predicate with a value of type `skos:ConceptScheme`, `skos:Collection`, or `owl:Ontology`.
A `tern:Observation` _MUST_ have exactly 1 `sosa:hasResult` where the value node is a blank node or IRI of type `tern:Value`.
Exactly 1 `sosa:hasSimpleResult` predicate _MUST_ exist where the value node is an IRI or literal.
A `sosa:madeBySensor` predicate _MAY_ exist where the value node is an IRI.
A `tern:Observation` _MUST_ have exactly 1 `sosa:observedProperty` where the value node is an IRI.
Exactly 1 `sosa:phenomenonTime` predicate _MUST_ exist where the value node is a blank node or IRI of type `time:Instant`.
A `tern:resultDateTime` predicate _MUST_ have a literal value where the datatype is an `xsd:date`, `xsd:dateTime` or `xsd:dateTimeStamp`.
Exactly 1 ``tern:resultDateTime` _MUST_ exist where the value node is a literal of datatype `xsd:date`, `xsd:dateTime`, or `xsd:dateTimeStamp`.
A property that links, e.g., a Site to a Site Visit.
A maximum of 1 `tern:hasSiteVisit` _MAY_ exist where the value node is an IRI of type `tern:SiteVisit`.
A maximum of 1 `tern:observationType` _MAY_ exist with an IRI value.
A `tern:ObservationCollection` _MAY_ have a maximum of 1 `sosa:hasFeatureOfInterest` predicate where the value node is an IRI of type `tern:FeatureOfInterest`.
A `tern:ObservationCollection` _MUST_ have at least 1 `sosa:hasMember` predicate where the value node is an IRI of type `tern:Observation` or `tern:ObservationCollection`.
Link to the ultimate feature of interest of an observation or act of sampling. This is useful when the proximate feature of interest is a sample of the ultimate feature of interest, directly or transitively.
A `tern:ObservationCollection` _MAY_ have a maximum of 1 `sosa:hasUltimateFeatureOfInterest` where the value node is an IRI of type `tern:FeatureOfInterest`.
A `tern:ObservationCollection` _MAY_ have a maximum of 1 `sosa:madeBySensor` predicate where the value node is an IRI of type `tern:Sensor`.
A `tern:ObservationCollection` _MAY_ have a maximum of 1 `sosa:observedProperty` predicate where the value node is an IRI.
A `tern:ObservationCollection` _MAY_ have a maximum of 1 `sosa:phenomenonTime` predicate where the value node is an IRI of type `time:Instant`.
A `tern:ObservationCollection` _MAY_ have a maximum of 1 `tern:resultDateTime` predicate where the value node is a literal with the datatype `xsd:date`, `xsd:dateTime` or `xsd:dateTimeStamp`.
A `tern:resultDateTime` predicate _MUST_ have a literal value with a datatype of `xsd:date`, `xsd:dateTime` or `xsd:dateTimeStamp`.
A `tern:ObservationCollection` _MAY_ have a maximum of 1 `sosa:usedProcedure` predicate where the value node is an IRI.
The Köppen Climate Classification code that categorizes climates based on temperature, precipitation, and seasonal patterns. It was developed by Wladimir Köppen in 1884 and has been refined over time.
A `tern:climateCode` predicate _MAY_ have an IRI value or a literal value.
A `tern:Platform` _MUST_ have exactly 1 `tern:platformType` predicate where the value node is a skos:Concept.
A `tern:purpose` predicate has a literal value with the datatype `xsd:string`.
A `tern:Procedure` _MUST_ have exactly 1 `tern:vocabulary` predicate.
A `tern:Procedure` _MAY_ have at most 1 `ssn:hasInput` predicate with a value of type `tern:Input`.
A `tern:Procedure` _MUST_ have exactly 1 `rdf:value` predicate with a value of type `tern:Method`.
If present, `tern:hasMethod` predicates on a `tern:Procedure` _MUST_ have values of type `tern:Method`.
A `tern:RDFDataset` _MAY_ have a `dcterms:contributor` predicate where the value node is an IRI.
Date of creation of the dataset. The value should be formatted and data-typed as an `xsd:date`.
A `tern:RDFDataset` _MAY_ have a `dcterms:created` predicate where the value node is a literal with the datatype `xsd:date`.
A `tern:RDFDataset` _MAY_ have a `dcterms:creator` predicate where the value node is an IRI.
A point or period of time associated with an event in the life-cycle of the resource. The value should be formatted and data-typed as an `xsd:date`.
A `tern:RDFDataset` _MAY_ have a `dcterms:date` predicate where the value node is a literal with the datatype `xsd:date`.
Date of formal issuance (e.g., publication) of the dataset. The value should be formatted and datatyped as an `xsd:date`.
A `tern:RDFDataset` _MAY_ have a `dcterms:issued` predicate where the value node is a literal with the datatype `xsd:date`.
A `tern:RDFDataset` _MAY_ have a `dcterms:license` predicate where the value node is an IRI.
Date on which the dataset was changed. The value should be formatted and datatyped as an `xsd:date`.
A `tern:RDFDataset` _MAY_ have a `dcterms:modified` predicate where the value node is a literal with the datatype `xsd:date`.
A `tern:RDFDataset` _MAY_ have a `dcterms:publisher` predicate where the value node is an IRI.
A `tern:RDFDataset` _MAY_ have a `dcterms:rightsHolder` predicate where the value node is an IRI or literal.
A `tern:RDFDataset` _MAY_ have a `dcterms:source` predicate where the value node is an IRI.
A topic of the resource. Recommended practice is to refer to the subject with a URI. If this is not possible or feasible, a literal value that identifies the subject may be provided. Both should preferably refer to a subject in a controlled vocabulary.
A `tern:RDFDataset` _MAY_ have a `dcterms:subject` predicate where the value node is an IRI or literal.
The `void:subset` property can be used to provide descriptions of parts of a dataset. A part of a dataset is itself a `void:Dataset`, and any of the annotations for datasets listed in this guide can be applied to the subset. Reasons for subdividing a dataset might include: - Parts have different provenance (different `dcterms:source`) - Parts have different publication dates (different `dcterms:date`) - Parts are accesible through different SPARQL endpoints (different `void:sparqlEndpoint`) - Parts are about different topics (different `dcterms:subject`) - Parts can be downloaded separately in different RDF dumps (different `void:dataDump`)
A `tern:RDFDataset` _MAY_ have a `void:subset` predicate where the value node is an IRI of type `void:Dataset`.
A `tern:RDFDataset` _MAY_ have a `dcterms:title` predicate where the value node is a literal with a datatype `xsd:string`.
A vocabulary or `owl:Ontology` whose classes or properties are used in a `void:Dataset`.
A `tern:RDFDataset` _MAY_ have a `void:vocabulary` predicate where the value node is an IRI.
A `tern:Result` _MAY_ have at most 1 `sosa:isResultOf` predicate where the value node is an IRI of type `tern:Observation` or `tern:Sampling`.
Relation linking a Result to the Sampling that created or caused it.
A `tern:Sample` _MAY_ have a `sosa:isResultOf` predicate where the value node is an IRI of type `tern:Sampling`.
At least one sdo:spatial, geo:hasGeometry, tern:transectStartPoint, or tern:transectEndPoint exists along the chain of sosa:isSampleOf or tern:hasSite paths.
Sample's sosa:isSampleOf or tern:hasSite
Relation between an entity that implements a Procedure in some executable way and the Procedure (an algorithm, procedure or method).
A `tern:Sampler` _MUST_ have at least 1 `ssn:implements` predicate where the value node is an IRI.
A `sosa:madeSampling` predicate _MAY_ exist where the value node is an IRI.
A `tern:Sampling` _MUST_ have at least 1 `sosa:hasResult` predicate where the value node is an IRI of type `tern:Sample`.
A `tern:Sampling` _MAY_ have a `sosa:madeBySampler` predicate where the value node is an IRI of type `tern:Sampler`.
A `tern:Sampling` _MAY_ have a maximum of 1 `tern:samplingType` predicate where the value node is an IRI.
A `tern:Sensor` _MUST_ have at least 1 `ssn:implements` predicate where the value node is an IRI.
Relation between a `Sensor` and an `Observation` made by the `Sensor`.
A `tern:Sensor` _MAY_ have an `sosa:madeObservation` predicate where the value node is an IRI of type `tern:Observation`.
Relation between a `Sensor` and an `ObservableProperty` that it is capable of sensing.
A `tern:Sensor` _MAY_ have an `sosa:observes` predicate where the value node is an IRI.
A `tern:Site` _MAY_ have a maximum of 1 `tern:dimension` predicate where the value node is a literal with the datatype `xsd:string.
A `tern:Site` _MUST_ have exactly 1 `tern:featureType` predicate where the value node is an IRI.
A `tern:Site` _MAY_ have a `tern:hasSiteVisit` predicate where the value node is an IRI of type `tern:SiteVisit`.
A `tern:Site` _MAY_ have a maximum of 1 `tern:locationProcedure` predicate where the value node is an IRI.
Exists if the subject SpatialObject is spatially within the object SpatialObject. DE-9IM: T*F**F***
A `geo:sfWithin` _MUST_ have an IRI value.
The description of the site's location. Example: 10km west of Fletcherview Tropical Rangeland SuperSite.
A `tern:locationDescription` _MUST_ have a literal value with the datatype `xsd:string`.
The description of the site. Example: Outer fringe of larger lake chain, isolated by reddish dunes, yellow sand fan into western edge. Very few, 3, plants regenerating after recent moderate rains. Silt, sand with scattered iron conglomerate stones on surface.
A `tern:siteDescription` _MUST_ have a literal value with the datatype `xsd:string`.
Relation between a System and a Deployment, recording that the System is deployed in that Deployment.
A `tern:System` _MAY_ have an `ssn:hasDeployment` predicate where the value node is an IRI of type `tern:Deployment`.
A `tern:System` _MAY_ have a maximum of 1 `sosa:isHostedBy` predicate where the value node is an IRI of type `tern:Platform`.
The type of system. Values are from some controlled vocabulary.
A `tern:System` _MAY_ have a `tern:systemType` predicate where the value node is an IRI.
Relevant contact information for the resource. Can be used to identify a person or organization that can be contacted for questions about the resource.
A resource _MAY_ have a `dcat:contactPoint` predicate where the value is an IRI or literal.
A related source from which the described resource is derived. The described resource may be derived from the related source in whole or in part.
A resource _MAY_ have a `dcterms:source` predicate where the value is an IRI or literal.
The serial number or any alphanumeric identifier of a device (e.g., sensor, sampler).
A `sdo:serialNumber` predicate _MUST_ have a literal value.
A `skos:altLabel` predicate _MUST_ have a literal value.
Indicates that two concepts, terms, or resources are semantically equivalent and can be used interchangeably. Used to link a resource to its exact corresponding match in another system or vocabulary.
A resource _MAY_ have a `skos:exactMatch` predicate where the value is an IRI.
A `skos:prefLabel` predicate _MUST_ have a literal value.
A note that provides additional information about the resource.
A `skos:scopeNote` predicate _MUST_ have a literal value.
Exactly 1 `ssn:implements` _MUST_ exist where the value node is a `tern:Method` or `tern:Procedure`.
Relation from an OperatingRange of a System to an OperatingProperty describing the operating range of the System. This property is used to specify the operating characteristics or properties that define the operating conditions of a system.
A `ssn-system:hasOperatingProperty` predicate _MUST_ have an IRI or blank node value of type `ssn-system:OperatingProperty`.
Relation from a System to a SystemCapability describing the capabilities of the System under certain Conditions. This property is used to specify what a system is capable of doing under specific circumstances.
A `ssn-system:hasSystemCapability` predicate _MUST_ have an IRI or blank node value of type `ssn-system:SystemCapability`.
Relation from a SystemCapability of a System to a SystemProperty describing the capabilities of the System. This property is used to specify the inherent properties or characteristics that describe the capabilities of a system.
A `ssn-system:hasSystemProperty` predicate _MUST_ have an IRI or blank node value of type `ssn-system:SystemProperty`.
Relation between a System and a Calibration, recording that the System is calibrated.
A `tern:System` _MAY_ have an `tern:hasCalibration` predicate where the value node is an IRI of type `tern:Calibration`.
The full name, with authorship and date information if known, of the currently valid (zoological) or accepted (botanical) taxon.
A `tern:Taxon` _MAY_ have a `dwc:acceptedNameUsage` predicate where the value node is a literal with the datatype `xsd:string`.
An identifier for the name usage (documented meaning of the name according to a source) of the currently valid (zoological) or accepted (botanical) taxon.
A `tern:Taxon` _MAY_ have a `dwc:acceptedNameUsageID` predicate where the value node is a literal with the datatype `xsd:string`.
The full scientific name of the class in which the taxon is classified.
A `tern:Taxon` _MAY_ have a `dwc:class` predicate where the value node is a literal with the datatype `xsd:string`.
Part of the name of a cultivar, cultivar group or grex that follows the scientific name.
A `tern:Taxon` _MAY_ have a `dwc:cultivarEpithet` predicate where the value node is a literal with the datatype `xsd:string`.
The full scientific name of the family in which the taxon is classified.
A `tern:Taxon` _MAY_ have a `dwc:family` predicate where the value node is a literal with the datatype `xsd:string`.
The genus part of the scientificName without authorship.
A `tern:Taxon` _MAY_ have a `dwc:genericName` predicate where the value node is a literal with the datatype `xsd:string`.
The full scientific name of the genus in which the taxon is classified.
A `tern:Taxon` _MAY_ have a `dwc:genus` predicate where the value node is a literal with the datatype `xsd:string`.
A list (concatenated and separated) of taxa names terminating at the rank immediately superior to the taxon referenced in the taxon record.
A `tern:Taxon` _MAY_ have a `dwc:higherClassification` predicate where the value node is a literal with the datatype `xsd:string`.
The infrageneric part of a binomial name at ranks above species but below genus.
A `tern:Taxon` _MAY_ have a `dwc:infragenericEpithet` predicate where the value node is a literal with the datatype `xsd:string`.
The name of the lowest or terminal infraspecific epithet of the scientificName, excluding any rank designation.
A `tern:Taxon` _MAY_ have a `dwc:infraspecificEpithet` predicate where the value node is a literal with the datatype `xsd:string`.
The full scientific name of the kingdom in which the taxon is classified.
A `tern:Taxon` _MAY_ have a `dwc:kingdom` predicate where the value node is a literal with the datatype `xsd:string`.
The reference to the source in which the specific taxon concept circumscription is defined or implied. For taxa that result from identifications, a reference to the keys, monographs, experts and other sources should be given.
A `tern:Taxon` _MAY_ have a `dwc:nameAccordingTo` predicate where the value node is a literal with the datatype `xsd:string`.
An identifier for the source in which the specific taxon concept circumscription is defined or implied. See nameAccordingTo.
A `tern:Taxon` _MAY_ have a `dwc:nameAccordingToID` predicate where the value node is a literal with a datatype of `xsd:string`.
A reference for the publication in which the scientificName was originally established under the rules of the associated nomenclaturalCode.
A `tern:Taxon` _MAY_ have a `dwc:namePublishedIn` predicate where the value node is a literal with the datatype `xsd:string`.
An identifier for the publication in which the scientificName was originally established under the rules of the associated nomenclaturalCode.
A `tern:Taxon` _MAY_ have a `dwc:namePublishedInID` where the value node is a literal with the datatype `xsd:string`.
The four-digit year in which the scientificName was published.
A `tern:Taxon` _MAY_ have a `dwc:namePublishedInYear` predicate where the value node is a literal with the datatype `xsd:string`.
The nomenclatural code (or codes in the case of an ambiregnal name) under which the scientificName is constructed.
A `tern:Taxon` _MAY_ have a `dwc:nomenclaturalCode` predicate where the value node is a literal with the datatype `xsd:string`.
The status related to the original publication of the name and its conformance to the relevant rules of nomenclature. It is based essentially on an algorithm according to the business rules of the code. It requires no taxonomic opinion.
A `tern:Taxon` _MAY_ have a `dwc:nomenclaturalStatus` predicate where the value node is a literal with the datatype `xsd:string`.
The full scientific name of the order in which the taxon is classified.
A `tern:Taxon` _MAY_ have a `dwc:order` predicate where the value node is a literal with the datatype `xsd:string`.
The taxon name, with authorship and date information if known, as it originally appeared when first established under the rules of the associated nomenclaturalCode. The basionym (botany) or basonym (bacteriology) of the scientificName or the senior/earlier homonym for replaced names.
A `tern:Taxon` _MAY_ have a `dwc:originalNameUsage` predicate where the value node is a literal with the datatype `xsd:string`.
An identifier for the name usage (documented meaning of the name according to a source) in which the terminal element of the scientificName was originally established under the rules of the associated nomenclaturalCode.
A `tern:Taxon` _MAY_ have a `dwc:originalNameUsageID` predicate where the value node is a literal with the datatype `xsd:string`.
The full name, with authorship and date information if known, of the direct, most proximate higher-rank parent taxon (in a classification) of the most specific element of the scientificName.
A `tern:Taxon` _MAY_ have a `dwc:parentNameUsage` predicate where the value node is a literal with the datatype `xsd:string`.
An identifier for the name usage (documented meaning of the name according to a source) of the direct, most proximate higher-rank parent taxon (in a classification) of the most specific element of the scientificName.
A `tern:Taxon` _MAY_ have a `dwc:parentNameUsageID` predicate where the value node is a literal with the datatype `xsd:string`.
The full scientific name of the phylum or division in which the taxon is classified.
A `tern:Taxon` _MAY_ have a `dwc:phylum` predicate where the value node is a literal with the datatype `xsd:string`.
The full scientific name, with authorship and date information if known. When forming part of an Identification, this should be the name in lowest level taxonomic rank that can be determined. This term should not contain identification qualifications, which should instead be supplied in the IdentificationQualifier term.
A `tern:Taxon` _MAY_ have a `dwc:scientificName` predicate where the value node is a literal with the datatype `xsd:string`.
The authorship information for the scientificName formatted according to the conventions of the applicable nomenclaturalCode.
A `tern:Taxon` _MAY_ have a `dwc:scientificNameAuthorship` predicate where the value node is a literal with the datatype `xsd:string`.
An identifier for the nomenclatural (not taxonomic) details of a scientific name.
A `tern:Taxon _MAY_ have a `dwc:scientificNameID` predicate where the value node is a literal with the datatype `xsd:string`.
The name of the first or species epithet of the scientificName.
A `tern:Taxon` _MAY_ have a `dwc:specificEpithet` predicate where the value node is a literal with the datatype `xsd:string`.
The full scientific name of the subfamily in which the taxon is classified.
A `tern:Taxon` _MAY_ have a `dwc:subfamily` predicate where the value node is a literal with the datatype `xsd:string`.
The full scientific name of the subgenus in which the taxon is classified. Values should include the genus to avoid homonym confusion.
A `tern:Taxon` _MAY_ have a `dwc:subgenus` predicate where the value node is a literal with the datatype `xsd:string`.
An identifier for the taxonomic concept to which the record refers - not for the nomenclatural details of a taxon.
A `tern:Taxon` _MAY_ have a `dwc:taxonConceptID` predicate where the value node is a literal with the datatype `xsd:string`.
A global unique identifier for the taxon (name in a classification).
A `ternTaxon` _MAY_ have a `dwc:taxonID` predicate where the value node is a literal with the datatype `xsd:string`.
The taxonomic rank of the most specific name in the scientificName.
A `tern:Taxon` _MAY_ have a `dwc:taxonRank` predicate where the value node is a literal with the datatype `xsd:string`.
Comments or notes about the taxon or name.
A `tern:Taxon` _MAY_ have a `dwc:taxonRemarks` predicate where the value node is a literal with the datatype `xsd:string`.
The status of the use of the scientificName as a label for a taxon. Requires taxonomic opinion to define the scope of a taxon. Rules of priority then are used to define the taxonomic status of the nomenclature contained in that scope, combined with the experts opinion. It must be linked to a specific taxonomic reference that defines the concept.
A `tern:Taxon` _MAY_ have a `dwc:taxonomicStatus` predicate where the value node is a literal with the datatype `xsd:string`.
The taxonomic rank of the most specific name in the scientificName as it appears in the original record.
A `tern:Taxon` _MAY_ have a `dwc:verbatimTaxonRank` predicate where the value node is a literal with the datatype `xsd:string`.
A `tern:Taxon` _MAY_ have a `dwc:vernacularName` predicate where the value node is a literal with the datatype `xsd:string`.
A `tern:Text` _MUST_ have exactly 1 `rdf:value` predicate where the value node is a literal with the datatype `xsd:string` or `rdf:langString`.
A `tern:Transect` _MUST_ have exactly 1 `tern:featureType` predicate where the value node is an IRI with the value `http://linked.data.gov.au/def/tern-cv/de46fa49-d1c9-4bef-8462-d7ee5174e1e1`.
A `tern:Transect` _MAY_ have a maximum of 1 `geo:hasGeometry` predicate where the value node is a blank node or IRI of type `sf:LineString` or `geo:Geometry`.
A `tern:Transect` _MAY_ have a maximum of 1 `sdo:spatial` predicate where the value node is a blank node or IRI of type `sf:LineString` or `geo:Geometry`.
A `tern:Transect` _MAY_ have a maximum of 1 `tern:transectDirection` where the value node is an IRI or literal.
Relationship to the link:http://www.opengis.net/ont/sf#Point[sf:Point] or geo:Geometry representing the end of a transect.
A `tern:Transect` _MAY_ have a maximum of 1 `tern:transectEndPoint` predicate where the value node is an IRI of type `sf:Point` or `geo:Geometry`.
Relationship to the link:http://www.opengis.net/ont/sf#Point[sf:Point] or geo:Geometry representing the start of a transect.
A `tern:Transect` _MAY_ have a maximum of 1 `tern:transectStartPoint` predicate where the value node is an IRI of type `sf:Point` or `geo:Geometry`.
A `tern:Value` _MAY_ have maximum one `tern:unit` predicate where the value is an IRI.
A `tern:Value` _MUST_ have exactly one `rdf:value` predicate.
This SHACL shape defines constraints for the `tern:maxAltitude` property. It specifies that values of the `tern:maxAltitude` property must be literals of type `xsd:integer`, `xsd:float`, `xsd:double`, or `xsd:decimal`. The status of this shape is experimental, indicating that it might be subject to change in the future.
A `tern:maxAltitude` predicate _MUST_ have a literal value of type `xsd:integer`, `xsd:float`, `xsd:double`, `xsd:decimal`.
This SHACL shape defines constraints for the `tern:minAltitude` property. It specifies that values of the `tern:minAltitude` property must be literals of type `xsd:integer`, `xsd:float`, `xsd:double`, or `xsd:decimal`. The status of this shape is experimental, indicating that it might be subject to change in the future.
A `tern:minAltitude` predicate _MUST_ have a literal value of type `xsd:integer`, `xsd:float`, `xsd:double`, `xsd:decimal`.
The model of the device (e.g., sensor, sampler).
A `sdo:model` predicate _MUST_ have either a literal value or an IRI.
This SHACL shape defines constraints for the `tern:collaborator` property. It specifies that values of the `tern:collaborator` property must be IRIs of type `prov:Agent`. The status of this shape is experimental, indicating that it might be subject to change in the future.
A `tern:collaborator` predicate _MUST_ have an IRI value of type `prov:Agent`.
This SHACL shape defines constraints for the `tern:editor` property. It specifies that values of the `tern:editor` property must be IRIs of type `prov:Agent`. The status of this shape is experimental, indicating that it might be subject to change in the future.
A `tern:editor` predicate _MUST_ have an IRI value of type `prov:Agent`.
This SHACL shape defines constraints for the `tern:environmentDescription` property. It specifies that values of the `tern:environmentDescription` property must be literals with the datatype `xsd:string`. The maximum cardinality of this property is restricted to one. The status of this shape is experimental, indicating that it might be subject to change in the future.
A `tern:environmentDescription` _MUST_ have a literal value with the datatype `xsd:string`.
This SHACL shape defines constraints for the `tern:funder` property. It specifies that values of the `tern:funder` property must be IRIs of type `prov:Agent`. The status of this shape is experimental, indicating that it might be subject to change in the future.
A `tern:funder` predicate _MUST_ have an IRI value of type `prov:Agent`.
This SHACL shape defines constraints for the `tern:producer` property. It specifies that values of the `tern:producer` property must be IRIs of type `prov:Agent`. The status of this shape is experimental, indicating that it might be subject to change in the future.
A `tern:producer` predicate _MUST_ have an IRI value of type `prov:Agent`.
This SHACL shape defines constraints for the `tern:resourceSpecificUsage` property. It specifies that values of the `tern:resourceSpecificUsage` property must be literals with the datatype `xsd:string`. The maximum cardinality of this property is restricted to one. The status of this shape is experimental, indicating that it might be subject to change in the future.
A `tern:resourceSpecificUsage` _MUST_ have a literal value with the datatype `xsd:string`.
This SHACL shape defines constraints for the `tern:supplementalInformation` property. It specifies that values of the `tern:supplementalInformation` property must be literals with the datatype `xsd:string`. The maximum cardinality of this property is restricted to one. The status of this shape is experimental, indicating that it might be subject to change in the future.
A `tern:supplementalInformation` _MUST_ have a literal value with the datatype `xsd:string`.
This SHACL shape defines constraints for the `tern:verticalExtent` property. It specifies that values of the `tern:verticalExtent` property must be IRIs or blank nodes of type `tern:VerticalExtent`. The status of this shape is experimental, indicating that it might be subject to change in the future.
A `tern:verticalExtent` predicate _MUST_ have an IRI or blank node value of type `tern:VerticalExtent`.
A `prov:wasInformedBy` predicate _MUST_ have an IRI value.
At least one (geo:hasGeoemtry, geo:sfWithin) must exist on itself or on a sample in the chain of samples)
At least one geo:hasGeometry must exist.
Has at least 1 spatial indicator alongs its chain of samples
An `Observation` _MUST_ have at least one `sosa:hasFeatureOfInterest` predicate where the value node is an IRI of type `tern:FeatureOfInterest` and its subclasses.
At least one tern:transectStartPoint must exist.
At least one tern:transectEndPoint must exist.
Sample node shape of sosa:hasFeatureOfInterest
At least one geo:sfWithin exists along the chain of sosa:isSampleOf paths.
A `tern:Sample` _MUST_ have at least one `sosa:isSampleOf` or `tern:hasSite` predicate with location information.
This ontology contains a number of Classes and Predicates used by the Prez system
Each Dataset must indicate exactly one bounding box showing the area of Earth it's data is relevant to
At least one keyword for the dataset must be a Concept from the EnvThes vocabulary
UN-GGIM Data Themes vocabulary describes a set of data themes for geospatial data based on the UN-GGIM document
This vocabulary is a slightly reformatted version of the original obtained from https://linkeddataops.adaptcentre.ie/vocabularies/unggim-data-themes. The only changes have been to remove the top-level 'Data Theme' Concept and to add ConceptScheme and Concept elements required for the VocPub profile of SKOS (https://w3id.org/profile/vocpub/spec)
UN-GGIM Data Themes
Airports and airfields are defined by the International Civil Aviation Organisation as defined points or areas on land or water intended to be used either wholly or in part for the arrival, departure and surface movement of aircraft. ICAO uses the term aerodromes. Airports are generally facilities that have commercial passenger and cargo facilities.
Airports and Airfields
Transport Networks are the suite of road, rail, air, cable and water transport routes and their connectivity.
Transport Networks
Land use mapping in Australia is coordinated by the Australian Collaborative Land Use and Management Program (ACLUMP), a consortium of state and national agencies. Mapping is conducted at two scales: national scale and catchment scale. Land use is mapped according to the nationally agreed Australian Land Use and Management (ALUM) Classification, a three-tier hierarchical structure. * National scale land use mapping is produced by ABARES using coarse-scale satellite data (pixel size of 1.1 square kilometres), ABS agricultural statistics and ground control point data for the agricultural land uses and various other digital maps, including the finer resolution catchment scale land use data, for the non-agricultural land uses. National scale (1:2 500 000) land use datasets have been compiled for 1992-93, 1993-94, 1996-97, 1998-99, 2000-01, 2001-02, 2005-06, 2010-11. * Catchment scale land use mapping is produced by the state and territory agencies using land tenure and other types of land use data, fine-scale satellite data and information collected in the field. The operational scale of catchment scale land use mapping varies according to the intensity of land-use activities and landscape context. Mapping ranges from fine scale (1:10 000 to 1:25 000) for irrigated and peri-urban areas to coarser scales for cropping regions (1:100 000) and for the semi-arid and arid pastoral zone (1:250 000). Catchment scale mapping is compiled into a national raster (50m) dataset by ABARES as new datasets are available from the jurisdictions.
Australian Collaborative Land Use and Management Program
Land Cover represent the physical and biological cover of the Earth’s surface. Land Use is the current and future planned management, and modification of the natural environment for different human purposes or economic activities.
Land Cover and Land Use
The geographical boundaries that divide the area of interest for the purposes of an election or referendum held under the Commonwealth Electoral Act, 1918. Australian Electoral boundaries are a collection of legislative, political boundaries sourced from Federal, State and Territory authorities: * Federal electoral boundaries * State electoral boundaries * Local government wards
Australian Electoral Boundaries
Functional Areas are the geographical extent of administrative, legislative, regulatory, electoral, statistical, governance, service delivery and activity management areas.
Functional Areas
The geographical boundaries that divide the area of interest on which the statistics are collected for purposes under the Australian Bureau of Statistics Act, 1975. The Australian Statistical Geography Standard (ASGS) is the Australian Bureau of Statistics' geographical framework. The ASGS brings all the regions used by the ABS to output data under the one umbrella. They are divided into two broad categories: ABS Structures, those regions which are defined and maintained by the ABS. Non-ABS Structures, those regions defined and maintained by other organisations, but for which the ABS supplies data. The ABS Structures are a hierarchy of regions developed for the release of ABS statistical information. Their main components are listed below: Australia State/Territory Statistical Areas Level 4 Statistical Areas Level 3 Statistical Areas Level 2 Statistical Areas Level 1 Mesh blocks
Australian Statistical Geographical Standard Boundaries
The National Catchments is a topologically consistent and hierologically enforced stream flow aggregation of boundaries
Catchment Boundaries
The Water theme covers the extent and conditions of all water features including rivers, lakes and marine features.
Water
The Dynamic Land Cover Dataset is a nationally consistent and thematically comprehensive land cover reference for Australia. Dynamic Land Cover Dataset provides an 8 year synoptic overview of land cover at 250 metre resolution for the Australian continent between April 2000 and April 2008.
Dynamic Land Cover
The Flow Direction Grid is a regular grid of surface flow directions accompanying the GEODATA 9 Second Digital Elevation Model (DEM) Version 3. It ascribes to each DEM point one of eight cardinal directions (E, SE, S, SW, W, NW, N, NE) denoting the direction of surface flow from each grid point to one of its eight immediate neighbours.
Flow Direction Grid
Forests of Australia (2018) is a continental spatial dataset of forest extent, by national forest categories and types, assembled for [Australia's State of the Forests Report 2018](http://www.agriculture.gov.au/abares/forestsaustralia/Pages/SOFR2018/sofr-2018.aspx). It was developed from multiple forest, vegetation and land cover data inputs, including contributions from Australian, state and territory government agencies and external sources. A forest is defined in this dataset as _"An area, incorporating all living and non-living components, that is dominated by trees having usually a single stem and a mature or potentially mature stand height exceeding two metres and with existing or potential crown cover of overstorey strata about equal to or greater than 20 per cent. This includes Australia's diverse native forests and commercial plantations, regardless of age. It is also sufficiently broad to encompass areas of trees that are sometimes described as woodlands"_. The dataset was compiled by the Australian Bureau of Agricultural and Resource Economics and Sciences (ABARES) for the [National Forest Inventory](http://www.agriculture.gov.au/abares/forestsaustralia/Pages/Australia%27s-National-Forest-Inventory.aspx) (NFI), a collaborative partnership between the Australian and state and territory governments. The role of the NFI is to collate, integrate and communicate information on Australia's forests. States and territories agencies collect forest data using independent methods and at varying scales or resolutions. The NFI applies a national classification to state and territory data to allow seamless integration of these datasets. Multiple independent sources of external data are used to fill data gaps and improve the quality of the final dataset. The NFI classifies forests into three national forest categories (Native forest, Commercial plantation, and Other forest) and then into various forest types. Commercial plantations presented in this dataset were sourced from the [National Plantation Inventory](http://www.agriculture.gov.au/abares/forestsaustralia/plantation-inventory-and-statistics) (NPI) spatial dataset (2016), also produced by ABARES. Another dataset produced by ABARES, the [Catchment scale Land Use and Management](http://www.agriculture.gov.au/abares/aclump/Pages/land-use/data-download.aspx) (CLUM) dataset (2016) was used to identify and mask out land uses that are inappropriate to map as forest.
Forests of Australia
The data represent the fractional cover of Photosynthetic Vegetation (PV), Non-Photosynthetic Vegetation (NPV) and Bare Soil (BS).
Fractional Ground Cover
A geographical index or dictionary of the names of cultural and physical features and their associated location in Australia. These names can include approved, unapproved, commonly used, alternate and historical place names.
Gazetteer of Australia
Geographical Names provide orientation and identity to places. They are location identifiers for cultural and physical features of the real world, such as regions, settlements, or any feature of public or historical interest. They are often used as a proxy for other data themes such as Buildings and Settlements.
Geographical Names
Nationally consistent set of groundwater boundaries and properties including aquifer boundaries, geometry, salinity, yield and hydraulic conductivity. The Interim Aquifer Framework has been used to standardise the hydrogeological unit terminology for this dataset.
Groundwater
Nationally consistent set of groundwater bores (including monitoring, irrigation and commercial bores) and associated lithology, construction and hydrostratigraphy logs. The National Aquifer Framework has been used to standardise the hydrogeological unit terminology for this dataset.
Groundwater Bores
Groundwater Dependent Ecosystems (GDE) is ecological and hydrogeological information on known groundwater dependent ecosystems and ecosystems that potentially use groundwater.
Groundwater Dependent Ecosystems (GDE)
These data sets have a spatial resolution of between 2.5-10 m and provide national coverage every quarter. They are primarily operated by Jurisdictions and/or commercial enterprises. There are an increasing number of these sensors available for both satellite and airborne platforms and an ever-expanding range of applications that use them. The data derived from SPOT from 2005 to Present and ALOS from 2009/2010 is identified as the primary data within this data set.
High Spatial Resolution (>2.5-10m) Low Temporal Coverage (>Quarterly)
Orthoimagery is geo-referenced rectified image data of the Earth's surface, from satellite or airborne sensors. Although technically not a theme in its own right, Orthoimagery is included as, when interpreted, it’s a widely-used data source for many other data themes.
Orthoimagery
Hydrological obstructions are man-made features that impact the water network either by obstruction, diversion or storage of water
Hydrological Obstructions
The agreed boundary separating the individual states and territories of Australia and bounded by the maritime boundary. Jurisdictional boundaries are a collection of legislative, regulatory, political and general administrative boundaries sourced from Federal, State and Territory authorities. * National boundary * State/Territory boundary * Local government areas * Parishes * Regions * Suburbs
Jurisdictional Boundaries
The Land Parcel dataset is a data aggregation sourced from the jurisdictions which depicts national and accurate land and strata based information including parcels representing easements, roads, crossing, rail and water.
Land Parcel Boundaries
Land Parcels are areas of land or more generally of the Earth’s surface (land and/or water) under common rights (such as ownership or easements), claims (such as minerals or indigenous land) or use. This theme can include individual fields and cadastral parcels.
Land Parcels
Aligns land tenure classifications to cadastral parcel identifiers, requiring the use of the CadLite® dataset to visualise or spatially analyse the Land Tenure dataset.
Land Tenure
These data sets have a spatial resolution of no closer than 80 m and are collected on a close to weekly basis. The AVHRR and MODIS sensors service most Australian needs for low resolution optical data. Data is derived from MODIS, AVHRR, VIIRS missions and includes the following spectral ranges, VIS, NIR, SWIR.
Low Resolution (>80m) High Temporal Coverage (>weekly)
The delineation of the baseline from which the outer limits of the various maritime zones are measured as set out in the UN Convention of the Law of the Sea (UNCLOS) and Seas and Submerged Lands Act, 1973. * Territorial Sea Baseline * Territorial Sea (12 nautical mile limit) * Contiguous Zone (24 nautical mile limit) * Exclusive Economic Zone (200 nautical mile limit) * Australian Fishing Zone
Maritime Jurisdiction Boundaries
These data sets have a spatial resolution between 10–80 m and are collected on a weekly to monthly basis. They are the most commonly used category of imagery data. For several decades the Landsat series of satellites have provided the majority of medium resolution optical imagery for operational programs in Australia. Data is derived from MSS, TM, ETM+, Aster, OLI, Sentinel-2 MSI missions and includes the following spectral ranges, VIS, NIR, SWIR, PAN. Medium resolution optical sensors have traditionally been operated for public good, although the number of commercial sensors is increasing.
Medium Resolution (>10-80m) Medium Temporal
Crossings are structures built to facilitate the movement over, under or through another physical feature. In the Transport Theme, crossings include bridges, tunnels, fords, culverts and boardwalks.
National Crossings
The one arc second (~30m) DEMs provide a nationally consistent, medium resolution dataset essential for national and regional scale analysis using the best available source data. It comprises data derived from the Shuttle Radar Topography Mission (SRTM) and LiDAR where available. Bathymetry is the study and mapping of sea floor topography. It involves obtaining measurements of the depth of the ocean and is equivalent to mapping the topography on land. Such measurements can be made using: * Multibeam (swath) echosounders * Airborne laser measurements (LADS) * Derived depths from satellite remote sensing * Singlebeam echosounders
National Digital Elevation and Depth Model
The Elevation and Depth theme describes the surface of the Earth both on land and under a body of water, relative to a vertical datum.
Elevation and Depth
The CORSnet is a network of permanent global navigation satellite systems (GNSS) continuously operating reference stations (CORS) providing DGPS, RTK and RINEX data 24/7 to enable users to achieve sub-metre positional accuracy. Expanding the CORSnet network of global navigation satellite systems (GNSS) continuously operating reference stations (CORS) providing DGPS, RTK and RINEX data 24/7 to enable users to achieve sub-metre positional accuracy.
National Geospatial Reference System
The Global Geodetic Reference Frame is the framework which allows users to precisely determine and express locations on the Earth, as well as to quantify changes of the Earth in space and time. It is not a data theme in the sense of the other themes, but it is a prerequisite for the accurate collection, integration, and use of all other geospatial data.
Global Geodetic Reference Frame
National Topographic data – principally referred to in this document as Geodata Topo 250K Series 3 – is a nationally consistent representation of natural and built environment features on the earth's surface for Australia excluding external territories. The data is thematically ordered and includes the following datasets containing up to 92 different feature classes: * Culture * Drainage * Elevation * Framework * Habitation * Transport Utility Vegetation
National Topographic Data
The NVIS framework was developed to enable the compilation of a nationally consistent vegetation dataset from data collected by states and territories. It provides a comprehensive means of describing and representing vegetation information based on establishing relationships between structural and floristic data. The NVIS Information Hierarchy is a system for describing the structural and floristic patterns of groups of plants in the landscape. Collectively, the different levels in the classification provide a description of vegetation that can be directly related to precise spatial areas as a vegetation map.
National Vegetation Information System
Mapping and spatial information play a key role in navigating native title. Applications, Indigenous land use agreements, and determinations of native title are described geographically and mapped, similar to other interests in land and/or water. Mapping enables people to gain an understanding of where these matters are in relation to other things, such as towns, roads, farms, mining tenements and local government areas. Together with other information, maps are also used to notify interested parties about native title matters, enabling them to become involved in the process.
Native Title Boundaries
Location, height and description of infrastructure, markers or other devices on land which may aid travellers in determining their position or safe course.
Navigation Aids and Obstacles
Railways are transportation systems using one or more rails to carry freight or passengers. Railway stations are recognised stopping places where goods, vehicles or passengers may be transferred from one form of transport to the rail network, and vice versa. Railway stations can also include what are now called “intermodal transfer stations”.
Railways and Railway Stations
Roads are defined paths for the transfer of goods or movement of vehicles, people or animals. Unlike Railways, Roads do not have fixed tracks. The Roads dataset includes cycleways, foot tracks and ferry routes.
Roads
The Surface Hydrology dataset provides a set of related feature classes to be used as the basis of the production of consistent hydrological information. This dataset contains a geometric representation of the (major) surface water features of Australia. Primarily, these are natural surface hydrology features, but the dataset also contains some artificial features (notably reservoirs, canals and other hydrographic features).
Surface Hydrology
Validates the captured address and makes it possible to verify a physical address and locate its position.
The Geocoded National Address File
An Address is a structured label, usually containing a property number, a street name and a locality name. It’s used to identify a plot of land, a building or part of a building, or some other construction, together with coordinates indicating their geographic position. Addresses are often used as a proxy for other data themes such as Land Parcels.
Addresses
Traffic control devices are used to control, calm, slow or impede the movement of traffic. They include roundabouts, gates, stock grids, level crossings, tolls and barriers
Traffic Control Devices
An orthophoto is an aerial photograph geometrically corrected (“orthorectified”) to ensure the scale is uniform: the photo has the same lack of distortion as a map. Unlike an uncorrected aerial photograph, an orthophotograph can be used to measure true distances, because it is an accurate representation of the Earth’s surface, having been adjusted for topographic relief, lens distortion, and camera tilt. The image has been corrected to ensure that horizontal scale is constant These data sets have a spatial resolution of 2.5m or closer and are primarily operated by Jurisdictions and/or commercial enterprises. There are an increasing number of these sensors available for both satellite and airborne platforms and an ever-expanding range of applications that use them.
Very High Resolution (<2.5 m) Very Low Temporal Coverage (>annual)
A Building refers to any roofed structure permanently constructed or erected on its site, for the protection of humans, animals, things, or the production of economic goods. Settlements are collections of buildings and associated features where a community carries out socio-economic activities.
Buildings and Settlements
Geology is the composition and properties of geologic materials (rocks and sediments) underground and outcropping at the Earth’s surface. It includes bedrock, aquifers, geomorphology for land and marine environments, mineral resources and overlying soils. Soils are the upper part of the Earth’s crust, formed by mineral particles, organic matter, water, air, and living organisms.
Geology and Soils
The Physical Infrastructure theme includes industrial & utility facilities, and the service delivery facilities associated with administrative & social governmental services such as public administrations, utilities, transport, civil protection, schools and hospitals.
Physical Infrastructure
The Population Distribution theme covers the geographical distribution of people, including population characteristics.
Population Distribution
This model is a Semantic Web data model used for address information. It caters specifically for Australian & New Zealand's address modelling needs.
This ontology was made for the Queensland Department of Resources, Spatial Information unit to assist with future Address database design. It is informed by the ICSM's Addressing 2035: Addressing Reform and Innovation for Australia and New Zealand, published in late 2021 and is based primarilty on the ISO19160-1 Addressing Part 1: Conceptual model with additional elements from a small set of well-regarded Semantic Web models such as GeoSPARQL and SKOS. It is also informed by the relational databalse model used for the G-NAF, Australia's Geocoded National Address File, and CSIRO work in 2018 to characterise the GNAF in Sematic Web form, the ontlogy for which is online at https:linked.data.gov.au/def/gnaf.
Address Model
(c) The State of Queensland (Department of Resources) 2020-2023
Derived from ISO19160-1's AddressLifecycle class
Represents the different lifecycle stages of an Address
# An Address with two Lifecycle Stages indicated: # one current and one past ex:addr-1 a addr:Address ; addr:hasLifeCycleStage [ # this Stage has ceased time:hasTime [ time:hasBeginning [ time:inXSDDate "1982-02-10"^^xsd:date ] ; time:hasEnd [ time:inXSDDate "1982-05-11"^^xsd:date ] ; ] ; addr:hasLifeCycleStageType addrls:proposed ; ] , [ # this Stage is still in effect - no hasEnd given time:hasTime [ time:hasBeginning [ time:inXSDDate "1982-05-11"^^xsd:date ] ; ] ; addr:hasLifeCycleStageType addrls:current ; ] , . # The Address Lifecycle Stage 'proposed' # from the Address Lifecycle Stage Types vocabulary # indicating only some properties addrls:proposed a skos:Concept ; ... skos:prefLabel "Proposed" ; .
Address Lifecycle Stage
An Address Lifecycle Stage's type should be indicated with values from a controlled vocabulary - a code list. A SKOS vocabulary of Address Lifecycle Stages is suplied with this ontology. In this model, these Lifecycle Stages are defined for use with Addresses only, not also Address Components, as per ISO19160-1.
Code that specifies the kind of Address Lifecycle Stage
# An Address with a Lifecycle Stages indicated # which then indicates its type ex:addr-1 a addr:Address ; addr:hasLifeCycleStage [ ... addr:hasLifeCycleStageType addrls:proposed ; ] ; ...
Address Lifecycle Stage Type
An Address Address Lifecycle Stage's type should be indicated with values from a controlled vocabulary - a code list. A SKOS vocabulary of Address Lifecycle Stage Types is suplied with this ontology.
Derived from ISO19160-1's object relations
Indicates an Address has been allocated for an Addressable Object
# the addr:AddressableObject, some-addressable-object, # indicates an address with addr:hasAddress <some-addressable-object> a addr:AddressableObject ; addr:hasAddress ex:addr-1 ; . ex:addr-1 a addr:Address ; .
has address
Derived from ISO19160-1's AddressableObject class and its associated codelist of subtypes
An object that is unambiguously determined by an address. Examples of types of AddressableObjects are a building, a dwelling or a land parcel.
# ex:parcel-x is inferred to be an Addressable object # due to the property addr:hasAddress indicated for it ex:parcel-x addr:hasAddress ex:addr-1 . # this object is declared to be an Addressable Object <http://example.com/building/y> a addr:AddressableObject ; rdfs:label "Building Y" ; . # ex:admin-area-z is inferred to be an Addressable Object # due to the property addr:isAddressFor indicating it ex:addre-2 addr:isAddressFor ex:admin-area-z .
Addressable Object
Judgement as to what makes for a permissable AddressableObject rests with the implementer. This model's technical requirements are only that the object is a legal `geo:Feature` object, thus implementers may make Addressable Objects of almost anything.
Derived from ISO19160-1's Address class
The Address class represents structured information that allows unambiguous determination of an object for the purposes of identification and location
ex:addr-1 a addr:Address ; addr:isAddressFor <some-external-object> ; addr:hasAddressComponent [ addr:hasValue 20 ; dcterms:type addrct:streetNumber ; ] , [ addr:hasValue "Oxford" ; dcterms:type addrct:thoroughfareName ; ] , [ addr:hasValue strt:Place ; addr:hasValueText "Place" ; dcterms:type addct:StreetType ; ] , [ addr:hasValue <LGA2021/1234> ; addr:hasValueText "Shorncliffe" ; dcterms:type addrct:localityName ; ] , [ addr:hasValue <STE2021/6> ; addr:hasValueText "Queensland" ; dcterms:type addct:StateOrTerritory ; ] , [ addr:hasValue <AUS2021/AUS> ; addr:hasValueText "Australia" ; dcterms:type addct:Nation ; ] ; .
Address
Indicates an Address Component of an Address
# an Address has an Address Component, a street number, indicated ex:addr-1 a addr:Address ; addr:hasAddressComponent [ addr:hasValue 20 ; dcterms:type addrct:streetNumber ; ] , ...
has address component
Derived from ISO19160-1's AddressComponent class
A component that is a constituent part of an address
ex:addr-1 a addr:Address ; addr:hasAddressComponent [ # a simple numerical literal - street number addr:hasValue 20 ; dcterms:type addrct:streetNumber ; ] , [ # a simple literal - street name addr:hasValue "Oxford" ; dcterms:type addrct:thoroughfareName ; ] , [ # complex object - a Locality addr:hasValue <http://example.com/lga/1234> ; # textual value of complex object addr:hasValueText "Shorncliffe" ; dcterms:type addrct:localityName ; ] , ...
Address Component
Address Components can be literals - numbers, words etc. - or complex ojects - Localities, districtes etc. If the Address Component is a complex object, a textual representation of it must be provided when a textual rendering of all of an Addresses' component are required, for example for letter printing. Complex objects are preferred for use over literals when the object referred to has independent identity. Ordering of Address Components, for example for letter printing, is not fixed within this model but should be implemented with a positioning preference system utilising the Address Component's `dcterms:type` values which should come from a controlled vocabulary of Address Component Type values.
Indicates an Addresses Component's type
# an Address has an Address Component with its type, # street number, indicated ex:addr-1 a addr:Address ; addr:hasAddressComponent [ addr:hasValue 20 ; dcterms:type addrct:streetNumber ; ] , ...
has address component type
Code that specifies the kind of address component
ex:addr-1 a addr:Address ; addr:hasAddressComponent [ # "StreetNumber" type addr:hasValue 20 ; dcterms:type addrct:streetNumber ; ] , [ # "StreetName" type addr:hasValue "Oxford" ; dcterms:type addrct:thoroughfareName ; ] , [ # "Locality" type addr:hasValue <http://example.com/lga/1234> ; # textual value of complex object addr:hasValueText "Shorncliffe" ; dcterms:type addrct:localityName ; ] , ...
Address Component Type
An Address Component's type should be indicated with values from a controlled vocabulary - a code list. A SKOS vocabulary of Address Component Types is suplied with this ontology.
Derived from ISO19160-1's AddressPosition class and properties
Indicates an Address Role for an Address
# An Address with two roles ex:addr-1 a addr:Address ; addr:hasAddressRole ex:emergencyAccess , buildingAccessPoint ; ...
has address role
Derived from ISO19160-1's AddressPosition & AddressPositionType classes
AddressRole represents a task for which this Address may be used
Address Role
ISO19160-1 does not contain an `AddressRole` class but instead an `AddressPosition` class with positioning and role properties. This Standard make role a direct property of `Address` instead and provides for a positional qualifier (qualified against the position of the `AddressableObject`) instead to allow whole addresses to carry role tasking.
Derived from the G-NAF's expression of Address position
Indicates a refined, that is a very accurate or specific, geometry, usually a point, for an Address qualified by the Geocode Type - how it was generated.
# An Address with a geocode and a role ex:addr-1 a addr:Address ; addr:hasGeocode [ dcterms:type geocodeType:DF ; # Driveway Frontage geo:hasGeometry "POINT (152.01 -35.03)"^^geo:wktLiteral ; ] ; addre:hasRole addr:buildingAccessPoint ; ...
has geocode
This property, along with hasRole, allows multiple Addresses with different locations to be allocated to Addressable Objects and for those addresses to be used for different purposes. The location indicated by this property should be within/on/next to the location of the Addressable Object this Address is for, within some acceptable tolerance.
Derived from ISO19160-1's AddressComponent object's properties
Indicates the value of an Address Component
ex:addr-1 a addr:Address ; addr:hasAddressComponent [ # "StreetNumber" type addr:hasValue 20 ; addr:hasComponentType addrct:streetNumber ; ] , [ # "StreetName" type addr:hasValue "Oxford" ; addr:hasComponentType addrct:thoroughfareName ; ] , [ # "Locality" type addr:hasValue <http://example.com/lga/1234> ; # textual value of complex object addr:hasValueText "Shorncliffe" ; addr:hasComponentType addrct:locality ; ] , ...
has value text
This property is to be used to represent the textual value of Address Components that are literals and also complex objects. For a literal, the same value will be present for hasValue and hasValueText, e.g. a street number of 20 or a property name of 'Bonnie Doon', however for a complex object, e.g. the locality <http://example.com/lga/1234>, a textual representation of it must be selected. Likely a simple name for the object will do, i.e. a Locality name or a Street Locality name.
Indicates an Addressable Object that an Address is allocated to
# the Address ex:addr-1 is allocated to # some-addressable-object ex:addr-1 a addr:Address ; addr:isAddressFor <some-addressable-object> ; .
is address for
Indicates an Addresses' Lifecycle Stage
# An Address with two Lifecycle Stages indicated: # one current and one past ex:addr-1 a addr:Address ; addr:hasLifeCycleStage [ # this Stage has ceased time:hasTime [ time:hasBeginning [ time:inXSDDate "1982-02-10"^^xsd:date ] ; time:hasEnd [ time:inXSDDate "1982-05-11"^^xsd:date ] ; ] ; dcterms:type addrls:proposed ; ] , [ # this Stage is still in effect - no hasEnd given time:hasTime [ time:hasBeginning [ time:inXSDDate "1982-05-11"^^xsd:date ] ; ] ; dcterms:type addrls:current ; ] , .
has lifecycle stage
This vocabulary allows multi-dimensional data, such as statistics, to be published in RDF. It is based on the core information model from SDMX (and thus also DDI).
Vocabulary for multi-dimensional (e.g. statistical) data publishing
An alternative to qb:componentProperty which makes explicit that the component is a attribute
The class of components which represent attributes of observations in the cube, e.g. unit of measurement
indicates a ComponentProperty (i.e. attribute/dimension) expected on a DataSet, or a dimension fixed in a SliceKey
gives the code list associated with a CodedProperty
Superclass of all coded ComponentProperties
Represents a generalized hierarchy of concepts which can be used for coding. The hierarchy is defined by one or more roots together with a property which relates concepts in the hierarchy to thier child concept . The same concepts may be members of multiple hierarchies provided that different qb:parentChildProperty values are used for each hierarchy.
indicates a component specification which is included in the structure of the dataset
Defines the structure of a DataSet or slice
Used to define properties of a component (attribute, dimension etc) which are specific to its usage in a DSD.
Indicates the level at which the component property should be attached, this might an qb:DataSet, qb:Slice or qb:Observation, or a qb:MeasureProperty.
Indicates whether a component property is required (true) or optional (false) in the context of a DSD. Only applicable to components correspond to an attribute. Defaults to false (optional).
gives the concept which is being measured or indicated by a ComponentProperty
Abstract super-property of all properties representing dimensions, attributes or measures
indicates the data set of which this observation is a part
A single observation in the cube, may have one or more associated measured values
Represents a collection of observations, possibly organized into various slices, conforming to some common dimensional structure.
An alternative to qb:componentProperty which makes explicit that the component is a dimension
The class of components which represent the dimensions of the cube
Specifies a root of the hierarchy. A hierarchy may have multiple roots but must have at least one.
An alternative to qb:componentProperty which makes explicit that the component is a measure
The class of components which represent the measured value of the phenomenon being observed
An alternative to qb:componentProperty which makes explicit that the component is a measure dimension
Generic measure dimension, the value of this dimension indicates which measure (from the set of measures in the DSD) is being given by the obsValue (or other primary measure)
indicates a observation contained within this slice of the data set
A, possibly arbitrary, group of observations.
indicates a priority order for the components of sets with this structure, used to guide presentations - lower order numbers come before higher numbers, un-numbered components come last
Specifies a property which relates a parent concept in the hierarchy to a child concept.
Indicates a subset of a DataSet defined by fixing a subset of the dimensional values
Denotes a subset of a DataSet defined by fixing a subset of the dimensional values, component properties on the Slice
Indicates a group of observations. The domain of this property is left open so that a group may be attached to different resources and need not be restricted to a single DataSet
indicates a slice key which is used for slices in this dataset
Denotes a subset of the component properties of a DataSet which are fixed in the corresponding slices
indicates the sub-key corresponding to this slice
indicates the structure to which this data set conforms
Abstract superclass for everything that can have attributes and dimensions
Abstract class of things which reference one or more ComponentProperties
The property that identifies the version IRI of an ontology.
The annotation property that provides version information for an ontology or another OWL construct.
The property that is used for importing other ontologies into a given ontology.
The class of annotated axioms for which the RDF serialization consists of an annotated subject, predicate and object.
The annotation property that indicates that a given entity has been deprecated.
The property that determines that two given individuals are equal.
The class of inverse-functional properties.
The property that determines that two given properties are inverse.
The property that determines that two given properties are equivalent.
The property that determines that two given classes are disjoint.
The property that determines that two given classes are equivalent, and that is used to specify datatype definitions.
The property that determines the collection of classes or data ranges that build a union.
The property that determines the cardinality of an exact cardinality restriction.
The property that determines the property that a property restriction refers to.
The annotation property that indicates that a given ontology is backward compatible with another ontology.
The annotation property that indicates that a given ontology is incompatible with another ontology.
The annotation property that indicates the predecessor ontology of a given ontology.
The property that determines the class that a universal property restriction refers to.
The property that determines the cardinality of a maximum cardinality restriction.
The property that determines the cardinality of a minimum cardinality restriction.
The property that determines the cardinality of a minimum qualified cardinality restriction.
The property that determines the class that a qualified object cardinality restriction refers to.
The property that determines the cardinality of an exact qualified cardinality restriction.
The property that determines the cardinality of a maximum qualified cardinality restriction.
The property that determines the data range that a qualified data cardinality restriction refers to.
The property that determines the individual that a has-value restriction refers to.
This ontology partially describes the built-in classes and properties that together form the basis of the RDF/XML syntax of OWL 2. The content of this ontology is based on Tables 6.1 and 6.2 in Section 6.4 of the OWL 2 RDF-Based Semantics specification, available at http://www.w3.org/TR/owl2-rdf-based-semantics/. Please note that those tables do not include the different annotations (labels, comments and rdfs:isDefinedBy links) used in this file. Also note that the descriptions provided in this ontology do not provide a complete and correct formal description of either the syntax or the semantics of the introduced terms (please see the OWL 2 recommendations for the complete and normative specifications). Furthermore, the information provided by this ontology may be misleading if not used with care. This ontology SHOULD NOT be imported into OWL ontologies. Importing this file into an OWL 2 DL ontology will cause it to become an OWL 2 Full ontology and may have other, unexpected, consequences.
The object property that relates every two individuals.
The property that determines the collection of classes or data ranges that build an intersection.
The class of collections of pairwise different individuals.
The class of collections of pairwise disjoint classes.
The class of collections of pairwise disjoint properties.
The class of annotated annotations for which the RDF serialization consists of an annotated subject, predicate and object.
The class of OWL data ranges, which are special kinds of datatypes. Note: The use of the IRI :DataRange has been deprecated as of OWL 2. The IRI rdfs:Datatype SHOULD be used instead.
The class of negative property assertions.
The property that determines the predicate of an annotated axiom or annotated annotation.
The property that determines the subject of an annotated axiom or annotated annotation.
The property that determines the object of an annotated axiom or annotated annotation.
The property that determines the predicate of a negative property assertion.
The data property that does not relate any individual to any data value.
The object property that does not relate any two individuals.
The property that determines that a given class is the complement of another class.
The property that determines that a given data range is the complement of another data range with respect to the data domain.
The property that determines that two given individuals are different.
The property that determines that a given class is equivalent to the disjoint union of a collection of other classes.
The property that determines the collection of pairwise different individuals in a :AllDifferent axiom.
The property that determines the collection of properties that jointly build a key.
The property that determines the property that a self restriction refers to.
The property that determines the collection of members in either a :AllDifferent, :AllDisjointClasses or :AllDisjointProperties axiom.
The property that determines the datatype that a datatype restriction refers to.
The property that determines the n-tuple of properties that a property restriction on an n-ary data range refers to.
The property that determines the collection of individuals or data values that build an enumeration.
The property that determines the n-tuple of properties that build a sub property chain of a given property.
The property that determines that two given properties are disjoint.
The property that determines the class that an existential property restriction refers to.
The property that determines the subject of a negative property assertion.
The property that determines the object of a negative object property assertion.
The property that determines the value of a negative data property assertion.
The data property that relates every individual to every data value.
The property that determines the collection of facet-value pairs that define a datatype restriction.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0c428cb8-25fe-5d09-a361-4164d8b15571>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Cat coat colour controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Cat coat colour controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0c428cb8-25fe-5d09-a361-4164d8b15571> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'0c428cb8-25fe-5d09-a361-4164d8b15571'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0c428cb8-25fe-5d09-a361-4164d8b15571> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/97c64ff0-455c-4e74-ba81-2aeb4adf042f>`. `<https://linked.data.gov.au/def/nrm/97c64ff0-455c-4e74-ba81-2aeb4adf042f>` is the IRI for "Transects Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/97c64ff0-455c-4e74-ba81-2aeb4adf042f`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0c428cb8-25fe-5d09-a361-4164d8b15571>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0c428cb8-25fe-5d09-a361-4164d8b15571>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/0c428cb8-25fe-5d09-a361-4164d8b15571>`. `<https://linked.data.gov.au/def/nrm/0c428cb8-25fe-5d09-a361-4164d8b15571>` is the IRI for "Cat coat colour".
The value of `tern:vocabulary` _MUST_ match the pattern `0c428cb8-25fe-5d09-a361-4164d8b15571$`.
The result _MUST_ not be a negative value.
If value is not free input, the value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the target species types controlled vocabulary.
If value is not free input, the value of `rdf:value` _MUST_ exist in the target species types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/26f843a5-e1ed-46da-b22b-053e567e3227> ; sosa:hasResult ?this . ?this a tern:IRI . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/ff157253-6923-5816-ac05-312dc32cd903>`. `<https://linked.data.gov.au/def/nrm/ff157253-6923-5816-ac05-312dc32cd903>` is the IRI for "Pest species types".
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/44c5567d-3437-4e89-b0b7-caefc07bb16c>`. `<https://linked.data.gov.au/def/nrm/44c5567d-3437-4e89-b0b7-caefc07bb16c>` is the IRI for "Vantage Point Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/44c5567d-3437-4e89-b0b7-caefc07bb16c`.
SHACL validator for the BDR Project Model
BDR Project Model Validator
Checks that projects are associated with agents
If a Project indicate a qualified association, the indicated object must further indicate an Agent (Person or Organisation) with the prov:agent predicate
If a Project is indicated as having generated something, that thing must be a tern:Dataset
If a Project is indicated as having a part, the other thing must also be a Project
TERN's ecologists have determined the feature type is _plant occurrence_ or _fire disturbance_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/b311c0d3-4a1a-4932-a39c-f5cdc1afa611[`plant occurrence`] or http://linked.data.gov.au/def/tern-cv/b293a07e-a1ff-4a4e-9af9-922057d5d742[`fire disturbance`].
Observations following the Fire Severity Module are made in the context of a site visit.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/91a54c7c-48ff-402d-a761-ed4fd4ad4a4b>`. `<https://linked.data.gov.au/def/nrm/91a54c7c-48ff-402d-a761-ed4fd4ad4a4b>` is the IRI for "Fire Severity Module".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/91a54c7c-48ff-402d-a761-ed4fd4ad4a4b`.
TERN's ecologists have determined the feature type is _land surface_ or _fire disturbance_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/8282fb22-4135-415c-8ca2-317860d102fb[`land surface`] or http://linked.data.gov.au/def/tern-cv/b293a07e-a1ff-4a4e-9af9-922057d5d742[`fire disturbance`].
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the fractional cover types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the fractional cover types controlled vocabulary.
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/51d1a677-0688-57b3-91c7-6f1e3beee188>`. `<https://linked.data.gov.au/def/nrm/51d1a677-0688-57b3-91c7-6f1e3beee188>` is the IRI for "fractional cover types".
TERN's ecologists have determined the feature type is _plant community_ or _fire disturbance_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/ea3a4c64-dac3-4660-809a-8ad5ced8997b[`plant community`] or http://linked.data.gov.au/def/tern-cv/b293a07e-a1ff-4a4e-9af9-922057d5d742[`fire disturbance`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3a2b344c-07b5-4536-8db3-06b73bc0e263>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3a2b344c-07b5-4536-8db3-06b73bc0e263>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3a2b344c-07b5-4536-8db3-06b73bc0e263> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3a2b344c-07b5-4536-8db3-06b73bc0e263>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/61754220-443e-4c02-936c-d1b50e86f7d7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Substrate burn extent types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Substrate burn extent types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/61754220-443e-4c02-936c-d1b50e86f7d7> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'78dda800-193d-5b0e-a18b-f54ad942aa51'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/61754220-443e-4c02-936c-d1b50e86f7d7> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/61754220-443e-4c02-936c-d1b50e86f7d7>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/61754220-443e-4c02-936c-d1b50e86f7d7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/78dda800-193d-5b0e-a18b-f54ad942aa51>`. `<https://linked.data.gov.au/def/nrm/78dda800-193d-5b0e-a18b-f54ad942aa51>` is the IRI for "Substrate burn extent types".
The value of `tern:vocabulary` _MUST_ match the pattern `78dda800-193d-5b0e-a18b-f54ad942aa51$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/58e6dc3c-647d-5208-a80a-9c48d9112293>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/58e6dc3c-647d-5208-a80a-9c48d9112293> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/58e6dc3c-647d-5208-a80a-9c48d9112293> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/58e6dc3c-647d-5208-a80a-9c48d9112293>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/58e6dc3c-647d-5208-a80a-9c48d9112293>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
SHACL validator for the BDR Submission Manifest Model
BDR Submission Manifest Model Validator
A Submission Manifest must have at least one Resource Descriptor indicated by hasResource
Each Resource Descriptor must have at least one literal artifact indicated with prof:hasArtifact
Each Resource Descriptor must have exactly one role IRI indicated with prof:hasRole
Each role indicated for a Resource Descriptor a member of the Submission Manifest Model Resource Roles Vocabulary, indicated with the skos:inScheme predicate for the role Concept
This model validator was made for NSW spatial Services, July 2026.
This validator is a Shapes Constraint Language (SHACL) resource that can be used to check the conformance of RDF data to the ANZ ICSM Address Model with extensions for the NSW
Each NSW Address must indicate an Address Part with the ASGS IRI for the NSW
1.1 Minor addition - license 1.0 First version
SHACL validator for catalogues used by the Biodiversity Data Repository
BDR Catalogues Validator
Checks all the properties of the Data Catalog class
Requirement D-created: Each catalogue MUST have exactly one created date indicated using the schema:dateCreated predicate with a literal value of either xsd:date, xsd:dateTime or xsd:dateTimeStamp type
Each catalogue MUST have one and description which is to be a text literal, indicated using the schema:description predicate
Requirement D-modified: Each catalogue MUST have exactly one created date indicated using the schema:dateModified predicate with a literal value of either xsd:date, xsd:dateTime or xsd:dateTimeStamp type
Each catalogue MUST have one and only one name which is to be a text literal, indicated using the schema:name predicate
The parts of this Catalogue must be of a known class
An entry that is seen as having a reasonable measure of stability, may be used to mark the full adoption of a previously 'experimental' entry.
stable
reg-status
1.0 - 2018-06 - as per Registry Ontology original
1.1 - 2020-06 - altered structure & metadata, not content, to conform to Vocab Publication Profile
1.2 - 2021-11 - changes IRI to reg-statuses; added unstable
2.0 - 2023-01 - addition of Concepts addition & original, as per updated Registry Item status codes
This vocabulary is a re-published and only marginally changed version of the Registry Ontology's (http://epimorphics.com/public/vocabulary/Registry.html) *Status* vocabulary (online in RDF: http://purl.org/linked-data/registry). The only real change to content has been the addition of the term `unstable`. This re-publication has been performed to allow the IRIs of each vocab term (skos:Concept) to resolve to both human-readable and machine-readable forms of content (HTML and RDF), using HTTP content negotiation. Note that just like the original form of this vocabulary, while it is a SKOS vocabulary implemented as a single skos:ConceptScheme, it is also an OWL Ontology and that each *Status* is both a skos:Concept and a reg:Status individual.
Originally published by Epimorphics build on the Registry Ontology statuses; adopted and adapted by the AGLDWG
Registry Status Vocabulary
(c) Commonwealth of Australia 2021
provisional
An entry that has been accepted into the register temporarily and may be subject to change or withdrawal.
experimental
The item's status is stable and was supplied to the registry after initial creation.
addition
Open set of status code for entries in a register
An entry that has been accepted into the register and is deemed fit for use.
valid
An entry which has been invalidated due to serious flaws, distinct from retrirement.
invalid
An entry that should not be visible in the default register listing.
notAccepted
A reserved entry allocated for some as yet undetermined future use.
reserved
withdrawn
An entry that has been withdrawn from use.
retired
An entry that has been Retired or Superseded or has become Unstable and is no longer to be used.
deprecated
A proposed entry which is not yet approved for use for use.
submitted
replaced
An entry that has been replaced by a new alternative which should be used instead.
superseded
An entry that is not seen as having a reasonable measure of stability. This status is expected to be allocated to entries that were once Stable but have become Unstable, due to a management or technical mishap, rather than being allocated to resources before they become Stable. Those resources should be allocated Experimental.
An entry that has been accepted for use and is visible in the default register listing. Includes entries that have seen been retired or superseded.
accepted
An RDF file that describes and links to a set of resources that can be loaded into an RDF database for the Prez system to provide access to
This ontology describes a formulation of a content manifest for catalogues of RDF data to be loaded into instances of the PRez tool
A catalogue of reference Semantic Web vocabularies used by KurrawongAI
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/88068941-4dc9-4b44-bcfe-5eeeb3ba1a21>`. # `<https://linked.data.gov.au/def/nrm/88068941-4dc9-4b44-bcfe-5eeeb3ba1a21>` is the IRI for "Enhanced Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/88068941-4dc9-4b44-bcfe-5eeeb3ba1a21`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b3dd4df5-589b-476e-8e9e-0af6a7155759>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the soil coarse fragments abundance types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the soil coarse fragments abundance types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/b3dd4df5-589b-476e-8e9e-0af6a7155759> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'bec608c4-3a66-4630-b666-cabb666ac8d2'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/b3dd4df5-589b-476e-8e9e-0af6a7155759> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b3dd4df5-589b-476e-8e9e-0af6a7155759>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b3dd4df5-589b-476e-8e9e-0af6a7155759>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/bec608c4-3a66-4630-b666-cabb666ac8d2>`. `<https://linked.data.gov.au/def/nrm/bec608c4-3a66-4630-b666-cabb666ac8d2>` is the IRI for "soil coarse fragments abundance types".
The value of `tern:vocabulary` _MUST_ match the pattern `bec608c4-3a66-4630-b666-cabb666ac8d2$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/4062f093-424b-441e-86fc-648d820ae1fb>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the soil lithology types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the soil lithology types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/4062f093-424b-441e-86fc-648d820ae1fb> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'1d50eb79-685f-45ea-84b4-627154eddede'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/4062f093-424b-441e-86fc-648d820ae1fb> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/4062f093-424b-441e-86fc-648d820ae1fb>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/4062f093-424b-441e-86fc-648d820ae1fb>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/1d50eb79-685f-45ea-84b4-627154eddede>`. `<https://linked.data.gov.au/def/nrm/1d50eb79-685f-45ea-84b4-627154eddede>` is the IRI for "soil lithology types".
The value of `tern:vocabulary` _MUST_ match the pattern `1d50eb79-685f-45ea-84b4-627154eddede$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/92ae6036-50a8-446c-8df8-573860011b79>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the soil coarse fragments sizes controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the soil coarse fragments sizes controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/92ae6036-50a8-446c-8df8-573860011b79> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'06d01bf1-3863-44ea-95fe-4c62bb47b996'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/92ae6036-50a8-446c-8df8-573860011b79> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/92ae6036-50a8-446c-8df8-573860011b79>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/92ae6036-50a8-446c-8df8-573860011b79>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/06d01bf1-3863-44ea-95fe-4c62bb47b996>`. `<https://linked.data.gov.au/def/nrm/06d01bf1-3863-44ea-95fe-4c62bb47b996>` is the IRI for "soil coarse fragments sizes".
The value of `tern:vocabulary` _MUST_ match the pattern `06d01bf1-3863-44ea-95fe-4c62bb47b996$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5af5cef1-179c-4bae-9037-42196668deff>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/5af5cef1-179c-4bae-9037-42196668deff> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/5af5cef1-179c-4bae-9037-42196668deff> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5af5cef1-179c-4bae-9037-42196668deff>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5af5cef1-179c-4bae-9037-42196668deff>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/d04de987-a562-495c-855a-ff5aed06f68f> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/d04de987-a562-495c-855a-ff5aed06f68f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/d04de987-a562-495c-855a-ff5aed06f68f> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/d04de987-a562-495c-855a-ff5aed06f68f>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/d04de987-a562-495c-855a-ff5aed06f68f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/132a1452-4fd7-473c-956b-3183dd315b67>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the slope classes controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the slope classes controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/132a1452-4fd7-473c-956b-3183dd315b67> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'d893e669-c530-4bc3-a057-a5799ffcb5db'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/132a1452-4fd7-473c-956b-3183dd315b67> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/132a1452-4fd7-473c-956b-3183dd315b67>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/132a1452-4fd7-473c-956b-3183dd315b67>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/d893e669-c530-4bc3-a057-a5799ffcb5db>`. `<https://linked.data.gov.au/def/nrm/d893e669-c530-4bc3-a057-a5799ffcb5db>` is the IRI for "slope classes".
The value of `tern:vocabulary` _MUST_ match the pattern `d893e669-c530-4bc3-a057-a5799ffcb5db$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b036ba09-d061-4a1c-99a8-890efc462a2c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b036ba09-d061-4a1c-99a8-890efc462a2c>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/b036ba09-d061-4a1c-99a8-890efc462a2c> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b036ba09-d061-4a1c-99a8-890efc462a2c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 0 and 90 inclusive.
The result _MUST_ have a value between 0 and 90 inclusively.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/615edd85-ea58-4d3c-b737-d31d8447ad49>`. # `<https://linked.data.gov.au/def/nrm/615edd85-ea58-4d3c-b737-d31d8447ad49>` is the IRI for "Standard Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/615edd85-ea58-4d3c-b737-d31d8447ad49`.
2025-06 2.2: fixed Dataset class targeting & allowed more temporal object types 2025-06: Added a requirement for geometry representation as WKT; removed ID requirements 2025-05: Update for maintenance by DCCEEW 2022: Initial release for the Loc-I project
Requirement-D-temporal: A Dataset MAY indicate the total temporal range that the features within it occupy by using the time:hasTime predicate
Requirement-D-created: Each Dataset MUST have exactly one created date indicated using the schema:dateCreated predicate with a literal value of either xsd:date, xsd:dateTime or xsd:dateTimeStamp type
Requirement-D-creator: Each Dataset MUST indicate one or more agents with the schema:creator predicate, typed as an schema:Person or schema:Organization
Requirement-D-desc: Each Dataset MUST have one and description which is to be a text literal, indicated using the schema:description predicate
Requirement-D-exists: Each graph MUST contain at least one Dataset instance
Requirement-D-history: Each Dataset SHOULD indicate how it was produced or its origin by use of one of the following predicates: skos:historyNote, schema:citation, prov:wasDerivedFrom
Requirement-D-license: Each Dataset MUST indicate a license that defines conditions for its use with the schema:license predicate with the value indicated coming from either the RDF Licenses dataset or being locally-defined odrl:Policy instance
Requirement-D-modified: Each Dataset MUST have exactly one created date indicated using the schema:dateModified predicate with a literal value of either xsd:date, xsd:dateTime or xsd:dateTimeStamp type
Requirement-D-name: Each Dataset MUST have one and only one name which is to be a text literal, indicated using the schema:name predicate
Requirement-D-publisher: Each Dataset MUST indicate one or more agents with the schema:publisher predicate, typed as an schema:Person or schema:Organization
Requirement-D-spatial: A Dataset MAY indicate the total region that the features within it occupy by using the geo:hasGeometry predicate or a sub property of it such as geo:hasBoundingBox and if it does, it must do so with a geo:Geometry objects
Requirement-F-part-of: Each Feature MUST indicate that it is part of exactly one geo:FeatureCollection instance with use of the schema:isPartOf predicate or Feature Collection must indicate the Feature Collection is a part of it with rdfs:member
Requirement-F-spatial: If a Feature indicates a geometry, MUST do so using the geo:hasGeometry predicate or sub properties of it
Requirement-FC-name: Each Feature Collection MUST have one and only one name which is to be a text literal, indicated using the schema:name predicate
Requirement-FC-part-of: Each Feature Collection MUST indicate that it is part of exactly one schema:Dataset instance with use of the schema:isPartOf predicate or the Dataset must indicate the Feature Collection is a part of it with rdfs:member
Requirement-FC-spatial: A Feature Collection MAY indicate the total region that the features within it occupy by using the geo:hasGeometry predicate or a sub property of it such as geo:hasBoundingBox and if it does, it must do so with a geo:Geometry objects
Requirement-FC-temporal: A Feature Collection MAY indicate the total temporal range that the features within it occupy by using the time:hasTime predicate
Requirement-G-representation: Geometry instances MUST indicate their spatial extent with exactly one geo:asWKT predicate with a geo:wktLiteral datatype
A set of RDF triples that are published, maintained or aggregated by a single provider.
A vocabulary that is used in the dataset.
Points to the void:Dataset that a document is a part of.
The Vocabulary of Interlinked Datasets (VoID) is an RDF Schema vocabulary for expressing metadata about RDF datasets. It is intended as a bridge between the publishers and users of RDF data, with applications ranging from data discovery to cataloging and archiving of datasets. This document provides a formal definition of the new RDF classes and properties introduced for VoID. It is a companion to the main specification document for VoID, Describing Linked Datasets with the VoID Vocabulary.
Vocabulary of Interlinked Datasets (VoID)
A collection of RDF links between two void:Datasets.
Defines a simple URI look-up protocol for accessing a dataset.
An OpenSearch description document for a free-text search service over a void:Dataset.
A URI that is a common string prefix of all the entity URIs in a void:Dataset.
A web resource whose foaf:primaryTopic or foaf:topics include void:Datasets.
The rdfs:Class that is the rdf:type of all entities in a class-based partition.
A subset of a void:Dataset that contains only the entities of a certain rdfs:Class.
The total number of distinct classes in a void:Dataset. In other words, the number of distinct resources occuring as objects of rdf:type triples in the dataset.
An RDF dump, partial or complete, of a void:Dataset.
The total number of distinct objects in a void:Dataset. In other words, the number of distinct resources that occur in the object position of triples in the dataset. Literals are included in this count.
The total number of distinct subjects in a void:Dataset. In other words, the number of distinct resources that occur in the subject position of triples in the dataset.
The total number of documents, for datasets that are published as a set of individual documents, such as RDF/XML documents or RDFa-annotated web pages. Non-RDF documents, such as web pages in HTML or images, are usually not included in this count. This property is intended for datasets where the total number of triples or entities is hard to determine. void:triples or void:entities should be preferred where practical.
The total number of entities that are described in a void:Dataset.
A technical feature of a void:Dataset, such as a supported RDF serialization format.
The dataset describing the objects of the triples contained in the Linkset.
One of the two datasets linked by the Linkset.
The total number of distinct properties in a void:Dataset. In other words, the number of distinct resources that occur in the predicate position of triples in the dataset.
The rdf:Property that is the predicate of all triples in a property-based partition.
A subset of a void:Dataset that contains only the triples of a certain rdf:Property.
A top concept or entry point for a void:Dataset that is structured in a tree-like fashion. All resources in a dataset can be reached by following links from its root resources in a small number of steps.
The dataset describing the subjects of triples contained in the Linkset.
The total number of triples contained in a void:Dataset.
Defines a regular expression pattern matching URIs in the dataset.
Department of Zoology, University of Oxford
Digital Enterprise Research Institute, NUI Galway
A description of the RFC 7946 GeoJSON model. See https://github.com/geojson/geojson-ld for vocabulary developments.
This work is licensed under the Creative Commons Attribution 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/ or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA.
This FSDF Themes vocabulary is the taxonomy of dataset themes implemented by the [ANZLIC - The Spatial Information Council](https://www.anzlic.gov.au)'s' Foundation Spatial Data Framework (FSDF) project which is "a common reference for the assembly and maintenance of Australian and New Zealand foundation level spatial data"
This vocabulary was developed by Geoscience Australia for ICSM vocabulary testing work in 2021 from the FSDF LINK website contains all this information in non-Semantic Web but highly structured, form
Use the UNGGIM Themes vocabulary for data classification instead of this one, wherever possible
Forests of Australia (2018) is a continental spatial ​dataset of forest extent, by national forest categories and types, assembled for [Australia's State of the Forests Report 2018](http://www.agriculture.gov.au/abares/forestsaustralia/Pages/SOFR2018/sofr-2018.aspx). It was developed from multiple forest, vegetation and land cover data inputs, including contributions from Australian, state and territory government agencies and external sources. ​ A forest is defined in this dataset as _"An area, incorporating all living and non-living components, that is dominated by trees having usually a single stem and a mature or potentially mature stand height exceeding two metres and with existing or potential crown cover of overstorey​ strata about equal to or greater than 20 per cent. This includes Australia's diverse native forests and commercial plantations, regardless of age. It is also sufficiently broad to encompass areas of trees that are sometimes described as woodlands"_. The dataset was compiled by the Australian Bureau of Agricultural and Resource Economics and Sciences (ABARES) for the [National Forest Inventory](http://www.agriculture.gov.au/abares/forestsaustralia/Pages/Australia%27s-National-Forest-Inventory.aspx) (NFI), a collaborative partnership between the Australian and state and territory governments. The role of the NFI is to collate, integrate and communicate information on Australia's forests. States and territories agencies collect forest data using independent methods and at varying scales or resolutions. The NFI applies a national classification to state and territory data to allow seamless integration of these datasets. Multiple independent ​sources of external data are used to fill data gaps and improve the quality of the final data​set. The NFI classifies forests into three national forest categories (Native forest, Commercial plantation, and Other forest) and then into various forest types. Commercial plantations presented in this dataset were sourced from the [National Plantation Inventory](http://www.agriculture.gov.au/abares/forestsaustralia/plantation-inventory-and-statistics) (NPI) spatial dataset (2016), also produced by ABARES. Another dataset produced by ABARES, the [Catchment scale Land Use and Management](http://www.agriculture.gov.au/abares/aclump/Pages/land-use/data-download.aspx) (CLUM) dataset (2016) was used to identify ​and mask out land uses that are inappropriate to map as forest.​
The Geocoded Addressing theme focusses on the connection between a physical address with location information which shows up as a 'place' or 'spot' on the Earth. This makes the information able to be mapped and connected to other location information. An address is a structured label usually containing a property number, a road name and a locality name.
Geocoded Addressing
The Elevation and Depth theme focusses on foundation datasets which measure the Earth’s surface (wet or dry) above or below a vertical datum to obtain either the height of the land or a bathymetric depth.
The positioning theme is Australia's spatial referencing system. The positioning service defined under this theme includes the coordinates and their uncertainty of all location-based data promulgated from or related to, the Australian Fiducial Network (AFN) and the defining Australian Height Datum tide gauge stations.
Positioning
The Place Names theme focuses on foundation datasets for the names of cultural and physical features and their location and extent.
Place Names
The Land Parcel and Property theme focusses on foundation datasets for the land boundary system. The term Land Parcel and Property can be interchangeable with cadastral, land administration and property systems. Land Parcel and Property contains a record of interest in land.
Land Parcel and Property
The Imagery theme focuses on foundation data which captures images of the Earths surface, from many different sensors and cameras. This data is often the base layer over which many other datasets are used.
Imagery
The Administrative Boundaries theme focusses on foundation datasets which define the spatial extent of legislative jurisdictions and regulatory, electoral, statistical and maritime geographic areas
Administrative Boundaries
The Land cover and Land Use theme focusses on foundation datasets for Land Cover and Land Use. Both land cover/use are often very interrelated datasets. Land cover shows the natural cover on the Earth's surface including trees, shrubs, grasses, soils, exposed rocks and water bodies; as well as human elements such as plantations, crops and built environments; Land Use refers to the ways in which land cover is used by humans (e.g. residential, industrial, commercial, agricultural, forestry, recreational).
The Transport theme focuses on foundation datasets for moving people, goods and freight, and other services from one location to another.
Transport
The Water theme focuses on foundation datasets for surface and groundwater and excludes atmospheric, industrial or oceanic water processes.
Population Distributions
Terms in the ssn: namespace have equivalence axioms to terms declared in the sosa: namespace, and are marked 'deprecated'. The axiomatization from the 2017 version of the standard is preserved. Terms in the sosa: namespace do not carry symmetric equivalent axioms. Axiomatization only uses sosa: terms.
The SSN module contains an axiomatization of the core terms from the SOSA module (serialized in the sosa:ttl file) plus some deprecated terms in the ssn: namespace.
Please report any errors to the W3C Spatial Data on the Web Working Group via the SDW WG Public List public-sdw-wg@w3.org
This module imports all the axiomatizations of the SOSA terms, and adds cross-module axioms.
This ontology describes sensors, actuators and observations, and related concepts. It does not describe domain concepts, time, locations, etc. these are intended to be included from other ontologies via OWL imports.
Semantic Sensor Network Ontology
New modular version of the SSN ontology. This ontology was originally developed in 2009-2011 by the W3C Semantic Sensor Networks Incubator Group (SSN-XG). For more information on the group's activities see: http://www.w3.org/2005/Incubator/ssn/. The ontology was revised and modularized in 2015-2017 by the W3C/OGC Spatial Data on the Web Working Group, see: https://www.w3.org/2015/spatial/wiki/Semantic_Sensor_Network_Ontology. In particular, (a) the scope is extended to include actuation and sampling; (b) the core concepts and properties are factored out into the SOSA ontology. The SSN ontology imports SOSA and adds formal axiomatization consistent with the text definitions in SOSA, and adds classes and properties to accommodate the scope of the original SSN ontology.
Created during the OGC's Open Science Persistent Demonstrator 2025 project
Ontology for the SpatioTemporal Asset Catalog (STAC) Core 1.0.0 specification
Datetime associated with the Item (typically acquisition time).
A STAC Item is a GeoJSON Feature augmented with STAC metadata fields and links.
A STAC Catalog is a JSON object that provides links to other STAC entities.
A Collection extends Catalog with additional metadata and describes a group of related STAC Items.
The spatiotemporal extent of a Collection.
An Asset represents a file associated with a STAC Item, such as an image, data file, or metadata file.
A Link describes a relationship between STAC entities using rel values and hrefs.
Collection-wide license applying to Items unless overridden by an Item.
Associates a STAC entity with its links.
The status of this register entry
status
2026-01 NJC: added OntPub elements. Removed RegStatus vocab as found elsewhere
Core ontology for linked data registry services. Based on ISO19135 but heavily modified to suit Linked Data representations and applications.
Registry ontology
The two-character ISO 639-1 language code.
A language that is supported by a multilingual registry.
A registerable entity which forwards all requests to a remote register. Queries which traverse the register hierarchy such as entity search will also be forwarded
Federated Register
A registerable entity which represents some form of delegation
Delegated
Represents a collection of registered items, together with some associated governance regime. If one or more licenses is stated then each license applies to all the entries in the register.
Register
Represents a SPARQL CONSTRUCT query.
SPARQL CONSTRUCT query
Represents a SPARQL query as a reusable resource.
SPARQL query
Represents a SPARQL SELECT query.
SPARQL SELECT query
A messaging topic that can be notified of changes in the registry.
Topic
The URI of a graph of annotation statements associate with this item
annotation
A metadata record for an entry in a register. Note that cardinality constraints can be met by sub-properties, for example an item with a skos:prefLabel implies an schema:name and so meets the cardinality constraint on schema:name.
RegisterItem
A sub-register to exclude from monitoring.
ignores
A specification for a register to be monitored.
Monitor Spec
Indicates a property which links a member of a collection back to the collection itself, this is the reverse direction to the normal ldp:membershipPredicate
inverse membership predicate
A register to be monitored.
monitors
Gives the label of a state which can follow from this state
next state
A topic or channel to be notified when the monitored register changes.
notifies
Presentational hint for showing items with this status
presentation
Gives the label of a state which can precede this state
A tagged snapshot of a register
release
Gives the source dataset in a Linkset, the other link target is assumed to be the destination
source dataset
Indicates a register that is itself an entry in this principle register.
subregister
Indicates the replacement for a superseded item.
successor
An item which has been replaced this one within the register. Should be asserted between hub resources (VersionedThing).
predecessor
The tag used to label a collection which snapshots the state of a register
tag
A registerable entity which simply forwards all requests to the delegation target.
Namespace Forward
The HTTP status code to return the requester in order to forward the request.
forwarding code
Represents a SPARQL ASK query as might be used for validation.
SPARQL ASK query
An alternative URI for the entity, the alias resource is regarded by this register as owl:sameAs the definition entity
alias
A reference to some internal or external Linked Data resource. The reg:entity gives the URI of the resource being referenced. If a reg:sourceGraph value is present then it is the URI for a named graph within the Registry containing the properties of the referenced entity. If reg:entityVersion is present it gives URI for the particular version:Version of the entity being referenced. Normally only one of reg:sourceGraph and reg:entityVersion is needed since versioned entities are normally stored in the default graph.
Entity Reference
Optional classification for a registered item within one or more SKOS classification schemes to support navigation and discovery. Orthogonal to the structure provided by the register hierarchy which is about governance.
category
A class of entities that can occur in this register
contained item class
The entity which has been registered.
definition
A resource to which the delegated register delegates, may be a register in another registry service, a SPARQL endpoint or some other web resource
delegation target
The RDF resource identified by an entity reference
Indicates the particular version:Version of the entity being referenced.
entity version
Specifies the object part of a triple pattern used to enumerate the members of a delegated register
enumeration object
A register whose member contents are determined through delegation to a SPARQL endpoint
Delegated Register
Specifies the predicate part of a triple pattern used to enumerate the members of a delegated register
enumeration predicate
Specifies the subject part of a triple pattern used to enumerate the members of a delegated register
enumeration subject
A resource, such as a web accessible-document, which describes the governance policy applicable to this register.
governance policy
The manager of the register, may be a person (foaf:Person) or an organization (org:Organization). Operates the register on behalf of the owner, makes day to day decisions on acceptance of entries based on agreed principles but it may be possible to appeal to the owner to override a decision by the manager.
manager
Indicates a language supported by the register and the items within it. The language should be indicated by a resource within a well-maintained URI set such as the Library of Congress language URIs e.g. http://id.loc.gov/vocabulary/iso639-1/en
operating language
The owner of the register, may be a person (foaf:Person) or an organization (org:Organization). The owner has final authority over the contents of the regster.
The source of a SPARQL query
query
The register in which this item has been registered.
register
A resource, typically a real-world object, which the registered entity is a representation for.
representation of
A resource representing an RDF graph (within the Registry's SPARQL dataset) containing the properties of the reference entity. If not present then assume default graph.
source graph
A SPARQL ASK query which can be used to validate a proposed entry in this register. Returns true of an error is found.
validation query
The type of the entity that this record is about. Note that it may be possible to register a non-RDF resource in which case this property provides a way to state the intended class of the entity even though no direct RDF assertion of type is available.
item class
A short text string which can be used to denote the register item. Must be unique within the register. If available it should be used as the path segment, relative to the parent register, for the RegisterItem (and for the item itself, if managed). Restricted to be a syntactically legal URI segment (i.e. *pchar).
notation
The person or organization who originally submitted this register entry. Subsequent chages to the entry may have been made by other agents.
submitter
EDES Plant Tissue Vouchering Shapes Graph
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3b2aa21d-c60f-45c5-9447-ff8a799a513e>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
Observations following the Plant Tissue Vouchering - Enhanced Protocol are made in the context of a site visit.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3b2aa21d-c60f-45c5-9447-ff8a799a513e>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3b2aa21d-c60f-45c5-9447-ff8a799a513e> ; sosa:hasResult ?this . }
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/eea8280c-6ec7-48c9-9b9e-2418731ff005>`. `<https://linked.data.gov.au/def/nrm/eea8280c-6ec7-48c9-9b9e-2418731ff005>` is the IRI for "Plant Tissue Vouchering - Enhanced Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/eea8280c-6ec7-48c9-9b9e-2418731ff005`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3b2aa21d-c60f-45c5-9447-ff8a799a513e>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 0 exclusive and 100 inclusive.
The result _MUST_ have a value between 0 exclusively and 100 inclusively.
Observations following the Plant Tissue Vouchering - Standard Protocol are made in the context of a site visit.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/c20d9a04-702d-429a-ab5f-d7424cd2990d>`. `<https://linked.data.gov.au/def/nrm/c20d9a04-702d-429a-ab5f-d7424cd2990d>` is the IRI for "Plant Tissue Vouchering - Standard Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/c20d9a04-702d-429a-ab5f-d7424cd2990d`.
prov:wasDerivedFrom must indicate an IRI
schema:citation must indicate a URL or a string
Check that the Data Catalogue has a created date
Check that the Data Catalogue has a creator
Check that the Data Catalogue has a description
Requirement D-history: Each catalogue SHOULD indicate how it was produced or its origin by use of one of the following predicates: skos:historyNote, schema:citation, prov:wasDerivedFrom
Check that the Data Catalogue has a license
Check that the Data Catalogue has a modified date
Check that the Data Catalogue has a name
Check that the Data Catalogue has a publisher
Requirement D-creator: Each catalogue MUST indicate one or more agents with the schema:creator predicate, typed as an schema:Person or schema:Organization
Each graph MUST have at least one catalogue instance
Requirement D-license: Each catalogue MUST indicate a license that defines conditions for its use with the schema:license predicate with the value indicated coming from either the RDF Licenses dataset or being locally-defined odrl:Policy instance
Requirement D-publisher: Each catalogue MUST indicate one or more agents with the schema:publisher predicate, typed as an schema:Person or schema:Organization
skos:historyNote must indicate a string, with or without language indicated
A temporal entity with non-zero extent or duration, i.e. for which the value of the beginning and end are different
A temporal entity with zero extent or duration
Feature at risk - added in 2017 revision, and not yet widely used.
Supports the association of a temporal entity (instant or interval) to any thing
Alternative to time:DurationDescription to support description of a temporal duration other than using a calendar/clock system.
Duration of a temporal extent expressed as a number scaled by a temporal unit
Position of a time instant expressed as a TimePosition
Position of an instant, expressed using xsd:date
Position of an instant, expressed using xsd:dateTimeStamp
Position of an instant, expressed using xsd:gYear
Position of an instant, expressed using xsd:gYearMonth
A temporal entity with an extent or duration
A temporal position described using either a (nominal) value from an ordinal reference system, or a (numeric) value in a temporal coordinate system.
2016-06-15 - initial update of OWL-Time - modified to support arbitrary temporal reference systems.
2016-12-20 - adjust range of time:timeZone to time:TimeZone, moved up from the tzont ontology.
2016-12-20 - restore time:Year and time:January which were present in the 2006 version of the ontology, but now marked "deprecated".
2017-02 - intervalIn, intervalDisjoint, monthOfYear added; TemporalUnit subclass of TemporalDuration
2017-04-06 - hasTime, hasXSDDuration added; Number removed; all duration elements changed to xsd:decimal
Update of OWL-Time ontology, extended to support general temporal reference systems. Ontology engineering by Simon J D Cox
Copyright © 2006-2017 W3C, OGC. W3C and OGC liability, trademark and document use rules apply.
OWL-Time is an OWL-2 DL ontology of temporal concepts, for describing the temporal properties of resources in the world or described in Web pages. The ontology provides a vocabulary for expressing facts about topological (ordering) relations among instants and intervals, together with information about durations, and about temporal position including date-time information. Time positions and durations may be expressed using either the conventional (Gregorian) calendar and clock, or using another temporal reference system such as Unix-time, geologic time, or different calendars.
Remove enumeration from definition, in order to allow other days to be used when required in other calendars. NOTE: existing days are still present as members of the class, but the class membership is now open. In the original OWL-Time the following constraint appeared: owl:oneOf ( time:Monday time:Tuesday time:Wednesday time:Thursday time:Friday time:Saturday time:Sunday ) ;
Membership of the class :DayOfWeek is open, to allow for alternative week lengths and different day names.
This class was present in the 2006 version of OWL-Time. It was presented as an example of how DateTimeDescription could be specialized, but does not belong in the revised ontology.
Month position in a calendar-clock system. The range of this property is not specified, so can be replaced by any specific representation of a calendar month from any calendar.
Description of date and time structured with separate values for the various elements of a calendar-clock system. The temporal reference system is fixed to Gregorian Calendar, and the range of year, month, day properties restricted to corresponding XML Schema types xsd:gYear, xsd:gMonth and xsd:gDay, respectively.
Year was proposed in the 2006 version of OWL-Time as an example of how DurationDescription could be specialized to allow for a duration to be restricted to a number of years. It is deprecated in this edition of OWL-Time.
length of, or element of the length of, a temporal extent expressed in years
length, or element of, a temporal extent expressed in minutes
length of, or element of the length of, a temporal extent expressed in weeks
length of, or element of the length of, a temporal extent expressed in seconds
length of, or element of the length of, a temporal extent expressed in months
length of, or element of the length of, a temporal extent expressed in hours
length of, or element of the length of, a temporal extent expressed in days
In the Gregorian calendar the length of the month is not fixed. Therefore, a value like "2.5 months" cannot be exactly compared with a similar duration expressed in terms of weeks or days.
Description of temporal extent structured with separate values for the various elements of a calendar-clock system. The temporal reference system is fixed to Gregorian Calendar, and the range of each of the numeric properties is restricted to xsd:decimal
Day of month - formulated as a text string with a pattern constraint to reproduce the same lexical form as gDay, except that values up to 99 are permitted, in order to support calendars with more than 31 days in a month. Note that the value-space is not defined, so a generic OWL2 processor cannot compute ordering relationships of values of this type.
Month of year - formulated as a text string with a pattern constraint to reproduce the same lexical form as gMonth, except that values up to 20 are permitted, in order to support calendars with more than 12 months in the year. Note that the value-space is not defined, so a generic OWL2 processor cannot compute ordering relationships of values of this type.
Year number - formulated as a text string with a pattern constraint to reproduce the same lexical form as gYear, but not restricted to values from the Gregorian calendar. Note that the value-space is not defined, so a generic OWL2 processor cannot compute ordering relationships of values of this type.
Value of DateTimeInterval expressed as a structured value. The beginning and end of the interval coincide with the limits of the shortest element in the description.
:DateTimeInterval can only be used for an interval whose limits coincide with a date-time element aligned to the calendar and timezone indicated. For example, while both have a duration of one day, the 24-hour interval beginning at midnight at the beginning of 8 May in Central Europe can be expressed as a :DateTimeInterval, but the 24-hour interval starting at 1:30pm cannot.
DateTimeInterval is a subclass of ProperInterval, defined using the multi-element DateTimeDescription.
Some combinations of properties are redundant - for example, within a specified :year if :dayOfYear is provided then :day and :month can be computed, and vice versa. Individual values should be consistent with each other and the calendar, indicated through the value of the :hasTRS property.
Description of date and time structured with separate values for the various elements of a calendar-clock system
Duration of a temporal entity, expressed using a structured description
The extent of a time duration expressed as a GeneralDurationDescription depends on the Temporal Reference System. In some calendars the length of the week or month is not constant within the year. Therefore, a value like "2.5 months" may not necessarily be exactly compared with a similar duration expressed in terms of weeks or days. When non-earth-based calendars are considered even more care must be taken in comparing durations.
Description of temporal extent structured with separate values for the various elements of a calendar-clock system.
Extent of a temporal entity, expressed using xsd:duration
The property :inXSDDateTime is replaced by :inXSDDateTimeStamp which makes the time-zone field mandatory.
Position of an instant, expressed using xsd:dateTime
An instant that falls inside the interval. It is not intended to include beginnings and ends of intervals.
Remove enumeration from definition, in order to allow other units to be used when required in other coordinate systems. NOTE: existing units are still present as members of the class, but the class membership is now open. In the original OWL-Time the following constraint appeared: owl:oneOf ( time:unitSecond time:unitMinute time:unitHour time:unitDay time:unitWeek time:unitMonth time:unitYear ) ;
Membership of the class TemporalUnit is open, to allow for other temporal units used in some technical applications (e.g. millions of years, Baha'i month).
A standard duration, which provides a scale factor for a time extent, or the granularity or precision for a time position.
Using xsd:dateTime in this place means that the duration of the interval is implicit: it corresponds to the length of the smallest non-zero element of the date-time literal. However, this rule cannot be used for intervals whose duration is more than one rank smaller than the starting time - e.g. the first minute or second of a day, the first hour of a month, or the first day of a year. In these cases the desired interval cannot be distinguished from the interval corresponding to the next rank up. Because of this essential ambiguity, use of this property is not recommended and it is deprecated.
Value of DateTimeInterval expressed as a compact value.
The temporal reference system used by a temporal position or extent description.
Membership of the class :MonthOfYear is open, to allow for alternative annual calendars and different month names.
Year position in a calendar-clock system. The range of this property is not specified, so can be replaced by any specific representation of a calendar year from any calendar.
Minute position in a calendar-clock system.
Weeks are numbered differently depending on the calendar in use and the local language or cultural conventions (locale). ISO-8601 specifies that the first week of the year includes at least four days, and that Monday is the first day of the week. In that system, week 1 is the week that contains the first Thursday in the year.
Day position in a calendar-clock system. The range of this property is not specified, so can be replaced by any specific representation of a calendar day from any calendar.
Second position in a calendar-clock system.
Hour position in a calendar-clock system.
A taxonomy of temporal reference systems is provided in ISO 19108:2002 [ISO19108], including (a) calendar + clock systems; (b) temporal coordinate systems (i.e. numeric offset from an epoch); (c) temporal ordinal reference systems (i.e. ordered sequence of named intervals, not necessarily of equal duration).
A temporal reference system, such as a temporal coordinate system (with an origin, direction, and scale), a calendar-clock combination, or a (possibly hierarchical) ordinal system. This is a stub class, representing the set of all temporal reference systems.
In the original 2006 version of OWL-Time, the TimeZone class, with several properties corresponding to a specific model of time-zones, was defined in a separate namespace "http://www.w3.org/2006/timezone#". In the current version a class with same local name is put into the main OWL-Time namespace, removing the dependency on the external namespace. An alignment axiom tzont:TimeZone rdfs:subClassOf time:TimeZone . allows data encoded according to the previous version to be consistent with the updated ontology.
A designated timezone is associated with a geographic region. However, for a particular region the offset from UTC often varies seasonally, and the dates of the changes may vary from year to year. The timezone designation usually changes for the different seasons (e.g. Australian Eastern Standard Time vs. Australian Eastern Daylight Time). Furthermore, the offset for a timezone may change over longer timescales, though its designation might not. Detailed guidance about working with time zones is given in http://www.w3.org/TR/timezone/ .
An ontology for time zone descriptions was described in and provided as RDF in a separate namespace tzont:. However, that ontology was incomplete in scope, and the example datasets were selective. Furthermore, since the use of a class from an external ontology as the range of an ObjectProperty in OWL-Time creates a dependency, reference to the time zone class has been replaced with the 'stub' class in the normative part of this version of OWL-Time.
In this implementation TimeZone has no properties defined. It should be thought of as an 'abstract' superclass of all specific timezone implementations.
A Time Zone specifies the amount by which the local time is offset from UTC. A time zone is usually denoted geographically (e.g. Australian Eastern Daylight Time), with a constant value in a given region. The region where it applies and the offset from UTC are specified by a locally recognised governing authority.
The day of week, whose value is a member of the class time:DayOfWeek
If a proper interval T1 is intervalAfter another proper interval T2, then the beginning of T1 is after the end of T2.
Gives directionality to time. If a temporal entity T1 is after another temporal entity T2, then the beginning of T1 is after the end of T2.
This interval relation is not included in the 13 basic relationships defined in Allen (1984), but is defined in (T.3) as the union of :intervalBefore v :intervalAfter . However, that is outside OWL2 expressivity, so is implemented as an explicit property, with :intervalBefore , :intervalAfter as sub-properties
If a proper interval T1 is intervalDisjoint another proper interval T2, then the beginning of T1 is after the end of T2, or the end of T1 is before the beginning of T2, i.e. the intervals do not overlap in any way, but their ordering relationship is not known.
If a proper interval T1 is intervalBefore another proper interval T2, then the end of T1 is before the beginning of T2.
Gives directionality to time. If a temporal entity T1 is before another temporal entity T2, then the end of T1 is before the beginning of T2. Thus, "before" can be considered to be basic to instants and derived for intervals.
If a proper interval T1 is intervalContains another proper interval T2, then the beginning of T1 is before the beginning of T2, and the end of T1 is after the end of T2.
If a proper interval T1 is intervalDuring another proper interval T2, then the beginning of T1 is after the beginning of T2, and the end of T1 is before the end of T2.
This interval relation is not included in the 13 basic relationships defined in Allen (1984), but is referred to as 'an important relationship' in Allen and Ferguson (1997). It is the disjoint union of :intervalStarts v :intervalDuring v :intervalFinishes . However, that is outside OWL2 expressivity, so is implemented as an explicit property, with :intervalStarts , :intervalDuring , :intervalFinishes as sub-properties
If a proper interval T1 is intervalIn another proper interval T2, then the beginning of T1 is after the beginning of T2 or is coincident with the beginning of T2, and the end of T1 is before the end of T2, or is coincident with the end of T2, except that end of T1 may not be coincident with the end of T2 if the beginning of T1 is coincident with the beginning of T2.
If a proper interval T1 is intervalEquals another proper interval T2, then the beginning of T1 is coincident with the beginning of T2, and the end of T1 is coincident with the end of T2.
If a proper interval T1 is intervalFinishedBy another proper interval T2, then the beginning of T1 is before the beginning of T2, and the end of T1 is coincident with the end of T2.
If a proper interval T1 is intervalFinishes another proper interval T2, then the beginning of T1 is after the beginning of T2, and the end of T1 is coincident with the end of T2.
If a proper interval T1 is intervalMeets another proper interval T2, then the end of T1 is coincident with the beginning of T2.
If a proper interval T1 is intervalMetBy another proper interval T2, then the beginning of T1 is coincident with the end of T2.
If a proper interval T1 is intervalOverlappedBy another proper interval T2, then the beginning of T1 is after the beginning of T2, the beginning of T1 is before the end of T2, and the end of T1 is after the end of T2.
If a proper interval T1 is intervalOverlaps another proper interval T2, then the beginning of T1 is before the beginning of T2, the end of T1 is after the beginning of T2, and the end of T1 is before the end of T2.
If a proper interval T1 is intervalStarted another proper interval T2, then the beginning of T1 is coincident with the beginning of T2, and the end of T1 is after the end of T2.
If a proper interval T1 is intervalStarts another proper interval T2, then the beginning of T1 is coincident with the beginning of T2, and the end of T1 is before the end of T2.
The month of the year, whose value is a member of the class time:MonthOfYear
The (nominal) value indicating temporal position in an ordinal reference system
The (numeric) value indicating position within a temporal coordinate system
In the original 2006 version of OWL-Time, the range of time:timeZone was a TimeZone class in a separate namespace "http://www.w3.org/2006/timezone#". An alignment axiom tzont:TimeZone rdfs:subClassOf time:TimeZone . allows data encoded according to the previous version to be consistent with the updated ontology.
IANA maintains a database of timezones. These are well maintained and generally considered authoritative, but individual items are not available at individual URIs, so cannot be used directly in data expressed using OWL-Time. DBPedia provides a set of resources corresponding to the IANA timezones, with a URI for each (e.g. http://dbpedia.org/resource/Australia/Eucla). The World Clock service also provides a list of time zones with the description of each available as an individual webpage with a convenient individual URI (e.g. https://www.timeanddate.com/time/zones/acwst). These or other, similar, resources might be used as a value of the time:timeZone property.
The time zone for clock elements in the temporal position
Time extent; duration of a time interval separate from its particular start position
Dublin Core Metadata Element Set, Version 1.1
A [second property](/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/description) with the same name as this property has been declared in the [dcterms: namespace](http://purl.org/dc/terms/). See the Introduction to the document [DCMI Metadata Terms](/specifications/dublin-core/dcmi-terms/) for an explanation.
An account of the resource.
Description
A [second property](/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/rights) with the same name as this property has been declared in the [dcterms: namespace](http://purl.org/dc/terms/). See the Introduction to the document [DCMI Metadata Terms](/specifications/dublin-core/dcmi-terms/) for an explanation.
Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights.
Rights
A [second property](/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/title) with the same name as this property has been declared in the [dcterms: namespace](http://purl.org/dc/terms/). See the Introduction to the document [DCMI Metadata Terms](/specifications/dublin-core/dcmi-terms/) for an explanation.
A name given to the resource.
Title
A [second property](/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/date) with the same name as this property has been declared in the [dcterms: namespace](http://purl.org/dc/terms/). See the Introduction to the document [DCMI Metadata Terms](/specifications/dublin-core/dcmi-terms/) for an explanation.
Date
A [second property](/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/identifier) with the same name as this property has been declared in the [dcterms: namespace](http://purl.org/dc/terms/). See the Introduction to the document [DCMI Metadata Terms](/specifications/dublin-core/dcmi-terms/) for an explanation.
Recommended practice is to identify the resource by means of a string conforming to an identification system.
Identifier
A [second property](/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/relation) with the same name as this property has been declared in the [dcterms: namespace](http://purl.org/dc/terms/). See the Introduction to the document [DCMI Metadata Terms](/specifications/dublin-core/dcmi-terms/) for an explanation.
A related resource.
A [second property](/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/creator) with the same name as this property has been declared in the [dcterms: namespace](http://purl.org/dc/terms/). See the Introduction to the document [DCMI Metadata Terms](/specifications/dublin-core/dcmi-terms/) for an explanation.
Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity.
An entity primarily responsible for making the resource.
Creator
A [second property](/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/format) with the same name as this property has been declared in the [dcterms: namespace](http://purl.org/dc/terms/). See the Introduction to the document [DCMI Metadata Terms](/specifications/dublin-core/dcmi-terms/) for an explanation.
Recommended practice is to use a controlled vocabulary where available. For example, for file formats one could use the list of Internet Media Types [[MIME](https://www.iana.org/assignments/media-types/media-types.xhtml)].
Format
A [second property](/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/language) with the same name as this property has been declared in the [dcterms: namespace](http://purl.org/dc/terms/). See the Introduction to the document [DCMI Metadata Terms](/specifications/dublin-core/dcmi-terms/) for an explanation.
A language of the resource.
A [second property](/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/publisher) with the same name as this property has been declared in the [dcterms: namespace](http://purl.org/dc/terms/). See the Introduction to the document [DCMI Metadata Terms](/specifications/dublin-core/dcmi-terms/) for an explanation.
Examples of a Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity.
Publisher
A [second property](/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/source) with the same name as this property has been declared in the [dcterms: namespace](http://purl.org/dc/terms/). See the Introduction to the document [DCMI Metadata Terms](/specifications/dublin-core/dcmi-terms/) for an explanation.
The described resource may be derived from the related resource in whole or in part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.
A [second property](/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/coverage) with the same name as this property has been declared in the [dcterms: namespace](http://purl.org/dc/terms/). See the Introduction to the document [DCMI Metadata Terms](/specifications/dublin-core/dcmi-terms/) for an explanation.
Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names [[TGN](https://www.getty.edu/research/tools/vocabulary/tgn/index.html)]. Where appropriate, named places or time periods may be used in preference to numeric identifiers such as sets of coordinates or date ranges.
Coverage
A [second property](/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/subject) with the same name as this property has been declared in the [dcterms: namespace](http://purl.org/dc/terms/). See the Introduction to the document [DCMI Metadata Terms](/specifications/dublin-core/dcmi-terms/) for an explanation.
Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary.
The topic of the resource.
Subject
A [second property](/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/type) with the same name as this property has been declared in the [dcterms: namespace](http://purl.org/dc/terms/). See the Introduction to the document [DCMI Metadata Terms](/specifications/dublin-core/dcmi-terms/) for an explanation.
Recommended practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [[DCMI-TYPE](http://dublincore.org/documents/dcmi-type-vocabulary/)]. To describe the file format, physical medium, or dimensions of the resource, use the Format element.
The nature or genre of the resource.
Type
A [second property](/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/contributor) with the same name as this property has been declared in the [dcterms: namespace](http://purl.org/dc/terms/). See the Introduction to the document [DCMI Metadata Terms](/specifications/dublin-core/dcmi-terms/) for an explanation.
The guidelines for using names of persons or organizations as creators also apply to contributors. Typically, the name of a Contributor should be used to indicate the entity.
Contributor
The Basic Catalogue Resource Profile validator
Basic Catalogue Resource Profile Validator
Each graph MUST have at least one catalogued resource instance
Checks all the property shapes for Resource
The subject MUST have a label (rdfs:label, schema:name or skos:prefLabel) predicate and it MUST indicate a string or a language string literal value
The subject MUST have a description (rdfs:comment, dcterms:description, schema:description or skos:definition) predicate and it MUST indicate a string or a language string literal value
Catalogued resource description property
Each catalogued resource MUST indicate one or more Agents with the schema:creator predicate, typed as an schema:Person or schema:Organization
Each catalogued resource MUST indicate one or more agents with the schema:publisher predicate, typed as an schema:Person or schema:Organization
Each catalogued resource MUST have exactly one created date indicated using the schema:dateCreated predicate with a literal value of either xsd:date, xsd:dateTime or xsd:dateTimeStamp type
Catalogued resource created date property
Each catalogued resource MUST have exactly one created date indicated using the schema:dateModified predicate with a literal value of either xsd:date, xsd:dateTime or xsd:dateTimeStamp type
Catalogued resource modified date property
Each catalogued resource MUST indicate a license that defines conditions for its use with the schema:license predicate
A catalogued resource MUST have at least one value for schema:citation (URL or string), skos:historyNote (string) or wasDerivedFrom (IRI)
Catalogued resource provenance property 01
Catalogued resource provenance property 02
Catalogued resource provenance property 03
Checks all the property shapes for Organization
The subject MUST must indicate exactly one schema:url predicate with an xsd:anyURI value
Checks all the property shapes for Person
The subject MUST indicate exactly one schema:email predicate with an xsd:anyURI value
Observations following the Condition Module are made in the context of a site visit.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/16a20c3f-e95d-4919-b2d1-a25c7a275109>`. `<https://linked.data.gov.au/def/nrm/16a20c3f-e95d-4919-b2d1-a25c7a275109>` is the IRI for "Condition Module".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/16a20c3f-e95d-4919-b2d1-a25c7a275109`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/05739eee-78b2-5084-b75e-620cea9a2a01>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/05739eee-78b2-5084-b75e-620cea9a2a01>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/05739eee-78b2-5084-b75e-620cea9a2a01> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/05739eee-78b2-5084-b75e-620cea9a2a01>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/f6af2c5e-d193-4337-b845-44550f661854>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/f6af2c5e-d193-4337-b845-44550f661854>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/f6af2c5e-d193-4337-b845-44550f661854> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/f6af2c5e-d193-4337-b845-44550f661854>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/5e3a10ee-ebd9-4854-9bc4-98f9fa09ddb7> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5e3a10ee-ebd9-4854-9bc4-98f9fa09ddb7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/5e3a10ee-ebd9-4854-9bc4-98f9fa09ddb7> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5e3a10ee-ebd9-4854-9bc4-98f9fa09ddb7>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5e3a10ee-ebd9-4854-9bc4-98f9fa09ddb7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
This is a [Shapes Constraint Language (SHACL)](https://www.w3.org/TR/shacl/) file that specifies validation rules for testing RDF data claiming conformance to the W3C's Sensor, Observation, Sample, and Actuator (SOSA) ontology, as needed by the Biodiversity Data Repository (BDR) Note that this is not an official SOSA validator, only a part-validator for elements of SOSA relevant to the BDR.
Checks that the value for usedProcedure is an IRI
Objects for the predicate sosa:usedProcedure must be IRIs
An RDF vocabulary extending SKOS and allowing the description and linking of lexical entities.
If C skosxl:altLabel L and L skosxl:literalForm V, then X skos:altLabel V.
The property skosxl:altLabel is used to associate an skosxl:Label with a skos:Concept. The property is analogous to skos:altLabel.
If C skosxl:hiddenLabel L and L skosxl:literalForm V, then C skos:hiddenLabel V.
The property skosxl:hiddenLabel is used to associate an skosxl:Label with a skos:Concept. The property is analogous to skos:hiddenLabel.
skosxl:labelRelation is not intended to be used directly, but rather as the basis for a design pattern which can be refined for more specific labeling scenarios.
The property skosxl:labelRelation is used for representing binary ('direct') relations between instances of the class skosxl:Label.
If C skosxl:prefLabel L and L skosxl:literalForm V, then X skos:prefLabel V.
The property skosxl:prefLabel is used to associate an skosxl:Label with a skos:Concept. The property is analogous to skos:prefLabel.
If two instances of the class skosxl:Label have the same literal form, they are not necessarily the same resource.
The range of skosxl:literalForm is the class of RDF plain literals.
The property skosxl:literalForm is used to give the literal form of an skosxl:Label.
Link to a member within a collection of (observations) or (collections of observations) that share the same value for one or more of the characteristic properties
should match a property chain something like this but with sosa:isSampleOf* owl:propertyChainAxiom ( sosa:hasFeatureOfInterest sosa:isSampleOf )
The classes, properties, and axioms in this RDF graph are described in https://www.w3.org/TR/vocab-ssn-ext/ Their status is non-normative, and SSN applications are not required to recognize or support them.
Some extensions to the SSN Ontology, to support 1. discovery and use of observation and sample data through links to an ultimate feature-of-interest, or sample 2. observations are made as part of a set or collection, in which one or more of the observation properties - hasFeatureOfInterest, observedProperty, madeBySensor, usedProcedure, phenomenonTime, resultTime - are shared by all members of the collection. These extensions to the SSN Ontology are packaged in a separate RDF graph to enable loading and use if required.
Collection of observations, typically with one or more property shared by all of its members
If values are not provided for the following Observation properties, they may be provided by the ObservationCollection of which it is a member: - hasFeatureOfInterest - hasUltimateFeatureOfInterest - madeBySensor - observedProperty - phenomenonTime - resultTime - usedProcedure
link to the original sample that is related to the context sample through a chain of isSampleOf relations
link to the ultimate feature of interest of the context sample - i.e. the end of a chain of isSampleOf relations
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/eb69a524-0aa1-4166-a596-d43dbe5ae08f> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/eb69a524-0aa1-4166-a596-d43dbe5ae08f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/eb69a524-0aa1-4166-a596-d43dbe5ae08f> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
Observations following the Enhanced Soil Sub-Pit and Soil Metagenomics protocol are made in the context of a site visit.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/eb69a524-0aa1-4166-a596-d43dbe5ae08f>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/9a1ab016-60d6-4876-a751-b25ccb734c2d>`. `<https://linked.data.gov.au/def/nrm/9a1ab016-60d6-4876-a751-b25ccb734c2d>` is the IRI for "Enhanced Soil Sub-Pit and Soil Metagenomics protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/9a1ab016-60d6-4876-a751-b25ccb734c2d`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/eb69a524-0aa1-4166-a596-d43dbe5ae08f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/5e49d84f-eb74-420a-9bee-afedcae264ea> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5e49d84f-eb74-420a-9bee-afedcae264ea>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/5e49d84f-eb74-420a-9bee-afedcae264ea> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5e49d84f-eb74-420a-9bee-afedcae264ea>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5e49d84f-eb74-420a-9bee-afedcae264ea>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
TERN's ecologists have determined the feature type is _soil profile_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/80c39b95-0912-4267-bb66-2fa081683723[`soil profile`].
Observations following the Soil Sample Pit are made in the context of a site visit.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/1c83a60d-12e5-4bb3-b876-7eb97da79fa9>`. `<https://linked.data.gov.au/def/nrm/1c83a60d-12e5-4bb3-b876-7eb97da79fa9>` is the IRI for "Soil Sample Pit".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/1c83a60d-12e5-4bb3-b876-7eb97da79fa9`.
TERN's ecologists have determined the feature type is _soil sample_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/06461021-a6c2-4175-9651-23653c2b9116[`soil sample`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/460784be-8ad5-4c32-b171-93d69984c0b9>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
Observations following the Soil Bulk Density Protocol are made in the context of a site visit.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/460784be-8ad5-4c32-b171-93d69984c0b9>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
Result value's unit of measure _MUST_ have the value `unit:GM-PER-CentiM3`.
The result _MUST_ have `unit:GM-PER-CentiM3` as the value for `tern:unit`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/460784be-8ad5-4c32-b171-93d69984c0b9> ; sosa:hasResult ?this . }
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/d9e6739a-c2dd-4619-be43-1251449a6436>`. `<https://linked.data.gov.au/def/nrm/d9e6739a-c2dd-4619-be43-1251449a6436>` is the IRI for "Soil Bulk Density Protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/d9e6739a-c2dd-4619-be43-1251449a6436`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/460784be-8ad5-4c32-b171-93d69984c0b9>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 1 and 2 inclusive.
The result _MUST_ have a value between 1 and 2 inclusively.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a344d029-4b47-455e-89d9-a1040877a5ce>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a344d029-4b47-455e-89d9-a1040877a5ce>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/a344d029-4b47-455e-89d9-a1040877a5ce> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a344d029-4b47-455e-89d9-a1040877a5ce>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ec510708-9ac1-4c8a-bfe2-31ba5bb693da>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ec510708-9ac1-4c8a-bfe2-31ba5bb693da>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/ec510708-9ac1-4c8a-bfe2-31ba5bb693da> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ec510708-9ac1-4c8a-bfe2-31ba5bb693da>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/02ae5760-c028-460a-837a-d1e3d997e744>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the soil ASC family criterias controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the soil ASC family criterias controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/02ae5760-c028-460a-837a-d1e3d997e744> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'4fd9daef-a132-4f20-b4b3-3ede888a015a'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/02ae5760-c028-460a-837a-d1e3d997e744> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
Observations following the Soil Site Observation and Pit Characterization are made in the context of a site visit.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/02ae5760-c028-460a-837a-d1e3d997e744>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/8f00b7c6-34b4-4203-8dcc-4be47f21d7db>`. `<https://linked.data.gov.au/def/nrm/8f00b7c6-34b4-4203-8dcc-4be47f21d7db>` is the IRI for "Soil Site Observation and Pit Characterization".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/8f00b7c6-34b4-4203-8dcc-4be47f21d7db`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/02ae5760-c028-460a-837a-d1e3d997e744>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/4fd9daef-a132-4f20-b4b3-3ede888a015a>`. `<https://linked.data.gov.au/def/nrm/4fd9daef-a132-4f20-b4b3-3ede888a015a>` is the IRI for "soil ASC family criterias".
The value of `tern:vocabulary` _MUST_ match the pattern `4fd9daef-a132-4f20-b4b3-3ede888a015a$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8ac01d1e-8ad1-4832-98bd-170a89efca33>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil asc classes controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil asc classes controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/8ac01d1e-8ad1-4832-98bd-170a89efca33> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'430ebf92-824e-4dc6-9410-2b454fe8a063'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/8ac01d1e-8ad1-4832-98bd-170a89efca33> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8ac01d1e-8ad1-4832-98bd-170a89efca33>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8ac01d1e-8ad1-4832-98bd-170a89efca33>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/430ebf92-824e-4dc6-9410-2b454fe8a063>`. `<https://linked.data.gov.au/def/nrm/430ebf92-824e-4dc6-9410-2b454fe8a063>` is the IRI for "Soil asc classes".
The value of `tern:vocabulary` _MUST_ match the pattern `430ebf92-824e-4dc6-9410-2b454fe8a063$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/1b7d133f-4d43-47d7-a6c5-8a98f505675e>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil asc orders controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil asc orders controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/1b7d133f-4d43-47d7-a6c5-8a98f505675e> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'cd377ef2-2174-4c7b-a6ef-7e0b1f83b85a'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/1b7d133f-4d43-47d7-a6c5-8a98f505675e> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/1b7d133f-4d43-47d7-a6c5-8a98f505675e>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/1b7d133f-4d43-47d7-a6c5-8a98f505675e>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/cd377ef2-2174-4c7b-a6ef-7e0b1f83b85a>`. `<https://linked.data.gov.au/def/nrm/cd377ef2-2174-4c7b-a6ef-7e0b1f83b85a>` is the IRI for "Soil asc orders".
The value of `tern:vocabulary` _MUST_ match the pattern `cd377ef2-2174-4c7b-a6ef-7e0b1f83b85a$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/cd334597-fedc-40cd-86e4-71295d8a222f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/cd334597-fedc-40cd-86e4-71295d8a222f> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/cd334597-fedc-40cd-86e4-71295d8a222f> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/cd334597-fedc-40cd-86e4-71295d8a222f>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/cd334597-fedc-40cd-86e4-71295d8a222f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/856d1030-f3db-4347-9c56-05d576ddcecd>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/856d1030-f3db-4347-9c56-05d576ddcecd> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/856d1030-f3db-4347-9c56-05d576ddcecd> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/856d1030-f3db-4347-9c56-05d576ddcecd>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/856d1030-f3db-4347-9c56-05d576ddcecd>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
TERN's ecologists have determined the feature type is _soil horizon_, defined by the link:https://www.publish.csiro.au/book/5230/[Australian Soil and Land Survey Field Handbook].
The value of `tern:featureType` _MUST_ be link: http://linked.data.gov.au/def/tern-cv/de1e18e4-6cfd-4c78-b389-a5b1dd04b899[`soil horizon`].
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e38d6585-30f4-4a50-bb3f-f9481ce9c595>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil coarse fragment alteration types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil coarse fragment alteration types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/e38d6585-30f4-4a50-bb3f-f9481ce9c595> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'87f4f5fc-d24d-4865-9b11-9ca9ac5e159f'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/e38d6585-30f4-4a50-bb3f-f9481ce9c595> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e38d6585-30f4-4a50-bb3f-f9481ce9c595>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e38d6585-30f4-4a50-bb3f-f9481ce9c595>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/87f4f5fc-d24d-4865-9b11-9ca9ac5e159f>`. `<https://linked.data.gov.au/def/nrm/87f4f5fc-d24d-4865-9b11-9ca9ac5e159f>` is the IRI for "Soil coarse fragment alteration types".
The value of `tern:vocabulary` _MUST_ match the pattern `87f4f5fc-d24d-4865-9b11-9ca9ac5e159f$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/944cf34d-4d88-4ddd-9464-c0653251ea43>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the coarse fragment distributions controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the coarse fragment distributions controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/944cf34d-4d88-4ddd-9464-c0653251ea43> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'0d2a417d-7ec0-424a-b7ea-45e3af09ce59'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/944cf34d-4d88-4ddd-9464-c0653251ea43> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/944cf34d-4d88-4ddd-9464-c0653251ea43>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/944cf34d-4d88-4ddd-9464-c0653251ea43>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/0d2a417d-7ec0-424a-b7ea-45e3af09ce59>`. `<https://linked.data.gov.au/def/nrm/0d2a417d-7ec0-424a-b7ea-45e3af09ce59>` is the IRI for "coarse fragment distributions".
The value of `tern:vocabulary` _MUST_ match the pattern `0d2a417d-7ec0-424a-b7ea-45e3af09ce59$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/7739f6d5-06dd-42da-82ae-763fd62ff0f0>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil coarse fragment strength types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil coarse fragment strength types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/7739f6d5-06dd-42da-82ae-763fd62ff0f0> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'1ac1c1c1-5a64-47e4-b593-aabfefd57e46'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/7739f6d5-06dd-42da-82ae-763fd62ff0f0> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/7739f6d5-06dd-42da-82ae-763fd62ff0f0>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/7739f6d5-06dd-42da-82ae-763fd62ff0f0>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/1ac1c1c1-5a64-47e4-b593-aabfefd57e46>`. `<https://linked.data.gov.au/def/nrm/1ac1c1c1-5a64-47e4-b593-aabfefd57e46>` is the IRI for "Soil coarse fragment strength types".
The value of `tern:vocabulary` _MUST_ match the pattern `1ac1c1c1-5a64-47e4-b593-aabfefd57e46$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/d83560e6-0356-446e-a8b5-e64b82e3c362>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil coarse fragment shapes controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil coarse fragment shapes controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/d83560e6-0356-446e-a8b5-e64b82e3c362> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'13c84b19-e2bb-48c4-93db-465bcad2dbb5'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/d83560e6-0356-446e-a8b5-e64b82e3c362> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/d83560e6-0356-446e-a8b5-e64b82e3c362>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/d83560e6-0356-446e-a8b5-e64b82e3c362>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/13c84b19-e2bb-48c4-93db-465bcad2dbb5>`. `<https://linked.data.gov.au/def/nrm/13c84b19-e2bb-48c4-93db-465bcad2dbb5>` is the IRI for "Soil coarse fragment shapes".
The value of `tern:vocabulary` _MUST_ match the pattern `13c84b19-e2bb-48c4-93db-465bcad2dbb5$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/9fc1503b-e690-41f0-a824-99f0e69699f1>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil erosion types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil erosion types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/9fc1503b-e690-41f0-a824-99f0e69699f1> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'4f3d9522-e612-40ef-ab8a-7d77960c9f8f'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/9fc1503b-e690-41f0-a824-99f0e69699f1> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/9fc1503b-e690-41f0-a824-99f0e69699f1>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/9fc1503b-e690-41f0-a824-99f0e69699f1>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/4f3d9522-e612-40ef-ab8a-7d77960c9f8f>`. `<https://linked.data.gov.au/def/nrm/4f3d9522-e612-40ef-ab8a-7d77960c9f8f>` is the IRI for "Soil erosion types".
The value of `tern:vocabulary` _MUST_ match the pattern `4f3d9522-e612-40ef-ab8a-7d77960c9f8f$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0408a67f-2448-4151-bc1e-d97b6ff34e4f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil fine macropore abundance types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil fine macropore abundance types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0408a67f-2448-4151-bc1e-d97b6ff34e4f> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'5c685afb-1a56-4261-93f1-8440fbc65ef3'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/0408a67f-2448-4151-bc1e-d97b6ff34e4f> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0408a67f-2448-4151-bc1e-d97b6ff34e4f>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/0408a67f-2448-4151-bc1e-d97b6ff34e4f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/5c685afb-1a56-4261-93f1-8440fbc65ef3>`. `<https://linked.data.gov.au/def/nrm/5c685afb-1a56-4261-93f1-8440fbc65ef3>` is the IRI for "Soil fine macropore abundance types".
The value of `tern:vocabulary` _MUST_ match the pattern `5c685afb-1a56-4261-93f1-8440fbc65ef3$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/181f2d40-8cb7-4b0e-83cb-90ca77b6327f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil horizon boundary distinctness types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil horizon boundary distinctness types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/181f2d40-8cb7-4b0e-83cb-90ca77b6327f> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'1c6b54da-bb31-4496-974e-050531b15e30'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/181f2d40-8cb7-4b0e-83cb-90ca77b6327f> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/181f2d40-8cb7-4b0e-83cb-90ca77b6327f>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/181f2d40-8cb7-4b0e-83cb-90ca77b6327f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/1c6b54da-bb31-4496-974e-050531b15e30>`. `<https://linked.data.gov.au/def/nrm/1c6b54da-bb31-4496-974e-050531b15e30>` is the IRI for "Soil horizon boundary distinctness types".
The value of `tern:vocabulary` _MUST_ match the pattern `1c6b54da-bb31-4496-974e-050531b15e30$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ee03aeec-28ef-4910-94af-338a981bb40d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil horizon boundary shapes controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil horizon boundary shapes controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/ee03aeec-28ef-4910-94af-338a981bb40d> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'2f514fb5-6c23-4fff-beed-858722a0f586'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/ee03aeec-28ef-4910-94af-338a981bb40d> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ee03aeec-28ef-4910-94af-338a981bb40d>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ee03aeec-28ef-4910-94af-338a981bb40d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/2f514fb5-6c23-4fff-beed-858722a0f586>`. `<https://linked.data.gov.au/def/nrm/2f514fb5-6c23-4fff-beed-858722a0f586>` is the IRI for "Soil horizon boundary shapes".
The value of `tern:vocabulary` _MUST_ match the pattern `2f514fb5-6c23-4fff-beed-858722a0f586$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/277f9c3d-4031-4935-886b-7b83c7513688>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the locations within landform element controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the locations within landform element controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/277f9c3d-4031-4935-886b-7b83c7513688> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'c5546283-dee6-475f-b139-81da028d0a96'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/277f9c3d-4031-4935-886b-7b83c7513688> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/277f9c3d-4031-4935-886b-7b83c7513688>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/277f9c3d-4031-4935-886b-7b83c7513688>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/c5546283-dee6-475f-b139-81da028d0a96>`. `<https://linked.data.gov.au/def/nrm/c5546283-dee6-475f-b139-81da028d0a96>` is the IRI for "locations within landform element".
The value of `tern:vocabulary` _MUST_ match the pattern `c5546283-dee6-475f-b139-81da028d0a96$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/796022f7-ccba-419a-8f70-020ee9e8e3f8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil macropore diameter classes controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil macropore diameter classes controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/796022f7-ccba-419a-8f70-020ee9e8e3f8> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'3c3ccc22-949a-4892-9c51-7b458a823fcd'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/796022f7-ccba-419a-8f70-020ee9e8e3f8> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/796022f7-ccba-419a-8f70-020ee9e8e3f8>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/796022f7-ccba-419a-8f70-020ee9e8e3f8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/3c3ccc22-949a-4892-9c51-7b458a823fcd>`. `<https://linked.data.gov.au/def/nrm/3c3ccc22-949a-4892-9c51-7b458a823fcd>` is the IRI for "Soil macropore diameter classes".
The value of `tern:vocabulary` _MUST_ match the pattern `3c3ccc22-949a-4892-9c51-7b458a823fcd$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c0512e0a-98dd-4f38-8db9-db79769457bf>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil medium macropore abundance types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil medium macropore abundance types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/c0512e0a-98dd-4f38-8db9-db79769457bf> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'ee3a4058-d8de-43b8-a002-3f072f039b75'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/c0512e0a-98dd-4f38-8db9-db79769457bf> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c0512e0a-98dd-4f38-8db9-db79769457bf>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c0512e0a-98dd-4f38-8db9-db79769457bf>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/ee3a4058-d8de-43b8-a002-3f072f039b75>`. `<https://linked.data.gov.au/def/nrm/ee3a4058-d8de-43b8-a002-3f072f039b75>` is the IRI for "Soil medium macropore abundance types".
The value of `tern:vocabulary` _MUST_ match the pattern `ee3a4058-d8de-43b8-a002-3f072f039b75$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/22caefc0-0201-4bf2-a108-ef173d607bf4>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/22caefc0-0201-4bf2-a108-ef173d607bf4>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/22caefc0-0201-4bf2-a108-ef173d607bf4> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/22caefc0-0201-4bf2-a108-ef173d607bf4>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/2f87b7cc-c029-4784-92cf-c32055b5c9b7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/2f87b7cc-c029-4784-92cf-c32055b5c9b7>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/2f87b7cc-c029-4784-92cf-c32055b5c9b7> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/2f87b7cc-c029-4784-92cf-c32055b5c9b7>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/cfd6aa2d-118a-497d-901c-29b10ce8dfae>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the plant root abundances controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the plant root abundances controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/cfd6aa2d-118a-497d-901c-29b10ce8dfae> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'65ae0e16-e2a9-4b6c-9ac2-d68a499df23f'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/cfd6aa2d-118a-497d-901c-29b10ce8dfae> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/cfd6aa2d-118a-497d-901c-29b10ce8dfae>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/cfd6aa2d-118a-497d-901c-29b10ce8dfae>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/65ae0e16-e2a9-4b6c-9ac2-d68a499df23f>`. `<https://linked.data.gov.au/def/nrm/65ae0e16-e2a9-4b6c-9ac2-d68a499df23f>` is the IRI for "plant root abundances".
The value of `tern:vocabulary` _MUST_ match the pattern `65ae0e16-e2a9-4b6c-9ac2-d68a499df23f$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/366ff48a-3d1f-4f73-8f6f-31bd650e7997>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the plant root sizes controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the plant root sizes controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/366ff48a-3d1f-4f73-8f6f-31bd650e7997> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'d6c277b9-885f-48c8-a5de-842130a0d1e6'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/366ff48a-3d1f-4f73-8f6f-31bd650e7997> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/366ff48a-3d1f-4f73-8f6f-31bd650e7997>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/366ff48a-3d1f-4f73-8f6f-31bd650e7997>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/d6c277b9-885f-48c8-a5de-842130a0d1e6>`. `<https://linked.data.gov.au/def/nrm/d6c277b9-885f-48c8-a5de-842130a0d1e6>` is the IRI for "plant root sizes".
The value of `tern:vocabulary` _MUST_ match the pattern `d6c277b9-885f-48c8-a5de-842130a0d1e6$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ee463caf-8310-49be-82f7-12ef1cd11d3a>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ee463caf-8310-49be-82f7-12ef1cd11d3a>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/ee463caf-8310-49be-82f7-12ef1cd11d3a> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/ee463caf-8310-49be-82f7-12ef1cd11d3a>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/30453b41-80b6-42d8-a388-893188414738>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil relative inclination of slope elements controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil relative inclination of slope elements controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/30453b41-80b6-42d8-a388-893188414738> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'844f1b7a-6a65-4994-9526-c337d84a7652'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/30453b41-80b6-42d8-a388-893188414738> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/30453b41-80b6-42d8-a388-893188414738>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/30453b41-80b6-42d8-a388-893188414738>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/844f1b7a-6a65-4994-9526-c337d84a7652>`. `<https://linked.data.gov.au/def/nrm/844f1b7a-6a65-4994-9526-c337d84a7652>` is the IRI for "Soil relative inclination of slope elements".
The value of `tern:vocabulary` _MUST_ match the pattern `844f1b7a-6a65-4994-9526-c337d84a7652$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/fc03df84-7ac9-47c6-9b7b-1da3dcb36364>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil rock outcrop abundance types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil rock outcrop abundance types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/fc03df84-7ac9-47c6-9b7b-1da3dcb36364> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'c06f57b7-fde3-47c6-b410-8db0ec7e68e1'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/fc03df84-7ac9-47c6-9b7b-1da3dcb36364> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/fc03df84-7ac9-47c6-9b7b-1da3dcb36364>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/fc03df84-7ac9-47c6-9b7b-1da3dcb36364>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/c06f57b7-fde3-47c6-b410-8db0ec7e68e1>`. `<https://linked.data.gov.au/def/nrm/c06f57b7-fde3-47c6-b410-8db0ec7e68e1>` is the IRI for "Soil rock outcrop abundance types".
The value of `tern:vocabulary` _MUST_ match the pattern `c06f57b7-fde3-47c6-b410-8db0ec7e68e1$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b023d177-2c9b-4d58-86e6-099b742fcf1c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil morphological types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil morphological types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/b023d177-2c9b-4d58-86e6-099b742fcf1c> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'50e0e5aa-3abf-4883-a713-245701efe314'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/b023d177-2c9b-4d58-86e6-099b742fcf1c> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b023d177-2c9b-4d58-86e6-099b742fcf1c>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b023d177-2c9b-4d58-86e6-099b742fcf1c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/50e0e5aa-3abf-4883-a713-245701efe314>`. `<https://linked.data.gov.au/def/nrm/50e0e5aa-3abf-4883-a713-245701efe314>` is the IRI for "Soil morphological types".
The value of `tern:vocabulary` _MUST_ match the pattern `50e0e5aa-3abf-4883-a713-245701efe314$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/d6b47f65-f99b-4111-b339-6be65b421240>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the soil colours - chroma controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the soil colours - chroma controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/d6b47f65-f99b-4111-b339-6be65b421240> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'aed1c2ff-4477-4e60-9c18-4e38f69e9144'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/d6b47f65-f99b-4111-b339-6be65b421240> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/d6b47f65-f99b-4111-b339-6be65b421240>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/d6b47f65-f99b-4111-b339-6be65b421240>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/aed1c2ff-4477-4e60-9c18-4e38f69e9144>`. `<https://linked.data.gov.au/def/nrm/aed1c2ff-4477-4e60-9c18-4e38f69e9144>` is the IRI for "soil colours - chroma".
The value of `tern:vocabulary` _MUST_ match the pattern `aed1c2ff-4477-4e60-9c18-4e38f69e9144$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8ee67cc6-4f95-4762-83d0-686e35ed3889>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the soil colours - hue controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the soil colours - hue controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/8ee67cc6-4f95-4762-83d0-686e35ed3889> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'fcc14073-0a36-494b-b757-1a74a327e46e'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/8ee67cc6-4f95-4762-83d0-686e35ed3889> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8ee67cc6-4f95-4762-83d0-686e35ed3889>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8ee67cc6-4f95-4762-83d0-686e35ed3889>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/fcc14073-0a36-494b-b757-1a74a327e46e>`. `<https://linked.data.gov.au/def/nrm/fcc14073-0a36-494b-b757-1a74a327e46e>` is the IRI for "soil colours - hue".
The value of `tern:vocabulary` _MUST_ match the pattern `fcc14073-0a36-494b-b757-1a74a327e46e$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5e211f9e-e7c2-4d31-b0db-5c358fc9be63>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the soil colours - value controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the soil colours - value controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/5e211f9e-e7c2-4d31-b0db-5c358fc9be63> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'b8e47630-b306-41f2-a511-dffc6f98c595'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/5e211f9e-e7c2-4d31-b0db-5c358fc9be63> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5e211f9e-e7c2-4d31-b0db-5c358fc9be63>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5e211f9e-e7c2-4d31-b0db-5c358fc9be63>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/b8e47630-b306-41f2-a511-dffc6f98c595>`. `<https://linked.data.gov.au/def/nrm/b8e47630-b306-41f2-a511-dffc6f98c595>` is the IRI for "soil colours - value".
The value of `tern:vocabulary` _MUST_ match the pattern `b8e47630-b306-41f2-a511-dffc6f98c595$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/9f7e048a-09e3-409d-a821-87c52a449412>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the soil consistency - plasticity types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the soil consistency - plasticity types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/9f7e048a-09e3-409d-a821-87c52a449412> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'fa24073b-145b-40e7-b79e-53f19f66012c'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/9f7e048a-09e3-409d-a821-87c52a449412> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/9f7e048a-09e3-409d-a821-87c52a449412>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/9f7e048a-09e3-409d-a821-87c52a449412>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/fa24073b-145b-40e7-b79e-53f19f66012c>`. `<https://linked.data.gov.au/def/nrm/fa24073b-145b-40e7-b79e-53f19f66012c>` is the IRI for "soil consistency - plasticity types".
The value of `tern:vocabulary` _MUST_ match the pattern `fa24073b-145b-40e7-b79e-53f19f66012c$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c8a1d968-36b1-4443-bd26-7f04a1bce78f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the soil consistency stickinesses controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the soil consistency stickinesses controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/c8a1d968-36b1-4443-bd26-7f04a1bce78f> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'09623c62-d6a0-4fe5-9614-2c271212e8b7'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/c8a1d968-36b1-4443-bd26-7f04a1bce78f> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c8a1d968-36b1-4443-bd26-7f04a1bce78f>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c8a1d968-36b1-4443-bd26-7f04a1bce78f>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/09623c62-d6a0-4fe5-9614-2c271212e8b7>`. `<https://linked.data.gov.au/def/nrm/09623c62-d6a0-4fe5-9614-2c271212e8b7>` is the IRI for "soil consistency stickinesses".
The value of `tern:vocabulary` _MUST_ match the pattern `09623c62-d6a0-4fe5-9614-2c271212e8b7$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6b2ba4eb-89d1-46bd-a845-f0b32d129806>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil strengths controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil strengths controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/6b2ba4eb-89d1-46bd-a845-f0b32d129806> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'9f599dbb-458f-4d8a-846a-fd1a080f8853'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/6b2ba4eb-89d1-46bd-a845-f0b32d129806> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6b2ba4eb-89d1-46bd-a845-f0b32d129806>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/6b2ba4eb-89d1-46bd-a845-f0b32d129806>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/9f599dbb-458f-4d8a-846a-fd1a080f8853>`. `<https://linked.data.gov.au/def/nrm/9f599dbb-458f-4d8a-846a-fd1a080f8853>` is the IRI for "Soil strengths".
The value of `tern:vocabulary` _MUST_ match the pattern `9f599dbb-458f-4d8a-846a-fd1a080f8853$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/74281a72-db08-4928-83a9-956187e06528>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil consistency- water statuses controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil consistency- water statuses controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/74281a72-db08-4928-83a9-956187e06528> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'e1573937-3a4e-4df6-beba-29e25e7c5596'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/74281a72-db08-4928-83a9-956187e06528> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/74281a72-db08-4928-83a9-956187e06528>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/74281a72-db08-4928-83a9-956187e06528>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/e1573937-3a4e-4df6-beba-29e25e7c5596>`. `<https://linked.data.gov.au/def/nrm/e1573937-3a4e-4df6-beba-29e25e7c5596>` is the IRI for "Soil consistency- water statuses".
The value of `tern:vocabulary` _MUST_ match the pattern `e1573937-3a4e-4df6-beba-29e25e7c5596$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/90dc7158-cc88-45ba-ad74-be80321e0344>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil cutan abundance types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil cutan abundance types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/90dc7158-cc88-45ba-ad74-be80321e0344> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'984fbd63-e521-4fef-80f9-bcb9307a76a9'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/90dc7158-cc88-45ba-ad74-be80321e0344> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/90dc7158-cc88-45ba-ad74-be80321e0344>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/90dc7158-cc88-45ba-ad74-be80321e0344>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/984fbd63-e521-4fef-80f9-bcb9307a76a9>`. `<https://linked.data.gov.au/def/nrm/984fbd63-e521-4fef-80f9-bcb9307a76a9>` is the IRI for "Soil cutan abundance types".
The value of `tern:vocabulary` _MUST_ match the pattern `984fbd63-e521-4fef-80f9-bcb9307a76a9$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/7cd4d597-be78-4c0e-b2b2-7a1206870974>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil cutan distinctness types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil cutan distinctness types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/7cd4d597-be78-4c0e-b2b2-7a1206870974> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'e9ea1cd7-4e33-4086-b0ce-cd2f00c2b8ad'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/7cd4d597-be78-4c0e-b2b2-7a1206870974> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/7cd4d597-be78-4c0e-b2b2-7a1206870974>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/7cd4d597-be78-4c0e-b2b2-7a1206870974>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/e9ea1cd7-4e33-4086-b0ce-cd2f00c2b8ad>`. `<https://linked.data.gov.au/def/nrm/e9ea1cd7-4e33-4086-b0ce-cd2f00c2b8ad>` is the IRI for "Soil cutan distinctness types".
The value of `tern:vocabulary` _MUST_ match the pattern `e9ea1cd7-4e33-4086-b0ce-cd2f00c2b8ad$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/786d4846-5b75-4b11-aba0-71fa40fd180a>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil cutan types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil cutan types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/786d4846-5b75-4b11-aba0-71fa40fd180a> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'e2e7323b-774a-4be0-a40d-2d52e042dd17'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/786d4846-5b75-4b11-aba0-71fa40fd180a> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/786d4846-5b75-4b11-aba0-71fa40fd180a>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/786d4846-5b75-4b11-aba0-71fa40fd180a>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/e2e7323b-774a-4be0-a40d-2d52e042dd17>`. `<https://linked.data.gov.au/def/nrm/e2e7323b-774a-4be0-a40d-2d52e042dd17>` is the IRI for "Soil cutan types".
The value of `tern:vocabulary` _MUST_ match the pattern `e2e7323b-774a-4be0-a40d-2d52e042dd17$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/1a8ca840-af43-41f2-bc69-965894bccd1a>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil field dispersion scores controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil field dispersion scores controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/1a8ca840-af43-41f2-bc69-965894bccd1a> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'0e0a3e73-4b7a-4ffb-8b91-ee0748688bb1'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/1a8ca840-af43-41f2-bc69-965894bccd1a> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/1a8ca840-af43-41f2-bc69-965894bccd1a>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/1a8ca840-af43-41f2-bc69-965894bccd1a>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/0e0a3e73-4b7a-4ffb-8b91-ee0748688bb1>`. `<https://linked.data.gov.au/def/nrm/0e0a3e73-4b7a-4ffb-8b91-ee0748688bb1>` is the IRI for "Soil field dispersion scores".
The value of `tern:vocabulary` _MUST_ match the pattern `0e0a3e73-4b7a-4ffb-8b91-ee0748688bb1$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c4ae89f9-49cb-4be8-b5f2-5f08177b8093>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil drainage types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil drainage types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/c4ae89f9-49cb-4be8-b5f2-5f08177b8093> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'0c9132dc-48bf-4a9c-ac9b-0c8b1909afb4'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/c4ae89f9-49cb-4be8-b5f2-5f08177b8093> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c4ae89f9-49cb-4be8-b5f2-5f08177b8093>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c4ae89f9-49cb-4be8-b5f2-5f08177b8093>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/0c9132dc-48bf-4a9c-ac9b-0c8b1909afb4>`. `<https://linked.data.gov.au/def/nrm/0c9132dc-48bf-4a9c-ac9b-0c8b1909afb4>` is the IRI for "Soil drainage types".
The value of `tern:vocabulary` _MUST_ match the pattern `0c9132dc-48bf-4a9c-ac9b-0c8b1909afb4$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/bfe1e9d6-4040-45c1-a2a9-bcb634b745ac>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil effervescence types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil effervescence types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/bfe1e9d6-4040-45c1-a2a9-bcb634b745ac> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'4f3a874f-4629-498a-b270-6880ca43b3a6'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/bfe1e9d6-4040-45c1-a2a9-bcb634b745ac> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/bfe1e9d6-4040-45c1-a2a9-bcb634b745ac>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/bfe1e9d6-4040-45c1-a2a9-bcb634b745ac>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/4f3a874f-4629-498a-b270-6880ca43b3a6>`. `<https://linked.data.gov.au/def/nrm/4f3a874f-4629-498a-b270-6880ca43b3a6>` is the IRI for "Soil effervescence types".
The value of `tern:vocabulary` _MUST_ match the pattern `4f3a874f-4629-498a-b270-6880ca43b3a6$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/22815fee-434e-4e21-b85f-8005a669a865>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/22815fee-434e-4e21-b85f-8005a669a865>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
Result value's unit of measure _MUST_ have the value `unit:S-PER-M`.
The result _MUST_ have `unit:S-PER-M` as the value for `tern:unit`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/22815fee-434e-4e21-b85f-8005a669a865> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/22815fee-434e-4e21-b85f-8005a669a865>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 10^(-18) and 10^7 inclusive.
The result _MUST_ have a value between 10^(-18) and 10^7 inclusively.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/739eb13d-5d01-4ffe-b801-8720f65b813a>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/739eb13d-5d01-4ffe-b801-8720f65b813a>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/739eb13d-5d01-4ffe-b801-8720f65b813a> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/739eb13d-5d01-4ffe-b801-8720f65b813a>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3c5263b7-8104-46a9-af05-a0c33aadde07>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil erosion states controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil erosion states controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3c5263b7-8104-46a9-af05-a0c33aadde07> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'e7087186-7027-42c3-ab54-b65a39034dd1'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3c5263b7-8104-46a9-af05-a0c33aadde07> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3c5263b7-8104-46a9-af05-a0c33aadde07>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3c5263b7-8104-46a9-af05-a0c33aadde07>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/e7087186-7027-42c3-ab54-b65a39034dd1>`. `<https://linked.data.gov.au/def/nrm/e7087186-7027-42c3-ab54-b65a39034dd1>` is the IRI for "Soil erosion states".
The value of `tern:vocabulary` _MUST_ match the pattern `e7087186-7027-42c3-ab54-b65a39034dd1$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e2c87884-5edf-4d87-a67d-6a13cf59e051>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil gilgal proportions controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil gilgal proportions controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/e2c87884-5edf-4d87-a67d-6a13cf59e051> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'c441cb41-6f65-417c-88b7-2c10375bf3f3'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/e2c87884-5edf-4d87-a67d-6a13cf59e051> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e2c87884-5edf-4d87-a67d-6a13cf59e051>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/e2c87884-5edf-4d87-a67d-6a13cf59e051>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/c441cb41-6f65-417c-88b7-2c10375bf3f3>`. `<https://linked.data.gov.au/def/nrm/c441cb41-6f65-417c-88b7-2c10375bf3f3>` is the IRI for "Soil gilgal proportions".
The value of `tern:vocabulary` _MUST_ match the pattern `c441cb41-6f65-417c-88b7-2c10375bf3f3$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3014409e-fa76-4159-8bd7-0a3bae695545>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil microrelief types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil microrelief types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3014409e-fa76-4159-8bd7-0a3bae695545> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'457faa4f-74e8-4b8a-9e4b-541bb7c50441'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3014409e-fa76-4159-8bd7-0a3bae695545> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3014409e-fa76-4159-8bd7-0a3bae695545>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3014409e-fa76-4159-8bd7-0a3bae695545>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/457faa4f-74e8-4b8a-9e4b-541bb7c50441>`. `<https://linked.data.gov.au/def/nrm/457faa4f-74e8-4b8a-9e4b-541bb7c50441>` is the IRI for "Soil microrelief types".
The value of `tern:vocabulary` _MUST_ match the pattern `457faa4f-74e8-4b8a-9e4b-541bb7c50441$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/759b8562-b416-4fdc-924e-b55288018286>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil moisture statuses controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil moisture statuses controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/759b8562-b416-4fdc-924e-b55288018286> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'a1e434a8-3fbb-4323-a0ae-0e31308eba8b'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/759b8562-b416-4fdc-924e-b55288018286> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/759b8562-b416-4fdc-924e-b55288018286>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/759b8562-b416-4fdc-924e-b55288018286>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/a1e434a8-3fbb-4323-a0ae-0e31308eba8b>`. `<https://linked.data.gov.au/def/nrm/a1e434a8-3fbb-4323-a0ae-0e31308eba8b>` is the IRI for "Soil moisture statuses".
The value of `tern:vocabulary` _MUST_ match the pattern `a1e434a8-3fbb-4323-a0ae-0e31308eba8b$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/049cd754-cdc4-46e3-868f-fefa258522c9>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil mottle abundance types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil mottle abundance types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/049cd754-cdc4-46e3-868f-fefa258522c9> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'100f6f80-d438-465a-8f57-5a76a038b961'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/049cd754-cdc4-46e3-868f-fefa258522c9> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/049cd754-cdc4-46e3-868f-fefa258522c9>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/049cd754-cdc4-46e3-868f-fefa258522c9>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/100f6f80-d438-465a-8f57-5a76a038b961>`. `<https://linked.data.gov.au/def/nrm/100f6f80-d438-465a-8f57-5a76a038b961>` is the IRI for "Soil mottle abundance types".
The value of `tern:vocabulary` _MUST_ match the pattern `100f6f80-d438-465a-8f57-5a76a038b961$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8861378e-8012-4ce4-932b-ed9b3d25de61>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil mottle boundary distinctness types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil mottle boundary distinctness types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/8861378e-8012-4ce4-932b-ed9b3d25de61> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'51622960-af4e-4398-82ca-a17223de1431'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/8861378e-8012-4ce4-932b-ed9b3d25de61> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8861378e-8012-4ce4-932b-ed9b3d25de61>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8861378e-8012-4ce4-932b-ed9b3d25de61>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/51622960-af4e-4398-82ca-a17223de1431>`. `<https://linked.data.gov.au/def/nrm/51622960-af4e-4398-82ca-a17223de1431>` is the IRI for "Soil mottle boundary distinctness types".
The value of `tern:vocabulary` _MUST_ match the pattern `51622960-af4e-4398-82ca-a17223de1431$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a0b98f1c-ebcb-4a06-b5bc-919de1e02331>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil mottle colours controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil mottle colours controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/a0b98f1c-ebcb-4a06-b5bc-919de1e02331> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'a6d2b7d3-fe4f-4bf6-82ce-d53ae951cb7d'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/a0b98f1c-ebcb-4a06-b5bc-919de1e02331> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a0b98f1c-ebcb-4a06-b5bc-919de1e02331>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/a0b98f1c-ebcb-4a06-b5bc-919de1e02331>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/a6d2b7d3-fe4f-4bf6-82ce-d53ae951cb7d>`. `<https://linked.data.gov.au/def/nrm/a6d2b7d3-fe4f-4bf6-82ce-d53ae951cb7d>` is the IRI for "Soil mottle colours".
The value of `tern:vocabulary` _MUST_ match the pattern `a6d2b7d3-fe4f-4bf6-82ce-d53ae951cb7d$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/922aa129-61d2-499e-9f2b-d57f3617737c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil mottle contrast types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil mottle contrast types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/922aa129-61d2-499e-9f2b-d57f3617737c> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'a0f8cc94-abbd-482b-8947-6017bc5f55e5'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/922aa129-61d2-499e-9f2b-d57f3617737c> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/922aa129-61d2-499e-9f2b-d57f3617737c>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/922aa129-61d2-499e-9f2b-d57f3617737c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/a0f8cc94-abbd-482b-8947-6017bc5f55e5>`. `<https://linked.data.gov.au/def/nrm/a0f8cc94-abbd-482b-8947-6017bc5f55e5>` is the IRI for "Soil mottle contrast types".
The value of `tern:vocabulary` _MUST_ match the pattern `a0f8cc94-abbd-482b-8947-6017bc5f55e5$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dd220b97-75b8-4d73-af57-793e431459b6>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil mottle sizes controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil mottle sizes controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/dd220b97-75b8-4d73-af57-793e431459b6> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'c8dd7af4-8e57-4f59-848a-66712349754a'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/dd220b97-75b8-4d73-af57-793e431459b6> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dd220b97-75b8-4d73-af57-793e431459b6>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dd220b97-75b8-4d73-af57-793e431459b6>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/c8dd7af4-8e57-4f59-848a-66712349754a>`. `<https://linked.data.gov.au/def/nrm/c8dd7af4-8e57-4f59-848a-66712349754a>` is the IRI for "Soil mottle sizes".
The value of `tern:vocabulary` _MUST_ match the pattern `c8dd7af4-8e57-4f59-848a-66712349754a$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/79df1f41-1a8e-44af-8362-87ac7944cfc3>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil mottle types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil mottle types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/79df1f41-1a8e-44af-8362-87ac7944cfc3> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'b12461fc-166e-477b-a58c-60682848010e'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/79df1f41-1a8e-44af-8362-87ac7944cfc3> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/79df1f41-1a8e-44af-8362-87ac7944cfc3>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/79df1f41-1a8e-44af-8362-87ac7944cfc3>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/b12461fc-166e-477b-a58c-60682848010e>`. `<https://linked.data.gov.au/def/nrm/b12461fc-166e-477b-a58c-60682848010e>` is the IRI for "Soil mottle types".
The value of `tern:vocabulary` _MUST_ match the pattern `b12461fc-166e-477b-a58c-60682848010e$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/f8993f1e-b4d8-47b8-acdd-a74dd84e845e>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/f8993f1e-b4d8-47b8-acdd-a74dd84e845e>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
Result value's unit of measure _MUST_ have the value `unit:PH`.
The result _MUST_ have `unit:PH` as the value for `tern:unit`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/f8993f1e-b4d8-47b8-acdd-a74dd84e845e> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/f8993f1e-b4d8-47b8-acdd-a74dd84e845e>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
Value _MUST_ be between 0 and 14 inclusive.
The result _MUST_ have a value between 0 and 14 inclusively.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/50baa5cb-43e1-465f-a842-0cf598576eb9>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil pan cementation types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil pan cementation types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/50baa5cb-43e1-465f-a842-0cf598576eb9> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'ad3e7729-fbe4-4b93-8428-74f6ced865c1'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/50baa5cb-43e1-465f-a842-0cf598576eb9> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/50baa5cb-43e1-465f-a842-0cf598576eb9>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/50baa5cb-43e1-465f-a842-0cf598576eb9>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/ad3e7729-fbe4-4b93-8428-74f6ced865c1>`. `<https://linked.data.gov.au/def/nrm/ad3e7729-fbe4-4b93-8428-74f6ced865c1>` is the IRI for "Soil pan cementation types".
The value of `tern:vocabulary` _MUST_ match the pattern `ad3e7729-fbe4-4b93-8428-74f6ced865c1$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/1c64a9a4-aee6-492a-a7cd-a375c2d1da27>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil pan continuity types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil pan continuity types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/1c64a9a4-aee6-492a-a7cd-a375c2d1da27> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'c80e269f-a328-4214-b690-849259e67e75'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/1c64a9a4-aee6-492a-a7cd-a375c2d1da27> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/1c64a9a4-aee6-492a-a7cd-a375c2d1da27>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/1c64a9a4-aee6-492a-a7cd-a375c2d1da27>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/c80e269f-a328-4214-b690-849259e67e75>`. `<https://linked.data.gov.au/def/nrm/c80e269f-a328-4214-b690-849259e67e75>` is the IRI for "Soil pan continuity types".
The value of `tern:vocabulary` _MUST_ match the pattern `c80e269f-a328-4214-b690-849259e67e75$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/151ce1f3-9ff5-456c-b780-806f705d97c6>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil pan structures controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil pan structures controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/151ce1f3-9ff5-456c-b780-806f705d97c6> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'295ca7cc-f6e6-451d-a0de-667fa3187378'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/151ce1f3-9ff5-456c-b780-806f705d97c6> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/151ce1f3-9ff5-456c-b780-806f705d97c6>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/151ce1f3-9ff5-456c-b780-806f705d97c6>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/295ca7cc-f6e6-451d-a0de-667fa3187378>`. `<https://linked.data.gov.au/def/nrm/295ca7cc-f6e6-451d-a0de-667fa3187378>` is the IRI for "Soil pan structures".
The value of `tern:vocabulary` _MUST_ match the pattern `295ca7cc-f6e6-451d-a0de-667fa3187378$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/084ba6fb-0cfd-48a1-bf00-e91c9bc0cea0>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil pan types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil pan types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/084ba6fb-0cfd-48a1-bf00-e91c9bc0cea0> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'995adb71-6439-4cd3-9ece-bb87a8a217c0'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/084ba6fb-0cfd-48a1-bf00-e91c9bc0cea0> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/084ba6fb-0cfd-48a1-bf00-e91c9bc0cea0>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/084ba6fb-0cfd-48a1-bf00-e91c9bc0cea0>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/995adb71-6439-4cd3-9ece-bb87a8a217c0>`. `<https://linked.data.gov.au/def/nrm/995adb71-6439-4cd3-9ece-bb87a8a217c0>` is the IRI for "Soil pan types".
The value of `tern:vocabulary` _MUST_ match the pattern `995adb71-6439-4cd3-9ece-bb87a8a217c0$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3f431e7a-6f1c-4dcd-b452-1cb14226a56d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil permeability types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil permeability types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3f431e7a-6f1c-4dcd-b452-1cb14226a56d> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'41a54b21-b885-4cfd-be09-7bedc4ae4dc4'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3f431e7a-6f1c-4dcd-b452-1cb14226a56d> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3f431e7a-6f1c-4dcd-b452-1cb14226a56d>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3f431e7a-6f1c-4dcd-b452-1cb14226a56d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/41a54b21-b885-4cfd-be09-7bedc4ae4dc4>`. `<https://linked.data.gov.au/def/nrm/41a54b21-b885-4cfd-be09-7bedc4ae4dc4>` is the IRI for "Soil permeability types".
The value of `tern:vocabulary` _MUST_ match the pattern `41a54b21-b885-4cfd-be09-7bedc4ae4dc4$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/38ac1807-fdfe-4b0c-abb4-9e8067ac4456> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/38ac1807-fdfe-4b0c-abb4-9e8067ac4456>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/38ac1807-fdfe-4b0c-abb4-9e8067ac4456> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/38ac1807-fdfe-4b0c-abb4-9e8067ac4456>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/38ac1807-fdfe-4b0c-abb4-9e8067ac4456>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b23d0935-6d2c-4657-a416-1e9f61761bad>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil segregation abundance types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil segregation abundance types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/b23d0935-6d2c-4657-a416-1e9f61761bad> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'9b4820fb-6ee1-439c-8972-f642b9a7b5f8'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/b23d0935-6d2c-4657-a416-1e9f61761bad> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b23d0935-6d2c-4657-a416-1e9f61761bad>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/b23d0935-6d2c-4657-a416-1e9f61761bad>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/9b4820fb-6ee1-439c-8972-f642b9a7b5f8>`. `<https://linked.data.gov.au/def/nrm/9b4820fb-6ee1-439c-8972-f642b9a7b5f8>` is the IRI for "Soil segregation abundance types".
The value of `tern:vocabulary` _MUST_ match the pattern `9b4820fb-6ee1-439c-8972-f642b9a7b5f8$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/898c9bd8-ae04-4917-94b9-75725c050850>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil segregation forms controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil segregation forms controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/898c9bd8-ae04-4917-94b9-75725c050850> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'e2a473c3-a2e3-44fc-a309-a662c6e53542'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/898c9bd8-ae04-4917-94b9-75725c050850> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/898c9bd8-ae04-4917-94b9-75725c050850>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/898c9bd8-ae04-4917-94b9-75725c050850>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/e2a473c3-a2e3-44fc-a309-a662c6e53542>`. `<https://linked.data.gov.au/def/nrm/e2a473c3-a2e3-44fc-a309-a662c6e53542>` is the IRI for "Soil segregation forms".
The value of `tern:vocabulary` _MUST_ match the pattern `e2a473c3-a2e3-44fc-a309-a662c6e53542$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/764d2097-c55e-46c4-a64b-2bc2204c22af>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil segregation magnetic types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil segregation magnetic types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/764d2097-c55e-46c4-a64b-2bc2204c22af> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'f503ff93-f7d7-4419-9d1e-6807e96dc2c1'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/764d2097-c55e-46c4-a64b-2bc2204c22af> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/764d2097-c55e-46c4-a64b-2bc2204c22af>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/764d2097-c55e-46c4-a64b-2bc2204c22af>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/f503ff93-f7d7-4419-9d1e-6807e96dc2c1>`. `<https://linked.data.gov.au/def/nrm/f503ff93-f7d7-4419-9d1e-6807e96dc2c1>` is the IRI for "Soil segregation magnetic types".
The value of `tern:vocabulary` _MUST_ match the pattern `f503ff93-f7d7-4419-9d1e-6807e96dc2c1$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/2884455e-8016-44e9-8b18-5f219c89bd26>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil segregations nature types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil segregations nature types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/2884455e-8016-44e9-8b18-5f219c89bd26> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'2e870427-8563-4d61-b7ac-3556aaf0cbf2'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/2884455e-8016-44e9-8b18-5f219c89bd26> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/2884455e-8016-44e9-8b18-5f219c89bd26>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/2884455e-8016-44e9-8b18-5f219c89bd26>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/2e870427-8563-4d61-b7ac-3556aaf0cbf2>`. `<https://linked.data.gov.au/def/nrm/2e870427-8563-4d61-b7ac-3556aaf0cbf2>` is the IRI for "Soil segregations nature types".
The value of `tern:vocabulary` _MUST_ match the pattern `2e870427-8563-4d61-b7ac-3556aaf0cbf2$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/958da592-ff9b-4110-92f1-c82fe0472de1>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil segregations sizes controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil segregations sizes controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/958da592-ff9b-4110-92f1-c82fe0472de1> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'f795d7e8-1bc9-4efa-98b7-e19717c66282'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/958da592-ff9b-4110-92f1-c82fe0472de1> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/958da592-ff9b-4110-92f1-c82fe0472de1>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/958da592-ff9b-4110-92f1-c82fe0472de1>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/f795d7e8-1bc9-4efa-98b7-e19717c66282>`. `<https://linked.data.gov.au/def/nrm/f795d7e8-1bc9-4efa-98b7-e19717c66282>` is the IRI for "Soil segregations sizes".
The value of `tern:vocabulary` _MUST_ match the pattern `f795d7e8-1bc9-4efa-98b7-e19717c66282$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dc7e53c1-ff9e-47eb-9d0d-594ca31adaef>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil segregation strength types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil segregation strength types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/dc7e53c1-ff9e-47eb-9d0d-594ca31adaef> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'ff36816d-ee76-4c55-a41f-8618ccd3860a'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/dc7e53c1-ff9e-47eb-9d0d-594ca31adaef> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dc7e53c1-ff9e-47eb-9d0d-594ca31adaef>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dc7e53c1-ff9e-47eb-9d0d-594ca31adaef>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/ff36816d-ee76-4c55-a41f-8618ccd3860a>`. `<https://linked.data.gov.au/def/nrm/ff36816d-ee76-4c55-a41f-8618ccd3860a>` is the IRI for "Soil segregation strength types".
The value of `tern:vocabulary` _MUST_ match the pattern `ff36816d-ee76-4c55-a41f-8618ccd3860a$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/040526b4-50a2-4bcf-a16a-ed5d1b5f7c4c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil field slaking scores controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil field slaking scores controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/040526b4-50a2-4bcf-a16a-ed5d1b5f7c4c> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'c2408628-477b-4867-bc12-532126801973'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/040526b4-50a2-4bcf-a16a-ed5d1b5f7c4c> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/040526b4-50a2-4bcf-a16a-ed5d1b5f7c4c>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/040526b4-50a2-4bcf-a16a-ed5d1b5f7c4c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/c2408628-477b-4867-bc12-532126801973>`. `<https://linked.data.gov.au/def/nrm/c2408628-477b-4867-bc12-532126801973>` is the IRI for "Soil field slaking scores".
The value of `tern:vocabulary` _MUST_ match the pattern `c2408628-477b-4867-bc12-532126801973$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8e87bc47-7bc6-4ad7-81ac-17d4968004e8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil structure grades controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil structure grades controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/8e87bc47-7bc6-4ad7-81ac-17d4968004e8> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'0cfcb0fc-75e3-4de1-a2d3-78c357a3ce06'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/8e87bc47-7bc6-4ad7-81ac-17d4968004e8> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8e87bc47-7bc6-4ad7-81ac-17d4968004e8>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/8e87bc47-7bc6-4ad7-81ac-17d4968004e8>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/0cfcb0fc-75e3-4de1-a2d3-78c357a3ce06>`. `<https://linked.data.gov.au/def/nrm/0cfcb0fc-75e3-4de1-a2d3-78c357a3ce06>` is the IRI for "Soil structure grades".
The value of `tern:vocabulary` _MUST_ match the pattern `0cfcb0fc-75e3-4de1-a2d3-78c357a3ce06$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dd8dcc19-8a0c-4d9f-995f-a449408b5aa5>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil structure sizes controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil structure sizes controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/dd8dcc19-8a0c-4d9f-995f-a449408b5aa5> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'f5226b34-eac7-42c3-9730-b7fdb2479697'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/dd8dcc19-8a0c-4d9f-995f-a449408b5aa5> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dd8dcc19-8a0c-4d9f-995f-a449408b5aa5>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/dd8dcc19-8a0c-4d9f-995f-a449408b5aa5>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/f5226b34-eac7-42c3-9730-b7fdb2479697>`. `<https://linked.data.gov.au/def/nrm/f5226b34-eac7-42c3-9730-b7fdb2479697>` is the IRI for "Soil structure sizes".
The value of `tern:vocabulary` _MUST_ match the pattern `f5226b34-eac7-42c3-9730-b7fdb2479697$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5b4dc0ad-3b4d-47d2-a775-7b405b4ff570>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil structure types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil structure types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/5b4dc0ad-3b4d-47d2-a775-7b405b4ff570> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'ba792941-7941-43c8-b992-b7f54dddf14c'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/5b4dc0ad-3b4d-47d2-a775-7b405b4ff570> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5b4dc0ad-3b4d-47d2-a775-7b405b4ff570>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/5b4dc0ad-3b4d-47d2-a775-7b405b4ff570>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/ba792941-7941-43c8-b992-b7f54dddf14c>`. `<https://linked.data.gov.au/def/nrm/ba792941-7941-43c8-b992-b7f54dddf14c>` is the IRI for "Soil structure types".
The value of `tern:vocabulary` _MUST_ match the pattern `ba792941-7941-43c8-b992-b7f54dddf14c$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/90edb127-cd04-42d6-9f0d-3f6b159f5e8c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/90edb127-cd04-42d6-9f0d-3f6b159f5e8c> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/90edb127-cd04-42d6-9f0d-3f6b159f5e8c> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/90edb127-cd04-42d6-9f0d-3f6b159f5e8c>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/90edb127-cd04-42d6-9f0d-3f6b159f5e8c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3a1ccb70-41dc-4f57-a74c-62e05aa02c61>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil surface soil conditions controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil surface soil conditions controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3a1ccb70-41dc-4f57-a74c-62e05aa02c61> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'253cc4d0-b1f2-4a55-bdaf-e3c054703451'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3a1ccb70-41dc-4f57-a74c-62e05aa02c61> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3a1ccb70-41dc-4f57-a74c-62e05aa02c61>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3a1ccb70-41dc-4f57-a74c-62e05aa02c61>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/253cc4d0-b1f2-4a55-bdaf-e3c054703451>`. `<https://linked.data.gov.au/def/nrm/253cc4d0-b1f2-4a55-bdaf-e3c054703451>` is the IRI for "Soil surface soil conditions".
The value of `tern:vocabulary` _MUST_ match the pattern `253cc4d0-b1f2-4a55-bdaf-e3c054703451$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/062078e4-716e-4f27-a0f2-5e9715ddb6dc>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil texture grades controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil texture grades controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/062078e4-716e-4f27-a0f2-5e9715ddb6dc> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'ecdcb81a-cbe9-4113-b9e9-422a0e6c751f'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/062078e4-716e-4f27-a0f2-5e9715ddb6dc> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/062078e4-716e-4f27-a0f2-5e9715ddb6dc>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/062078e4-716e-4f27-a0f2-5e9715ddb6dc>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/ecdcb81a-cbe9-4113-b9e9-422a0e6c751f>`. `<https://linked.data.gov.au/def/nrm/ecdcb81a-cbe9-4113-b9e9-422a0e6c751f>` is the IRI for "Soil texture grades".
The value of `tern:vocabulary` _MUST_ match the pattern `ecdcb81a-cbe9-4113-b9e9-422a0e6c751f$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/51101df7-f8ac-4b5f-8890-482cc7a083ed>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil texture modifiers controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil texture modifiers controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/51101df7-f8ac-4b5f-8890-482cc7a083ed> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'65d26894-1b2e-4c80-92ee-fa420142ed67'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/51101df7-f8ac-4b5f-8890-482cc7a083ed> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/51101df7-f8ac-4b5f-8890-482cc7a083ed>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/51101df7-f8ac-4b5f-8890-482cc7a083ed>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/65d26894-1b2e-4c80-92ee-fa420142ed67>`. `<https://linked.data.gov.au/def/nrm/65d26894-1b2e-4c80-92ee-fa420142ed67>` is the IRI for "Soil texture modifiers".
The value of `tern:vocabulary` _MUST_ match the pattern `65d26894-1b2e-4c80-92ee-fa420142ed67$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c0e91cf7-b099-498a-8450-a37783404b3c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil texture qualifications controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil texture qualifications controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/c0e91cf7-b099-498a-8450-a37783404b3c> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'367b9d17-0e08-4ad4-9c44-20e8c3f515fb'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/c0e91cf7-b099-498a-8450-a37783404b3c> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c0e91cf7-b099-498a-8450-a37783404b3c>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/c0e91cf7-b099-498a-8450-a37783404b3c>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/367b9d17-0e08-4ad4-9c44-20e8c3f515fb>`. `<https://linked.data.gov.au/def/nrm/367b9d17-0e08-4ad4-9c44-20e8c3f515fb>` is the IRI for "Soil texture qualifications".
The value of `tern:vocabulary` _MUST_ match the pattern `367b9d17-0e08-4ad4-9c44-20e8c3f515fb$`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/f6504250-db2c-47ae-98f5-17f9534aff84>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the Soil void crack types controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the Soil void crack types controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/f6504250-db2c-47ae-98f5-17f9534aff84> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'1acac98b-808d-4efa-aa27-a0cb7782e63f'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/f6504250-db2c-47ae-98f5-17f9534aff84> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/f6504250-db2c-47ae-98f5-17f9534aff84>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/f6504250-db2c-47ae-98f5-17f9534aff84>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/1acac98b-808d-4efa-aa27-a0cb7782e63f>`. `<https://linked.data.gov.au/def/nrm/1acac98b-808d-4efa-aa27-a0cb7782e63f>` is the IRI for "Soil void crack types".
The value of `tern:vocabulary` _MUST_ match the pattern `1acac98b-808d-4efa-aa27-a0cb7782e63f$`.
Observations following the Standard Soil Sub-Pit and Soil Metagenomics protocol are made in the context of a site visit.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/5d12a157-61a0-42e6-b23d-895018974c67>`. `<https://linked.data.gov.au/def/nrm/5d12a157-61a0-42e6-b23d-895018974c67>` is the IRI for "Standard Soil Sub-Pit and Soil Metagenomics protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/5d12a157-61a0-42e6-b23d-895018974c67`.
This model validator was made for the Australian Capital Territory government.
This validator is a Shapes Constraint Language (SHACL) resource that can be used to check the conformance of RDF data to the ANZ ICSM Address Model with extensions for the ACT
Each ACT Address must indicate a Road part with additionalType indicating road from the Address Part Types vocabulary
Each ACT Address must indicate an Address Part with the ASGS IRI for the ACT
5.5 2026-02: Aligns with use of VocPub 5.5. eCatID requirement for Concept Scheme only
Previous to v5.5, this validator contained all of VocPub. Since 5.5 it contains only the GA-specific Shapes so must be used with VocPub (5.5+) to validate a vocabulary completely
Geoscience Australia's additional vocabulary validation rules, to be added to VocPub
VocPub Validator - GA
Requirement GA ECAT-ID: Each vocabulary MUST have exactly one identifier predicate indicating an eCatID, which means a schema:identifier predicate indicating a URL starting https://pid.geoscience.gov.au/dataset/ga/ and ending with a multi-digit number
The Bibliographic Ontology describes bibliographic things on the semantic Web in RDF. This ontology can be used as a citation ontology, as a document classification ontology, or simply as a way to describe any kind of document in RDF. It has been inspired by many existing document description metadata formats, and can be used as a common ground for converting other bibliographic data sources.
Electronic International Standard Serial Number
The name defining a special edition of a document. Normally its a literal value composed of a version number and words.
Ending page number within a continuous page range.
An International Standard Serial Number is an 8-digit code used to identify newspapers, journals, magazines and periodicals of all kinds and on all media–print and electronic.
A description (often numeric) that locates an item within a containing document or collection.
Starting page number within a continuous page range.
Used to link an agent (a person) to an event (a conference, an hearing, etc.)
Used to relate an event such as a conference to the geographical place where it happens, for example Paris.
Used to link big events with smaller events such as workshops that happen in the context of a conference.
events smaller than a bigger event that contain them
Used to describe the timing of an event. For example, when a conference starts and stops.
A scholarly academic article, typically published in a journal.
A written composition in prose, usually nonfiction, on a specific topic, forming an independent part of a book or other publication, as a newspaper or magazine.
A document (noun) is a bounded physical representation of body of information designed with the capacity (and usually intent) to communicate. A document may manifest symbolic, diagrammatic or sensory-representational information.
Draft legislation presented for discussion to a legal body.
A legal document proposing or enacting a law or a group of laws.
A written argument submitted to a court.
A group of related documents issued at regular intervals.
A meeting for consultation or discussion.
Used to describe bibliographic related events such as conferences, hearing, etc.
A legal document; for example, a court decision, a brief, and so forth.
A document that simultaneously contains other documents.
A written communication addressed to a person or organization and transmitted electronically.
A personal communication manifested in some document.
An audio-visual document; film, video, and so forth.
An instance or a session in which testimony and arguments are presented, esp. before an official, as a judge in a lawsuit.
A formalized discussion between two or more people.
A periodical of scholarly journal Articles.
something that is printed or published and distributed, esp. a given number of a periodical
A written or printed communication addressed to a person or organization and usually transmitted by mail.
A periodical of magazine Articles. A magazine is a publication that is issued periodically, usually bound in a paper cover, and typically contains essays, stories, poems, etc., by many writers, and often photographs and drawings, frequently specializing in a particular subject or area, as hobbies, news, or sports.
A small reference book, especially one giving instructions.
An unpublished Document, which may also be submitted to a publisher for publication.
A graphical depiction of geographic features.
A document that presents visual or diagrammatic information.
A loose, thematic, collection of Documents, often Books.
A written or printed work of fiction or nonfiction, usually on sheets of paper fastened or bound together within covers.
A collection of Documents or Collections
A periodical of documents, usually issued daily or weekly, containing current news, editorials, feature articles, and usually advertising.
A document describing the exclusive right granted by a government to an inventor to manufacture, use, or sell an invention for a certain number of years.
A communication between an agent and one or more specific recipients.
A compilation of documents published from an event, such as a conference.
A document that presents authoritative reference information, such as a dictionary or encylopedia .
A document describing an account or statement describing in detail an event, situation, or the like, usually as the result of observation, inquiry, etc..
A presentation of a series of slides, usually presented in front of an audience with written text and images.
A document describing a standard: a specification organized through a standards body.
A group of Webpages accessible on the Web.
A web page is an online document available (at least initially) on the world wide web. A web page is written first and foremost to appear on the web, as distinct from other online resources such as books, manuscripts or audio documents which use the web primarily as a distribution mechanism alongside other more traditional methods such as print.
A seminar, discussion group, or the like, that emphasizes zxchange of ideas and the demonstration and application of techniques, skills, etc.
A document containing an authoritative determination (as a decree or judgment) made after consideration of facts or law.
A legal decision on appeal that takes action on a case (affirming it, reversing it, etc.).
Critical or explanatory note for a Document.
The date on which a legal case is argued before a court. Date is of format xsd:date
An Amazon Standard Identification Number (ASIN) is a 10-character alphanumeric unique identifier assigned by Amazon.com and its partners
A code that uniquely identifies something within a context
An ordered list of authors. Normally, this list is seen as a priority list that order authors by importance.
An ordered list of contributors. Normally, this list is seen as a priority list that order contributors by importance.
Relates a document to another document that cites the first document.
Relates a document to another document that is cited by the first document as reference, comment, review, quotation or for another purpose.
CODEN – according to ASTM standard E250 – is a six-character, alphanumeric bibliographic code that provides concise, unique and unambiguous identification of the titles of periodicals and non-serial publications from all subject areas.
bibo:content has been deprecated; we recommend to use "rdf:value" for this purpose. Here is the rational behind this choice: http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#rdfvalue
This property is for a plain-text rendering of the content of a Document. While the plain-text content of an entire document could be described by this property.
A court associated with a legal document; for example, that which issues a decision.
We are not defining, using an enumeration, the range of the bibo:degree to the defined list of bibo:ThesisDegree. We won't do it because we want people to be able to define new degress if needed by some special usecases. Creating such an enumeration would restrict this to happen.
A document created to summarize research findings associated with the completion of an academic degree.
Distributor of a document or a collection of documents.
An EAN-13 barcode is a 13-digit international retail product identifier, comprising 12 data digits and a check digit to ensure scanning accuracy.
A person having managerial and sometimes policy-making responsibility for the editorial part of a publishing firm or of a newspaper, magazine, or other publication.
An ordered list of editors. Normally, this list is seen as a priority list that order editors by importance.
A GTIN-14 (Global Trade Item Number 14, also called ITF-14 or TUN) is a 14-digit number used for logistics and shipping cartons, identifying a group of retail products (like a case of soda) rather than individual items, and is encoded in ITF-14 barcodes, not for point-of-sale scanning but for tracking in warehouses and supply chains.
The Handle System is a proprietary registry assigning persistent identifiers, or handles, to information resources
An agent that is interviewed by another agent.
The 10-digit International Standard Book Number format was developed by the International Organization for Standardization (ISO) and was published in 1970
An ISBN-13 (International Standard Book Number) is a unique 13-digit identifier for a specific book edition, replacing the older 10-digit system in 2007
An entity responsible for issuing often informally published documents such as press releases, reports, etc.
The Library of Congress Control Number (LCCN) is a serially based system of numbering cataloged records in the Library of Congress, in the United States.
The number of pages contained in a document
The number of volumes contained in a collection of documents (usually a series, periodical, etc.).
A generic item or document number. Not to be confused with issue number.
The OCLC Number is a unique number associated with a record in WorldCat. WorldCat is the world's largest network of library holdings.
The organizer of an event; includes conference organizers, but also government agencies or other bodies that are responsible for conducting hearings.
Owner of a document or a collection of documents.
A string of non-contiguous page spans that locate a Document within a Collection. Example: 23-25, 34, 54-56. For continuous page ranges, use the pageStart and pageEnd properties.
A PMID (PubMed Identifier) is a unique number assigned to each article in the PubMed database, serving as a simple, direct way to find, cite, and link to specific biomedical literature, including research papers, letters, and opinions, regardless of the article's type or funding status.
Relates an event to associated documents; for example, conference to a paper.
Relates a document to an event; for example, a paper to a conference.
Producer of a document or a collection of documents.
An agent that receives a communication document.
The resource in which another resource is reproduced.
A legal decision that reverses a ruling.
Relates a review document to a reviewed thing (resource, item, etc.).
Di Rado, Alicia. 1995. Trekking through college: Classes explore modern society using the world of Star trek. Los Angeles Times, March 15, sec. A, p. 3.
The Serial Item and Contribution Identifier (SICI) was a code (ANSI/NISO standard Z39. 56-1996 [R2002]) used to uniquely identify specific volumes, articles or other identifiable parts of a serial.
We are not defining, using an enumeration, the range of the bibo:status to the defined list of bibo:DocumentStatus. We won't do it because we want people to be able to define new status if needed by some special usecases. Creating such an enumeration would restrict this to happen.
The publication status of (typically academic) content.
The status of the publication of a document.
Accepted for publication after peer reviewing.
The process by which articles are chosen to be included in a refereed journal. An editorial board consisting of experts in the same field as the author review the article and decide if it is authoritative enough for publication.
Rejected for publication after peer reviewing.
Relates a document to some transcribed original.
Relates a translated document to the original document.
A person who translates written document from one language to another.
Universal Resource Identifier of a document
a distinct part of a larger document or collected document.
1297.0 ANZSRC - Australian and New Zealand Standard Research Classification, 2020 Fields of Research (FoR)
Released at 11.30am (Canberra time) 30 June 2020 Explanatory Notes More information on the ABS website ANZSRC - Australian and New Zealand Standard Research Classification, 2020 Summary (https://www.abs.gov.au/AUSSTATS/abs@.nsf/mf/1297.0) Abbreviations ABS -- Australian Bureau of Statistics ANZSRC -- Australian and New Zealand Standard Research Classification Aus -- Australia FoR -- Fields of Research nec -- not elsewhere classified NZ -- New Zealand R&D -- research and development SEO -- Socio-Economic Objectives StatsNZ -- Stats NZ Tatauranga Aotearoa is New Zealand's official data agency Introduction 1. These tables detail the structure and explanatory notes of the FoR component of ANZSRC 2020. Nature and purpose of the FoR classification 2. The FoR classification enables R&D to be categorised according to common knowledge domains and/or methodologies used in the R&D. It describes the nature of the research being performed and reflects the area of knowledge discovery. 3. The categories in the classification include fields of research and emerging areas of study investigated by businesses, universities, tertiary institutions, national research institutions and other organisations. Structure of the FoR classification 4. The FoR classification is a hierarchical classification with three levels: Division (2-digit), Group (4-digit) and Field (6-digit). Each level is identified by a unique number. 5. Each Division is based on a broad discipline. Groups within each Division are those which share the same broad methodology, knowledge domain and/or perspective as others in the Division. Each Group is a collection of related Fields of Research. Groups and Fields of Research are categorised to the Divisions sharing the same methodology rather than the Division they support. Guidelines for classifying by FoR 6. The research should first be considered in its broadest sense and in terms of the discipline that the research relates. The research is to be allocated to a FoR in a hierarchical manner. This is achieved by: ▪ first determining the most relevant division in which the largest component of the R&D is being performed; then ▪ determining the most relevant group within that division; and then ▪ determining the most relevant field within that group. 7. Many R&D projects will be a homogenous body of work in a specific field. These are more straightforward to categorise. However, the emergence of new interdisciplinary and multidisciplinary fields of research is a feature of the modern R&D environment. The categorisation of such fields within a hierarchical and exclusive classification system can pose difficulties for users of the FoR. The use of multiple fields to classify a research project ensures that this research is accommodated within the classification structure. 8. If the research is sufficiently large or complex then multiple fields should be selected and attributed with a proportion of resources relative to the total expenditure of the R&D. If the disaggregation is difficult, consideration of relative importance may indicate a primary objective only. 9. Where a defined field cannot be identified within a group, the 'not elsewhere classified' category at the field level is to be used. © Commonwealth of Australia 2020 (http://www.abs.gov.au/websitedbs/d3310114.nsf/Home/%C2%A9+Copyright?OpenDocument) © Crown Copyright New Zealand 2020 (http://www.stats.govt.nz/about_us/about-this-site/copyright-terms-of-use.aspx)
1297.0 ANZSRC - Australian and New Zealand Standard Research Classification, 2020: Fields of Research (FoR)
Agricultural biotechnology diagnostics (incl. biosensors)
This group covers agricultural biotechnology.
Agricultural biotechnology
a) Improvement of plants through selective breeding is included in Group 3004 Crop and pasture production and Group 3007 Forestry sciences and Group 3008 Horticultural production. b) Improvement of animals through selective breeding is included in Group 3003 Animal production. b) Genetic modification of plants, microbes or animals for environmental purposes and biological control of pests, diseases and exotic species is included in Group 4103 Environmental biotechnology. c) Genetic modification of plants, microbes or animals for industrial purposes (other than agriculture) is included in Group 3106 Industrial biotechnology. d) Genetic modification of plants, microbes or animals for medical purposes is included in Group 3206 Medical biotechnology. e) Nanobiotechnology is included in Group 3106 Industrial biotechnology and medical biotechnology is included in Group 1119 Nanotechnology health. f) Ethical use of biotechnology is included in Group 5001 Applied ethics.
This division covers the sciences and technologies supporting agriculture. It includes: • crop and pasture production; • agronomy; • horticultural production; • animal production; • forestry sciences; • fisheries sciences; • food sciences; and, • veterinary sciences.
AGRICULTURAL, VETERINARY AND FOOD SCIENCES
a) Indigenous agricultural, veterinary and food sciences is included in Division 45 Indigenous studies.
Agricultural marine biotechnology
Agricultural molecular engineering of nucleic acids and proteins
Genetically modified animals
Genetically modified field crops and pasture
Genetically modified horticulture plants
Genetically modified trees
Livestock cloning
Non-genetically modified uses of biotechnology
Transgenesis
Agricultural biotechnology not elsewhere classified
Agricultural hydrology
This group covers the management of agriculture, land, farms and rural businesses.
Agriculture, land and farm management
a) Management of parks in natural environments is included in Group 4104 Environmental management. b) Soil sciences are included in Group 4106 Soil sciences. c) Management of forests for agricultural production is included in Group 3007 Forestry sciences. d) Agricultural water management is included in Group 3099 Other agricultural, veterinary and food sciences. e) Management and planning of land and parks in built environments is included in Group 3304 Urban and regional planning. f) Management of non-rural businesses is included in Group 3507 Strategy, management and organisational behaviour. g) Fisheries management is included in Group 3005 Fisheries sciences.
Agricultural land management
Agricultural land planning
Agricultural management of nutrients
Agricultural production systems simulation
Agricultural spatial analysis and modelling
Agricultural systems analysis and modelling
Farm management, rural management and agribusiness
Germplasm management
Sustainable agricultural development
Agriculture, land and farm management not elsewhere classified
Animal growth and development
This group covers the sciences and technologies supporting the primary production of livestock, including birds and poultry. It includes: • bees and apiary culture; • egg production; and • animal production for domestic or sporting uses.
Animal production
a) The culture and production of marine and freshwater animals, including fish, crustaceans and shellfish, is included in Group 3005 Fisheries sciences. b) Veterinary sciences is included in Group 3009 Veterinary sciences. c) Food sciences, including food processing and packaging, is included in Group 3006 Food sciences. d) Genetic engineering and cloning of livestock is included in Group 3001 Agricultural biotechnology.
Animal management
Animal nutrition
Animal protection (incl. pests and pathogens)
Animal reproduction and breeding
Animal welfare
Environmental studies in animal production
Animal production not elsewhere classified
Agrochemicals and biocides (incl. application)
This group covers the sciences and technologies supporting the production of crops, pastures and grains. It includes: • agronomy; • genetics and field protection procedures for crop and pasture production; • post harvest treatment transportation of crops and grains; and • weed science
Crop and pasture production
a) Genetic engineering of crops and pasture is included in Group 3001 Agricultural biotechnology.
Agro-ecosystem function and prediction
Agronomy
Crop and pasture biochemistry and physiology
Crop and pasture biomass and bioproducts
Crop and pasture improvement (incl. selection and breeding)
Crop and pasture nutrition
Crop and pasture post harvest technologies (incl. transportation and storage)
Crop and pasture protection (incl. pests, diseases and weeds)
Crop and pasture waste water use
Fertilisers (incl. application)
Organic and low chemical input crop production
Pollination biology and systems
Crop and pasture production not elsewhere classified
Aquaculture
This group covers the sciences and technologies supporting fishing and production of freshwater and marine fisheries (including shellfish and crustaceans).
Fisheries sciences
a) Food science, including food processing and packaging, is included in Group 3006 Food sciences. b) Genetic engineering and cloning of livestock is included in Group 3001 Agricultural biotechnology.
Aquaculture and fisheries stock assessment
Fish pests and diseases
Fish physiology and genetics
Fisheries management
Post-harvest fisheries technologies (incl. transportation)
Fisheries sciences not elsewhere classified
Beverage chemistry and beverage sensory science
This group covers the food sciences.
Food sciences
a) Fermentation for non-food products is included in Group 3106 Industrial biotechnology. b) Human nutrition is included in Group 3210 Nutrition and dietetics.
Food chemistry and food sensory science
Food nutritional balance
Food packaging, preservation and processing
Food safety, traceability, certification and authenticity
Food sustainability
Food technology
Food sciences not elsewhere classified
Agroforestry
This group covers forestry sciences and silviculture.
Forestry sciences
a) Management of forests in natural environments other than for forestry production is included in Group 4104 Environmental management.
Forest biodiversity
Forest ecosystems
Forest health and pathology
Forestry biomass and bioproducts
Forestry fire management
Forestry management and environment
Forestry product quality assessment
Tree improvement (incl. selection and breeding)
Tree nutrition and physiology
Wood fibre processing
Wood processing
Forestry sciences not elsewhere classified
Field organic and low chemical input horticulture
This group covers horticultural production and horticultural science.
Horticultural production
Horticultural crop growth and development
Horticultural crop improvement (incl. selection and breeding)
Horticultural crop protection (incl. pests, diseases and weeds)
Oenology and viticulture
Post harvest horticultural technologies (incl. transportation and storage)
Horticultural production not elsewhere classified
Veterinary anaesthesiology and intensive care
This group covers veterinary sciences practised on livestock for primary production, domestic, sporting and other uses.
Veterinary sciences
a) Field procedures to protect animals against pests and pathogens are included in Group 3003 Animal production. b) Biological or life sciences associated with human health and medicine are included in Division 31 Biological sciences.
Veterinary anatomy and physiology
Veterinary bacteriology
Veterinary diagnosis and diagnostics
Veterinary epidemiology
Veterinary immunology
Veterinary medicine (excl. urology)
Veterinary mycology
Veterinary parasitology
Veterinary pathology
Veterinary pharmacology
Veterinary surgery
Veterinary urology
Veterinary virology
Veterinary sciences not elsewhere classified
Other agricultural, veterinary and food sciences not elsewhere classified
This group covers agricultural and veterinary and food sciences not elsewhere classified.
Other agricultural, veterinary and food sciences
Analytical biochemistry
This group covers biochemistry or the chemistry of living organisms. It includes bioinformatics, cell biology and membrane biology.
Biochemistry and cell biology
a) Chemistry, including organic and biomolecular chemistry, is included in Division 34 Chemical sciences. b) Cell and molecular biology specific to plants is included in Group 3108 Plant biology. c) Cell and molecular biology specific to animals is included in Group 3109 Zoology. d) Biochemistry of agricultural plants is included in Group 3004 Crop and pasture production. e) Bioinformatics software is included in Group 3102 Bioinformatics and computational biology. f) Biochemistry and proteomics associated with medical sciences is included in Group 3205 Medical biochemistry and metabolomics.
This division covers biological sciences.
BIOLOGICAL SCIENCES
a) Indigenous biological sciences are included in Division 45 Indigenous studies.
Cell development, proliferation and death
Cell metabolism
Cell neurochemistry
Cellular interactions (incl. adhesion, matrix, cell wall)
Enzymes
Glycobiology
Protein trafficking
Proteomics and intermolecular interactions (excl. medical proteomics)
Receptors and membrane biology
Signal transduction
Structural biology (incl. macromolecular modelling)
Synthetic biology
Systems biology
Biochemistry and cell biology not elsewhere classified
Bioinformatic methods development
This group covers bioinformatics and computational biology.
Bioinformatics and computational biology
a) Metabolomic chemistry is included in Group 3401 Analytical chemistry. b) Gene mapping is included in Group 3105 Genetics.
Biological network analysis
Computational ecology and phylogenetics
Genomics and transcriptomics
Proteomics and metabolomics
Sequence analysis
Statistical and quantitative genetics
Translational and applied bioinformatics
Bioinformatics and computational biology not elsewhere classified
Behavioural ecology
This group covers ecology other than its environmental applications.
Ecology
a) Palaeontology other than that associated with palaeoecological studies is included in Group 3705 Geology. b) Applications of ecology, including the ecology of invasive species, are included in Group 4102 Ecological applications. c) Population and ecological genetics is included in Group 3105 Genetics. d) Microbial ecology is included in Group 3107 Microbiology. e) Freshwater ichthyology and animal physiological ecology are included in Group 3109 Zoology.
Community ecology (excl. invasive species ecology)
Ecological physiology
Freshwater ecology
Marine and estuarine ecology (incl. marine ichthyology)
Palaeoecology
Population ecology
Terrestrial ecology
Ecology not elsewhere classified
Animal systematics and taxonomy
This group covers evolutionary biology, including biogeography and adaptation.
Evolutionary biology
a) Evolutionary genetics and molecular evolution is included in Group 3105 Genetics. b) Evolutionary impacts of climate change are included in Group 4101 Climate change impacts and adaptation. c) Climate change processes are included in Group 3702 Climate change science. d) Ethology and sociobiology are included in Group 3103 Ecology.
Biogeography and phylogeography
Biological adaptation
Evolution of developmental systems
Evolutionary ecology
Evolutionary impacts of climate change
Host-parasite interactions
Life histories
Microbial taxonomy
Phylogeny and comparative analysis
Plant and fungus systematics and taxonomy
Speciation and extinction
Evolutionary biology not elsewhere classified
Anthropological genetics
This group covers genetics and heredity.
Genetics
a) Microbial genetics is included in Group 3107 Microbiology. b) Animal genetics associated with animal reproduction is included in Group 3003 Animal production. c) Genetics of agricultural crops (excl. genetic engineering) is included in Groups 3004 Crop and pasture production and 3008 Horticultural production. d) Genetic engineering of agricultural crops is included in Group 3001 Agricultural biotechnology. e) Genetics associated with human health and medicine is included in Groups 3202 Clinical sciences and 3211 Oncology and carcinogenesis. f) Phylogenetic networks, ontologies and statistical and quantitative genetics are included in Group 3102 Bioinformatics and computational biology. g) Phylogeny is included in Group 3104 Evolutionary biology.
Cell and nuclear division
Developmental genetics (incl. sex determination)
Epigenetics (incl. genome methylation and epigenomics)
Gene expression (incl. microarray and other genome-wide approaches)
Gene mapping
Genetic immunology
Genome structure and regulation
Genomics
Molecular evolution
Neurogenetics
Genetics not elsewhere classified
Biocatalysis and enzyme technology
This group covers industrial biotechnology .
Industrial biotechnology
a) Environmental biotechnology, nanotechnology and nanometrology is included in Group 4103 Environmental biotechnology. b) Genetic modification of plants, microbes or animals for agricultural purposes is included in Group 3001 Agricultural biotechnology. c) Genetic modification of plants, microbes or animals for industrial purposes (other than agriculture) is included in Group 3106 Industrial biotechnology. d) Genetic modification of plants, microbes or animals for medical purposes is included in Group 3206 Medical biotechnology.
Bioprocessing, bioproduction and bioproducts
Fermentation
Industrial biotechnology diagnostics (incl. biosensors)
Industrial microbiology (incl. biofeedstocks)
Industrial molecular engineering of nucleic acids and proteins
Nanobiotechnology
Industrial biotechnology not elsewhere classified
Bacteriology
This group covers microbiology, including bacteriology, parasitology and virology.
Microbiology
a) Microbial systematics, taxonomy and phylogeny are included in Group 3104 Evolutionary biology. b) Veterinary microbiology is included in Group 3009 Veterinary sciences. c) Medical and clinical microbiology are included in Division 32 Biomedical and Clinical Sciences.
Infectious agents
Microbial ecology
Microbial genetics
Mycology
Virology
Microbiology not elsewhere classified
Phycology (incl. marine grasses)
This group covers plant biology. It includes: • plant pathology other than that associated with plant protection procedures used in agriculture and horticulture; and • phycology (including algae and marine grasses).
Plant biology
a) Palaeobotany and palynology (other than palynology associated with ecological studies) are included in Group 3705 Geology. b) Cell and molecular biology not specific to plants or animals is included in Group 3101 Biochemistry and cell biology. c) Plant ecology and palynology associated with ecological studies is included in Group 3103 Ecology. d) Plant and fungus systematics and taxonomy are included in Group 3104 Evolutionary biology. e) Plant sciences or plant pathology associated with agriculture, forestry or primary production is included in Division 30 Agricultural, veterinary and food sciences. f) Mycology, which for the purpose of this classification includes the study of lichen, is included in Group 3107 Microbiology.
Plant biochemistry
Plant cell and molecular biology
Plant developmental and reproductive biology
Plant pathology
Plant physiology
Plant biology not elsewhere classified
Animal behaviour
This group covers zoology.
Zoology
a) Palaeontology other than that associated with palaeoecological studies is included in Group 3705 Geology. b) Cell and molecular biology not specific to plants or animals is included in Group 3101 Biochemistry and cell biology. c) Animal ecology and marine ichthyology are included in Group 3103 Ecology. d) Animal systematics, taxonomy and phylogeny are included in Group 3104 Evolutionary biology. e) The use of live animals for purposes of primary production is included in Group 3003 Animal production. f) Fisheries and aquaculture for primary production is included in Group 3005 Fisheries sciences. g) The human immune system is included in Group 3204 Immunology. h) The human nervous system is included in Group 3209 Neurosciences. i) The use of live animals or material from live animals for medical research is included in Group 3299 Other biomedical and clinical sciences. j) Animal bioethics is included in Group 5001 Applied ethics.
Animal cell and molecular biology
Animal developmental and reproductive biology
Animal diet and nutrition
Animal immunology
Animal neurobiology
Animal physiological ecology
Animal physiology - biophysics
Animal physiology - cell
Animal physiology - systems
Animal structure and function
Comparative physiology
Invertebrate biology
Vertebrate biology
Zoology not elsewhere classified
Forensic biology
This group covers biological sciences not elsewhere classified. It includes forensic biology and global change biology.
Other biological sciences
Global change biology
Other biological sciences not elsewhere classified
Cardiology (incl. cardiovascular diseases)
This group covers cardiovascular medicine and haematology.
Cardiovascular medicine and haematology
a) Pathology is included in Group 3202 Clinical sciences.
This division covers biomedical and clinical science.
BIOMEDICAL AND CLINICAL SCIENCES
a) Indigenous biomedical and clinical sciences are included in Division 45 Indigenous studies.
Haematology
Respiratory diseases
Cardiovascular medicine and haematology not elsewhere classified
Anaesthesiology
This group covers specific clinical aspects of medicine, including causes, diagnosis, treatment and management of specific diseases and conditions.
Clinical sciences
a) Accelerators and other equipment for the production of radioisotopes for nuclear medicine are included in Group 5110 Synchrotrons and accelerators. b) Anthropological genetics is included in Group 3105 Genetics. c) Medical biochemistry, cardiovascular medicine, dentistry, immunology, medical microbiology, neurosciences, oncology, ophthalmology, paediatrics, pharmacology and medical physiology are included in other groups in Division 32 Biomedical and clinical sciences. d) Oral pathology is included in Group 3203 Dentistry. e) Radiotherapy and cancer genetics is included in Group 3211 Oncology and carcinogenesis. f) Psychology is included in Division 52 Psychology. g) Physiotherapy, podiatry and rehabilitation and therapy are included in Group 4201 Allied health and rehabilitation science. h) Human movement is included in 4207 Sports science and exercise.
Clinical chemistry (incl. diagnostics)
Clinical microbiology
Clinimetrics
Dermatology
Diagnostic radiography
Emergency medicine
Endocrinology
Gastroenterology and hepatology
Geriatrics and gerontology
Infectious diseases
Intensive care
Medical genetics (excl. cancer genetics)
Nephrology and urology
Nuclear medicine
Orthopaedics
Otorhinolaryngology
Pain
Paramedicine
Pathology (excl. oral pathology)
Psychiatry (incl. psychotherapy)
Radiology and organ imaging
Rheumatology and arthritis
Rural clinical health
Sports medicine
Surgery
Venereology
Clinical sciences not elsewhere classified
Craniofacial biology
This group covers dentistry.
Dentistry
a) Biomaterials not solely restricted to dental use are included in Group 4003 Biomedical engineering.
Dental materials and equipment
Dental therapeutics, pharmacology and toxicology
Endodontics
Oral and maxillofacial surgery
Oral implantology
Oral medicine and pathology
Orthodontics and dentofacial orthopaedics
Paedodontics
Periodontics
Prosthodontics
Special needs dentistry
Dentistry not elsewhere classified
Allergy
This group covers the processes and reactions of the human immune system.
Immunology
a) Specific human disorders or diseases are included in Group 3202 Clinical sciences.
Applied immunology (incl. antibody engineering, xenotransplantation and t-cell therapies)
Autoimmunity
Cellular immunology
Humoural immunology and immunochemistry
Immunogenetics (incl. genetic immunology)
Innate immunity
Transplantation immunology
Tumour immunology
Immunology not elsewhere classified
Medical biochemistry - amino acids and metabolites
This group covers human biochemistry or the chemistry of human living organisms and the human life process. It includes proteomics, metabolomics and metabolic medicine.
Medical biochemistry and metabolomics
a) Medicinal and biomolecular chemistry is included in Group 3404 Medicinal and biomolecular chemistry. b) Biochemistry of species other than human or non-agricultural plant and biochemistry not related to medicine or health are included in Group 3101 Biochemistry and cell biology. c) Biochemistry of agricultural plants is included in Groups 3004 Crop and pasture production and 3008 Horticultural production. d) Clinical chemistry and hormonal control of metabolism is included in Group 3202 Clinical sciences. e) Nutrition and dietetics is included in Group 3210 Nutrition and dietetics.
Medical biochemistry - carbohydrates
Medical biochemistry - inorganic elements and compounds
Medical biochemistry - lipids
Medical biochemistry - nucleic acids
Medical biochemistry - proteins and peptides (incl. medical proteomics)
Metabolic medicine
Medical biochemistry and metabolomics not elsewhere classified
Gene and molecular therapy
This group covers medical biotechnology.
Medical biotechnology
a) Biomedical imaging, medical devices, neural engineering and tissue engineering are included in Group 4003 Biomedical engineering.
Medical biotechnology diagnostics (incl. biosensors)
Medical molecular engineering of nucleic acids and proteins
Nanomedicine
Nanotoxicology, health and safety
Regenerative medicine (incl. stem cells)
Medical biotechnology not elsewhere classified
Medical bacteriology
This group covers microbiology associated with human health and disease, other than clinical microbiology.
Medical microbiology
a) Microbiology unrelated to human medicine is included in Group 3107 Microbiology. b) Microbiology related to veterinary practice is included in Group 3009 Veterinary sciences. c) Clinical microbiology is included in Group 3202 Clinical sciences.
Medical infection agents (incl. prions)
Medical mycology
Medical parasitology
Medical virology
Medical microbiology not elsewhere classified
Cell physiology
This group covers the processes and function of the human body or the physical and chemical processes involved in the functioning of the human body and its component parts.
Medical physiology
a) Medical physics and biophysics unrelated to humans are included in Group 5199 Other physical sciences. b) Basic animal physiology and comparative physiology are included in Group 3109 Zoology. c) Physiology related to specific aspects of plant or animal production or veterinary practice is included in the appropriate groups in Division 30 Agricultural, veterinary and food sciences. d) Exercise physiology is included in Group 4207 Sports science and exercise. e) Nutritional physiology is included in Group 3210 Nutrition and dietetics. f) Physiological psychology is included in Division 52 Psychology.
Human biophysics
Systems physiology
Medical physiology not elsewhere classified
Autonomic nervous system
This group covers processes and reactions of the human nervous system. It includes neurology and neuromuscular disease.
Neurosciences
a) Psychiatry and psychotherapy are included in Group 3202 Clinical sciences. b) Biological psychology is included in Group 5202 Biological psychology. c) Motor control is included in Group 4207 Sports science and exercise.
Cellular nervous system
Central nervous system
Computational neuroscience (incl. mathematical neuroscience and theoretical neuroscience)
Neurology and neuromuscular diseases
Peripheral nervous system
Sensory systems
Neurosciences not elsewhere classified
Clinical nutrition
This group covers nutrition and dietetics.
Nutrition and dietetics
a) Nutritional content and balance of foods is included in Group 3006 Food sciences. b) Metabolism is included in Group 3205 Medical biochemistry and metabolomics.
Food properties (incl. characteristics and health benefits)
Nutrigenomics and personalised nutrition
Nutritional science
Public health nutrition
Sport and exercise nutrition
Nutrition and dietetics not elsewhere classified
Cancer cell biology
This group covers oncology and carcinogenesis.
Oncology and carcinogenesis
a) Accelerators and other equipment for the production of radiation or radioisotopes for radiation therapy are included in Group 5199 Other physical sciences. b) Medical genetics other than cancer genetics is included in Group 3202 Clinical sciences. c) Tumour immunology is included in Group 3204 Immunology.
Cancer diagnosis
Cancer genetics
Cancer therapy (excl. chemotherapy and radiation therapy)
Chemotherapy
Haematological tumours
Liquid biopsies
Molecular targets
Predictive and prognostic markers
Radiation therapy
Solid tumours
Oncology and carcinogenesis not elsewhere classified
Ophthalmology
This group covers ophthalmology and optometry.
Ophthalmology and optometry
Optical technology
Optometry
Vision science
Ophthalmology and optometry not elsewhere classified
Adolescent health
This group covers paediatrics.
Paediatrics
a) Stem cells and tissue engineering are included in Group 3206 Medical biotechnology.
Infant and child health
Neonatology
Paediatrics not elsewhere classified
Basic pharmacology
This group covers the preparation, properties, uses and actions of drugs for medical uses. It includes pharmacogenomics.
Pharmacology and pharmaceutical sciences
a) Medicinal chemistry is included in Group 3404 Medicinal and biomolecular chemistry. b) Pharmacology for veterinary use is included in Group 3009 Veterinary sciences. c) Dental therapeutics, pharmacology and toxicology are included in Group 3203 Dentistry. d) Nanomedicine is included in Group 3206 Medical biotechnology.
Clinical pharmacology and therapeutics
Clinical pharmacy and pharmacy practice
Pharmaceutical delivery technologies
Pharmaceutical sciences
Pharmacogenomics
Toxicology (incl. clinical toxicology)
Pharmacology and pharmaceutical sciences not elsewhere classified
Foetal development and medicine
This group covers reproductive medicine. It includes: assisted reproduction; foetal development and medicine; and obstetrics and gynaecology.
Reproductive medicine
a) Stem cells and tissue engineering are included in Group 3206 Medical biotechnology. b) Paediatrics is included in Group 3213 Paediatrics.
Obstetrics and gynaecology
Reproductive medicine not elsewhere classified
Other biomedical and clinical sciences not elsewhere classified
This group covers biomedical and clinical sciences not elsewhere classified.
Other biomedical and clinical sciences
Architectural computing and visualisation methods
This group covers architecture.
Architecture
a) Construction and structural engineering are included in Group 4005 Civil engineering. b) Building is included in Group 3302 Building. c) History and theory of the built environment other than architectural history and theory is included in Group 3304 Urban and regional planning. d) Data visualisation and computational (parametric and generative) design is included in Group 3303 Design.
This division covers built environment and design. It includes: • architecture; • building; • design; and • urban and regional planning.
BUILT ENVIRONMENT AND DESIGN
a) Indigenous built environment and design is included in Division 45 Indigenous studies.
Architectural design
Architectural heritage and conservation
Architectural history, theory and criticism
Architectural science and technology
Architecture for disaster relief
Architecture management
Interior design
Landscape architecture
Sustainable architecture
Architecture not elsewhere classified
Automation and technology in building and construction
This group covers building.
Building
a) Civil engineering, including construction materials and engineering, and transport engineering is included in Group 4005 Civil engineering. b) Surveying is included in Group 4013 Geomatic engineering. c) Project management is included in Group 3507 Strategy, management and organisational behaviour.
Building construction management and project planning
Building industry studies
Building information modelling and management
Building organisational studies
Building science, technologies and systems
Quantity surveying
Building not elsewhere classified
Data visualisation and computational (incl. parametric and generative) design
This group covers design. It includes: • design history and theory; • ergonomics; • industrial design; • textile and fashion design; and • visual communication and graphics design.
Design
a) Architectural design and architectural history is included in Group 3301 Architecture. b) Engineering design is included in Group 4010 Engineering practice and education. c) Fine arts are included in Group 3606 Visual Arts.
Design anthropology
Design for disaster relief
Design history, theory and criticism
Design management
Design practice and methods
Ergonomics design
Fire safety design
Industrial and product design
Interaction and experience design
Models and simulations of design
Service design
Social design
Sustainable design
Textile and fashion design
Visual communication design (incl. graphic design)
Design not elsewhere classified
Community planning
This group covers urban and regional planning.
Urban and regional planning
a) Management of parks in natural environments is included in Group 4104 Environmental management. b) Agricultural land use and planning is included in Group 3002 Agriculture, land and farm management. c) Transport engineering is included in Group 4005 Civil engineering. d) Architectural history and theory is included in Group 3301 Architecture. e) Urban and regional studies other than planning is included in Group 4406 Human geography. f) Urban policy is included in Group 4407 Policy and administration.
History and theory of the built environment (excl. architecture)
Housing markets, development and management
Land use and environmental planning
Public participation and community engagement
Regional analysis and development
Regulatory planning and development assessment
Strategic, metropolitan and regional planning
Transport planning
Urban analysis and development
Urban design
Urban informatics
Urban planning and health
Urban and regional planning not elsewhere classified
Other built environment and design not elsewhere classified
This group covers built environment and design not elsewhere classified.
Other built environment and design
Analytical spectrometry
This group covers analytical chemistry.
Analytical chemistry
This division covers the chemical sciences.
CHEMICAL SCIENCES
a) Indigenous chemical sciences are included in Division 45 Indigenous studies.
Bioassays
Electroanalytical chemistry
Flow analysis
Instrumental methods (excl. immunological and bioassay methods)
Metabolomic chemistry
Quality assurance, chemometrics, traceability and metrological chemistry
Sensor technology (incl. chemical aspects)
Separation science
Analytical chemistry not elsewhere classified
Bioinorganic chemistry
This group covers inorganic chemistry.
Inorganic chemistry
a) Other material sciences are included in Groups 5104 Condensed matter physics, 3403 Macromolecular and materials chemistry, 4003 Biomedical engineering, 4016 Materials engineering and 4019 Resources engineering and extractive metallurgy. b) Mineralogy and crystallography are included in Group 3705 Geology.
Crystallography
F-block chemistry
Inorganic green chemistry
Main group metal chemistry
Metal cluster chemistry
Metal organic frameworks
Non-metal chemistry
Organometallic chemistry
Solid state chemistry
Transition metal chemistry
Inorganic chemistry not elsewhere classified
Inorganic materials (incl. nanomaterials)
This group covers macromolecular and materials chemistry. It includes nanochemistry.
Macromolecular and materials chemistry
a) Other material sciences are included in Groups 5104 Condensed matter physics, 3402 Inorganic chemistry, 4003 Biomedical engineering, 4016 Materials engineering and 4019 Resources engineering and extractive metallurgy. b) Supramolecular chemistry is included in Group 3405 Organic chemistry. c) Nanoscale characterisation and nanotechnology other than nanochemistry are included in Group 4018 Nanotechnology.
Macromolecular materials
Nanochemistry
Optical properties of materials
Physical properties of materials
Polymerisation mechanisms
Structure and dynamics of materials
Supramolecular chemistry
Theory and design of materials
Macromolecular and materials chemistry not elsewhere classified
Biologically active molecules
This group covers medicinal and biomolecular chemistry. It includes cheminformatics.
Medicinal and biomolecular chemistry
a) Biochemistry other than medical biochemistry or biomolecular chemistry is included in Group 3101 Biochemistry and cell biology. b) Pharmacology for animal use is included in Group 3009 Veterinary sciences. c) Food chemistry is included in Group 3006 Food sciences. d) Medical biochemistry is included in Group 3205 Medical biochemistry and metabolomics. e) Clinical chemistry is included in Group 3202 Clinical sciences. f) Pharmacology for human use and human toxicology is included in Group 3214 Pharmacology and pharmaceutical sciences.
Biomolecular modelling and design
Characterisation of biological macromolecules
Cheminformatics and quantitative structure-activity relationships
Glycoconjugates
Molecular medicine
Proteins and peptides
Medicinal and biomolecular chemistry not elsewhere classified
Free radical chemistry
This group covers organic chemistry.
Organic chemistry
a) Immunological and bioassay methods are included in Group 3401 Analytical chemistry. b) Medicinal and biomolecular chemistry is included in Group 3404 Medicinal and biomolecular chemistry. c) Organometallic chemistry is included in Group 3402 Inorganic chemistry. d) Biochemistry is included in Group 3101 Biochemistry and cell biology. e) Pharmacology for animal use is included in Group 3009 Veterinary sciences. f) Food chemistry is included in Group 3006 Food sciences. g) Medical biochemistry is included in Group 3205 Medical biochemistry and metabolomics. h) Clinical chemistry is included in Group 3202 Clinical sciences. i) Pharmacology for human use and human toxicology is included in Group 3214 Pharmacology and pharmaceutical sciences. j) Environmental chemistry is included in 3701 Atmospheric sciences.
Natural products and bioactive compounds
Organic chemical synthesis
Organic green chemistry
Physical organic chemistry
Organic chemistry not elsewhere classified
Catalysis and mechanisms of reactions
This group covers physical chemistry.
Physical chemistry
a) Other material sciences are included in Groups 5104 Condensed matter physics, 3402 Inorganic chemistry, 3403 Macromolecular and materials chemistry, 4003 Biomedical engineering, 4016 Materials engineering and 4019 Resources engineering and extractive metallurgy. b) Physical organic chemistry is included in Group 3405 Organic chemistry. c) Chemical engineering, including catalytic process engineering, is included in Group 4004 Chemical engineering. d) Mechanical engineering is included in Group 4017 Mechanical engineering. e) Biocatalysis is included in Group 3106 Industrial biotechnology.
Chemical thermodynamics and energetics
Colloid and surface chemistry
Electrochemistry
Molecular imaging (incl. electron microscopy and neutron diffraction)
Photochemistry
Reaction kinetics and dynamics
Solution chemistry
Transport properties and non-equilibrium processes
Physical chemistry not elsewhere classified
Computational chemistry
This group covers theoretical chemistry and computational chemistry.
Theoretical and computational chemistry
a) Reaction kinetics and dynamics is included in 3406 Physical chemistry.
Radiation and matter
Statistical mechanics in chemistry
Theoretical quantum chemistry
Theoretical and computational chemistry not elsewhere classified
Forensic chemistry
This group covers other chemical sciences not elsewhere classified. It includes forensic chemistry.
Other chemical sciences
Other chemical sciences not elsewhere classified
Accounting theory and standards
This group covers accounting, auditing and accountability.
Accounting, auditing and accountability
a) The economics of taxation are included in Group 3801 Applied economics. b) Taxation law is included in Group 4801 Commercial law.
This division covers commerce, management, tourism and services.
COMMERCE, MANAGEMENT, TOURISM AND SERVICES
a) Commerce, management, tourism and services relating to Aboriginal and Torres Strait Islanders are included in Group 4505 Aboriginal and Torres Strait Islander peoples, society and community, Māori in Group 4511 Te ahurea, reo me te hītori o te Māori (Māori culture, language and history), Pacific Peoples in Group 4517 Pacific Peoples, society and community and other Indigenous in Group 4519 Other Indigenous data, methodologies and global Indigenous studies.
Auditing and accountability
Financial accounting
International accounting
Management accounting
Not-for-profit accounting and accountability
Sustainability accounting and reporting
Taxation accounting
Accounting, auditing and accountability not elsewhere classified
Environment and climate finance
This group covers banking, finance and investment.
Banking, finance and investment
a) Financial mathematics is included in Group 4901 Applied mathematics. b) Econometrics other than financial econometrics is included in Group 3802 Econometrics. c) Demography is included in Group 4403 Demography. d) International economics is included in Group 3801 Applied economics.
Finance
Financial econometrics
Financial institutions (incl. banking)
Household finance and financial literacy
Insurance studies
International finance
Investment and risk management
Not-for-profit finance and risk
Banking, finance and investment not elsewhere classified
Business analytics
This group covers business systems in context.
Business systems in context
a) Data models, systems and quality are included in Group 4605 Data management and data science. b) Information modelling, management and ontologies are included in Group 4609 Information systems. c) Organisational planning and management is included in Group 3507 Strategy, management and organisational behaviour. d) Logistics and supply chain management is included in Group 3509 Transportation, logistics and supply chains.
Business information management (incl. records, knowledge and intelligence)
Business information systems
Forensic intelligence
Forensic science and management
Technology management
Business systems in context not elsewhere classified
Food and hospitality services
This group covers commercial services, other than tourism and transportation and freight services.
Commercial services
a) Tourism is included in Group 3508 Tourism. b) Transportation and freight services are included in Group 3509 Transportation, logistics and supply chains. c) Private policing and security services are included in Group 4402 Criminology.
Hospitality management
Real estate and valuation services
Retail
Sport and leisure management
Commercial services not elsewhere classified
Business and labour history
This group covers human resources and industrial relations.
Human resources and industrial relations
a) Organisational and occupational health and safety is included in Group 4206 Public health.
Employment equity and diversity
Human resources management
Industrial and employee relations
Occupational and workplace health and safety
Workforce planning
Workplace wellbeing and quality of working life
Human resources and industrial relations not elsewhere classified
Consumer behaviour
This group covers marketing.
Marketing
a) Tourism marketing is included in Group 3508 Tourism. b) Social impacts of marketing are included in Group 4701 Communication and media studies. c) Cultural impacts of marketing are included in Group 4702 Cultural studies. d) Market research does not constitute R&D in ANZSRC and as such should not be classified.
Consumer-oriented product or service development
Industrial marketing
Marketing communications
Marketing management (incl. strategy and customer relations)
Marketing research methodology
Marketing technology
Marketing theory
Not-for-profit marketing
Pricing (incl. consumer value estimation)
Service marketing
Social marketing
Marketing not elsewhere classified
Corporate governance
This group covers strategy, management and organisational behaviour.
Strategy, management and organisational behaviour
a) Tourism is included in Group 3508 Tourism. b) Transportation and freight services are included in Group 3509 Transportation, logistics and supply chains. c) Private policing and security services are included in Group 4402 Criminology. d) Decision theory is included in Group 5003 Philosophy. e) Human resource management and workforce planning are included in Group 3505 Human resources and industrial relations.
Corporate social responsibility
Disaster and emergency management
Entrepreneurship
Innovation management
International business
Leadership
Not-for-profit business and management
Organisation and management theory
Organisational behaviour
Organisational planning and management
Production and operations management
Project management
Public sector organisation and management
Quality management
Small business organisation and management
Stakeholder engagement
Strategy
Strategy, management and organisational behaviour not elsewhere classified
Impacts of tourism
This group covers tourism.
Tourism
a) Hospitality, sport and leisure management are included in Group 3504 Commercial services. b) Tourism geography is included in Group 4406 Human geography. c) Tourism policy is included in Group 4407 Policy and administration.
Tourism forecasting
Tourism management
Tourism marketing
Tourism resource appraisal
Tourist behaviour and visitor experience
Tourism not elsewhere classified
Air transportation and freight services
This group covers transportation, logistics and supply chains.
Transportation, logistics and supply chains
a) Transport engineering is included in Group 4005 Civil engineering. b) Transport planning is included in Group 3304 Urban and regional planning. c) Data engineering and data science is included in Group 4605 Data management and data sciences.
Intelligent mobility
Logistics
Maritime transportation and freight services
Passenger needs
Public transport
Rail transportation and freight services
Road transportation and freight services
Supply chains
Transportation, logistics and supply chains not elsewhere classified
Other commerce, management, tourism and services not elsewhere classified
This group covers commerce, management, tourism and services not elsewhere classified.
Other commerce, management, tourism and services
Art criticism
This group covers art history, theory and criticism.
Art history, theory and criticism
a) Literary studies are included in Group 4705 Literary studies. b) Curatorial and related studies are included in Group 4302 Heritage, archive and museum studies. c) Creative arts, media and communication curriculum and pedagogy is included in Group 3901 Curriculum and pedagogy. d) Music therapy is included in Group 4201 Allied health and rehabilitation science.
This division covers the creative arts and writing.
CREATIVE ARTS AND WRITING
a) Indigenous creative arts and writing are included in Division 45 Indigenous studies.
Art history
Art theory
Visual cultures
Art history, theory and criticism not elsewhere classified
Creative writing (incl. scriptwriting)
This group covers professional and creative writing.
Creative and professional writing
a) Journalism is included in 4701 Communication and media studies.
Digital writing
Professional writing and journalism practice
Site-based writing
Technical writing
Creative and professional writing not elsewhere classified
Music cognition
This group covers music.
Music
a) Song lyrics and libretti is included in Group 3602 Creative and professional writing. b) Music therapy is included in Group 4201 Allied health and rehabilitation science.
Music composition and improvisation
Music education
Music performance
Music technology and recording
Musicology and ethnomusicology
Music not elsewhere classified
Applied theatre
This group covers performing arts.
Performing arts
a) Film, television and digital media are included in Group 3605 Screen and digital media. b) Performance and installation art are included in Group 3606 Visual arts. c) Literary studies are included in Group 4705 Literary studies. d) Music therapy is included in Group 4201 Allied health and rehabilitation science.
Dance and dance studies
Drama, theatre and performance studies
Performing arts not elsewhere classified
Cinema studies
This group covers screen and digital media.
Screen and digital media
a) Computer software is included in Group 4612 Software engineering. b) Communications technologies are included in Group 4006 Communications engineering. c) Lens-based practice, including photography, is included in Group 3606 Visual arts. d) Creative writing including scriptwriting and screen writing is included in Group 3602 Creative and professional writing.
Computer gaming and animation
Digital and electronic media art
Interactive media
Screen media
Visual effects
Screen and digital media not elsewhere classified
Crafts
This group covers visual arts.
Visual arts
a) Film, television and digital media are included in Group 3605 Screen and digital media. b) Drama theatre and performance studies are included in Group 3604 Performing Arts. c) Art history, theory and criticism are included in Group 3601 Art history, theory and criticism. d) Museum Studies are included in Group 4302 Heritage, archive and museum studies.
Fine arts
Performance art
Photography, video and lens-based practice
Visual arts not elsewhere classified
Other creative arts and writing not elsewhere classified
This group covers studies in creative arts and writing not elsewhere classified.
Other creative arts and writing
Adverse weather events
This group covers atmospheric sciences.
Atmospheric sciences
a) Mesospheric, ionospheric and magnetospheric physics is included in Group 5109 Space sciences. b) Palaeoclimatology is included in Group 3709 Physical geography and environmental geoscience. c) Environmental sciences, including environmental monitoring, carbon sequestration science and impacts of climate change are included in Division 41 Environmental sciences. d) Climate change science, including processes, greenhouse gas inventories and climatology is included in Group 3702 Climate change science.
This division covers the earth sciences.
EARTH SCIENCES
a) Indigenous earth sciences are included in Division 45 Indigenous studies.
Air pollution processes and air quality measurement
Atmospheric aerosols
Atmospheric composition, chemistry and processes
Atmospheric dynamics
Atmospheric radiation
Cloud physics
Meteorology
Tropospheric and stratospheric physics
Atmospheric sciences not elsewhere classified
Climate change processes
This group covers climate change science.
Climate change science
a) Climate change impacts and adaptation is included in Group 4101 Climate change impacts and adaptation.
Climatology
Greenhouse gas inventories and fluxes
Climate change science not elsewhere classified
Exploration geochemistry
This group covers geochemistry.
Geochemistry
Inorganic geochemistry
Isotope geochemistry
Organic geochemistry
Geochemistry not elsewhere classified
Computational modelling and simulation in earth sciences
This group covers geoinformatics.
Geoinformatics
a) Information systems are included in Group 4609 Information systems. b) Computer vision is included in Group 4603 Computer vision and multimedia computation. c) Ecological, population and community analysis is included in Group 3102 Bioinformatics and computational biology. d) Geospatial and geosystem data visualisation is included in Group 4013 Geomatic engineering.
Earth and space science informatics
Geoscience data visualisation
Geoinformatics not elsewhere classified
Biomineralisation
This group covers geology. It includes palaeontology, including palaeozoology, palaeobotany and palynology, other than that associated with palaeoecological studies.
Geology
a) Planetary science (excl. solar system and planetary geology) is included in Group 5101 Astronomical sciences. b) Solid state chemistry and the chemical aspects of crystallography are included in Group 3402 Inorganic chemistry. c) Oceanography is included in Group 3708 Oceanography. d) Palaeoclimatology is included in Group 3709 Physical geography and environmental geoscience. e) Palaeontology associated with palaeoecological studies is included in Group 3103 Ecology. f) Materials engineering is included in Group 4016 Materials engineering. g) Mining, mineral processing and metallurgy are included in Group 4019 Resources engineering and extractive metallurgy. h) Solar system planetary science (excl. planetary geology) is included in 5109 Space sciences.
Geochronology
Igneous and metamorphic petrology
Marine geoscience
Mineralogy and crystallography
Palaeontology (incl. palynology)
Planetary geology
Resource geoscience
Sedimentology
Stratigraphy (incl. biostratigraphy, sequence stratigraphy and basin analysis)
Structural geology and tectonics
Volcanology
Geology not elsewhere classified
Applied geophysics
This group covers geophysics.
Geophysics
a) Geophysical fluid dynamics is included in Group 4012 Fluid mechanics and thermal engineering.
Electrical and electromagnetic methods in geophysics
Geodesy
Geodynamics
Geothermics and radiometrics
Gravimetrics
Magnetism and palaeomagnetism
Petrophysics and rock mechanics
Seismology and seismic exploration
Geophysics not elsewhere classified
Contaminant hydrology
This group covers hydrology.
Hydrology
a) Surface water pollution processes and water quality measurement is included in Group 4105 Pollution and contamination.
Ecohydrology
Groundwater hydrology
Surface water hydrology
Urban hydrology
Hydrology not elsewhere classified
Biological oceanography
This group covers oceanography.
Oceanography
a) Marine geoscience is included in Group 3705 Geology. b) Marine ecology is included in Group 3103 Ecology.
Chemical oceanography
Physical oceanography
Oceanography not elsewhere classified
Geomorphology and earth surface processes
This group covers physical geography and environmental geoscience
Physical geography and environmental geoscience
a) Climatology is included in Group 3701 Atmospheric sciences. b) Environmental sciences, including environmental monitoring, carbon sequestration science and impacts of climate change are included in Division 41 Environmental sciences. c) Climate change science, including processes, greenhouse gas inventories and climatology is included in Group 3702 Climate change science. d) Hydrology other than agricultural hydrology is included in Group 3707 Hydrology. e) Agricultural hydrology is included in Group 3002 Agriculture, land and farm management f) Water reticulation for household and non-agricultural industry use is included in Groups 4004 Chemical engineering and 4005 Civil engineering. g) Environmental engineering is included in Group 4011 Environmental engineering. h) Social aspects of geography are included in Group 4406 Human geography.
Glaciology
Natural hazards
Palaeoclimatology
Quaternary environments
Regolith and landscape evolution
Physical geography and environmental geoscience not elsewhere classified
Earth system sciences
This group covers earth sciences not elsewhere classified.
Other earth sciences
Other earth sciences not elsewhere classified
Agricultural economics
This group covers applied economics.
Applied economics
a) Taxation accounting is included in Group 3501 Accounting, auditing and accountability. b) Economic geography is included in Group 4406 Human geography. c) Taxation law is included in Group 4801 Commercial law. d) International finance is included in Group 3502 Banking, finance and investment.
This division covers economics.
ECONOMICS
a) Indigenous economics is included in Division 45 Indigenous studies.
Behavioural economics
Economic history
Economics of education
Environment and resource economics
Experimental economics
Financial economics
Health economics
Industry economics and industrial organisation
International economics
Labour economics
Macroeconomics (incl. monetary and fiscal theory)
Public economics - public choice
Public economics - publicly provided goods
Public economics - taxation and revenue
Tourism economics
Transport economics
Urban and regional economics
Welfare economics
Applied economics not elsewhere classified
Cross-sectional analysis
This group covers econometrics.
Econometrics
a) Financial econometrics is included in Group 3502 Banking, finance and investment.
Econometric and statistical methods
Economic models and forecasting
Panel data analysis
Time-series analysis
Econometrics not elsewhere classified
History of economic thought
This group covers economic theory. It includes history of economic thought.
Economic theory
Macroeconomic theory
Mathematical economics
Microeconomic theory
Economic theory not elsewhere classified
Comparative economic systems
This group covers economics not elsewhere classified.
Other economics
Ecological economics
Heterodox economics
Other economics not elsewhere classified
Creative arts, media and communication curriculum and pedagogy
This group covers curriculum and pedagogy.
Curriculum and pedagogy
a) Teacher education and the professional development of educators is included in Group 3904 Specialist studies in education. b) Educational linguistics is included in Group 4704 Linguistics. c) Engineering education is included in Group 4010 Engineering practice and education.
This division covers education.
EDUCATION
a) Indigenous education is included in Division 45 Indigenous studies.
Curriculum and pedagogy theory and development
Economics, business and management curriculum and pedagogy
English and literacy curriculum and pedagogy (excl. LOTE, ESL and TESOL)
Environmental education curriculum and pedagogy
Geography education curriculum and pedagogy
Humanities and social sciences curriculum and pedagogy (excl. economics, business and management)
LOTE, ESL and TESOL curriculum and pedagogy
Mathematics and numeracy curriculum and pedagogy
Medicine, nursing and health curriculum and pedagogy
Physical education and development curriculum and pedagogy
Religion curriculum and pedagogy
Science, technology and engineering curriculum and pedagogy
Vocational education and training curriculum and pedagogy
Work integrated learning (incl. internships)
Curriculum and pedagogy not elsewhere classified
Education policy
This group covers education policy, sociology and philosophy.
Education policy, sociology and philosophy
History and philosophy of education
Sociology of education
Education policy, sociology and philosophy not elsewhere classified
Continuing and community education
This group covers systems for the delivery of education services.
Education systems
a) Educational administration and special education and disability are included in Group 3904 Specialist studies in education.
Early childhood education
Higher education
Primary education
Professional education and training
Secondary education
Teacher education and professional development of educators
Technical, further and workplace education
Education systems not elsewhere classified
Comparative and cross-cultural education
This group covers specialist studies in education.
Specialist studies in education
a) Education systems, including Māori primary and early childhood education, are included in Group 3903 Education systems. b) Curriculum and pedagogy relating to specific subject areas is included in Group 3901 Curriculum and pedagogy. c) Economics of education are included in Group 3801 Applied economics. d) Education policy is included in Group 3903 Education systems. e) Educational psychology is included in Group 5201 Applied and developmental psychology. f) Educational linguistics is included in Group 4704 Linguistics. g) History and philosophy of education is included in Group 5002 History and philosophy of specific fields. h) Teacher education and professional development of educators is included in Group 3903 Education systems.
Education assessment and evaluation
Educational administration, management and leadership
Educational counselling
Educational technology and computing
Gender, sexuality and education
Inclusive education
Learning analytics
Learning sciences
Multicultural education (excl. Aboriginal and Torres Strait Islander, Māori and Pacific Peoples)
Special education and disability
Teacher and student wellbeing
Specialist studies in education not elsewhere classified
Other education not elsewhere classified
This group covers education not elsewhere classified.
Other education
Aerospace materials
This group covers aerospace engineering including avionics and aeronautical and astronomical engineering.
Aerospace engineering
a) Space sciences are included in Group 5109 Space sciences. b) Transport engineering other than aerospace engineering is included in Group 4005 Civil engineering. c) Remote sensing is included in Group 4013 Geomatic engineering. d) Heat and mass transfer operations, fluidisation, fluid mechanics and turbulent flows are included in Group 4012 Fluid mechanics and thermal engineering. e) Satellite communications are included in Group 4006 Communications engineering. f) Aerodynamics is included in 4012 Fluid mechanics and thermal engineering.
This division covers engineering.
ENGINEERING
a) Indigenous engineering is included in Division 45 Indigenous studies.
Aerospace structures
Aircraft performance and flight control systems
Avionics
Flight dynamics
Hypersonic propulsion and hypersonic aerothermodynamics
Satellite, space vehicle and missile design and testing
Aerospace engineering not elsewhere classified
Automotive combustion and fuel engineering
This group covers automotive engineering.
Automotive engineering
a) Combustion and fuel engineering without automotive applications is included in Group 4004 Chemical engineering. b) Transport engineering other than automotive engineering is included in Group 4005 Civil engineering. c) Mechatronics without automotive applications is included in Group 4007 Control engineering, mechatronics and robotics. d) Materials engineering without automotive applications is included in Group 4016 Materials engineering. e) Heat and mass transfer operations, fluidisation, fluid mechanics and turbulent flows are included in Group 4012 Fluid mechanics and thermal engineering. f) Electrical energy generation and storage are included in 4008 Electrical engineering.
Automotive engineering materials
Automotive mechatronics and autonomous systems
Automotive safety engineering
Hybrid and electric vehicles and powertrains
Automotive engineering not elsewhere classified
Biofabrication
This group covers biomedical engineering.
Biomedical engineering
a) Regenerative medicine and medical biotechnology is included in Group 3206 Medical biotechnology. b) Other material sciences are included in Groups 5104 Condensed matter physics, 3402 Inorganic chemistry, 3403 Macromolecular and materials chemistry, 4016 Materials engineering, and 4019 Resources engineering and extractive metallurgy. c) Materials used in dentistry are included in Group 3203 Dentistry. d) Medical robotics and biomechatronics are included in Group 4007 Control engineering, mechatronics and robotics.
Biomaterials
Biomechanical engineering
Biomedical imaging
Biomedical instrumentation
Computational physiology
Mechanobiology
Medical devices
Neural engineering
Rehabilitation engineering
Tissue engineering
Biomedical engineering not elsewhere classified
Carbon capture engineering (excl. sequestration)
This group covers chemical engineering including process technologies.
Chemical engineering
a) Chemistry is included in Division 34 Chemical sciences. b) Carbon sequestration science and modelling are included in Group 4101 Climate change impacts and adaptation. c) Combustion and fuel engineering for automotive applications is included in Group 4002 Automotive engineering. d) Water resources and quality engineering are included in Group 4005 Civil engineering. e) Process control and simulation associated with control engineering is included in Group 4007 Control engineering, mechatronics and robotics. f) Fluidisation, fluid mechanics and heat and mass transfer operations are included in Group 4012 Fluid mechanics and thermal engineering. g) Biocatalysis is included in Group 3106 Industrial biotechnology. h) Non-Newtonian fluid flows including rheology are included in Group 4012 Fluid mechanics and thermal engineering.
Chemical and thermal processes in energy and combustion
Chemical engineering design
Electrochemical energy storage and conversion
Food engineering
Powder and particle technology
Process control and simulation
Reaction engineering (excl. nuclear reactions)
Separation technologies
Wastewater treatment processes
Water treatment processes
Chemical engineering not elsewhere classified
Architectural engineering
This group covers civil engineering.
Civil engineering
a) Hydrology other than agricultural hydrology is included in Group 3707 Hydrology. b) Agricultural hydrology is included in Group 3002 Agriculture, land and farm management. c) Aerospace engineering is included in Group 4001 Aerospace engineering. d) Automotive engineering is included in Group 4002 Automotive engineering. e) Water treatment processes are included in Group 4004 Chemical engineering. f) Surveying is included in Group 4013 Geomatic engineering. g) Maritime engineering is included in Group 4015 Maritime engineering. h) Materials engineering without civil engineering applications is included in Group 4016 Materials engineering. i) Geotechnical engineering associated with mining and mineral extraction is included in Group 4019 Resources engineering and extractive metallurgy. j) Agricultural engineering is included in Group 4099 Other engineering. k) Building science and techniques including acoustics, lighting, structure, thermal and moisture are included in Group 3302 Building. l) Building science, construction management and quantity surveying are included in Group 3302 Building. m) Transport planning is included in Group 3304 Urban and regional planning. n) Mechanical engineering asset management is included in Group 4017 Mechanical engineering.
Civil geotechnical engineering
Complex civil systems
Construction engineering
Construction materials
Earthquake engineering
Fire safety engineering
Infrastructure engineering and asset management
Structural dynamics
Structural engineering
Timber engineering
Transport engineering
Water resources engineering
Civil engineering not elsewhere classified
Antennas and propagation
This group covers communications engineering.
Communications engineering
a) Electronic devices and digital hardware for communication engineering is included in Group 4009 Electronics, sensors and digital hardware. b) Molecular and biological materials are included in Group 4016 Materials engineering.
Data communications
Molecular, biological, and multi-scale communications
Network engineering
Optical fibre communication systems and technologies
Satellite communications
Signal processing
Wireless communication systems and technologies (incl. microwave and millimetrewave)
Communications engineering not elsewhere classified
Assistive robots and technology
This group covers control engineering, mechatronics and robotics.
Control engineering, mechatronics and robotics
a) Automotive mechatronics and autonomous systems are included in Field 400203 Automotive mechatronics and autonomous systems. b) Control Theory is included in Group 4901 Applied mathematics.
Automation engineering
Autonomous vehicle systems
Biomechatronics
Control engineering
Field robotics
Manufacturing robotics
Mechatronics hardware design and architecture
Medical robotics
Micro-manipulation
Simulation, modelling, and programming of mechatronics systems
Control engineering, mechatronics and robotics not elsewhere classified
Circuits and systems
This group covers electrical engineering including electrical circuits and systems and electromagnetics, but excluding electronics, communications and control engineering
Electrical engineering
a) Electronic circuits and systems are included in Group 4009 Electronics, sensors and digital hardware. b) Electromagnetics of antennas and propagation is included in Group 4006 Communications engineering.
Electrical circuits and systems
Electrical energy generation (incl. renewables, excl. photovoltaics)
Electrical energy storage
Electrical energy transmission, networks and systems
Electrical machines and drives
Engineering electromagnetics
Photovoltaic power systems
Electrical engineering not elsewhere classified
Analog electronics and interfaces
This group covers electronics, sensors and digital hardware.
Electronics, sensors and digital hardware
a) Semiconductor materials are included in Group 4016 Materials engineering. b) Quantum device science is included in Group 5108 Quantum physics.
Digital electronic devices
Digital processor architectures
Electronic device and system performance evaluation, testing and simulation
Electronic instrumentation
Electronic sensors
Industrial electronics
Microelectronics
Photonic and electro-optical devices, sensors and systems (excl. communications)
Photovoltaic devices (solar cells)
Power electronics
Quantum engineering systems (incl. computing and communications)
Radio frequency engineering
Electronics, sensors and digital hardware not elsewhere classified
Engineering design
This group covers engineering practice and education.
Engineering practice and education
a) Risk engineering associated with vehicle safety, fire safety and manufacturing safety, is included in Group 4002 Automotive engineering, Group 4005 Civil engineering, and Group 4014 Manufacturing engineering, respectively. b) Systems engineering associated with the single disciplines of aerospace engineering, civil engineering, communication systems, electronics and electrical engineering is included in Group 4001 Aerospace engineering, Group 4005 Civil engineering, Group 4006 Communications engineering, Group 4009 Electronics, sensors and digital hardware and Group 4008 Electrical engineering, respectively. c) Education theory and practice in areas not principally focussed on engineering is included in Group 3901 Curriculum and pedagogy.
Engineering education
Engineering practice
Humanitarian engineering
Risk engineering
Systems engineering
Engineering practice and education not elsewhere classified
Air pollution modelling and control
This group covers environmental engineering.
Environmental engineering
a) Hydrology other than agricultural hydrology is included in Group 3707 Hydrology. b) Environmental sciences is included in Division 41 Environmental sciences. c) Agricultural hydrology is included in Group 3002 Agriculture, land and farm management. d) Protection of infrastructure from climate change and other environmental factors is included in Group 4005 Civil engineering. e) Environmental biotechnology, including bioremediation, is included in Group 4103 Environmental biotechnology.
Environmentally sustainable engineering
Global and planetary environmental engineering
Health and ecological risk assessment
Life cycle assessment and industrial ecology
Waste management, reduction, reuse and recycling
Environmental engineering not elsewhere classified
Aerodynamics (excl. hypersonic aerodynamics)
This group covers fluid mechanics and thermal engineering.
Fluid mechanics and thermal engineering
a) Hypersonic aerothermodynamics is included in Group 4001 Aerospace engineering. b) Hydrodynamics in maritime engineering applications is included in Group 4015 Maritime engineering. c) Thermal processes in chemical energy transformation and combustion is included in Group 4004 Chemical engineering.
Bio-fluids
Biomedical fluid mechanics
Computational methods in fluid flow, heat and mass transfer (incl. computational fluid dynamics)
Experimental methods in fluid flow, heat and mass transfer
Fluid-structure interaction and aeroacoustics
Fundamental and theoretical fluid dynamics
Geophysical and environmental fluid flows
Hydrodynamics and hydraulic engineering
Microfluidics and nanofluidics
Multiphysics flows (incl. multiphase and reacting flows)
Non-Newtonian fluid flows (incl. rheology)
Turbulent flows
Fluid mechanics and thermal engineering not elsewhere classified
Cartography and digital mapping
This group covers geomatic engineering.
Geomatic engineering
a) Geophysics and Geodesy are included in Group 3706 Geophysics. b) Antennas for use in remote sensing are included in Group 4006 Communication engineering.
Geospatial information systems and geospatial data modelling
Navigation and position fixing
Photogrammetry and remote sensing
Satellite-based positioning
Surveying (incl. hydrographic surveying)
Geomatic engineering not elsewhere classified
Additive manufacturing
This group covers manufacturing engineering.
Manufacturing engineering
a) Post-harvest packaging, transportation and storage of agricultural products are included in Division 30 Agricultural, veterinary and food sciences. b) Automotive engineering and automotive mechatronics are included in Group 4002 Automotive engineering. c) Membrane and separation technologies are included in Group 4004 Chemical engineering. d) Manufacturing robotics is included in Group 4007 Control engineering, mechatronics and robotics. e) Food packaging, preservation and safety are included in Group 3006 Food sciences. f) Heat and mass transfer operations, fluidisation and fluid mechanics and turbulent flows are included in Group 4012 Fluid mechanics and thermal engineering. g) Applications of biosensors to manufacturing are included in Group 3106 Industrial biotechnology. h) Manufacturing robotics and mechatronics, other than their automotive applications are included in Group 4007 Control engineering, mechatronics and robotics.
CAD/CAM systems
Flexible manufacturing systems
Industrial engineering
Machine tools
Machining
Manufacturing management
Manufacturing processes and technologies (excl. textiles)
Manufacturing safety and quality
Microtechnology
Packaging, storage and transportation (excl. food and agricultural products)
Precision engineering
Textile technology
Manufacturing engineering not elsewhere classified
Marine engineering
This group covers maritime engineering.
Maritime engineering
a) Transport engineering other than aerospace engineering is included in Group 4005 Civil engineering. b) Fluidisation, fluid mechanics and turbulent flows are included in Group 4012 Fluid mechanics and thermal engineering.
Naval architecture
Ocean engineering
Ship and platform structures (incl. maritime hydrodynamics)
Special vehicles
Maritime engineering not elsewhere classified
Ceramics
This group covers materials engineering. It includes: • ceramics science, technologies and engineering; • polymer and textiles engineering; • composite and hybrid materials; • physical metallurgy and alloy materials; • functional materials; and • semiconductor materials science and technologies.
Materials engineering
a) Materials physics is included in Group 5104 Condensed matter physics. b) Materials chemistry, including the theory and design of materials, is included in Group 3403 Macromolecular and materials chemistry. c) Engineering of materials for automotive applications is included in Group 4002 Automotive engineering. d) Biomaterials are included in Group 4003 Biomedical engineering. e) Powder and particle technology is included in Group 4004 Chemical engineering. f) Construction materials are included in Group 4005 Civil engineering. g) Extractive metallurgy is included in Group 4019 Resource engineering and extractive metallurgy. h) Nanomaterials, molecular and organic electronics, and nanotechnology are included in Group 4018 Nanotechnology. i) Electro-optical, photonic and photovoltaic devices are included in Group 4009 Electronics, sensors and digital hardware.
Composite and hybrid materials
Compound semiconductors
Elemental semiconductors
Functional materials
Glass
Metals and alloy materials
Organic semiconductors
Polymers and plastics
Timber, pulp and paper
Wearable materials
Materials engineering not elsewhere classified
Acoustics and noise control (excl. architectural acoustics)
This group covers mechanical engineering.
Mechanical engineering
a) Control theory is included in Group 4901 Applied mathematics. b) Energy generation from photovoltaic devices (solar cells) is included in Group 4009 Electronics, sensors and digital hardware. c) Heat and mass transfer operations, fluidisation and fluid mechanics and turbulent flows are included in Group 4012 Fluid mechanics and thermal engineering. d) Nanoelectromechanical Systems (NEMS) are included in Group 4018 Nanotechnology. e) Architectural acoustics is included in Group 3301 Architecture. f) Automation, control engineering and autonomous vehicles are included in Group 4007 Control engineering, mechatronics and robotics. g) Electrical energy generation and storage is included in Group 4008 Electrical engineering. h) Chemical energy generation and storage is included in Group 4004 Chemical engineering. i) Automotive combustion and fuel engineering is included in Group 4002 Automotive engineering. j) Control engineering, mechatronics and robotics is included in Group 4007 Control engineering, mechatronics and robotics.
Dynamics, vibration and vibration control
Energy generation, conversion and storage (excl. chemical and electrical)
Mechanical engineering asset management
Microelectromechanical systems (MEMS)
Numerical modelling and mechanical characterisation
Solid mechanics
Tribology
Mechanical engineering not elsewhere classified
Micro- and nanosystems
This group covers nanotechnology.
Nanotechnology
a) Nanobiotechnology is included in Group 3106 Industrial biotechnology. b) Medical biotechnology is included in Group 3206 Medical biotechnology.
Molecular and organic electronics
Nanoelectromechanical systems
Nanoelectronics
Nanofabrication, growth and self assembly
Nanomanufacturing
Nanomaterials
Nanometrology
Nanophotonics
Nanoscale characterisation
Nanotechnology not elsewhere classified
Electrometallurgy
This group covers resources engineering and extractive metallurgy.
Resources engineering and extractive metallurgy
a) Earth sciences are included in Division 37 Earth sciences. b) Geotechnical engineering associated with civil engineering is included in Group 4005 Civil engineering. c) Physical metallurgy is included in Group 4016 Materials engineering.
Geomechanics and resources geotechnical engineering
Hydrometallurgy
Mineral processing/beneficiation
Mining engineering
Nuclear engineering (incl. fuel enrichment and waste processing and storage)
Petroleum and reservoir engineering
Pyrometallurgy
Resources engineering and extractive metallurgy not elsewhere classified
Agricultural engineering
This group covers engineering not elsewhere classified. It includes: • agricultural engineering; • engineering instrumentation; • granular mechanics.
Other engineering
Engineering instrumentation
Granular mechanics
Other engineering not elsewhere classified
Carbon sequestration science
This group covers climate change impacts and adaptation.
Climate change impacts and adaptation
a) Climate change science and processes are included in Group 3702 Climate change science.
This division covers environmental sciences.
ENVIRONMENTAL SCIENCES
a) Indigenous environmental sciences are included in Division 45 Indigenous studies.
Ecological impacts of climate change and ecological adaptation
Human impacts of climate change and human adaptation
Climate change impacts and adaptation not elsewhere classified
Bioavailability and ecotoxicology
This group covers applications of ecology.
Ecological applications
a) Conservation and biodiversity are included in Group 4104 Environmental management. b) Basic ecological research which includes terrestrial ecology is included in Group 3103 Ecology.
Biosecurity science and invasive species ecology
Ecosystem function
Ecosystem services (incl. pollination)
Fire ecology
Landscape ecology
Ecological applications not elsewhere classified
Biodiscovery
This group covers environmental biotechnology.
Environmental biotechnology
a) Environmental engineering is included in Group 4011 Environmental engineering. b) Genetic modification of plants, microbes or animals for agricultural purposes is included in Group 3001 Agricultural biotechnology. c) Genetic modification of plants, microbes or animals for industrial purposes (other than agriculture) is included in Group 3106 Industrial biotechnology. d) Genetic modification of plants, microbes or animals for medical purposes is included in Group 3206 Medical biotechnology. e) Nanometrology is included in Group 4018 Nanotechnology.
Biological control
Bioremediation
Environmental biotechnology diagnostics (incl. biosensors)
Environmental marine biotechnology
Environmental nanotechnology and nanometrology
Environmental biotechnology not elsewhere classified
Conservation and biodiversity
This group covers environmental management.
Environmental management
a) Ecological applications are included in Group 4102 Ecological applications. b) Management of land for agricultural production other than forestry production is included in Group 3002 Agriculture, land and farm management. c) Management of forests for forestry production is included in Group 3007 Forestry sciences. d) Bioremediation and environmental biosensors are included in Group 4103 Environmental biotechnology. e) Management of land and parks in built environments is included in Group 3304 Urban and regional planning. f) Environment policy is included in Group 4407 Policy and Administration. g) Waste management and recycling are included in Group 4011 Environmental engineering. h) Environmental education curriculum and pedagogy is included in Group 3901 Curriculum and pedagogy.
Environmental assessment and monitoring
Environmental education and extension
Environmental rehabilitation and restoration
Natural resource management
Wildlife and habitat management
Environmental management not elsewhere classified
Environmental biogeochemistry
This group covers pollution and contamination.
Pollution and contamination
a) Processes, modelling and mitigation of air pollution is included in Group 3701 Atmospheric sciences. b) Pollution modelling and control, environmental sustainable engineering and waste management is included in Group 4011 Environmental engineering.
Noise and wave pollution processes and measurement
Groundwater quality processes and contaminated land assessment
Surface water quality processes and contaminated sediment assessment
Pollution and contamination not elsewhere classified
Land capability and soil productivity
This group covers soil sciences.
Soil sciences
a) Environmental chemistry is included in Group 3499 Other chemical sciences. b) Management of land and soil for agricultural production is included in Group 3002 Agriculture, land and farm management. c) Carbon capture engineering is included in Group 4004 Chemical engineering. d) Environmental biogeochemistry is included in Group 4103 Environmental biotechnology.
Pedology and pedometrics
Soil biology
Soil chemistry and soil carbon sequestration (excl. carbon sequestration science)
Soil physics
Soil sciences not elsewhere classified
Other environmental sciences not elsewhere classified
This group covers other environmental sciences not elsewhere classified.
Other environmental sciences
Arts therapy
This group covers allied health and rehabilitation science.
Allied health and rehabilitation science
a) Nutrition and dietetics is included in Group 3210 Nutrition and dietetics.
This division covers health sciences.
HEALTH SCIENCES
a) Indigenous health sciences and services are included in Division 45 Indigenous studies.
Audiology
Music therapy
Occupational therapy
Orthoptics
Physiotherapy
Podiatry
Prosthetics and orthotics
Rehabilitation
Speech pathology
Allied health and rehabilitation science not elsewhere classified
Behavioural epidemiology
This group covers epidemiology.
Epidemiology
Disease surveillance
Environmental epidemiology
Epidemiological methods
Epidemiological modelling
Forensic epidemiology
Major global burdens of disease
Nutritional epidemiology
Occupational epidemiology
Social epidemiology
Epidemiology not elsewhere classified
Aged health care
This group covers health services and systems.
Health services and systems
a) Applications in health is included in Group 4608 Human-centred computing.
Digital health
Family care
General practice
Health and community services
Health care administration
Health counselling
Health informatics and information systems
Health management
Health surveillance
Health systems
Implementation science and evaluation
Mental health services
Multimorbidity
One health
Palliative care
Patient safety
People with disability
Primary health care
Residential client care
Rural and remote health services
Health services and systems not elsewhere classified
Clinical midwifery
This group covers midwifery.
Midwifery
a) Medicine, nursing and health curriculum and pedagogy is included in Group 3901 Curriculum and pedagogy.
Models of care and place of birth
Psychosocial aspects of childbirth and perinatal mental health
Midwifery not elsewhere classified
Acute care
This group covers nursing.
Nursing
a) Aged, people with disability, family and residential client care are included in Group 4203 Health services and systems. b) Midwifery is included in Group 4204 Midwifery. c) Medicine, nursing and health curriculum and pedagogy is included in Group 3901 Curriculum and pedagogy.
Aged care nursing
Community and primary care
Mental health nursing
Nursing workforce
Sub-acute care
Nursing not elsewhere classified
Community child health
This group covers public health.
Public health
a) Health informatics is included in Group 4203 Health services and systems. b) Nursing is included in Group 4205 Nursing. c) Nutrition and public nutrition intervention is included in Group 3210 Nutrition and dietetics. d) Health economics is included in Group 3801 Applied economics. e) Demography is included in Group 4403 Demography. f) Health policy is included in Group 4407 Policy and administration. g) Human bioethics and medical ethics are included in Group 5001 Applied ethics. h) Medicine, nursing and health curriculum and pedagogy is included in Group 3901 Curriculum and pedagogy. i) Occupational and workplace health and safety are included Group 3505 Human resources and industrial relations.
Health equity
Health promotion
Injury prevention
Preventative health care
Social determinants of health
Public health not elsewhere classified
Biomechanics
This group covers sports science and exercise.
Sports science and exercise
Exercise physiology
Motor control
Sports science and exercise not elsewhere classified
Chiropractic
This group covers traditional, complementary and integrative medicine.
Traditional, complementary and integrative medicine
a) Indigenous traditional medicine is included in Division 45 Indigenous studies.
Naturopathy
Traditional Chinese medicine and treatments
Traditional, complementary and integrative medicine not elsewhere classified
Other health sciences not elsewhere classified
This group covers other health sciences not elsewhere classified.
Other health sciences
Archaeological science
This group covers archaeology.
Archaeology
a) Remote sensing and surveying are included in Group 4013 Geomatic engineering. b) Anthropology is included in Group 4401 Anthropology.
This division covers history, heritage and archaeology.
HISTORY, HERITAGE AND ARCHAEOLOGY
a) Indigenous history, heritage and archaeology are included in Division 45 Indigenous studies.
Archaeology of Asia, Africa and the Americas
Archaeology of Australia (excl. Aboriginal and Torres Strait Islander)
Archaeology of Europe, the Mediterranean and the Levant
Archaeology of New Zealand (excl. Māori)
Digital archaeology
Historical archaeology (incl. industrial archaeology)
Maritime archaeology
Archaeology not elsewhere classified
Archival, repository and related studies
This group covers heritage, archive and museum studies. It includes heritage and cultural conservation.
Heritage, archive and museum studies
a) Librarianship is included in Group 4610 Library and information studies. b) Cultural studies are included in Group 4702 Cultural studies.
Critical heritage, museum and archive studies
Cultural heritage management (incl. world heritage)
Digital heritage
Heritage and cultural conservation
Heritage collections and interpretations
Heritage tourism, visitor and audience studies
Intangible heritage
Materials conservation
Heritage, archive and museum studies not elsewhere classified
Asian history
This group covers the study of the history of peoples, nations or geographic regions. It includes biography.
Historical studies
a) History of architecture is included in Group 3301 Architecture. b) History of design is included in Group 3303 Design. c) History of the built environment is included in Group 3304 Urban and regional planning. d) Art history is included in Group 3601 Art history, theory and criticism. e) History of specific concepts or fields of study (including the sciences, humanities and social sciences) which defy geographical classification other than architecture, design, built environment and art are included in Group 5002 History and philosophy of specific fields.
Australian history
Biography
British history
Classical Greek and Roman history
Digital history
Environmental history
European history (excl. British, classical Greek and Roman)
Gender history
Global and world history
Historical studies of crime
Histories of race
History of empires, imperialism and colonialism
History of religion
History of the pacific
International history
Latin and South American history
Middle Eastern and North African history
Migration history
New Zealand history
North American history
Sub-Saharan African history
Transnational history
Historical studies not elsewhere classified
Other history, heritage and archaeology not elsewhere classified
This group covers history, heritage and archaeology not elsewhere classified.
Other history, heritage and archaeology
Anthropology of development
This group covers anthropology.
Anthropology
a) Anthropological genetics is included in Group 3105 Genetics. b) Archaeology is included in Group 4301 Archaeology.
This division covers human society.
HUMAN SOCIETY
a) Indigenous human society is included in Division 45 Indigenous studies.
Anthropology of gender and sexuality
Biological (physical) anthropology
Environmental anthropology
Linguistic anthropology
Medical anthropology
Social and cultural anthropology
Anthropology not elsewhere classified
Causes and prevention of crime
This group covers criminology.
Criminology
a) Forensic biology is included in Group 3199 Other biological sciences. b) Forensic chemistry is included in Group 3499 Other chemical sciences. c) Forensic intelligence and forensic science and management is included in Group 3503 Business systems in context. d) Forensic epidemiology is included in Group 4202 Epidemiology. e) Historical studies in crime is included in Group 4303 Historical studies. f) Crime policy is included in Group 4407 Policy and administration. g) Digital forensics is included in Group 4604 Cybersecurity and privacy. h) International criminal law is included in Group 4803 International and comparative law. i) Criminal Law is included in Group 4804 Law. j) Criminal procedure is included in 4805 Legal systems. k) Forensic evaluation, inference and statistics is included in Group 4905 Statistics. l) Forensic psychology is included in Group 5201 Applied and developmental psychology.
Correctional theory, offender treatment and rehabilitation
Courts and sentencing
Crime and social justice
Criminological theories
Critical approaches to crime
Cybercrime
Environmental crime
Gender and crime
Organised crime
Police administration, procedures and practice
Private policing and security services
Race/ethnicity and crime
Sociological studies of crime
State crime
Technology, crime and surveillance
Terrorism
Victims
White collar crime
Criminology not elsewhere classified
Family and household studies
This group covers demography.
Demography
a) Actuarial studies are included in Group 3502 Banking, finance and investment.
Fertility
Migration
Mortality
Population trends and policies
Demography not elsewhere classified
Development cooperation
This group covers development studies.
Development studies
a) Community planning; Management and development of housing markets; Urban and regional analysis and development; Transport planning; and urban design are included in Group 3304 Urban and regional planning. b) Economic development and growth is included in Group 3801 Applied economics. c) Anthropology of development is included in Group 4401 Anthropology. d) Urban and regional studies are included in Group 4406 Human geography. e) International and development communication is included in Group 4701 Communication and media studies.
Humanitarian disasters, conflict and peacebuilding
Labour, migration and development
Political economy and social change
Poverty, inclusivity and wellbeing
Rural community development
Socio-economic development
Urban community development
Development studies not elsewhere classified
Feminist and queer theory
This group covers gender studies.
Gender studies
a) Gender, sexuality and education is included 3904 Specialist studies in education. b) Gender history is included in Group 4303 Historical studies. c) Anthropology of gender and sexuality is included in Group 4401 Anthropology. d) Gender and crime is included in Group 4402 Criminology. e) Gender and politics is included in Group 4408 Political science. f) Gender, policy and administration is included in Group 4407 Policy and administration. g) Sociology of gender is included in Group 4410 Sociology. h) Culture, representation and identity is included in Group 4702 Cultural studies. i) Law, gender and sexuality is included in Group 4804 Law. j) Gender psychology is included in Group 5205 Social and personality psychology.
Feminist methodologies
Feminist theory
Gender relations
Intersectional studies
Sexualities
Studies of men and masculinities
Transgender studies
Women's studies (incl. girls' studies)
Gender studies not elsewhere classified
Cultural geography
This group covers human geography.
Human geography
a) Physical geography is included in Group 3709 Physical geography and environmental geoscience. b) Urban and regional planning is included in Group 3304 Urban and regional planning. c) Economics, including urban and regional economics, is included in Group 3801 Applied economics. d) Demography is included in Group 4403 Demography. e) Urban and environment policy is included in Group 4407 Policy and administration.
Development geography
Economic geography
Environmental geography
Health geography
Political geography
Population geography
Recreation, leisure and tourism geography
Rural and regional geography
Social geography
Transport geography
Urban geography
Human geography not elsewhere classified
Communications and media policy
This group covers policy and administration.
Policy and administration
a) Health care administration is included in Group 4203 Health services and systems. b) Educational administration is included in Group 3904 Specialist studies in education. c) Business Administration is included in Division 35 Commerce, management, tourism and services. d) Police administration, procedures and practice is included in Group 4402 Criminology. e) Administrative law is included in Group 4807 Public law.
Crime policy
Economic development policy
Environment policy
Gender, policy and administration
Health policy
Housing policy
Public administration
Public policy
Research, science and technology policy
Risk policy
Social policy
Tourism policy
Urban policy
Policy and administration not elsewhere classified
Australian government and politics
This group covers political science.
Political science
Citizenship
Comparative government and politics
Defence studies
Environmental politics
Gender and politics
Government and politics of Asia and the Pacific
International relations
New Zealand government and politics
Peace studies
Political theory and political philosophy
Political science not elsewhere classified
Clinical social work practice
This group covers social work.
Social work
a) Urban and regional studies are included in Group 4406 Human geography. b) Social policy is included in Group 4407 Policy and administration.
Counselling, wellbeing and community services
Social program evaluation
Social work not elsewhere classified
Applied sociology, program evaluation and social impact assessment
This group covers sociology.
Sociology
a) Criminology is included in Group 4402 Criminology. b) Social policy is included in Group 4407 Policy and administration. c) Law and society is included in Division 48 Law and legal Studies. d) Language in society (sociolinguistics) is included in Group 4704 Linguistics. e) History and philosophy of the social sciences is included in Group 5002 History and philosophy of specific fields. f) Social and political philosophy is included in Group 5003 Philosophy. g) Religion and society is included in Group 5004 Religious studies.
Environmental sociology
Rural sociology
Social change
Social theory
Sociological methodology and research methods
Sociology and social studies of science and technology
Sociology of culture
Sociology of family and relationships
Sociology of gender
Sociology of health
Sociology of inequalities
Sociology of migration, ethnicity and multiculturalism
Sociology of religion
Sociology of the life course
Urban sociology and community studies
Sociology not elsewhere classified
Studies of Asian society
This group covers human society not elsewhere classified.
Other human society
Other human society not elsewhere classified
Aboriginal and Torres Strait Islander archaeology
This group covers culture, languages, history, creative and performing arts, archaeology, built environment and design, philosophy and religion related to Aboriginal and Torres Strait Islander.
Aboriginal and Torres Strait Islander culture, language and history
This division covers research that significantly: . relates to Aboriginal and Torres Strait Islander, Māori, Pacific, and other Indigenous peoples, nations, communities, languages, places, cultures or knowledges and/or . incorporates or utilises Indigenous methodologies/ways of knowing, theories, practice and/or . is undertaken with or by these peoples, nations or communities.
INDIGENOUS STUDIES
Aboriginal and Torres Strait Islander artefacts
Aboriginal and Torres Strait Islander cultural history
Aboriginal and Torres Strait Islander culture
Aboriginal and Torres Strait Islander curatorial, archives and museum studies
Aboriginal and Torres Strait Islander ethics
Aboriginal and Torres Strait Islander history
Aboriginal and Torres Strait Islander linguistics and languages
Aboriginal and Torres Strait Islander literature, journalism and professional writing
Aboriginal and Torres Strait Islander media, film, animation and photography
Aboriginal and Torres Strait Islander music and performing arts
Aboriginal and Torres Strait Islander philosophy
Aboriginal and Torres Strait Islander religion and religious studies
Aboriginal and Torres Strait Islander repatriation
Aboriginal and Torres Strait Islander research methods
Aboriginal and Torres Strait Islander visual arts and crafts
Aboriginal and Torres Strait Islander ways of knowing, being and doing
Conservation of Aboriginal and Torres Strait Islander heritage
Aboriginal and Torres Strait Islander culture, language and history not elsewhere classified
Aboriginal and Torres Strait Islander curriculum and pedagogy
This group covers all aspects of education related to Aboriginal and Torres Strait Islander.
Aboriginal and Torres Strait Islander education
Aboriginal and Torres Strait Islander early childhood education
Aboriginal and Torres Strait Islander educational methods
Aboriginal and Torres Strait Islander technical, further, continuing and community education
Aboriginal and Torres Strait Islander higher education
Aboriginal and Torres Strait Islander language education
Aboriginal and Torres Strait Islander men’s education
Aboriginal and Torres Strait Islander primary education
Aboriginal and Torres Strait Islander secondary education
Aboriginal and Torres Strait Islander student engagement and teaching
Aboriginal and Torres Strait Islander women’s education
Cultural responsiveness and working with Aboriginal and Torres Strait Islander communities education
Embedding Aboriginal and Torres Strait Islander knowledges, histories, culture, country, perspectives and ethics in education
Aboriginal and Torres Strait Islander education not elsewhere classified
Aboriginal and Torres Strait Islander agriculture and forestry
This group covers earth sciences, environmental sciences, knowledges and management (caring for country), agricultural sciences and veterinary sciences related to Aboriginal and Torres Strait Islander.
Aboriginal and Torres Strait Islander environmental knowledges and management
Aboriginal and Torres Strait Islander earth sciences
Aboriginal and Torres Strait Islander environmental conservation
Aboriginal and Torres Strait Islander environmental knowledges
Aboriginal and Torres Strait Islander fisheries and customary fisheries
Aboriginal and Torres Strait Islander land and water management
Aboriginal and Torres Strait Islander marine environment science
Aboriginal and Torres Strait Islander environmental knowledges and management not elsewhere classified
Aboriginal and Torres Strait Islander and disability
This group covers health and wellbeing (including physical, psychological and spiritual wellbeing), health services and biomedical and clinical sciences related to Aboriginal and Torres Strait Islander.
Aboriginal and Torres Strait Islander health and wellbeing
Aboriginal and Torres Strait Islander biomedical and clinical sciences
Aboriginal and Torres Strait Islander child health and wellbeing
Aboriginal and Torres Strait Islander cultural determinants of health
Aboriginal and Torres Strait Islander diet and nutrition
Aboriginal and Torres Strait Islander epidemiology
Aboriginal and Torres Strait Islander health policy
Aboriginal and Torres Strait Islander health promotion
Aboriginal and Torres Strait Islander health services
Aboriginal and Torres Strait Islander lifecourse
Aboriginal and Torres Strait Islander medicine and treatments
Aboriginal and Torres Strait Islander men’s health and wellbeing
Aboriginal and Torres Strait Islander midwifery and paediatrics
Aboriginal and Torres Strait Islander mothers and babies health and wellbeing
Aboriginal and Torres Strait Islander nursing
Aboriginal and Torres Strait Islander psychology
Aboriginal and Torres Strait Islander public health and wellbeing
Aboriginal and Torres Strait Islander remote health
Aboriginal and Torres Strait Islander social determinants of health
Aboriginal and Torres Strait Islander social, emotional, cultural and spiritual wellbeing
Aboriginal and Torres Strait Islander sport and physical activity
Aboriginal and Torres Strait Islander theory of change models for health
Aboriginal and Torres Strait Islander youth and family social and emotional wellbeing
Aboriginal and Torres Strait Islander health and wellbeing not elsewhere classified
Aboriginal and Torres Strait Islander accounting
This group covers human society, economics, commerce, tourism, community governance and decision making, anthropology, human geography, community-based research, architecture and design, and urban planning related to Aboriginal and Torres Strait Islander.
Aboriginal and Torres Strait Islander peoples, society and community
a) Aboriginal and Torres Strait Islander health policy is included in Group 4504.
Aboriginal and Torres Strait Islander anthropology
Aboriginal and Torres Strait Islander architecture
Aboriginal and Torres Strait Islander commerce
Aboriginal and Torres Strait Islander community and regional development
Aboriginal and Torres Strait Islander community governance and decision making
Aboriginal and Torres Strait Islander community-based research
Aboriginal and Torres Strait Islander criminology
Aboriginal and Torres Strait Islander customary law
Aboriginal and Torres Strait Islander design practice and management
Aboriginal and Torres Strait Islander economics
Aboriginal and Torres Strait Islander finance
Aboriginal and Torres Strait Islander human geography and demography
Aboriginal and Torres Strait Islander legislation
Aboriginal and Torres Strait Islander management
Aboriginal and Torres Strait Islander marketing
Aboriginal and Torres Strait Islander not-for-profit social enterprises
Aboriginal and Torres Strait Islander peoples and the law
Aboriginal and Torres Strait Islander perspectives
Aboriginal and Torres Strait Islander political participation and representation
Aboriginal and Torres Strait Islander politics
Aboriginal and Torres Strait Islander social impact and program evaluation
Aboriginal and Torres Strait Islander social work and social justice
Aboriginal and Torres Strait Islander sociological studies
Aboriginal and Torres Strait Islander sociology
Aboriginal and Torres Strait Islander tourism
Aboriginal and Torres Strait Islander urban and regional planning
Aboriginal and Torres Strait Islander peoples, society and community not elsewhere classified
Aboriginal and Torres Strait Islander astronomy and cosmology
This group covers mathematical sciences, physical sciences, chemical sciences, biology, engineering, information systems and computing sciences related to Aboriginal and Torres Strait Islander.
Aboriginal and Torres Strait Islander sciences
a) Broader Indigenous data and data technologies is included in Group 4519.
Aboriginal and Torres Strait Islander biological sciences
Aboriginal and Torres Strait Islander computing technology use and design
Aboriginal and Torres Strait Islander engineering
Aboriginal and Torres Strait Islander genomics
Aboriginal and Torres Strait Islander information and knowledge management systems
Aboriginal and Torres Strait Islander innovation
Aboriginal and Torres Strait Islander knowledge management methods
Aboriginal and Torres Strait Islander mathematical, physical and chemical sciences (excl. astronomy and cosmology)
Aboriginal and Torres Strait Islander sciences not elsewhere classified
Te whāomoomo i te tuku ihotanga Māori (conservation of Māori heritage)
This group covers culture, languages, history, creative and performing arts, archaeology, built environment and design, philosophy and religion related to Māori.
Te ahurea, reo me te hītori o te Māori (Māori culture, language and history)
Te mana wahine (female status)
Te mana tāne (male status)
Te mātai whaipara Māori (Māori archaeology)
Ngā taonga Māori nō mua (Māori artefacts)
Te hītori ahurea Māori (Māori cultural history)
Te ahurea Māori (Māori culture)
Ngā mātai kaitiaki, pūranga me ngā whare tongarewa o te Māori (Māori curatorial, archives and museum studies)
Ngā matatika o te Māori (Māori ethics)
Te hītori Māori (Māori history)
Te whenua, ahurea me te tuakiri o te Māori (Māori land, culture and identity)
Te mātai i te reo Māori me te reo Māori (Māori linguistics and languages)
Te mātākōrero, te kawe kōrero me te tuhituhi ngaio o te Māori (Māori literature, journalism and professional writing)
Ngā arapāho, ngā kiriata, te hākoritanga me te hopu whakaahua o te Māori (Māori media, film, animation and photography)
Te puoro me ngā mahi a te rēhia o te Māori (Māori music and performing arts)
Te rapunga whakaaro o te Māori (Māori philosophy)
Ngā Kaupapa Māori (Māori projects)
Te whakapono me te mātai whakapono o te Māori (Māori religion and religious studies)
Te whakahoki taonga a te Māori ki te kāinga (Māori repatriation)
Ngā tikanga rangahau o te Māori (Māori research methods)
Ngā toi ataata ngā mahi ā-rehe o te Māori (Māori visual arts and crafts)
Te ahurea, reo, me te hītori o te Māori kāore anō kia whakarōpūtia i wāhi kē (Māori culture, language and history not elsewhere classified)
Ngā kōhanga reo (Māori curriculum and pedagogy)
This group covers all aspects of education related to Māori.
Mātauranga Māori (Māori education)
Te Whāriki - te mātauranga kōhungahunga Māori (Māori early childhood education)
Ngā tikanga mātauranga o te Māori (Māori educational methods)
Te mātauranga kura tuatoru Māori (Māori higher education)
Te mātauranga reo Māori (Māori language education)
Ngā kura kaupapa Māori (Māori primary education)
Te urupare me te whai wāhi Māori ki te mātauranga (Māori responsiveness and engaged education)
Te mātauranga kura tuarua Māori (Māori secondary education)
Te whai wāhi ākonga me ngā mahi whakaako o te Māori (Māori student engagement and teaching)
Tō te Māori mātauranga hangarau, mātauranga atu anō, mātauranga haere tonu, me te mātauranga hapori (Māori technical, further, continuing and community education)
Te mātauranga Māori i roto i te mātauranga (Mātauranga Māori in education)
Te mātauranga Māori kāore anō kia whakarōpūtia i wāhi kē (Māori education not elsewhere classified)
Te ahuwhenua me ngā mahi ngahere o te Māori (Māori agriculture and forestry)
This group covers earth sciences, environmental sciences and knowledges, agricultural sciences and veterinary sciences related to Māori.
Ngā mātauranga taiao o te Māori (Māori environmental knowledges)
Ngā pūtaiao-ā-nuku o te Māori (Māori earth sciences)
Te whāomoomo taiao o te Māori (Māori environmental conservation)
Te ahumoana me te ahumoana tuku iho o te Māori (Māori fisheries and customary fisheries)
Te whakahaere whenua me te wai o te Māori (Māori land and water management)
Te pūtaiao taiao moana o te Māori (Māori marine environment science)
Ngā mātauranga taiao o te Māori kāore anō kia whakarōpūtia i wāhi kē (Māori environmental knowledges not elsewhere classified)
Te whaikaha me te Māori (Māori and disability)
This group covers health and wellbeing (including physical, psychological and spiritual wellbeing), health services and biomedical and clinical sciences related to Māori.
Te hauora me te oranga o te Māori (Māori health and wellbeing)
Ngā pūtaiao koiora-hauora, haumanu hoki o te Māori (Māori biomedical and clinical sciences)
Ngā tokoingoa ahurea o te hauora o te Māori (Māori cultural determinants of health)
Te horakai me ngā kai o te Māori (Māori diet and nutrition)
Te mātai tahumaero o te Māori (Māori epidemiology)
Ngā kaupapahere hauora o te Māori (Māori health policy)
Te whakatairanga hauora o te Māori (Māori health promotion)
Ngā wāhanga ora o te Māori (Māori life course)
Ngā rongoā me ngā whakamaimoa o te Māori (Māori medicine and treatments)
Ngā kaiwhakawhānau me te mātai mate tamariki o te Māori (Māori midwifery and paediatrics)
Te hauora me te oranga ā-whaea, ā-pēpi o te Māori (Māori mothers and babies health and wellbeing)
Te mahi tapuhi o te Māori (Māori nursing)
Mātauranga hinengaro kaupapa Māori (Māori psychology)
Ngā pūnaha mātauranga hinengaro o te Māori (Māori psychology knowledge systems)
Te hauora me te oranga tūmatanui o te Māori (Māori public health and wellbeing)
Te hauora mamao o te Māori (Māori remote health)
Te oranga ā-pāpori, ā-hinengaro, ā-ahurea, ā-wairua o te Māori (Māori social, cultural, emotional and spiritual wellbeing)
Ngā tokoingoa pāpori o te hauora o te Māori (Māori social determinants of health)
Ngā hākinakina me te korikori tinana o te Māori (Māori sport and physical activity)
Te ariā o ngā tauira panoni hauora o te Māori (Māori theory of change models for health)
Ngā taiohi me ngā whānau Māori (Māori youth and family)
Te hauora me te oranga o te Māori kāore anō kia whakarōpūhia i wāhi kē (Māori health and wellbeing not elsewhere classified)
Te mahi kaute o te Māori (Māori accounting)
This group covers human society, economics, commerce, tourism, community governance and decision making, anthropology, human geography, community-based research, architecture and design, and urban planning related to Māori.
Ngā tāngata, te porihanga me ngā hapori o te Māori (Māori peoples, society and community)
a) Māori health policy is included in Group 4512.
Te mātauranga tikanga Māori (Māori anthropology)
Te hoahoanga whare o te Māori (Māori architecture)
Ngā mahi tauhokohoko o te Māori (Māori commerce)
Te whanaketanga ā-hapori, ā-rohe o te Māori (Māori community and regional development)
Te rangahau kei rō hapori o te Māori (Māori community-based research)
Te kāwana ā-hapori, whakatau take hoki o te Māori (Māori community governance and decision making)
Te mātauranga taihara Māori (Māori criminology)
Ngā tikanga Māori (Māori customary law)
Te whakaharatau me te whakahaere hoahoa o te Māori (Māori design practice and management)
Te mātauranga ōhanga o te Māori (Māori economics)
Te ahumoni Māori (Māori finance)
Te mātauranga matawhenua ā-iwi me te tatauranga ā-iwi o te Māori (Māori human geography and demography)
Te ture Whenua (Māori land law)
Te ture me te tika Māori (Māori law and justice)
Ngā ture Māori (Māori legislation)
Te whakahaere o te Māori (Māori management)
Te whakamākete o te Māori (Māori marketing)
Ngā hinonga pāpori kaupapa atawhai o te Māori (Māori not-for-profit social enterprises)
Ngā iwi Māori me te ture (Māori peoples and the law)
Ngā tirohanga Māori (Māori perspectives)
Te whai wāhi me te whakakanohi taha tōrāngapū o te Māori (Māori political participation and representation)
Ngā mahi tōrangapū Māori (Māori politics)
Ngā ture rawa Māori (Māori resource law)
Te pāpātanga pāpori me te aromātai hōtaka o te Māori (Māori social impact and program evaluation)
Ngā mahi tauwhiro me te tika pāpori o te Māori (Māori social work and social justice)
Ngā mātai tikanga ā-iwi o te Māori (Māori sociological studies)
Te mātauranga pāpori o te Māori (Māori sociology)
Te mahi tāpoi Māori (Māori tourism)
Te Tiriti o Waitangi (The Treaty of Waitangi)
Te whakamahere ā-tāone, ā-rohe o te Māori (Māori urban and regional planning)
Ngā tāngata, te porihanga me ngā hapori o te Māori kāore anō kia whakarōpūtia i wāhi kē (Māori peoples, society and community not elsewhere classified)
Te mātai arorangi me te mātai tuarangi o te Māori (Māori astronomy and cosmology)
This group covers mathematical, biological, physical, chemical, engineering, and information systems and computing sciences related to Māori.
Ngā pūtaiao Māori (Māori sciences)
Ngā pūtaiao koiora o te Māori (Māori biological sciences)
Te whakamahi me te hoahoa o te hangarau rorohiko o te Māori (Māori computing technology use and design)
Te mana motuhake o ngā raraunga Māori (Māori data sovereignty)
Te mātauranga pūkaha o te Māori (Māori engineering)
Te mātai huingaira o te Māori (Māori genomics)
Ngā pūnaha whakahaere mōhiohio me te mātauranga o te Māori (Māori information and knowledge management systems)
Te wairua auaha o te Māori (Māori innovation)
Ngā tikanga whakahaere mōhiotanga Māori (Māori knowledge management methods)
Ngā pūtaiao pāngarau, ōkiko, matū hoki - hāunga te mātai arorangi me te mātai tuarangi o te Māori (Māori mathematical, physical and chemical sciences - excl. astronomy and cosmology)
Te tukatuka reo noa o te Māori (Māori natural language processing)
Ngā pūtaiao Māori kāore anō kia whakarōpūhia i wāhi kē (Māori sciences not elsewhere classified)
Archaeology of New Guinea and Pacific Islands (excl. New Zealand)
This group covers culture, languages, history, creative and performing arts, archaeology, built environment and design, philosophy and religion related to Pacific Peoples.
Pacific Peoples culture, language and history
Conservation of Pacific Peoples heritage
Pacific Peoples artefacts
Pacific Peoples cultural history
Pacific Peoples culture
Pacific Peoples curatorial, archives and museum studies
Pacific Peoples ethics
Pacific Peoples history
Pacific Peoples land, culture and identity
Pacific Peoples linguistics and languages
Pacific Peoples literature, journalism and professional writing
Pacific Peoples media, film, animation and photography
Pacific Peoples music and performing arts
Pacific Peoples philosophy
Pacific Peoples religion and religious studies
Pacific Peoples repatriation
Pacific Peoples research methods
Pacific Peoples visual arts and crafts
Pacific Peoples ways of knowing, being and doing
Pacific Peoples culture, language and history not elsewhere classified
Cultural responsiveness and working with Pacific Peoples communities education
This group covers all aspects of education related to Pacific Peoples.
Pacific Peoples education
Embedding Pacific Peoples knowledges, histories, culture, country, perspectives and ethics in education
Pacific Peoples curriculum and pedagogy
Pacific Peoples early childhood education
Pacific Peoples educational methods
Pacific Peoples technical, further, continuing and community education
Pacific Peoples higher education
Pacific Peoples language education
Pacific Peoples men’s education
Pacific Peoples primary education
Pacific Peoples secondary education
Pacific Peoples student engagement and teaching
Pacific Peoples women’s education
Pacific Peoples education not elsewhere classified
Pacific Peoples agriculture and forestry
This group covers earth sciences, environmental sciences, knowledges and management, agricultural sciences and veterinary sciences related to Pacific Peoples.
Pacific Peoples environmental knowledges
Pacific Peoples earth sciences
Pacific Peoples environmental conservation
Pacific Peoples fisheries and customary fisheries
Pacific Peoples land and water management
Pacific Peoples marine environment science
Pacific Peoples environmental knowledges not elsewhere classified
Pacific Peoples and disability
This group covers health and wellbeing (including physical, psychological and spiritual wellbeing), health services and biomedical and clinical sciences related to Pacific Peoples.
Pacific Peoples health and wellbeing
Pacific Peoples biomedical and clinical science
Pacific Peoples cultural determinants of health
Pacific Peoples diet and nutrition
Pacific Peoples epidemiology
Pacific Peoples health policy
Pacific Peoples health promotion
Pacific Peoples life course
Pacific Peoples medicine and treatments
Pacific Peoples midwifery and paediatrics
Pacific Peoples mothers and babies health and wellbeing
Pacific Peoples nursing
Pacific Peoples psychology
Pacific Peoples public health and wellbeing
Pacific Peoples remote health
Pacific Peoples social determinants of health
Pacific Peoples social, cultural, emotional and spiritual wellbeing
Pacific Peoples sport and physical activity
Pacific Peoples theory of change models for health
Pacific Peoples youth and family
Pacific Peoples health and wellbeing not elsewhere classified
Pacific Peoples astronomy and cosmology
This group covers human society, economics, commerce, tourism, community governance and decision making, anthropology, human geography, community-based research, architecture and design, and urban planning related to Pacific Peoples.
Pacific Peoples sciences
a) Pacific Peoples health policy is included in Group 4516.
Pacific Peoples biological sciences
Pacific Peoples computing technology use and design
Pacific Peoples engineering
Pacific Peoples genomics
Pacific Peoples information and knowledge management systems
Pacific Peoples innovation
Pacific Peoples knowledge management methods
Pacific Peoples mathematical, physical and chemical sciences (excl. astronomy and cosmology)
Pacific Peoples sciences not elsewhere classified
Pacific Peoples and the law
This group covers mathematical, biological, physical, chemical, engineering, and information systems and computing sciences related to Pacific Peoples.
Pacific Peoples society and community
Pacific Peoples anthropology
Pacific Peoples architecture
Pacific Peoples commerce
Pacific Peoples community and regional development
Pacific Peoples community governance and decision making
Pacific Peoples community-based research
Pacific Peoples criminology
Pacific Peoples customary law
Pacific Peoples design practice and management
Pacific Peoples economics
Pacific Peoples finance
Pacific Peoples human geography and demography
Pacific Peoples legislation
Pacific Peoples management
Pacific Peoples marketing
Pacific Peoples not-for-profit social enterprises
Pacific Peoples perspectives
Pacific Peoples political participation and representation
Pacific Peoples politics
Pacific Peoples social impact and program evaluation
Pacific Peoples social work and social justice
Pacific Peoples sociological studies
Pacific Peoples sociology
Pacific Peoples tourism
Pacific Peoples urban and regional planning
Pacific Peoples, society and community not elsewhere classified
Global Indigenous studies culture, language and history
This group covers Indigenous data, data technologies, Indigenous methodologies and global Indigenous studies.
Other Indigenous data, methodologies and global Indigenous studies
a) Research methods of Aboriginal and Torres Strait Islander are included in Group 4501, Māori in Group 4511 and Pacific Peoples in Group 4513. d) Māori data sovereignty is in 4509.
Global Indigenous studies environmental knowledges and management
Global Indigenous studies health and wellbeing
Global Indigenous studies peoples, society and community
Global Indigenous studies sciences
Indigenous data and data technologies
Indigenous methodologies
Other Indigenous data, methodologies and global Indigenous studies not elsewhere classified
Other Indigenous studies not elsewhere classified
This group covers other Indigenous studies not elsewhere classified.
Other Indigenous studies
Applications in arts and humanities
This group covers computing techniques specific to particular application domains and also topics which combine techniques from different sub-disciplines of computing.
Applied computing
a) Hardware oriented applications in Health or life sciences are included in Group 4003 Biomedical engineering. b) Applications where primary focus is the field of application, rather than the application and evaluation of computing technology are included in the appropriate application codes.
This division covers information and computing sciences.
INFORMATION AND COMPUTING SCIENCES
a) Indigenous information and computing sciences are included in Division 45 Indigenous studies.
Applications in health
Applications in life sciences
Applications in physical sciences
Applications in social sciences and education
Spatial data and applications
Applied computing not elsewhere classified
Artificial life and complex adaptive systems
This group covers artificial intelligence other than Machine learning and computer vision.
Artificial intelligence
a) Machine learning is included in Group 4611 Machine learning. b) Vision and imaging are included in Group 4603 Computer vision and multimedia computation. c) Robotics hardware is included in Group 4007 Control engineering, mechatronics and robotics. d) Signal processing is included in Group 4006 Communications engineering. e) Fairness, accountability, transparency, trust and ethics of AI systems is included in Group 4608 Human-centred computing.
Autonomous agents and multiagent systems
Evolutionary computation
Fuzzy computation
Intelligent robotics
Knowledge representation and reasoning
Modelling and simulation
Natural language processing
Planning and decision making
Satisfiability and optimisation
Speech production
Speech recognition
Artificial intelligence not elsewhere classified
Active sensing
This group covers computer vision, and methods, systems and technologies for dealing with images, video data, audio and combinations of these.
Computer vision and multimedia computation
a) Sound and music processing is included in Group 4607 Graphics, augmented reality and games. b) Signal processing is included in Group 4006 Communications engineering.
Audio processing
Computational imaging
Computer vision
Image and video coding
Image processing
Multimodal analysis and synthesis
Pattern recognition
Video processing
Computer vision and multimedia computation not elsewhere classified
Cryptography
This group covers the technology that supports cybersecurity and privacy.
Cybersecurity and privacy
a) Legal aspects of cybersecurity and privacy are included in Group 4604 Cybersecurity and privacy. b) Cybercrime is included in Group 4402 Criminology.
Data and information privacy
Data security and protection
Digital forensics
Hardware security
Software and application security
System and network security
Cybersecurity and privacy not elsewhere classified
Data engineering and data science
This group covers methods and computing systems for working with data sets.
Data management and data science
a) Mathematical transformations and techniques used in the querying of audio, images, or video are included in Group 4603 Computer vision and multimedia computation. b) The management of or administration strategies for database systems are included in Group 4609 Information systems. c) Cryptography, privacy, or security aspects of database systems are included in Group 4604 Cybersecurity and privacy. d) The graphical visualization or visual presentations of data is included in Group 4608 Human-centred computing. e) Machine learning techniques for analysis of large data sets is included in Group 4611 Machine learning.
Data mining and knowledge discovery
Data models, storage and indexing
Data quality
Database systems
Graph, social and multimedia data
Information extraction and fusion
Information retrieval and web search
Query processing and optimisation
Recommender systems
Stream and sensor data
Data management and data science not elsewhere classified
Cloud computing
This group covers methods and systems for supporting the efficient execution of application software, including those which use multiple computation units.
Distributed computing and systems software
a) The engineering processes that produce these software components are included in Group 4612 Software engineering.
Concurrent/parallel systems and technologies
Cyberphysical systems and internet of things
Dependable systems
Distributed systems and algorithms
Energy-efficient computing
High performance computing
Mobile computing
Networking and communications
Operating systems
Performance evaluation
Service oriented computing
Distributed computing and systems software not elsewhere classified
Computer aided design
This group covers algorithms, methods and systems that generate convincing synthetic imagery and sound, amongst other things to allow user interaction in virtual, augmented and simulated environments (including, but not limited to games, online virtual worlds, real-time military, industrial or medical simulators).
Graphics, augmented reality and games
a) CAD/CAM systems for manufacturing are included in Group 4014 Manufacturing engineering. b) Storage and querying of graphics data is included in Group 4605 Data management and data science. c) Human interaction focus in media or games is included in Group 4608 Human-centred computing.
Computer graphics
Entertainment and gaming
Interactive narrative
Procedural content generation
Serious games
Sound and music computing
Virtual and mixed reality
Graphics, augmented reality and games not elsewhere classified
Accessible computing
This group covers methods and technologies which relate to how people and computer systems function together.
Human-centred computing
a) Use of computing for education other than in the computer sciences and information systems disciplines is included in Division 39 Education. b) Use of computing for information systems education is included in Group 4609 Information systems. c) Intelligent robotics not focussing primarily on the social aspects of interactions between human and robot is included in Group 4602 Artificial intelligence. d) Hardware aspects of social robotics is included in Group 4007 Control engineering, mechatronics and robotics. e) Design of interfaces for, and experience with, business information systems is included in Group 4906 Information systems.
Affective computing
Collaborative and social computing
Computing education
Fairness, accountability, transparency, trust and ethics of computer systems
Human-computer interaction
Information visualisation
Mixed initiative and human-in-the-loop
Pervasive computing
Social robotics
Human-centred computing not elsewhere classified
Business process management
This group covers systems that manage information for organisational purposes.
Information systems
a) Organisation of information and knowledge resources is included in Group 4610 Library and information studies. b) Information retrieval and web search/querying are included in Group 4605 Data management and data science. b) Geospatial information systems are included in Group 4013 Geomatic engineering. c) Development of computer hardware is included in Group 4009 Electronics, sensors and digital hardware. d) Health information systems, including surveillance, where the focus is not on computer science are included in Group 4203 Health services and systems. e) Health information systems with a focus on computer sciences are included in Group 4601 Applied computing. f) Business information systems are included in Group 3503 Business systems in context. g) Data science for earth science and geospatial data visualisation is included in Group 3704 Geoinformatics and geospatial information systems and geospatial data modelling is included in 4013 Geomatic engineering.
Decision support and group support systems
Information modelling, management and ontologies
Information security management
Information systems development methodologies and practice
Information systems education
Information systems for sustainable development and the public good
Information systems organisation and management
Information systems philosophy, research methods and theory
Information systems user experience design and development
Inter-organisational, extra-organisational and global information systems
Knowledge and information management
Information systems not elsewhere classified
Digital curation and preservation
This group covers library and information studies.
Library and information studies
a) Cheminformatics is included in Group 3404 Medicinal and biomolecular chemistry. b) Bioinformatics is included in Group 4601 Applied computing and Group 3102 Bioinformatics and computational biology. c) Information systems organisation and management is included in Group 4609 Information systems. d) Archival, repository and related studies is included in Group 4302 Heritage, archive and museum studies. e) Information Retrieval and Web Search is included in Group 4605 Data management and data science.
Human information behaviour
Human information interaction and retrieval
Information governance, policy and ethics
Informetrics
Library studies
Open access
Organisation of information and knowledge resources
Recordkeeping informatics
Social and community informatics
Library and information studies not elsewhere classified
Adversarial machine learning
This group covers machine learning and the techniques used by machine learning.
Machine learning
a) Machine learning that is specific to a particular application domain is included in the corresponding code for that domain. b) Systems software to support efficient execution of machine learning is included in Group 4606 Distributed computing and systems software.
Context learning
Deep learning
Neural networks
Reinforcement learning
Semi- and unsupervised learning
Machine learning not elsewhere classified
Automated software engineering
This group covers software engineering and technologies and processes associated with the development of computer software.
Software engineering
a) Descriptions of software applications that are not focussed on the structure or development of the software are included in the appropriate codes for the application domain or type of software.
Empirical software engineering
Formal methods for software
Programming languages
Requirements engineering
Software architecture
Software quality, processes and metrics
Software testing, verification and validation
Software engineering not elsewhere classified
Coding, information theory and compression
This group covers the theory of computation.
Theory of computation
a) Logic not relating to computation is included in Group 4904 Pure mathematics. b) Engineering of quantum computing systems is included in Group 4009 Electronics, sensors and digital hardware. c) Physics of quantum computing is included in Group 5108 Quantum physics. d) Numerical computation and mathematical software that is not in a particular domain and not relating to computer algorithms is included in Division 49 Mathematical Sciences. e) Numerical computation relating to a particular domain is covered in that domain (e.g. computational chemistry is included in Group 3407 Theoretical and computational chemistry).
Computational complexity and computability
Computational logic and formal languages
Concurrency theory
Data structures and algorithms
Numerical computation and mathematical software
Quantum computation
Theory of computation not elsewhere classified
Other information and computing sciences not elsewhere classified
This group covers other information and computing sciences not elsewhere classified.
Other information and computing sciences
Communication studies
This group covers communication and media studies. It includes the social impacts of marketing and advertising.
Communication and media studies
a) Marketing and advertising, other than their social or cultural impacts, are included in Group 3506 Marketing. b) Film, television and digital media are included in Group 3605 Screen and digital media. c) Professional writing and journalism practice is included in Group 3602 Creative and professional writing. d) Communications technologies are included in Group 4006 Communications engineering.
This division covers language, communication and culture
LANGUAGE, COMMUNICATION AND CULTURE
a) Indigenous language, communication and culture are included in Division 45 Indigenous studies.
Communication technology and digital media studies
Environmental communication
International and development communication
Journalism studies
Media industry studies
Media studies
Organisational, interpersonal and intercultural communication
Communication and media studies not elsewhere classified
Arts and cultural policy
This group covers cultural studies.
Cultural studies
a) Marketing and advertising, other than their social or cultural impacts, are included in Group 3506 Marketing. b) Gender studies are included in Group 4405 Gender studies. c) Visual cultures is included in Group 3601 Art history, theory and criticism and print culture is included in Group 4705 Literary studies. d) Intercultural communication and the social impacts of marketing and advertising are included in Group 4701 Communication and media studies. e) Language in culture is included in Group 4704 Linguistics. f) Cultural conservation is included in Group 4302 Heritage, archive and museum studies. g) Indigenous cultural studies are included in Division 45 Indigenous studies.
Asian cultural studies
Consumption and everyday life
Cultural and creative industries
Cultural studies of agriculture, food and wine
Cultural studies of nation and region
Cultural theory
Culture, representation and identity
Environment and culture
Globalisation and culture
Migrant cultural studies
Multicultural, intercultural and cross-cultural studies
Postcolonial studies
Screen and media culture
Cultural studies not elsewhere classified
African languages
This group covers language studies. It includes comparative language studies and translation and interpretation studies.
Language studies
a) Writing is included in Division 36 Creative arts and writing. b) Linguistics is included in Group 4704 Linguistics. c) Literary studies are included in Group 4705 Literary studies. d) Philosophy of language is included in Group 5003 Philosophy. e) Indigenous linguistics and languages is included in Division 45 Indigenous studies.
Central and Eastern European languages (incl. Russian)
Chinese languages
Comparative language studies
Early English languages
English as a second language
English language
French language
German language
Iberian languages
Indian languages
Indonesian languages
Italian language
Japanese language
Korean language
Latin and classical Greek languages
Middle Eastern languages
Other Asian languages (excl. South-East Asian)
Other European languages
South-East Asian languages (excl. Indonesian)
Translation and interpretation studies
Language studies not elsewhere classified
Applied linguistics and educational linguistics
This group covers linguistics.
Linguistics
a) Linguistic anthropology is included in Group 4401 Anthropology. b) Psycholinguistics (incl. speech production and comprehension) are included in Group 5204 Cognitive and computational psychology. c) Language studies are included in Group 4703 Language studies. d) Philosophy of language is included in Group 5003 Philosophy. e) Indigenous linguistics and languages are included in Division 45 Indigenous studies.
Child language acquisition
Computational linguistics
Corpus linguistics
Discourse and pragmatics
Historical, comparative and typological linguistics
Language documentation and description
Lexicography and semantics
Linguistic structures (incl. phonology, morphology and syntax)
Phonetics and speech science
Sociolinguistics
Linguistics not elsewhere classified
African literature
This group covers literature and literary studies.
Literary studies
a) Writing is included in Division 36 Creative arts and writing. b) Language studies are included in Group 4703 Language studies. c) Biography is included in Group 4303 Historical studies.
Australian literature (excl. Aboriginal and Torres Strait Islander literature)
Book history
British and Irish literature
Central and Eastern European literature (incl. Russian)
Children's literature
Comparative and transnational literature
Digital literature
Ecocriticism
Indian literature
Indonesian literature
Korean literature
Latin and classical Greek literature
Literary theory
Literature in Chinese
Literature in French
Literature in German
Literature in Italian
Literature in Japanese
Literature in Spanish and Portuguese
Middle Eastern literature
New Zealand literature (excl. Māori literature)
North American literature
Other Asian literature (excl. South-East Asian)
Other European literature
Other literatures in English
Popular and genre literature
Print culture
South-East Asian literature (excl. Indonesian)
Stylistics and textual analysis
Young adult literature
Literary studies not elsewhere classified
Other language, communication and culture not elsewhere classified
This group covers language, communication and culture not elsewhere classified.
Other language, communication and culture
Banking, finance and securities law
This group covers commercial law.
Commercial law
This division covers law and legal studies.
LAW AND LEGAL STUDIES
a) Criminology, including policing and correctional theory, is included in Group 4402 Criminology. b) Legal ethics and human rights and justice issues are included in Group 5001 Applied ethics. c) History and philosophy of law and justice is included in Group 5002 History and philosophy of specific fields. d) Indigenous law and legal studies are included in Division 45 Indigenous studies.
Corporations and associations law
Labour law
Not-for-profit law
Taxation law
Commercial law not elsewhere classified
Animal law
This group covers environmental and resources law.
Environmental and resources law
Climate change law
Environmental law
Mining, energy and natural resources law
Environmental and resources law not elsewhere classified
Asian and Pacific law
This group covers international and comparative law.
International and comparative law
Comparative law
Conflict of laws (incl. private international law)
European Union law
International arbitration
International criminal law
International humanitarian and human rights law
International trade and investment law
Ocean law and governance
Public international law
Space, maritime and aviation law
International and comparative law not elsewhere classified
Criminal law
This group covers law.
Law in context
Family law
Law and humanities
Law and religion
Law and society and socio-legal research
Law reform
Law, gender and sexuality (incl. feminist legal scholarship)
Law, science and technology
Legal education
Legal theory, jurisprudence and legal interpretation
Media and communication law
Medical and health law
Race, ethnicity and law
Sports law
Law in context not elsewhere classified
Access to justice
This group covers legal systems.
Legal systems
Civil procedure
Criminal procedure
Legal institutions (incl. courts and justice systems)
Legal practice, lawyering and the legal profession
Litigation, adjudication and dispute resolution
Youth justice
Legal systems not elsewhere classified
Contract law
This group covers private law and civil obligations.
Private law and civil obligations
Equity and trusts law
Intellectual property law
Property law (excl. intellectual property law)
Tort law
Private law and civil obligations not elsewhere classified
Administrative law
This group covers public law.
Public law
a) International humanitarian and human rights law is included in Group 4803 International and comparative law.
Constitutional law
Domestic human rights law
Migration, asylum and refugee law
Military law and justice
Privacy and data rights
Welfare, insurance, disability and social security law
Public law not elsewhere classified
Other law and legal studies not elsewhere classified
This group covers law and legal studies not elsewhere classified.
Other law and legal studies
Approximation theory and asymptotic methods
This group covers applied mathematics.
Applied mathematics
a) Mathematical aspects of physics are included in Group 4902 Mathematical physics. b) Bioinformatics is included in Group 3101 Biochemistry and cell biology. c) Geodesy is included in Group 3706 Geophysics. d) Applications of control theory to engineering are included in Groups 4007 Control engineering, mechatronics and robotics and 4017 Mechanical engineering. e) Mathematics applied in economics is included in Division 38 Economics. f) Complex systems mathematics applied in engineering is included in Division 40 Engineering.
This division covers mathematics, statistics, and mathematical aspects of the physical sciences.
MATHEMATICAL SCIENCES
a) Indigenous mathematical sciences are included in Division 45 Indigenous studies.
Biological mathematics
Calculus of variations, mathematical aspects of systems theory and control theory
Complex systems
Dynamical systems in applications
Financial mathematics
Mathematical methods and special functions
Operations research
Theoretical and applied mechanics
Applied mathematics not elsewhere classified
Algebraic structures in mathematical physics
This group covers the mathematical aspects of physics.
Mathematical physics
a) Combinatorics other than physical combinatorics is included in Group 4904 Pure mathematics. b) Development of statistical techniques is included in Group 4905 Statistics. c) Statistical physics is included in Group 5103 Classical physics. d) Statistical mechanics associated with chemical processes is included in 3407 Theoretical and computational chemistry.
Integrable systems (classical and quantum)
Mathematical aspects of classical mechanics, quantum mechanics and quantum information theory
Mathematical aspects of general relativity
Mathematical aspects of quantum and conformal field theory, quantum gravity and string theory
Statistical mechanics, physical combinatorics and mathematical aspects of condensed matter
Mathematical physics not elsewhere classified
Experimental mathematics
This group covers numerical and computational mathematics.
Numerical and computational mathematics
a) Computational analysis and mathematical software are included in Group 4613 Theory of computation.
Numerical analysis
Numerical solution of differential and integral equations
Optimisation
Numerical and computational mathematics not elsewhere classified
Algebra and number theory
This group covers pure mathematics.
Pure mathematics
a) Physical combinatorics is included in Group 4902 Mathematical physics. b) Mathematics associated with computer sciences is included in Division 46 Information and computing sciences.
Algebraic and differential geometry
Category theory, k theory, homological algebra
Combinatorics and discrete mathematics (excl. physical combinatorics)
Group theory and generalisations
Lie groups, harmonic and Fourier analysis
Mathematical logic, set theory, lattices and universal algebra
Operator algebras and functional analysis
Ordinary differential equations, difference equations and dynamical systems
Partial differential equations
Real and complex functions (incl. several variables)
Topology
Pure mathematics not elsewhere classified
Applied statistics
This group covers statistics. It includes the development of statistical techniques.
Statistics
a) Statistical mechanics is included in Group 4902 Mathematical physics. b) Statistical physics is included in Group 5103 Classical physics. c) Bioinformatics is included in Group 3101 Biochemistry and cell biology. d) Applications of statistical techniques are included in the appropriate division. e) Econometrics, economic time series analysis and fields are included in Division 38 Economics. f) Criminology is included in Group 4402 Criminology. g) Forensic intelligence and forensic science and management is covered in Group 3503 Business systems in context.
Biostatistics
Computational statistics
Forensic evaluation, inference and statistics
Large and complex data theory
Probability theory
Spatial statistics
Statistical data science
Statistical theory
Stochastic analysis and modelling
Time series and spatial modelling
Statistics not elsewhere classified
Other mathematical sciences not elsewhere classified
This group covers any mathematical sciences not elsewhere classified.
Other mathematical sciences
Bioethics
This group covers applied ethics. It included human rights and justice issues.
Applied ethics
a) Humane treatment of animals in agriculture, domestic or sporting environments is included in Group 3003 Animal production. b) Human rights law is included in Group 4807 Public law. c) Ethical theory and environmental philosophy, including environmental ethics, is included in Group 5003 Philosophy.
This division covers philosophy and religious studies.
PHILOSOPHY AND RELIGIOUS STUDIES
a) Indigenous philosophy and religious studies are included in Division 45 Indigenous studies.
Business ethics
Ethical use of new technology
Human rights and justice issues (excl. law)
Legal ethics
Medical ethics
Professional ethics
Applied ethics not elsewhere classified
History and philosophy of engineering and technology
This group covers the history and philosophy of specific concepts or fields of study which defy geographical classification.
History and philosophy of specific fields
a) History of architecture is included in Group 3301 Architecture. b) History of design is included in Group 3303 Design. c) History of the built environment is included in Group 3304 Urban and regional planning. d) Sociology and social studies of science and technology is included in Group 4410 Sociology. e) Art history is included in Group 3601 Art history, theory and criticism. f) Historical linguistics is included in Group 4704 Linguistics. g) History of peoples, nations or geographic areas is included in Group 4303 Historical studies.
History and philosophy of law and justice
History and philosophy of medicine
History and philosophy of science
History and philosophy of the humanities
History and philosophy of the social sciences
History of ideas
History of philosophy
History and philosophy of specific fields not elsewhere classified
Aesthetics
This group covers philosophy.
Philosophy
a) Mathematical logic is included in Group 4904 Pure mathematics. b) Political philosophy is included in Group 4408 Political science. c) Applied ethics is included in Group 5001 Applied ethics. d) History of philosophy and the history and philosophy of specific fields of study are included in Group 5002 History and philosophy of specific fields.
Critical theory
Decision theory
Environmental philosophy
Epistemology
Ethical theory
Hermeneutics
Logic
Metaphysics
Phenomenology
Philosophical psychology (incl. moral psychology and philosophy of action)
Philosophy of cognition
Philosophy of gender
Philosophy of language
Philosophy of mind (excl. cognition)
Philosophy of religion
Philosophy of science (excl. history and philosophy of specific fields)
Philosophy of specific cultures (incl. comparative philosophy)
Poststructuralism
Psychoanalytic philosophy
Social and political philosophy
Philosophy not elsewhere classified
Christian studies
This group covers the study of religion. It includes comparative religious studies.
Religious studies
a) Language studies are included in Group 4703 Language studies. b) Philosophy of religion is included in Group 5003 Philosophy.
Comparative religious studies
Islamic studies
Jewish studies
Religion, society and culture
Studies in eastern religious traditions
Studies in religious traditions (excl. Eastern, Jewish, Christian and Islamic traditions)
Religious studies not elsewhere classified
Theology
This group covers theology.
Theology not elsewhere classified
Other philosophy and religious studies not elsewhere classified
This group covers philosophy and religious studies not elsewhere classified.
Other philosophy and religious studies
Astrobiology
This group covers astronomical sciences, including cosmology.
Astronomical sciences
a) Field theory and string theory are included in Group 5106 Nuclear and plasma physics. b) Tropospheric and stratospheric physics are included in Group 3701 Atmospheric sciences. c) Planetary geology is included in Group 3705 Geology. d) Satellite and space vehicle design and testing is included in Group 4001 Aerospace engineering. e) Photogrammetry and remote sensing are included in Group 4013 Geomatic engineering. f) Communications technologies using satellites are included in Group 4006 Communications engineering.
This division covers the physical sciences. It includes biological physics (other than human biophysics), medical physics and synchrotron and accelerator technologies.
PHYSICAL SCIENCES
a) Indigenous physical sciences are included in Division 45 Indigenous studies.
Astronomical instrumentation
Cosmology and extragalactic astronomy
Galactic astronomy
General relativity and gravitational waves
High energy astrophysics and galactic cosmic rays
Planetary science (excl. solar system and planetary geology)
Solar physics
Stellar astronomy and planetary systems
Astronomical sciences not elsewhere classified
Atomic and molecular physics
This group covers atomic, molecular and optical physics.
Atomic, molecular and optical physics
a) Atom optics is included in Group 5108 Quantum physics.
Lasers and quantum electronics
Nonlinear optics and spectroscopy
Photonics, optoelectronics and optical communications
Terahertz physics
Atomic, molecular and optical physics not elsewhere classified
Acoustics and acoustical devices; waves
This group covers classical physics.
Classical physics
a) Mathematical aspects of classical physics are included in Group 4902 Mathematical physics. b) Classical and physical optics is included in Group 5103 Classical physics.
Classical and physical optics
Electrostatics and electrodynamics
Thermodynamics and statistical physics
Classical physics not elsewhere classified
Condensed matter characterisation technique development
This group covers condensed matter physics.
Condensed matter physics
a) Other material sciences are included in Groups 3402 Inorganic chemistry, 3403 Macromolecular and materials chemistry, 4003 Biomedical engineering, 4016 Materials engineering and 4019 Resources engineering and extractive metallurgy. b) Nanotechnology is included in Group 4103 Environmental biotechnology, 3106 Industrial biotechnology, 4018 Nanotechnology and 3206 Medical biotechnology.
Condensed matter imaging
Condensed matter modelling and density functional theory
Electronic and magnetic properties of condensed matter; superconductivity
Soft condensed matter
Structural properties of condensed matter
Surface properties of condensed matter
Condensed matter physics not elsewhere classified
Biological physics
This group covers medical and biological physics.
Medical and biological physics
a) Human biophysics is included in Group 3208 Medical physiology.
Medical physics
Medical and biological physics not elsewhere classified
Nuclear physics
This group covers nuclear and plasma physics.
Nuclear and plasma physics
Plasma physics; fusion plasmas; electrical discharges
Nuclear and plasma physics not elsewhere classified
Astroparticle physics and particle cosmology
This group covers particle and high energy physics.
Particle and high energy physics
a) Atom optics is included in Group 5108 Quantum physics. b) Nuclear and plasma physics is included in Group 5106 Nuclear and plasma physics.
Field theory and string theory
Particle physics
Particle and high energy physics not elsewhere classified
Degenerate quantum gases and atom optics
This group covers quantum physics.
Quantum physics
a) Mathematical aspects of quantum physics are included in Group 4902 Mathematical physics. b) Communications technologies are included in Group 4006 Communications engineering.
Foundations of quantum mechanics
Quantum information, computation and communication
Quantum optics and quantum optomechanics
Quantum technologies
Quantum physics not elsewhere classified
Astrodynamics and space situational awareness
This group covers space sciences.
Space sciences
a) Astronomical sciences, including cosmology are included in 5101 Astronomical sciences. b) Field theory and string theory are included in Group 5106 Nuclear and plasma physics. c) Tropospheric and stratospheric physics are included in Group 3701 Atmospheric sciences. d) Planetary geology is included in Group 3705 Geology. e) Satellite and space vehicle design and testing is included in Group 4001 Aerospace engineering. f) Remote sensing is included in Group 4013 Geomatic engineering. g) Communications technologies using satellites are included in Group 4006 Communications engineering.
Heliophysics and space weather
Mesospheric, thermospheric, ionospheric and magnetospheric physics
Solar system energetic particles
Solar system planetary science (excl. planetary geology)
Space instrumentation
Space sciences not elsewhere classified
Accelerators
This group covers synchrotrons, accelerators, instruments and techniques.
Synchrotrons and accelerators
Instruments and techniques
Synchrotrons
Synchrotrons and accelerators not elsewhere classified
Complex physical systems
This group covers any physical sciences not elsewhere classified. It includes complex physical systems.
Other physical sciences
Other physical sciences not elsewhere classified
Child and adolescent development
This group covers the development and application of psychological methods and psychological research findings to solve practical problems of human and animal behaviour and the manner in which those psychological processes change through the life span.
Applied and developmental psychology
This division covers psychology and cognitive sciences.
PSYCHOLOGY
a) Indigenous psychology is included in Division 45 Indigenous studies.
Educational psychology
Forensic psychology
Industrial and organisational psychology (incl. human factors)
Psychological methodology, design and analysis
Psychology of ageing
Sport and exercise psychology
Testing, assessment and psychometrics
Applied and developmental psychology not elsewhere classified
Behavioural genetics
This group covers biological psychology research into the neural and physiological mechanisms that underpin psychological processes.
Biological psychology
Behavioural neuroscience
Cognitive neuroscience
Evolutionary psychological studies
Psychopharmacology
Psychophysiology
Social and affective neuroscience
Biological psychology not elsewhere classified
Clinical neuropsychology
This group covers clinical and health psychology. It includes the detection, aetiology, treatment and prevention of mental health problems and psychological and behavioural processes in health and illness.
Clinical and health psychology
a) Psychiatry where chemical interventions are employed to modify behaviour is included in 3202 Clinical sciences. b) Research investigating mental health services is included in the Group 4203 Health services and systems.
Clinical psychology
Counselling psychology
Health psychology
Clinical and health psychology not elsewhere classified
Cognition
This group covers cognitive and computational psychology. It includes the experimental study, computational and mathematical modelling of cognitive processes.
Cognitive and computational psychology
a) Computational modelling of expert systems that are not intended to study or mimic human or animal behaviour are included in the Group 4602 Artificial intelligence.
Decision making
Learning, motivation and emotion
Memory and attention
Psycholinguistics (incl. speech production and comprehension)
Sensory processes, perception and performance
Cognitive and computational psychology not elsewhere classified
Community psychology
This group covers social and personality psychology. The study of the manner in which social groups influence the motivations, attitudes, personality and behaviour of the individual and the importance of the ways that individuals differ on those factors.
Social and personality psychology
a) Neuroscientific underpinnings of interpersonal, individual-group and intergroup interactions are included in the Group 5202 Biological psychology.
Gender psychology
Personality and individual differences
Psychology of religion
Social psychology
Social and personality psychology not elsewhere classified
Other psychology not elsewhere classified
This group covers psychology not elsewhere classified.
Other psychology
EDES Fauna Aerial Survey Protocol Shapes Graph
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/69e33304-f95e-41d3-b8bc-6307d3d774bf>`. `<https://linked.data.gov.au/def/nrm/69e33304-f95e-41d3-b8bc-6307d3d774bf>` is the IRI for "Fauna Aerial Surveys".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/69e33304-f95e-41d3-b8bc-6307d3d774bf`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/99d12a9f-71db-506b-bb8f-1eb180c9df9d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
The value in `sosa:hasResult` _MUST_ be a value in `sh:in`, which is the line transect - distance sampling categories controlled vocabulary.
The value of `rdf:value` _MUST_ exist in the line transect - distance sampling categories controlled vocabulary.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/99d12a9f-71db-506b-bb8f-1eb180c9df9d> ; sosa:hasResult ?this . }
PREFIX skos: <http://www.w3.org/2004/02/skos/core#> select ?values { values ?categoricalUUID {'c67f241f-6f45-5e87-88ad-d679eb0bf461'} ?s skos:member ?values . filter (STRENDS(str(?s), ?categoricalUUID)) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/99d12a9f-71db-506b-bb8f-1eb180c9df9d> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/99d12a9f-71db-506b-bb8f-1eb180c9df9d>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/99d12a9f-71db-506b-bb8f-1eb180c9df9d>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of `tern:vocabulary` in `sosa:hasResult` _MUST_ have the value `<https://linked.data.gov.au/def/nrm/c67f241f-6f45-5e87-88ad-d679eb0bf461>`. `<https://linked.data.gov.au/def/nrm/c67f241f-6f45-5e87-88ad-d679eb0bf461>` is the IRI for "line transect - distance sampling categories".
The value of `tern:vocabulary` _MUST_ match the pattern `c67f241f-6f45-5e87-88ad-d679eb0bf461$`.
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/69e33304-f95e-41d3-b8bc-6307d3d774bf>`. `<https://linked.data.gov.au/def/nrm/69e33304-f95e-41d3-b8bc-6307d3d774bf>` is the IRI for "Fauna aerial survey".
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3db9d094-ebf1-588e-8166-63b999710ac1>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3db9d094-ebf1-588e-8166-63b999710ac1> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3db9d094-ebf1-588e-8166-63b999710ac1>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/3db9d094-ebf1-588e-8166-63b999710ac1> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/3db9d094-ebf1-588e-8166-63b999710ac1>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
This property is defined by the Time Ontology in OWL and is a general purpose property for indicating that something has a temporality. It should be used in this model to indicate the timespan of a Lifecycle Stage
This model was made for the Queensland Department of Resources, Spatial Information unit in 2023 to assist with the lifecylcing of components within multiple ontologies.
This model allows for the representation of lifecycle stages for any Resource. The specific stages are expected to be taken from vocabularies relevant to the Resource.
Use this property to indicate the specialised type of a Lifeycle Stage which is likely selected from a controlled vocabulary
Indicates a Lifecycle Stage of a Resource
# showing lifecycle stages for a Geographical Name ex:name-1 a gn:GeographicalName ; :hasLifeCycleStage [ # this Stage has ceased time:hasTime [ time:hasBeginning [ time:inXSDDate "1982-02-10"^^xsd:date ] ; time:hasEnd [ time:inXSDDate "1982-05-11"^^xsd:date ] ; ] ; sdo:additionalType <http://example.com/stage/proposed> ; ] , [ # this Stage is still in effect - no hasEnd given time:hasTime [ time:hasBeginning [ time:inXSDDate "1982-05-11"^^xsd:date ] ; ] ; sdo:additionalType <http://example.com/stage/gazetted> ; ] , .
A distinct part of a resource's lifecycle
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/1a6953e4-a830-41f8-9cfd-11ead4dd6bc2>`. `<https://linked.data.gov.au/def/nrm/1a6953e4-a830-41f8-9cfd-11ead4dd6bc2>` is the IRI for "Camera Trap Deployment protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/1a6953e4-a830-41f8-9cfd-11ead4dd6bc2`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/4cba50f1-ad45-41d4-924c-c7efb9801248>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:hasFeatureOfInterest ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select $this { $this a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/4cba50f1-ad45-41d4-924c-c7efb9801248> ; sosa:hasSimpleResult ?simple ; sosa:hasResult ?result . ?result rdf:value ?value . filter (?simple != ?value) }
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/a2afccd5-766e-44bc-98c1-f27aae26727f>`. `<https://linked.data.gov.au/def/nrm/a2afccd5-766e-44bc-98c1-f27aae26727f>` is the IRI for "Camera Trap Re-equipping protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/a2afccd5-766e-44bc-98c1-f27aae26727f`.
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/4cba50f1-ad45-41d4-924c-c7efb9801248>} ?observation a tern:Observation ; sosa:observedProperty ?property_uri ; sosa:usedProcedure ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { ?observation a tern:Observation ; sosa:observedProperty <https://linked.data.gov.au/def/nrm/4cba50f1-ad45-41d4-924c-c7efb9801248> ; sosa:hasResult ?this . }
PREFIX tern: <https://w3id.org/tern/ontologies/tern/> PREFIX unit: <http://qudt.org/vocab/unit/> PREFIX sosa: <http://www.w3.org/ns/sosa/> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> select ?this { values ?property_uri {<https://linked.data.gov.au/def/nrm/4cba50f1-ad45-41d4-924c-c7efb9801248>} ?this a tern:Observation ; sosa:observedProperty ?property_uri . }
IRI of method in procedure _MUST_ have the value `<https://linked.data.gov.au/def/nrm/cb497bbc-75dc-450d-b020-5bc3c54d5586>`. `<https://linked.data.gov.au/def/nrm/cb497bbc-75dc-450d-b020-5bc3c54d5586>` is the IRI for "Camera Trap Retrieval protocol".
The procedure's `tern:hasMethod` _MUST_ have the value `https://linked.data.gov.au/def/nrm/cb497bbc-75dc-450d-b020-5bc3c54d5586`.