Datatype Validation of StratML Parts 1 & 2

StratML is an XML Format which, at present, holds Strategic Plans, Performance Plans and Reports.

The terms used in XML Files often require specific datatype formats to assist in interoperability with other formats.

For example, a date can be in the format YYYY-MM-DD (ISO 8601). If no other formats are to be permitted ... "three weeks after my cat's birthday", etc. ... then the XML File must be validated against a schema (XSD File) or Document Type Definition (DTD). Validation serves two (equally important) functions: 1) The date is "understandable" to other applications, and 2) No third-parties will, in the interest of user friendliness substitute their own cat's birthdays without warning. That would be wrong, and unprofessional.

All XML is plain text, but may include binary segments. Behind the scenes, this is non-negotiable, and there is no technical impediment to high level transparency.

XML 1.0 (Fifth Edition) 1.1 Origin and Goals

And

IETF RFC 4646

2.  The Language Tag

   Language tags are used to help identify languages, whether spoken,
   written, signed, or otherwise signaled, for the purpose of
   communication.  This includes constructed and artificial languages,
   but excludes languages not intended primarily for human
   communication, such as programming languages.

Validation is involked in root node of an XML File with properties in the XSI (Schema Instance) Namespace. On some small screen and Mobile Devices, the editing of large XML Documents may prove awkward, if not impossible and text editing facilities may be wildly impractical. However, equipment limitations should not dictate Specification limitations and an archive of an XML File can always be contained in one "envelope" regardless of the (public access) external files which may be needed for validation.

Root Node Examples

PSI Archive/Envelope XSD Schema (XHTML 1.0)

PSI Archive/Envelope for StratML (Empty)

Apache Xerces Project

StratML Part 1 XML

Test (NASA 2011 StratML Part 1), non-standard components redacted. This file is both valid XML and valid StratML Part 1.

Validation Trace (Validation Errors: none)

Public Access Schema. http://xml.gov/stratml/references/StrategicPlan.xsd

A sample Archive/Envelope (XHTML 1.0). StratML is validated in place (Validation Trace ca. Line 75).

StratML Part 2 XML

Test (NASA 2011 StratML Part 2), non-standard components redacted. This file is both valid XML and valid StratML Part 2.

Validation Trace (Validation Errors: none)

Public Access Schema. http://xml.gov/stratml/references/PerformancePlanOrReport.xsd

A sample Archive/Envelope (XHTML 1.0). StratML is validated in place (Validation Trace ca. Line 75).

Since validation is involked by the XSI Namespace, a local machine copy of the XSD Schema is identical to the XML public copy. StratML Documents are intended for the Public Domain and Public Access. Still, annotated drafts can be exchanged between editors for small or proposed changes, prepublication. XFORMS make possible editing on-line. For manual editing, the file may be validated against a local schema (XHTML 1.0 in this case) which has been modified to accept an embeded block level XML element. Normally only local validation is practical in this case, but in Bring Your Own Device (BYOD) and Work From Home situations, in-house Source Control and local validation can replace complex, centralized, generalized Firewalls.

There are several advantages to retaining the manual editing option.