Nobuyuki SAMBUICHI

ISO/TC295 Audit data services/SG1 Semantic model Convener

Model: Default (GPT-3.5)

Is it allowed to extend existiong iso standard to draft new iso standard?

Yes, it is possible to extend an existing ISO (International Organization for Standardization) standard to draft a new ISO standard. ISO standards are developed and maintained by technical committees and working groups composed of experts from various industries and organizations.

When a need arises to address additional aspects or areas related to an existing ISO standard, a new standard can be developed as an extension or revision of the original standard. This process typically involves establishing a new working group or task force to draft the new standard, which will consider the specific requirements, scope, and objectives of the extension.

The development of a new ISO standard based on an existing one often follows a similar process, including drafting, review, and consensus-building stages. The final standard is then subject to approval and publication by the ISO.

It’s important to note that the specific procedures and guidelines for developing ISO standards are outlined in ISO/IEC Directives, which provide detailed information on the standards development process, including how to initiate new work and draft new standards based on existing ones. These directives ensure consistency and quality in the development of ISO standards.

ISO1500-5 CCS and ISO1179 MDR provides well designed framework fro semantic modeling. but these are mainly intended to model a single document. When drafting audit data services we need a framework to express relathinships among classes. For instance association in CCS os only used to represent aggregation. But we need a simple association, which is a relation, and inheritance/generalization.

While ISO 15000-5 (CCS) and ISO 1179 (MDR) provide a well-designed framework for semantic modeling of a single document or data structure, they may not specifically address the modeling of relationships among classes or the concepts of simple associations, inheritance, or generalization.

When developing a framework to express relationships among classes, you may need to consider other standards or modeling approaches that cater to these specific requirements. Some commonly used standards and methodologies for modeling relationships in information systems include:

Unified Modeling Language (UML): UML provides a standardized notation for modeling object-oriented systems and includes constructs such as associations, generalizations (inheritance), and various types of relationships.

Entity-Relationship (ER) modeling: ER modeling is commonly used in database design and provides a graphical representation of entities, attributes, and relationships, including associations and inheritance.

Resource Description Framework (RDF): RDF is a standard for representing information about resources on the web. It allows expressing relationships between resources using properties and provides flexibility in modeling relationships.

Object Management Group’s (OMG) Meta Object Facility (MOF): MOF is a metamodeling standard that allows defining other modeling languages and frameworks. It supports concepts like associations, inheritance, and generalization.

When drafting audit data services and requiring a framework to express relationships among classes, you can consider leveraging these standards or methodologies alongside ISO 15000-5 (CCS) and ISO 1179 (MDR) to enhance your modeling capabilities. It’s important to choose a framework that aligns with your specific needs and integrates well with your existing standards and technologies.

What we want to do is extend ACC and ASCC to include Relation Core Component and Genaralized Core Component. To this purouse, we like to introduce new CC namely Primary Key Core Component, Reference Core Component, and Generalized Core Component. And also introduce new Business Information entity such as PHBIE, RBIE, and GBIE.

It seems like you have a specific requirement to extend the ISO 15000-5 (CCS) and ISO 1179 (MDR) standards by introducing new core components and business information entities. While ISO standards can be extended or customized to meet specific needs, it’s important to ensure that any extensions or modifications are aligned with the principles and guidelines set forth by ISO.

To introduce new core components such as Primary Key Core Component, Reference Core Component, and Generalized Core Component, you would need to define their semantics, properties, and relationships within the context of the existing CCS and MDR frameworks. This would involve establishing a clear definition for each component, its purpose, and how it relates to other components.

Similarly, when introducing new business information entities like PHBIE, RBIE, and GBIE, it’s essential to define their structure, attributes, and relationships with other existing entities. Consideration should be given to how these entities align with the overall architecture and principles of ISO 15000-5 and ISO 1179.

To proceed with these extensions, it would be advisable to form a working group or task force of experts familiar with the original standards and knowledgeable in the domain specific to your requirements. This group can collaborate to define the extensions, ensuring that they adhere to ISO’s guidelines and requirements for standardization.

It’s worth mentioning that the process of extending ISO standards may involve following specific procedures, such as proposal submission, review, consensus-building, and validation by relevant ISO technical committees. Engaging with the ISO organization and seeking their guidance throughout the extension process would be valuable to ensure the extensions are developed and introduced in a standardized and recognized manner.

Is it easier to extend than developping our own Basic Class and Business object similar to BCC,ACC,ASCC,PKCC,RCC,GCC and BBIE,ABIE,ASBIE,PKBIE,RBIE,GBIE from scratch?

Extending existing ISO standards such as CCS and MDR to incorporate additional core components and business information entities can often be easier compared to developing your own basic classes and business objects from scratch. There are a few reasons for this:

Standardization: ISO standards provide a recognized and widely accepted framework for data modeling and information exchange. By extending existing ISO standards, you can leverage the established concepts, principles, and guidelines already present in the standards. This can save time and effort by building upon a well-defined foundation.

Compatibility: Extending existing ISO standards ensures compatibility with other systems and organizations that adhere to those standards. It allows for interoperability and seamless integration with existing implementations that conform to the same standards.

Community and Support: ISO standards have a community of experts and stakeholders who contribute to their development and maintenance. By extending the existing standards, you can benefit from the knowledge, expertise, and support of this community. There may be resources, documentation, and best practices available to help you navigate the extension process.

Consistency and Alignment: Extending existing standards helps maintain consistency and alignment with the original standards’ concepts and principles. This can facilitate understanding, adoption, and future evolution of the extended components and entities.

That being said, there may be cases where developing your own basic classes and business objects from scratch is necessary if your requirements are significantly different from what existing ISO standards offer. In such cases, you would have the freedom to design and tailor the components and entities specifically to your needs. However, this approach would require careful consideration of factors such as standardization, interoperability, and industry acceptance.

Ultimately, the decision between extending existing ISO standards or developing your own components and entities depends on the specific requirements, resources, and context of your project.