Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Create README Issue #1. #1. Issue 34. #34. Issue #2. #2. Added role="warning" to all sch:report statements. Issue 3. #3. Issue 4. #4. "Do not leak representation into data definition" Issue #5. #5. Added introduction text supporting international use of NIEM. Issue 6. #6. Section 4.1.2 Extension schema document Issue 7. #7. "6.3.1 Namespaces enhance reuse" Tweaked the suggested text, and added a bit about validation. Issue 36. #36. Revise language from BCP 14 to "IETF Best Current Practice 14". Cleaned up stray whitespace. Issue 8. #8. Clarify language around "reflect the real world". Issue 9. #9. Revised as indicated by the issue, with more supporting text. Defined "document" as a lightweight defined term. Added term references to normative terms. Tweaked makefile to clean up better. Cleaned up reference syntax. Updated validation of the doc to use a minimal NIEM subset. Updated NDR doc accordingly with xsi:nil="true" to support validation. Issues #10: #10. Added examples of structures:{uri,ref,id} and xml:base, with supporting text. Added 'example' namespace (a namespace for example exchange content), and introduced it. Issue #11: #11. Merged problematic trailing sentence into an earlier paragraph with the same topic. Issue #12: #12. Revised identifier o67 to k25 as indicated by the issue. Revised "link metadata" terminology to "relationship metadata", in line with current terminology. Issue #13: #13. Revised to exclude type xs:string from use in the "$lexical-form"^^$datatype-IRI syntax. Issue #14: #14. Revised indicated sentences. Issue #15: #15. Updated the indicated paragraph to clarify effect of import statements. Issue #16: #16. Moved rule up in the section. Issue #17: #17. Revised as requested. Issue #18: #18. Revised as indicated. Issue #19: #19. Clarified the indicated text. Removed vague reference with no clear referent. Issue #20: #20. Revised as indicated. Issue #21: #21. Added suggested text, reworked a bit. Issue #22: #22. Changed as indicated, with small modification. Issue #23: #23. Removed one of the duplicates. Issue #24: #24. Made change as indicated. Issue #25: #25. Align association terminology with augmentation terminology: "association", "association element declaration", and "association type". Updated title of object type derivation rule. Updated title and supporting text for rule enforcing that types derived from augmentation types are themselves augmentation types. Issue #26: #26. Updated definition for term "augmentation" to clarify that it's an instance element. Cleaned up language around term "augmentation elemetn declaration". Issue #27: #27. The type that carries an augmentation point is the "base type" of the augmentation point. Issue #28: #28. Updated rules to uniformly use term "augmentation point element". Issue #29: #29. Merged Schematron rule on metadata types with text rule on metadata types. Metadata types may be derived from other metadata types. Issue #30: #30. Fixed awkward wording. Issue #32: #32. Fixed typo as requested. Issue #35: #35. We've removed the Schematron warnings for things that Schematron can't check, so I removed the text that describes that use case for Schematron warnings. Issue #69: #69. Moved as requested. Issue #37: #37. Removed as requested. Issue #39: #39. Accepted suggested text. Issue #40: #40. Revised definition of "local term" to use "may" instead of looking like it's indicating a "must". Issue #41: #41. Revised rule name from "component" to "element or attribute". Issue #42: #42. Revised as requested. Issue #44: #44. Revised as indicated. Issue #45: #45. Revised supporting text a bit, including dropping the sentence indicated. Issue #46: #46. Put the indicated rules into a section on annotations for external adapters. Issue #47: #47. Revised section on structures namespace to allow for profile schemas. Issue #48: #48. Revised as indicated. Issue #49: #49. Revised as indicated. Issue #50: #50. Added similar text to indicated sections. Issue #51: #51. Updated as indicated. Issue #52: #52. Added "data definition" to section titles for standard opening phrases for element declarations and type definitions. Issue #53: #53. Updated opening phrases to start with a captial letter. Issue #54: #54. Revised rules for standard opening phrase to include attributes as well as elements Issue #55: #55. Revised rule to "profiles" from "different views". Issue #56: #56. Revised rule titles for consistency. Issue #57: #57. Revised as requested. Issue #59: #59. Added example as indicated. Supported with text and rearragned a bit. Issue #60: #60. Updated as indicated. Fixed typo in schematron rule. Issue #61: #61. Updated percent from 0.25 to 25. Issue #62: #62. Added example of the use of appinfo:appliesToTypes. Added link to that example. Issue #63: #63. Added sentence as indicated. Issue #64: #64. Revised as indicated. Issue #66: #66. Reordered out-of-order references. Issue #67: #67. Stood down references to the errata for XML namespaces. Issue #68: #68. Revised definition of percent. Issue #38: #38. Updated reference to NIEM Code Lists Specification to version 4.0. Updated document version and date for 4.0.
- Loading branch information