Example set of DFDL 1.0 properties

Similar documents
Example set of DFDL 1.0 properties

Framing how values are extracted from the data stream. Includes properties for alignment, length, and delimiters.

Multi-Server Based Namespace Data Management of Resource Namespace Service

Complex type. This subset is enough to model the logical structure of all kinds of non-xml data.

* * DFDL Introduction For Beginners. Lesson 2: DFDL Language Basics. DFDL and XML Schema

XDI Requirements and Use Cases

Framing how values are extracted from the data stream. Includes properties for alignment, length, and delimiters.

Chin Guok, ESnet. Network Service Interface Signaling and Path Finding

Open Cloud Computing Interface Platform

Updates: 2710 September 2003 Category: Standards Track. Source Address Selection for the Multicast Listener Discovery (MLD) Protocol

Level of Assurance Authentication Context Profiles for SAML 2.0

Network Working Group Request for Comments: Category: Best Current Practice January 2004

Open Cloud Computing Interface Service Level Agreements

OCCI Compute Resource Templates Profile

Steven Newhouse, Microsoft Mario Antonioletti, EPCC August 1, 2011

Network Working Group. November Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4)

Metadata for SAML 1.0 Web Browser Profiles

Michel Drescher, FLE, Ltd. Standardised Namespaces for XML in GGF (draft 09) N/A

SMOA Computing HPC Basic Profile adoption Experience Report

Request for Comments: 2711 Category: Standards Track BBN October 1999

Configuration Description, Deployment and Lifecycle Management Working Group (CDDLM-WG) Final Report

Expires: February 25, 2004 August 27, Using the NETCONF Configuration Protocol over Secure Shell (SSH) draft-wasserman-netconf-over-ssh-00.

Request for Comments: 3934 Updates: 2418 October 2004 BCP: 94 Category: Best Current Practice

Mapping between DFDL 1.0 Infoset and XML Data Model

Network Working Group. Category: Informational January Unused Dynamic Host Configuration Protocol (DHCP) Option Codes

Position Paper: Facets for Content Components

Category: Standards Track September 2003

OpenOffice Specification Sample

Data Format Description Language (DFDL)

Use and Interpretation of HTTP Version Numbers

OASIS - Artifact naming guidelines

Category: Standards Track December 2003

Network Working Group. Category: Standards Track September 2003

IETF TRUST. Legal Provisions Relating to IETF Documents. Approved November 6, Effective Date: November 10, 2008

Network Working Group. Category: Standards Track February SIEVE Filtering: Spamtest and VirusTest Extensions

Network Working Group Request for Comments: 3634 Category: Standards Track Comcast Cable J. Bevilacqua N. Davoust YAS Corporation December 2003

Network Working Group. Category: Standards Track <draft-aboba-radius-iana-03.txt> 30 March 2003 Updates: RFC IANA Considerations for RADIUS

Deployment Profile Template Version 1.0 for WS-Reliability 1.1

Request for Comments: 4633 Category: Experimental August 2006

{Describe the status and stability of the specification here.}

IETF TRUST. Legal Provisions Relating to IETF Documents. February 12, Effective Date: February 15, 2009

Request for Comments: 2493 Category: Standards Track January 1999

Open Cloud Computing Interface Text Rendering

Network Working Group Request for Comments: 3397 Category: Standards Track Apple Computer, Inc. November 2002

SWOP Specifications for Web Offset Publications Edition 10.0 Errata

Updates: 2535 November 2003 Category: Standards Track

Network Working Group. Category: Informational January 2006

Network Working Group Request for Comments: 3937 Category: Informational October 2004

HPCP-WG, OGSA-BES-WG March 20, Smoa Computing HPC Basic Profile Adoption Experience Report

J. Basney, NCSA Category: Experimental October 10, MyProxy Protocol

Editor: Mark Morgan, University of Virginia Category: Recommendation 31 October

GWD-R (draft-ogf-jsdl-spmd-008) Andreas Savva, Fujitsu

E. Lewis ARIN September 23, KEY RR Secure Entry Point Flag draft-ietf-dnsext-keyrr-key-signing-flag-09. Status of this Memo

OASIS Specification Document Template Usage

Authentication, Authorization and Accounting Requirements for the Session Initiation Protocol

Abstract Code-Signing Profile of the OASIS Digital Signature Services

XACML Profile for Requests for Multiple Resources

Network Working Group Internet-Draft August 2005 Expires: February 2, Atom Link No Follow draft-snell-atompub-feed-nofollow-00.

Network Working Group. Category: Informational May OSPF Database Exchange Summary List Optimization

Network Working Group. Category: Informational April A Uniform Resource Name (URN) Namespace for the Open Geospatial Consortium (OGC)

Internet-Draft Harvard U. Editor March Intellectual Property Rights in IETF Technology. <draft-ietf-ipr-technology-rights-02.

Test Assertions for the SCA Assembly Model Version 1.1 Specification

Category: Best Current Practice February Early IANA Allocation of Standards Track Code Points

Hierarchical Resources: Non-XML Resource Use Case

Data Format Description Language (DFDL) v1.0 Core Specification

SCA JMS Binding v1.1 TestCases Version 1.0

TestCases for the SCA Assembly Model Version 1.1

Proposal for SAML Attribute Changes

Network Working Group Request for Comments: August Address-Prefix-Based Outbound Route Filter for BGP-4

Feb :33 draft-glenn-id-sensor-alert-mib-01.txt Page 1

Request for Comments: 3578 Category: Standards Track dynamicsoft J. Peterson NeuStar L. Ong Ciena August 2003

Network Working Group Internet-Draft January 25, 2006 Expires: July 29, Feed Rank draft-snell-atompub-feed-index-05.txt. Status of this Memo

Network Working Group. Cisco Systems June 2007

Network Working Group. Intended status: Standards Track Columbia U. Expires: March 5, 2009 September 1, 2008

Network Working Group Internet-Draft August 2005 Expires: February 2, Atom Link No Follow draft-snell-atompub-feed-nofollow-03.

Request for Comments: 5179 Category: Standards Track May 2008

Metadata for SAML 1.0 Web Browser Profiles

Request for Comments: 5010 Category: Standards Track Cisco Systems, Inc. September 2007

DFDL Enhancements SOA Subcommittee

Network Working Group. Updates: 3463, 4468, 4954 June 2008 Category: Best Current Practice. A Registry for SMTP Enhanced Mail System Status Codes

Category: Standards Track October 2006

Network Working Group Request for Comments: December 2004

Network Working Group Request for Comments: 2514 Category: Standards Track Cisco Systems K. Tesink Bellcore Editors February 1999

Test Assertions for the SCA_J Common Annotations and APIs Version 1.1 Specification

Category: Informational March Methods for Avoiding the "Small-Subgroup" Attacks on the Diffie-Hellman Key Agreement Method for S/MIME

Request for Comments: 4481 Columbia U. Category: Standards Track July 2006

Category: Informational October Common Format and MIME Type for Comma-Separated Values (CSV) Files

SCA-J POJO Component Implementation v1.1 TestCases Version 1.0

Category: Informational March Portable Font Resource (PFR) - application/font-tdpfr MIME Sub-type Registration

Network Working Group. Category: Standards Track June Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Subscriber-ID Option

Expires in six months 24 October 2004 Obsoletes: RFC , , 3377, 3771

Service Component Architecture Client and Implementation Model for C++ Test Cases Version 1.1

TestCases for the SCA POJO Component Implementation Specification Version 1.1

Open Cloud Computing Interface - HTTP Protocol

Network Working Group. Category: Standards Track August Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option

Network Working Group Request for Comments: 4603 Category: Informational Cisco Systems July Additional Values for the NAS-Port-Type Attribute

Certification Test Plan SSRF Conformance for OpenSSRF Software v Document WINNF-14-S-0023

SAML V2.0 Profile for Token Correlation

Network Working Group Request for Comments: 4424 February 2006 Updates: 4348 Category: Standards Track

Test Assertions for the SCA Web Service Binding Version 1.1 Specification

Transcription:

Example set of DFDL 1.0 properties Status of This Document This working draft document provides an example to the OGF community of the Data Format Description Language (DFDL) standard. Distribution is unlimited Copyright Notice Copyright Open Grid Forum (2012). Some Rights Reserved. Distribution is unlimited. Abstract This document provides a set of DFDL properties that can be used as defaults for creating DFDL schema. Table of contents 1. Introduction...2 2. Example DFDL defineformat...3 3. Authors and Contributors...6 4. Intellectual Property Statement...6 5. Disclaimer...6 6. Full Copyright Notice...6 7. References...6 dfdl-wg@ogf.org Page 1 of 6

1. Introduction Data Format Description Language 1.0 [DFDL] is a language with a rich set of properties for modeling text and binary data formats. For portability of DFDL schemas, the language is designed to have very few built-in default values for these properties. This means that a DFDL schema can not be silent about any property that is applicable to any of the objects in the schema. To assist first -time DFDL schema authors, this document provides a defineformat annotation that can be used to provide defaults for just about all DFDL properties. The defineformat annotation is defined within a DFDL schema which itself defines no schema objects. The recommended usage is for the DFDL author to refer to this DFDL schema from his own DFDL schema using xs:import [XSDLV1]. If any property values need to be changed, it is recommended that the DFDL author either: o o overrides the property values in his own DFDL schema makes a copy of this DFDL schema in a different namespace and overrides the property values in the copy. The values for the properties are suitable for modeling text data, in particular they can be used without modification when modeling standard Comma Separated Value (CSV) text data [RFC4180]. The defineformat annotation provides defaults for all properties where it makes sense to do so. However there are some properties where a default is not appropriate, and for these the defineformat is silent. An example is the length property, which if used would typically vary on a per element basis. DFDL escape scheme property values are defined in an accompanying defineescapescheme annotation which is referenced from the defineformat annotation. Section 2 defines the DFDL schema containing the defineformat and defineescapescheme annotations. dfdl-wg@ogf.org Page 2 of 6

2. Example DFDL defineformat In the schema below, the file name is assumed to be DFDLGeneralFormatDefinition.xsd. When copying the text into a DFDL schema file, the copyright statement must be retained. <?xml version="1.0" encoding="utf-8"?> (C) Copyright IBM Corp 2011 All Rights Reserved This DFDL schema provides a set of DFDL property values to assist in the creation of DFDL schema that model general text or b inary data, or a mixture of text and binary data. DFDL Version 1.0 Schema Version 1.0 The primary purpose of this schema is to provide sensible values for the vast majority of DFDL properties as an illustration. However the properties are a consistent set that model a variable length text format consisting of a single record of CSV dat a, (for example, aaa,bbb,ccc,ddd,eee). The recommended usage is to refer to this schema from other DFDL schema using a xs:import statement. If any property values need to be changed, it is possible to update this schema directly, but it is recommended either to override them locally in the schema that includes this one, or make a copy of this schema in a different namespace. For example, to model fixed length, binary data then override "representation" to "binary", override "lengthkind" to "explicit" and set "length". Example usage: 1) To apply the properties in this schema as defaults for all objects in another DFDL schema: <xs:schema xmlns:tns="http://www.ogf.org/dfdl/dfdl-1.0/examples/"... > <xs:import namespace="http://www.ogf.org/dfdl/dfdl-1.0/examples/" schemalocation="dfdlgeneralformatdefinition.xsd"/> <xs:annotation> <xs:appinfo source="http://www.ogf.org/dfdl/"> <dfdl:format ref="tns:generalformat"... override property values if desired... </dfdl:format> </xs:appinfo> </xs:annotation>... </xs:schema> 2) To apply the properties in this schema to specific schema objects and override selected property values: <xs:schema xmlns:tns="http://www.ogf.org/dfdl/dfdl-1.0/examples/"... > dfdl-wg@ogf.org Page 3 of 6

<xs:import namespace="http://www.ogf.org/dfdl/dfdl-1.0/examples/" schemalocation="dfdlgeneralformatdefinition.xsd"/> <xs:element name="root" dfdl:ref="tns:generalformat" dfdl:lengthkind="explicit" dfdl:length="80"> <xs:complextype> <xs:sequence dfdl:ref="tns:generalformat" dfdl:separator="">... </xs:sequence> </xs:complextype> </xs:element> </xs:schema> <xs:schema xmlns:xs="http://www.w3.org/2001/xmlschema" xmlns:dfdl="http://www.ogf.org/dfdl/dfdl-1.0/" targetnamespace="http://www.ogf.org/dfdl/dfdl-1.0/examples/" xmlns:tns="http://www.ogf.org/dfdl/dfdl-1.0/examples/" > <xs:annotation> <xs:appinfo source="http://www.ogf.org/dfdl/"> A general purpose defineformat annotation. <dfdl:defineformat name="generalformat"> <dfdl:format encoding="utf-8" utf16width="fixed" byteorder="bigendian" ignorecase="no" outputnewline="%cr;%lf;" alignment="1" alignmentunits="bytes" fillbyte="0" leadingskip="0" trailingskip="0" lengthkind="delimited" lengthunits="characters" prefixincludesprefixlength="no" representation="text" textpadkind="none" texttrimkind="none" escapeschemeref="tns:generalblockescapescheme" textbidi="no" textbiditextordering="implicit" textbidisymmetric="yes" textbiditextshaped="no" textbidinumeralshapes="nominal" textbidiorientation="rtl" textstringjustification="left" textstringpadcharacter="%sp;" truncatespecifiedlengthstring="no" textoutputminlength="0" textnumberjustification="right" textnumberpadcharacter="0" decimalsigned="yes" textnumbercheckpolicy="lax" textnumberrep="standard" textstandardbase="10" textnumberrounding="pattern" textnumberroundingmode="roundup" textnumberroundingincrement="0.0" textstandarddecimalseparator="." textstandardgroupingseparator="," textstandardexponentcharacter="e" textstandardzerorep="" textstandardinfinityrep="inf" textstandardnanrep="nan" textnumberpattern="#0" textzonedsignstyle="asciistandard" textbooleanjustification="left" textbooleanpadcharacter="%sp;" textbooleantruerep="true" textbooleanfalserep="false" textcalendarjustification="left" textcalendarpadcharacter="%sp;" calendarpatternkind="implicit" calendarpattern="yyyy-mm-dd't'hh:mm:ss" calendarcheckpolicy="lax" calendartimezone="utc" calendarobservedst="yes" calendarfirstdayofweek="monday" calendardaysinfirstweek="4" calendarcenturystart="53" dfdl-wg@ogf.org Page 4 of 6

calendarlanguage="en-us" occurscountkind="parsed" sequencekind="ordered" separator="," separatorpolicy="required" separatorposition="infix" initiatedcontent="no" floating="no" choicelengthkind="implicit" initiator="" terminator="" documentfinalterminatorcanbemissing="no" emptyvaluedelimiterpolicy="none" nilkind="literalvalue" usenilfordefault="no" nilvalue="nil" nilvaluedelimiterpolicy="none" binarynumberrep="binary" binarypackedsigncodes="c D F C" binarydecimalvirtualpoint="0" binarynumbercheckpolicy="lax" binaryfloatrep="ieee" binarycalendarrep="bcd" binarycalendarepoch="1970-01-01t00:00:00+00:00" binarybooleantruerep="1" binarybooleanfalserep="0"> </dfdl:format> </dfdl:defineformat> An example defineescapescheme annotation. Assumes 'block' style escaping. <dfdl:defineescapescheme name="generalblockescapescheme"> <dfdl:escapescheme escapekind="escapeblock" escapeblockstart='"' escapeblockend='"' escapeescapecharacter='"' generateescapeblock="whenneeded" extraescapedcharacters="%#x0d; %#x0a;"> </dfdl:escapescheme> </dfdl:defineescapescheme> </xs:appinfo> </xs:annotation> </xs:schema> dfdl-wg@ogf.org Page 5 of 6

3. Authors and Contributors Stephen M. Hanson, IBM Software Group, Hursley, Winchester,UK smh@uk.ibm.com We greatly acknowledge the contributions made to this document by the following people. Suman Kalia, IBM Software Group, Markham, Ontario, Canada 4. Intellectual Property Statement The OGF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the OGF Secretariat. The OGF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights, which may cover technology that may be required to practice this recommendation. Please address the information to the OGF Executive Director. 5. Disclaimer This document and the information contained herein is provided on an As Is basis and the OGF disclaims all warranties, express or implied, including but not limited to any warranty that the use of the information herein will not infringe any rights or any implied warranties of merchantability or fitness for a particular purpose. 6. Full Copyright Notice Copyright Open Grid Forum (2012). Some Rights Reserved. Distribution is unlimited. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included as references to the derived portions on all such copies and derivative works. The published OGF document from which such works are derived, however, may not be modified in any way, such as by removing the copyright notice or references to the OGF or other organizations, except as needed for the purpose of developing new or updated OGF documents in conformance with the procedures defined in the OGF Document Process, or as required to translate it into languages other than English. OGF, with the approval of its board, may remove this restriction for inclusion of OGF document content for the purpose of producing standards in cooperation with other international standards bodies. The limited permissions granted above are perpetual and will not be revoked by the OGF or its successors or assignees. 7. References [DFDL] [XSDLV1] [RFC 4180] DFDL 1.0, http://www.ogf.org/documents/gfd.174.pdf XML Schema Part 1: Structures, http://www.w3.org/tr/xmlschema-1/ Common Format and MIME Type for CSV Files, http://www.ietf.org/rfc/rfc4180.txt dfdl-wg@ogf.org Page 6 of 6