[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [Bug 222] New: Reference to the schema from the text
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=222 Summary: Reference to the schema from the text Product: WS-Context Version: 1.0 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Schema AssignedTo: ws-caf@lists.oasis-open.org ReportedBy: tony.fletcher@choreology.com QAContact: mark.little@arjuna.com Personally I would like the schema to be included in the specification in Appendix as is common practice in many other specifications that have a schema as a normative aspect of the specification. The advantage is that the reader then knows that they have the version of the schema that corresponds to this version of the specification (although I also recognise there are arguments against inclusion). Currently the specification includes fragments of the complete schema (Figures 1, 4, 5, and the unnumbered figure under 5.1 Status) but has no reference to the full schema. Add the normative schema back in as an Appendix or add a clear and normative reference to the schema which in this case needs to be located so it is reliably accessible and not subject to alteration. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]