Hi there,
I have also loaded this into Extensibilities 'XML-Authority' and if you
look in the errors box
it shows that there is an illegal character in the DTD i.e. '{'
Cheers, Phil
----- Original Message -----
From: spinksedi.com <[EMAIL PROTECTED]>
To: Philip Goatly <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, June 08, 2000 3:42 PM
Subject: Re: Your EDI DTDs
> Hi Philip-
>
> I have sent this issue to my developer to research. I
> will get back to you regarding this later today.
>
> Gerard
> --- Philip Goatly <[EMAIL PROTECTED]> wrote:
> > Hi There,
> >
> > The problem seems to be the { and } that appear in
> > your DTDs .
> >
> > Unless it is a new feature of XML I am unfamiliar
> > with the use of { and }
> >
> > I have studied the W3C documents about XML and do
> > not recall the use of
> > either of these characters.
> >
> > Please could you show me where to look for them in
> > the W3C documentation and
> > how they should be used.
> >
> >
> > Cheers, Phil Goatly.
> >
> > ----- Original Message -----
> > From: spinksedi.com <[EMAIL PROTECTED]>
> > To: Philip Goatly <[EMAIL PROTECTED]>;
> > <[EMAIL PROTECTED]>;
> > <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> > Cc: <[EMAIL PROTECTED]>
> > Sent: Thursday, June 08, 2000 3:23 PM
> > Subject: Re: Your EDI DTDs
> >
> >
> > > Hi Mr. Goatly-
> > >
> > > We have used XML Authority to check the integrity
> > of
> > > our DTD's. I am unfamiliar with XML Near and Far.
> > I
> > > will be certain to check them once more with XML
> > > Authority and get back to you.
> > >
> > > Regards-
> > >
> > > Gerard
> > > --- Philip Goatly <[EMAIL PROTECTED]>
> > wrote:
> > > > Hello there Mr Spinks,
> > > >
> > > > I am sending back these DTDs that you asked
> > us
> > > > to look at, and comment on.
> > > >
> > > > Unfortunately they do not parse using the
> > XML
> > > > parser Near and Far.
> > > >
> > > > The problem is that they contain {
> > characters
> > > > and other non XML compliant stuff.
> > > >
> > > >
> > > > They appear to be created programmatically,
> > so
> > > > are fairly unreadable BUT I would have thought
> > that
> > > > you
> > > > would have some quality control in place
> > to
> > > > avoid embarassments like this.
> > > >
> > > > Please could you correct them and re-send.
> > > >
> > > >
> > > > Cheers, Phil Goatly
> > > > > <!ELEMENT
> > > >
> > >
> >
>
Invoice(ST_Transaction_Set_Header,BIG_Beginning_Segment_for_Invoice,NTE_Note
> >
>
Special_Instruction*,CUR_Currency?,REF_Reference_Identification*,YNQ_YesNo_Q
> >
>
uestion*,PER_Administrative_Communications_Contact*,{11_N1_Name?,N2_Addition
> >
>
al_Name_Information*,N3_Address_Information*,N4_Geographic_Location?,REF_Ref
> >
>
erence_Identification*,PER_Administrative_Communications_Contact*,DMG_Demogr
> >
>
aphic_Information?},ITD_Terms_of_SaleDeferred_Terms_of_Sale*,DTM_DateTime_Re
> >
>
ference*,FOB_F.O.B._Related_Instructions?,PID_ProductItem_Description*,MEA_M
> >
>
easurements*,PWK_Paperwork*,PKG_Marking_Packaging_Loading*,L7_Tariff_Referen
> >
>
ce?,BAL_Balance_Detail*,INC_Installment_Information?,PAM_Period_Amount*,{12_
> >
>
LM_Code_Source_Information?,LQ_Industry_Code},{13_N9_Reference_Identificatio
> >
>
n?,MSG_Message_Text},{14_V1_Vessel_Identification?,R4_Port_or_Terminal*,DTM_
> >
>
DateTime_Reference*},{15_FA1_Type_of_Financial_Accounting_Data?,FA2_Accounti
> >
>
ng_Data},{16_IT1_Baseline_Item_Data_Invoice?,CRC_Conditions_Indicator?,QTY_Q
> >
>
uantity*,CUR_Currency?,IT3_Additional_Item_Data*,TXI_Tax_Information*,CTP_Pr
> >
>
icing_Information*,PAM_Period_Amount*,MEA_Measurements*,{17_PID_ProductItem_
> >
>
Description?,MEA_Measurements*},PWK_Paperwork*,PKG_Marking_Packaging_Loading
> >
>
*,PO4_Item_Physical_Details?,ITD_Terms_of_SaleDeferred_Terms_of_Sale*,REF_Re
> >
>
ference_Identification*,YNQ_YesNo_Question*,PER_Administrative_Communication
> >
>
s_Contact*,SDQ_Destination_Quantity*,DTM_DateTime_Reference*,CAD_Carrier_Det
> >
>
ail*,L7_Tariff_Reference*,SR_Requested_Service_Schedule?,{18_SAC_Service_Pro
> >
>
motion_Allowance_or_Charge_Information?,TXI_Tax_Information*},{19_SLN_Sublin
> >
>
e_Item_Detail?,DTM_DateTime_Reference?,REF_Reference_Identification*,PID_Pro
> >
>
ductItem_Description*,SAC_Service_Promotion_Allowance_or_Charge_Information*
> >
>
,TC2_Commodity*,TXI_Tax_Information*},{20_N1_Name?,N2_Additional_Name_Inform
> >
>
ation*,N3_Address_Information*,N4_Geographic_Location?,REF_Reference_Identif
> >
>
ication*,PER_Administrative_Communications_Contact*,DMG_Demographic_Informat
> >
> ion?},{21_LM_Code_Source_Information?,LQ_Industry_Code}!
> > > >
> > >
> >
>
,{22_V1_Vessel_Identification?,R4_Port_or_Terminal*,DTM_DateTime_Reference*}
> >
>
,{23_FA1_Type_of_Financial_Accounting_Data?,FA2_Accounting_Data}},TDS_Total_
> >
>
Monetary_Value_Summary,TXI_Tax_Information*,CAD_Carrier_Detail?,AMT_Monetary
> >
>
_Amount*,{24_SAC_Service_Promotion_Allowance_or_Charge_Information?,TXI_Tax_
> >
>
Information*},{25_ISS_Invoice_Shipment_Summary?,PID_ProductItem_Description?
> >
> },CTT_Transaction_Totals?,SE_Transaction_Set_Trailer)>
> > > >
> > > > <!ELEMENT
> > > >
> > >
> >
>
ST_Transaction_Set_Header(Transaction_Set_Identifier_Code_01_143,Transaction
> > _Set_Control_Number_02_329)>
> > > >
> > > > <!ELEMENT
> > > >
> > >
> >
>
BIG_Beginning_Segment_for_Invoice(Date_01_373,Invoice_Number_02_76,Date_03_3
> >
>
73?,Purchase_Order_Number_04_324?,Release_Number_05_328?,Change_Order_Sequen
> >
>
ce_Number_06_327?,Transaction_Type_Code_07_640?,Transaction_Set_Purpose_Code
> > _08_353?,Action_Code_09_306?,Invoice_Number_10_76?)>
> > > >
> > > > <!ELEMENT
> > > >
> > >
> >
>
NTE_NoteSpecial_Instruction(Note_Reference_Code_01_363?,Description_02_352)>
> > > >
> > > > <!ELEMENT
> > > >
> > >
> >
>
CUR_Currency(Entity_Identifier_Code_01_98,Currency_Code_02_100,Exchange_Rate
> >
>
_03_280?,Entity_Identifier_Code_04_98?,Currency_Code_05_100?,Currency_Market
> >
>
Exchange_Code_06_669?,DateTime_Qualifier_07_374?,Date_08_373?,Time_09_337?,D
> >
>
ateTime_Qualifier_10_374?,Date_11_373?,Time_12_337?,DateTime_Qualifier_13_37
> >
>
4?,Date_14_373?,Time_15_337?,DateTime_Qualifier_16_374?,Date_17_373?,Time_18
> >
> _337?,DateTime_Qualifier_19_374?,Date_20_373?,Time_21_337?)>
> > > >
> > > > <!ELEMENT
> > > >
> > >
> >
>
REF_Reference_Identification(Reference_Identification_Qualifier_01_128,Refer
> >
>
ence_Identification_02_127?,Description_03_352?,C040_Reference_Identifier?)>
> > > >
> > > > <!ELEMENT
> > > >
> > >
> >
>
YNQ_YesNo_Question(Condition_Indicator_01_1321?,YesNo_Condition_or_Response_
> >
>
Code_02_1073,Date_Time_Period_Format_Qualifier_03_1250?,Date_Time_Period_04_
> >
>
1251?,FreeForm_Message_Text_05_933?,FreeForm_Message_Text_06_933?,FreeForm_M
> >
>
essage_Text_07_933?,Code_List_Qualifier_Code_08_1270?,Industry_Code_09_1271?
> > ,FreeForm_Message_Text_10_933?)>
> > > >
> > > > <!ELEMENT
> > > >
> > >
> >
>
PER_Administrative_Communications_Contact(Contact_Function_Code_01_366,Name_
> >
>
02_93?,Communication_Number_Qualifier_03_365?,Communication_Number_04_364?,C
> >
>
ommunication_Number_Qualifier_05_365?,Communication_Number_06_364?,Communica
> >
>
tion_Number_Qualifier_07_365?,Communication_Number_08_364?,Contact_Inquiry_R
> > eference_09_443?)>
> > > >
> > > > <!ELEMENT
> > > >
> > >
> >
>
N1_Name(Entity_Identifier_Code_01_98,Name_02_93?,Identification_Code_Qualifi
> >
>
er_03_66?,Identification_Code_04_67?,Entity_Relationship_Code_05_706?,Entity
> > _Identifier_Code_06_98?)>
> > > >
> > > > <!ELEMENT
> > > >
> > >
> >
> N2_Additional_Name_Information(Name_01_93,Name_02_93?)>
> > > >
> > > > <!ELEMENT
> > > >
> > >
> >
>
N3_Address_Information(Address_Information_01_166,Address_Information_02_166
> > ?)>
> > > >
> > > > <!ELEMENT
> > > >
> > >
> >
>
N4_Geographic_Location(City_Name_01_19?,State_or_Province_Code_02_156?,Posta
> >
>
l_Code_03_116?,Country_Code_04_26?,Location_Qualifier_05_309?,Location_Ident
> > ifier_06_310?)>
> > > >
> > > > <!ELEMENT
> > > >
> > >
> >
>
DMG_Demographic_Information(Date_Time_Period_Format_Qualifier_01_1250?,Date_
> >
>
Time_Period_02_1251?,Gender_Code_03_1068?,Marital_Status_Code_04_1067?,Race_
> >
>
or_Ethnicity_Code_05_1109?,Citizenship_Status_Code_06_1066?,Country_Code_07_
> >
> 26?,Basis_of_Verification_Code_08_659?,Quantity_09_380?)>
> > > >
> > > > <!ELEMENT
> > > >
> > >
> >
>
ITD_Terms_of_SaleDeferred_Terms_of_Sale(Terms_Type_Code_01_336?,Terms_Basis_
> >
>
Date_Code_02_333?,Terms_Discount_Percent_03_338?,Terms_Discount_Due_Date_04_
> >
> === message truncated ===
>
>
> =====
> Gerard Spinks
> B2B Practice Director
> Spinks Engineering, Inc.
> www.spinksedi.com
> 925-706-7694 West Coast Office
> 212-658-9309 East Coast Office
> "Enabling Business to Business Commerce"
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Photos -- now, 100 FREE prints!
> http://photos.yahoo.com
>
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
