Did I respond to this? I'd vote for option2 to make a page, something like http://oozie.apache.org/XsdSchemaList.html and which has links to point http://oozie.apache.org/schemas/*.xsd which has the latest xsd files, we can manually copy the latest for now.
Regardless of option 1 or 2, I would like to see the xsd files in the following locations. http://oozie.apache.org/schemas/*.xsd (which has always the latest only) http://oozie.apache.org/schemas/{version nubmer}/*.xsd (they are generated as we release new versions.) e.g. http://www.w3.org/2002/08/xhtml/xhtml1-strict.xsd is the xsd of xhtml. and I kinda want to omit "doc" folder. I made a patch for review https://reviews.apache.org/r/8431/ Please let me know your feedback. On Thu, Dec 6, 2012 at 2:57 PM, Alejandro Abdelnur <[email protected]> wrote: > Makes sense > > * option 1: create a wiki with a table with all the schemas for > everything all versions and attach them there > * option 2: create an APT page with the same and republish the site > > option 1 is simpler and the effect would be the same, just the URL of > the XSD would be a bit ugly. > > Thoughts? > > On Thu, Dec 6, 2012 at 2:09 PM, Robert Kanter <[email protected]> > wrote: > > Good idea. > > > > Though if we put this as part of the generated site, it won't be on > > http://oozie.apache.org/docs/ until our next release, right? Perhaps we > > should have a url off the main site (e.g. > http://oozie.apache.org/schemas/) > > and just put the schemas in there for now; once we have the next release, > > we can have the url forward to the generated /docs/ location. This would > > allow us to make the schemas available now and also have a permanent > > "latest" link to the schemas so it doesn't keep changing (from the user's > > perspective) with every release (under the /docs/ location, it would be > > /docs/3.3.0/whatever, then /docs/3.3.1/whatever, etc). > > > > - Robert > > > > > > > > On Thu, Dec 6, 2012 at 12:59 PM, Jun Aoki <[email protected]> > wrote: > > > >> Done > >> > >> https://issues.apache.org/jira/browse/OOZIE-1120 > >> > >> > >> - jun > >> > >> > >> On Thu, Dec 6, 2012 at 12:05 PM, Mohammad Islam <[email protected]> > >> wrote: > >> > Good proposal. > >> > > >> > --Mohammad > >> > > >> > > >> > > >> > > >> > ________________________________ > >> > From: Alejandro Abdelnur <[email protected]> > >> > To: [email protected] > >> > Sent: Thursday, December 6, 2012 12:02 PM > >> > Subject: Re: Publish schemas on the web site ? > >> > > >> > Sounds good, we should added to the generated site. We'll need to play > >> > with the assembly that generates the docs. > >> > > >> > Clément or Jun Aoki, would you mind filing a JIRA for this? And of > >> > course, working on it would be welcome :) > >> > > >> > Cheers > >> > > >> > On Thu, Dec 6, 2012 at 11:11 AM, jun aoki <[email protected]> > >> wrote: > >> >> Forgot to mention one liner. In my previous email, <start> <action> > >> >> <map-reduce> <end> and all other elements defined in the xsd can be > >> >> suggested and autocompleted by the XML editors. It is very productive > >> for > >> >> users. > >> >> > >> >> > >> >> On Thu, Dec 6, 2012 at 11:06 AM, jun aoki <[email protected]> > >> wrote: > >> >> > >> >>> Alejandro, > >> >>> > >> >>> It will be good if the schema files are accessible from a real xml > >> file, > >> >>> but not in a part of web page. > >> >>> For example > >> >>> > >> > http://svn.apache.org/viewvc/oozie/trunk/client/src/main/resources/oozie-workflow-0.4.xsd?revision=1382193&view=co > >> >>> is exactly what Clement needs, but the URL is not ideal because it > has > >> a > >> >>> revision number and it should not be in a Subversion. > >> >>> Instead, it will be great if we could publish it shorter and more > >> permanent > >> >>> link type like > >> >>> http://oozie.apache.org/schemas/3.1.3/oozie-workflow-0.4.xsd > >> >>> > >> >>> What users benefit from it is they can open any XML editor (e.g. > >> Eclipse, > >> >>> XMLSpy) and start with schemaLocation, then the editors will > >> autocomplete > >> >>> and suggests possible elements and attributes. > >> >>> > >> >>> Clement, if it is what you want I can make a ticket and will see > what I > >> >>> can do. > >> >>> > >> >>> <?xml version="1.0" encoding="UTF-8"?> > >> >>> <workflow-app xmlns="uri:oozie:workflow:0.4" > >> >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > >> >>> xsi:schemaLocation="uri:oozie:workflow:0.4 > >> >>> http://oozie.apache.org/schemas/3.1.3/oozie-workflow-0.4.xsd"; > >> >>> name="flow1"> > >> >>> > >> >>> <start to="next1"/> > >> >>> <action name="action1"> > >> >>> <map-reduce></map-reduce> > >> >>> <ok to="ok1"/> > >> >>> <error to="error1"/> > >> >>> </action> > >> >>> > >> >>> <end name="end1"/> > >> >>> </workflow-app> > >> >>> > >> >>> > >> >>> > >> >>> On Thu, Dec 6, 2012 at 10:41 AM, Clément MATHIEU < > >> [email protected]>wrote: > >> >>> > >> >>>> On 2012-12-06 18:16, Alejandro Abdelnur wrote: > >> >>>> > >> >>>> Hi Alejandro, > >> >>>> > >> >>>> > >> >>>> They are avail in the Oozie docs: > >> >>>>> > >> >>>> > >> >>>> My goal is to use the schemas for validation purpose not > >> documentation. > >> >>>> By specifying the schema(s) location(s) in the document, or in a > >> catalog, > >> >>>> you allow the editor to validate the document on the fly and to > >> provide > >> >>>> auto-completion and documentation. > >> >>>> > >> >>>> If the schemas are not officially published, users have to deploy > the > >> >>>> schemas by themselves (or use the svn/github web interfaces when > >> possible). > >> >>>> > >> >>>> Am I the only one to find this feature valuable ? > >> >>>> > >> >>>> - Clément > >> >>>> > >> >>> > >> >>> > >> >
