ARXML Serialization Rules, AUTOSAR 779,   R22-11 (2)

 ARXML Serialization Rules, No.779, 2022-11

AUTOSARは、ISO、IEC、ITUと情報交換契約を結んでいません。
AUTOSAR文書には、ISO、IEC,ITU記述を全文引用することはできません。
WTO/TBT協定に基づき、国際的な調達は国際規格との差異を記述することにより文化依存しない仕様を目指します。
ISO、IEC、ITU文書を合わせて読むと技術内容は理解できます。　
CAN、OSEK/VDX OS、DIAGは、ISO定義を先に確認しましょう。　　
OSEK COM、OSEK NMなどはISOの規定から基本的な部分で定義を変えています。
変更している部分を仕様等で明記するか、ISOを改定するとよいでしょう。　

AUTOSARの参考文献欄の改定が進んでいません。　
Glossary用語定義の網羅性が低いです。
本文を読む前に確認するとよいかもしれません。
本文を読んでから確認してもよいかもしれません。

AUTOSARが、2022年の版、R22-11公開しました。公開行事の模様は

AUTOSAR R22-11 Release Event 20221208
https://qiita.com/kaizen_nagoya/items/18471d0b340480fdcd42

下記URL順次確認中です。
https://www.autosar.org/fileadmin/standards/R22-11/FO/AUTOSAR_TPS_ARXMLSerializationRules.pdf

文書は検索してダウンロードすることができます。
クラウドサービスにありがちな、あるのにないかのような検索結果が出ることがあります。

https://www.autosar.org/standards

# 要求/仕様（Requirement and Specification)

# 一覧

AUTOSAR R22-11 Adaptive Platform 一覧はこちら。

Adaptive Platform Release Overview, No.782, AP, AUTOSAR 22-11 新

https://qiita.com/kaizen_nagoya/items/7f8d6ddacc8573351232

Foundation Release Overview, No.781, FO, AUTOSAR 22-11 新

https://qiita.com/kaizen_nagoya/items/7fcfa4aa0786a38ac3d6

Classic Platform Release Overview, AUTOSAR R22-11, CP, No.0(2)

https://qiita.com/kaizen_nagoya/items/80636f4ca7c16501803b

AUTOSAR R22-11 マラソン

https://qiita.com/kaizen_nagoya/items/988aa405a6fdd794fe53

AUTOSAR 文書番号と発行年　

https://qiita.com/kaizen_nagoya/items/871d81b822984be5239d

Qiitaの記事の一覧は作成中です。

AUTOSAR R22-11 一覧（２）

https://qiita.com/kaizen_nagoya/items/6b0615884e954c65fb43

# Abstract Platformとの関係

離散模型統合

# 文書変更(Document Change) 

>• Minor clarifications

# 用語(terms)

|term|definition|
|:--|:--|
|Class| The name of the class as defined in the UML model.
|Package|The UML package the class is defined in. This is only listed to help locating the class in the overall meta model.
|Note| The comment the modeler gave for the class (class note). Stereotypes and UML tags of the class are also denoted here.
|Base Classes| If applicable, the list of direct base classes. The headers in the table have the following meaning:
|Attribute| The name of an attribute of the class. Note that AUTOSAR does not distinguish between class attributes and owned association ends.
|Type| The type of an attribute of the class.
|Mul.| The assigned multiplicity of the attribute, i.e. how many instances of the given data type are associated with the attribute.
|Kind| Specifies, whether the attribute is aggregated in the class (aggr aggregation), an UML attribute in the class (attr primitive attribute), or just referenced by it (ref reference). Instance references are also indicated (iref instance reference) in this field.
|Note| The comment the modeler gave for the class attribute (role note). Stereotypes and UML tags of the class are also denoted here.
|Artifact| This is a Work Product Definition that provides a description and definition for tangible work product types. Artifacts may be composed of other artifacts ([12]). At a high level, an artifact is represented as a single conceptual file.
|AUTOSAR Tool |This is a software tool which supports one or more tasks defined as AUTOSAR tasks in the methodology. Depending on the supported tasks, an AUTOSAR tool can act as an authoring tool, a converter tool, a processor tool or as a combination of those (see separate definitions).
|AUTOSAR Authoring Tool| An AUTOSAR Tool used to create and modify AUTOSAR XML Descriptions. Example: System Description Editor.
|AUTOSAR Converter Tool| An AUTOSAR Tool used to create AUTOSAR XML files by converting information from other AUTOSAR XML files. Example: ECU Flattener
|AUTOSAR Definition |This is the definition of parameters which can have values. One could say that the parameter values are Instances of the definitions. But in the meta model hierarchy of AUTOSAR, definitions are also instances of the meta model and therefore considered as a description. Examples for AUTOSAR definitions are: EcucParameterDef, PostBuildVariantCriterion, SwSystemconst.
|AUTOSAR XML Description| In AUTOSAR this means "filled Template". In fact an AUTOSAR XML description is the XML representation of an AUTOSAR model. The AUTOSAR XML description can consist of several files. Each individual file represents an AUTOSAR partial model and shall validate successfully against the AUTOSAR XML schema.
|AUTOSAR Meta-Model |This is an UML2.0 model that defines the language for describing AUTOSAR systems. The AUTOSAR meta-model is an UML representation of the AUTOSAR templates. UML2.0 class diagrams are used to describe the attributes and their interrelationships. Stereotypes, UML tags and OCL expressions (object constraint language) are used for defining specific semantics and constraints.
|AUTOSAR Meta-Model Tool| The AUTOSAR Meta-Model Tool is the tool that generates different views (class tables, list of constraints, diagrams, XML Schema etc.) on the AUTOSAR meta-model.
|AUTOSAR Model| This is a representation of an AUTOSAR product. The AUTOSAR model represents aspects suitable to the intended use according to the AUTOSAR methodology. Strictly speaking, this is an instance of the AUTOSAR meta-model. The information contained in the AUTOSAR model can be anything that is representable according to the AUTOSAR meta-model.
|AUTOSAR Partial Model| In AUTOSAR, the possible partitioning of models is marked in the meta-model by atpSplitable. One partial model is represented in an AUTOSAR XML description by one file. The partial model does not need to fulfill all semantic constraints applicable to an AUTOSAR model.
|AUTOSAR Processor Tool |An AUTOSAR Tool used to create non-AUTOSAR files by processing information from AUTOSAR XML files. Example: RTE Generator
|AUTOSAR Specification Element| An AUTOSAR Specification Element is a named element that is part of an AUTOSAR specification. Examples: requirement, constraint, specification item, class or attribute in the meta model, methodology, deliverable, methodology activity, model element, bsw module etc.
|AUTOSAR Template| The term "Template" is used in AUTOSAR to describe the format different kinds of descriptions. The term template comes from the idea, that AUTOSAR defines a kind of form which shall be filled out in order to describe a model. The filled form is then called the description. In fact the AUTOSAR templates are now defined as a meta-model.
|AUTOSAR Validation Tool |A specialized AUTOSAR Tool which is able to check an AUTOSAR model against the rules defined by a profile.
|AUTOSAR XML Schema |This is a W3C XML schema that defines the language for exchanging AUTOSAR models. This Schema is derived from the AUTOSAR meta-model. The AUTOSAR XML Schema defines the AUTOSAR data exchange format.
|Blueprint |This is a model from which other models can be derived by copy and refinement. Note that in contrast to meta model resp. types, this process is not an instantiation.
|Instance| Generally this is a particular exemplar of a model or of a type.
|Life Cycle| Life Cycle is the course of development/evolutionary stages of a model element during its life time.
|Meta-Model |This defines the building blocks of a model. In that sense, a Meta-Model represents the language for building models.
|Meta-Data |This includes pertinent information about data, including information about the authorship, versioning, access-rights, timestamps etc.
|Model |A Model is an simplified representation of reality. The model represents the aspects suitable for an intended purpose.
|Partial Model | This is a part of a model which is intended to be persisted in one particular artifact.
|Pattern in GST |This is an approach to simplify the definition of the meta model by applying a model transformation. This transformation creates an enhanced model out of an annotated model.
|Profile Authoring Support Data |Data that is used for efficient authoring of a profile. E.g. list of referable constraints, meta-classes, meta-attributes or other reusable model assets (blueprints)
|Profile Authoring Tool|  A specialized AUTOSAR Tool which focuses on the authoring of profiles for data exchange points. It e.g. provides support for the creation of profiles from scratch, modification of existing profiles or composition of existing profiles.
|Profile Compatibility Checker Tool |A specialized AUTOSAR Tool which focuses on checking the compatibility of profiles for data exchange. Note that this compatibility check includes manual compatibility checks by engineers and automated assistance using more formal algorithms.
|Profile Consistency Checker Tool| A specialized AUTOSAR Tool which focuses on checking the consistency of profiles.
|Property |A property is a structural feature of an object. As an example a “connector” has the properties “receive port” and “send port” Properties are made variant by the atpVariation.
|Prototype |This is the implementation of a role of a type within the definition of another type. In other words a type may contain Prototypes that in turn are typed by "Types". Each one of these prototypes becomes an instance when this type is instantiated.
|Type |A type provides features that can appear in various roles of this type.
|Value| This is a particular value assigned to a “Definition”.
|Variability |Variability of a system is its quality to describe a set of variants. These variants are characterized by variant specific property settings and / or selections. As an example, such a system property selection manifests itself in a particular “receive port” for a connection. This is implemented using the atpVariation.
|Variant| A system variant is a concrete realization of a system, so that all its properties have been set respectively selected. The software system has no variability anymore with respect to the binding time. This is implemented using EvaluatedVariantSet.
|Variation Binding |A variant is the result of a variation binding process that resolves the variability of the system by assigning particular values/selections to all the system’s properties. This is implemented by VariationPoint.
|Variation Binding Time| The variation binding time determines the step in the methodology at which the variability given by a set of variable properties is resolved. This is implemented by vh.LatestBindingtime at the related properties.
|Variation Definition Time |The variation definition time determines the step in the methodology at which the variation points are defined.
|Variation Point |A variation point indicates that a property is subject to variation. Furthermore, it is associated with a condition and a binding time which define the system context for the selection / setting of a concrete variant. This is implemented by VariationPoint.


## 英日
日本語は仮訳
|no.|count|word|日本語|
|:----|:----|:----|:----|
|1|957|the|その|
|2|911|xml|Extensible Markup Language(短縮名）|
|3|790|xsd| XML Schema Definition（短縮名）|
|4|527|of|の|
|5|518|type|型|
|6|475|element|要素|
|7|385|schema|図式|
|8|359|autosar|AUTomotive Open System Architecture(短縮名)|
|9|312|name|名前|
|10|295|is|です|
|11|250|production|製造|
|12|243|rules|規則|
|13|242|to|に|
|14|225|property|財産|
|15|216|b|b|
|16|187|in|の中に|
|17|177|tps_xmlspr_|tps_xmlspr_|
|18|174|a|一つの|
|19|168|complex|複雑|
|20|157|c|c|
|21|152|for|にとって|
|22|151|role|役割|
|23|140|class|級|
|24|136|wrapper|包み|
|25|129|and|と|
|26|129|by|に|
|27|129|minoccurs|minoccurs|
|28|124|occurs|発生する|
|29|123|max|最大|
|30|119|are|です|
|31|117|multiplicity|多様性|
|32|116|document|資料|
|33|114|r|r|
|34|110|choice|選択|
|35|110|if|もし|
|36|109|example|例|
|37|109|model|模型|
|38|105|ref|reference(短縮名）|
|39|100|create|作る|
|40|99|TRUE|真|
|41|98|meta|超|
|42|98|not|いいえ|
|43|97|elements|要素|
|44|95|id|identifier, 識別子(短縮名）|
|45|92|representation|表現|
|46|91|autosar_tps_xml|autosar_tps_xml|
|47|91|fo|foundation(短縮名）|
|48|90|FALSE|偽|
|49|88|ar|AUTOSAR(短縮名）|
|50|87|attribute|属性|
|51|86|value|価値|
|52|86|with|と|
|53|85|all|すべて|
|54|84|an|一つの|
|55|81|this|これ|
|56|80|that|それ|
|57|79|defined|定義した|
|58|79|instance|実例|
|59|75|tagged|タグ付き|
|60|72|att|attribute(短縮名）|
|61|72|uml|Unified Modeling Language（短縮名）|
|62|71|composite|複合|
|63|70|properties|特性|
|64|64|upper|上の|
|65|63|string|文字列|
|66|62|be|です|
|67|61|description|説明|
|68|60|group|班|
|69|56|figure|形|
|70|55|lower|低い|
|71|53|as|なので|
|72|50|types|型|
|73|49|default|既定値|
|74|49|sequence|順序|
|75|46|d|d|
|76|46|on|の上|
|77|46|then|それから|
|78|46|tr_aprxml_|tr_aprxml_|
|79|45|values|値|
|80|44|see|見る|
|81|44|set|設定する|
|82|42|created|作った|
|83|42|no|いいえ|
|84|41|rule|規則|
|85|41|stereo|立体|
|86|39|reference|参照|
|87|38|component|成分|
|88|38|target|目標|
|89|37|aggregation|集約|
|90|37|pattern|類型|
|91|37|unbounded|無制限|
|92|36|association|協会|
|93|36|mapping|対応付け|
|94|36|primitive|原生的|
|95|35|configuration|構成|
|96|35|or|または|
|97|35|used|使った|
|98|34|o|o|
|99|33|applies|適用する|
|100|33|represented|表現|


minoccurs
https://www.techscore.com/tech/XML/XML_Schema/Schema2/2_4

maxoccursは計数せずに分解しているのか未確認。


# 参考(reference)
　
Glossary も　参考に入れましょう。
https://www.autosar.org/fileadmin/standards/foundation/22-11/AUTOSAR_TR_Glossary.pdf

[1] AUTOSAR XML Schema Production Rules
AUTOSAR_TPS_XMLSchemaProductionRules
[2] Software Component Template
AUTOSAR_TPS_SoftwareComponentTemplate
[3] System Template
AUTOSAR_TPS_SystemTemplate
[4] Specification of ECU Configuration
AUTOSAR_TPS_ECUConfiguration
[5] Meta Model
AUTOSAR_MMOD_MetaModel
[6] Meta Model-generated XML Schema
AUTOSAR_MMOD_XMLSchema
[7] Standardization Template
AUTOSAR_TPS_StandardizationTemplate
[8] Extensible Markup Language (XML), v1.0
http://www.w3.org/TR/REC-xml/
[9] XML Schema 1.0
http://www.w3.org/TR/xmlschema-1
[10] Generic Structure Template
AUTOSAR_TPS_GenericStructureTemplate
[11] Unified Modeling Language: Superstructure, Version 2.0, OMG Available Specification, ptc/05-07-04
http://www.omg.org/cgi-bin/apps/doc?formal/05-07-04
[12] Software Process Engineering Meta-Model Specification
http://www.omg.org/spec/SPEM/2.0/

# 関連文書(Related document)

AUTOSAR Abstract Platformへの道（詳細編）

https://qiita.com/kaizen_nagoya/items/cb217133884fa0a2c704

2023年1月　記事数一覧

https://qiita.com/kaizen_nagoya/items/78153968c5de76a7fd83

年末100記事を30点に仕上げる。

https://qiita.com/kaizen_nagoya/items/3ffdc82caee3a325d1d7

2023 書き初め

https://qiita.com/kaizen_nagoya/items/d494737e2627127b530d

「はじめてのCAN/CANFD 」 ベクタージャパン ＜エンジニア夏休み企画>【読書感想文】

https://qiita.com/kaizen_nagoya/items/1fee270be00ef90ca4ec


三方良し　Udemy 車載LAN入門講座 CAN通信編

https://qiita.com/kaizen_nagoya/items/bed038c52510fea72c0a


詳解 車載ネットワーク CAN, CAN FD, LIN, CXPI, Ethernetの仕組みと設計のために(1) 著者　 ＜エンジニア夏休み企画 読書感想文＞

https://qiita.com/kaizen_nagoya/items/e9971698a108c3dba794

詳解 車載ネットワーク CAN, CAN FD, LIN, CXPI, Ethernetの仕組みと設計のために(2)参考文献 ＜エンジニア夏休み企画>【読書感想文】

https://qiita.com/kaizen_nagoya/items/e156cbdd5fce9263776e

詳解 車載ネットワーク CAN、CAN FD、LIN、CXPI、Ethernetの仕組みと設計のために

https://qiita.com/kaizen_nagoya/items/44a9e6b0f5363b4a5b35

AUTOSAR Abstract Platform User Group Weekly Report(1) 2022.1.8

https://qiita.com/kaizen_nagoya/items/fece4f7719ef55d612bf

AUTOSAR Abstract Platform User Group Weekly Report(2) 2022.1.15

https://qiita.com/kaizen_nagoya/items/6f1168a36e795976a906

# R23-11
https://qiita.com/kaizen_nagoya/items/4074f721a186ceca9e47

＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞
This article is an individual impression based on the individual's experience. It has nothing to do with the organization or business to which I currently belong.

# 文書履歴(document history)
ver. 0.01 初稿 　　20230131
ver. 0.02 R23-11追記 20240101

### 最後までおよみいただきありがとうございました。
いいね　💚、フォローをお願いします。
#### Thank you very much for reading to the last sentence.
Please press the like icon 💚　and follow me for your happy life.