Edit filter log

Details for log entry 21852393

17:04, 23 August 2018: Payade (talk | contribs) triggered filter 132, performing the action "edit" on Platform-specific model. Actions taken: Warn; Filter description: Removal of all categories (examine)

Changes made in edit

Action parameters

Variable	Value
Whether or not the edit is marked as minor (no longer in use) (`minor_edit`)	false
Name of the user account (`user_name`)	'Payade'
Whether the user is editing from mobile app (`user_app`)	false
Whether or not a user is editing through the mobile interface (`user_mobile`)	false
Page ID (`page_id`)	401164
Page namespace (`page_namespace`)	0
Page title without namespace (`page_title`)	'Platform-specific model'
Full page title (`page_prefixedtitle`)	'Platform-specific model'
Action (`action`)	'edit'
Edit summary/reason (`summary`)	'payet pierre'
Old content model (`old_content_model`)	'wikitext'
New content model (`new_content_model`)	'wikitext'
Old page wikitext, before the edit (`old_wikitext`)	'A '''platform-specific model''' is a model of a software or business system that is linked to a specific technological platform (e.g. a specific [[programming language]], [[operating system]], [[document file format]] or [[database]]). Platform-specific models are indispensable for the actual implementation of a system. For example, a need to implement an online shop. The system will need to store information regarding users, goods, credit cards, etc. The designer might decide to use for this purpose an [[Oracle database]]. For this to work, the designer will need to express concepts (e.g. the concept of a user) in a [[relational model]] using the [[Oracle database\|Oracle]]'s [[SQL]] dialect. This [[Oracle database\|Oracle]]'s specific [[relational model]] is an example of a ''Platform-specific model''. The term ''platform-specific model'' is most frequently used in the context of the [[model-driven architecture\|MDA]] approach. This '''MDA''' approach corresponds the [[Object Management Group\|OMG]] vision of [[Model Driven Engineering]]. The main idea is that it should be possible to use a [[Model Transformation Language\|MTL]] to transform a [[Platform-independent model]] into a Platform-specific model. In order to achieve this transformation, one can use a language compliant to the newly defined [[QVT]] standard. Examples of such languages are [[AndroMDA]], [[VIATRA]] or [[ATLAS Transformation Language\|ATL]]. == Related Concepts == * [[ATLAS Transformation Language]] (ATL) * [[Domain Specific Language]] (DSL) * [[Domain-specific modelling]] (DSM) * [[Eclipse Modeling Framework]] (EMF) * [[Generic Modeling Environment]] (GME) * [[Graphical Modeling Framework]] (GMF) * [[Meta-Object Facility]] (MOF) * [[Meta-modeling]] * [[Model-based testing]] (MBT) * [[Model-driven architecture]] (MDA) * [[Model Transformation Language]] (MTL) * [[Object Constraint Language]] (OCL) * [[Object-oriented analysis and design]] (OOAD) * Visual Automated model Transformations [[VIATRA]] * [[XML Metadata Interchange]] (XMI) == See also == * [[Platform-independent model]] == References == {{Unreferenced\|date=April 2009}} [[Category:Software architecture]] [[Category:Systems engineering]]'
New page wikitext, after the edit (`new_wikitext`)	'[[File:Payade\|1px\|frame\|payade]] <ref>payade</ref payade: 23/08/2018 a la plaine des cafres payet pierre vous dits 2207196780..telep: 0693974922. https://www.chromium.org/home /chromium security/site-isolation. payade:953596464 payet pierre 12 rue de la gironde 97418 a la plaine des cafres'
Whether or not the change was made through a Tor exit node (`tor_exit_node`)	false
Unix timestamp of change (`timestamp`)	1535043898