OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

provision message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Nuke the schema section?


I think that we should remove the Schema reference section. The Schema 
section is currently redundant with the Protocol section (and it's 
redundant with the XSD).

The Schema section has a subsection for the core and each of the 
standard capabilities.  Each subsection contains a further subsection 
for each type or top-level element.  Each type or element subsection:
1) shows a schema snippet of a type or element in isolation.
2) provides usage and cross-reference information.
3) normatively describes the syntax defined in the XSD.

1) The schema snippets are redundant with those at the beginning of each 
Protocol operation subsection.
3) The normative description of syntax is redundant with the XSD and is 
largely redundant with the normative descriptions of the request and 
response elements in the Protocol section.
2) You could get the same usage and cross-reference information by 
searching the protocol section (or by viewing and searching the XSD files).

The feedback I've received from reviewers suggests that the schema 
snippets are most useful in the Protocol section. Here the schema 
snippets provide context for the normative descriptions of request and 
response elements (and also to the examples).

The Schema section currently takes up 40 pages (and will probably be 50 
or 60 when complete).  I say we save the space (and kill fewer trees).

Does anyone object?



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]