-
Notifications
You must be signed in to change notification settings - Fork 586
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.
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
XSD - Provide concrete XSD that XML Documents can Validated against #1015
Comments
At one point we did work on a schema as a part of the XML Format but it turned out to be more productive (for us at least) to work with an expected wire-format while we hashed it out - we followed a similar model for the JSON Format as it turns out. It's always been a goal to provide a schema so I think it's worthwhile leaving this issue open until that has been done. I'll try taking a crack at this soon (@jskeet) |
Attached File May be a good starting point, If you want other input, let me know, I have been with XML and XSD for over 20 years |
@JimWeier-VeteransUnited I don't see the attachment |
CloudEvent.txt |
Yes .. thanks ... I'll take a look.. |
@JemDay any update on this one? still something we should work on? |
This issue is stale because it has been open for 30 days with no |
If the XML specification is only intended to be an "Abstract" data type, and not a concrete Implementation, It be nice to Create a Standard XSD that can Validate any given XML to See If it Adheres to the Concrete Implementation of a cloud event
CloudEvent.txt, rename this to .xsd - I couldnt upload a .XSD file
The text was updated successfully, but these errors were encountered: