Importing DTD as External Def.
Hi all,
My Customer gave one DTD file, when i import that under external Def. by seleting the Category a DTD and Messages from the first ELEMENT,I can able to see Structure name under messages TAB and i can able to see ../global/Global.dtd under External References TAB
When i see the imported DTD with mapping editor, it does not have all the structure according to the sample xml file.It has from the middle of the file
They gave another DTD "Global.dtd", i imported this also and this contains the rest of the structure missed above.
What to do in this case, why is this behavior here
REgards
Edited by: Vamsi Krishna on Sep 13, 2010 10:53 PM
Guru,
>>If you have validated them separately, try validating and traversing as i said above.
As i have two separate file( status.dtd and Global.dtd), i validated them separately.
when i validate status.dtd file, it gave error like Error *opening local file,The system can't find the path specified* . then now i changed the path as C:\Global.dtd and placed Global.dtd file in C:/. Validation is fine now.
*<!-- Include Nistevo Global -->*
<!========================================================>
<!ENTITY % NISTEVO_GLOBAL PUBLIC "Global" "../global/Global.dtd">
%NISTEVO_GLOBAL;
the 2nd file Global.dtd validation is fine.
When i validated status.dtd, i couldn't traversed, how this works , i do not understand
I can send you both dtd file to you
Regards
Edited by: Vamsi Krishna on Sep 17, 2010 5:10 PM
Similar Messages
-
What is main diff b/w imported Archives and External Defination in IR
What is main diff b/w imported Archives and External Defination in IR
Hi Vijay,
ED-standard schema for describing the message structure.If you have the structure provided to you from some external application you can use it in PI directly without recreating in PI.you can import following formats which are used to describe message schema
WSDL (Web Service Description Language),
XSD (XML Schema Definition Language),
DTDs (Document Type Definitions)
Imported Archives: its used basically for java and xslt mapping where you create the required mapping externally using some tools
(java-eclipse/NWDS .XSLT-stylus studio).You can also implement XSLT and Java mappingsf and save them as archives in the Integration Repository.
read More details here
[ED|http://help.sap.com/saphelp_nwesrce/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm]
[Imported Archives|http://help.sap.com/saphelp_nw04/helpdata/en/4c/b2ad3de2d76b3be10000000a114084/content.htm]
Regards,
Srinivas -
Doubt in Making IDOC as External Def
Hi,
I have imported the IDOC From R/3 to XI ( IR ).
If i changed the Occurence of one segment say 0unbounded to 01 by exporting the IDOC into notepad and imported as External def.
Q1) Is ther any problem that having the 0--unbounded occurence at R/3 side and 0-1 occurence at IDOC structure in XI.
Q2) While Trigering the IDOC values from R/3 we may provide multiple lineitems but we have changed the structure to 0...1.How this will handle
How this will Effect???
Regards
SumanHi Suman,
yes you can change the occurances... check below links
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
Sachin
Edited by: Sachin Dhingra on Mar 17, 2008 1:26 PM -
How do i import to a external hard drive
Hi in I movie how to i import to a external hard drive from my video camera as i find it takes to much room on my imac. thanks
Hello there foxcub 6,
It sounds like you want to be able to import your video to an external drive rather than your internal drive to save space.
First, you'll need to create an iMovie library on your external hard drive. Take a look at the "Create a new library" section here: http://help.apple.com/imovie/mac/10.0/#mov3fa25bae7
After you've created the library, you can import media directly to it, and copy existing projects and events to it as well. You can learn more about importing here:
http://help.apple.com/imovie/mac/10.0/#movbc953953e
Step 6 outlines how to Import to a different library specifically:
Do one of the following:
To choose an existing event to contain the imported clips: Choose the event from the “Import to” pop-up menu at the top of the Import window.
To create a new event to contain the imported clips: Choose New Event from the “Import to” pop-up menu, type a name for the new event, and press Return.
To learn more about events, see Organize your events and projects.
The Import To dropdown is at the top of the Import window that opens when you click File > Import.
Thank you for using Apple Support Communities.
Cheers,Sterling -
White spaces in token area of xsd - error when importing xsd as ext. def.
Hello,
we are not sure about this issue.
This is how an area of the xsd (unfortunately an xsd of a published standard message format of german government!)
is defined that we need to import as an external definition:
<xs:complexContent>
<xs:restriction base="tns:WLT_String">
<xs:sequence>
<xs:element name="content">
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value="Allgemeine Fahrerlaubnis (§ 5 StVZO) " />
<xs:enumeration value="Dienstfahrerlaubnis-Klassen (bisheriger § 5 i. V. m. § 14 StVZO)" />
<xs:enumeration value="Dienstfahrerlaubnis-Klassen (§ 6 i. V. m. § 26 FeV)" />
<xs:enumeration value="Dienstfahrerlaubnis-Klassen Bundeswehr (bisheriger § 5 i. V. m. § 14 StVZO)" />
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
<xs:attribute name="wl_fassung" type="xs:string" use="optional" default="0" />
<xs:attribute name="wl_version" type="xs:string" use="required" fixed="1.1" />
</xs:restriction>
</xs:complexContent>
So we can see this defintion:
<xs:restriction base="xs:token">
which means per definition:
xsd:token: normalizedString w/o 2 white spaces succeeding and w/o white spaces at start and end.
But you can see that the enumerations contain 2 white spaces succeeding or white space at the end.
Impporting this xsd as an external definition into PI will fail.
So it looks like PI is doing a very restricitve check of the values against the token definition.
We would expect that any xml editor would do the same check but behaviour of xml editors is different means accepting this xsd.
So is it correct that PI is more restrictive at the latest during activation of such an xsd?
This results in the situation that official standard xsds will be used by governement with other tools but only interfaces with PI will fail..
Any ideas how to run with that issue?
Regards
DirkHello,
Your issue looks like the one described in this page:
http://www.xmlplease.com/normalized
For reference purposes, here is the link for the supported schema and wsdl in PI 7.1
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00a9a425-1769-2a10-9196-bd8eeed72e4c
As a temporary work around, you can try editing the xsd by removing the spaces before importing it into PI.
Hope this helps,
Mark -
Importing Users from external table in obiee 11g
Hi Every one,
Do any one help me giving suggestions that how we can import users from external table.
I am using obiee 11.1.1.6.
In that external table Which i am using there are 56K users.
They are able to login to obiee analytics.
But for setting object level security I need to make diffrent groups with these users to assign the dashbords and required objects in front end.
But how can we get all these users into BI server or presentation server to make them into groups.
Thanks in advance.
Edited by: 861096 on Mar 13, 2012 8:44 AMHi,
or if your lowest level is the same like
Day->month->year->Total
Day->businessMonth->businessyear->Total
Then yes, it is.
Create the first, then you start to create the second by adding your top(business year) level on the same level as the one you have (year) both under your total.
Then when you would add your second base level, there is a special option for it, something like use other hierarchy level/shared level (sorry can't recall and does not have a connection right now) then you select your existing day level under your businessmonth level.
Hope this helps,
Regards,
D -
LR has problem importing just from external drive
I am trying to import from an external drive into LR5. From the import panel I select the external drive and for some reason it displays and checks (check mark) all photos on my internal drive as well as the photos on the external drive. I remember when I first gone LR3 years ago I ran into the same issue and do not know what I did to resolve it.
As I am writing this I also tried just importing from a specific folder on my desktop and I get the same result. It appears as though LR is scanning my entire Macintosh HD drive instead of just the selected folder or drive. LR currently shows 132000 (and climbing) images to be imported and I know the selected folder only has around 500 images.
Any ideas?Problem solved, for those that are interested or have this similar problem. After a few days trying to import to lightrrom from an external drive, I finally discovered this issue.
Somehow several shortcuts to the Machintiosh HD (equivelent to C:drive in Windows) got tucked away inside several folders. When LR started scanning the drive for for images it finds the "Machitosh HD" shorcut and beggins scanning the intire internal drive for jpg, png, tiff, psd etc... Once I found the shortcuts, inside the random folders, and deleted them all was well in the world of LR importing.
So even though this external drive had nothing to do with the internal drive, the "Machintosh HD" linked LR to the internal drive for scanning. -
How do I import photos from external hard drive to iCloud library?
I have saved many photos to an external hard drive for security. I would like to store at least some of them in iCloud so I have direct access from Photos. Is this possible please?
how do I import photos from external hard drive to iCloud library?
Just like you'd do it with iPhoto. Drag the photos or folder of photos into the open Photos Library window or onto the Photos icon in the Dock.
If you have the iCloud Photo Library activated in Photos the new photos will be copied to the online iCloud Photo Library along with the rest of the photos in your library. Remember, with the iCloud Photo Liberty it's all the photos or none. You may have to purchase additional iCloud space to store all of your photos. -
Can we import DTD's in B2B 11g
Hi All,
For Custom document can we import DTD ? If yes then what will be the XPATH for the DTD, according to my knowledge no xpath for DTD?
Regards
ShankarHi,
B2B11g does not allow DTD imports for custom document. only XSD import is allowed.
So, this answers your other question as well.
xpath is for XML message.. not for the schema definition...
Regards,
Vijay -
Importing WSDL with external references issue
Hi guys,
pls help me on this:
I have a WSDL file which referes to external data types. Obviously, if I want to create a message mapping I can't see the WSDL data type. How are such situations resolved? How to import external types into PI?
Thx, A.HI,
You have to inport the WSDL alongwith all its external references.
You can refer the following threads:
Import WSDL with external reference
Re: PI 7.1: Importing a wsdl file with references to other xsd files
http://help.sap.com/saphelp_nwesrce/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm -
What classes to import for this external as code?
Hi
Just wondering what classes I need to import into my external as fiule to make the following code work:
public static var loader:Loader = newLoader();
loader.contentLoaderInfo.addEventListener(Event.INIT, fontLoaded);
loader.load(new URLRequest("font.swf"));
Cheers
Shaunthe Loader and URLRequest classes.
flash will tell you when you try to publish.
well, now that i look at it more carefully, you should see some error messages that help you fix that. -
Error While Importing DTD to XI
Hi all,
I have a DTD from cxml.org. While importing that DTD into the XI as external definitions, the message types couldn't be shown.
Can anybody please suggest the reason?
Any help will be appriciated.
Kind regards,
KulwantHi,
Thanks alll for reply. Let me bit explain more. While i import this DTD, i get an error in the WSDL tab in the imported external definitions screen,
Unable to convert imported document to WSDL
Reason: Entity "Method.ANY" already declared
Check the selected category
Can any body suggest
I have posted the dtd below:
<?xml version="1.0" encoding="UTF-8"?>
<!--
For cXML license agreement information, please see
http://www.cxml.org/home/license.asp
$Id: //ariba/cxml/modules/Common.mod#6 $
-->
<!--
A few character entities the XML recommendation says should be defined
"for interoperability" with existing SGML parsers. By default, these
are not included to avoid warnings (about entity redefinition) from
many XML parsers.
-->
<!ENTITY % SGML-help "IGNORE">
<![%SGML-help;[
<!ENTITY lt "&#60;">
<!ENTITY gt ">">
<!ENTITY amp "&#38;">
<!ENTITY apos "'">
<!ENTITY quot """>
]]>
<!--
Common types used throughout the cXML definition.
The types try to follow the XML DATA definition submitted to the W3C. See
the following for more information,
http://msdn.microsoft.com/xml/reference/schema/datatypes.asp
http://www.w3c.org/TR/1998/NOTE-XML-data-0105/
-->
<!-- Atomic-level Types -->
<!ENTITY % bin.base64 "CDATA">
<!ENTITY % bin.hex "CDATA">
<!ENTITY % boolean "(0 | 1)"> <!-- 0 is false, 1 is true -->
<!ENTITY % char "CDATA">
<!ENTITY % date "CDATA">
<!ENTITY % datetime.tz "CDATA"> <!-- Time zone is required -->
<!ENTITY % fixed.14.4 "CDATA">
<!ENTITY % i8 "CDATA">
<!ENTITY % int "%i8;">
<!ENTITY % r8 "CDATA">
<!ENTITY % number "CDATA"> <!-- No limit on number of digits, unlike
%r8; -->
<!ENTITY % string "CDATA">
<!ENTITY % time.tz "CDATA"> <!-- Time zone is required -->
<!ENTITY % duration "CDATA"> <!--ISO8601 duration http://www.w3.org/TR/xmlschema-2/#duration -->
<!ENTITY % ui8 "CDATA">
<!ENTITY % uint "%ui8;"> <!-- Unique to this specification -->
<!ENTITY % uri "CDATA">
<!ENTITY % uuid "CDATA">
<!-- Higher-level Types -->
<!--
NOTE: The following is a temporary hack to allow empty values for
some attributes with these types. The nmtoken entity should resolve to
NMTOKEN.
-->
<!ENTITY % nmtoken "CDATA"> <!-- Any combination of XML name chars. -->
<!ENTITY % isoLangCode "%nmtoken;"> <!-- ISO 639 Language Code -->
<!ENTITY % isoCountryCode "%nmtoken;"> <!-- ISO 3166 Country Code -->
<!ENTITY % isoCurrencyCode "%nmtoken;"> <!-- ISO 4217 Currency Code -->
<!ENTITY % xmlLangCode "%nmtoken;"> <!-- Language code as defined by XML
recommendation: Language and
country. -->
<!ENTITY % URL "%uri;">
<!--
For cXML license agreement information, please see
http://www.cxml.org/home/license.asp
$Id: //ariba/cxml/schema/Modules/Base.mod#8 $
-->
<!--
This file defines the basic elements used to build higher level
constructs in cXML.
-->
<!-- Basic Name/Data Elements -->
<!--
Name is used to provide an identifier for other elements.
xml:lang
The language in which the name is written.
-->
<!ELEMENT Name (#PCDATA)> <!-- string -->
<!ATTLIST Name
xml:lang %xmlLangCode; #REQUIRED
>
<!--
An Extrinsic is an element which can be used to extend the data
associated with known elements.
Since this Element is of type ANY, it could contain any arbitrary XML
document within itself, or a binary ![CDATA[]] document.
name
Name used to identify this extrinsic.
-->
<!ELEMENT Extrinsic ANY>
<!ATTLIST Extrinsic
name %string; #REQUIRED
>
<!--
Description is a string which describes something.
Though text may be interspersed with ShortName elements in this content
model, placing the ShortName at the beginning or end of the element is
much preferred. At most one ShortName element is allowed per
Description. The intended content model would be more like
(( ShortName, #PCDATA ) | ( #PCDATA | ShortName? )) if DTD syntax
supported it.
xml:lang
The language in which the description is written.
-->
<!ELEMENT Description ( #PCDATA | ShortName )* > <!-- mixed: string and
ShortName -->
<!ATTLIST Description
xml:lang %xmlLangCode; #REQUIRED
>
<!--
A short string which describes something in fewer characters than the
entire Description. This should be used when limited space is available.
For example, a table of elements might show the ShortName's of each. A
linked "details" view would show the entire Description (including the
ShortName). Without a ShortName, the user interface must default to a
truncation of the Description.
This element does not require an xml:lang attribute since it appears only
within a Description element. The language of the ShortName must match
that of the surrounding Description.
-->
<!ELEMENT ShortName (#PCDATA)> <!-- string -->
<!-- Telephone Number Elements -->
<!--
International ITU dial code for the country code in question. This
code would be entered after any escape code necessary to begin
International dialing. That is, the escape code does not appear in the
content of this element.
isoCountryCode
The ISO 3166 2-letter country code for the dial code in question.
-->
<!ELEMENT CountryCode (#PCDATA)> <!-- uint -->
<!ATTLIST CountryCode
isoCountryCode %isoCountryCode; #REQUIRED
>
<!--
The areacode or city code within a CountryCode.
-->
<!ELEMENT AreaOrCityCode (#PCDATA)> <!-- uint -->
<!--
The local number part of a telephone number.
-->
<!ELEMENT Number (#PCDATA)> <!-- string -->
<!--
An extension within relative to the Number element. This element has no
meaning without an associated Number element.
-->
<!ELEMENT Extension (#PCDATA)> <!-- uint -->
<!--
TelephoneNumber represents international telephone numbers.
-->
<!ELEMENT TelephoneNumber (CountryCode, AreaOrCityCode, Number, Extension?)>
<!--
Phone is a "named" TelephoneNumber.
name
specifies an identifier which indicates the type of phone number.
US examples would include "work","home", etc.
-->
<!ELEMENT Phone (TelephoneNumber)>
<!ATTLIST Phone
name %string; #IMPLIED
>
<!--
Fax number.
-->
<!ELEMENT Fax (TelephoneNumber | URL | Email)>
<!ATTLIST Fax
name %string; #IMPLIED
>
<!-- Addressing Elements -->
<!--
URL. A string which represents a URL
-->
<!ELEMENT URL (#PCDATA)> <!-- URL -->
<!ATTLIST URL
name %string; #IMPLIED
>
<!--
An email address. Address must conform to RFC 821 (SMTP Standard).
preferredLang
optional language that the email owner prefers to receive
emails in. Refer to the definition of xmlLangCode entity.
-->
<!ELEMENT Email (#PCDATA)> <!-- string -->
<!ATTLIST Email
name %string; #IMPLIED
preferredLang %xmlLangCode; #IMPLIED
>
<!--
Contact represents an entity at a location. The nature of this
element is that it represents a communication "end point" for a
location.
role
Position this person or group plays in the procurement process.
Likely values include endUser, administrator, purchasingAgent,
technicalSupport, customerService, sales,
supplierCorporate, supplierMasterAccount, supplierAccount,
buyerCorporate, buyerMasterAccount, buyerAccount, buyer,
subsequentBuyer. Other values may be allowed in some cases.
from and to roles are reserved for future use.
addressID
An id for the address. Needed to support address codes for
relationships that require id references.
-->
<!ELEMENT Contact (Name, PostalAddress*, Email*, Phone*, Fax*, URL*)>
<!ATTLIST Contact
role NMTOKEN #IMPLIED
addressID %string; #IMPLIED
>
<!--
The DeliverTo part of an Address. This would be internal to the actual
address know to the outside world. Similar to what an extension is to a
TelephoneNumber.
-->
<!ELEMENT DeliverTo (#PCDATA)> <!-- string -->
<!--
Street is a single line of an Address' location.
-->
<!ELEMENT Street (#PCDATA)> <!-- string -->
<!--
City is the name of the city in an Address' location.
-->
<!ELEMENT City (#PCDATA)> <!-- string -->
<!--
State is an optional state identifier in an Address' location.
-->
<!ELEMENT State (#PCDATA)> <!-- string -->
<!--
PostalCode (I have no idea how to describe it)
-->
<!ELEMENT PostalCode (#PCDATA)> <!-- string -->
<!--
Country is the name of the country in an Address' location. The
content of this element is a string which may (for example) be printed
directly to a shipping label. The content is the human-readable
equivalent of the isoCountryCode used by applications.
isoCountryCode
The ISO 3166 2-letter country code for this country.
-->
<!ELEMENT Country (#PCDATA)> <!-- string -->
<!ATTLIST Country
isoCountryCode %isoCountryCode; #REQUIRED
>
<!--
PostalAddress is a real-world location for a business or person.
-->
<!ELEMENT PostalAddress (DeliverTo*, Street+, City, State?,
PostalCode?, Country)>
<!ATTLIST PostalAddress
name %string; #IMPLIED
>
<!--
Address is the association of a Contact and an Location.
isoCountryCode
The ISO 3166 2-letter country code for the country containing this
location.
addressID
An id for the address. Needed to support address codes for
relationships that require id references. An example would be a
shipping code.
-->
<!ELEMENT Address (Name, PostalAddress?, Email?, Phone?, Fax?, URL?)>
<!ATTLIST Address
isoCountryCode %isoCountryCode; #IMPLIED
addressID %string; #IMPLIED
>
<!-- Financial Elements -->
<!--
Money is the representation of the object used to pay for items.
currency
specifies the currency in which amount is stated, must conform to ISO
4217 currency codes.
alternateAmount
the amount of money in the alternateCurrency. Optional and used to
support dual-currency requirements such as the Euro.
alternateCurrency
specifies the currency in which the alternateAmount is stated, must
conform to ISO 4217 currency codes.
-->
<!ELEMENT Money (#PCDATA)> <!-- number -->
<!ATTLIST Money
currency %isoCurrencyCode; #REQUIRED
alternateAmount %number; #IMPLIED
alternateCurrency %isoCurrencyCode; #IMPLIED
>
<!--
Optional textual child for communicating arbitrary comments or
description along with the parent.
Though text may be interspersed with Attachment elements in this content
model, grouping the Attachment list at the begging or end of the element
is much preferred. The intended content model would be more like
(( Attachment+, #PCDATA ) | ( #PCDATA | Attachment* )) if the DTD syntax
supported it.
xml:lang
The language in which the Comments are written. This attribute
will be required in a future version of cXML. (Leaving it out is
deprecated.)
-->
<!ELEMENT Comments ( #PCDATA | Attachment )* > <!-- mixed: string and
opt. Attachment list -->
<!ATTLIST Comments
xml:lang %xmlLangCode; #IMPLIED
>
<!--
Optional child of Comments element referencing a part in a multipart MIME
transmission.
The contained URL must use the scheme "cid:". This is the identifier for
the referenced attachment within the larger transmission. Must match the
Content-ID header of one (and only one) part of the MIME transmission
containing this cXML document. May also be used to retrieve the
attachment file separately.
-->
<!ELEMENT Attachment (URL)>
<!---
Reference to a remote attachment.
AttachmentReference is used inside Extrinsic elements that have a
predefined name of "Attachments".
In the context of AttachmentReference, the domain attribute of
InternalID is currently optional. However, as a way to prevent
circular request paths, the sending application may use a
predefined value of "local" to indicate that the attachment
requested is local to the other application.
length
length of the attachment in bytes.
-->
<!ELEMENT AttachmentReference (Name, Description, InternalID)>
<!ATTLIST AttachmentReference
length %uint; #IMPLIED
>
<!--
Price per unit of item.
-->
<!ELEMENT UnitPrice (Money)>
<!--
Reference to an earlier document (for example, OrderRequest). In a
StatusUpdateRequest, this element identifies the purchase order to be
updated.
payloadID
A unique identifier for the document. Copied directly from the
cXML element of the original document.
-->
<!ELEMENT DocumentReference EMPTY>
<!ATTLIST DocumentReference
payloadID %string; #REQUIRED
>
<!ELEMENT InternalID (#PCDATA)> <!-- string -->
<!ATTLIST InternalID
domain %string; #IMPLIED
>
<!-- ====
Common to most variants of the PunchOut transaction set. Defined here
to be easily shared between multiple DTD files without requiring
inclusion of Transaction.mod in all of them.
All of the PunchOut transaction sets include an originating Request
(ProviderSetupRequest for example), relatively simple Response
(PunchOutSetupResponse for example) and final Message
(ProviderDoneMessage or PunchOutOrderMessage). The Request and
Response comprise a back-end transaction between two cooperating
applications that wish to extend an interactive session from one to the
other. The Request provides the destination application with
authentication, identification and other setup information. The
Response provides the originating application with a unique starting
location for the interactive (HTML) session at the destination system.
After receiving a Response of this type, the originating application
redirects the user's browser to the provided location. (For some
non-HTML applications, opening a new browser window at that location
may be more appropriate.) The destination system eventually provides
an HTML form to the user's browser. This form submits the final
Message to close the remote session, return that user to the
originating application and carry any required information back to the
originating application.
==== -->
<!--
OriginatorCookie - Identification of a specific PunchOut session. Used
in both originating Request and later Message that returns user to
originating application.
Note: The BuyerCookie element used in a 'regular' PunchOut transaction
(defined in Transaction.mod) is of type ANY. That does not seem
useful. The string required below better matches the needs for this
element. Future transactions similar to the PunchOut transaction will
use this element.
-->
<!ELEMENT OriginatorCookie (#PCDATA)>
<!--
BrowserFormPost - Location to which the user's browser must submit the
final Message. This location (carried in the originating Request) does
not need to be specific to a PunchOut session since the
OriginatorCookie is returned in the Message.
-->
<!ELEMENT BrowserFormPost (URL)>
<!--
SelectedService - Identification of a service offered by this provider
and requested in this transaction. Used only in the originating
Request.
-->
<!ELEMENT SelectedService (#PCDATA)>
<!--
StartPage - Location to which the user's browser must be redirected to
begin the interactive portion of the session at the remote site. The
destination system returns this information in the Response document.
This location must be specific to a particular session. It is
effectively a one time key, providing authenticated entry into the
destination system.
-->
<!ELEMENT StartPage (URL)>
<!--
ReturnData - Any information the originator must know about the
completed operation at the provider site. The ReturnValue is for
applications; the Name is for human consumption (direct presentation in
the User Interface of the application). Where appropriate for the
possible services, this element may appear in the final Message for a
PunchOut session.
name
An identifier for the data returned. Provides a meaning for the
contents of a ReturnData element.
-->
<!ELEMENT ReturnData (ReturnValue, Name)>
<!ATTLIST ReturnData
name %string; #IMPLIED
>
<!ELEMENT ReturnValue (#PCDATA)>
<!--
Defines a time range. The start and end can be unbounded
startDate
The starting date of the time range
endDate
The ending date of the range
-->
<!ELEMENT TimeRange EMPTY>
<!ATTLIST TimeRange
startDate %datetime.tz; #IMPLIED
endDate %datetime.tz; #IMPLIED
>
<!--
Defines a period in time.
startDate
The starting date of the period
endDate
The ending date of the period
-->
<!ELEMENT Period EMPTY>
<!ATTLIST Period
startDate %datetime.tz; #REQUIRED
endDate %datetime.tz; #REQUIRED
>
<!--
Must be a UN/CEFACT (Recommendation 20) unit of measure code.
-->
<!ELEMENT UnitOfMeasure (#PCDATA)> <!-- nmtoken -->
<!--
Defines a reference to a term which is defined
in another document.
termName
The name of the ID attribute containing the term.
term
The value of that attribute (i.e., the term itself).
-->
<!ELEMENT TermReference EMPTY>
<!ATTLIST TermReference
termName %string; #REQUIRED
term %string; #REQUIRED
>
<!--
Defines an optionally named monetary rate at which goods or services are
charged or paid.
Money
The amount of Money per UnitOfMeasure to be charged or paid.
UnitOfMeasure
Unit of measure.
TermReference
Identifies the definition of this UnitRate
(found, for example, in contracts, master agreements, and other documents
which may or may not be cXML documents).
-->
<!ELEMENT UnitRate (
Money,
UnitOfMeasure,
TermReference?
)>
<!--
The rate information used to define the rate of a purchase. For
example, this could be the total room rate for 4 nights of stay
at a hotel.
Total
The total amount for the rate. The total amount must equal
to quantity x UnitRate.
UnitRate
The single unit rate.
Description
Textual description for the rate. For example, hotel nightly rate.
Quantity
The quantity. For example, a 4 nights stay at a hotel will
have quantity set to 4 with UnitofMesure in UnitRate set to Day.
-->
<!ELEMENT Rate (Total, UnitRate, Description?)>
<!ATTLIST Rate
quantity %r8; #REQUIRED
>
<!--
The total for something.
-->
<!ELEMENT Total (Money)>
<!--
For cXML license agreement information, please see
http://www.cxml.org/home/license.asp
$Id: //ariba/cxml/modules/Version.mod#4 $
-->
<!--
Another top-level entity used in Transport.mod. Defined here to allow
easy updates to the release version of cXML without opening
Transport.mod. This should also provide an easy file to search for
the current release version string.
-->
<!-- cxml.version
Current default string for the cXML@version attribute. Corresponds to
the final directory of the SYSTEM identifier used in all up-to-date
cXML documents.
For easy parsing of this file, do not remove whitespace surrounding the
actual version string.
-->
<!ENTITY cxml.version "1.2.019" >
<!--
For cXML license agreement information, please see
http://www.cxml.org/home/license.asp
$Id: //ariba/cxml/schema/Modules/Supplier.mod#1 $
-->
<!--
Supplier of goods and services. Includes a list of SupplierIDs which
identify the Supplier.
corporateURL
URL to web site about the supplier
storeFrontURL
URL to web site where a user can shop or browse
-->
<!ELEMENT Supplier (Name, Comments?, SupplierID+, SupplierLocation*)>
<!ATTLIST Supplier
corporateURL %URL; #IMPLIED
storeFrontURL %URL; #IMPLIED
>
<!--
One of the locations for a supplier. Supplier location is
generally a physical location.
-->
<!ELEMENT SupplierLocation (Address, OrderMethods)>
<!--
OrderMethods is the list of methods by which one can order
from a supplier. The contact element is the technical contact
who should be able to assist with order processing issues.
The list is to be ordered by supplier preference, the first
element having the highest degree of preference.
-->
<!ELEMENT OrderMethods (OrderMethod+, Contact?)>
<!--
OrderMethod is a method for ordering. It is comprised of a
target address for the order and the protocol expected by
the address.
-->
<!ELEMENT OrderMethod (OrderTarget, OrderProtocol?)>
<!--
OrderTarget represents an address to which orders can be
sent.
-->
<!ELEMENT OrderTarget (Phone | Email | Fax | URL | OtherOrderTarget)>
<!--
OrderProtocol is the communication method to be used when
communicating an order to a supplier. An example would be "cXML".
-->
<!ELEMENT OrderProtocol (#PCDATA)> <!-- string -->
<!--
OtherOrderTarget represents an address which is not enumerated by
default in the OrderTarget Element. This may contain address targets
beyond the ability of this document to describe.
name
Optional name for target.
-->
<!ELEMENT OtherOrderTarget ANY>
<!ATTLIST OtherOrderTarget
name %string; #IMPLIED
>
<!--
Definition of a supplier id. A supplier id is a (domain, value)
pair so that suppliers have the flexibility to define their id's
according to an arbitrary convention (e.g., (DUNS, 12345),
(TaxID, 88888888)).
domain
the domain of the id
-->
<!ELEMENT SupplierID (#PCDATA)> <!-- string -->
<!ATTLIST SupplierID
domain %string; #REQUIRED
>
<!--
Defines a List of Suppliers that might be associated with a quote Item. Used in
ItemOut.
-->
<!ELEMENT SupplierList (Supplier+)>
<!--
For cXML license agreement information, please see
http://www.cxml.org/home/license.asp
$Id: //ariba/cxml/modules/Item.mod#6 $
-->
<!--
ID with which the item's manufacturer identifies the item.
-->
<!ELEMENT ManufacturerPartID (#PCDATA)> <!-- string -->
<!--
Name of the item's manufacturer.
xml:lang
The language in which the ManufacturerName is written. This
attribute will be required in a future version of cXML. (Leaving it
out is deprecated.)
-->
<!ELEMENT ManufacturerName (#PCDATA)> <!-- string -->
<!ATTLIST ManufacturerName
xml:lang %xmlLangCode; #IMPLIED
>
<!--
Classification is used to group items into similar categories.
domain
"name" of classification, ie., SPSC
-->
<!ELEMENT Classification (#PCDATA)> <!-- string -->
<!ATTLIST Classification
domain %string; #REQUIRED
>
<!--
LeadTime specifies, in days, the amount of time required to
receive the item.
-->
<!ELEMENT LeadTime (#PCDATA)> <!-- uint -->
<!--
How the supplier identifies an item they sell.
If SupplierPartID does not provide a unique key to identify the item,
then the supplier should generate a key which identifies the part
uniquely when combined with the SupplierID and SupplierPartID. The
key is called SupplierPartAuxiliaryID.
An example is where a Supplier would use the same PartID for an
item but have a different price for units of "EA" versus "BOX".
In this case, the ItemIDs should be:
<ItemID>
<SupplierPartID>pn12345</SupplierPartID>
<SupplierPartAuxiliaryID>EA</SupplierPartAuxiliaryID>
</ItemID>
<ItemID>
<SupplierPartID>pn12345</SupplierPartID>
<SupplierPartAuxiliaryID>
<foo>well formed XML here</foo>
</SupplierPartAuxiliaryID>
</ItemID>
In this case, the "foo" element must be defined in an internal subset
sent with the cXML document. Otherwise, parsers will not be able to
validate that document.
In a preferred approach, the sending application may escape the contained
XML using CDATA sections. This would appear as:
<SupplierPartAuxiliaryID>
<![CDATA[<foo>well formed XML here</foo>]]>
</SupplierPartAuxiliaryID>
Finally, the angle brackets could be escaped using XML character
entities. This might be a bit harder for humans to read. For example:
<SupplierPartAuxiliaryID>
<foo>well formed XML here</foo>
</SupplierPartAuxiliaryID>
-->
<!ELEMENT SupplierPartID (#PCDATA)> <!-- string -->
<!ELEMENT SupplierPartAuxiliaryID ANY>
<!--
A unique identification of an item. SupplierID is not required since
ItemIDs never travel alone.
ItemIDs used to define a Supplier/Commodity level Blanket Order Item should
use Empty SupplierPartID tag. These type of items do not have specific part numbers
at the time of placing the Blanket Order. There will be subsequent release orders
or invoices that will define the SupplierID.
-->
<!ELEMENT ItemID (SupplierPartID, SupplierPartAuxiliaryID?)>
<!--
ItemDetail contains detailed information about an item. All the data that
a user would want to see about an item instead of the bare essentials
that are represented in the ItemID.
LeadTime
time in days to receive the item
-->
<!ELEMENT ItemDetail (UnitPrice, Description+, UnitOfMeasure,
Classification+, ManufacturerPartID?,
ManufacturerName?, URL?, LeadTime?, Extrinsic*)>
<!--
Item details specific for items that describe blanket purchase order items.
This element should only be used for items in a purchase order of
type "blanket"
-->
<!ELEMENT BlanketItemDetail (Description+, MaxAmount?, MinAmount?,
MaxQuantity?, MinQuantity?,
UnitPrice?, UnitOfMeasure?,
Classification*, Extrinsic*)>
<!--
For cXML license agreement information, please see
http://www.cxml.org/home/license.asp
$Id$
-->
<!--
This element captures travel information. It could be one of four
types: air, car rental, hotel or rail.
AirDetail
Air travel detail.
CarRentalDetail
Car rental detail.
HotelDetail
Hotel detail.
RailDetail
Rail detail.
PolicyViolation
List of policy violations (if any) associated with this
travel line item.
Comments
Top level comments for this travel line item (if any). This
is not the policy violation comment but a top level comment
given by the user for this travel line item while in Travel
Booking Provider's web site.
TermsAndConditions
List of Terms and conditions (if any) associated with this
travel line item.
confirmationNumber
A unique confirmation number that is useful to both the
traveler and the vendor who is providing the service for this
travel line item. For example, hotel reservation number or
e-ticket number from the airline.
pnrLocator
Passenger Name Record (PNR) Locator that is useful to the
Travel Booking Provider.
quoteExpirationTime
Date and time that this quote will expire. This value is
normally supplied in the PunchoutOrderMessage. If no value is
supplied, it is assumed that there is no expiration time or
date for this quote.
-->
<!ELEMENT TravelDetail ((AirDetail | CarRentalDetail | HotelDetail | RailDetail),
PolicyViolation*,
Comments?,
TermsAndConditions?)>
<!ATTLIST TravelDetail
confirmationNumber %string; #REQUIRED
pnrLocator %string; #IMPLIED
quoteExpirationTime %datetime.tz; #IMPLIED
>
<!-- Air -->
<!--
Air detail information for the air trip.
TripType
Round Trip, One Way, or Multi Leg
AirLeg
Different air leg that makes up this air detail.
For example a round trip from SFO -> TPE with no stops
will have two air legs. One air leg from SFO -> TPE
and another from TPE -> SFO.
AvailablePrice
Other available airfare prices that the user did not pick.
Penalty
Penalty amount (if any). This is normally due to changes or
cancelation of the ticket.
-->
<!ELEMENT AirDetail (TripType,
AirLeg+,
AvailablePrice*,
Penalty?)>
<!--
Define a single leg in the air travel.
Vendor
Airline vendor name and information.
AirLegOrigin
Originating airport for this air leg.
AirLegDestination
Destination airport for this air leg.
BookingClassCode
Airline booking class code. This is the de-facto
airline standard. For example,
F, FN, P, R, A - first class
C, CN, D, J, I, Z - business class.
Y, YN, B, BN, M, H, V, VN, O, Q, QN, S,
K, KN, L, U, T, W - coach class.
Rate
Rate for this particular air leg. If specify, the total
of all the rate for the different air legs must add up
to the total the line item level.
Meal
Meal information for this air leg (if any)
travelSegment
Textual information to identify this travel segment.
This information is specific to the Travel Booking Provider.
departureTime
Departure date and time for this air leg
arrivalTime
Arrival date and time for this air leg
flightNumber
Flight number for this air leg
seatNumber
Seat number for this air leg
seatType
Seat type
aisle - Aisle
window - Window
middle - Middle
upgrade
Is this ticket an upgrade?
stops
The number of stop for this air leg.
0 if it is a direct flight. If no information is supplied
it is defaulted to 0.
equipment
The plane equipment information for this air leg
-->
<!ELEMENT AirLeg (Vendor,
AirLegOrigin,
AirLegDestination,
BookingClassCode?,
Rate?,
Meal*)>
<!ATTLIST AirLeg
travelSegment %string; #REQUIRED
departureTime %datetime.tz; #REQUIRED
arrivalTime %datetime.tz; #REQUIRED
flightNumber %string; #REQUIRED
seatNumber %string; #IMPLIED
seatType (window | aisle | middle) #IMPLIED
upgrade (yes) #IMPLIED
stops %r8; #IMPLIED
equipment %string; #IMPLIED
>
<!--
Originating airport for this Air Leg.
Airport
Originating airport
-->
<!ELEMENT AirLegOrigin (Airport)>
<!--
Destination airport for this Air Leg.
Airport
Destination airport
-->
<!ELEMENT AirLegDestination (Airport)>
<!--
Airport information that includes the iso airport code
Address
Physical adress of the airport.
airportCode
The 3 letter IATA airport code.
-->
<!ELEMENT Airport (Address?)>
<!ATTLIST Airport airportCode %string; #REQUIRED>
<!---
Meal information used by air, hotel and rail.
BookingClassCode
Code for the meal. For example, airlines use
B - Breakfast
C - Complimentary liquor
D - Dinner
F - Food for purchase
G - Food and beverage for purchase
H - Hot meal
K - Continental breakfast
L - Lunch
M - Meal
N - No meal service
O - Cold meal
P - Liquor for purchase
R - Refreshments
S - Snack or brunch
V - Refreshments for purchase
Description
Textual description of the meal, including any special needs
such as vegetarian or dairy-free.
-->
<!ELEMENT Meal (BookingClassCode?, Description?)>
<!-- Car Rental -->
<!--
Car rental information.
Vendor
Car rental vendor information.
CarRentalPickup
Pickup location for the rental car.
CarRentalDropoff
Drop off location for the rental car.
BookingClassCode
4 letter code for car.
1st Letter - M (Mini), E (Economy), C (Compact), S (Standard),
I (Intermediate), F (Full size), P (Premium), L (Luxury)
V (MiniVan), X (Special)
2nd Letter - B (2 door), C (2/4 door), D (4 door), T (Convertible),
F (Four wheel drive), V (Van), W (Wagon), S (Sport)
X (Special)
3rd Letter - A (Automatic), M (Manual)
4th Letter - R (A/c), N (No A/C)
CarRentalFee
Mutliple car rental fee can be specified to capture the
break down of different fees. The total of these fees must
add up to the total at the line item level.
LimitedMileage
Mileage limit information
AvailablePrice
Other available prices for car rental that the user did not pick.
travelSegment
Textual information to identify this travel segment.
This information is specific to the Travel Booking Provider.
pickupTime
The intended pickup date and time
dropoffTime
The intended dropoff date and time
-->
<!ELEMENT CarRentalDetail (Vendor,
CarRentalPickup,
CarRentalDropoff,
BookingClassCode?,
CarRentalFee+,
LimitedMileage?,
AvailablePrice*)>
<!ATTLIST CarRentalDetail
travelSegment %string; #REQUIRED
pickupTime %datetime.tz; #REQUIRED
dropoffTime %datetime.tz; #REQUIRED
>
<!--
Physical location where the rental car should be picked up. This
is either an Airport or off airport car rental location.
Airport
An airport location.
Address
Physical address of the car rental location
-->
<!ELEMENT CarRentalPickup (Airport | Address)>
<!--
Physical location where the rental car should be dropped off.
This is either an Airport or off-airport car rental location.
Airport
An airport location.
Address
Physical address of the car rental location
-->
<!ELEMENT CarRentalDropoff (Airport | Address)>
<!--
This specifies the quantity and the unit of measure of the mileage
limit.
UnitOfMeasure
Unit of measure either miles or kilometers.
quantity
The mileage limit amount.
-->
<!ELEMENT LimitedMileage (UnitOfMeasure)>
<!ATTLIST LimitedMileage
quantity %r8; #REQUIRED
>
<!--
Car rental fee information. CarRentalFee captures the actual
charges and fee that applies to this rental. Conditional charges
such as extra mileages that are over the mileage limit should not
be specified here but rather in the TermsAndConditions text.
Total
Total amount for this car rental fee. All the total for the rates
must add up to this amount.
Rate
The individual broken-down fee information.
type
Type of rate
baseRate - Base rental rate
additionalDriver - Additional driver fee
airportAccessFee - Airport Access fee
dropOffCharge - Drop off charge
vehicleLicensingFee - Vehicle lincensing fee
touristTax - Tourist tax
prepaidGasoline - Prepaid gasoline charge
navigationSystem - Navigation system
childSeat - Child seat charge
luggageRack - Luggage rack charge
collisionDamageInsurance - Collision damage insurance
liabilityInsurance - Liability insurance
mobilePhone - Mobile phone base charge
other - Other charges.
-->
<!ELEMENT CarRentalFee (Total, Rate*)>
<!ATTLIST CarRentalFee
type (baseRate | additionalDriver | airportAccessFee | dropOffCharge |
vehicleLicensingFee | touristTax | prepaidGasoline |
navigationSystem | childSeat | luggageRack | collisionDamageInsurance |
liabilityInsurance | mobilePhone | other) "baseRate"
>
<!-- Hotel -->
<!--
Hotel detail information.
Vendor
Hotel vendor information.
Address
Physical address of the hotel. This is might be different
from the address specified in the Vendor field as the vendor
address might be the head quarter address.
RoomType
The type of room reserved.
BookingClassCode
Hotel booking class code.
Meal
Any complementary meals that are included with the room. For
example, complementary continental breakfast.
Rate
Hotel rate information. Multiple rates can be specified. For
example, the night rate, valet parking rate, and other rates.
AvailablePrice
Other available prices that user did not pick. Available
prices can be from the same vendor or different vendor.
travelSegment
Textual information to identify this travel segment. This
information is specific to the Travel Booking Provider. -
Error importing xsd as external definition
I'm importing a wsdl file as external definition and it references some xsd files that I'm trying to import too. Specifically there are 2 of them that I can't import in PI, as I get the next error:
Error when loading XML document (Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.UnknownHostException: www.w3.org)
XSD files might be found under next urls:
[XAdES.xsd|https://www3.aeat.es/ADUA/internet/es/aeat/dit/adu/xades/XAdES.xsd]
[xmldsig-core-schema.xsd|https://www3.aeat.es/ADUA/internet/es/aeat/dit/adu/xades/xmldsig-core-schema.xsd]
and are meant to be used to sign the document.
I have validated the files using the service in the next url:
[http://www.w3.org/2001/03/webdata/xsv|http://www.w3.org/2001/03/webdata/xsv] as well as in Altova XML Spy.
Has anyone any idea of what the problem might be? It is really interfering in my development.
Thanks in advance.Ok I think I might have solved it. First there was a pair of problems with the file xmldsig-core-schema.xsd.
1. The name couldn't be used in PI as '-' characters are not allowed.
I changed the name to xmldsig_core_schema.xsd
2. The file had these lines at the start:
<!DOCTYPE schema PUBLIC "-//W3C//DTD XMLSchema 200102//EN" "http://www.w3.org/2001/XMLSchema.dtd" [
<!ATTLIST schema
xmlns:ds CDATA #FIXED "http://www.w3.org/2000/09/xmldsig#"
>
<!ENTITY dsig 'http://www.w3.org/2000/09/xmldsig#'>
<!ENTITY % p ''>
<!ENTITY % s ''>
]>
PI doesn't like that if you import the file as XSD because I guess that is DTD not XSD format.
I removed those lines.
With these two changes this file could be imported.
However I still had problems with the XAdES.xsd file. PI couldn't recognize the import of xmldsig-core-schema.xsd file:
<xsd:import namespace="http://www.w3.org/2000/09/xmldsig#" schemaLocation="http://www.w3.org/TR/2002/
REC-xmldsig-core-20020212/xmldsig-core-schema.xsd"/>
It didn't like the URL, so I changed it to make reference to my local file.
After this, it all worked. The question is, will it also work in runtime when I'll make use of these external definitions created? Or will my changes have an impact on the results? I guess it will work fine but perhaps I'm wrong.
Besides, when activated I got the next warning:
Name of '/schema/complexType("TimeStampType")/sequence/choice/element("XMLTimeStamp")' starts with 'xml'
There's an element name that starts by XML. Is this forbidden? Will I have problems if I activate and use it just as it is?
Thanks for the answers. -
How to import songs from external drive to itunes in Leopard?
my computer had issues after installing leopard and i had to erase everything on my computer. since all of my music files from itunes are on my external hard drive, they are safe! but now that i'm starting from scratch on my iBook, how do i tell the computer to import all my music files to my itunes?
i mean, i know how to click one song at a time and import them one at a time but that would take a long time. is there any easier way?
thanks muchIts very easy. I hope that you have all your music in one folder. Just drag that folder which contains every music you have to the iTunes icon in the dock. iTunes will open and copy every file on its own.
-
Setup problem importing library from external hard drive
my old iMac died, and I am setting up iPhoto on my new iMac (10.7.2). I had backed up my iPhoto library to an external hard drive before the old iMac went kaput. However, when I try to import this library when setting up iPhoto, the Library file itself is inhibited / not selectable.
I also tried copying the Library to my Pictures folder on the new iMac, but that is failing (error code -36) about a third of the way through. That incomplete file, also, is inhibited.
appreciate any suggestions on how to confront this problem. thanks.Thanks, Terence.
When I held down the command/option keys, it prompted me to select a Library. This time, I chose the Library resident on the EHD. iPhoto then indicated it needed to run an upgrade in order to render the library (paraphrasing - I should've written down what it said). That took about 20 minutes, and then it proceeded to import. I could see all of my Events, and everything appeared to be good to go. My plan was going to be to then figure out a way to get the photos individually backed up and then monkey with it some more until I could have the Library resident on the Mac HD and backed up on the EHD.
However, before I got that far, I noted that many of my Events were empty. I would see a thumbnail image for it, but clicking in it would indicate that there were zero photos in that Event. I'm flummoxed.
Right now, I am individually exporting the files to newly created sub-folder within Pictures so that I at least have a copy of everything on the new iMac, but that is failing about a third of the way through and yielding an error indicating that the files cannot be copied to users/.... Further, I'm not exactly sure what to make of the empty Events issue. I read another thread on this that says to close and re-launch iPhoto with Command/Option held down and run the repairs, but someone had written that their empty events vanished when they closed the application. Should I proceed?
Thanks again to you both.
Maybe you are looking for
-
Can anyone help me to verify my account, i have tried sending the e-mail a few times but it wont send.?
-
Cannot sync ipone. Message says 'sync session failed to start'. What do I do?
-
I am creating a webi report where each person has own complaint numbers. The result I wanted to be: Person A Person B Person C 1 4 7 3 5 9 2 8 6 I tried several ways but nothing come out correctly. One of them is I just put complaint number and all
-
Photosmart Pro B9180 not sold anymore
On the HP website and one aother site i read that the Photosmart pro B9180 printer is not sold anymore. I wonder if anyone else has found this information and if it is correct will HP produce a successor of this excellent printer? Jeu
-
Hi Team, I would like to maintain planning time fence value in material master. I do not have any clue that how to determine the value for the planning time fence. Some where i read that the planning time fence value will be the interval time between