Skip to content

Update readme.md for version 1.4 #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lorenzhaas wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update readme.md for version 1.4 #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 18 additions & 4 deletions readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
MTConnect Schema Files Versions 1.0 - 1.3
MTConnect Schema Files Versions 1.0 - 1.4
===

Files are named with respect to the section of the standard they apply.
Expand Down Expand Up @@ -49,8 +49,22 @@ Version 1.3 (With XSD 1.0 compatible files)
MTConnectError_1.3_1.0.xsd
```

Microsoft XML an many legacy XML parsers are not current on the XML Schema 1.1 standard accepted in 2012 by the w3c. The MTConnect standard takes advantage of the latest advances in extensibility to add additional properties in a regulated manor using the xs:any tag and specifying they tags must be from another namespace.
Version 1.4 (With XSD 1.0 compatible files)
---

```
MTConnectAssets_1.4.xsd
MTConnectAssets_1.4_1.0.xsd
MTConnectDevices_1.4.xsd
MTConnectDevices_1.4_1.0.xsd
MTConnectStreams_1.4.xsd
MTConnectStreams_1.4_1.0.xsd
MTConnectError_1.4.xsd
MTConnectError_1.4_1.0.xsd
```

Microsoft XML and many legacy XML parsers are not current on the XML Schema 1.1 standard accepted in 2012 by the w3c. The MTConnect standard takes advantage of the latest advances in extensibility to add additional properties in a regulated manor using the xs:any tag and specifying the tags must be from another namespace.

We are also using Schema Versioning from XML Schema 1.1 and will be creating new schema that use these new features as we move into 1.4 and beyond. There are many XML Parsers that now correctly handle XML Schema 1.1, namely Raptor from Altova and Xerces from Apache. If you must use Microsoft XML with validation turned on, then you must use the ...1.3_1.0.xsd files in the directory.
We are also using Schema Versioning from XML Schema 1.1 and will be creating new schema that use these new features as we move into 1.4 and beyond. There are many XML Parsers that now correctly handle XML Schema 1.1, namely Raptor from Altova and Xerces from Apache. If you must use Microsoft XML with validation turned on, then you must use the ...1.3_1.0.xsd or ...1.4_1.0.xsd files in the directory.

The 1.3_1.0.xsd files will support the MSXML parser and validation, but will not support the advance extensibility. If you want both, talk with Microsoft to update their parser.
The 1.3_1.0.xsd and 1.4_1.0.xsd files will support the MSXML parser and validation, but will not support the advance extensibility. If you want both, talk with Microsoft to update their parser.