class can be used to indicate the sub-type of data-center as primary or alternate.local-definitions of an Assessment Plan or Assessment Results.local-definitions of an Assessment Plan or Assessment Results.location defined in the metadata of the SSP, Assessment Plan, or Assessment Results.party in the metadata of the SSP, Assessment Plan, or Assessment Results.user defined in the SSP, or in the local-definitions of an Assessment Plan or Assessment Results.local-definitions of an Assessment Plan or Assessment Results.local-definitions of an Assessment Plan or Assessment Results.location defined in the metadata of the SSP, Assessment Plan, or Assessment Results.party in the metadata of the SSP, Assessment Plan, or Assessment Results.user defined in the SSP, or in the local-definitions of an Assessment Plan or Assessment Results.local-definitions of an Assessment Plan or Assessment Results.local-definitions of an Assessment Plan or Assessment Results.location defined in the metadata of the SSP, Assessment Plan, or Assessment Results.party in the metadata of the SSP, Assessment Plan, or Assessment Results.user defined in the SSP, or in the local-definitions of an Assessment Plan or Assessment Results.class can be used to indicate the sub-type of data-center as primary or alternate.
+ { $validating-filename } contains { @elements} {
+ mx:pluralize(@elements/number(),'element') } and { @attributes } {
+ mx:pluralize(@attributes/number(),'attribute') }.
{ count(.//mx:report) } { mx:pluralize(count(.//mx:report),'issue') } reported.
+
+
Good news - nothing to report - the instance is valid. 🚀 +
+{ @class }{ @level[not(.='ERROR')] ! (' ' || .) }
+{ . }
+ { @test }
+ { @matching }
+ { @xpath }
+
+
+ at, atx, mini-itx or an alternative.x86, x86-64, arm, or an alternative.pata (parallel ATA), sata (Serial ATA), or an alternative.pci (PCI, e.g. Peripheral Component Interconnect), pcie (PCI Express), or an alternative.name.id-ref. This insert mechanism allows the selection of which text value from the object to dynamically include based on the application's display requirements.type. The specific value to include is based on the application's display requirements, which will likely use a specific data element associated with the type (e.g., title, identifier, value, etc.) that is appropriate for the application.
+ { $validating-filename } contains { @elements} {
+ mx:pluralize(@elements/number(),'element') } and { @attributes } {
+ mx:pluralize(@attributes/number(),'attribute') }.
{ count(.//mx:report) } { mx:pluralize(count(.//mx:report),'issue') } reported.
+
+
Good news - nothing to report - the instance is valid. 🚀 +
+{ @class }{ @level[not(.='ERROR')] ! (' ' || .) }
+{ . }
+ { @test }
+ { @matching }
+ { @xpath }
+
+
+ A metaschema can be small and yet deep.
+id-ref. This insert mechanism allows the selection of which text value from the object to dynamically include based on the application's display requirements.type. The specific value to include is based on the application's display requirements, which will likely use a specific data element associated with the type (e.g., title, identifier, value, etc.) that is appropriate for the application.A metaschema can be small and yet deep.
+A metaschema can be small and yet deep.
+For a more extensive model supporting definitions, acronyms etc. build this out into an assembly. + As a field, this supports some control over the vocabulary and formatting without heavier embedded metadata.
+Of course you could always make a structured glossary out of regular and controlled parts for your terminology, and use this inside it, potentially with title/insert.
+A whole number is expected here although '0' is permitted. Values among siblings are not constrained to be ordered, only different. Ordering is up to the receiving application.
+An application may constrain the value of the node to a datatype or other requirement, on the basis of @key, @class or other association(s).
{ @xspec }
- { @xspec/replace(.,'.*/','') }{ @xspec/replace(.,'.*/','') }
- { local-name(..) }/{ local-name(.) }: { . }
-{ local-name(..) }/{ local-name(.) }: { . }
-{ local-name(..) }/{ local-name(.) }: { format-dateTime(xs:dateTime(.),'[MNn] [D1], [Y0001] [H01]:[m01]:[s01]') } ({.})