Petri Net Markup Language (PNML) schema. RELAX NG implementation of PNML Core Model. File name: pnmlcoremodel.rng Version: 2009 (c) 2001-2009 Michael Weber, Ekkart Kindler, Christian Stehno, Lom Hillah (AFNOR) Revision: July 2008 - L.H A PNML document consists of one or more Petri nets. It has a version. A net has a unique identifier (id) and refers to its Petri Net Type Definition (PNTD) (type). The sub-elements of a net may occur in any order. A net consists of at least a top-level page which may contain several objects. A net may have a name, other labels (net.labels) and tool specific information in any order. Identifier (id) declaration shared by all objects in any PNML model. The net type (nettype.uri) of a net should be redefined in the grammar for a new Petri net Type. An example of such a definition is in ptnet.pntd, the grammar for P/T Nets. The following value is a default. http://www.pnml.org/version-2009/grammar/pnmlcoremodel A net may have unspecified many labels. This pattern should be used within a PNTD to define the net labels. Basic contents for any object of a PNML model. A page has an id. It may have a name and tool specific information. It may also have graphical information. It can also have many arbitrary labels. Note: according to this definition, a page may contain other pages. All these sub-elements may occur in any order. A net object is either a page, a node or an arc. A node is a place or a transition, a reference place of a reference transition. A page may have unspecified many labels. This pattern should be used within a PNTD to define new labels for the page concept. A place may have several labels (place.labels) and the same content as a node. A place may have arbitrary many labels. This pattern should be used within a PNTD to define the place labels. A transition may have several labels (transition.labels) and the same content as a node. A transition may have arbitrary many labels. This pattern should be used within a PNTD to define the transition labels. A node may have graphical information. Here, we define the attribute ref including its data type. Modular PNML will extend this definition in order to change the behavior of references to export nodes of module instances. A reference place is a reference node. Validating instruction: - _ref_ MUST refer to _id_ of a reference place or of a place. - _ref_ MUST NOT refer to _id_ of its reference place element. - _ref_ MUST NOT refer to a cycle of reference places. A reference transition is a reference node. Validating instruction: - The reference (ref) MUST refer to a reference transition or to a transition. - The reference (ref) MUST NOT refer to the identifier (id) of its reference transition element. - The reference (ref) MUST NOT refer to a cycle of reference transitions. A reference node has the same content as a node. It adds a reference (ref) to a (reference) node. An arc has a unique identifier (id) and refers both to the node's id of its source and the node's id of its target. In general, if the source attribute refers to a place, then the target attribute refers to a transition and vice versa. The sub-elements of an arc may occur in any order. An arc may have a name, graphical and tool specific information. It may also have several labels. An arc may have arbitrary many labels. This pattern should be used within a PNTD to define the arc labels. A page graphics is actually a node graphics The sub-elements of a node's graphical part occur in any order. At least, there may be one position element. Furthermore, there may be a dimension, a fill, and a line element. The sub-elements of an arc's graphical part occur in any order. There may be zero or more position elements. Furthermore, there may be a line element. This definition describes the contents of simple text labels without graphics. A text should have a value. If not, then there must be a default. The definition annotationstandard.content describes the standard contents of an annotation. Each annotation may have graphical or tool specific information. A simple text label is an annotation to a net object containing arbitrary text. Its sub-elements occur in any order. A simple text label behaves like an attribute to a net object. Furthermore, it contains the standard annotation contents which basically defines the graphics of the text. Label definition for a user given name of an element. An annotation's graphics part requires an offset element describing the offset the center point of the surrounding text box has to the reference point of the net object on which the annotation occurs. Furthermore, an annotation's graphic element may have a fill, a line, and font element. A position element describes Cartesian coordinates. An offset element describes Cartesian coordinates. The coordinates are decimal numbers and refer to an appropriate xy-system where the x-axis runs from left to right and the y-axis from top to bottom. A dimension element describes the width (x coordinate) and height (y coordinate) of a node. The coordinates are actually positive decimals. Definition of a restricted positive decimals domain with a total digits number of 4 and 1 fraction digit. Ranges from 0 to 999.9 4 1 0 A fill element describes the interior colour, the gradient colour, and the gradient rotation between the colors of an object. If an image is available the other attributes are ignored. vertical horizontal diagonal A line element describes the shape, the colour, the width, and the style of an object. line curve solid dash dot This describes the type of a color attribute. Actually, this comes from the CSS2 (and latest versions) data type system. A font element describes several font attributes, the decoration, the alignment, and the rotation angle of an annotation's text. The font attributes (family, style, weight, size) should be conform to the CSS2 and latest versions data type system. underline overline line-through left center right The tool specific information refers to a tool and its version. The further substructure is up to the tool.