100% Offline Reference
BYOS StAEDI Schemas
Authoring Custom StAEDI XML & JSON Companion Schemas (BYOS)
Enterprise trading partners routinely add custom REF qualifiers, proprietary ZZ codes, or stricter loop cardinalities beyond base specifications. EdiPrism's BYOS adapter loads both native io.xlate:staedi XML schemas and concise JSON schemas offline.
Minimal Clean-Room StAEDI XML Schema Snippet
<schema xmlns="http://xlate.io/EDISchema/v4" description="Custom Partner 850 Overlay">
<transaction>
<sequence>
<segment type="BEG" minOccurs="1" maxOccurs="1"/>
<segment type="REF" minOccurs="1" maxOccurs="10"/>
<loop code="N1_LOOP" maxOccurs="200">
<sequence>
<segment type="N1" minOccurs="1"/>
<segment type="N3" maxOccurs="2"/>
<segment type="N4" maxOccurs="1"/>
</sequence>
</loop>
</sequence>
</transaction>
</schema>
Frequently Asked Engineering Questions
Are custom schemas synced to any external server?
Never. Custom XML and JSON schema files are read strictly from your local project directory or filesystem and cached locally per trading-partner ISA/UNB sender-receiver pair.
Inspect, Diff, Validate & Scrub This Payload Offline in Your JetBrains IDE
Never paste regulated healthcare PHI (837/835/271) or supply-chain payloads (850/ORDERS) into browser parsers. EdiPrism X12 EDIFACT runs 100% air-gapped inside IntelliJ IDEA, PyCharm, DataGrip, Rider, GoLand, and WebStorm with a free core tier and a 14-day [Pro] trial.