"DEFINITIONs. rules and tasks" - Revision history

Ashkotin:
added

2026-04-09T18:46:17Z

added

Ashkotin: space lines eliminated

2026-04-09T16:00:05Z

space lines eliminated

Show changes

Ashkotin: version one

2026-03-28T12:52:08Z

version one

New page

This document is a collection of rules to keep a collection of definitions.

'''Abbreviations to use in collection'''

'''DiU''' - definition is unattainable. This means we have a URL to the source description, but not the definition itself there!

'''DB''' - database.

'''KB''' - knowledge base.

'''PID''' - person ID. There are two person roles: presenting his own definition xor presenting a reference to the source of the definition.

'''bref''' - bibliographic reference. If not full, keep "???".

Every definition has a unique ID and is a separate unit of knowledge. If the definition is personal, "!" follows after the ID.

If there is no direct link to the source in the form of a URL, the ID of the person who provided the definition is provided to ask. If the person created the definition himself, the definition's ID is followed by "!".

End letter "G" in definition ID means that the definition is IN GENERAL i.e. not only for IT.

'''General abbr'''

ITSM - IT Service Management refers to the entire lifecycle of designing, delivering, managing, and optimizing IT services for users. URL:???

__TOC__


== Rules to keep collection and discussion ==

Every definition is a unique unit of knowledge. In the collection, we keep attributes for reference to real where a definition does exist, reference to the author of it to ask and discuss.

Classification of definitions is a separate artefact with one or more authors involved. Ad should be kept out of the collection using a reference by collection ID of a definition.


=== (Rcf) canonical form of definition ===

We need canonical form when definition is embedded in text, but we need it separately.

See examples: [https://ontologforum.com/index.php/Ontology(IT)#canonical_form IT-ontology DEFINITIONs]


=== (Rca) collector action ===

The collector acts strictly formally: he transfers the author's definition from the original source in its entirety. If the text is transferred with modifications, the transferred part is enclosed in "". By finding this part in the source, anyone can verify that the changes only affected the form.


=== (Rdc) definition ''must be'' complete ===

From description to definition: It is usually easy to describe something preliminary, the definition must be complete.


=== (Roaod) one author one definition ===

There should be a very clear reason to keep more than one definition from an author in a collection.

''Example-1''. JA must consolidate all his definitions in one for every collection ([https://ontologforum.com/index.php/Knowledge_base#JA_group_of_definitions IT-knowledge base DEFINITIONs] [https://ontologforum.com/index.php/Ontology(IT)#JA_group_of_definitions IT-ontology DEFINITIONs]). Part of these definitions are descriptions, maybe all of them. And only JA can do this consolidation.

Presumably every of five his current definitions of ontology must be derived from a consolidated one.

For example consider we think that JA004 is the consolidation then we reason:

If JA004 then JA001.

i.e.

If X is a knowledge base whose artifacts constitute explicit axioms about domain entities and relations, expressed in a language with formal declarative semantics.

THEN

X is a formal semantic model enabling logical inference.


=== (do-topic)2the_[https://ontologforum.com/index.php/WikiHomePage site] ===

AS2KB\4.4.2026:Once the document is stabilized, I think we'll need to discuss how to publish its information on the website. A radical idea is to have each definition on a separate page. And some overview pages, too. Furthermore, it's unclear whether we should have a section in the left-hand menu, for example, called Dictionary.

There's a problem with definitions proposed by a specific individual: they shouldn't change them once they're published. It's their opinion at a given moment, which they've decided to publish. But they can, of course, publish a new definition. We need to develop rules for publishing and maintaining definitions on the website.

So we have an article about KB, and a collection of definitions.

For me, the most valuable thing is the collection.


== Person IDs ==

in ABC order.


=== AS Alex Shkotin ===

[mailto:ashkotin@acm.org Alex Shkotin]

Independent Computer Scientist

[https://www.linkedin.com/in/ashkotin/ Linkedin] ∘ [https://www.researchgate.net/profile/Alex-Shkotin RGate] ∘ [https://mipt.academia.edu/AlexShkotin Academia.edu]

[https://ontologforum.com/ Ontolog] BoT


=== BL Ben Lutkevich ===

[https://www.techtarget.com/contributor/Ben-Lutkevich https://www.techtarget.com/contributor/Ben-Lutkevich]


=== JA John Antill ===

MS KM, MCKM, CKS IA & KT, KCS

MS AI Student at Purdue

256-541-1229

[mailto:djanteater@gmail.com djanteater@gmail.com]


=== KB Ken Baclawski ===

[https://ontologforum.com/index.php/KenBaclawski https://ontologforum.com/index.php/KenBaclawski]

[[Category:Definition]]

← Older revision		Revision as of 18:46, 9 April 2026
Line 1:		Line 1:
	This document is a collection of rules to keep a collection of definitions.		This document is a collection of rules to keep a collection of definitions.
	'''Abbreviations to use in collection'''		<br>'''Abbreviations to use in collection'''
	'''DiU''' - definition is unattainable. This means we have a URL to the source description, but not the definition itself there!		<br>'''DiU''' - definition is unattainable. This means we have a URL to the source description, but not the definition itself there!
	'''DB''' - database.		<br>'''DB''' - database.
	'''KB''' - knowledge base.		<br>'''KB''' - knowledge base.
	'''PID''' - person ID. There are two person roles: presenting his own definition xor presenting a reference to the source of the definition.		<br>'''PID''' - person ID. There are two person roles: presenting his own definition xor presenting a reference to the source of the definition.
	'''bref''' - bibliographic reference. If not full, keep "???".		<br>'''bref''' - bibliographic reference. If not full, keep "???".
	Every definition has a unique ID and is a separate unit of knowledge. If the definition is personal, "!" follows after the ID.		<br>Every definition has a unique ID and is a separate unit of knowledge. If the definition is personal, "!" follows after the ID.
	If there is no direct link to the source in the form of a URL, the ID of the person who provided the definition is provided to ask. If the person created the definition himself, the definition's ID is followed by "!".		<br>If there is no direct link to the source in the form of a URL, the ID of the person who provided the definition is provided to ask. If the person created the definition himself, the definition's ID is followed by "!".
	End letter "G" in definition ID means that the definition is IN GENERAL i.e. not only for IT.		<br>End letter "G" in definition ID means that the definition is IN GENERAL i.e. not only for IT.
	'''General abbr'''		<br>'''General abbr'''
	ITSM - IT Service Management refers to the entire lifecycle of designing, delivering, managing, and optimizing IT services for users. URL:???		<br>ITSM - IT Service Management refers to the entire lifecycle of designing, delivering, managing, and optimizing IT services for users. URL:???

	__TOC__		__TOC__
Line 16:		Line 16:
	<span id="rules-to-keep-collection-and-discussion"></span>		<span id="rules-to-keep-collection-and-discussion"></span>
	== Rules to keep collection and discussion ==		== Rules to keep collection and discussion ==
	Every definition is a unique unit of knowledge. In the collection, we keep attributes for reference to real where a definition does exist, reference to the author of it to ask and discuss.		Every definition is a unique unit of knowledge. In the collection, we keep attributes for reference to real where a definition does exist, reference to the author of it to ask and discuss.
	Classification of definitions is a separate artefact with one or more authors involved. Ad should be kept out of the collection using a reference by collection ID of a definition.		<br>Classification of definitions is a separate artefact with one or more authors involved. Ad should be kept out of the collection using a reference by collection ID of a definition.

	<span id="rcf-canonical-form-of-definition"></span>		<span id="rcf-canonical-form-of-definition"></span>
	=== (Rcf) canonical form of definition ===		=== (Rcf) canonical form of definition ===
	We need canonical form when definition is embedded in text, but we need it separately.		We need canonical form when definition is embedded in text, but we need it separately.
	See examples: [https://ontologforum.com/index.php/Ontology(IT)#canonical_form <u>IT-ontology DEFINITIONs</u>]		<br>See examples: [https://ontologforum.com/index.php/Ontology(IT)#canonical_form <u>IT-ontology DEFINITIONs</u>]

	<span id="rca-collector-action"></span>		<span id="rca-collector-action"></span>
	=== (Rca) collector action ===		=== (Rca) collector action ===
	The collector acts strictly formally: he transfers the author's definition from the original source in its entirety. If the text is transferred with modifications, the transferred part is enclosed in "". By finding this part in the source, anyone can verify that the changes only affected the form.		The collector acts strictly formally: he transfers the author's definition from the original source in its entirety. If the text is transferred with modifications, the transferred part is enclosed in "". By finding this part in the source, anyone can verify that the changes only affected the form.

	<span id="rdc-definition-must-be-complete"></span>		<span id="rdc-definition-must-be-complete"></span>
	=== (Rdc) definition ''must be'' complete ===		=== (Rdc) definition ''must be'' complete ===
	From description to definition: It is usually easy to describe something preliminary, the definition must be complete.		From description to definition: It is usually easy to describe something preliminary, the definition must be complete.

	<span id="roaod-one-author-one-definition"></span>		<span id="roaod-one-author-one-definition"></span>
	=== (Roaod) one author one definition ===		=== (Roaod) one author one definition ===
	There should be a very clear reason to keep more than one definition from an author in a collection.		There should be a very clear reason to keep more than one definition from an author in a collection.
	''Example-1''. JA must consolidate all his definitions in one for every collection ([https://ontologforum.com/index.php/Knowledge_base#JA_group_of_definitions <u>IT-knowledge base DEFINITIONs</u>] [https://ontologforum.com/index.php/Ontology(IT)#JA_group_of_definitions <u>IT-ontology DEFINITIONs</u>]). Part of these definitions are descriptions, maybe all of them. And only JA can do this consolidation.		<br>''Example-1''. JA must consolidate all his definitions in one for every collection ([https://ontologforum.com/index.php/Knowledge_base#JA_group_of_definitions <u>IT-knowledge base DEFINITIONs</u>] [https://ontologforum.com/index.php/Ontology(IT)#JA_group_of_definitions <u>IT-ontology DEFINITIONs</u>]). Part of these definitions are descriptions, maybe all of them. And only JA can do this consolidation.
	Presumably every of five his current definitions of ontology must be derived from a consolidated one.		<br>Presumably every of five his current definitions of ontology must be derived from a consolidated one.
	For example consider we think that JA004 is the consolidation then we reason:		<br>For example consider we think that JA004 is the consolidation then we reason:
	If JA004 then JA001.		<br>If JA004 then JA001.
	i.e.		<br>i.e.
	If X is a knowledge base whose artifacts constitute explicit axioms about domain entities and relations, expressed in a language with formal declarative semantics.		<br>If X is a knowledge base whose artifacts constitute explicit axioms about domain entities and relations, expressed in a language with formal declarative semantics.
	THEN		<br>THEN
	X is a formal semantic model enabling logical inference.		<br>X is a formal semantic model enabling logical inference.

	<span id="do-topic2the_site"></span>		<span id="do-topic2the_site"></span>
	=== (do-topic)2the_[https://ontologforum.com/index.php/WikiHomePage <u>site</u>] ===		=== (do-topic)2the_[https://ontologforum.com/index.php/WikiHomePage <u>site</u>] ===
	AS2KB\4.4.2026:Once the document is stabilized, I think we'll need to discuss how to publish its information on the website. A radical idea is to have each definition on a separate page. And some overview pages, too. Furthermore, it's unclear whether we should have a section in the left-hand menu, for example, called Dictionary.		AS2KB\4.4.2026:Once the document is stabilized, I think we'll need to discuss how to publish its information on the website. A radical idea is to have each definition on a separate page. And some overview pages, too. Furthermore, it's unclear whether we should have a section in the left-hand menu, for example, called Dictionary.
	There's a problem with definitions proposed by a specific individual: they shouldn't change them once they're published. It's their opinion at a given moment, which they've decided to publish. But they can, of course, publish a new definition. We need to develop rules for publishing and maintaining definitions on the website.		<br>There's a problem with definitions proposed by a specific individual: they shouldn't change them once they're published. It's their opinion at a given moment, which they've decided to publish. But they can, of course, publish a new definition. We need to develop rules for publishing and maintaining definitions on the website.
	So we have an article about KB, and a collection of definitions.		<br>So we have an article about KB, and a collection of definitions.
	For me, the most valuable thing is the collection.		<br>For me, the most valuable thing is the collection.

	<span id="person-ids"></span>		<span id="person-ids"></span>
Line 57:		Line 57:
	<span id="as-alex-shkotin"></span>		<span id="as-alex-shkotin"></span>
	=== AS Alex Shkotin ===		=== AS Alex Shkotin ===
	[mailto:ashkotin@acm.org <u>Alex Shkotin</u>]		[mailto:ashkotin@acm.org <u>Alex Shkotin</u>]
	Independent Computer Scientist		<br>Independent Computer Scientist
	[https://www.linkedin.com/in/ashkotin/ <u>Linkedin</u>] ∘ [https://www.researchgate.net/profile/Alex-Shkotin <u>RGate</u>] ∘ [https://mipt.academia.edu/AlexShkotin <u>Academia.edu</u>]		<br>[https://www.linkedin.com/in/ashkotin/ <u>Linkedin</u>] ∘ [https://www.researchgate.net/profile/Alex-Shkotin <u>RGate</u>] ∘ [https://mipt.academia.edu/AlexShkotin <u>Academia.edu</u>]
	[https://ontologforum.com/ <u>Ontolog</u>] BoT		<br>[https://ontologforum.com/ <u>Ontolog</u>] BoT

	<span id="bl-ben-lutkevich"></span>		<span id="bl-ben-lutkevich"></span>
Line 68:		Line 68:
	<span id="ja-john-antill"></span>		<span id="ja-john-antill"></span>
	=== JA John Antill ===		=== JA John Antill ===
	MS KM, MCKM, CKS IA & KT, KCS		MS KM, MCKM, CKS IA & KT, KCS
	MS AI Student at Purdue		<br>MS AI Student at Purdue
	256-541-1229		<br>256-541-1229
	[mailto:djanteater@gmail.com <u>djanteater@gmail.com</u>]		<br>[mailto:djanteater@gmail.com <u>djanteater@gmail.com</u>]

	<span id="kb-ken-baclawski"></span>		<span id="kb-ken-baclawski"></span>

"DEFINITIONs. rules and tasks" - Revision history

Ashkotin: added

Ashkotin: space lines eliminated

Ashkotin: version one

Ashkotin:
added