Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Summary

The Vocabulary Service description and assumptions are hearing completion, but there is much to do on the modeling of contracts and schemas, and some questions on the structural (hierarchy) modeling.

Risks

Describe each risk, estimate the likelihood (Low, Medium, High) and the severity of impact (Low, Medium, High), and then provide a mitigation plan

#

Description

Likelihood

Severity

Mitigation

1

We need to address a broad range of functionality, but we also need to stage development and not get bogged down in an end-all-be-all implementation.

Low

Med

Carefully stage this service as a set of discrete milestones.

2

We need to minimize dependencies in other services on a complex Vocabulary service, or we will violate principles of agnostic service design.

Low

High

Separate Enumeration service from more sophisticated services

3

Not clear how to handle local changes to an external vocabulary that is regularly updated.

Med

Med

Need to work soon on the definition of requirements and expectations from the community.

Known Issues

Status of Milestones

  • Complete initial design, specification - In Progress
  • No labels