Schema for the XML headers of the SDM Binary Data Format (vers. 0.94)

Simple Type: AnyProjectPath

[Table of contents]

Super-types:	xs:string < AnyProjectPath (by restriction)
Sub-types:	None

Name	AnyProjectPath
Content	Base XSD Type: string pattern = /\d{1,3}/\d{1,5}/\d{1,5}/\d{1,5}/\d{1,5}
Documentation	Project path: for atomic data the minimum number of levels is 3 for /execblockNum/scanNum/subscanNum. Would the data be a set of integrations there are 4 levels. Would the data correspond to subintegrations there would be 5 levels. The model restricting to a single binary BLOB (MIME message) per configDescriptionId, this path is unique in this BLOB. Hence it is a node which can be used as a unique label to refer to a fragment. Reminder: these number are one-based.

Name

AnyProjectPath

Content

Base XSD Type: string

pattern = /\d{1,3}/\d{1,5}/\d{1,5}/\d{1,5}/\d{1,5}

Documentation

Project path: for atomic data the minimum number of levels is 3 for /execblockNum/scanNum/subscanNum. Would the data be a set of integrations there are 4 levels. Would the data correspond to subintegrations there would be 5 levels. The model restricting to a single binary BLOB (MIME message) per configDescriptionId, this path is unique in this BLOB. Hence it is a node which can be used as a unique label to refer to a fragment. Reminder: these number are one-based.

Diagram

Schema Component Representation

<xs:simpleType name="AnyProjectPath">

<xs:restriction base="xs:string">

<-- <xs:pattern value="/.*\d/.*\d/.*\d"></xs:pattern> -->

<xs:pattern value="/\d{1,3}/\d{1,5}/\d{1,5}/\d{1,5}/\d{1,5}"/>

<xs:pattern value="/\d{1,3}/\d{1,5}/\d{1,5}/\d{1,5}"/>

<xs:pattern value="/\d{1,3}/\d{1,5}/\d{1,5}"/>

<xs:pattern value="/\d{1,3}/\d{1,5}"/>

</xs:restriction>

</xs:simpleType>