Page History

...

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

...

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

...

Resolution: The interfaces are the same but the functionality is available from one then 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

...

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 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.

...

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: Cecil CECIL