Wf: pushed from contexts by wikipush

2025-06-05T09:58:05Z

pushed from contexts by wikipush

New page

== WikiSon - Wiki Simple Object Notation ==

[http://www.WikiSon.org WikiSon] follows the following principles:
* simplicity
* brevity
* platform independence
* problem space orientation
*

WikiSon is compatible with:
* [https://www.mediawiki.org MediaWiki] - [https://www.mediawiki.org/wiki/Help:Templates Templates/Macros]
* [https://semantic-mediawiki.org/ SemanticMediaWiki], especially [https://www.mediawiki.org/wiki/Extension:Page_Schemas SMW PageSchemas] and [https://github.com/WolfgangFahl/JSMW_PageSchema JSMW PageSchema]]
* WikiData

=== compatible formats ===
It can be easily transformed from and to the formats:
* csv
* {{Link|target=http://www.json.org|title=json}}
* {{Link|target=https://en.wikipedia.org/wiki/Resource_Description_Framework|title=rdf}}
* {{Link|target=http://microformats.org/wiki/microformats2|title=html microformats}}
* xml
* ... you name it

== Simple examples ==
=== Books ===
<pre>
{{ Book | Lord of the Rings | 0261102389 }}
</pre>
is a valid {{Link|target=Lord of the Rings|title=WikiSon sample}} for the Three Book Set Edition of the Book with the title "Lord of the Rings" by John R. R. Tolkien which happens to have the ISBN-10 number 0261102389

=== Cities ===
<pre>
{{City
|name=Tokyo
|id=JP-13
|localname=東京
|webpage=http://www.tokyo2020.jp
|Population=9153953
|wikipedia_url=https://de.wikipedia.org/wiki/Tokio
|average_income=56
|Country=Japan
}}
</pre>

is a valid WikiSon sample for the Metro-City of "Tokyo"
A possible human readable version of it would look like:
{{City
|name=Tokyo
|id=JP-13
|localname=東京
|webpage=http://www.tokyo2020.jp
|Population=9153953
|wikipedia_url=https://de.wikipedia.org/wiki/Tokio
|average_income=56
|Country=Japan
}}

WikiSon asks for:
<pre>
{{City|name=Tokyo|id=JP-13}}
{{City|name=Tokyo}}
{{City|id=JP-13}}
{{City|Tokyo|JP-13}}
{{City|Tokyo}}
{{City|JP-13}}

</pre>
to render all the same result. The preferred notation is:
<pre>
{{City|name=Tokyo|id=JP-13}}
</pre>

== Concepts and Properties ==
In the above example City is a {{Link|target=:Concept:Concept|title=Concept}}.<br>
In the above example
* name,
* id
* localname
* webpage
* ...
are {{Link|target=:Concept:Property|title=Properties}}.<br>
See the {{Link|target=:Concept:City|title=Description of the City concept}}.

{{smartMediaWiki}} extends the meaning of Concept and Property beyond the definition of {{semanticMediaWiki}}

=== How do derive concepts and properties ===
Let's assume someone wants a software and tells you:
''"Could you please create a software for me that will show me
* whether it rained yesterday in Berlin
* whether the sun shines today in Munich
* whether it snows tomorrow in Vienna
"''

These sentences might lead you to three concepts:
* City
* Calendardate
* Weather

The customer has given you three examples for each concept:
Cities:

* {{City|Berlin}}<nowiki>{{City|Berlin}}</nowiki>
* {{City|Munich}}
* {{City|Vienna}}

...

== Conventions ==

We are following the [[Y-Principle]] here and the A/T/R Bloodgroup approach of Siedersleben.

=== Concepts and Attributes ===
compare to [[Workdocumentation_2015-01-10]]

<uml>
skinparam class {
BackgroundColor White
ArrowColor black
BorderColor #FF8000
FontColor black
FontSize 12
FontName Technical
}
hide Circle
namespace WikiSon {
class Concept {
name
description
}
class Attribute {
name
value
Concept type
}
Concept "1" -- "n" Attribute
}
</uml>
<pre>
{{<Concept>
|<name>=<value>
...
}}
</pre>
where value is of the type specified in the corresponding Attribute.

==== Concept ====
'''Concept''' has the synonms/ corresponding ideas in the problem space:
* Thing
* Subject
* Topic
* Name
* Group
* Definition
* Class
* Entity

Typical solution space mappings are:
* GUI Form
* Database Table
* Excel Sheet
* Class
* Java Class
* PHP Class
* CORBA Interface

==== Attribution ====
===== Examples =====

In Berlin (Thema) hat es heute geregnet (Rhema).

==> implicit Concepts: City, heute->Date, geregnet-> Weather

Did i understand you right that
{{City|name=berlin}}
{{Date|today}}
{{Weather|rain}}

and
{{City|name=munich}}
{{Date|tomorrow}}
{{Weather|sun}}

{{City|name=münster}}
{{Date|yesterday}}
{{Weather|snow}}

are examples for what you'd like to cover with a computer program?

Ich (Thema) habe gerade einen Anruf bekommen (Rhema).
Es war einmal ein König (Rhema). Der (Thema) hatte drei Töchter (Rhema).
Frage-Antwort-Paar:

Was hat Papa gestern gemacht? (nur rhematisches Material bzw. kontextabhängige Thema-Rhema-Aufteilung)
Papa hat gestern (Thema) das Auto gewaschen (Rhema, erfragte Information).

Durch Verschiebung der Positionen von Thema und Rhema erhält der Satz eine starke Betonung oder emotionale Färbung:

Was hat Papa gestern gemacht?
Das Auto (Rhema) hat Papa (Thema) gestern gewaschen!

====== ... =======
Attributions done on Concepts can be perceived or ...
'''Attribute''' has the synonms/ corresponding ideas in the problem space:
* Feature
* Property
* Entry

Typical solution space mappings are:
* SMW triple
* GUI Field
* Database Row
* COBOL Record
* Excel Row
* C# Property
* Java Bean Field
* CORBA Attribute

=== Identifier / Primary Keys ===
The first few attributes of a concept are considered to be the key attributes of a concept.
E.g. in the WikiSon
<pre>
{{Person
|name=Doe
|firstname=John
|email=john@doe.org
|id=4711
|date of birth=1972-05-06
}}
</pre>
name and firstname naturally but not unambigiously identify john doe. Technically the email and id are much better suited as unique identifiers. The date of birth is just a regular attribute.
By convention in this example id would be the technical primary key.

=== Primary key convention ===
The first attribute with a name found in the following list:
* id
* oid
* uid
* uuid
* {{Link|target=List of known Technical Primary Key Attribute Names|title=...}}
is considered to be the technical primary key. All attributes declared before such a technical primary key are considered to form natural (effective in SAPese) keys when the values are concatenated using
"," as a delimiter.
==== Examples ====
<pre>
{{Person
|name=Doe
|firstname=John
|email=john@doe.org
|id=4711
|date of birth=1972-05-06
}}
</pre>
The primary key is "john@doe.org" and the natural key "Doe,John"

<pre>
{{Person
|firstname=John
|name=Doe
|id=4711
|email=john@doe.org
|date of birth=1972-05-06
}}
</pre>
The primary key is "4711" and the natural key "John,Doe"

== Configuration ==
=== Configuration Overview ===
To map Concepts in the Problem Space to Solutions one or more configurations per Concept are necessary.<br>
Think of
* resource forks
* Java Profiles
* UML Sterotypes/Taggedvalues
The configuration has details on what the solution should look like.
E.g. the Concept concept might have the following internationalization Configurations:
{{Configuration
|name=Internationalisierung des Concept Konzeptes für die deutsche Sprache
|id=i18nConfiguration_Concept_de
|concept=Concept
}}
==== UML diagram describing the Configuration ====
<uml>
skinparam class {
BackgroundColor White
ArrowColor black
BorderColor #FF8000
FontColor black
FontSize 12
FontName Technical
}
hide Circle
namespace WikiSon {
class Concept {
name
}
class SolutionConcept {
id
}
class Attribute {
name
value
Concept type
}
class Configuration {
Concept concept
}
Concept "1" -- "n" Attribute
Configuration "1" -- "n" Attribute
SolutionConcept <|-- Configuration
Concept <|-- SolutionConcept

}
</uml>
=== Synonyms aliases ====

== Mapppings ==
{{Link|target=Mapping WikiSon to SemanticMediaWiki}}

== Mapping WikiSon to WikiData ==
* https://www.wikidata.org/wiki/Wikidata:Glossary#Item

== Mapping WikiSon to UML ==
=== Corresponding UML approach for "Concept" ===
<uml>
skinparam class {
BackgroundColor White
ArrowColor black
BorderColor #FF8000
FontColor black
FontSize 12
FontName Technical
}
class UMLClass {
name
}
class StructuralFeature {
name
value
type
}
UMLClass "1" -- "* structural features" StructuralFeature
hide UMLClass circle
hide StructuralFeature circle
</uml>

=== Example: the City Concept described in UML ===
<uml>
skinparam classBackgroundColor white
skinparam classBorderColor #FF8000
skinparam classFontColor black
skinparam classFontSize 12
skinparam classFontName Arial
skinparam NoteBorderColor #FF8000
skinparam NoteBackgroundColor #FFFFF0
hide circle

title City
note as CityDiagramNote
Copyright (c) 2015 BITPlan GmbH
[[http://www.bitplan.com]]
end note
note as CityNote
I represent a City like Berlin, New York or Tokyo
end note
CityNote ..City
Class City <<Category>> {
Text local Name
URL website
Number Pop.
URL wikipedia url
Number average income T$/year

}
City -- Country
City -- Mayor
hide <<Category>> circle
</uml>
=== Mapping a Concept to a UML Class ===
* the name of a concept is used as a UML Class name
* the attributes of a concept are mapped to UML attributes aka structural features
* the name of an attribute is mapped to an UML attribute name
* the type of an attribute is mapped to a UML type starting (bootstrapping) from a {{Link|target=Wikison generic type system}}

=== UML Attributes / Associations and Inheritance ===
In UML
# Attributes
# Associations
# Inheritance
are three different concepts. In WikiSon we consider all three of them are handled as attributes.
==== Regular Attributes and 1:1 Associations ====
If a concept has another concept as it's attribute this corresponds to :1 UML relations/association or UML
inheritance between the two concepts. The UML differentiation of attribute, association, inheritance is not
essentially necessary on the problem side. On the solutions side it will make a difference when
displaying the data. There may be different solution modes:
# displaying the attributes concept's attributes directly (this is like the UML attribute concept)
# displaying the attribute concept as a link (this is like the UML association concept)
# optionally hiding and showing the attributes's concepts attributes and making them available directly in the scope of the concept (this is like the UML inheritance concept)
==== Examples ====
===== Attribute =====
<uml>
class City{
name
Country myCountry
}
</uml>
myCountry is simply an attribute of City of type Country.

==== 1:1 association ====
<uml>
class MetroCity {
}
class City{
name
}
class Country {
name
}
City "1" -- "1 myCountry" Country
City "1 myCity" -- "1" MetroCity
</uml>
Country is simply handled like an attribute of City.
metrocity.myCity.myCountry.name will show the name of the country of the MetroCity in typical solution environments. What is the WikiSon equivalent?

Most UML knowlegeable people would be inclined to fix the above model and put an "n" on the City side of the Country-City association.

===== Inheritance =====
<uml>
class MetroCity {
}
class City{
name
}
class Country {
name
}
City "1" -- "1 myCountry" Country
City <|-- MetroCity
</uml>
metrocity.name will show the name of the metrocity
metrocity.myCountry.name will show the country of the metrocity

==== 1:n and n:m relations ====
* If I am a concept and another concept has a an attribute with me as a type than there is a 1:n relation between me and the other concept.
* If additionaly I do have an attribute with the other concept as a type than there is a n:m relation between me and the other concept.
[[Category:ProfiWiki]]

WikiSon - Revision history

Wf: pushed from contexts by wikipush