SFS Suomen Standardit

 

This standard will provide a description of the numbering system replacing the DOMES numbering. The description of the DOMES numbering can be found in MERIT/COTES joint working groups, MERIT campaign: connection of reference frames, implementation plan, 1983. The standard will provide to the geodetic data producers and users a proper identification of the permanently instrumented stations, (e.g. those used in the production of the International Terrestrial Reference Frame and other similar stations), with special emphasis on the backward compatibility with existing DOMES numbers, which will have a positive impact on interoperability issues when merging several data from different communities. This standard will: • support interoperability among GNSS providers (GPS, GLONASS, GALILEO, BEIDOU, …) • clarify the potential confusion between communities which have already adopted their own numbering systems • support the UNGGIM GGRF resolution on global geodetic infrastructure.

 

This draft amendment explains all the changes and extensions to ISO/IEC 23092-2 (MPEG-G Part 2) required for supporting graph-based alignment and reference genome data.

 

This document specifies for - renewable and low-carbon methane rich gases for injection in the gas network - natural gas, renewable and low-carbon methane rich gases and mixtures thereof as fuel for engines This documents also specifies necessary related methods for sampling, analysis, and testing. This document applies to the previously mentioned gases irrespective of the storage state (compressed or liquefied). To check compliance with some requirements set by the standard, LNG or liquefied biomethane should be re-gasified prior to testing.

 

This document specifies the characteristics, qualification and acceptance requirements for self-locking shaft-nuts and threaded rings, with right- or left-hand MJ threads, in FE-PA2601, silver-plated, for aerospace applications. Temperature class: 450 °C . It is applicable whenever referenced.

 

This document specifies the characteristics of screws, 100° countersunk normal head, offset cruciform recess, close tolerance shank, short thread, in titanium alloy, aluminium IVD coated. Classification: 1 100 MPa /425 °C .

 

This document specifies the characteristics of silver plated bolts, normal hexagonal head with relieved shank and long thread in heat resisting steel FE-PA2601 (A286), for aerospace applications. Classification: 900 MPa /650 °C

 

This document specifies the characteristics of dummy receptacles in the family of bayonet coupling circular connectors, intended for use in an operating temperature range of -65 °C to 175 °C or 200 °C continuous. It applies to models specified in Table 3. For plugs associated with these dummy receptacles, see EN 3646 008.

 

This document specifies the reference software for carriage of haptics data as specified in ISO/IEC 23090-32. The information provided describes the reference software modules and the features that it supports. It also provides a description of how the reference software can be utilized. Finally, it also provides a description of conformance test vectors.

 

Warning The use of this International Standard may involve hazardous materials, operations and equipment. This International Standard does not purport to address all of the safety problems associated with its use. It is the responsibility of the user of this International Standard to establish appropriate safety and health practices and determine the applicability of regulatory limitations prior to use. This International Standard gives specifications and operating instructions for glass capillary viscometers widely used for the determination of kinematic viscosity of petroleum products by the procedure described in ISO 3104. The calibration of these viscometers is also described. The types of viscometers described are modified Ostwald viscometers (Annex A), suspended-level viscometers (Annex B) and reverse-flow viscometers (Annex C). Other viscometers of the glass capillary type which are capable of measuring kinematic viscosity within the limits of precision given in ISO 3104 may be used.

 

Furthermore, this document, as amended by the corresponding amendment for Gaussian splat support, also specifies the use of the visual volumetric video-based coding mechanism for 3D scenes represented using Gaussian splat. In such representations, each point of the point cloud corresponds to a Gaussian primitive in 3D space and is described by a set of parameters, including at least its 3D position and additional attributes such as covariance, opacity and appearance coefficients. These parameters are mapped to geometry and attribute components within the V-PCC framework and coded using the same video-based mechanism. This enables efficient compression of Gaussian-splat-based scene representations and provides a coding solution suitable for Gaussian splat coding applications. 

 

The Kernel Modeling Language (KerML) is an application-independent modeling language with a well-grounded formal semantics for modeling existing or planned systems. The language includes general syntactic constructs for structuring models, such as relationships, annotations and namespaces; core semantic constructs that have semantics based on classification; and additional constructs for commonly needed modeling capabilities, such as associations and behaviors.

 

System models are expressed in KerML using a textual concrete syntax. This can be parsed to an abstract syntax representation, which is then given a semantic interpretation for the system being modeled. The semantics for the KerML core constructs is grounded in formal mathematical logic, providing a consistent basis for mathematical reasoning about KerML models. However, beyond this, the semantics of KerML constructs are specified by the relationship of user model elements to the KerML Semantic Library.

 

The Semantic Library models, also expressed in KerML, provide an ontological model of the meaning of KerML models. Indeed, all KerML models can be semantically expressed using solely core modeling constructs referencing the appropriate semantic concepts defined in the Semantic Library. KerML semantic constructs beyond the core are essentially just syntactic conveniences for reusing specific library concepts: structures for modeling objects, behaviors for modeling performances, associations for modeling links, etc.

 

Indeed, the full KerML language can be considered to be simply a syntactic extension of the core, which is semantically extended using library models. By intent, this approach can also be used to build on KerML to create more specific modeling languages. Application specific modeling languages can be built on KerML by extending the KerML abstract syntax, specializing its semantics, with concrete syntaxes similar to or entirely different from KerML's.

 

To support this, the KerML Semantic Library also includes additional library models beyond those directly providing semantics for KerML syntactic constructs, capturing typical semantic patterns (such as asynchronous transfers and state-based behavior) that can be reused by languages built on KerML. Specialized modeling languages can provide additional syntax for these libraries, tailored to their applications, with semantics based largely or entirely on the KerML libraries.

 

In this way, KerML can provide the kernel for a family of syntactically diverse but semantically integrated modeling languages.

 

The purpose of this standard is to specify the Systems Modeling Application Programming Interface (API) and Services that provide standard services to access, navigate, and operate on KerML-based models [KerML], and, in particular, SysML models [SysML]. The standard services facilitate interoperability both across SysML modeling environments and between SysML modeling environments and other engineering tools and enterprise services.

 

The Systems Modeling API and Services specifies the types and details of the requests that can be made and responses that can be received by software applications that are consuming the services to software applications that are providing the services.

 

The Systems Modeling API and Services specification includes the Platform Independent Model (PIM) - see Clause 7- and two Platform Specific Models (PSMs) - see Clause 8 : REST/HTTP PSM and OSLC PSM.

 

The purpose of this standard is to specify the Systems Modeling Language™ (SysML), to guide the implementation of conformant modeling tools, and to provide the basis for the development of material and other resources to train users in the application of SysML.

 

SysML is a general-purpose modeling language for modeling systems that is intended to facilitate a model-based systems engineering (MBSE) approach to engineer systems. It provides the capability to create and visualize models that represent many different aspects of a system. This includes representing the requirements, structure, and behavior of the system, and the specification of analysis cases and verification cases used to analyze and verify the system. The language is intended to support multiple systems engineering methods and practices. The specific methods and practices may impose additional constraints on how the language is used.

 

SysML is defined as an extension of the Kernel Modeling Language (KerML), which provides a common, domain independent language for building semantically rich and interoperable modeling languages. SysML also provides a capability to provide further language extensions. It is anticipated that SysML will be customized using this language extension mechanism to model more specialized domain-specific applications, such as automotive, aerospace, healthcare, and information systems, as well as discipline specific extensions such as safety and reliability.

 

Note. Definitions of system and systems engineering can be found in ISO/IEC 15288 Systems and Software Engineering – System Life Cycle Process.

 

This specification describes a transformation for a semantic translation from SysML v1 [SysMLv1] to SysML v2 [SysMLv2] in a precise way. (In this document, "SysML v1" refers to SysML v1.7, the last version of SysML prior to v2.0, and "SysML v2" refers to SysML v2.0, or whatever version corresponds to the current version of this specification.)

 

The main intent is to provide the rules on which automated conversions of SysML v1 models to the SysML v2 standard can be developed. In addition, this annex can be considered an educational document that provides useful information for people who would like to compare using SysML v2 and using SysML v1.

 

More sophisticated applications of this transformation can also be envisaged. For instance, a SysML v1 conformant tool could use this transformation to implement a limited subset of the SysML v2 API that will provide "SysMLv2-like" read-only access to its SysMLv1 models for external applications.

 

The Structured Patterns Metamodel Standard (SPMS) specification defines a common standard for the definition and description of patterns as used in architecting, designing, and implementing software systems, working with software faults or security issues, and any situation where a pattern is appropriately applied.

 

SPMS has three main goals:

1) Sharing of pattern definitions in repositories or catalogs, including human-oriented specifications and machine oriented formalisms for automated tool use.

2) Sharing of pattern instances – indicators of the existence of a pattern within a model – regardless of how that pattern was determined, with traceability back to the methodology, and traceability to the model artifacts that prove its existence. if applicable. These instances may come from manual assertion, or from the results of an automated tool.

3) A visual representation for pattern instances that augments existing modeling representations and supports both automated production of graphical diagrams, and informal “line and box” style human-generated sketching.

 

The first goal is supported by the Definitions package, which defines a metamodel for defining and storing pattern specifications, suitable for use in tooling and repositories.

 

The second goal is supported by the Observations package, which defines a metamodel for pattern instances. The classes defined here offer support for both human-oriented use cases (consulting, investigation, education) and machine oriented use cases (automated analysis tools, automated results analysis, etc.).

 

Both goals are further supported by the Relationships package, which augments the Definitions package with metadata appropriate for a repository or catalog of patterns. This metadata offers a set of semantic relationships between pattern definitions and instances, enhancing searchability and other use cases appropriate to the domain. Again, both human oriented and machine-oriented use cases are supported in this package.

 

The Formalisms package supports the first goal more thoroughly for automated tool use cases and research purposes. It provides a mechanism for linking to a variety of formal metamodels such as Object Constraint Language (OCL), Knowledge Domain Metamodel (KDM), Abstract Syntax Tree Metamodel (ASTM), or Pattern Hierarchical Object Relation Metamodel Language (PHORML), depending on the needs of the modeler and community.

 

The third goal is supported by the Pattern Instance Notation (PIN) metamodel, which defines a common metamodel for the graphical depiction of pattern instances. It relies on the abstractions defined in SPMS. PIN and the corresponding elements in SPMS are equivalent in their expressive power, and have a one-to-one coherence of features.

 

PIN was developed hand in hand with the Patterns package of SPMS and provides a simple and human-oriented approach for quickly depicting instances of patterns, how they work in concert, and how they are expressed in an implementation or further design document. Most notably, PIN can be used entirely by itself to illustrate pattern interactions independent of an implementation, or used as an annotation with the variety of other graphical notations, such as UML diagrams. 

 

This document specifies methodologies for measuring the performance of AI models for classification, regression, clustering and recommendation tasks.

 

This European Standard specifies performance requirements, validation methods and provides general instructions on the use of diffusive samplers for the determination of the concentration of gases in ambient air. This standard applies to all stages of the measuring procedure, including preparation, deployment, transportation and storage. It includes general principles applicable to diffusive sampling and analysis. It enables manufacturers and users to adopt a consistent approach to sampler validation and provides a framework for the assessment of sampler performance.

 

This document specifies a method for the enumeration of the characteristic microorganisms Lactobacillus delbrueckii subsp. bulgaricus (in short: L. bulgaricus) and Streptococcus thermophilus (in short: S. thermophilus) by means of the colony-count technique. The method is applicable to yoghurts (for the definition see CXS 243-2003). The colony-count technique (pour plates) is suitable for, but not limited to, the enumeration of L. bulgaricus and S. thermophilus in test samples with a minimum of 10 colonies counted on a plate. This corresponds to a level of the characteristic microorganisms L. bulgaricus and S. thermophilus that is expected to be higher than 100 cfu/g. The colony-count technique (spread plates) is suitable for, but not limited to, the enumeration of L. bulgaricus and S. thermophilus in test samples with a minimum of 10 colonies counted on a plate. This corresponds to a level of the characteristic microorganisms L. bulgaricus and S. thermophilus that is expected to be higher than 1 000 cfu/g.

 

This document provides terminology, concepts, requirements, and guidance for humanoversight of AI systems. It is primarily intended for organizations placing on the market or putting into service AI systems and is not specific to any particular sector;

 

This document describes an analytical procedure for the determination of platinum in platinum alloys with a nominal content up to 990 ‰ (parts per thousand), including alloys according to ISO 9202.