Radiobutton equivalent in a schema

I have 2 radio buttons in my form with values "Day" and "Night". I would like to prefill these radio buttons from an XML/database using a schema.
Can someone tell me
1) How would I design the schema to accomodate the radio buttons ?
2) Out of the two what would I bind in the form ?
3) How will I setup the radio buttons to receive string values("Day"/"Night") as input ?
Thanks
Aditya

In the schema definition you can indicate that a node value is limited to Day or Night. These are the only two valid values that are allowed. When that gets inported into Designer we will create a dropdown list with the two values in it. There is no indication that you want a radio button, so you will have to go and adjust this after you import.
You can indicate what you want for the ON/Off values in the binding tab of the radiobuttonList. In Your case the On value for one radio button will be "Day" and the On Value for the other will be "Night". By querying the RadioButtonList it will tell you which one is On.

Similar Messages

Mapping to Equivalent in Output Schema

Hi
I have a output schema which includes a <Equivalent> element with several possible options, e.g.
        <Product>
    <Equivalent>
<Desktops>
<Laptops>
etc.
The XSD looks like this
<xs:element name="VendorCatalog">
    <xs:complexType>
      <xs:sequence maxOccurs="unbounded">
        <xs:element ref="tns:Product" />
        etc .....
<xs:element block="substitution" name="Product" type="tns:VendorProduct">
etc .....
<xs:complexType name="VendorProduct" abstract="true">
    <xs:sequence>
      <xs:element minOccurs="0" maxOccurs="1" name="PriceInformation">
        <xs:complexType>
  etc .....
<xs:complexType name="Laptops">
    <xs:annotation>
      <xs:documentation>Laptops</xs:documentation>
    </xs:annotation>
    <xs:complexContent mixed="false">
      <xs:extension base="VendorProduct">
        <xs:sequence>
1. I need to generate XML which starts like this with a xsi:type dependant on a value in the imput XML.
<Product xsi:type="Laptops" ProductCode="PROD123456">
  <PriceInformation>
   <Price Currency="GBP" UnitOfMeasure="Quantity" Value="9.99"/>
  </PriceInformation>
If I deceide that I want to generate a "Laptop", using the BizTalk Mapper - how do I assign a value to Product xsi:type ??
2. The structure Laptops has extension base="VendorProduct"
If I deceide that I want to generate a "Laptop" and I want to generate a field in the VendorProduct structure (eg price), do link to the field Price in the VendorProduct data structure or the Price field in the Laptops data structure?
Or is there an Idiot's guide to mapping to <Equivalent>
Thanks

If your schema contains information like..
<xs:element name="VendorCatalog">
<xs:complexType>
<xs:sequence maxOccurs="unbounded">
<xs:element ref="tns:Product" />
and..
<xs:complexType name="VendorProduct" abstract="true">
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1" name="PriceInformation">
<xs:complexType>
if you want to map the "xsi:type" attribute with name
of the node/element like..
<Product xsi:type="Laptops" ProductCode="PROD123456">
rather than the mapped node/element's value, then change the link's "Soruce Links" property value from its defualt "Copy text value" to "Copy name". So link the Laptop element from the soruce to the xsi:type attribute to the
destination schema using a standard link. Then select the link, go to its property and change the above mentioned property.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

BSI upgradation and customer version schema UTX0/UTAC

Hi All,
In upgrading of BSI notes 1022656 describes all steps and in 9 th step it is given as modify customer version schema UTX0/UTAC.
What exactly to be done there.
Please can any one answer this que?
Regards
Senthil

UTX0 is tax sub-schema for US , and UTAC is tax sub-schema for US using concurrent employment (you only use this if your company is implementing concurrent emp).
All you have to do is to go to either one of these schema (again, depending on whether you use concurr. emp or not) or equivalent custom sub-schema and change line 'UPAR1 BSI 70' to 'UPAR1 BSI 80'.
Rgds.

Project organization help needed

I work for a rather large health care company and we are just beginning our move from eGate to JCAPS. We have approximately 100 separate interfaces, each with an average of five eWays.
Our initial idea was to organize our JCAPS projects as follows:
Outer Project (equivalent to eGate schema)
Inner Project (equivalent to eGate eWay)
- collaboration
- connectivity map
- deployment profile
- any external files, schedulers, etc needed by the collaboration
Inner Project for OTD's
Inner Project for Queues and Topics
Inner Project for shared collaborations that are used by multiple projects (such as resending, journalling, etc)
My concern is if we make a change to a single project, when we go to export that project to our production system, we may be forced to export a lot more than we need.
I would like to know how others have organized their systems interfaces, and any issues they may have come up with.
Thank You
Steve

I would be wary of creating projects within projects.
The concept of project in JCAPS is nebulous.
Even though JCAPS allows you to nest projects within projects the nested projects are treated more like folders.
Like most other IDEs, projects are the ones created at root level.
Unlike most other IDEs JCAPS does not have the concept of project view and file view.
If you create an "Outer Project" and then inside it a bunch of "inner project" , JCAPS would treat the "Outer Project" as a project and all the inner projects as artifacts of this "Outer Project".
If any other project were to refer to any one of these "inner projects", then JCAPS will assume that this other project is dependent on the "outer project".
If you try to export this other project, it will export the whole "outer project" as a dependent project.
So, if possible, I would try to create all projects at root level especially if they are going to be referenced by other projects.
Use a flat structure rather than a hierarchical one. Use naming conventions to segregate and organize.
Instead of
ProjectA
ProjectA1
ProjectA2create
ProjectA_ProjectA1
ProjectA_ProjectA2
If this looks too cluttered you might want to consider branching to separate major projects
Also I would be careful of creating dependencies between projects.
Lets say you have a JCD which refers to an OTD in another shared project.
If somebody updates the OTD and creates a new version of the OTD, your JCD would automatically start referring to the new version.
Without your knowing a build will pick up the new OTD.
Of course if you know that a new version was created ,you can specify an older version of the OTD during a build.
Not so if you are editing the JCD. Here you will be stuck with the latest version.
This may or may not be what you want.
A better alternative would be to copy over the OTD to your project and use the local version.
Hope this helps.

Where clause in UPDATE statement is ignored

I have the following procedure that updates a field in a table. The only problem is that all rows in the table are updated like the update statement doesn't have a where clause. When I hard code the number (733) in the where clause it works as expected. Even if I don't alias the table name it still updates all rows in the table. Any ideas?
DECLARE
extlinkid CONSTANT NUMBER := 733;
newURL CONSTANT VARCHAR2(250) := 'mailto:[email protected]';
BEGIN
UPDATE SCHEMA.TABLE A
SET A.URL = newURL
WHERE (A.EXTLINKID = extlinkid);
commit;
END;

Oracle is resolving your variable extlinkid as the column in the table, so your UPDATE statement is equivalent to:
UPDATE schema.table a
SET a.url = newurl
WHERE (a.extlinkid = a.extlinkid);Which, of course, matches every record in the table. You need to change the name of your variable to something that is not a column name.
TTFN
John

What's the command to reset user's calendar (not csuser reset - schema2)

Hi,
We're running JES5. A user has problems accessing his calendar, and I wanted to reset the calendar's attributes.
I tried:
root@jescal sbin/ > ./csuser reset uid
but I got this error:
This command is not valid for schema 2. Please use the Communications Services Delegated Administrators Utility.
What's the correct command for schema2 ? probably commadmin user modify of somesuch, but can't find the right suboption in the delegated admin administration guide...
Thanks,
Tom.

shane_hjorth wrote:
tom_absi wrote:
We're running JES5. A user has problems accessing his calendar, and I wanted to reset the calendar's attributes.What precisely is the problem that they are having and how are they accessing their calendar data (Calendar Express, WCAP/Lightning, Outlook connector, Communications Express/UWC)? When logging on in the UWC, the calendar wouldn't be available.
But I think it was an ldap issue, I corrected a field and asked them to try again.
Somehow, the icscalendarowned attribute contained only:
uid$user name
whereas in all the other account I could found, it contained
uid$user name
uid
So I corrected that, I guess that was what caused the problem (not sure how this could happen...)
>
I tried:
root@jescal sbin/ > ./csuser reset uid
but I got this error:
This command is not valid for schema 2. Please use the Communications Services Delegated Administrators Utility.There is no equivalent command for schema 2. The "./csuser reset uid" is somewhat heavy handed, it removes all calendar related attributes from the account will likely "break" more then it will "fix".
Regards,
Shane.

IMAC/VERIZON DSL wireless connection

Has anyone been able to connect "wireless" an IMAC-24 (intel) with Verizon's DSL?
Mac OS X (10.4.8) XP - 2000 - NT
Imac 24 - Intel Core 2 Duo Mac OS X (10.4.8) XP - 2000 - NT

Thanks Donald, but I should had been more specific.
My equipment:
My Apple is an Imac-24 Intel Core 2 Duo with an Airport Extreme card w/ firmware version 4.80.76.1.
I network a Toshiba laptop w/MS XP using an Atheros AR5001+ wireless card, a couple of generic Intel PC w/MS XP using an Ethernet cable connections, A USB D-link print server using Ethernet cable.
My ISP is Verizon and the connection type is DSL.
Verizon provided me with a modem/router combo to use - a Westell VersaLink model 327W. This device is a specifically made for Verizon by Westell, thus Westell will not even talk to me.
The Problem:
I can not connect wireless my Imac to the network.
My Apple Airport is able to find the network and it makes it available for connection. When I try to connect I get the following message: "There was an error joining the AirPort network 'nameofmynetwork'." Can there be a more useless message?
Background:
All computers, ethernet and wireless, except for the Imac Wireless, connect and function properly. Thus, reasonably, I can eliminate a hardware problem with the possible exception of the Airport Card malfunctioning, but I doubt it since it seems to be recognizing my network. I don't have access to another AP (access Point) device to fully eliminate the AirPort Card from being the problem.
Not that it really matters, but an ethernet connect to my Apple works well.
The Westell only uses the Wire Equivalent Privacy (WEP) scheme. I understand the problem with this scheme in which, unfortunately, it wasn't very standarized and hashing of passwords could occur among devices from different vendors producing non-matching encryption. I have tried all kinds of combinations open, shared, 64, 128, hex, ascii, and I even reconfigured my network to be totally unsecure (Eliminated password, mac table, etc, etc.) but I still can not connect.
I have called Apple, Verizon, Westell and exhausted the capabilities of their "technical support" - that is, we went through their entire "Scripted" Q&A system without a solution, and I could never get them to scalate my problem to a real tech person. - They are all pointing the finger at each other, except for Westell who basically said: "NO MY PROBLEM! We build this device specifically for Verizon and we provide no support"
I went to the local store and spoke with the resident guru but, all he tried to impress on me was how complicated networking was. To that I left, I couldn't take it anymore, I am not looking for a network guru, just someone who knows what are the parameters I should use so that that the Apple's version of the Airport Extreme can communicate with Verizon-Westell VersaLink 327W or that maybe can confirm that this two things will never talk to each other.
To anyone reading the above, I apologize if sounded cranky.
Mac OS X (10.4.8) XP - 2000 - NT
Mac OS X (10.4.8) XP - 2000 - NT
Mac OS X (10.4.8) XP - 2000 - NT

How: multiple insert stmt's in Database Express edition SQL commands GUI?

I have installed the Express 10g version today and played around with it for a while.
If I go to the SQL commands GUI and enter one insert like this:
INSERT INTO pageit (PagID, PagParent, PagName, PagActive) VALUES (19, 17, 'Mango tree', 1)
then it works nicely:
But if I do this:
INSERT INTO pageit (PagID, PagParent, PagName, PagActive) VALUES (20, 17, 'Grape trees', 1);
INSERT INTO pageit (PagID, PagParent, PagName, PagActive) VALUES (21, 16, 'Animals', 1);
Then it says:
ORA-00911: invalid character
Looks like semicolon is not allowed,
but if I remove the semicolon then it says;
ORA-00905: missing keyword
Is there a way to use multiple insert statements in one go in this GUI at all?
If not, could someone please recommend how I do this.
I have exported thousands of insert lines from MySql and I would like to get them into my newly created Oracle table without having to type one line at the time in this gui.
Any suggestions?
Then if there is a nice WEB GUI like phpmyadmin for Oracle then I would like to know about that to? (Preferably free)

I've not done a lot with the express edition, so there may be tools I'm not aware of. There is a dedicated Express Edition forum that may be more helpful for some of these questions.
I would normally use the command-line SQL*Plus to run a script with a large number of SQL statements. I'd generally prefer, though, to get a comma-separated data file from the other system and load that into Oracle using SQL*Loader for efficiency reasons.
In Oracle, you would normally only want a single database on a single physical machine. I know in SQL Server that what they call a "database" is roughly equivalent to a "schema" in Oracle, which is created by creating a new user.
Justin

Error while registering a schema

Hi :
I get this error while I am registering my XML schema.
ERROR at line 1:
ORA-31154: invalid XML document
ORA-19202: Error occurred in XML processing
LPX-00217: invalid character 0 (\u0000)
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 0
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 26
ORA-06512: at line 2
I have marked in bold the part of the schema which bombs while registering. (When I validate this scehms in XML Spy it says it is a valid schems)
The Schema definition is as follows :
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="urn:uk:ac:ebi:spml" xmlns="urn:uk:ac:ebi:spml" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
<xs:include schemaLocation="feature.xsd"/>

<xs:complexType name="evidenceListType">
<xs:annotation>
<xs:documentation>The list of all evidences stored in one entry.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="evidence" type="evidenceType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="evidenceType">
<xs:annotation>
<xs:documentation>The evidence element is equivalent to the actual evidence (**EV line).</xs:documentation>
</xs:annotation>
<xs:attribute name="category" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="curator"/>
<xs:enumeration value="import"/>
<xs:enumeration value="program"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="ANU-2DPAGE_ADD"/>
<xs:enumeration value="COMPLUYEAST-2DPAGE_ADD"/>
<xs:enumeration value="Curator"/>
<xs:enumeration value="EMBL"/>
<xs:enumeration value="Experimental"/>
<xs:enumeration value="FLYBASE_ADD"/>
<xs:enumeration value="GENEW_ADD"/>
<xs:enumeration value="GOA_ADD"/>
<xs:enumeration value="GRAMENE_ADD"/>
<xs:enumeration value="HSSP_ADD"/>
<xs:enumeration value="Import"/>
<xs:enumeration value="MEROPS_ADD"/>
<xs:enumeration value="MGD_ADD"/>
<xs:enumeration value="Opinion"/>
<xs:enumeration value="PHCI-2DPAGE_ADD"/>
<xs:enumeration value="PMMA-2DPAGE_ADD"/>
<xs:enumeration value="ProtImp"/>
<xs:enumeration value="REBASE_ADD"/>
<xs:enumeration value="Rulebase"/>
<xs:enumeration value="SGD_ADD"/>
<xs:enumeration value="SIENA-2DPAGE_ADD"/>
<xs:enumeration value="SignalP"/>
<xs:enumeration value="Similarity"/>
<xs:enumeration value="TRANSFAC_ADD"/>
<xs:enumeration value="TrEMBL"/>
<xs:enumeration value="ZFIN_ADD"/>
<xs:enumeration value="internal"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="attribute" type="xs:string" use="optional"/>
<xs:attribute name="date" type="xs:date" use="required"/>
<xs:attribute name="evID" type="xs:string" use="required"/>
</xs:complexType>


<xs:complexType name="proteinType">
<xs:sequence>
<xs:element name="name" type="nameType" maxOccurs="unbounded"/>
<xs:element name="iRefList" type="iRefListType" minOccurs="0">
<xs:annotation>
<xs:documentation>This is referring to a possible EC number (ENZYME database cross reference).</xs:documentation>
</xs:annotation>
</xs:element>
<xs:choice minOccurs="0">
<xs:element name="componentList">
<xs:annotation>
<xs:documentation>The component list is equivalent to the CONTAINS section of the DE line.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="component" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="nameType" maxOccurs="unbounded"/>
<xs:element name="iRefList" type="iRefListType" minOccurs="0">
<xs:annotation>
<xs:documentation>This is referring to a possible EC number (ENZYME database cross reference).</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="domainList">
<xs:annotation>
<xs:documentation>The domain list is equivalent to the INCLUDES section of the DE line.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="domain" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="nameType" maxOccurs="unbounded"/>
<xs:element name="iRefList" type="iRefListType" minOccurs="0">
<xs:annotation>
<xs:documentation>This is referring to a possible EC number (ENZYME database cross reference).</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:choice>
<xs:element name="evList" type="evListType" minOccurs="0">
<xs:annotation>
<xs:documentation>This contains all evidence that are connected to the complete DE line (For the time being also the ones that couldn't be resolved to a single name).</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
<xs:attribute name="evidenceStatus">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="hypothetical"/>
<xs:enumeration value="putative"/>
<xs:enumeration value="possible"/>
<xs:enumeration value="probable"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="type">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="fragment"/>
<xs:enumeration value="fragments"/>
<xs:enumeration value="version1"/>
<xs:enumeration value="version2"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>


<xs:complexType name="sptrProperties">
<xs:complexContent>
<xs:restriction base="propertyBaseType">
<xs:attribute name="name" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="edition"/>
<xs:enumeration value="entry name"/>
<xs:enumeration value="evidence"/>
<xs:enumeration value="gene designation"/>
<xs:enumeration value="last revision date"/>
<xs:enumeration value="match status"/>
<xs:enumeration value="match status hits"/>
<xs:enumeration value="method"/>
<xs:enumeration value="organism name"/>
<xs:enumeration value="pdb accession"/>
<xs:enumeration value="protein sequence ID"/>
<xs:enumeration value="status"/>
<xs:enumeration value="term"/>
<xs:enumeration value="type"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="value" type="xs:string" use="required"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:simpleType name="allSPTrDbsType">
<xs:restriction base="xs:string">
<xs:enumeration value="ANU-2DPAGE"/>
<xs:enumeration value="Aarhus/Ghent-2DPAGE"/>
<xs:enumeration value="COMPLUYEAST-2DPAGE"/>
<xs:enumeration value="DictyDb"/>
<xs:enumeration value="EC"/>
<xs:enumeration value="ECO2DBASE"/>
<xs:enumeration value="EMBL"/>
<xs:enumeration value="EcoGene"/>
<xs:enumeration value="FlyBase"/>
<xs:enumeration value="GO"/>
<xs:enumeration value="Genew"/>
<xs:enumeration value="GlycoSuiteDB"/>
<xs:enumeration value="Gramene"/>
<xs:enumeration value="HIV"/>
<xs:enumeration value="HSC-2DPAGE"/>
<xs:enumeration value="HSSP"/>
<xs:enumeration value="InterPro"/>
<xs:enumeration value="Leproma"/>
<xs:enumeration value="ListiList"/>
<xs:enumeration value="MAIZE-2DPAGE"/>
<xs:enumeration value="MEROPS"/>
<xs:enumeration value="MGD"/>
<xs:enumeration value="MIM"/>
<xs:enumeration value="MaizeDB"/>
<xs:enumeration value="MypuList"/>
<xs:enumeration value="PDB"/>
<xs:enumeration value="PHCI-2DPAGE"/>
<xs:enumeration value="PhosSite"/>
<xs:enumeration value="PIR"/>
<xs:enumeration value="PMMA-2DPAGE"/>
<xs:enumeration value="PRINTS"/>
<xs:enumeration value="PROSITE"/>
<xs:enumeration value="Pfam"/>
<xs:enumeration value="ProDom"/>
<xs:enumeration value="REBASE"/>
<xs:enumeration value="SGD"/>
<xs:enumeration value="SMART"/>
<xs:enumeration value="SWISS-2DPAGE"/>
<xs:enumeration value="Siena-2DPAGE"/>
<xs:enumeration value="StyGene"/>
<xs:enumeration value="SubtiList"/>
<xs:enumeration value="TIGR"/>
<xs:enumeration value="TIGRFAMs"/>
<xs:enumeration value="TRANSFAC"/>
<xs:enumeration value="TubercuList"/>
<xs:enumeration value="WormPep"/>
<xs:enumeration value="ZFIN"/>
</xs:restriction>
</xs:simpleType>

<xs:complexType name="sptrDbReferenceType">
<xs:complexContent>
<xs:restriction base="dbReferenceBaseType">
<xs:sequence>
<xs:element name="property" type="propertyBaseType" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="db" type="allSPTrDbsType" use="required"/>
<xs:attribute name="id" type="xs:string" use="required"/>
<xs:attribute name="iRefID" type="xs:string" use="required"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>




<xs:complexType name="taxonomyDBType">
<xs:annotation>
<xs:documentation>This dbRef type is meant for taxonomy database such as the NCBI taxonomy database.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:restriction base="dbReferenceBaseType">
<xs:sequence>
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="db" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="NCBI Taxonomy"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="id" type="xs:string" use="required"/>
<xs:attribute name="iRefID" type="xs:string" use="required"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>



<xs:complexType name="nameType" mixed="true">
<xs:annotation>
<xs:documentation>The name type is used for all names occuring in an entry.</xs:documentation>
</xs:annotation>
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="organismNameType">
<xs:annotation>
<xs:documentation>The name type is used for source organism names.</xs:documentation>
</xs:annotation>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="common name"/>
<xs:enumeration value="full name"/>
<xs:enumeration value="scientific name"/>
<xs:enumeration value="synonym"/>
<xs:enumeration value="abbreviation"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:simpleContent>
</xs:complexType>


<xs:complexType name="geneLocationListType">
<xs:annotation>
<xs:documentation>Defines the locations/origins of the shown sequence (OG line).</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="geneLocation" type="geneLocationBaseType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="geneLocationBaseType" abstract="true">
<xs:annotation>
<xs:documentation>The location's supertype.</xs:documentation>
</xs:annotation>
</xs:complexType>
<xs:complexType name="organelleLocationType">
<xs:annotation>
<xs:documentation>This type stores the location if it's a chloroplast, cyanelle or mitochondrium.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="geneLocationBaseType">
<xs:sequence>
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="chloroplast"/>
<xs:enumeration value="cyanelle"/>
<xs:enumeration value="mitochondrion"/>
<xs:enumeration value="nucleomorph"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="plasmidLocationType">
<xs:annotation>
<xs:documentation>This type stores the location if it's a plasmid including all plasmid names.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="geneLocationBaseType">
<xs:sequence>
<xs:element name="name" type="nameType"/>
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="plasmid"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>


<xs:complexType name="baseFeatureType" mixed="true">
<xs:annotation>
<xs:documentation>The feature's supertype from which all other feature element types are derived.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:group ref="locationGroup" minOccurs="0"/>
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="description" type="xs:string" use="optional"/>
</xs:complexType>
<xs:complexType name="featureType" mixed="true">
<xs:annotation>
<xs:documentation>Currently there is only one basic feature type, but this will change in future with enhancement of the FT line parsers.</xs:documentation>
</xs:annotation>
<xs:complexContent mixed="true">
<xs:extension base="baseFeatureType">
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="active site"/>
<xs:enumeration value="binding site"/>
<xs:enumeration value="calcium-binding region"/>
<xs:enumeration value="glycosylation site"/>
<xs:enumeration value="chain"/>
<xs:enumeration value="sequence conflict"/>
<xs:enumeration value="disulfide bond"/>
<xs:enumeration value="DNA-binding region"/>
<xs:enumeration value="domain"/>
<xs:enumeration value="helix"/>
<xs:enumeration value="initiator methionine"/>
<xs:enumeration value="lipid moiety-binding region"/>
<xs:enumeration value="metal ion-binding site"/>
<xs:enumeration value="modified residue"/>
<xs:enumeration value="mutagenesis site"/>
<xs:enumeration value="non-consecutive residues"/>
<xs:enumeration value="non-terminal residue"/>
<xs:enumeration value="nucleotide phosphate-binding region"/>
<xs:enumeration value="peptide"/>
<xs:enumeration value="propeptide"/>
<xs:enumeration value="repeat"/>
<xs:enumeration value="selenocysteine"/>
<xs:enumeration value="signal peptide"/>
<xs:enumeration value="site"/>
<xs:enumeration value="strand"/>
<xs:enumeration value="thioether bond"/>
<xs:enumeration value="thiolester bond"/>
<xs:enumeration value="transit peptide"/>
<xs:enumeration value="transmembrane region"/>
<xs:enumeration value="turn"/>
<xs:enumeration value="unsure residue"/>
<xs:enumeration value="sequence variant"/>
<xs:enumeration value="splice variant"/>
<xs:enumeration value="zinc finger region"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>


<xs:complexType name="baseCommentType" abstract="true" mixed="true">
<xs:annotation>
<xs:documentation>The comment's supertype from which all other comment element types are derived</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="commentType" mixed="true">
<xs:annotation>
<xs:documentation>Basic comment type which contains only text and evidence tags, no extra structure/attributes.</xs:documentation>
</xs:annotation>
<xs:complexContent mixed="true">
<xs:extension base="baseCommentType">
<xs:attribute name="topic" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="alternative products"/>
<xs:enumeration value="biotechnology"/>
<xs:enumeration value="catalytic activity"/>
<xs:enumeration value="caution"/>
<xs:enumeration value="cofactor"/>
<xs:enumeration value="database"/>
<xs:enumeration value="developmental stage"/>
<xs:enumeration value="disease"/>
<xs:enumeration value="domain"/>
<xs:enumeration value="enzyme regulation"/>
<xs:enumeration value="function"/>
<xs:enumeration value="induction"/>
<xs:enumeration value="miscellaneous"/>
<xs:enumeration value="pathway"/>
<xs:enumeration value="pharmaceutical"/>
<xs:enumeration value="polymorphism"/>
<xs:enumeration value="ptm"/>
<xs:enumeration value="similarity"/>
<xs:enumeration value="subcellular location"/>
<xs:enumeration value="subunit"/>
<xs:enumeration value="tissue specificity"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>

<xs:complexType name="massSpecType" mixed="true">
<xs:annotation>
<xs:documentation>The information of the mass spectrometry comment is stored in the attributes:
-molWeight (molecular weight)
-mwError (error of the molecular weight)
-msMethod (the method used for the mass spectrometry)
-range (which amino acids were messured. It's not mentioned if the complete sequence as shown in the entry was messured)</xs:documentation>
</xs:annotation>
<xs:complexContent mixed="true">
<xs:extension base="baseCommentType">
<xs:sequence minOccurs="0">
<xs:element name="range" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:attribute name="begin" type="xs:int" use="required"/>
<xs:attribute name="end" type="xs:int" use="required"/>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="topic" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="mass spectrometry"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="molWeight" type="xs:float" use="required"/>
<xs:attribute name="mwError" type="xs:string" use="optional"/>
<xs:attribute name="msMethod" type="xs:string" use="optional"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>



<xs:complexType name="scopeListType">
<xs:annotation>
<xs:documentation>Contains a list of scopes regarding a citation. There is no classification currently, but will be introduced in future. (RP lines).</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="scope" type="xs:string" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="sourceDataType">
<xs:annotation>
<xs:documentation>Contains specific information about the sequence source that was used in the ciation (RC lines).</xs:documentation>
</xs:annotation>
<xs:choice maxOccurs="unbounded">
<xs:element name="species">
<xs:complexType>
<xs:sequence>
<xs:element name="iRefList" type="iRefListType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="strain">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="xs:string" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="plasmid" type="xs:string"/>
<xs:element name="transposon" type="xs:string"/>
<xs:element name="tissue" type="xs:string"/>
</xs:choice>
</xs:complexType>
<xs:group name="sptrCitationGroup">
<xs:annotation>
<xs:documentation>Groups the scope and source data lists.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="scopeList" type="scopeListType"/>
<xs:element name="source" type="sourceDataType" minOccurs="0"/>
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
</xs:group>

<xs:complexType name="referenceType">
<xs:annotation>
<xs:documentation>Stores all information of the reference block in SPTr (RN, RP, RC, RX, RA, RT and RL line).</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="citation" type="citationType"/>
<xs:group ref="sptrCitationGroup"/>
</xs:sequence>
<xs:attribute name="iRefID" type="xs:string" use="required"/>
</xs:complexType>


<xs:complexType name="entryType">
<xs:annotation>
<xs:documentation>A (public) SPTr entry</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="secondaryAccessionList" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="accession" type="xs:string" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="secondaryNameList" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="xs:string" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="protein" type="proteinType"/>
<xs:element name="geneList" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="gene" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="nameType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="organismList">
<xs:complexType>
<xs:sequence>
<xs:element name="organism" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="organismNameType" maxOccurs="unbounded"/>
<xs:element name="dbReferenceList">
<xs:complexType>
<xs:sequence>
<xs:element name="dbReference" type="taxonomyDBType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="lineage" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="taxon" type="xs:string" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="iRefID" type="xs:string" use="optional"/>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="geneLocationList" type="geneLocationListType" minOccurs="0"/>
<xs:element name="referenceList">
<xs:complexType>
<xs:choice maxOccurs="unbounded">
<xs:element name="reference" type="referenceType"/>
</xs:choice>
</xs:complexType>
</xs:element>
<xs:element name="commentList" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="comment" type="baseCommentType" nillable="true" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="dbReferenceList" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="dbReference" type="sptrDbReferenceType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="keywordList" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="keyword" maxOccurs="unbounded">
<xs:complexType mixed="true">
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="evList" type="evListType"/>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="featureList" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="feature" type="featureType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="evidenceList" type="evidenceListType" minOccurs="0"/>
<xs:element name="sequence">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="length" type="xs:integer" use="required"/>
<xs:attribute name="weight" type="xs:integer" use="required"/>
<xs:attribute name="crc64" type="xs:string" use="required"/>
<xs:attribute name="lastUpdate" type="xs:date" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="accession" type="xs:string" use="required"/>
<xs:attribute name="database" type="xs:string" use="required"/>
<xs:attribute name="name" type="xs:string" use="required"/>
<xs:attribute name="firstPublic" type="xs:date" use="required"/>
<xs:attribute name="lastAnnotationUpdate" type="xs:date" use="required"/>
</xs:complexType>


<xs:element name="sptr">
<xs:annotation>
<xs:documentation>Contains a collection of Swiss-Prot entries.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="entry" type="entryType" maxOccurs="unbounded">
<xs:key name="referenceKey">
<xs:annotation>
<xs:documentation>Defines the key constraint for iRefID attribute where possible in the entry (citations are missing still).</xs:documentation>
</xs:annotation>
<xs:selector xpath="organismList/organism|dbReferenceList/dbReference"/>
<xs:field xpath="iRefID"/>
</xs:key>
<xs:key name="evidenceReferenceKey">
<xs:annotation>
<xs:documentation>Defines the key constraint for evID attribute in evidence elements.</xs:documentation>
</xs:annotation>
<xs:selector xpath="evidenceList/evidence"/>
<xs:field xpath="evID"/>
</xs:key>

<xs:keyref name="evidenceReference" refer="evidenceReferenceKey">
<xs:selector xpath=".//ev"/>
<xs:field xpath="ref"/>
</xs:keyref> 
</xs:element>
<xs:element name="copyright">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="iRefID" type="xs:string" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
feature.xsd is below :
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="urn:uk:ac:ebi:spml" xmlns="urn:uk:ac:ebi:spml" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">

<xs:complexType name="positionType">
<xs:attribute name="position" type="xs:unsignedLong" use="required"/>
</xs:complexType>
<xs:complexType name="gapType">
<xs:complexContent>
<xs:extension base="positionType">
<xs:attribute name="length" type="xs:unsignedLong" use="optional"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="intervalType">
<xs:attribute name="begin" type="xs:unsignedLong" use="required"/>
<xs:attribute name="end" type="xs:unsignedLong" use="required"/>
</xs:complexType>
<xs:complexType name="baseLocationType">
<xs:annotation>
<xs:documentation>A location can be either a position, site or have a start and end, only start, only end or is an empty element if the position is unknown.
The iRef attribute points to an external database reference (equivalent to J00194:100..202 in EMBL).</xs:documentation>
</xs:annotation>
<xs:choice>
<xs:sequence>
<xs:choice minOccurs="0">
<xs:element name="begin" type="positionType"/>
<xs:element name="beginInterval" type="intervalType"/>
</xs:choice>
<xs:choice minOccurs="0">
<xs:element name="end" type="positionType"/>
<xs:element name="endInterval" type="intervalType"/>
</xs:choice>
</xs:sequence>
<xs:element name="position" type="positionType"/>
<xs:element name="positionInterval" type="intervalType"/>
<xs:element name="site" type="positionType"/>
</xs:choice>
<xs:attribute name="iRef" type="xs:string" use="optional"/>
<xs:attribute name="complement" type="xs:boolean" use="optional" default="false"/>
</xs:complexType>
<xs:complexType name="fuzzyLocationType">
<xs:annotation>
<xs:documentation>A location can be either a position, site or have a start and end, only start, only end or is an empty element if the position is unknown.
The iRef attribute points to an external database reference (equivalent to J00194:100..202 in EMBL).</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="baseLocationType">
<xs:attribute name="fuzzy" use="optional" default="none">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="left"/>
<xs:enumeration value="right"/>
<xs:enumeration value="both"/>
<xs:enumeration value="none"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="joinType">
<xs:sequence>
<xs:choice maxOccurs="unbounded">
<xs:element name="location" type="baseLocationType"/>
<xs:element name="gap" type="gapType"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="fuzzy" use="optional" default="none">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="left"/>
<xs:enumeration value="right"/>
<xs:enumeration value="both"/>
<xs:enumeration value="none"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="complement" type="xs:boolean" use="optional" default="false"/>
</xs:complexType>
<xs:group name="locationGroup">
<xs:choice>
<xs:element name="location" type="fuzzyLocationType"/>
<xs:element name="join" type="joinType"/>
</xs:choice>
</xs:group>


<xs:complexType name="evListType">
<xs:annotation>
<xs:documentation>Contains a list of evidence tags.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="ev" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>The ev element is equivalent to an evidence tags.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:attribute name="ref" type="xs:string" use="required"/>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>


<xs:complexType name="propertyBaseType">
<xs:attribute name="name" type="xs:string" use="required"/>
<xs:attribute name="value" type="xs:string" use="required"/>
</xs:complexType>
<xs:complexType name="dbReferenceBaseType" abstract="true">
<xs:annotation>
<xs:documentation>DR line</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="property" type="propertyBaseType" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="db" type="xs:string" use="required"/>
<xs:attribute name="id" type="xs:string" use="required"/>
<xs:attribute name="iRefID" type="xs:string" use="required"/>
</xs:complexType>
<xs:complexType name="citationDBType">
<xs:annotation>
<xs:documentation>This dbRef type is meant for citation database such as PubMed and MEDLINE.</xs:documentation>
<xs:documentation>This dbRef type is meant for citation database such as PubMed and MEDLINE.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:restriction base="dbReferenceBaseType">
<xs:sequence>
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="db" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="PubMed"/>
<xs:enumeration value="MEDLINE"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="id" type="xs:string" use="required"/>
<xs:attribute name="iRefID" type="xs:string" use="required"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>


<xs:group name="citationContentGroup">
<xs:sequence>
<xs:element name="authorList" type="nameListType"/>
<xs:element name="dbReferenceList" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="dbReference" type="citationDBType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="iRefList" type="iRefListType" minOccurs="0"/>
</xs:sequence>
</xs:group>
<xs:complexType name="citationType" abstract="true">
<xs:annotation>
<xs:documentation>The citation super type</xs:documentation>
</xs:annotation>
<xs:attribute name="iRefID" type="xs:string" use="optional"/>
</xs:complexType>
<xs:complexType name="bookType">
<xs:annotation>
<xs:documentation>Stores all information about a book.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="citationType">
<xs:sequence>
<xs:element name="title" type="freeTextType" minOccurs="0"/>
<xs:element name="bookTitle" type="xs:string"/>
<xs:element name="editorList" type="nameListType" minOccurs="0"/>
<xs:group ref="citationContentGroup"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="book"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="volume" type="xs:string" use="optional"/>
<xs:attribute name="year" type="xs:int" use="required"/>
<xs:attribute name="first" type="xs:unsignedInt" use="required"/>
<xs:attribute name="last" type="xs:unsignedInt" use="required"/>
<xs:attribute name="ISDN" type="xs:string" use="optional"/>
<xs:attribute name="publisher" type="xs:string" use="required"/>
<xs:attribute name="city" type="xs:string" use="required"/>
<xs:attribute name="country" type="xs:string" use="optional"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="electronicType">
<xs:annotation>
<xs:documentation>Stores all information about a so-called online citation.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="citationType">
<xs:sequence>
<xs:element name="title" type="freeTextType" minOccurs="0"/>
<xs:group ref="citationContentGroup"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="online journal article"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="volume" type="xs:string" use="optional"/>
<xs:attribute name="year" type="xs:int" use="required"/>
<xs:attribute name="issue" type="xs:unsignedInt" use="optional">
<xs:annotation>
<xs:documentation>Currently used only in the "Worm Breeder's Gazette".</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="articleNo" type="xs:unsignedInt" use="required">
<xs:annotation>
<xs:documentation>Currently used only in the "Worm Breeder's Gazette".</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="name" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>Can be used for stating the name of the electronic journal.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="incompleteJournalType">
<xs:annotation>
<xs:documentation>Stores all information about an incomplete journal article.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="citationType">
<xs:sequence>
<xs:element name="title" type="freeTextType" minOccurs="0"/>
<xs:group ref="citationContentGroup"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="incomplete journal article"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="first" type="xs:string" use="optional"/>
<xs:attribute name="last" type="xs:string" use="optional"/>
<xs:attribute name="volume" type="xs:string" use="optional"/>
<xs:attribute name="year" type="xs:int" use="optional"/>
<xs:attribute name="name" type="xs:string" use="optional"/>
<xs:attribute name="ISSN" type="xs:string" use="optional"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="journalType">
<xs:annotation>
<xs:documentation>Stores all information about a journal article.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="citationType">
<xs:sequence>
<xs:element name="title" type="freeTextType"/>
<xs:group ref="citationContentGroup"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="journal article"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="first" type="xs:string" use="required"/>
<xs:attribute name="last" type="xs:string" use="required"/>
<xs:attribute name="volume" type="xs:string" use="required"/>
<xs:attribute name="year" type="xs:int" use="required"/>
<xs:attribute name="name" type="xs:string" use="required"/>
<xs:attribute name="ISSN" type="xs:string" use="optional"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="observationType">
<xs:annotation>
<xs:documentation>Stores all information about a citation of the type "Unpublished Observations".</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="citationType">
<xs:sequence>
<xs:group ref="citationContentGroup"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="unpublished observations"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="date" type="xs:gYearMonth" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="patentType">
<xs:annotation>
<xs:documentation>Stores all information about a patent.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="citationType">
<xs:sequence>
<xs:element name="title" type="freeTextType" minOccurs="0"/>
<xs:group ref="citationContentGroup" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="patent"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="number" type="xs:string" use="required"/>
<xs:attribute name="date" type="xs:date" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="resultType">
<xs:annotation>
<xs:documentation>Stores all information about a citation of the type "Unpublished Results". For the unpublished results type it is necessary that the title element is optional, since one won't find this data in flat files (and might not be added in future, either).</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="citationType">
<xs:sequence>
<xs:element name="title" type="freeTextType" minOccurs="0"/>
<xs:group ref="citationContentGroup"/>
<xs:choice>
<xs:element name="citedInBook" type="bookType"/>
<xs:element name="citedInArticle" type="incompleteJournalType">
<xs:annotation>
<xs:documentation>The type of this element needs to be the incompleteJournalType as the SP-ML converter cannot create the title yet (it doesn't evaluate the PubMed database).</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="citedInElectronic" type="electronicType"/>
<xs:element name="citedInThesis" type="thesisType"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="unpublished results"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="submissionType">
<xs:annotation>
<xs:documentation>Stores all information about a submission to one of the following databases:
-EMBL/GenBank/DDBJ databases
-SWISS-PROT data bank
-HIV data bank
-PDB data bank
-PIR data bank</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="citationType">
<xs:sequence>
<xs:element name="title" type="freeTextType" minOccurs="0"/>
<xs:group ref="citationContentGroup"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="submission"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="date" type="xs:gYearMonth" use="required"/>
<xs:attribute name="db" type="xs:string" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="thesisType">
<xs:annotation>
<xs:documentation>Stores all information about a thesis.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="citationType">
<xs:sequence>
<xs:element name="title" type="freeTextType" minOccurs="0"/>
<xs:group ref="citationContentGroup"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="thesis"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="institute" type="xs:string" use="required"/>
<xs:attribute name="city" type="xs:string" use="optional"/>
<xs:attribute name="country" type="xs:string" use="required"/>
<xs:attribute name="year" type="xs:int" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="groupType">
<xs:attribute name="name" type="xs:string" use="required"/>
</xs:complexType>
<xs:complexType name="personType">
<xs:attribute name="name" type="xs:string" use="required"/>
<xs:attribute name="forename" type="xs:string" use="optional"/>
<xs:attribute name="surname" type="xs:string" use="optional"/>
</xs:complexType>
<xs:complexType name="nameListType">
<xs:choice maxOccurs="unbounded">
<xs:element name="person" type="personType"/>
<xs:element name="group" type="groupType"/>
</xs:choice>
</xs:complexType>

<xs:complexType name="freeTextType" mixed="true">
<xs:sequence minOccurs="0">
<xs:element name="iRefList" type="iRefListType"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="iRefType">
<xs:attribute name="type" type="xs:string" use="optional"/>
<xs:attribute name="ref" type="xs:string" use="required"/>
</xs:complexType>
<xs:complexType name="iRefListType">
<xs:sequence>
<xs:element name="iRef" type="iRefType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:schema>

We've found two errors, both which can be worked around.
Currently there is a bug in XMLDB which fails to create a unique name for the case where the subtype and supertype both define an element or attribute with the same name. In your schema both baseCommentType defines an element called evList. massSpecType extends baseCommentType and adds an element with the same name.
This causes an error creating the massSpecType SQLType. The workaround for this is to declare the XMLDB namespace in the schema and use the xdb:SQLName annotation to define a unique name for the second element.
Eg
     <xs:complexType name="massSpecType" mixed="true">
          <xs:complexContent mixed="true">
               <xs:extension base="baseCommentType">
                    <xs:sequence minOccurs="0">
                         <xs:element name="range" minOccurs="0" maxOccurs="unbounded">
                              <xs:complexType>
                                   <xs:attribute name="begin" type="xs:int" use="required"/>
                                   <xs:attribute name="end" type="xs:int" use="required"/>
                              </xs:complexType>
                         </xs:element>
                         <xs:element name="evList" type="evListType" minOccurs="0" xdb:SQLName="EVLIST1"/>
                    </xs:sequence>
                    <xs:attribute name="topic" use="required">
                         <xs:simpleType>
                              <xs:restriction base="xs:string">
                                   <xs:enumeration value="mass spectrometry"/>
                              </xs:restriction>
                         </xs:simpleType>
                    </xs:attribute>
                    <xs:attribute name="molWeight" type="xs:float" use="required"/>
                    <xs:attribute name="mwError" type="xs:string" use="optional"/>
                    <xs:attribute name="msMethod" type="xs:string" use="optional"/>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
Eg...
The second issue with the /u0000 is caused by the key/key reference definitions in the schema.
If you comment them out the schema will register

Is there a way to determine the equivalent ANSI C code from a Labview project?

I'm a complete beginner to Labview. I have this fairly complex Labview project that was used to create a DLL which matlab could call to control my PCI-6534 card without having to know the NIDAQmx calls.
I'm in the process of figuring out how to make those NIDAQmx calls directly from Matlab but I'm not getting the same results as when I call this DLL mentioned above so I thought I'd try to make sense of the Labview project VIs. I'm starting to make sense of the overall scheme of the VIs, but I'd like to be able to run the project, step through it, and perhaps see the NIDAQmx commands (or something equivalent so I can determine how to call the NIDAQmx commands within Matlab).
Is this possible to do?
Thanks,
Jason
Solved!
Go to Solution.

Yes. The toolbar allows you to turn on highlighting so you can run the VI and see the contents of wires. You can put probes on wires. You can single-step through code. All of this is explained in the LabVIEW Help under Fundamantals -> Running and DEbugging VIs -> Concepts -> Debugging Techniques.
In regards to the implied question in the title of your post, no you cannot directly convert LabVIEW code to C in the development environment. Yes, there are tools to convert LabVIEW to C, but that's intended for microprocessors.

SQL Equivalent in Berkeley DB

Hi,
In SQL, we can create a table from the result of a select statement as follows:
CREATE TABLE table3 AS SELECT * FROM table1, table2 WHERE ...
which is called a "materialized view" because the results of the query are not processed on the fly, but are stored in database table for further processing.
I would like to do something equivalent in Berkeley DB, where the I have some databases that already exist, and I want to perform some processing on them (joins, filters, etc), and instead of getting a cursor, I would like to store the result in a new database (table in SQL terminology). Is there a way to do so? I have Key/Data Java class definitions for the base tables only (table1 and table2 in the SQL example).
Thanks,
Walaa.

I understand now, thanks. Now I realize that you're not generating bindings, you have fixed hand-coded bindings for the base table.
The general question you're asking is: How can I store data in BDB without knowing the schema in advance?
Since you are already using Java serialization, this is not too difficult. For the generated database, you could use a TupleSerial binding as you're already doing. This has two parts of course, the key and the data.
I'm not sure what the key should be, perhaps a sequence number? It's up to you.
Because you're using a a TupleSerial binding, the data can be any serialized object. For the serialized data, you could store a List or Map containing the fields that are defined at runtime by the query. A List<Object> may be appropriate if the fields are identified by their order, or a Map<String,Object> if the fields are identified by name. This should work fairly well as long as the List or Map data fields are primitives.
Does this answer your question?
--mark

SQL Server 2012 Management Studio:In the Database, how to print out or export the old 3 dbo Tables that were created manually and they have a relationship for 1 Parent table and 2 Child tables?How to handle this relationship in creating a new XML Schema?

Hi all,
Long time ago, I manually created a Database (APGriMMRP) and 3 Tables (dbo.Table_1_XYcoordinates, dbo.Table_2_Soil, and dbo.Table_3_Water) in my SQL Server 2012 Management Studio (SSMS2012). The dbo.Table_1_XYcoordinates has the following columns: file_id,
Pt_ID, X, Y, Z, sample_id, Boring. The dbo.Table_2_Soil has the following columns: Boring, sample_date, sample_id, Unit, Arsenic, Chromium, Lead. The dbo.Table_3_Water has the following columns: Boring, sample_date, sample_id, Unit, Benzene, Ethylbenzene,
Pyrene. The dbo.Table_1_XYcoordinates is a Parent Table. The dbo.Table_2_Soil and the dbo.Table_3_Water are 2 Child Tables. The sample_id is key link for the relationship between the Parent Table and the Child Tables.
Problem #1) How can I print out or export these 3 dbo Tables?
Problem #2) If I right-click on the dbo Table, I see "Start PowerShell" and click on it. I get the following error messages: Warning: Failed to load the 'SQLAS' extension: An exception occurred in SMO while trying to manage a service.
--> Failed to retrieve data for this request. --> Invalid class. Warning: Could not obtain SQL Server Service information. An attemp to connect to WMI on 'NAB-WK-02657306' failed with the following error: An exception occurred in SMO while trying
to manage a service. --> Failed to retrieve data for this request. --> Invalid class. .... PS SQLSERVER:\SQL\NAB-WK-02657306\SQLEXPRESS\Databases\APGriMMRP\Table_1_XYcoordinates>   What causes this set of error messages? How can
I get this problem fixed in my PC that is an end user of the Windows 7 LAN System? Note: I don't have the regular version of Microsoft Visual Studio 2012 in my PC. I just have the Microsoft 2012 Shell (Integrated) program in my PC.
Problem #3: I plan to create an XML Schema Collection in the "APGriMMRP" database for the Parent Table and the Child Tables. How can I handle the relationship between the Parent Table and the Child Table in the XML Schema Collection?
Problem #4: I plan to extract some results/data from the Parent Table and the Child Table by using XQuery. What kind of JOIN (Left or Right JOIN) should I use in the XQuerying?
Please kindly help, answer my questions, and advise me how to resolve these 4 problems.
Thanks in advance,
Scott Chang

In the future, I would recommend you to post your questions one by one, and to the appropriate forum. Of your questions it is really only #3 that fits into this forum. (And that is the one I will not answer, because I have worked very little with XSD.)
1) Not sure what you mean with "print" or "export", but when you right-click a database, you can select Tasks from the context menu and in this submenu you find "Export data".
2) I don't know why you get that error, but any particular reason you want to run PowerShell?
4) If you have tables, you query them with SQL, not XQuery. XQuery is when you query XML documents, but left and right joins are SQL things. There are no joins in XQuery.
As for left/right join, notice that these two are equivalent:
SELECT ...
FROM   a LEFT JOIN b ON a.col = b.col
SELECT ...
FROM   b RIGHT JOIN a ON a.col = b.col
But please never use RIGHT JOIN - it gives me a headache!
There is nothing that says that you should use any of the other. In fact, if you are returning rows from parent and child, I would expect an inner join, unless you want to cater for parents without children.
Here is an example where you can study the different join types and how they behave:
CREATE TABLE apple (a int    NOT NULL PRIMARY KEY,
b varchar(23) NOT NULL)
INSERT apple(a, b)
   VALUES(1, 'Granny Smith'),
   (2, 'Gloster'),
   (4, 'Ingrid-Marie'),
   (5, 'Milenga')
CREATE TABLE orange(c int NOT NULL PRIMARY KEY,
d varchar(23) NOT NULL)
INSERT orange(c, d)
   VALUES(1, 'Agent'),
   (3, 'Netherlands'),
   (4, 'Revolution')
SELECT a, b, c, d
FROM   apple
CROSS JOIN orange
SELECT a, b, c, d
FROM   apple
INNER JOIN orange ON apple.a = orange.c
SELECT a, b, c, d
FROM   apple
LEFT   OUTER JOIN orange ON apple.a = orange.c
SELECT a, b, c, d
FROM   apple
RIGHT OUTER JOIN orange ON apple.a = orange.c
SELECT a, b, c, d
FROM   apple
FULL OUTER JOIN orange ON apple.a = orange.c
go
DROP TABLE apple, orange
Erland Sommarskog, SQL Server MVP, [email protected]

If I partitioned my drive from within a bootcamped windows volume will it destroy my GPT scheme and disable my booting ability into Mac OSx?

Alright I consider myself a fairly computer literate person but do excuse me if this issue is not actually all that interesting. Know that I would call apple care but what I am trying to do isn't exactly supported by them so they wouldn't help me. I am setting up my system to triple boot. I did the normal method as far as I can tell. I used bootcamp assistant to shrink my drive and installed windows through that. All went well. So then I had a apprx 400gb mac os volume and a 100gb windows volume. Following the advice from the mactel team over at the ubuntu help site I logged into windows via startup+option. When I did this all volumes popped up. recovery mac and windows. selected windows and then used the windows disk utility equivalent to shrink that partition in half. When I did this I check the disk manager and all was well. all volumes were there and healthy. When I restarted my computer in the boot manager window though only the recovery boot and the windows boot showed up. After doing a little research I figured that the error was negligible and that I could fix it easily enough later so I proceeded to then format the free space volume into an ntfs for the ubuntu setup. When I did that and restarted only the windows boot shows up in the boot menu. When I look through disk manager all of the partitions are where they should be and healthy. The only real clue I've found is that when inside of bootcamp control panel instead of the different volumes showing up as they are normally supposed to it gives me the option of startup from the windows volume the ntfs volume and a pseudo volume that doesnt physically exist that serves the purpose of windows recovery. This makes me think something went wrong with bootcamp. I would rEFIt it and try to see if theres some magic I could work in there but I can't install that program on windows. Additionally I found out that theres some talk that ssd can only handle two bootable partitions and that perhaps when I added a partition it shifted priority to volumes 2 and 3 instead of 1 and 2. I've tried all of the bootup tricks i know and some I looked up. the only one that still works is the boot manager window. The rest just do nothing and then go straight to windows which makes me thing if something happened with bootcamp that all the very low level osx to setup and then run windows on top of that- that now the operation isn't running as planned and windows is actually touching the hardware thus subverting any attempts to use low level osx tricks to get around it. Anyway those are the facts and my thoughts.
Having done more research than when I originally wrote ^^ I now realize that the entire reason for bootcamp (sans driver issues) is to deal with the difference between the use of GPT and MBR. I am now pretty sure that rewriting any part of the drive from software that uses MBR will mess up the partition scheme of the entire drive. Additionally I've seen a few things about ssd's being weird when they have too many partitions on them. And lastly I have an iso image of my computer right before I started tinkering so if anything I can factory reset and voila(I don't feel like pulling up a french keyboard).
picture from disk manager in windows

I actually managed to get the setup running and relatively stable. There were alot of random issues and quite honestly I was fixing my computer more often that I was using it so I backed out. If anyone wants to do this like I did I would say: It's not easy and definitely not for someone who doesn't know anything about the differences between operating systems and partitioning schemes. That being said I didn't know nearly enough and if you're careful its possible. The steps however aer pretty simple.
Before doing anything get a third party boot handle up and stable on your machine.
1. Create a partition for Windows
2. Create a partition for Linux
3. Bootcamp Windows. This step can be tricky with the extra partition because bootcamp tries to handle all of it for you so it may benefit some people to bootcamp first and then create a linux partition. But that comes with its own set of issues.
4. Run Linux setup from inside of osX NOT windows.
There are a hundred steps that could come between each of those and I neither have the expertise nor the balls to empower someone who needs to read a forum post how to do it. But it really wasn't more conceptually complicated than that.
Now on to the new issue. I was getting .NET framework incompatibilities and the whole reason I wanted the windows setup was to game so I deleted that partition. When I did that everything went back to normal EXCEPT somewhere somehow the windows boot manager is still buried and when I boot up it tries to boot into windows which obviously doesnt exist anymore. Any advise on how to get rid of this?
to make things clear I'm now running "single" partition.
@Allen Eckert

Help regarding radiobutton text in Adobe Forms

<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="nodes">
    <xs:complexType>
      <xs:sequence>
        <xs:element maxOccurs="unbounded" name="node">
          <xs:complexType>
            <xs:sequence>
              <xs:element name="PName" type="xs:string" />
              <xs:element name="IsRegistered" type="xs:boolean" />
              <xs:element name="Gender" maxOccurs="unbounded" type="GenderType" />
              <xs:element name="QT" type="xs:string" />
            </xs:sequence>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
    </xs:complexType>
</xs:element>
<xs:simpleType name="GenderType">
    <xs:restriction base="xs:string">
      <xs:pattern value="([A-Z,a-z])*" />
      <xs:minLength value="0" />
      <xs:maxLength value="6" />
      <xs:enumeration value="Male" />
      <xs:enumeration value="Female" />
    </xs:restriction>
</xs:simpleType>
</xs:schema>
I’m trying to generate a PDF form using a schema(above) and xml file(based on this xsd) using LiveCycle Designer. I have embedded the xml schema in pdf file by creating a Data Connection using this xsd file. I can generate different type of form controls by importing the xml file(based on this xsd) in PDF file using Acrobat 9.0 menu Forms > Manage Form Data > Import Data.
What I can’t figure out is how can I generate radio button's text/label based on data in xml? The Gender enumeration that I have used becomes hardcoded in design time and there can’t be more radio buttons than that specified in the Gender enumeration in the xsd. Also even though I have specified the text for the radiobutton in the xsd I have to specify it again while designing the form using Adobe Live Cycle Designer. This is like hardcoding the radiobutton text during design time. How do i read the radiobutton text from the xsd file only ???
I want the number of radio buttons and their labels to be generated based on data
from xml.
For e.g. if my xml is:
<node>
<rbType>Option1</rbType>
<rbType>Option2</rbType>
<rbType>Option3</rbType>
</node>
,then there sould be 3 radio buttons with labels as Option1, Option2 and Option3. If there are only 2 'rbType' tags, then only 2 radio buttons with respective labels.
Any help\suggestions is appreciated. Thanx
Sunit.

Use
<b>
instead of
<strong>
See http://partners.adobe.com/public/developer/en/xml/xfa_spec_2_5.pdf -> Part 3 -> Rich Text Reference for a list of supported xhtml tags.
Sebastian

Mapping problem with XML scheme

Hi All,
I have a scenario which I am trying to send a XML file through SFTP (Advanco) to a Z RFC.
I created the message mapping, but I am dealing with a issue that I would like to see if it already happened with someone else and which is the best way to solve it.
In the message mapping - test tab - source view we can find this xml tag regarding the messagetype (see that my MT is called ROOT)
<?xml version="1.0" encoding="UTF-8"?>
<ns0:ROOT xmlns:ns0="http://www.post.ch/schemas/dfu/2006/20/Report6">
the problem is, when I am testing the interface the original file comes like this below
<?xml version="1.0" encoding="UTF-8"?>
<ROOT xmlns="http://www.post.ch/schemas/dfu/2006/20/Report6">
without ns0:
And if I test in message mapping without ns0: I have the problem.
Shouldnt it be equivalent ? I mean, as far as I know the ns0: shouldnt be a problem
Does someone have any suggestion regarding my issue above ?
Thank you
Regards
Diego
Edited by: Diego Crespo on Feb 10, 2011 10:01 AM

Shouldnt it be equivalent ? I mean, as far as I know the ns0: shouldnt be a problem
when you have a namespace in the message then you need to associate it with some prefix....since ns0 (or any other prefix) is not present you are getting the error....having the namespace but not ns0 is the problem.
XMLAnonymizer bean may help you to add the namespace prefix...

Radiobutton equivalent in a schema

Similar Messages

Maybe you are looking for