4 messages in org.oasis-open.lists.search-ws-commentRe: [search-ws-comment] XML Schema de...| From | Sent On | Attachments |
|---|---|---|
| Saašha Metsärantala | Jan 16, 2012 5:49 am | |
| Ray Denenberg, Library of Congress | Feb 24, 2012 9:13 am | |
| Saašha Metsärantala | Feb 24, 2012 1:16 pm | |
| Ray Denenberg, Library of Congress | Mar 30, 2012 11:47 am |
| Subject: | Re: [search-ws-comment] XML Schema design for search WS | |
|---|---|---|
| From: | Saašha Metsärantala (saa...@acc.umu.se) | |
| Date: | Feb 24, 2012 1:16:59 pm | |
| List: | org.oasis-open.lists.search-ws-comment | |
Hello!
The OASIS WS TC thanks you for your comment of January 16 about schema design.
Thanks Ray for your answer!
There is no single "right way" to design a schema
That is true!
valid instances can be created which make no sense for the searchRetrieve application.
I would like to try to avoid that.
In our schemas we have chosen to define each element as global so that it can be imported by another schema.
That represents a valid approach, of course!
there may be other applications [...] that may want to [...] reference to specific elements.
Of course, it is important to take that into account.
it seems simpler [...] to globalize all elements rather than arbitrarily (or best guest) select some but not others.
It is!
I would like to suggest to combine these approaches. This could be done in different ways. One example is the following:
We could create one new schema where all elements defined there can be root elements.
The other schemas would be rewritten to mainly select and combine the elements defined in the new schema and define which elements are allowed to be used as root elements.
Thus, we could prevent many non-sense instances to validate without giving up the reusability of most elements.
Of course, one more schema would slightly increase the complexity of the overall design, but I consider that the flexibility such an approach can offer would combine well with the ability to avoid the validation of many non-sense instances.
Future versions of the new schema could add new elements without removing nor modifying previously defined elements, thus improving its forward compatibility. Future versions of the other schemas could focus on new ways to combine (previously defined or newly defined) elements.
Regards!
Saašha,
-- This publicly archived list offers a means to provide input to the OASIS Search Web Services TC.
In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.
Subscribe: sear...@lists.oasis-open.org Unsubscribe: sear...@lists.oasis-open.org List help: sear...@lists.oasis-open.org List archive: http://lists.oasis-open.org/archives/search-ws-comment/ Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: http://www.oasis-open.org/maillists/guidelines.php Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=search-ws Join OASIS: http://www.oasis-open.org/join/