I have a custom XSD parser that expects certain attributes in my element definitions. I don’t mean the elements in the resulting  xml have attributes, I mean actual xsd definition has these attributes. A simple example shown below

 

<element name="my_date" type="xs:date"   my_namespace:calendarPattern="yyyymmdd" />

My parser accepts a stream of data and uses the xsd schema to create a xml output. In this example it uses the calendarPattern attribute know how the incoming eight digits should be used to create a valid xml date. Sometimes the data could contain an alternate pattern like mmddyyyy, so a schema file is used to inform the parser. There are several dozen custom attributes that can be added, depending on the element type. Everything works great when the xsd is written by hand. But would love to be able to use the design view to graphically edit the schema. I need a way to enforce the inclusion of the calendarPattern attribute every time the element type is xs:date. Furthermore, I need to restrict the possible values for that attribute to be either the string  “yyyymmdd” or “mmddyyyy” as those are the two valid options my parser knows ho to deal with.

 

Ideally I could accomplish this with some sort of xml / xsd file that Studio uses to populate all of its components. But I would just as thrilled if there is a plugin API that I could use to extend this capability. My goal is to allow my customers, the users of the custom parser, to more easily create and edit xsd files. I want to be able to tell them to go buy a license for the graphical xsd editor, and with my extension they can create xsd files that will work with the parser. Is that something that is possible?