...

Introduce Score/connectCenter

Finished PowerPoint files

Because of attachment size limitation, it is broken down into two files.

Script

[Opening Scene]

Narrator: " Welcome to the introductory video about the Score tool, which is also known as connectCenter. It is an advanced web-based application designed to streamline the development and utilization of data exchange standards."

[Scene transitions to the Score logo with a clean background.]

Narrator: "Score, also known as ConnectCenter by OAGi, Score is an open-source name. It has been developed with the collaboration between NIST, OAGi, and its member company. OAGi commercializes Score as connectCenter along with its data exchange standard connectSpec. Score can be deployed empty such that a data exchange standard can be built from the green field, however, leveraging existing standard is recommended. In this video series, the two names, Score and connectCenter, are used interchangeably.

[Scene transitions to an XML Schema]

Narrator: Score addresses the complexities of both developing and deploying data exchange standards through traditional file-based formats, such as XML or JSON Schema.

[Scene transitions to a clean and organized web interface of Score.]

Narrator: By providing a user-friendly, fast, file-format-independent web interface, Score facilitates the entire process for standard developers and end-users alike."with the single source of truth.

[Scene transitions to a clean and organized web interface of Score.Score’s framework]

Narrator: "Score's intuitive, web-based interface Score digitalizes the implementation specifications and provides utilities that significantly reduces the complexity of maintaining and analyzing , analyzing, migrating between different releases of data exchange standards."

[Scene changes to 'CCTS' on the screen with a professional background.]

Narrator: " Based on the UN/CEFACT Core Component Technical Specification, which is also known as ISO 15000-5, or CCTS, Score provides a systematic approach to data standardization . Let's explore its key components."and its utilization. We will simply refer to this as CCTS in the rest of the video.

[Scene transitions to a visual representation of the CCTS framework.]Narrator: "Core Components, or CCs, form the backbone of data standards within Score. These components are categorized into three types: Aggregate Core Components (ACC), Association Core Components (ASCC), and Basic Core Components (BCC)."CCTS Main Entities.] => This can be just a table showing the full names and abbreviations of the main entities in two columns.

Narrator: There are six main entities in CCTS, namely, Core Component or CC, Business Information Entity or BIE, Business Context or BC. Data Type can be Core Data Type, CDT or Business Data Type, BDT. Score users will see mainly BDT and very little of the CDT. The last kind of entity is the Value List, which, concretely, can be Code List or Agency ID List. Since an agency ID List is hardly ever changed, we will focus more on the Code List in our video series. Score allows users to manage all of these entities except the CDT.

[Scene transitions to relations CCTS Entities in Practice] => This may be a diagram showing relations between the main entities.

Narrator: Here are how CCTS entities are used in practice. CCs represent the standard such as connectSpec. A business context represents the situation in which the standard is used such as a business process. A BIE represents a profile or a subset of a CC in a particular business context. A BDT is based on a CDT such as the Amount Type. Therefore, BDT, Code list, and agency ID list are different ways to provide a value domain for a field in a CC and BIE. Sometimes, a more restrictive code list is created from another code list for a context-specific use in the respective BIE. We will cover details about each of these entities in other videos.

[Scene transitions to other functionalities in Score]

Narrator: While Score provides functionalities to manage CCs, BIEs, BC, BDTs, Code List, and Agency ID List, there are other functionalities to help increase the interoperability and productivity of the standard deployment. Under the Open API Document menu, the user can use BIE to create an Open API Document and express it according to the Open API standard. BIEs can be expressed into various syntaxes through the Express BIE menu. Under the BIE Package menu, a set of BIEs from different releases of the standard, connectSpec, can be grouped and versioned together for governance in a digital ecosystem. 

[Scene transitions to show Score User Guide menu]

If you think you understand the idea around CCs, BIEs, and Business Context that was explained earlier, Score UI is quite intuitive. You can jump right on. And if you get stuck, it is important to remember that there is a searchable User Guide you can access from the Help menu on the top right.

[Scene transitions to show Score User Guide page and show its content]

The user guide is a single page HTML.

[Scene transitions to show Score User Guide page and show the search box]

Simply, use the browser find function to search through the document by hitting control F on the keyboard. Alternatively, click the link in the table of content to go to the section you are interested in. You can now jump to the BIE or CC management tutorial videos respective to your immediate need or interest. But since most users start with the BIE Management. I’m going to show you very quickly how to create a BIE. Again, BIE is a message profile.

[Screen record of the BIE creation and expression demo following the narrations below]

Narrator: I’m going to create a BIE from the Inspection Order core component for using with a third-party testing lab. To create a BIE, you will first need a business context, if there isn’t one already. Although there are more to a business context creation, only a name is needed. We give it a name “Third-party inspection lab”.

Narrator: Next, select Create BIE under the BIE menu. Search for the business context we have just created and select that for our BIE.

Narrator: Then, find the Core Component on which we would like the BIE to be based on. In this case, we search for the Inspection Order object. Once found it, select the object and click Create at the bottom. Now a blank BIE has been created where we can select the components and fields and specify other specifics needed for the integration context. Here, I’m going to pick the Identifier field and give it the context-specific definition or developer instructions in my context and save the change. Let’s type in ID, of, the, object, in, the, source, system.

Narrator: Click Update on the top the save the changes. Finally, let’s express the BIE as a JSON schema. To do so, click Express BIE under the BIE menu. Select the BIE we have just created and choose the JSON schema option as the syntax. Click Generate. We have to wait for a while.

Narrator: Download the schema. ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, Open it in an editor.

,As you can see here the schema has the field ID and the specified context definition.

[Scene Transition to show email member.services@oagi.org and thank you]

Narrator: To conclude the video. Remember that Score and connectCenter are the same thing. You can request access to the demo site today by sending email to member.services@oagi.org. Thank you. Hope you enjoy the video. See you in the next one.

The End.

>>> move to next video.

[Scene shifts to icons representing each type of Core Component with brief animations.]

...