Blueprint assignments for “lxml”
This listing shows the assignment of work for blueprints currently associated with lxml. The drafter is responsible for getting the specification correctly written up and approved. The approver is usually the person who would sign off on the specification.
| 1 → 6 of 6 specifications | First • Previous • Next • Last |
| Priority | Name | Definition | Delivery | Assignee | Drafter | Approver |
|---|---|---|---|---|---|---|
| 1 Undefined | Bootstrapping namespace implementations based on a schema | 4 Discussion | 1 Not started | scoder | ||
| 1 Undefined | Annotating objectify trees with an XML Schema | 4 Discussion | 0 Unknown | |||
| 1 Undefined | Validation messages should be localized or easily localizable | 5 New | 0 Unknown | |||
| 1 Undefined | In-Context Validation/Transformation | 5 New | 0 Unknown | |||
| 1 Undefined | Move fixing xml namespaces of a moved node to C | 5 New | 0 Unknown | |||
| 1 Undefined | RelaxNG parameters max limit | 5 New | 1 Not started | scoder | Ferney Forero |
| 1 → 6 of 6 specifications | First • Previous • Next • Last |
