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:
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:
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:
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:
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?
Resolution:
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:
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:
