Agenda
Item | Time |
---|---|
Welcome | 1400 |
Update on tasks | |
Any other business | |
Close | 1530 |
Panel | ||||
---|---|---|---|---|
| ||||
|
Welcome
Objectives of this meeting are:
- work on tasks
Update on tasks
Task list
The updated task list is at SSCONE-SITCOM Tasks.
Completed tasks
Ongoing tasks
- /wiki/spaces/SCOI/pages/59605888
/wiki/spaces/SCOI/pages/59605387.- Some All rows have been marked as "Review and accept? ". The group is asked to review these by the next meeting to ensure the proposed solution is accepted.
- Service Categories
- The group is asked to review the mature schemes by the next meeting. If accepted, they will be published on the reference site:
- Start work on standardised implementations were accepted with one exception: there is still a need to discuss the best approach for documenting withheld network addresses.
- It was agreed to close the item concerning the names of service providers. The new service metadata structure is already an improvement as it split the name and the abbreviated name of the organisation.
- All the other rows will be discussed as part of the standardised implementations task and can be closed.
- Some All rows have been marked as "Review and accept? ". The group is asked to review these by the next meeting to ensure the proposed solution is accepted.
- Service Categories
- It was accepted that there is no need for the CodeDataFormatType given the new approach in the service metadata schema.
- The changes to CodeLifecyleStageType were not approved. This scheme will be discussed later.
- The other mature schemes were approved and can be moved to the reference site.
- OTHER will be added to CodeDocumentType
- The phrase "based on the SWIM Technical Infrastructure capability" will be removed from the definition of CodeSecurityMechanismType.
- swim-reference-categories.ttl - the updated skos representation of the service categories will also be made available.
- FAQ
- The FAQ on HTTP error codes was reviewed. It needs to be updated to better tie the behaviour of operations to the error message semantics. After the edits are made the FAQ can be moved to supporting material.
- /wiki/spaces/SCOI/pages/59605888
- Items 28, 36 and 48 can be closed. Item 36 will be discussed with the Registry CCB
- Documenting the use of standardised implementations.
- The pages were reorganised based on the comments and input already received.
- A new category (Service Categories - Service Type) has been added based on service type. This grew out of discussions in A3SG. It is used as a way to identify similarities in the services being discussed. We should discuss this at the next meeting. It overlaps with the discussion on standardised implementations
- Service Definition Template
- This has been added. It is draft material to help in the various *3SGs. We should discuss this at the next meeting.
Any other business
none
- The community should review the pages by the next meeting and suggest what else needs to be done.
- /wiki/spaces/SCOI/pages/59606413
- Discuss - explain, understand, plan.
- The community should review the pages by the next meeting so we can start to work on the content.
- Service definition template
- This will be used in the upcoming service definition work in A3SG and MET3SG. At the moment it is a translation of the requirements. Issues that arise when using the requirements/templates will be referred to SSCONE.
- Note also the work that has been asked concerning conformance/compliance assessment report templates.
Any other business
Registry
- Integrating the new schema. Changes to the Registry will be presented at the next meeting so we can assess any impact on us.
Next meetings
Meeting schedule is maintained at SSCONE-SITCOM Meetings.
Next progress meeting is 526September 2022.