This schema document describes the XML namespace, in a form suitable for import by other schema documents.
See http://www.w3.org/XML/1998/namespace.html and http://www.w3.org/TR/REC-xml for information about this namespace.
Note that local names in this namespace are intended to be defined only by the World Wide Web Consortium or its subgroups. The names currently defined in this namespace are listed below. They should not be used with conflicting semantics by any Working Group, specification, or document instance.
See further below in this document for more information about how to refer to this schema document from your own XSD schema documents and about the namespace-versioning policy governing this schema document.
denotes an attribute whose value is a language code for the natural language of the content of any element; its value is inherited. This name is reserved by virtue of its definition in the XML specification.
Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility.
See BCP 47 at http://www.rfc-editor.org/rfc/bcp/bcp47.txt and the IANA language subtag registry at http://www.iana.org/assignments/language-subtag-registry for further information.
The union allows for the 'un-declaration' of xml:lang with the empty string.
denotes an attribute whose value is a keyword indicating what whitespace processing discipline is intended for the content of the element; its value is inherited. This name is reserved by virtue of its definition in the XML specification.
denotes an attribute whose value provides a URI to be used as the base for interpreting any relative URIs in the scope of the element on which it appears; its value is inherited. This name is reserved by virtue of its definition in the XML Base specification.
See http://www.w3.org/TR/xmlbase/ for information about this attribute.
denotes an attribute whose value should be interpreted as if declared to be of type ID. This name is reserved by virtue of its definition in the xml:id specification.
See http://www.w3.org/TR/xml-id/ for information about this attribute.
denotes Jon Bosak, the chair of the original XML Working Group. This name is reserved by the following decision of the W3C XML Plenary and XML Coordination groups:
In appreciation for his vision, leadership and dedication the W3C XML Plenary on this 10th day of February, 2000, reserves for Jon Bosak in perpetuity the XML name "xml:Father".
PSDZData is the container for the actual firmware and diagnostic data used by ISTA+. The version of PSDZData typically ranges between 60GB to over 100GB. It contains every single firmware file for every BMW model and ECU produced up to that date.
You can also check the Bimmerfest software links for up-to-date repository access. Installation
Try connecting to your vehicle via an ENET cable. When the "Connect" window pops up, you should see a comprehensive list of target vehicle chassis codes (e.g., F020, G011, S15A) corresponding to the V4.27.20 database. Troubleshooting Common Issues 1. "No ZConnectors Found" or Missing Targets
Version is part of the v.4.27.x release family, typically compatible with E-Sys 3.30+ and ISTA 4.27.x . This release supports: v42720 psdzdata lite download install
E-Sys and BMW coding tools operate natively on Windows.
Open Windows File Explorer and navigate to your main E-Sys directory. By default, this is usually: C:\Data\ or C:\EC-Apps\ESG\E-Sys_Data\
C:\EC-Apps\ESG\E-Sys\psdzdata\
Check that the file inside psdzdata reads:
Visit a trusted BMW coding forum such as Bimmerfest or BMWChe.
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. PSDZData is the container for the actual firmware
Tip: Always download the latest version if available, but ensure your ISTA+ version is compatible with the PSDZData version. Generally, newer ISTA+ versions can read older PSDZData, but older ISTA+ versions may struggle with brand new PSDZData structures.
You only need to update PSdZData if your car has recently received a dealer software update and E-Sys can no longer read the modules.
In keeping with the XML Schema WG's standard versioning policy, this schema document will persist at http://www.w3.org/2009/01/xml.xsd.
At the date of issue it can also be found at http://www.w3.org/2001/xml.xsd.
The schema document at that URI may however change in the future, in order to remain compatible with the latest version of XML Schema itself, or with the XML namespace itself. In other words, if the XML Schema or XML namespaces change, the version of this document at http://www.w3.org/2001/xml.xsd will change accordingly; the version at http://www.w3.org/2009/01/xml.xsd will not change.
Previous dated (and unchanging) versions of this schema document are at: