Link to page: 6.3 - Tools for Semantic Infrastructure 2.0
Comment 07 on Section 6.3
Section 6 > Tools for Semantic Infrastructure 2.0 > Semantic Infrastructure Services and Interactions November 22 version
"The artifact authoring part describes "register the object identifier with its metadata" and "link artifacts to service specifications". Additionally, the artifact analysis part describes "execute semantic queries for search and analysis". I assume these semantic queries work on the above-mentioned metadata and service specifications?
Resolution: Yes. Raghu Chintalapati
Comment 06 on Section 6.3
November 22 version
The latter service specifications are being authored in the "Administer Services and Specifications" as well as the so-called service metadata. Is the meta-data in "register the object identifier with its metadata" this service data, if not, where is this metadata being authored?
Resolution: The metadata is either derived from the artifacts (if they are computable) or specified by the user using a set of API's/interfaces. Raghu Chintalapati
Comment 05 on Section 6.3
November 22 version
"Link the artifacts to the service specification" is appearing 2 times, once in the "Artifact authoring" and once in the "Administer services and specifications". Is this intentionally a bi- directional activity (can be done from both sides)? Which again brings up the service registry in some form, is this different from the artifact registry?
Resolution: The interfaces are the same but the functionality is available from one place. SI provides is a design time repository of service specifications and all the artifacts that make up a specification. The words ECCF registry, design time service registry and artifact registry are all used interchangeably. Raghu Chintalapati
Comment 04 on Section 6.3
November 22 version
Also the "execute semantic queries for search and analysis" appears both in "Artifact Analysis" and in "Analyze Services". The relation between artifacts and services is not clear.
Resolution: It implies that search and analysis can be performed against both services and artifacts. Services specification is usually an aggregation of artifacts. SI is expected to support individual artifacts as well, like form definitions, etc. Raghu Chintalapati
Comment 03 on Section 6.3
November 22 version
Many things are unclear. For example, "allow governance to set the status of a specification and promote". What can be the status of a specification and its promotions? Raghu Chintalapati
Resolution: The status of a specification can be draft, new, production, etc. The status allows the service owners to track the status of his/her specification as it goes through the governance lifecycle.
Comment 02 on Section 6.3
November 22 version
There is a task for discovery "Discovery services" in the Search and Access Services but no task for composition/orchestration even though this is in the functional requirements.
Resolution: Composition/Orchestration rely heavily on discovery of the right services. The SI team is assessing the feasibility of automated and semi-automated composition and orchestration. Raghu Chintalapati
Comment 01 on Section 6.3
November 22 version
The Knowledge Based Systems Support Tools part is just not OK. What is the difference between Knowledge Representation Definition and Knowledge Base Model Definition, why have a Rule Pattern Definition but no Description Logic Knowledge Base definition (or is this the Domain Model Development?), what is the difference between Rule Pattern Definition and Rule Generation tooling?
Resolution:
Knowledge Representation Definition refers to the reference model used as the overall model for the knowledge base, your reference information model. The Knowledge Base Model Definition refers to the instance model for your actual knowledge base, which is likely a subset of the Knowledge Representation Definition.
The Knowledge Base Model Definition is the Description Logic (DL) Knowledge Base definition.
The Rule Pattern Definition is the transform between a DL pattern and another (usually first order logic) rule language. The Rule Generation Tooling is the tooling to accomplish the conversion of the DL pattern to the rule pattern.
