[
https://issues.apache.org/jira/browse/SOLR-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791023#action_12791023
]
Uri Boness commented on SOLR-17:
--------------------------------
Having well defined XSD's for public services can be *extremely* helpful in
many aspects... together with proper version management they define the
contract between the users the the service. Some of the use cases that Chris
listed above are definitely valid and realistic. Moreover, XSD provides a
natural and proper documentation for the supported formats which any decent xml
editor can make use of and provide you with hints for writing the
solrconfig.xml and the schema.xml (for example).
That said... most of the xml formats in Solr are too generic to benefit from
XSD's. The only format where it makes sense is the schema.xml as it has an
expressive domain-driven structure. Unfortunately this is something you cannot
say for for the response formats and the solrconfig.xml where the
expressiveness lays within the *values* of the elements/attributes rather than
in the elements/attribute *names* themselves. XSD doesn't handle
element/attribute values very well.
> XSD for solr requests/responses
> -------------------------------
>
> Key: SOLR-17
> URL: https://issues.apache.org/jira/browse/SOLR-17
> Project: Solr
> Issue Type: Improvement
> Reporter: Mike Baranczak
> Priority: Minor
> Attachments: solr-complex.xml, solr-rev2.xsd, solr.xsd,
> UselessRequestHandler.java
>
>
> Attaching an XML schema definition for the responses and the update requests.
> I needed to do this for myself anyway, so I might as well contribute it to
> the project.
> At the moment, I have no plans to write an XSD for the config documents, but
> it wouldn't be a bad idea.
> TODO: change the schema URL. I'm guessing that Apache already has some sort
> of naming convention for these?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
