diff --git a/FND/Accounting/CurrencyAmount.rdf b/FND/Accounting/CurrencyAmount.rdf index 661b2b63f..cb47c4ec7 100644 --- a/FND/Accounting/CurrencyAmount.rdf +++ b/FND/Accounting/CurrencyAmount.rdf @@ -37,7 +37,7 @@ Currency Amount Ontology This ontology defines currency and monetary amount related concepts for use in defining other FIBO ontology elements. There are two distinct kinds of concepts that correspond to money and amounts: a concrete, actual amount of money, and the monetary measure of something denominated in some currency. These are dimensionally the same but whereas 'money amount' is defined as an amount of money, 'monetary amount' is an abstract monetary measure. -The definition of currency provided herein is compliant with the definitions given in ISO 4217. ISO 4217 provides universally applicable coded representations of names of currencies and funds, used internationally for financial transaction support. The ontology has been partitioned into 2 parts: (1) the essential concept system describing the standard (this module), and (2) ISO4217-1-CurrencyCodes, which contains all of the individuals specified in ISO 4217. +The definition of currency provided herein is compliant with the definitions given in ISO 4217. ISO 4217 provides universally applicable coded representations of names of currencies and funds, used internationally for financial transaction support. The ontology has been partitioned into 2 parts: (1) the essential concept system describing the standard (this module), and (2) ISO4217-1-CurrencyCodes, which contains all of the individuals specified in ISO 4217. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ Copyright (c) 2013-2022 EDM Council, Inc. @@ -60,7 +60,7 @@ The definition of currency provided herein is compliant with the definitions giv - + The FIBO FND 1.0 (https://spec.edmcouncil.org/fibo/ontology/FND/20141101/Accounting/CurrencyAmount.rdf) version of this ontology was modified per the additions introduced in the FIBO FBC RFC and related issue resolutions identified in the FIBO FND 1.1 RTF report and https://spec.edmcouncil.org/fibo/ontology/FND/1.0/AboutFND-1.1/, including adding support for ISO 4217 currency codes. The FIBO FND 1.1 (https://spec.edmcouncil.org/fibo/ontology/FND/20160201/Accounting/CurrencyAmount.rdf) version of this ontology was modified per FIBO 2.0 RFC, including the addition of a new hasMonetaryAmount property as a superproperty of others required by various FIBO domain teams and integration with LCC. The https://spec.edmcouncil.org/fibo/ontology/FND/20000601/Accounting/CurrencyAmount/ version of this ontology was modified to replace a redundant concept, calculation formula with formula. @@ -73,6 +73,7 @@ The definition of currency provided herein is compliant with the definitions giv The https://spec.edmcouncil.org/fibo/ontology/FND/20210201/Accounting/CurrencyAmount/ version of this ontology was modified to loosen a restriction on currency to allow for more than one numeric currency code, which was necessitated by the October 2021 update to the ISO currency code definitions. The https://spec.edmcouncil.org/fibo/ontology/FND/20220101/Accounting/CurrencyAmount/ version of this ontology was modified to move the definition of precious metal and the corresponding identifier to this ontology from Products and Services to simplify imports in cases where the broader definitions for commodities are not required and deprecated isTenderIn, given that we have used the property isUsedBy for this purpose in the currency codes themselves. The https://spec.edmcouncil.org/fibo/ontology/FND/20220201/Accounting/CurrencyAmount/ version of this ontology was modified to add a restriction to indicate the currency on percentage monetary amount, make currency a subclass of unit of measure, and deprecate the notion of monetary measure, which is more about monetary policy and was incorrectly used in a few places, and is out of scope for our current set of use cases. + The https://spec.edmcouncil.org/fibo/ontology/FND/20220301/Accounting/CurrencyAmount/ version of this ontology was modified to eliminate hygiene errors with respect to text formatting. (1) The present version of the ontology covers the English sections of the ISO 4217 standard only, and (2) UTF-8 character encodings are employed in names in the currency codes ontology to support the broadest number of tools. @@ -465,7 +466,7 @@ The definition of currency provided herein is compliant with the definitions giv has notional amount has an abstract, unchangeable value used for certain applicable calculations, expressed as some monetary amount - The domain for this property should be interpreted as being an abstraction which covers various forms of commitment, which may set out the existence of some notional amount of money, specified via this property. This is left unspecified for now, so that the property can also be defined directly as being a property of some contractual term which describes that commitment. + The domain for this property should be interpreted as being an abstraction which covers various forms of commitment, which may set out the existence of some notional amount of money, specified via this property. This is left unspecified for now, so that the property can also be defined directly as being a property of some contractual term which describes that commitment. The notional amount (or notional principal amount or notional value) on a financial instrument is the nominal or face amount that is used to calculate payments made on that instrument. This amount generally does not change and is thus referred to as notional. For securities the nominal value is often referred to as the face or par value. This is the redemption price of the security and is normally stated on the front of that security. With respect to bonds and stocks, it is the stated value of an issued security, as opposed to its market value. diff --git a/FND/Accounting/ISO4217-CurrencyCodes.rdf b/FND/Accounting/ISO4217-CurrencyCodes.rdf index f8b378610..2ebb4868b 100644 --- a/FND/Accounting/ISO4217-CurrencyCodes.rdf +++ b/FND/Accounting/ISO4217-CurrencyCodes.rdf @@ -54,12 +54,13 @@ - + The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/Accounting/ISO4217-CurrencyCodes/ version of this ontology was modified to replace Swaziland with Eswatini, which was revised by the LCC 1.1 RTF to reflect the change to the country name per the U.N. The https://spec.edmcouncil.org/fibo/ontology/FND/20190401/Accounting/ISO4217-CurrencyCodes/ version of this ontology was modified to eliminate duplication with concepts in LCC. The https://spec.edmcouncil.org/fibo/ontology/FND/20200201/Accounting/ISO4217-CurrencyCodes/ version of this ontology was modified to eliminate unnecessary dependencies on the relations ontology, and to replace rdfs:comment with skos:definition per FIBO policy. The https://spec.edmcouncil.org/fibo/ontology/FND/20220101/Accounting/ISO4217-CurrencyCodes/ version of this ontology was modified to reflect latest ISO and LCC data. The https://spec.edmcouncil.org/fibo/ontology/FND/20220201/Accounting/ISO4217-CurrencyCodes/ version of this ontology reflects the move of precious metal from products and services to currency amount, with no additional changes to the codes themselves. + The https://spec.edmcouncil.org/fibo/ontology/FND/20220301/Accounting/ISO4217-CurrencyCodes/ version of this ontology was modified to address hygiene errors with respect to text formatting. This version was generated from the ISO XML file as published on October 1, 2021 This release includes all codes included in the ISO 4217 published code set. @@ -3354,7 +3355,7 @@ 0 940 - The UYI (URUIURUI) is used for issuance of debt instruments by the Uruguayan government in the international global bond market. It is calculated based on an established methodology using underlying inflationary statistics in the Uruguayan market. (Introduced in 2002). + The UYI (URUIURUI) is used for issuance of debt instruments by the Uruguayan government in the international global bond market. It is calculated based on an established methodology using underlying inflationary statistics in the Uruguayan market. (Introduced in 2002). Uruguay Peso en Unidades Indexadas (UI) diff --git a/FND/AgentsAndPeople/Agents.rdf b/FND/AgentsAndPeople/Agents.rdf index 31d108af4..2f4bcbcdd 100644 --- a/FND/AgentsAndPeople/Agents.rdf +++ b/FND/AgentsAndPeople/Agents.rdf @@ -28,27 +28,28 @@ This ontology defines the concept of autonomous agent for use in other FIBO ontology elements. As defined here, autonomous agent corresponds to what is often referred to as "agent" in software and other systems. It is defined as any entity which is able to act on its own part, and embraces all such things, including people, animals, software agents organizations and all forms of legal persons, although not all of these concepts are elaborated in FIBO as not all are relevant to financial services. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2013-2021 EDM Council, Inc. - Copyright (c) 2013-2021 Object Management Group, Inc. + Copyright (c) 2013-2022 EDM Council, Inc. + Copyright (c) 2013-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/ https://www.omg.org/spec/LCC/Languages/LanguageRepresentation/ fibo-fnd-aap-agt Agents.rdf - + The https://spec.edmcouncil.org/fibo/ontology/FND/20130801/AgentsAndPeople/Agents.rdf version of this ontology was modified per the issue resolutions identified in the FIBO FND 1.0 FTF report and in https://spec.edmcouncil.org/fibo/ontology/FND/1.0/AboutFND-1.0/. The https://spec.edmcouncil.org/fibo/ontology/FND/20141101/AgentsAndPeople/Agents.rdf version of this ontology was modified to support the FIBO 2.0 RFC, primarily with respect to equivalence relationships to LCC. The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/AgentsAndPeople/Agents.rdf version of this ontology was modified to loosen the range restriction on hasName to rdfs:Literal, facilitating multi-lingual name representation. The https://spec.edmcouncil.org/fibo/ontology/FND/20190301/AgentsAndPeople/Agents.rdf version of this ontology was modified to eliminate duplication with concepts in LCC. The https://spec.edmcouncil.org/fibo/ontology/FND/20200201/AgentsAndPeople/Agents.rdf version of this ontology was modified to add a custom datatype for text values (which might be either xsd:string or rdf:langString) and use that in the restriction on hasName on autonomous agent. The https://spec.edmcouncil.org/fibo/ontology/FND/20210601/AgentsAndPeople/Agents.rdf version of this ontology was modified to add notes on the custom Text datatype indicating that it is outside the RL profile and that if someone wants to use this ontology with OWL 2 RL rules they might want to comment this out / eliminate it where it is used. + The https://spec.edmcouncil.org/fibo/ontology/FND/20210901/AgentsAndPeople/Agents.rdf version of this ontology was modified to address hygiene issues with respect to text formatting. The https://spec.edmcouncil.org/fibo/ontology/Foundations/20130601/AgentsAndPeople/Agents.owl version of the ontology was revised in advance of the September 2013 New Brunswick, NJ meeting, as follows: - (1) to use slash style URI/IRIs (also called 303 URIs, vs. hash style) as required to support server side processing - (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs - (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools - (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure - (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. + (1) to use slash style URI/IRIs (also called 303 URIs, vs. hash style) as required to support server side processing + (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs + (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools + (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure + (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. @@ -87,15 +88,15 @@ http://www.jamesodell.com/WhatIsAnAgent.pdf http://www.jamesodell.com/WhyShouldWeCareAboutAgents.pdf something autonomous that can adapt to and interact with its environment - Agents, then, can be software agents, hardware agents, firmware agents, robotic agents, human agents, and so on. While software developers naturally think of IT systems as being constructed of only software agents, a combination of agent mechanisms might in fact be used from shop-floor manufacturing to warfare systems. The definition incorporated herein must be sufficiently general to account for these and other uses, such as for describing people and organizations who participate in broader processes and systems, for FIBO, other OMG standards and usage, and in general. + Agents, then, can be software agents, hardware agents, firmware agents, robotic agents, human agents, and so on. While software developers naturally think of IT systems as being constructed of only software agents, a combination of agent mechanisms might in fact be used from shop-floor manufacturing to warfare systems. The definition incorporated herein must be sufficiently general to account for these and other uses, such as for describing people and organizations who participate in broader processes and systems, for FIBO, other OMG standards and usage, and in general. Whether or not you restrict your view of agents to the software variety, most agree that agents deployed for IT systems are not useful without the following three important properties: -(1) Autonomous - an agent is capable of acting without direct external intervention. Agents have some degree of control over their internal state and can act based on their own experiences. They can also possess their own set of internal responsibilities and processing that enable them to act without any external choreography. When an agent acts on behalf of (or as a proxy for) some person or thing, its autonomy is expected to embody the goals and policies of the entity that it represents. +(1) Autonomous - an agent is capable of acting without direct external intervention. Agents have some degree of control over their internal state and can act based on their own experiences. They can also possess their own set of internal responsibilities and processing that enable them to act without any external choreography. When an agent acts on behalf of (or as a proxy for) some person or thing, its autonomy is expected to embody the goals and policies of the entity that it represents. -(2) Interactive - an agent communicates with the environment and other agents. Agents are interactive entities because they are capable of exchanging rich forms of messages with other entities in their environment. These messages can support requests for services and other kinds of resources, as well as event detection and notification. They can be synchronous or asynchronous in nature. The interaction can also be conversational in nature, such as negotiating contracts, marketplace-style bidding, or simply making a query. +(2) Interactive - an agent communicates with the environment and other agents. Agents are interactive entities because they are capable of exchanging rich forms of messages with other entities in their environment. These messages can support requests for services and other kinds of resources, as well as event detection and notification. They can be synchronous or asynchronous in nature. The interaction can also be conversational in nature, such as negotiating contracts, marketplace-style bidding, or simply making a query. -(3) Adaptive - an agent is capable of responding to other agents and/or its environment. Agents can react to messages and events and then respond appropriately. Agents can be designed to make difficult decisions and even modify their behavior based on their experiences. They can learn and evolve. +(3) Adaptive - an agent is capable of responding to other agents and/or its environment. Agents can react to messages and events and then respond appropriately. Agents can be designed to make difficult decisions and even modify their behavior based on their experiences. They can learn and evolve. Note that this does not necessarily imply that an agent is free to act as it sees fit, without constraint. Rather, an autonomous thing in the sense meant here is something which may or may not be subject to controls and constraints but is self-actualizing in its behavior in response to any such constraints. Autonomous things may include human beings, organizations, software agents, robots and animals. The use of custom datatypes is outside the OWL 2 RL profile and so users should consider commenting out the restriction on hasTextValue altogether or change the data range to rdfs:Literal in applications that are constrained to OWL 2 RL. diff --git a/FND/AgentsAndPeople/People.rdf b/FND/AgentsAndPeople/People.rdf index 195eb6ef4..7d5a94c0b 100644 --- a/FND/AgentsAndPeople/People.rdf +++ b/FND/AgentsAndPeople/People.rdf @@ -46,8 +46,8 @@ This ontology defines concepts for people and human related terms, for use in other FIBO ontology elements. People as defined here are human persons only. This ontology sets out a number of basic properties which are held by people or are definitive of a small number of specific types of people such as minors or adults. Primary use cases for determining the set of personal information definitions included are the common elements required to (1) open a bank account, (2) identify a sophisticated investor, and (3) establish foreign account ownership for money laundering purposes. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2013-2021 EDM Council, Inc. - Copyright (c) 2013-2021 Object Management Group, Inc. + Copyright (c) 2013-2022 EDM Council, Inc. + Copyright (c) 2013-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/AgentsAndPeople/Agents/ https://spec.edmcouncil.org/fibo/ontology/FND/Arrangements/Documents/ https://spec.edmcouncil.org/fibo/ontology/FND/Arrangements/IdentifiersAndIndices/ @@ -71,18 +71,18 @@ - + The http://spec.edmcouncil.org/fibo/ontology/FND/20130801/AgentsAndPeople/People.rdf version of the ontology was was modified per the issue resolutions identified in the FIBO FND 1.0 FTF report and in https://spec.edmcouncil.org/fibo/ontology/FND/1.0/AboutFND-1.0/. It was further revised in the FTF in advance of the Long Beach meeting, resulting in https://spec.edmcouncil.org/fibo/ontology/FND/20141101/AgentsAndPeople/People/. The http://spec.edmcouncil.org/fibo/ontology/FND/20141101/AgentsAndPeople/People.rdf version of the ontology was was modified per the issue resolutions identified in the FIBO FND 1.1 RTF report, primarily to use the hasAddress property in addresses, and change PostalAddress to PhysicalAddress in a restriction on Person. Also revised the identifiesAddress property in favor of verifiesAddress, and revised hasDateofBirth with respect to an identity document to be verifiesDateOfBirth, which was determined to be more appropriate by the RTF. - The http://www.omg.org/spec/EDMC-FIBO/FND/20160201/AgentsAndPeople/People.rdf version of the ontology was was modified per the FIBO 2.0 RFC, including integration of LCC. + The http://www.omg.org/spec/EDMC-FIBO/FND/20160201/AgentsAndPeople/People.rdf version of the ontology was modified per the FIBO 2.0 RFC, including integration of LCC. The http://www.omg.org/spec/FIBO/Foundations/20130601/AgentsAndPeople/People.owl version of the ontology was revised in advance of the September 2013 New Brunswick, NJ meeting, as follows: - (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing - (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs - (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools - (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure - (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. - (6) to revise and extend the set of properties about people required to fulfill the set of use cases listed above. - The https://spec.edmcouncil.org/fibo/ontology/FND/20181101/AgentsAndPeople/People.rdf version of the ontology was was modified to revise a restriction on IdentityDocument to reference the appropriate identifier rather than use a tag. The impetus behind this change is to support privacy legislation, such as GDPR, which requires protection of both identifiers, such as a passport number, drivers' license number, etc. as well as the documents themselves. Thus, properties and individuals related to those identifiers are urgently needed. + (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing + (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs + (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools + (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure + (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. + (6) to revise and extend the set of properties about people required to fulfill the set of use cases listed above. + The https://spec.edmcouncil.org/fibo/ontology/FND/20181101/AgentsAndPeople/People.rdf version of the ontology was was modified to revise a restriction on IdentityDocument to reference the appropriate identifier rather than use a tag. The impetus behind this change is to support privacy legislation, such as GDPR, which requires protection of both identifiers, such as a passport number, drivers' license number, etc. as well as the documents themselves. Thus, properties and individuals related to those identifiers are urgently needed. The https://spec.edmcouncil.org/fibo/ontology/FND/20190501/AgentsAndPeople/People.rdf version of the ontology was modified to replace hasDefinition with isDefinedIn to clarify intent. The https://www.omg.org/spec/EDMC-FIBO/FND/20180801/AgentsAndPeople/People.rdf version of the ontology was modified to deprecate legally capable person in favor of natural person (defined in Business Entities). The https://www.omg.org/spec/EDMC-FIBO/FND/20190501/AgentsAndPeople/People.rdf version of the ontology was modified to eliminate deprecated elements. @@ -92,6 +92,7 @@ The https://www.omg.org/spec/EDMC-FIBO/FND/20210301/AgentsAndPeople/People.rdf version of the ontology was modified to allow the People ontology to import Parties, rather than the other way around, to simplify the class hierarchy for ease of use in data mapping and alignment, and to add person name as a first class concept, revising property definitions to allow for structured names by loosening constraints. The https://www.omg.org/spec/EDMC-FIBO/FND/20210401/AgentsAndPeople/People.rdf version of the ontology was modified to add concepts specific to legal age, age of majority, legal working age and legal working age person. The https://www.omg.org/spec/EDMC-FIBO/FND/20210601/AgentsAndPeople/People.rdf version of the ontology was modified to revise the definition of passport number as a national identification number and eliminate restrictions that would cause people to be inferred to be passports. + The https://www.omg.org/spec/EDMC-FIBO/FND/20211101/AgentsAndPeople/People.rdf version of the ontology was modified to address hygiene issues with respect to text formatting. @@ -128,7 +129,7 @@ birth certificate an original document certifying the circumstances of the birth, or a certified copy of or representation of the ensuing registration of that birth http://en.wikipedia.org/wiki/Birth_certificate - A birth certificate is a vital record that documents the birth of a child. Depending on the jurisdiction, a record of birth might or might not contain verification of the event by such as a midwife or doctor. + A birth certificate is a vital record that documents the birth of a child. Depending on the jurisdiction, a record of birth might or might not contain verification of the event by such as a midwife or doctor. certificate of live birth @@ -319,7 +320,7 @@ identity document any legal document which may be used to verify aspects of a person's identity https://en.wikipedia.org/wiki/Identification_card - If issued in the form of a small, mostly standard-sized card, it is usually called an identity card (IC). Countries which do not have formal identity documents may require informal documents. In the absence of a formal identity document, driving licenses can be used in many countries as a method of proof of identity, although some countries do not accept driving licenses for identification, often because in those countries they don't expire as documents and can be old and easily forged. Most countries accept passports as a form of identification. Most countries have the rule that foreign citizens need to have their passport or occasionally a national identity card from their country available at any time if they do not have residence permit in the country. + If issued in the form of a small, mostly standard-sized card, it is usually called an identity card (IC). Countries which do not have formal identity documents may require informal documents. In the absence of a formal identity document, driving licenses can be used in many countries as a method of proof of identity, although some countries do not accept driving licenses for identification, often because in those countries they don't expire as documents and can be old and easily forged. Most countries accept passports as a form of identification. Most countries have the rule that foreign citizens need to have their passport or occasionally a national identity card from their country available at any time if they do not have residence permit in the country. identity card @@ -676,7 +677,7 @@ Many countries issued such numbers ostensibly for a singular purpose, but over t has person name links a name to an individual - Note that the concept of a person name may include symbology as long as the symbols are properly encoded. Because person name is a class, other iconography or symbology that cannot be encoded in UTF-8 can, alternatively, be linked or attached as a separate image or in another form. + Note that the concept of a person name may include symbology as long as the symbols are properly encoded. Because person name is a class, other iconography or symbology that cannot be encoded in UTF-8 can, alternatively, be linked or attached as a separate image or in another form. @@ -693,7 +694,7 @@ Many countries issued such numbers ostensibly for a singular purpose, but over t identifies a dwelling where an individual resides the majority of the year - For tax purposes, in cases when an individual owns more than one home, their primary residence is the home in which they reside most of the time, and for which they can provide evidence to that effect. Having said this, there are cases, such as for individuals that have dual citizenship, where they may have multiple primary residences, one in each country in which they maintain a home. There may also be subtle issues related to 'rent control' that may impact the statements an individual makes about their primary residence. In other words, one cannot necessarily infer a person's identity from their primary place of residence. + For tax purposes, in cases when an individual owns more than one home, their primary residence is the home in which they reside most of the time, and for which they can provide evidence to that effect. Having said this, there are cases, such as for individuals that have dual citizenship, where they may have multiple primary residences, one in each country in which they maintain a home. There may also be subtle issues related to 'rent control' that may impact the statements an individual makes about their primary residence. In other words, one cannot necessarily infer a person's identity from their primary place of residence. diff --git a/FND/Agreements/Contracts.rdf b/FND/Agreements/Contracts.rdf index 776896189..560bb9d5f 100644 --- a/FND/Agreements/Contracts.rdf +++ b/FND/Agreements/Contracts.rdf @@ -75,13 +75,13 @@ - + The http://www.omg.org/spec/FIBO/Foundations/20130601/Agreements/Contracts.owl version of the ontology was revised in advance of the September 2013 New Brunswick, NJ meeting, as follows: - (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing - (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs - (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools - (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure - (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. + (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing + (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs + (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools + (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure + (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. The https://spec.edmcouncil.org/fibo/ontology/FND/20130801/Agreements/Contracts.rdf version of the ontology was was modified per the issue resolutions identified in the FIBO FND 1.0 FTF report and in https://spec.edmcouncil.org/fibo/ontology/FND/1.0/AboutFND-1.0/. The https://spec.edmcouncil.org/fibo/ontology/FND/20141101/Agreements/Contracts.rdf version of this ontology was revised as a part of the issue resolutions identified in the FIBO FND 1.1 RTF report to add a parent of hasDate to date properties. The https://spec.edmcouncil.org/fibo/ontology/FND/20160201/Agreements/Contracts.rdf version of this ontology was revised as a part of the issue resolutions identified in the FIBO FND 1.2 RTF report to revise definitions related to contractual element, add contractual commitment and deprecate contract terms set. @@ -95,6 +95,7 @@ The https://spec.edmcouncil.org/fibo/ontology/FND/20210401/Agreements/Contracts.rdf version of this ontology was revised to change a duplicate definition on hasContractDuration to an explanatory note. The https://spec.edmcouncil.org/fibo/ontology/FND/20210701/Agreements/Contracts.rdf version of this ontology was revised to add the concept of a master agreement and fix spelling errors. The https://spec.edmcouncil.org/fibo/ontology/FND/20211201/Agreements/Contracts.rdf version of this ontology was revised to move the property hasTerm from FinancialInstruments to Contracts as it is more broadly applicable. + The https://spec.edmcouncil.org/fibo/ontology/FND/20220101/Agreements/Contracts.rdf version of this ontology was revised to address hygiene issues with respect to text formatting. @@ -258,7 +259,7 @@ contract principal party that originates a contract and is identified as the first party to that contract, in the event that the contract distinguishes any party as such - The principal to a contract is typically the originator and, in the case of a security, the issuer. In law, the principal is the party that has the primary responsibility in a liability or obligation, as opposed to an endorser, guarantor, or surety. + The principal to a contract is typically the originator and, in the case of a security, the issuer. In law, the principal is the party that has the primary responsibility in a liability or obligation, as opposed to an endorser, guarantor, or surety. diff --git a/FND/Arrangements/Arrangements.rdf b/FND/Arrangements/Arrangements.rdf index 1feb2cba5..ea7e621c9 100644 --- a/FND/Arrangements/Arrangements.rdf +++ b/FND/Arrangements/Arrangements.rdf @@ -30,8 +30,8 @@ This ontology defines abstract structural concepts, including arrangement and collection, for use in other FIBO ontology elements. These abstract concepts are further refined to support definition of identifiers, codes, quantities, and schemata that organize and classify such identifiers and codes. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2014-2021 EDM Council, Inc. - Copyright (c) 2014-2021 Object Management Group, Inc. + Copyright (c) 2014-2022 EDM Council, Inc. + Copyright (c) 2014-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/Relations/Relations/ https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/ https://www.omg.org/spec/LCC/Languages/LanguageRepresentation/ @@ -40,8 +40,8 @@ - - The https://spec.edmcouncil.org/fibo/ontology/FND/20140801/Arrangements/Arrangements.rdf version of this ontology was introduced as a part of the issue resolutions identified in the FIBO FND 1.0 FTF report and in https://spec.edmcouncil.org/fibo/ontology/FND/1.0/AboutFND-1.0/. It was further revised in the FTF in advance of the Long Beach meeting to promote Collection to the top level in the hierarchy, resulting in https://spec.edmcouncil.org/fibo/ontology/FND/20141101/Arrangements/Arrangements/. + + The https://spec.edmcouncil.org/fibo/ontology/FND/20140801/Arrangements/Arrangements.rdf version of this ontology was introduced as a part of the issue resolutions identified in the FIBO FND 1.0 FTF report and in https://spec.edmcouncil.org/fibo/ontology/FND/1.0/AboutFND-1.0/. It was further revised in the FTF in advance of the Long Beach meeting to promote Collection to the top level in the hierarchy, resulting in https://spec.edmcouncil.org/fibo/ontology/FND/20141101/Arrangements/Arrangements/. The https://spec.edmcouncil.org/fibo/ontology/FND/20141101/Arrangements/Arrangements.rdf version of this ontology was revised as a part of the issue resolutions identified in the FIBO FND 1.2 RTF report to add a definition for a structured collection. The https://spec.edmcouncil.org/fibo/ontology/FND/20170201/Arrangements/Arrangements.rdf version of this ontology was revised for the FIBO 2.0 RFC report to add a general definition for scheme, add dated collection, and add mappings to LCC. The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/Arrangements/Arrangements.rdf version of this ontology was revised to loosen the range on hasObservedDateTime such that it can be used more generally. @@ -49,6 +49,7 @@ The https://spec.edmcouncil.org/fibo/ontology/FND/20190401/Arrangements/Arrangements.rdf version of this ontology was revised to eliminate duplication with concepts in LCC for classes including arrangement, collection, code element, code set, etc to simplify the hierarchy and usage for FIBO users. The https://spec.edmcouncil.org/fibo/ontology/FND/20200201/Arrangements/Arrangements.rdf version of this ontology was revised to move the concepts of a dated collection and dated collection constituent to Financial Dates in order to improve usability and simplify reasoning and make definitions ISO 704 compliant. The https://spec.edmcouncil.org/fibo/ontology/FND/20200701/Arrangements/Arrangements.rdf version of this ontology was revised to add a restriction to structured collection pointing to the arrangement used to organize that collection, and to revise the definition accordingly. + The https://spec.edmcouncil.org/fibo/ontology/FND/20210901/Arrangements/Arrangements.rdf version of this ontology was revised to address hygiene issues with respect to text formatting. @@ -99,7 +100,7 @@ has constituent consists of or contains - Being a constituent of something does not necessarily mean parthood. Whole-part relations are transitive, whereas constituency is not necessarily transitive and so this property is useful in cases where transitivity is not necessarily desirable or appropriate. + Being a constituent of something does not necessarily mean parthood. Whole-part relations are transitive, whereas constituency is not necessarily transitive and so this property is useful in cases where transitivity is not necessarily desirable or appropriate. diff --git a/FND/Arrangements/ClassificationSchemes.rdf b/FND/Arrangements/ClassificationSchemes.rdf index fcb75e550..a0ad835f9 100644 --- a/FND/Arrangements/ClassificationSchemes.rdf +++ b/FND/Arrangements/ClassificationSchemes.rdf @@ -32,8 +32,8 @@ This ontology defines abstract concepts for representation of classification schemes that themselves are intended to permit the classification of arbitrary concepts into hierarchies (or partial orders) for use in other FIBO ontology elements. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2014-2021 EDM Council, Inc. - Copyright (c) 2014-2021 Object Management Group, Inc. + Copyright (c) 2014-2022 EDM Council, Inc. + Copyright (c) 2014-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/Arrangements/Arrangements/ https://spec.edmcouncil.org/fibo/ontology/FND/Relations/Relations/ https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/ @@ -44,11 +44,12 @@ - + The https://spec.edmcouncil.org/fibo/ontology/FND/20150501/Arrangements/ClassificationSchemes.rdf version of this ontology was introduced as a part of the initial FIBO FBC RFC and revised due to changes introduced in the FIBO 2.0 RFC. The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/Arrangements/ClassificationSchemes.rdf version of this ontology was revised to replace hasDefinition with isDefinedIn to clarify intent. The https://spec.edmcouncil.org/fibo/ontology/FND/20190701/Arrangements/ClassificationSchemes.rdf version of this ontology was revised to eliminate duplication of concepts in LCC and change the parent class of Classifier to Aspect in Analytics. The https://spec.edmcouncil.org/fibo/ontology/FND/20200701/Arrangements/ClassificationSchemes.rdf version of this ontology was revised to eliminate circular definitions. + The https://spec.edmcouncil.org/fibo/ontology/FND/20210201/Arrangements/ClassificationSchemes.rdf version of this ontology was revised to address hygiene issues with respect to text formatting and loosen the constraint on classifier from classifies something to min 0. @@ -69,15 +70,15 @@ - - - 1 + + 0 - - + + + 1 classifier @@ -95,7 +96,7 @@ industry sector classification scheme system for allocating classifiers to organizations by industry sector - Examples include the North American Industry Classification System (NAICS) and Standardized Industry Classification (SIC) in the U.S. and Canada, and the NACE (Nomenclature Générale des Activités Économiques dans les Communautés Européennes) in the EU, developed by governments to classify industries. They also include commercial classification schemes, such as the Global Industry Standard Classification (GICS) developed jointly by Morgan Stanley Capital International (MSCI) and Standard and Poor's, and competing schemes including the Industry Classification Benchmark (ICB) system, maintained by Dow Jones and London's FTSE Group, among others. + Examples include the North American Industry Classification System (NAICS) and Standardized Industry Classification (SIC) in the U.S. and Canada, and the NACE (Nomenclature Générale des Activités Économiques dans les Communautés Européennes) in the EU, developed by governments to classify industries. They also include commercial classification schemes, such as the Global Industry Standard Classification (GICS) developed jointly by Morgan Stanley Capital International (MSCI) and Standard and Poor's, and competing schemes including the Industry Classification Benchmark (ICB) system, maintained by Dow Jones and London's FTSE Group, among others. diff --git a/FND/Arrangements/Ratings.rdf b/FND/Arrangements/Ratings.rdf index b1d12763d..7d3cf4e15 100644 --- a/FND/Arrangements/Ratings.rdf +++ b/FND/Arrangements/Ratings.rdf @@ -52,8 +52,8 @@ This ontology defines abstract concepts for representation of ratings and rating schemes, particularly for ratings describing aspects of business performance, credit worthiness, and investment quality at a high level. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2019-2021 EDM Council, Inc. - Copyright (c) 2019-2021 Object Management Group, Inc. + Copyright (c) 2019-2022 EDM Council, Inc. + Copyright (c) 2019-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/Agreements/Contracts/ https://spec.edmcouncil.org/fibo/ontology/FND/Arrangements/Assessments/ https://spec.edmcouncil.org/fibo/ontology/FND/Arrangements/ClassificationSchemes/ @@ -83,12 +83,13 @@ - + The https://spec.edmcouncil.org/fibo/ontology/FND/20190601/Arrangements/Ratings.rdf version of this ontology was revised to replace hasDefinition with isDefinedIn to clarify intent. The https://spec.edmcouncil.org/fibo/ontology/FND/20190701/Arrangements/Ratings.rdf version of this ontology was revised to add properties indicating the 'best' and 'worst' scores on a given scale. The https://spec.edmcouncil.org/fibo/ontology/FND/20190901/Arrangements/Ratings.rdf version of this ontology was revised to eliminate duplication with LCC. The https://spec.edmcouncil.org/fibo/ontology/FND/20200201/Arrangements/Ratings.rdf version of this ontology was revised to replace uses of hasTag in Relations with hasTag from LCC, as the more complex union of datatypes in the Relations concept is not needed here. The https://spec.edmcouncil.org/fibo/ontology/FND/20200701/Arrangements/Ratings.rdf version of this ontology was revised to eliminate circular definitions. + The https://spec.edmcouncil.org/fibo/ontology/FND/20210201/Arrangements/Ratings.rdf version of this ontology was revised to address hygiene issues with respect to text formatting. @@ -324,7 +325,7 @@ rating score grade, classification, or ranking of for something in accordance with some rating scale - The meaning and methodology for determining a rating score for the rating of something is determined by a rating issuer. A given rating may apply at some point in time, as a part of a lifecycle or process, or generally. Typically ratings reflect an assessment of a state of affairs at some point in time. + The meaning and methodology for determining a rating score for the rating of something is determined by a rating issuer. A given rating may apply at some point in time, as a part of a lifecycle or process, or generally. Typically ratings reflect an assessment of a state of affairs at some point in time. diff --git a/FND/DatesAndTimes/BusinessDates.rdf b/FND/DatesAndTimes/BusinessDates.rdf index fb6707c83..553548ef2 100644 --- a/FND/DatesAndTimes/BusinessDates.rdf +++ b/FND/DatesAndTimes/BusinessDates.rdf @@ -34,8 +34,8 @@ This ontology extends definitions of date and schedule concepts from the FinancialDates ontology with concepts defining dates that may be adjusted when they fall on weekends or holidays as defined in a given business center, for use in other FIBO ontologies. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2014-2021 EDM Council, Inc. - Copyright (c) 2014-2021 Object Management Group, Inc. + Copyright (c) 2014-2022 EDM Council, Inc. + Copyright (c) 2014-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/DatesAndTimes/FinancialDates/ https://spec.edmcouncil.org/fibo/ontology/FND/Places/Locations/ https://spec.edmcouncil.org/fibo/ontology/FND/Relations/Relations/ @@ -48,20 +48,21 @@ - + The https://spec.edmcouncil.org/fibo/ontology/FND/20141101/DatesAndTimes/BusinessDates/ version of this ontology was revised by the FIBO FND 1.2 RTF in order to add definitions for business recurrence intervals such as the day of the month and week, and to revise the representation of the end of the month to correspond to the way that the other intervals are represented for use in parametric schedules. The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/DatesAndTimes/BusinessDates/ version of this ontology was revised to better support definitions related to business day adjustments. The https://spec.edmcouncil.org/fibo/ontology/FND/20180901/DatesAndTimes/BusinessDates/ version of this ontology was revised to loosen domains on properties related to business day and day count (recurrence interval) conventions, eliminate a duplicate individual, normalize definitions to be ISO 704 compliant, eliminate duplication of concepts in LCC, move hasBusinessCenter to locations, where the class BusinessCenter is defined and merge countries with locations. The https://spec.edmcouncil.org/fibo/ontology/FND/20200301/DatesAndTimes/BusinessDates/ version of this ontology was revised to eliminate a remaining circular definition. - This ontology was added to Foundations in advance of the December 2014 Long Beach meeting in support of the SEC specification. It is also needed to provide temporal relationships for Ownership and Control. + The https://spec.edmcouncil.org/fibo/ontology/FND/20210201/DatesAndTimes/BusinessDates/ version of this ontology was revised to address hygiene issues with respect to text processing. + This ontology was added to Foundations in advance of the December 2014 Long Beach meeting in support of the SEC specification. It is also needed to provide temporal relationships for Ownership and Control. These three ontologies are designed for use together: - * FinancialDates -- financial Dates and Schedules - * BusinessDates -- business day adjustments - * Occurrences -- occurrences (events) and kinds of occurrences + * FinancialDates -- financial Dates and Schedules + * BusinessDates -- business day adjustments + * Occurrences -- occurrences (events) and kinds of occurrences -They are modularized this way to minimize the ontological committments that are imposed upon ontologies that rely upon them. Ontologies can import FinancialDates alone, or FinancialDates + BusinessDates, or FinancialDates + Occurrences, or all three together. +They are modularized this way to minimize the ontological committments that are imposed upon ontologies that rely upon them. Ontologies can import FinancialDates alone, or FinancialDates + BusinessDates, or FinancialDates + Occurrences, or all three together. diff --git a/FND/DatesAndTimes/FinancialDates.rdf b/FND/DatesAndTimes/FinancialDates.rdf index c099276aa..58f23c821 100644 --- a/FND/DatesAndTimes/FinancialDates.rdf +++ b/FND/DatesAndTimes/FinancialDates.rdf @@ -30,8 +30,8 @@ This ontology provides definitions of date and schedule concepts for use in other FIBO ontologies. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2014-2021 EDM Council, Inc. - Copyright (c) 2014-2021 Object Management Group, Inc. + Copyright (c) 2014-2022 EDM Council, Inc. + Copyright (c) 2014-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/Arrangements/Arrangements/ https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/ https://www.omg.org/spec/LCC/ @@ -40,7 +40,7 @@ - + The https://spec.edmcouncil.org/fibo/ontology/FND/20141101/DatesAndTimes/FinancialDates/ version of this ontology was revised by the FIBO FND 1.2 RTF in order to introduce the definition of a time interval, which is a location, to ground some of the concepts such as a date period, and duration as well as to support the definition of business recurrence intervals for use in parametric schedules for securities. The https://spec.edmcouncil.org/fibo/ontology/FND/20170201/DatesAndTimes/FinancialDates/ version of this ontology was revised by the FIBO 2.0 RFC in order to introduce the definition of a time instant, to eliminate a reasoning issue with relative dates, and remove a circular dependency inadvertently incorporated in the ontology with a FIBO FND 1.2 modification. The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/DatesAndTimes/FinancialDates/ version of this ontology was revised to introduce a composite date datatype to allow for cases whereby the representation of a date for certain purposes, such as GLEIF LEI data, is inconsistent, and to facilitate mapping FIBO to multiple data sources in user environments. @@ -51,15 +51,16 @@ The https://spec.edmcouncil.org/fibo/ontology/FND/20201201/DatesAndTimes/FinancialDates/ version of this ontology was revised to add the concept of age and a corresponding property that supports its use. The https://spec.edmcouncil.org/fibo/ontology/FND/20210601/DatesAndTimes/FinancialDates.rdf version of this ontology was modified to add notes on the custom CombinedDateTime datatype indicating that it is outside the RL profile and that if someone wants to use this ontology with OWL 2 RL rules they might want to comment this out / eliminate it where it is used. The https://spec.edmcouncil.org/fibo/ontology/FND/20210901/DatesAndTimes/FinancialDates.rdf version of this ontology was modified to remove a functional declaration on hasObservedDateTime, which causes reasoning inconsistencies when there are multiple uses of that property for certain individuals, such as for LEI registration. - This ontology was added to Foundations in advance of the December 2014 Long Beach meeting in support of the SEC specification. It is also needed to provide temporal relationships for Ownership and Control. + The https://spec.edmcouncil.org/fibo/ontology/FND/20211201/DatesAndTimes/FinancialDates.rdf version of this ontology was modified to address hygiene issues with respect to text formatting. + This ontology was added to Foundations in advance of the December 2014 Long Beach meeting in support of the SEC specification. It is also needed to provide temporal relationships for Ownership and Control. These three ontologies are designed for use together: - * FinancialDates -- financial Dates and Schedules - * BusinessDates -- business day adjustments - * Occurrences -- occurrences (events) and kinds of occurrences + * FinancialDates -- financial Dates and Schedules + * BusinessDates -- business day adjustments + * Occurrences -- occurrences (events) and kinds of occurrences -They are modularized this way to minimize the ontological committments that are imposed upon ontologies that rely upon them. Ontologies can import FinancialDates alone, or FinancialDates + BusinessDates, or FinancialDates + Occurrences, or all three together. +They are modularized this way to minimize the ontological committments that are imposed upon ontologies that rely upon them. Ontologies can import FinancialDates alone, or FinancialDates + BusinessDates, or FinancialDates + Occurrences, or all three together. @@ -106,7 +107,7 @@ They are modularized this way to minimize the ontological committments that are calculated date date that is or will be determined based on some formula - The hasDateValue property of a CalculatedDate is not set until the Date is calculated. Since the calculation may depend upon future events that may or may not ever happen, the hasDateValue property may never be set. + The hasDateValue property of a CalculatedDate is not set until the Date is calculated. Since the calculation may depend upon future events that may or may not ever happen, the hasDateValue property may never be set. @@ -122,7 +123,7 @@ They are modularized this way to minimize the ontological committments that are time interval that occurs within a system that fixes the beginning and length of a segment of the year with respect to that system The terms 'calendar xxx' are intended to reinforce that these are periods on a calendar, not durations. -For example, a calendar year always starts on a January 1 and ends on a December 31. The term 'calendar year' does not mean the same thing as a duration (an amount of time) of 1 year, nor can a calendar year start on any arbitrary day of a year. For example, a calendar year never starts on September 1. +For example, a calendar year always starts on a January 1 and ends on a December 31. The term 'calendar year' does not mean the same thing as a duration (an amount of time) of 1 year, nor can a calendar year start on any arbitrary day of a year. For example, a calendar year never starts on September 1. Similar points apply to other kinds of calendar periods, such as calendar week, calendar month, and calendar quarter. A calendar-specified date may be figured with respect to a calendar week, a calendar month, a calendar quarter, or a calendar year. @@ -194,7 +195,7 @@ Similar points apply to other kinds of calendar periods, such as calendar week, datatype that maps to several base types for dates and times - There are many cases where the representation of a date may or may not include a time, and where the underlying data representation varies. This composite datatype should only be used in cases where a standard representation using one of the options in the union for date or date and time value specification does not work. + There are many cases where the representation of a date may or may not include a time, and where the underlying data representation varies. This composite datatype should only be used in cases where a standard representation using one of the options in the union for date or date and time value specification does not work. The use of custom datatypes is outside the OWL 2 RL profile and so users should consider commenting this and its usage here, and in other ontologies out, or replacing it with rdfs:Literal out in applications that are constrained to OWL 2 RL. Valid values must use the ISO 8601 representation for a date, or the corresponding XML Schema Datatypes representation for a date and time, or date and time including the time zone. @@ -210,7 +211,7 @@ Similar points apply to other kinds of calendar periods, such as calendar week, date calendar day on some calendar - A Date may or may not have a value, and may be explicit or calculated. A Date that has a value is one that is either explicitly set as a literal when it is created, or is some form of CalculatedDate. In an instance of Date, the existence of the 'hasDateValue' property both indicates that the Date is known, and gives the value of the Date. A Date that does not have a value is one that is some form of CalculatedDate, in which the actual date has not (yet) been established. + A Date may or may not have a value, and may be explicit or calculated. A Date that has a value is one that is either explicitly set as a literal when it is created, or is some form of CalculatedDate. In an instance of Date, the existence of the 'hasDateValue' property both indicates that the Date is known, and gives the value of the Date. A Date that does not have a value is one that is some form of CalculatedDate, in which the actual date has not (yet) been established. @@ -253,7 +254,7 @@ Similar points apply to other kinds of calendar periods, such as calendar week, date time time point including a date and a time, optionally including a time zone offset - 'hasDateTimeValue' is omitted if the DateTime is not (yet) known. Note that the time zone is implicitly GMT. + 'hasDateTimeValue' is omitted if the DateTime is not (yet) known. Note that the time zone is implicitly GMT. @@ -281,7 +282,7 @@ Similar points apply to other kinds of calendar periods, such as calendar week, dated collection constituent element of a collection that is associated with a date and time - Note that the use of several options for the representation of a date and time stamp enables extensions for milliseconds, nanoseconds using an xsd:string that has the format of an xsd:dateTime datatype but extends the level of granularity consistently. An example of where this is required is to represent prices that change multiple times in a given day. + Note that the use of several options for the representation of a date and time stamp enables extensions for milliseconds, nanoseconds using an xsd:string that has the format of an xsd:dateTime datatype but extends the level of granularity consistently. An example of where this is required is to represent prices that change multiple times in a given day. The use of custom datatypes is outside the OWL 2 RL profile and so users should consider commenting out the restriction on hasObservedDateTime altogether or change the data range to rdfs:Literal in applications that are constrained to OWL 2 RL. @@ -460,14 +461,14 @@ Similar points apply to other kinds of calendar periods, such as calendar week, The payment schedule is a RegularSchedule with these properties: -* comprises: regular payment OccurrenceKind (with payment details) (see the 'comprises' property of the Occurrences ontology) +* comprises: regular payment OccurrenceKind (with payment details) (see the 'comprises' property of the Occurrences ontology) * hasInitialStub: June 15-30, 2015 for initial payment * hasFinalStub: June 1-14, 2045 for final payment * hasCount: 358 * hasOverallPeriod starting Date: June 15, 2015 with a duration of 30 years * hasRecurrenceInterval: specifies 10th day of each calendar month * hasRecurrenceStartDate: July 1, 2015 - A corporate bond pays interest for 10 years starting on the first day of 2015. Interest payments are due 15 days after the expiration of each 6 month period: on July 15 and January 16. + A corporate bond pays interest for 10 years starting on the first day of 2015. Interest payments are due 15 days after the expiration of each 6 month period: on July 15 and January 16. The payment schedule is a RegularSchedule, with these properties: @@ -476,13 +477,13 @@ The payment schedule is a RegularSchedule, with these properties: * hasCount is 20 (2 payments per year for 10 years) * hasRecurrenceInterval is 'P6M' * hasRecurrenceStartDate is '2015-01-15' - A RegularSchedule is a Schedule defined as a set of Dates that start on a recurrence start date and repeat after each recurrence interval. The size of this set is defined by a count. + A RegularSchedule is a Schedule defined as a set of Dates that start on a recurrence start date and repeat after each recurrence interval. The size of this set is defined by a count. -The 'initial ScheduleStub' associated with a RegularSchedule identifies any special treatment applied before the recurrence start date. Similarly, a 'final ScheduleStub' identifies any special handling at the end of the recurrences. For example, a mortgage loan that is due each calendar month may have an initial payment due before the first calendar month, or a final payment due after the last monthly payment. +The 'initial ScheduleStub' associated with a RegularSchedule identifies any special treatment applied before the recurrence start date. Similarly, a 'final ScheduleStub' identifies any special handling at the end of the recurrences. For example, a mortgage loan that is due each calendar month may have an initial payment due before the first calendar month, or a final payment due after the last monthly payment. Other ontologies can extend RegularSchedule as needed. -In particular, the Occurrences ontology extends RegularSchedule to 'comprise' an 'OccurrenceKind'. The intended meaning is that a regular schedule comprises a number of scheduled dates and an event which is scheduled to occur on each of those dates, in other words an Occurrence of the OccurrenceKind should happen on each Date defined by the RegularSchedule. - The recurrence start date can be an ExplicitDate or any kind of CalculatedDate. Hence, the starting date could be relative to another Date (e.g. T+3) or triggered by the Occurrence of an OccurrenceKind, etc. +In particular, the Occurrences ontology extends RegularSchedule to 'comprise' an 'OccurrenceKind'. The intended meaning is that a regular schedule comprises a number of scheduled dates and an event which is scheduled to occur on each of those dates, in other words an Occurrence of the OccurrenceKind should happen on each Date defined by the RegularSchedule. + The recurrence start date can be an ExplicitDate or any kind of CalculatedDate. Hence, the starting date could be relative to another Date (e.g. T+3) or triggered by the Occurrence of an OccurrenceKind, etc. The recurrence start date can also be relative to the starting Date of the overall DatePeriod of the Schedule. @@ -506,7 +507,7 @@ The recurrence start date can also be relative to the starting Date of the overa relative date calculated date that is some duration before or after another date - A settlement date, defined as T+3: three days after the trade date. The 'hasRelativeDuration' property is set to '3D'. + A settlement date, defined as T+3: three days after the trade date. The 'hasRelativeDuration' property is set to '3D'. When the 'hasRelativeDuration' property is negative, the RelativeDate is before the 'isRelativeTo' Date; otherwise the RelativeDate is after the 'isRelativeTo' Date. @@ -543,7 +544,7 @@ The recurrence start date can also be relative to the starting Date of the overa schedule stub date period before the start of the recurring part of a schedule or after the end of the recurring part, which may be associated with a specific occurrence kind The Occurrences ontology extends ScheduleStub to 'comprise' an OccurrenceKind. The meaning is that a schedule stub comprises a date period and an event which is scheduled to occur during that date period; in other words that an Occurrence of the OccurrenceKind should happen during the DatePeriod of the ScheduleStub. - A 30 year mortgage calls for monthly payments on the first day of each month, according to a RegularSchedule. If the mortgage does not start on the first day of a calendar month, then an initial ScheduleStub specifies the payment due for the DatePeriod up to the first day of the next calendar month. Similarly, a final ScheduleStub specifies the last payment due for the DatePeriod after the end of the last full calendar month. + A 30 year mortgage calls for monthly payments on the first day of each month, according to a RegularSchedule. If the mortgage does not start on the first day of a calendar month, then an initial ScheduleStub specifies the payment due for the DatePeriod up to the first day of the next calendar month. Similarly, a final ScheduleStub specifies the last payment due for the DatePeriod after the end of the last full calendar month. @@ -612,7 +613,7 @@ The recurrence start date can also be relative to the starting Date of the overa time of day explicit time, according to a clock - The representation similar to xsd:dateTime, but should exclude the date component and time zone. The value of the hasTimeValue property roughly corresponds to xsd:time in XML schema datatypes, which is prohibited from use in OWL due to ambiguity in its definition. Use of TimeOfDay with a business center would enable inferred time zone, using the hasBusinessCenter property from Business Dates. + The representation similar to xsd:dateTime, but should exclude the date component and time zone. The value of the hasTimeValue property roughly corresponds to xsd:time in XML schema datatypes, which is prohibited from use in OWL due to ambiguity in its definition. Use of TimeOfDay with a business center would enable inferred time zone, using the hasBusinessCenter property from Business Dates. diff --git a/FND/DatesAndTimes/Occurrences.rdf b/FND/DatesAndTimes/Occurrences.rdf index 103179f13..2beedb2d8 100644 --- a/FND/DatesAndTimes/Occurrences.rdf +++ b/FND/DatesAndTimes/Occurrences.rdf @@ -42,8 +42,8 @@ This ontology extends definitions of date and schedule concepts from the FinancialDates ontology with concepts defining occurrences (i.e., event-related concepts) for use in other FIBO ontologies. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2014-2021 EDM Council, Inc. - Copyright (c) 2014-2021 Object Management Group, Inc. + Copyright (c) 2014-2022 EDM Council, Inc. + Copyright (c) 2014-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/Arrangements/Arrangements/ https://spec.edmcouncil.org/fibo/ontology/FND/Arrangements/ClassificationSchemes/ https://spec.edmcouncil.org/fibo/ontology/FND/DatesAndTimes/BusinessDates/ @@ -63,21 +63,22 @@ - + The https://spec.edmcouncil.org/fibo/ontology/FND/20141101/DatesAndTimes/Occurrences/ version of this ontology was revised to address the issue resolutions in the FIBO 2.0 RFC, primarily to add properties that are relevant to the inputs and outputs from processes, events, systems and the like. The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/DatesAndTimes/Occurrences/ version of this ontology was revised to make use of the new composite date type added to Financial Dates. The https://spec.edmcouncil.org/fibo/ontology/FND/20190201/DatesAndTimes/Occurrences/ version of this ontology was revised to eliminate duplication of concepts in LCC, and eliminate unnecessary complexity in restrictions. The https://spec.edmcouncil.org/fibo/ontology/FND/20200701/DatesAndTimes/Occurrences/ version of this ontology was revised to eliminate the hasDescription property, which can easily supported using an annotation or isDescribedBy, depending on the situation, clarify the formal definition of occurrence kind, and correct circular and/or non-ISO 704 compliant definitions. The https://spec.edmcouncil.org/fibo/ontology/FND/20200901/DatesAndTimes/Occurrences/ version of this ontology was revised to fix spelling errors. - This ontology was added to Foundations in advance of the December 2014 Long Beach meeting in support of the SEC specification. It is also needed to provide temporal relationships for Ownership and Control. + The https://spec.edmcouncil.org/fibo/ontology/FND/20211201/DatesAndTimes/Occurrences/ version of this ontology was revised to address hygiene errors with respect to text formatting. + This ontology was added to Foundations in advance of the December 2014 Long Beach meeting in support of the SEC specification. It is also needed to provide temporal relationships for Ownership and Control. These three ontologies are designed for use together: - * FinancialDates -- financial Dates and Schedules - * BusinessDates -- business day adjustments - * Occurrences -- occurrences (events) and kinds of occurrences + * FinancialDates -- financial Dates and Schedules + * BusinessDates -- business day adjustments + * Occurrences -- occurrences (events) and kinds of occurrences -They are modularized this way to minimize the ontological committments that are imposed upon ontologies that rely upon them. Ontologies can import FinancialDates alone, or FinancialDates + BusinessDates, or FinancialDates + Occurrences, or all three together. +They are modularized this way to minimize the ontological committments that are imposed upon ontologies that rely upon them. Ontologies can import FinancialDates alone, or FinancialDates + BusinessDates, or FinancialDates + Occurrences, or all three together. @@ -187,7 +188,7 @@ They are modularized this way to minimize the ontological committments that are occurrence-based date calculated date that is defined with respect to the occurrence of some occurrence kind - The 'hasDateValue' property of an OccurrenceBasedDate is not set until the Occurrence happens. The 'triggeredBy' property relates an OccurrenceBasedDate to the OccurrenceKind that gives the meaning of the OccurrenceBasedDate. + The 'hasDateValue' property of an OccurrenceBasedDate is not set until the Occurrence happens. The 'triggeredBy' property relates an OccurrenceBasedDate to the OccurrenceKind that gives the meaning of the OccurrenceBasedDate. diff --git a/FND/GoalsAndObjectives/Objectives.rdf b/FND/GoalsAndObjectives/Objectives.rdf index 7a01c7eee..90ab8049f 100644 --- a/FND/GoalsAndObjectives/Objectives.rdf +++ b/FND/GoalsAndObjectives/Objectives.rdf @@ -29,11 +29,11 @@ Objectives Ontology - This ontology defines the concept of an objective, for use in other FIBO ontology elements. Objectives are defined as being distinct from goals, in that they constitute time limited and measurable targets which some entity may seek to attain in pursuit of its goals. + This ontology defines the concept of an objective, for use in other FIBO ontology elements. Objectives are defined as being distinct from goals, in that they constitute time limited and measurable targets which some entity may seek to attain in pursuit of its goals. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2013-2020 EDM Council, Inc. - Copyright (c) 2013-2020 Object Management Group, Inc. + Copyright (c) 2013-2022 EDM Council, Inc. + Copyright (c) 2013-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/DatesAndTimes/FinancialDates/ https://spec.edmcouncil.org/fibo/ontology/FND/Relations/Relations/ https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/ @@ -44,18 +44,19 @@ - + The http://www.omg.org/spec/FIBO/Foundations/20130601/GoalsAndObjectives/Objectives.owl version of the ontology was revised in advance of the September 2013 New Brunswick, NJ meeting, as follows: - (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing - (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs - (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools - (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure - (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations - (6) to eliminate an unnecessary hasObjectives property and related imports dependencies. + (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing + (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs + (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools + (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure + (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations + (6) to eliminate an unnecessary hasObjectives property and related imports dependencies. The https://spec.edmcouncil.org/fibo/ontology/FND/20130801/GoalsAndObjectives/Objectives.rdf version of this ontology was modified per the issue resolutions identified in the FIBO FND 1.0 FTF report and in https://spec.edmcouncil.org/fibo/ontology/FND/1.0/AboutFND-1.0/. The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/GoalsAndObjectives/Objectives.rdf version of this ontology was modified to integrate concepts such as investment objective, business objective, strategy, and related properties. The https://spec.edmcouncil.org/fibo/ontology/FND/20190401/GoalsAndObjectives/Objectives.rdf version of this ontology was modified to integrate concepts such as distribution and sales strategy, and to eliminate duplication of concepts in LCC. The https://spec.edmcouncil.org/fibo/ontology/FND/20200201/GoalsAndObjectives/Objectives.rdf version of this ontology was modified to add the concept of a program, required for IND but also to represent compliance, and other kinds of programs. + The https://spec.edmcouncil.org/fibo/ontology/FND/20201101/GoalsAndObjectives/Objectives.rdf version of this ontology was modified to address hygiene issues with respect to text formatting. diff --git a/FND/Law/Jurisdiction.rdf b/FND/Law/Jurisdiction.rdf index 9c40ad716..6819ca5ae 100644 --- a/FND/Law/Jurisdiction.rdf +++ b/FND/Law/Jurisdiction.rdf @@ -36,8 +36,8 @@ This ontology defines high level concepts relating to jurisdictions for use in other FIBO ontology elements. This includes a general definition of jurisdiction along with some basic types of jurisdiction, along with the factors which distinguish one type of jurisdiction from another. This ontology also defines basic types of legal system, and extends the basic concept of law which is in the LegalCore ontology.. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2013-2021 EDM Council, Inc. - Copyright (c) 2013-2021 Object Management Group, Inc. + Copyright (c) 2013-2022 EDM Council, Inc. + Copyright (c) 2013-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/AgentsAndPeople/People/ https://spec.edmcouncil.org/fibo/ontology/FND/Law/LegalCore/ https://spec.edmcouncil.org/fibo/ontology/FND/Parties/Parties/ @@ -52,19 +52,20 @@ - + The http://www.omg.org/spec/EDMC-FIBO/FND/20130801/Law/Jurisdiction.rdf version of the ontology was was modified per the issue resolutions identified in the FIBO FND 1.0 FTF report and in http://www.omg.org/spec/EDMC-FIBO/FND/1.0/AboutFND-1.0/. The http://www.omg.org/spec/EDMC-FIBO/FND/20141101/Law/Jurisdiction.rdf version of the ontology was was modified per the FIBO 2.0 RFC to integrate LCC. The http://www.omg.org/spec/FIBO/Foundations/20130601/Law/Jurisdiction.owl version of the ontology was revised in advance of the September 2013 New Brunswick, NJ meeting, as follows: - (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing - (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs - (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools - (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure - (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations - (6) to revise definitions using more formal sources. + (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing + (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs + (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools + (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure + (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations + (6) to revise definitions using more formal sources. The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/Law/Jurisdiction.rdf version of the ontology was modified to remove the constraint on jurisdiction that it is governed by some legal system, eliminate the class legal system and its children, which were very general and not used anywhere in FIBO, clean up remaining definitions with better sources, and eliminate an unused import. The https://spec.edmcouncil.org/fibo/ontology/FND/20200901/Law/Jurisdiction.rdf version of the ontology was modified to extend the concept of a tax identifier and identification scheme with the applicable jurisdiction. The https://spec.edmcouncil.org/fibo/ontology/FND/20201101/Law/Jurisdiction.rdf version of the ontology was modified to extend the concept of legal age with the applicable jurisdiction. + The https://spec.edmcouncil.org/fibo/ontology/FND/20210601/Law/Jurisdiction.rdf version of the ontology was modified to address hygiene issues with respect to text formatting. @@ -101,7 +102,7 @@ statutory law law enacted by a legislature https://www.law.cornell.edu/wex/statute - In the United States, statutes may also be called acts, such as the Civil Rights Act of 1964 or the Sarbanes-Oxley Act. Federal laws must be passed by both houses of Congress, the House of Representative and the Senate, and then usually require approval from the president before they can take effect. + In the United States, statutes may also be called acts, such as the Civil Rights Act of 1964 or the Sarbanes-Oxley Act. Federal laws must be passed by both houses of Congress, the House of Representative and the Senate, and then usually require approval from the president before they can take effect. Statutes may originate with national, state legislatures or local municipalities. Statutory laws are subordinate to the higher constitutional laws of the land. diff --git a/FND/Law/LegalCapacity.rdf b/FND/Law/LegalCapacity.rdf index 4521992a9..ab77e50f3 100644 --- a/FND/Law/LegalCapacity.rdf +++ b/FND/Law/LegalCapacity.rdf @@ -50,8 +50,8 @@ This ontology defines high-level legal concepts, especially those related to legal responsibilities, for use in other FIBO ontology elements. The ontology defines things which are conferred upon some entity by some legal instrument, and elaborates this into a number of specific capacities, responsibilities and powers, each of which forms the basis for many of the concepts used elsewhere in FIBO in defining legal personhood, executive powers and the like. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2013-2021 EDM Council, Inc. - Copyright (c) 2013-2021 Object Management Group, Inc. + Copyright (c) 2013-2022 EDM Council, Inc. + Copyright (c) 2013-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/Agreements/Agreements/ https://spec.edmcouncil.org/fibo/ontology/FND/Agreements/Contracts/ https://spec.edmcouncil.org/fibo/ontology/FND/Arrangements/Documents/ @@ -78,13 +78,13 @@ - + The http://www.omg.org/spec/FIBO/Foundations/20130601/Law/LegalCapacity.owl version of the ontology was revised in advance of the September 2013 New Brunswick, NJ meeting, as follows: - (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing - (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs - (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools - (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure - (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. + (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing + (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs + (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools + (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure + (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. The https://spec.edmcouncil.org/fibo/ontology/FND/20130801/Law/LegalCapacity.rdf version of the ontology was modified per the issue resolutions identified in the FIBO FND 1.0 FTF report. The https://spec.edmcouncil.org/fibo/ontology/FND/20141101/Law/LegalCapacity.rdf version of the ontology was modified per the FIBO FBC RFC, namely to add concepts to support license, licensee, and licensor to the ontology. The https://spec.edmcouncil.org/fibo/ontology/FND/20150801/Law/LegalCapacity.rdf version of the ontology was modified per the FIBO 1.1 RTF to add the concept of litigation capacity to the ontology. @@ -95,6 +95,7 @@ The https://spec.edmcouncil.org/fibo/ontology/FND/20200601/Law/LegalCapacity.rdf version of this ontology was modified to reflect the merge of Goals and Objectives. The https://spec.edmcouncil.org/fibo/ontology/FND/20201101/Law/LegalCapacity.rdf version of this ontology was modified to replace autonomous agent with independent party in property declarations. The https://spec.edmcouncil.org/fibo/ontology/FND/20210401/Law/LegalCapacity.rdf version of this ontology was modified to introduce 'right' as a kind of legal construct, move legal right, contractual right, and contingent right under right as siblings, and update their definitions as appropriate. + The https://spec.edmcouncil.org/fibo/ontology/FND/20211201/Law/LegalCapacity.rdf version of this ontology was modified to eliminate an unnecessary link. @@ -547,7 +548,6 @@ licenses issues a license required in order to perform some task, provide some service, exercise some privilege, or pursue some line of business or occupation to some party - http://www.merriam-webster.com/dictionary/regulate \ No newline at end of file diff --git a/FND/Law/LegalCore.rdf b/FND/Law/LegalCore.rdf index 98cd0700e..140603cd5 100644 --- a/FND/Law/LegalCore.rdf +++ b/FND/Law/LegalCore.rdf @@ -32,8 +32,8 @@ This ontology defines high-level legal concepts for use in other FIBO ontology elements. These concepts include law and constitution, both of which are framed at a more abstract level than national or state laws and constitutions, so that law forms the basis both for statutes and for company by-laws, and constitution forms the basis both for national or state constitutions and for instruments which are constitutive of incorporated legal entities. This ontology also defines some of the variants of these such as governmental constitutions and ordinances. Other types of law are provided in the Jurisdictions ontology as extensions of concepts in this ontology. Court of Law is also defined here. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2013-2021 EDM Council, Inc. - Copyright (c) 2013-2021 Object Management Group, Inc. + Copyright (c) 2013-2022 EDM Council, Inc. + Copyright (c) 2013-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/Organizations/FormalOrganizations/ https://spec.edmcouncil.org/fibo/ontology/FND/Relations/Relations/ https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/ @@ -44,18 +44,19 @@ - + The http://www.omg.org/spec/EDMC-FIBO/FND/20130801/Law/LegalCore.rdf version of the ontology was was modified per the issue resolutions identified in the FIBO FND 1.0 FTF report and in http://www.omg.org/spec/EDMC-FIBO/FND/1.0/AboutFND-1.0/. The http://www.omg.org/spec/EDMC-FIBO/FND/20141101/Law/LegalCore.rdf version of the ontology was was modified per the FIBO 2.0 RFC. The http://www.omg.org/spec/FIBO/Foundations/20130601/Law/LegalCore.owl version of the ontology was revised in advance of the September 2013 New Brunswick, NJ meeting, as follows: - (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing - (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs - (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools - (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure - (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. - (6) to revise some of the text definitions using more formal sources. + (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing + (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs + (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools + (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure + (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. + (6) to revise some of the text definitions using more formal sources. The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/Law/LegalCore.rdf version of the ontology was revised to correct the camel case name of hasInForce (was hasInforce). The https://spec.edmcouncil.org/fibo/ontology/FND/20200501/Law/LegalCore.rdf version of the ontology was revised to eliminate circular and ambiguous definitions, and simplify the ontology by eliminating unused concepts, including GovernmentalConstitution, Ordinance and narrowly defined and unused properties - constrains and isConstrainedBy. + The https://spec.edmcouncil.org/fibo/ontology/FND/20210101/Law/LegalCore.rdf version of the ontology was revised to address hygiene issues with respect to text formatting. @@ -82,7 +83,7 @@ law rule recognized by some community as regulating the behavior of its members and that it may enforce through the imposition of penalties - Law is a term which does not have a universally accepted definition. Certain laws are made by governments, specifically by their legislatures although the sense intended here is broader. The formation of laws themselves may be influenced by a constitution (written or unwritten) and the rights encoded therein. The law shapes politics, economics and society in countless ways and serves as a social mediator of relations between people. + Law is a term which does not have a universally accepted definition. Certain laws are made by governments, specifically by their legislatures although the sense intended here is broader. The formation of laws themselves may be influenced by a constitution (written or unwritten) and the rights encoded therein. The law shapes politics, economics and society in countless ways and serves as a social mediator of relations between people. diff --git a/FND/Organizations/FormalOrganizations.rdf b/FND/Organizations/FormalOrganizations.rdf index 258a4d0c7..c485ef4f6 100644 --- a/FND/Organizations/FormalOrganizations.rdf +++ b/FND/Organizations/FormalOrganizations.rdf @@ -39,9 +39,9 @@ Formal Organizations Ontology - This ontology defines the high level concept of formal organization for use in other FIBO ontology elements. It is purposefully underspecified to facilitate mapping to other formal organization ontologies, such as the emerging W3C formal organization ontology, or others defined for specific business and financial services standards. The concepts in this ontology extend those in the Organizations ontology. + This ontology defines the high level concept of formal organization for use in other FIBO ontology elements. It is purposefully underspecified to facilitate mapping to other formal organization ontologies, such as the emerging W3C formal organization ontology, or others defined for specific business and financial services standards. The concepts in this ontology extend those in the Organizations ontology. http://opensource.org/licenses/MIT - http://www.w3.org/standards/techs/owl#w3c_all + https://www.w3.org/TR/owl2-quick-reference/ Copyright (c) 2013-2022 EDM Council, Inc. Copyright (c) 2013-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/AgentsAndPeople/Agents/ @@ -63,17 +63,18 @@ - + The http://www.omg.org/spec/EDMC-FIBO/FND/20130801/Organizations/FormalOrganizations.rdf version of this ontology was modified per the issue resolutions identified in the FIBO FND 1.0 FTF report and in http://www.omg.org/spec/EDMC-FIBO/FND/1.0/AboutFND-1.0/. It was further revised in the FTF in advance of the Long Beach meeting, resulting in http://www.omg.org/spec/EDMC-FIBO/FND/20141101/Organizations/FormalOrganizations/. The http://www.omg.org/spec/EDMC-FIBO/FND/20141101/Organizations/FormalOrganizations.rdf version of this ontology was modified per the FIBO 2.0 RFC to integrate concepts from LCC. The http://www.omg.org/spec/FIBO/Foundations/20130601/Organizations/FormalOrganizations.owl version of the ontology was revised in advance of the September 2013 New Brunswick, NJ meeting, as follows: - (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing - (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs - (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools - (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure - (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. + (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing + (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs + (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools + (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure + (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/Organizations/FormalOrganizations.rdf version of this ontology was revised to loosen the constraints on the range of isDomiciledIn, allow for multiple values, update definitions to be ISO 704 compliant, and eliminate duplication with concepts in LCC. The https://spec.edmcouncil.org/fibo/ontology/FND/20200201/Organizations/FormalOrganizations.rdf version of this ontology was revised to incorporate the concept of employment, required to support regulatory reporting. + The https://spec.edmcouncil.org/fibo/ontology/FND/20220101/Organizations/FormalOrganizations.rdf version of this ontology was revised to address hygiene issues with respect to text formatting. @@ -136,7 +137,7 @@ employment situation representing the state of being employed, i.e., the relationship that holds between an employer and employee for some period of time - This definition does not include workers in contingent arrangements, such as independent contractors, leased employees, temporary employees, on-call workers, and others that do not have a direct contractual relationship with the employer. The distinction is important for legal reasons, particularly for regulatory reporting with respect to responsible parties such as corporate officers, lending officers, others authorized or licensed to perform certain tasks, and traders, for example. + This definition does not include workers in contingent arrangements, such as independent contractors, leased employees, temporary employees, on-call workers, and others that do not have a direct contractual relationship with the employer. The distinction is important for legal reasons, particularly for regulatory reporting with respect to responsible parties such as corporate officers, lending officers, others authorized or licensed to perform certain tasks, and traders, for example. In the broadest sense, employment is the situation in which someone is fully engaged in doing something that they want to do. From a FIBO perspective, however, employment is understood to be more specific. It is the relationship between two parties, evidenced by an implicit or explicit contract, in which work is compensated and in which one party, a legal person, typically a formal organization, acts as the employer and the other, typically a legally capable natural person, as the employee. @@ -212,7 +213,7 @@ indicates the principal place where an entity conducts business, such as where its headquarters is located - Corporate domicile refers to a place where a company's affairs are discharged. It is also typically the legal home of a corporation because the place is considered by law as the center of corporate affairs. In cases where a business has incorporated in one location for convenience, such as for taxation, legal, or regulatory purposes, but operates primarily in one or more other locations, domicile in FIBO refers to the operational location(s) rather than legal location. Many companies in the US have incorporated in the State of Delaware, for example, but do not have operational facilities in Delaware (or only have small offices there). + Corporate domicile refers to a place where a company's affairs are discharged. It is also typically the legal home of a corporation because the place is considered by law as the center of corporate affairs. In cases where a business has incorporated in one location for convenience, such as for taxation, legal, or regulatory purposes, but operates primarily in one or more other locations, domicile in FIBO refers to the operational location(s) rather than legal location. Many companies in the US have incorporated in the State of Delaware, for example, but do not have operational facilities in Delaware (or only have small offices there). diff --git a/FND/Organizations/Organizations.rdf b/FND/Organizations/Organizations.rdf index 72059fe08..279635512 100644 --- a/FND/Organizations/Organizations.rdf +++ b/FND/Organizations/Organizations.rdf @@ -39,11 +39,11 @@ Organizations Ontology - This ontology defines high-level concepts for organizations and related terms, for use in other FIBO ontology elements. It is purposefully underspecified to facilitate mapping to specific organization ontologies, such as the emerging W3C organization ontology, organization from a BMM or BPMN perspective, organization from a records management (RMS) perspective, and so forth. + This ontology defines high-level concepts for organizations and related terms, for use in other FIBO ontology elements. It is purposefully underspecified to facilitate mapping to specific organization ontologies, such as the emerging W3C organization ontology, organization from a BMM or BPMN perspective, organization from a records management (RMS) perspective, and so forth. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2013-2021 EDM Council, Inc. - Copyright (c) 2013-2021 Object Management Group, Inc. + Copyright (c) 2013-2022 EDM Council, Inc. + Copyright (c) 2013-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/AgentsAndPeople/Agents/ https://spec.edmcouncil.org/fibo/ontology/FND/GoalsAndObjectives/Objectives/ https://spec.edmcouncil.org/fibo/ontology/FND/Parties/Parties/ @@ -63,20 +63,21 @@ - + The http://www.omg.org/spec/EDMC-FIBO/FND/20160201/Organizations/Organizations.rdf version of this ontology was modified per the FIBO 2.0 RFC, to revise the definition of Organization per ISO 6523. The http://www.omg.org/spec/FIBO/Foundations/20130601/Organizations/Organizations.owl version of the ontology was revised in advance of the September 2013 New Brunswick, NJ meeting, as follows: - (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing - (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs - (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools - (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure - (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. + (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing + (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs + (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools + (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure + (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. The https://spec.edmcouncil.org/fibo/ontology/FND/20130801/Organizations/Organizations.rdf version of this ontology was modified per the issue resolutions identified in the FIBO FND 1.0 FTF report and in https://spec.edmcouncil.org/fibo/ontology/FND/1.0/AboutFND-1.0/. The https://spec.edmcouncil.org/fibo/ontology/FND/20141101/Organizations/Organizations.rdf version of this ontology was modified per the issue resolutions identified in the FIBO FND 1.1 RTF report, to revise a restriction on Organization to reference PhysicalAddress (vs. PostalAddress). The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/Organizations/Organizations.rdf version of this ontology was modified to revise the definition of Organization to broaden its scope to individuals that may or may not be people and eliminate duplication with concepts in LCC. The https://spec.edmcouncil.org/fibo/ontology/FND/20200201/Organizations/Organizations.rdf version of this ontology was modified to reflect the merge of Goals and Objectives. The https://spec.edmcouncil.org/fibo/ontology/FND/20201101/Organizations/Organizations.rdf version of this ontology was modified to allow the Organizations ontology to import Parties, rather than the other way around, to simplify the class hierarchy for ease of use in data mapping and alignment, including moving OrganizationMember from Parties to Organizations, and to add the basis for structured organization name representation. The https://spec.edmcouncil.org/fibo/ontology/FND/20210601/Organizations/Organizations.rdf version of this ontology was modified to to move basic organization sub-unit and identifier definitions to FND from BE due to their fundamental nature and reusability and add links to the W3C organization ontology to provide hints as to which classes in this ontology map to the W3C ontology. Note that mappings are approximate and thus we used seeAlso rather than OWL equivalence relations. + The https://spec.edmcouncil.org/fibo/ontology/FND/20211001/Organizations/Organizations.rdf version of this ontology was modified to address hygiene issues with respect to text formatting. diff --git a/FND/OwnershipAndControl/Control.rdf b/FND/OwnershipAndControl/Control.rdf index eb74f9d80..f51fe767c 100644 --- a/FND/OwnershipAndControl/Control.rdf +++ b/FND/OwnershipAndControl/Control.rdf @@ -35,11 +35,11 @@ Control Ontology - This ontology defines high-level, control-related concepts for use in other FIBO ontology elements. The ontology covers basic concepts around control, along with a distinction between de jure and de facto control, the former being derived with reference to terms in the LegalCapacity ontology. + This ontology defines high-level, control-related concepts for use in other FIBO ontology elements. The ontology covers basic concepts around control, along with a distinction between de jure and de facto control, the former being derived with reference to terms in the LegalCapacity ontology. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2013-2021 EDM Council, Inc. - Copyright (c) 2013-2021 Object Management Group, Inc. + Copyright (c) 2013-2022 EDM Council, Inc. + Copyright (c) 2013-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/DatesAndTimes/BusinessDates/ https://spec.edmcouncil.org/fibo/ontology/FND/DatesAndTimes/FinancialDates/ https://spec.edmcouncil.org/fibo/ontology/FND/Law/LegalCapacity/ @@ -56,18 +56,19 @@ - + The http://www.omg.org/spec/FIBO/Foundations/20130601/OwnershipAndControl/Control.owl version of the ontology was revised in advance of the September 2013 New Brunswick, NJ meeting, as follows: - (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing - (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs - (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools - (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure - (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. + (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing + (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs + (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools + (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure + (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. The https://spec.edmcouncil.org/fibo/ontology/FND/20130801/OwnershipAndControl/Control.rdf version of the ontology was was modified per the issue resolutions identified in the FIBO FND 1.0 FTF report and in https://spec.edmcouncil.org/fibo/ontology/FND/1.0/AboutFND-1.0/. The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/OwnershipAndControl/Control.rdf version of the ontology was modified to integrate the concept of a situation, situational roles, and corresponding relations with the definition of control and eliminate minimum cardinality of 1 restrictions. The https://spec.edmcouncil.org/fibo/ontology/FND/20200601/OwnershipAndControl/Control.rdf version of the ontology was modified to simplify control concepts and relations, complete the control patterns, and eliminate ambiguity in definitions. The https://spec.edmcouncil.org/fibo/ontology/FND/20201201/OwnershipAndControl/Control.rdf version of the ontology was modified to eliminate references to external dictionary sites that no longer resolve. The https://spec.edmcouncil.org/fibo/ontology/FND/20210101/OwnershipAndControl/Control.rdf version of the ontology was modified to incorporate the latest insights into how control relations should integrate with the control situation and to unwind confusion around the various properties used to represent aspects of control with respect to their domains and ranges. + The https://spec.edmcouncil.org/fibo/ontology/FND/20210401/OwnershipAndControl/Control.rdf version of the ontology was modified to address hygiene issues with respect to text formatting. diff --git a/FND/OwnershipAndControl/Ownership.rdf b/FND/OwnershipAndControl/Ownership.rdf index 880cb5b79..a1f025d15 100644 --- a/FND/OwnershipAndControl/Ownership.rdf +++ b/FND/OwnershipAndControl/Ownership.rdf @@ -36,8 +36,8 @@ This ontology defines high-level, ownership-related concepts for use in other FIBO ontology elements. These include the concept of owner, asset and ownership along with relationships between them whereby an asset is some thing owned by some owner. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2013-2021 EDM Council, Inc. - Copyright (c) 2013-2021 Object Management Group, Inc. + Copyright (c) 2013-2022 EDM Council, Inc. + Copyright (c) 2013-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/Parties/Parties/ https://spec.edmcouncil.org/fibo/ontology/FND/Parties/Roles/ https://spec.edmcouncil.org/fibo/ontology/FND/Relations/Relations/ @@ -50,19 +50,20 @@ - + The http://www.omg.org/spec/EDMC-FIBO/FND/20130801/OwnershipAndControl/Ownership.rdf version of the ontology was modified per the issue resolutions identified in the FIBO FND 1.0 FTF report and in http://www.omg.org/spec/EDMC-FIBO/FND/1.0/AboutFND-1.0/. The http://www.omg.org/spec/EDMC-FIBO/FND/20180801/OwnershipAndControl/Ownership.rdf version of the ontology was modified to revise the definition of Asset using the new CombinedDateTime datatype rather than xsd:dateTime to provide increased flexibility. The http://www.omg.org/spec/FIBO/Foundations/20130601/OwnershipAndControl/Ownership.owl version of the ontology was revised in advance of the September 2013 New Brunswick, NJ meeting, as follows: - (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing - (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs - (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools - (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure - (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. + (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing + (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs + (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools + (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure + (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. The https://spec.edmcouncil.org/fibo/ontology/FND/20190401/OwnershipAndControl/Ownership.rdf version of the ontology was modified to add definitions for tangible and intangible asset, etc., as needed for refinement of the concept of collateral and other loan-specific concepts. The https://spec.edmcouncil.org/fibo/ontology/FND/20200101/OwnershipAndControl/Ownership.rdf version of the ontology was modified to integrate the concept of a situation, situational roles, and corresponding relations with the definition of ownership, and eliminate minimum cardinality of 1 in restrictions. The https://spec.edmcouncil.org/fibo/ontology/FND/20200601/OwnershipAndControl/Ownership.rdf version of the ontology was modified to reflect the move of hasAquisitionDate from relations to financial dates and eliminate circular definitions. The https://spec.edmcouncil.org/fibo/ontology/FND/20200701/OwnershipAndControl/Ownership.rdf version of the ontology was modified to better align with revisions to the situation lattice. + The https://spec.edmcouncil.org/fibo/ontology/FND/20210401/OwnershipAndControl/Ownership.rdf version of the ontology was modified to address hygiene issues with respect to text formatting. @@ -100,7 +101,7 @@ identifiable, non-monetary asset that lacks physical substance Intangible assets may include intellectual property, patents, copyrights, trademarks, rights-of-way (easements), brands, organizational abilities (know-how), and data. - Intangible assets include assets that may involve a legal claim to some future benefit, typically a claim to future cash. Intangible assets have become an increasingly larger component of the valuation for all companies, from newer social media companies to even the most established and iconic manufacturers. + Intangible assets include assets that may involve a legal claim to some future benefit, typically a claim to future cash. Intangible assets have become an increasingly larger component of the valuation for all companies, from newer social media companies to even the most established and iconic manufacturers. @@ -143,7 +144,7 @@ tangible asset asset that is a physical, measurable resource, i.e., one that takes a physical form - Tangible assets include cash, cash equivalents and accounts receivables (AR), inventory, equipment, buildings and real estate, crops, and investments. Tangible assets such as art, furniture, stamps, gold, wine, toys and books of significant value may be included in an individual or organization's asset portfolio. + Tangible assets include cash, cash equivalents and accounts receivables (AR), inventory, equipment, buildings and real estate, crops, and investments. Tangible assets such as art, furniture, stamps, gold, wine, toys and books of significant value may be included in an individual or organization's asset portfolio. diff --git a/FND/OwnershipAndControl/OwnershipAndControl.rdf b/FND/OwnershipAndControl/OwnershipAndControl.rdf index 1240b4d81..d8c85d85b 100644 --- a/FND/OwnershipAndControl/OwnershipAndControl.rdf +++ b/FND/OwnershipAndControl/OwnershipAndControl.rdf @@ -34,8 +34,8 @@ This ontology brings the concepts of ownership and control together, in cases where the combined semantics are applicable, such as for a wholly owned subsidiary. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2013-2021 EDM Council, Inc. - Copyright (c) 2013-2021 Object Management Group, Inc. + Copyright (c) 2013-2022 EDM Council, Inc. + Copyright (c) 2013-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/OwnershipAndControl/Control/ https://spec.edmcouncil.org/fibo/ontology/FND/OwnershipAndControl/Ownership/ https://spec.edmcouncil.org/fibo/ontology/FND/Parties/Parties/ @@ -47,9 +47,10 @@ - + The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/OwnershipAndControl/OwnershipAndControl.rdf version of the ontology was modified to better integrate it with the situation pattern and eliminate circular definitions. The https://spec.edmcouncil.org/fibo/ontology/FND/20210201/OwnershipAndControl/OwnershipAndControl.rdf version of the ontology was modified to integrate the properties defined herein with the ownership and control patterns. + The https://spec.edmcouncil.org/fibo/ontology/FND/20211201/OwnershipAndControl/OwnershipAndControl.rdf version of the ontology was modified to address hygiene issues with respect to text formatting. This ontology was added to Foundations in advance of the December 2014 Long Beach meeting in support of the issue resolutions identified in the FIBO FND 1.0 FTF report and in https://spec.edmcouncil.org/fibo/ontology/FND/1.0/AboutFND-1.0/. @@ -85,7 +86,7 @@ directs and exercises authoritative or dominating influence over some thing that is also owned - basic rule: if x controls y and x owns y then x owns and controls y + basic rule: if x controls y and x owns y then x owns and controls y SWRL rule: controls(?x, ?y), owns(?x, ?y) -> ownsAndControls(?x, ?y) diff --git a/FND/Parties/Parties.rdf b/FND/Parties/Parties.rdf index 5e17a3032..2d29dba97 100644 --- a/FND/Parties/Parties.rdf +++ b/FND/Parties/Parties.rdf @@ -42,8 +42,8 @@ This ontology defines the high-level concepts of parties in roles, for use in other FIBO ontology elements. The concept of a party in a role describes some entity defined specifically in terms of some role which it performs in some formal contractual or transactional relationship. The ontology includes one or more basic party in role concepts. The ontology also includes one or more logical combinations of types of autonomous entity which may perform some of the party roles defined elsewhere in this ontology, such as the role of ownership. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2013-2021 EDM Council, Inc. - Copyright (c) 2013-2021 Object Management Group, Inc. + Copyright (c) 2013-2022 EDM Council, Inc. + Copyright (c) 2013-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/AgentsAndPeople/Agents/ https://spec.edmcouncil.org/fibo/ontology/FND/Arrangements/IdentifiersAndIndices/ https://spec.edmcouncil.org/fibo/ontology/FND/DatesAndTimes/BusinessDates/ @@ -64,17 +64,17 @@ - + The http://www.omg.org/spec/EDMC-FIBO/FND/20130801/Parties/Parties.rdf version of the ontology was was modified per the issue resolutions identified in the FIBO FND 1.0 FTF report and in https://spec.edmcouncil.org/fibo/ontology/FND/1.0/AboutFND-1.0/. The http://www.omg.org/spec/EDMC-FIBO/FND/20141101/Parties/Parties.rdf version of this ontology was revised as a part of the issue resolutions identified in the FIBO FND 1.1 RTF report to add a parent of hasDate to date properties. The http://www.omg.org/spec/EDMC-FIBO/FND/20160201/Parties/Parties.rdf version of this ontology was revised as a part of the FIBO 2.0 RFC to introduce disjointness axioms to aid users in understanding. The http://www.omg.org/spec/FIBO/Foundations/20130601/Roles/Parties.owl version of the ontology was revised in advance of the September 2013 New Brunswick, NJ meeting, as follows: - (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing - (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs - (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools - (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure - (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. - (6) to combine Parties, Party Roles, and Roles in a single, new, Parties module, combine Parties and Party Roles into a single ontology, and add an inverse for the hasParty property. + (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing + (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs + (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools + (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure + (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations. + (6) to combine Parties, Party Roles, and Roles in a single, new, Parties module, combine Parties and Party Roles into a single ontology, and add an inverse for the hasParty property. The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/Parties/Parties.rdf version of this ontology was revised to add semantics to the definition of independent party, making it a direct subclass of autonomous agent (rather than inferred only) and making person and organization direct subclasses (rather than inferred only). The https://spec.edmcouncil.org/fibo/ontology/FND/20190101/Parties/Parties.rdf version of this ontology was revised to add a relationship directly between parties and a party identifier and rename (migrate) the hasDefinition property to isDefinedIn to clarify intent. The https://spec.edmcouncil.org/fibo/ontology/FND/20190701/Parties/Parties.rdf version of this ontology was revised to eliminate duplication with the concepts in LCC. @@ -84,6 +84,7 @@ The https://spec.edmcouncil.org/fibo/ontology/FND/20200901/Parties/Parties.rdf version of this ontology was extended to add the concepts of tax identifier and tax identification scheme. The https://spec.edmcouncil.org/fibo/ontology/FND/20201101/Parties/Parties.rdf version of this ontology was revised to make hasRelatedPartyInRole symmetric and move hasMailingAddress from people to this ontology. The https://spec.edmcouncil.org/fibo/ontology/FND/20210301/Parties/Parties.rdf version of this ontology was revised to add the two remaining property chains to complete the lattice, from independent party to thing via the situation, to simplify the class hierarchy for improved understanding, data mapping and alignment, and to add the notion of a contextual name (i.e., a name for someone, some place or something that applies for some period of time in some context). + The https://spec.edmcouncil.org/fibo/ontology/FND/20210601/Parties/Parties.rdf version of this ontology was revised to address hygiene issues with respect to text formatting. @@ -113,7 +114,7 @@ contextual name designation by which someone, some place, or something is known in some context Names of people, places, and organizations often change over time, and may be used in a particular context, such as a DBA name for a business or legal name for a person. - Names for people may be considered to be personally identifying information (PII), especially when other details are also available. Specifying names as string values attached directly to an individual makes name reconciliation and management, including from a privacy perspective, more challenging. + Names for people may be considered to be personally identifying information (PII), especially when other details are also available. Specifying names as string values attached directly to an individual makes name reconciliation and management, including from a privacy perspective, more challenging. This class is designed to be extended to include provenance details regarding the source for a particular name as well as links to the various contexts in which it is used. diff --git a/FND/Places/Addresses.rdf b/FND/Places/Addresses.rdf index 297981318..7c0f5a972 100644 --- a/FND/Places/Addresses.rdf +++ b/FND/Places/Addresses.rdf @@ -40,8 +40,8 @@ This ontology provides high level definitions for addresses and address components including elements that are common to addressing standards. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2013-2021 EDM Council, Inc. - Copyright (c) 2013-2021 Object Management Group, Inc. + Copyright (c) 2013-2022 EDM Council, Inc. + Copyright (c) 2013-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/Arrangements/ClassificationSchemes/ https://spec.edmcouncil.org/fibo/ontology/FND/Arrangements/IdentifiersAndIndices/ https://spec.edmcouncil.org/fibo/ontology/FND/Places/Locations/ @@ -59,7 +59,7 @@ - + The http://www.omg.org/spec/EDMC-FIBO/FND/20141101/Places/Addresses.rdf version of this ontology was modified per the issue resolutions identified in the FIBO FND 1.1 RTF report. Differences from the 1.0 version include the addition of a hasAddress property and PhysicalAddress class as a parent of PostalAddress. The http://www.omg.org/spec/EDMC-FIBO/FND/20160201/Places/Addresses.rdf version of this ontology was modified for the FIBO 2.0 RFC to integrate LCC. The https://spec.edmcouncil.org/fibo/ontology/FND/20130801/Places/Addresses.rdf version of this ontology was modified per the issue resolutions identified in the FIBO FND 1.0 FTF report and in https://spec.edmcouncil.org/fibo/ontology/FND/1.0/AboutFND-1.0/. Primary differences include elimination of data properties in favor of a simple class model,the addition of virtual address, and the addition of addressing scheme. @@ -69,13 +69,14 @@ The https://spec.edmcouncil.org/fibo/ontology/FND/20200601/Places/Addresses.rdf version of this ontology was modified to eliminate unnecessary unions and max 1 restrictions. The https://spec.edmcouncil.org/fibo/ontology/FND/20200701/Places/Addresses.rdf version of this ontology was modified to revise names of address elements that could be construed as referring to multiple concepts. The https://spec.edmcouncil.org/fibo/ontology/FND/20210201/Places/Addresses.rdf version of this ontology was modified to make postcode a subclass of geographic region identifier and fix spelling errors. + The https://spec.edmcouncil.org/fibo/ontology/FND/20211201/Places/Addresses.rdf version of this ontology was modified to address hygiene issues with respect to text formatting. The https://spec.edmcouncil.org/fibo/ontology/Foundations/20130601/Organizations/Addresses.owl version of the ontology was revised in advance of the September 2013 New Brunswick, NJ meeting, as follows: - (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing - (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs - (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools - (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure - (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations - (6) to move this ontology from Organizations to Places and eliminate unnecessary properties and related imports dependencies. + (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing + (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs + (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools + (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure + (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations + (6) to move this ontology from Organizations to Places and eliminate unnecessary properties and related imports dependencies. @@ -309,7 +310,7 @@ physical address physical address where communications can be addressed, papers served or representatives located for any kind of organization or person - An address may be used as an index to the location of a building, apartment, office within an office block, or other structure or parcel of land, often using political boundaries and street names as references, along with other information such as house or building numbers or names. Some addresses also contain secondary elements such as apartment or building numbers, or special codes to aid routing of mail and packages. + An address may be used as an index to the location of a building, apartment, office within an office block, or other structure or parcel of land, often using political boundaries and street names as references, along with other information such as house or building numbers or names. Some addresses also contain secondary elements such as apartment or building numbers, or special codes to aid routing of mail and packages. Typically, addresses will have only one postcode expressed either as a string value or individual, and only a municipality (individual) or city (string value). diff --git a/FND/Places/Facilities.rdf b/FND/Places/Facilities.rdf index 5cc49d6e1..8479a2ffa 100644 --- a/FND/Places/Facilities.rdf +++ b/FND/Places/Facilities.rdf @@ -52,11 +52,12 @@ - + The http://www.omg.org/spec/EDMC-FIBO/FND/20141101/Places/Facilities.rdf version of this ontology was modified for the FIBO 2.0 RFC to integrate it with LCC. The http://www.omg.org/spec/EDMC-FIBO/FND/20180801/Places/Facilities.rdf version of this ontology was modified to eliminate deprecated elements. The http://www.omg.org/spec/EDMC-FIBO/FND/20190901/Places/Facilities.rdf version of this ontology was modified to eliminate circular and ambiguous definitions, and simplify the ontology by merging physical site with site. The http://www.omg.org/spec/EDMC-FIBO/FND/20210101/Places/Facilities.rdf version of this ontology was modified to allow a facility to exist at some location that has an address without requiring it to be situated at some site to simplify usage in cases where the site and facility have 100 percent overlap and are not tracked independently. + The http://www.omg.org/spec/EDMC-FIBO/FND/20220101/Places/Facilities.rdf version of this ontology was modified to address hygiene issues with respect to text formatting. This ontology was added to Foundations in advance of the December 2014 Long Beach meeting in support of the SEC specification. @@ -97,7 +98,7 @@ facility something established to serve a particular purpose, make some course of action or operation easier, or provide some capability or service - A facility may be concrete (as in a manufacturing facility) or abstract. Concrete facilities may be permanent, semi-permanent, or temporary structures, providing one or more capabilities at a given site. A single site may include multiple facilities and a given facility may span multiple sites. + A facility may be concrete (as in a manufacturing facility) or abstract. Concrete facilities may be permanent, semi-permanent, or temporary structures, providing one or more capabilities at a given site. A single site may include multiple facilities and a given facility may span multiple sites. diff --git a/FND/Places/Locations.rdf b/FND/Places/Locations.rdf index 950972391..18dd96b1d 100644 --- a/FND/Places/Locations.rdf +++ b/FND/Places/Locations.rdf @@ -25,22 +25,23 @@ Locations Ontology - This ontology provides a very high level definition of geographic region and geopolitical entity related concepts, including, but not limited to, countries, sub-country regions such as states and provinces, municipalities, etc., extending the Object Management Group (OMG)'s Languages, Countries, and Codes (LCC) ontologies as needed in FIBO. As such, these terms are automatically mapped to the LCC controlled vocabulary representing ISO 3166 country and country subdivision codes, and may be mapped to other de facto standards such as Geonames and the CIA World Factbook. The concept of a business center, defined herein, maps directly to the FpML concept with the same name, and to the set of business centers and broader municipalities included in ISO 10383, Codes for exchanges and market identification (MIC). + This ontology provides a very high level definition of geographic region and geopolitical entity related concepts, including, but not limited to, countries, sub-country regions such as states and provinces, municipalities, etc., extending the Object Management Group (OMG)'s Languages, Countries, and Codes (LCC) ontologies as needed in FIBO. As such, these terms are automatically mapped to the LCC controlled vocabulary representing ISO 3166 country and country subdivision codes, and may be mapped to other de facto standards such as Geonames and the CIA World Factbook. The concept of a business center, defined herein, maps directly to the FpML concept with the same name, and to the set of business centers and broader municipalities included in ISO 10383, Codes for exchanges and market identification (MIC). http://opensource.org/licenses/MIT - http://www.w3.org/standards/techs/owl#w3c_all - Copyright (c) 2013-2020 EDM Council, Inc. - Copyright (c) 2013-2020 Object Management Group, Inc. + https://www.w3.org/TR/owl2-quick-reference/ + Copyright (c) 2013-2022 EDM Council, Inc. + Copyright (c) 2013-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/ https://www.omg.org/spec/LCC/Countries/CountryRepresentation/ fibo-fnd-plc-loc Locations.rdf - + The http://www.omg.org/spec/EDMC-FIBO/FND/20130801/Places/Locations.rdf version of this ontology was modified per the issue resolutions identified in the FIBO FND 1.0 FTF report and in http://www.omg.org/spec/EDMC-FIBO/FND/1.0/AboutFND-1.0/. The http://www.omg.org/spec/EDMC-FIBO/FND/20141101/Places/Locations.rdf version of this ontology was modified for the FIBO 2.0 RFC to integrate it with LCC. The https://www.omg.org/spec/EDMC-FIBO/FND/20180801/Places/Locations.rdf version of this ontology was modified eliminate deprecated elements. The https://www.omg.org/spec/EDMC-FIBO/FND/20190901/Places/Locations.rdf version of this ontology was modified to revise definitions to improve them and make them ISO 704 compliant, and merge the concepts that were previously in the countries ontology into this one. + The https://www.omg.org/spec/EDMC-FIBO/FND/20200301/Places/Locations.rdf version of this ontology was modified to address hygiene issues with respect to text formatting. @@ -123,7 +124,7 @@ https://en.wikipedia.org/wiki/City https://www.gleif.org/en/about-lei/common-data-file-format/lei-cdf-format/lei-cdf-format-version-2-1 Typical working definitions for small-city populations start at around 100,000 people. Common population definitions for an urban area (city or town) range between 1,500 and 50,000 people, with most U.S states using a minimum between 1,500 and 5,000 inhabitants. Some jurisdictions set no such minima. - This property should be used in cases where a formal individual for the business center or municipality is not available. Note that Geonames could be used as a source in addition to FIBO, however, in cases where an individual is desired. Use the property fibo-fnd-plc-loc;hasMunicipality in cases where an individual is available. Also note that with respect to an address, this property may stand in for any village, town, or city of any size. + This property should be used in cases where a formal individual for the business center or municipality is not available. Note that Geonames could be used as a source in addition to FIBO, however, in cases where an individual is desired. Use the property fibo-fnd-plc-loc;hasMunicipality in cases where an individual is available. Also note that with respect to an address, this property may stand in for any village, town, or city of any size. diff --git a/FND/Places/NorthAmerica/USPostalServiceAddresses.rdf b/FND/Places/NorthAmerica/USPostalServiceAddresses.rdf index 75bffeabc..b28b313eb 100644 --- a/FND/Places/NorthAmerica/USPostalServiceAddresses.rdf +++ b/FND/Places/NorthAmerica/USPostalServiceAddresses.rdf @@ -33,12 +33,12 @@ U.S. Postal Service Addresses Ontology - This ontology augments the Addresses ontology in FND with concepts that conform to the USPS Pub 28. The USPS provides automated address verification services that use the concepts defined herein for that purpose, and which many financial services entities use for data quality purposes. + This ontology augments the Addresses ontology in FND with concepts that conform to the USPS Pub 28. The USPS provides automated address verification services that use the concepts defined herein for that purpose, and which many financial services entities use for data quality purposes. http://opensource.org/licenses/MIT - http://www.w3.org/standards/techs/owl#w3c_all + https://www.w3.org/TR/owl2-quick-reference/ Thematix Partners LLC - Copyright (c) 2019-2020 EDM Council, Inc. - Copyright (c) 2019-2020 Object Management Group, Inc. + Copyright (c) 2019-2022 EDM Council, Inc. + Copyright (c) 2019-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/Places/Addresses/ https://spec.edmcouncil.org/fibo/ontology/FND/Places/Locations/ https://spec.edmcouncil.org/fibo/ontology/FND/Relations/Relations/ @@ -54,8 +54,9 @@ - + The https://spec.edmcouncil.org/fibo/ontology/FND/20200301/Places/NorthAmerica/USPostalServiceAddresses.rdf version of this ontology was revised to replace uses of hasTag in Relations with hasTag from LCC, as the more complex union of datatypes in the Relations concept is not needed here, and correct a duplicate label. + The https://spec.edmcouncil.org/fibo/ontology/FND/20200701/Places/NorthAmerica/USPostalServiceAddresses.rdf version of this ontology was revised to address hygiene issues with respect to text formatting. @@ -222,7 +223,7 @@ delivery point code specific set of digits between 00 and 99 assigned to a delivery point - When combined with the ZIP + 4 code, the delivery point code provides a unique identifier for every deliverable address served by the USPS. The delivery point digits are almost never printed on mail in human-readable form; instead they are encoded in the POSTNET delivery point barcode (DPBC) or as part of the newer Intelligent Mail Barcode (IMB). + When combined with the ZIP + 4 code, the delivery point code provides a unique identifier for every deliverable address served by the USPS. The delivery point digits are almost never printed on mail in human-readable form; instead they are encoded in the POSTNET delivery point barcode (DPBC) or as part of the newer Intelligent Mail Barcode (IMB). @@ -426,7 +427,7 @@ overseas military address - delivery address whose delivery address line uses an abbreviation for the unit or command such as 'CMR', 'PSC', or 'UNIT', or 'HC', followed by the unit identifier, followed by 'BOX' followed by box number, in place of a street address, either 'APO' or 'FPO' as the literal value for the city and the appropriate armed forces subdivision code in place of a subdivision (state) code + delivery address whose delivery address line uses an abbreviation for the unit or command such as 'CMR', 'PSC', or 'UNIT', or 'HC', followed by the unit identifier, followed by 'BOX' followed by box number, in place of a street address, either 'APO' or 'FPO' as the literal value for the city and the appropriate armed forces subdivision code in place of a subdivision (state) code @@ -603,7 +604,7 @@ has urbanization - indicates area, sector, or development within a geographic area relevant to a delivery address + indicates area, sector, or development within a geographic area relevant to a delivery address \ No newline at end of file diff --git a/FND/Places/NorthAmerica/USPostalServiceAddressesIndividuals.rdf b/FND/Places/NorthAmerica/USPostalServiceAddressesIndividuals.rdf index 4a75b3617..046a75c66 100644 --- a/FND/Places/NorthAmerica/USPostalServiceAddressesIndividuals.rdf +++ b/FND/Places/NorthAmerica/USPostalServiceAddressesIndividuals.rdf @@ -39,10 +39,10 @@ U.S. Postal Service Addresses Individuals Ontology This ontology augments the U.S. Postal Service Address ontology with individuals for various street suffixes, military and U.S. Department of State specific individuals, and preferred designations for state and territory codes. http://opensource.org/licenses/MIT - http://www.w3.org/standards/techs/owl#w3c_all + https://www.w3.org/TR/owl2-quick-reference/ Thematix Partners LLC - Copyright (c) 2019-2020 EDM Council, Inc. - Copyright (c) 2019-2020 Object Management Group, Inc. + Copyright (c) 2019-2022 EDM Council, Inc. + Copyright (c) 2019-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/Places/NorthAmerica/USPostalServiceAddresses/ https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/ https://www.omg.org/spec/LCC/ @@ -58,7 +58,8 @@ - + + The https://spec.edmcouncil.org/fibo/ontology/FND/20200301/Places/NorthAmerica/USPostalServiceAddressesIndividuals.rdf version of this ontology was revised to update a dead link. diff --git a/FND/Places/VirtualPlaces.rdf b/FND/Places/VirtualPlaces.rdf index 7979dc936..842c30747 100644 --- a/FND/Places/VirtualPlaces.rdf +++ b/FND/Places/VirtualPlaces.rdf @@ -33,9 +33,9 @@ Virtual Places Ontology This ontology provides scaffolding for use in describing virtual location-oriented concepts. http://opensource.org/licenses/MIT - http://www.w3.org/standards/techs/owl#w3c_all - Copyright (c) 2013-2020 EDM Council, Inc. - Copyright (c) 2013-2020 Object Management Group, Inc. + https://www.w3.org/TR/owl2-quick-reference/ + Copyright (c) 2013-2022 EDM Council, Inc. + Copyright (c) 2013-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/Places/Addresses/ https://spec.edmcouncil.org/fibo/ontology/FND/Places/Locations/ https://spec.edmcouncil.org/fibo/ontology/FND/Relations/Relations/ @@ -49,9 +49,10 @@ - + The http://www.omg.org/spec/EDMC-FIBO/FND/20141101/Places/VirtualPlaces.rdf version of this ontology was modified for the FIBO 2.0 RFC to integrate it with LCC. The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/Places/VirtualPlaces.rdf version of this ontology was modified to eliminate duplication of concepts in LCC and email address and telephone number. + The https://spec.edmcouncil.org/fibo/ontology/FND/20200301/Places/VirtualPlaces.rdf version of this ontology was modified to address hygiene issues with respect to text formatting. This ontology was added to Foundations in advance of the December 2014 Long Beach meeting in support of the SEC specification. @@ -62,7 +63,7 @@ virtual address that defines an electronic messaging endpoint to which email messages can be delivered, typically via an Simple Mail Transfer Protocol (SMTP) based communications system e-mail address email address - Electronic mail, abbreviated e-mail or email, is a method of composing, sending, and receiving messages over electronic communication systems. The term e-mail applies both to the Internet e-mail system based on the Simple Mail Transfer Protocol (SMTP) and to intranet systems allowing users within one company or organization to send messages to each other. Often these workgroup collaboration systems natively use non-standard protocols but have some form of gateway to allow them to send and receive Internet e-mail. Some organizations may use the Internet protocols for internal e-mail service. + Electronic mail, abbreviated e-mail or email, is a method of composing, sending, and receiving messages over electronic communication systems. The term e-mail applies both to the Internet e-mail system based on the Simple Mail Transfer Protocol (SMTP) and to intranet systems allowing users within one company or organization to send messages to each other. Often these workgroup collaboration systems natively use non-standard protocols but have some form of gateway to allow them to send and receive Internet e-mail. Some organizations may use the Internet protocols for internal e-mail service. diff --git a/FND/Quantities/QuantitiesAndUnits.rdf b/FND/Quantities/QuantitiesAndUnits.rdf index 7a6367267..e496946f9 100644 --- a/FND/Quantities/QuantitiesAndUnits.rdf +++ b/FND/Quantities/QuantitiesAndUnits.rdf @@ -32,8 +32,8 @@ This ontology provides an initial set of concepts supporting the representation of quantities, units, systems of quantities, and systems of units for use in FIBO. It is compatible with and can be mapped directly to the OMG Date Time Vocabulary (DTV) Quantities Ontology, but has been integrated into FND to provide local coverage of quantities and measurements and eliminate the SBVR mark-up. http://opensource.org/licenses/MIT https://www.w3.org/TR/owl2-quick-reference/ - Copyright (c) 2015-2021 EDM Council, Inc. - Copyright (c) 2015-2021 Object Management Group, Inc. + Copyright (c) 2015-2022 EDM Council, Inc. + Copyright (c) 2015-2022 Object Management Group, Inc. https://spec.edmcouncil.org/fibo/ontology/FND/Arrangements/Arrangements/ https://spec.edmcouncil.org/fibo/ontology/FND/Arrangements/ClassificationSchemes/ https://spec.edmcouncil.org/fibo/ontology/FND/Relations/Relations/ @@ -46,13 +46,14 @@ - + The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/Quantities/QuantitiesAndUnits/ was modified to untangle this ontology from analytics, untangle quantity values (measurements) from measures and add refinements from SysML and ISO 11179, including dimensionality. The https://spec.edmcouncil.org/fibo/ontology/FND/20190501/Quantities/QuantitiesAndUnits/ was modified to rename (migrate) the hasDefinition property to isDefinedIn. The https://spec.edmcouncil.org/fibo/ontology/FND/20190701/Quantities/QuantitiesAndUnits/ was modified to eliminate deprecated properties. The https://spec.edmcouncil.org/fibo/ontology/FND/20190901/Quantities/QuantitiesAndUnits/ was modified to allow for dimensionless quantity kinds, including but not limited to percentages, and to eliminate duplication with concepts in LCC. The https://spec.edmcouncil.org/fibo/ontology/FND/20200201/Quantities/QuantitiesAndUnits/ was modified to eliminate the redundant definition of rate, in favor of ratio in Analytics. The https://spec.edmcouncil.org/fibo/ontology/FND/20200901/Quantities/QuantitiesAndUnits/ was modified to eliminate circular definitions. + The https://spec.edmcouncil.org/fibo/ontology/FND/20210201/Quantities/QuantitiesAndUnits/ was modified to address hygiene issues with respect to text formatting and eliminate dead links. @@ -67,8 +68,7 @@ base quantity quantity kind in a conventionally chosen subset of a given system of quantities, where no subset quantity can be expressed in terms of the others - The International System of Quantities (ISQ) comprises these base quantities (with their SI base measurement units): length (meter), mass (kilogram), duration (second), electric current (ampere), thermodynamic temperature (kelvin), amount of substance (mole), and luminous intensity (candela). These base quantities are not mutually comparable. All quantities of any one of these kinds are, however, mutually comparable. - http://www.omg.org/spec/DTV/1.1/ + The International System of Quantities (ISQ) comprises these base quantities (with their SI base measurement units): length (meter), mass (kilogram), duration (second), electric current (ampere), thermodynamic temperature (kelvin), amount of substance (mole), and luminous intensity (candela). These base quantities are not mutually comparable. All quantities of any one of these kinds are, however, mutually comparable. https://www.omg.org/spec/SysML/1.5/ @@ -76,7 +76,6 @@ base unit measurement unit that is defined by a system of units to be the reference measurement unit for a base quantity - http://www.omg.org/spec/DTV/1.1/ https://www.omg.org/spec/SysML/1.5/ Quantity units that are not base units are derived units. @@ -108,7 +107,6 @@ quantity kind that may be defined as a product of powers of one or more other kinds of quantity velocity (length/time), mass density (mass/length3) - http://www.omg.org/spec/DTV/1.1/ https://www.omg.org/spec/SysML/1.5/ A derived quantity may also be used to define a synonym kind of quantity for another kind of quantity. @@ -131,7 +129,6 @@ measurement unit that is defined with respect to one or more base units, such as as a product of powers of one or more other measurement units 1 minute = 60 seconds For example velocity can be specified as the product of length to the power one times time to the power minus one, and subsequently speed can be specified as velocity to the power one. - http://www.omg.org/spec/DTV/1.1/ https://www.omg.org/spec/SysML/1.5/ Every derived unit is defined in terms of base units. @@ -170,7 +167,6 @@ measurement unit quantity, defined and adopted by convention, with which any other quantity of the same kind can be compared to express the ratio of the two quantities as a number week, day, hour, minute, second, kilogram, joule, meter - http://www.omg.org/spec/DTV/1.1/ https://www.omg.org/spec/SysML/1.5/ A Unit is a quantity in terms of which the magnitudes of other quantities that have the same quantity kind can be stated. A unit often relies on precise and reproducible ways to measure the unit. For example, a unit of length such as meter may be specified as a multiple of a particular wavelength of light. A unit may also specify less stable or precise ways to express some value, such as a cost expressed in some currency, or a severity rating measured by a numerical scale. @@ -186,7 +182,6 @@ property of a phenomenon, body, or substance, to which a number can be assigned with respect to a reference The term quantity is used here to refer to the abstraction of the properties - the amount of measurable stuff that can be compared between particular quantities. The height of the something refers to a particular quantity; 555 ft 5 inches refers to a quantity value. second, kilogram, joule, meter. These are quantities in a general sense, which is what is meant here by quantity. - http://www.omg.org/spec/DTV/1.1/ https://www.omg.org/spec/SysML/1.5/ A quantity as defined here is said to be a "scalar" as distinct from a "vector." However, a vector or a tensor whose components are quantities is also considered to be a quantity. @@ -209,9 +204,8 @@ quantity kind classifier for 'quantity' that characterizes quantities as being mutually comparable - http://www.omg.org/spec/DTV/1.1/ https://www.omg.org/spec/SysML/1.5/ - A QuantityKind is a kind of quantity that may be stated by means of defined units. For example, the quantity kind of length may be measured by units of meters, kilometers, or feet. Note that this definition allows for dimensionless quantity kinds, such as rates. + A QuantityKind is a kind of quantity that may be stated by means of defined units. For example, the quantity kind of length may be measured by units of meters, kilometers, or feet. Note that this definition allows for dimensionless quantity kinds, such as rates. Every instance of 'quantity kind' is also a specialization of 'quantity'. So the concept 'duration' is an instance of 'quantity kind' and it is a specialization of 'quantity', i.e., it is a classifier of actual quantities. But a given duration (i.e., the duration of something) is an instance of 'duration' and thus a 'quantity value,' not an instance of 'quantity kind'. For example, a 'year' is not an instance of quantity kind; it is an instance of quantity, but not a category of quantity. @@ -254,9 +248,8 @@ quantity value number and measurement unit together giving magnitude of a quantity 2 days, 3.5 hours, 150 lb, 45.5 miles - http://www.omg.org/spec/DTV/1.1/ https://www.omg.org/spec/SysML/1.5/ - The quantity expressed by a quantity value is the quantity whose ratio to the measurement unit is the number. Note that dimensionless quantities may not have a measurement unit associated with them. + The quantity expressed by a quantity value is the quantity whose ratio to the measurement unit is the number. Note that dimensionless quantities may not have a measurement unit associated with them. measurement @@ -294,7 +287,6 @@ system of quantities set of quantities together with a set of non-contradictory equations relating those quantities The International System of Quantities (ISQ) is an example of a SystemOfQuantities, defined in ISO 31 and ISO/IEC 80000. - http://www.omg.org/spec/DTV/1.1/ https://www.omg.org/spec/SysML/1.5/ @@ -330,7 +322,6 @@ system of units set of measurement units associated with a system of quantities, together with a set of rules that assign one measurement unit to be the base unit for each base quantity in the system of quantities and a set of rules for the derivation of other units from the base units The International System of Units (SI) is a system of units. - http://www.omg.org/spec/DTV/1.1/ https://www.omg.org/spec/SysML/1.5/ diff --git a/FND/Relations/Relations.rdf b/FND/Relations/Relations.rdf index c8f0fdda8..666e49f5d 100644 --- a/FND/Relations/Relations.rdf +++ b/FND/Relations/Relations.rdf @@ -29,7 +29,7 @@ Relations Ontology - This ontology defines a set of general purpose relations for use in other FIBO ontology elements. These include a number of properties required for reuse across the foundations and business entities models. + This ontology defines a set of general purpose relations for use in other FIBO ontology elements. These include a number of properties required for reuse across the foundations and business entities models. http://opensource.org/licenses/MIT Copyright (c) 2013-2022 EDM Council, Inc. @@ -43,17 +43,17 @@ - + The http://www.omg.org/spec/EDMC-FIBO/FND/20170201/Relations/Relations.rdf version of this ontology was modified per the FIBO 2.0 RFC to include additional properties and the linkage to LCC. The http://www.omg.org/spec/FIBO/Foundations/20130601/Relations/Relations.owl version of the ontology submitted with the FIBO FND RFC, was revised in advance of the September 2013 New Brunswick, NJ meeting, as follows: - (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing - (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs - (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools - (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure - (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations - (6) to move the ontology from the Utilities module to an independent Relations module - (7) to revise a number of definitions, per discussion with various stakeholders. - (8) to augment the definitions to include entity names from Business Entities. + (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing + (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs + (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools + (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure + (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations + (6) to move the ontology from the Utilities module to an independent Relations module + (7) to revise a number of definitions, per discussion with various stakeholders. + (8) to augment the definitions to include entity names from Business Entities. The https://spec.edmcouncil.org/fibo/ontology/FND/20130801/Relations/Relations.rdf version of this ontology was revised to add the appliesTo object property in support of the IND RFC. The https://spec.edmcouncil.org/fibo/ontology/FND/20140501/Relations/Relations.rdf version of this ontology was modified per the issue resolutions identified in the FIBO FND 1.0 FTF report and in https://spec.edmcouncil.org/fibo/ontology/FND/1.0/AboutFND-1.0/. It was further revised in FTF 2 resulting in https://spec.edmcouncil.org/fibo/ontology/FND/20141101/Relations/Relations/. The https://spec.edmcouncil.org/fibo/ontology/FND/20141101/Relations/Relations.rdf version of this ontology was modified per the issue resolutions identified in the FIBO FND 1.2 RTF report. @@ -67,6 +67,7 @@ The https://spec.edmcouncil.org/fibo/ontology/FND/20201201/Relations/Relations.rdf version of this ontology was modified to clean up references to external dictionaries that don't meet FIBO policies, eliminate ambiguity where possible, eliminate the superproperties of produces and is produced by, whose semantics are different from their parent properties, and improve ISO 704 compliance of definitions. The https://spec.edmcouncil.org/fibo/ontology/FND/20210201/Relations/Relations.rdf version of this ontology was modified to add Reference as a superclass of Name and use the hasTextValue property as the superproperty of certain data properties. The https://spec.edmcouncil.org/fibo/ontology/FND/20210601/Relations/Relations.rdf version of this ontology was modified to remove the deprecated hasTag property. + The https://spec.edmcouncil.org/fibo/ontology/FND/20220401/Relations/Relations.rdf version of this ontology was modified to address hygiene issues with respect to text formatting. diff --git a/FND/Utilities/Analytics.rdf b/FND/Utilities/Analytics.rdf index 2c884345c..da85cbbfd 100644 --- a/FND/Utilities/Analytics.rdf +++ b/FND/Utilities/Analytics.rdf @@ -67,7 +67,7 @@ - + The https://spec.edmcouncil.org/fibo/ontology/FND/20140501/Utilities/Analytics.rdf version of this ontology was modified per the issue resolutions identified in the FIBO FND 1.0 FTF report and in https://spec.edmcouncil.org/fibo/ontology/FND/1.0/AboutFND-1.0/. The https://spec.edmcouncil.org/fibo/ontology/FND/20141101/Utilities/Analytics.rdf version of this ontology was modified to address issue FIBOFND11-20, which added the definition of Calculation and corrected a reasoning issue related to the use of a custom datatype. The https://spec.edmcouncil.org/fibo/ontology/FND/20160201/Utilities/Analytics.rdf version of this ontology was modified per the FIBO 2.0 RFC. @@ -83,6 +83,7 @@ The https://spec.edmcouncil.org/fibo/ontology/FND/20210201/Utilities/Analytics.rdf version of this ontology was modified to update the reference link for ratio. The https://spec.edmcouncil.org/fibo/ontology/FND/20210601/Utilities/Analytics.rdf version of this ontology was modified to expand the definition of release date and release date and time and to make a statistical area identifier a subclass of geographic region identifier. The https://spec.edmcouncil.org/fibo/ontology/FND/20211101/Utilities/Analytics.rdf version of this ontology was modified to eliminate unused imports. + The https://spec.edmcouncil.org/fibo/ontology/FND/20220101/Utilities/Analytics.rdf version of this ontology was modified to eliminate hygiene issues related to text formatting and eliminate dead or outdated references. This ontology was added to Foundations in advance of the June 2014 Boston meeting in support of the IND RFC. @@ -114,7 +115,7 @@ annualized standard deviation standard deviation for some measure over a specific reference period - Standard deviation applied to the annual rate of return of an investment provides insights on the historical volatility of that investment. The greater the standard deviation of the price of a security, the greater the volatility. Multiplying monthly standard deviation by the square root of twelve (12) is an industry standard method of approximating annualized standard deviations of monthly returns. + Standard deviation applied to the annual rate of return of an investment provides insights on the historical volatility of that investment. The greater the standard deviation of the price of a security, the greater the volatility. Multiplying monthly standard deviation by the square root of twelve (12) is an industry standard method of approximating annualized standard deviations of monthly returns. @@ -203,7 +204,7 @@ dispersion degree of scatter or variability shown by observations - Common examples of measures of statistical dispersion are the variance, standard deviation, and interquartile range. The collection size argument, above, represents the number of elements in the set, if known. The collection of values under consideration is represented as a structured collection in FIBO, typically a sample set derived from a finite population. + Common examples of measures of statistical dispersion are the variance, standard deviation, and interquartile range. The collection size argument, above, represents the number of elements in the set, if known. The collection of values under consideration is represented as a structured collection in FIBO, typically a sample set derived from a finite population. http://stats.oecd.org/glossary/detail.asp?ID=3637 A measure of statistical dispersion is a nonnegative real number that is zero if all the data are the same and increases as the data become more diverse. It is usually measured as an average deviation about some central value (e.g. mean deviation, standard deviation) or by an order statistic (e.g. quartile deviation, range) but may also be a mean of deviations of values among themselves (e.g. Gini's mean difference and also standard deviation). @@ -270,7 +271,6 @@ most common measure of central tendency; the average of a set of numbers http://www.statcan.gc.ca/edu/power-pouvoir/glossary-glossaire/5214842-eng.htm#m https://stats.oecd.org/glossary/detail.asp?ID=3762 - https://www.census.gov/glossary/#term_Mean When unqualified, the mean usually refers to the expectation of a variate, or to the arithmetic mean of a sample used as an estimate of the expectation. μ expected value @@ -297,7 +297,6 @@ median value of the variate dividing the total frequency of a data sample, population, or probability distribution, into two halves https://stats.oecd.org/glossary/detail.asp?ID=3717 - https://www.census.gov/glossary/#term_Median The basic advantage of the median in describing data compared to the mean is that it is not skewed by extremely large or small values, and may provide a better idea of a 'typical' value. This measure represents the middle value (if n is odd) or the average of the two middle values (if n is even) in an ordered list of data values. The median divides the total frequency distribution into two equal parts: one-half of the cases fall below the median and one-half of the cases exceed the median. @@ -455,7 +454,6 @@ SD http://www.statcan.gc.ca/edu/power-pouvoir/glossary-glossaire/5214842-eng.htm#s https://stats.oecd.org/glossary/detail.asp?ID=3845 - https://www.census.gov/glossary/#term_Standarddeviation The most widely used measure of dispersion of a frequency distribution introduced by K. Pearson (1893). It is equal to the positive square root of the variance. The standard deviation should not be confused with the root mean square deviation. While standard deviation is the most widely-used measure of spread, using squared deviations, it may not be the most robust. σ @@ -473,7 +471,6 @@ physical location that is defined per some program for designating geographic regions for the purposes of tabulating and presenting statistical data U.S. Bureau of Labor Statistics and Statistics Canada reference definitions - https://wiki.edmcouncil.org/display/IND/Statistics+Canada+Census+Information U.S. Bureau of Labor Statistics and Statistics Canada reference definitions - https://wiki.edmcouncil.org/pages/viewpage.action?pageId=6358041 - @@ -489,7 +486,6 @@ identifier for a physical location that is defined per a nationally consistent program for designating geographic regions for the purposes of tabulating and presenting statistical data U.S. Bureau of Labor Statistics and Statistics Canada reference definitions - https://wiki.edmcouncil.org/display/IND/Statistics+Canada+Census+Information U.S. Bureau of Labor Statistics and Statistics Canada reference definitions - https://wiki.edmcouncil.org/pages/viewpage.action?pageId=6358041 - @@ -619,8 +615,8 @@ weighting function expression or function that determines the relative importance or influence of a given element of a set with respect to the whole - Given a sample size of 1000, and a population of 300M, then the chance that any individual is selected is 1 in 300K. In that case, 300K is the weight assigned to each of the elements in the sample. -For certain indices, one of the most common weighting factor is by market capitalization. In that case, each of the elements in the basket is multiplied by its market cap to determine its relative importance to the basket overall. + Given a sample size of 1000, and a population of 300M, then the chance that any individual is selected is 1 in 300K. In that case, 300K is the weight assigned to each of the elements in the sample. + For certain indices, one of the most common weighting factor is by market capitalization. In that case, each of the elements in the basket is multiplied by its market cap to determine its relative importance to the basket overall. With respect to discrete calculations, weighting functions are positive functions defined on discrete sets, such as weighted sums and weighted averages. diff --git a/FND/Utilities/AnnotationVocabulary.rdf b/FND/Utilities/AnnotationVocabulary.rdf index 6aed5904f..54905f525 100644 --- a/FND/Utilities/AnnotationVocabulary.rdf +++ b/FND/Utilities/AnnotationVocabulary.rdf @@ -21,29 +21,29 @@ Annotation Vocabulary - This vocabulary provides a set of metadata annotations for use in describing FIBO ontology elements. The annotations extend properties defined in the OMG's Specification Metadata Recommendation, in the Dublin Core Metadata Terms Vocabulary and in the W3C Simple Knowledge Organization System (SKOS) Vocabulary, and have been customized to suit the FIBO specification development process. + This vocabulary provides a set of metadata annotations for use in describing FIBO ontology elements. The annotations extend properties defined in the OMG's Specification Metadata Recommendation, in the Dublin Core Metadata Terms Vocabulary and in the W3C Simple Knowledge Organization System (SKOS) Vocabulary, and have been customized to suit the FIBO specification development process. -Note that any of the original properties provided in Dublin Core and SKOS can be used in addition to the terms provided herein. However, any Dublin Core terms that are not explicitly defined as OWL annotation properties in this ontology or in any of its imports must be so declared in the ontologies that use them. +Note that any of the original properties provided in Dublin Core and SKOS can be used in addition to the terms provided herein. However, any Dublin Core terms that are not explicitly defined as OWL annotation properties in this ontology or in any of its imports must be so declared in the ontologies that use them. http://opensource.org/licenses/MIT - http://www.w3.org/standards/techs/owl#w3c_all - Copyright (c) 2013-2020 EDM Council, Inc. - Copyright (c) 2013-2020 Object Management Group, Inc. + https://www.w3.org/TR/owl2-quick-reference/ + Copyright (c) 2013-2022 EDM Council, Inc. + Copyright (c) 2013-2022 Object Management Group, Inc. fibo-fnd-utl-av AnnotationVocabulary.rdf - - + The http://www.omg.org/spec/EDMC-FIBO/FND/20130801/Utilities/AnnotationVocabulary.rdf version of this ontology was modified per the issue resolutions identified in the FIBO FND 1.0 FTF report and in http://www.omg.org/spec/EDMC-FIBO/FND/1.0/AboutFND-1.0/. The http://www.omg.org/spec/FIBO/Foundations/20130601/Utilities/AnnotationVocabulary.owl version of the ontology was revised in advance of the September 2013 New Brunswick, NJ meeting, as follows: - (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing - (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs - (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools - (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure - (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations + (1) to use slash style URI/IRIss (also called 303 URIs, vs. hash style) as required to support server side processing + (2) to use version-independent IRIs for all definitions internally as opposed to version-specific IRIs + (3) to change the file suffix from .owl to .rdf to increase usability in RDF tools + (4) to use 4-level abbreviations and corresponding namespace prefixes for all FIBO ontologies, reflecting a family/specification/module/ontology structure + (5) to incorporate changes to the specification metadata to support documentation at the family, specification, module, and ontology level, similar to the abbreviations The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/Utilities/AnnotationVocabulary.rdf version of this ontology was modified to add the symbol annotation. The https://spec.edmcouncil.org/fibo/ontology/FND/20190501/Utilities/AnnotationVocabulary.rdf version of this ontology was modified to eliminate deprecated properties. The https://spec.edmcouncil.org/fibo/ontology/FND/20190901/Utilities/AnnotationVocabulary.rdf version of this ontology was modified to add common and preferred designations as needed for postal addresses and other purposes, to correct named individuals to be properly declared, and to revise definitions to be ISO 704 compliant. The https://spec.edmcouncil.org/fibo/ontology/FND/20200301/Utilities/AnnotationVocabulary.rdf version of this ontology was modified to eliminate skos:Concept as a superclass of MaturityLevel (replaced with LifecycleStage in the Lifecycles ontology), revise explanatory notes for maturity levels based on community feedback, and correct the subproperty inheritance for adaptedFrom and logicalDefinition. + The https://spec.edmcouncil.org/fibo/ontology/FND/20200601/Utilities/AnnotationVocabulary.rdf version of this ontology was modified to address hygiene issues with respect to text formatting and eliminate the explicit SKOS import which is not needed.