[
https://issues.apache.org/jira/browse/SOLR-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791137#action_12791137
]
Hoss Man commented on SOLR-17:
------------------------------
bq. There are actually a lot of useful things that could be done with an XSD.
I agree ... my comment (way back when) was more about what we should do with it
in a Solr release: converting it from a *.xsd attachment to a *.patch
attachment...
1. where should it live in source control? where should it live in the release
artifact?
2. what schema URI should we pick for identifying this? (i suspect apache.org
has a standard for this, so or at least precident from other projects, so we
should make sure we follow those examples before picking one arbitrarily
3. it won't do any good unless we make the XmlResponseWriter refrence the
schema URI so client tools can validate with it.
4. we need hooks in our own test system for validating responses we get back to
catch potential bugs (either in the schema itself, or in xml that might get
inadvertantly changed)
...etc...
> 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.
