Difference between revisions of "Extending SiDIF"

From BITPlan cr Wiki
Jump to navigation Jump to search
Line 5: Line 5:
  
 
=== Natural Language Statement ===
 
=== Natural Language Statement ===
 +
The simplest form of a statement contains:
 +
* subject
 +
* predicate
 +
* object
 +
 +
Example:
 
<syntaxhighlight lang="text">
 
<syntaxhighlight lang="text">
 
dad loves mom
 
dad loves mom
 
</syntaxhighlight>
 
</syntaxhighlight>
This represents the most basic, human-readable form of a statement. It contains:
 
* subject (dad)
 
* predicate (loves)
 
* object (mom)
 
  
 
=== Semantic Web Identifiers ===
 
=== Semantic Web Identifiers ===
Line 20: Line 22:
  
 
https://www.wikidata.org/wiki/Q76 https://www.wikidata.org/wiki/Property:P26 https://www.wikidata.org/wiki/Q13133
 
https://www.wikidata.org/wiki/Q76 https://www.wikidata.org/wiki/Property:P26 https://www.wikidata.org/wiki/Q13133
 
Now each part has a unique identifier in the semantic web space. The first version shows the raw syntax, while the second version shows the actual linked URIs.
 
  
 
=== Human-Readable with Links ===
 
=== Human-Readable with Links ===
Line 29: Line 29:
  
 
[https://www.wikidata.org/wiki/Q76 Barack Obama] [https://www.wikidata.org/wiki/Property:P26 spouse] [https://www.wikidata.org/wiki/Q13133 Michelle Obama]
 
[https://www.wikidata.org/wiki/Q76 Barack Obama] [https://www.wikidata.org/wiki/Property:P26 spouse] [https://www.wikidata.org/wiki/Q13133 Michelle Obama]
 
Combines human readability with semantic web identifiers.
 
  
 
== Current SiDIF Reference Mechanism ==
 
== Current SiDIF Reference Mechanism ==
  
 
=== Using 'it' Keyword ===
 
=== Using 'it' Keyword ===
 +
The 'it' keyword refers to the subject of the previous statement:
 +
 
<syntaxhighlight lang="text">
 
<syntaxhighlight lang="text">
 
dad loves mom
 
dad loves mom
 
https://www.wikidata.org/wiki/Q76 is wikidata_url of it
 
https://www.wikidata.org/wiki/Q76 is wikidata_url of it
 
</syntaxhighlight>
 
</syntaxhighlight>
'it' refers to the subject of the previous statement, bridging Object-Oriented concepts (this/self) with semantic web references.
 
  
 
=== Proposed Extension for Statement Parts ===
 
=== Proposed Extension for Statement Parts ===
 +
References to different parts of statements:
 +
 
<syntaxhighlight lang="text">
 
<syntaxhighlight lang="text">
 
https://www.wikidata.org/wiki/Q76 is wikidata_url of subject
 
https://www.wikidata.org/wiki/Q76 is wikidata_url of subject
Line 47: Line 48:
 
https://www.wikidata.org/wiki/Q13133 is wikidata_url of object
 
https://www.wikidata.org/wiki/Q13133 is wikidata_url of object
 
</syntaxhighlight>
 
</syntaxhighlight>
Allows referencing any part of the previous statement.
 
  
 
== Core Concepts and Bridging ==
 
== Core Concepts and Bridging ==
  
 
=== Fundamental Elements ===
 
=== Fundamental Elements ===
<syntaxhighlight lang="text">
+
* Core elements:
Entity - Object
+
** Entity - Object
Link - relation between two objects
+
** Link - relation between two objects
</syntaxhighlight>
+
 
These map to both OO and Semantic Web paradigms:
+
* Paradigm mappings:
* OO: Objects and their relationships
+
** OO: Objects and their relationships
* Semantic Web: Resources and their properties
+
** Semantic Web: Resources and properties
 +
 
 +
=== Technology Integration ===
 +
Example of technology bindings:
  
=== Technology Integration Example ===
 
 
<syntaxhighlight lang="text">
 
<syntaxhighlight lang="text">
 
Person isA Concept
 
Person isA Concept
 
# Technology binding options
 
 
Person_Sparql is sparql_impl of subject
 
Person_Sparql is sparql_impl of subject
 
http://foaf/... is prefix_url of subject
 
http://foaf/... is prefix_url of subject
Line 76: Line 76:
  
 
=== Description Logic Basis ===
 
=== Description Logic Basis ===
OWL/Description Logic components:
+
* Components:
* Concepts (Classes)
+
** Concepts (Classes)
* Roles (Properties)
+
** Roles (Properties)
* Individuals (Instances)
+
** Individuals (Instances)
  
 
=== RDF/OWL Mappings ===
 
=== RDF/OWL Mappings ===
 +
Class hierarchy and instance relationships:
 +
 
<syntaxhighlight lang="text">
 
<syntaxhighlight lang="text">
# Class hierarchy
+
Concept subClassOf owl:Thing
Concept subClassOf owl:Thing   # Top concept (T with bar)
+
owl:Nothing
owl:Nothing                     # Bottom concept (inverted T)
+
Barack rdfType Person
 
 
# Instance relationship
 
Barack rdfType Person         # Individual -> Class relationship
 
 
</syntaxhighlight>
 
</syntaxhighlight>
  
Line 94: Line 93:
  
 
=== Reference Keywords Options ===
 
=== Reference Keywords Options ===
# Full form: subject/predicate/object
+
* Full form approach:
# Short form: s/p/o
+
** subject for the entity being described
# Alternative: subject/link/object
+
** predicate for the relationship
 +
** object for the target entity
 +
* Short form approach:
 +
** s for subject
 +
** p for predicate
 +
** o for object
 +
* Alternative approach:
 +
** subject for entity
 +
** link for relationship
 +
** object for target
  
 
=== Key Bridging Concepts ===
 
=== Key Bridging Concepts ===
 
* 'it' semantics bridges:
 
* 'it' semantics bridges:
** OO: self/this/me
+
** OO: self/this/me concepts
** Semantic Web: subject reference
+
** Semantic Web: subject references
* Statement part references enable:
+
* Statement part references support:
 
** Metadata about relationships
 
** Metadata about relationships
 
** Integration with semantic web identifiers
 
** Integration with semantic web identifiers
Line 108: Line 116:
  
 
=== Relationship Considerations ===
 
=== Relationship Considerations ===
 +
* 1:n relations characteristics:
 +
** Enables flexible technology bindings
 +
** Increases system complexity
 +
** Requires careful management
 +
 +
Example of 1:n relation expression:
 +
 
<syntaxhighlight lang="text">
 
<syntaxhighlight lang="text">
# 1:n relations bring:
 
# Good: Flexibility for different tech bindings
 
# Challenge: Increased complexity
 
 
Person_Sparql is sparql_impl of subject
 
Person_Sparql is sparql_impl of subject
 
foaf is prefix of subject
 
foaf is prefix of subject
 
</syntaxhighlight>
 
</syntaxhighlight>
 +
 +
[[Category:SiDIF]]
 +
[[Category:Semantic Web]]
 +
[[Category:Knowledge Representation]]

Revision as of 10:56, 28 January 2025

⚠️ LLM-generated content notice: Parts of this page may have been created or edited with the assistance of a large language model (LLM). The prompts that have been used might be on the page itself, the discussion page or in straight forward cases the prompt was just "Write a mediawiki page on X" with X being the page name. While the content has been reviewed it might still not be accurate or error-free. - by asking Claude AI to format and explain Talk:Extending_SiDIF

SiDIF Extension Proposal

Statement Representations and Evolution

Natural Language Statement

The simplest form of a statement contains:

  • subject
  • predicate
  • object

Example:

dad loves mom

Semantic Web Identifiers

The same triple structure with Wikidata URLs:

https://www.wikidata.org/wiki/Q76 https://www.wikidata.org/wiki/Property:P26 https://www.wikidata.org/wiki/Q13133

https://www.wikidata.org/wiki/Q76 https://www.wikidata.org/wiki/Property:P26 https://www.wikidata.org/wiki/Q13133

Human-Readable with Links

[https://www.wikidata.org/wiki/Q76 Barack Obama] [https://www.wikidata.org/wiki/Property:P26 spouse] [https://www.wikidata.org/wiki/Q13133 Michelle Obama]

Barack Obama spouse Michelle Obama

Current SiDIF Reference Mechanism

Using 'it' Keyword

The 'it' keyword refers to the subject of the previous statement:

dad loves mom
https://www.wikidata.org/wiki/Q76 is wikidata_url of it

Proposed Extension for Statement Parts

References to different parts of statements:

https://www.wikidata.org/wiki/Q76 is wikidata_url of subject
1992-10-03 is date of predicate
https://www.wikidata.org/wiki/Q13133 is wikidata_url of object

Core Concepts and Bridging

Fundamental Elements

  • Core elements:
    • Entity - Object
    • Link - relation between two objects
  • Paradigm mappings:
    • OO: Objects and their relationships
    • Semantic Web: Resources and properties

Technology Integration

Example of technology bindings:

Person isA Concept
Person_Sparql is sparql_impl of subject
http://foaf/... is prefix_url of subject
foaf is prefix of subject

Barack1950 isA Person
"Barack" is firstname of subject

Semantic Web Foundation

Description Logic Basis

  • Components:
    • Concepts (Classes)
    • Roles (Properties)
    • Individuals (Instances)

RDF/OWL Mappings

Class hierarchy and instance relationships:

Concept subClassOf owl:Thing
owl:Nothing
Barack rdfType Person

Design Decisions

Reference Keywords Options

  • Full form approach:
    • subject for the entity being described
    • predicate for the relationship
    • object for the target entity
  • Short form approach:
    • s for subject
    • p for predicate
    • o for object
  • Alternative approach:
    • subject for entity
    • link for relationship
    • object for target

Key Bridging Concepts

  • 'it' semantics bridges:
    • OO: self/this/me concepts
    • Semantic Web: subject references
  • Statement part references support:
    • Metadata about relationships
    • Integration with semantic web identifiers
    • Technology-specific bindings

Relationship Considerations

  • 1:n relations characteristics:
    • Enables flexible technology bindings
    • Increases system complexity
    • Requires careful management

Example of 1:n relation expression:

Person_Sparql is sparql_impl of subject
foaf is prefix of subject