Schema metalex.xsd


targetNamespace:  http://www.metalex.nl/latest
 
Elements  Complex types  Attr. groups 
Annotation  AReferringTextType  descriptorAttrs 
Appendix  ArticleType  extTemporalAttrs 
Article  CiteGroupType  identityAttrs 
Category  CiteRangeType  temporalAttrs 
CitationDesignation  IndexDesignationType 
CitationTitle  ListType 
Cite  MixedType 
CiteFrom  PartType 
CiteGroup  ReferringTextType 
CiteRange  RegulationType 
CiteTo  SentenceFragmentSubPartType 
Conclusion  SubPartType 
Index  TextType 
IndexDesignation  TextVersionType 
Introduction 
List 
MetaData 
Part 
Quote 
Reference 
Regulation 
Sentence 
SentenceFragment 
SentenceFragmentSubPart 
SubPart 
TextVersion 
Title 


targetNamespace:  http://www.w3.org/1999/xlink
 


element Annotation
diagram
namespace http://www.metalex.nl/latest
type extension of MixedType
properties
content complex
used by
complexTypes ArticleType PartType RegulationType SubPartType TextType
attributes
Name  Type  Use  Annotation
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
annotation
Any commentary, footnotes, references etc. that are not part of a regulation in the sense that they were not added by the author.
source <xsd:element name="Annotation">
  <xsd:annotation>
    <xsd:documentation>Any commentary, footnotes, references etc. that are not part of a regulation in the sense that they were not added by the author.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="MixedType">
        <xsd:attributeGroup ref="identityAttrs"/>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>

element Appendix
diagram
namespace http://www.metalex.nl/latest
type TextType
properties
content complex
mixed true
children TextVersion Annotation MetaData
used by
complexType RegulationType
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
Some regulations will contain appendices that are referred to in the primary declarative/directive part of the regulation.
source <xsd:element name="Appendix" type="TextType">
  <xsd:annotation>
    <xsd:documentation>Some regulations will contain appendices that are referred to in the primary declarative/directive part of the regulation.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element Article
diagram
namespace http://www.metalex.nl/latest
type ArticleType
properties
content complex
children IndexDesignation Title SubPart List Sentence Annotation MetaData
used by
complexTypes PartType RegulationType
attributes
Name  Type  Use  Annotation
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
A regulation consists of articles (optionally divided in parts).
source <xsd:element name="Article" type="ArticleType">
  <xsd:annotation>
    <xsd:documentation>A regulation consists of articles (optionally divided in parts).</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element Category
diagram
namespace http://www.metalex.nl/latest
type TextType
properties
content complex
mixed true
children TextVersion Annotation MetaData
used by
complexType IndexDesignationType
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
The category of an article, part or subpart. Example: part, chapter, article, sub, etc.
source <xsd:element name="Category" type="TextType">
  <xsd:annotation>
    <xsd:documentation>The category of an article, part or subpart. Example: part, chapter, article, sub, etc.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element CitationDesignation
diagram
namespace http://www.metalex.nl/latest
type TextType
properties
content complex
mixed true
children TextVersion Annotation MetaData
used by
complexType RegulationType
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
The full designation at the top of the document identifying the regulation. This designation if often used to cite the regulation. In other cases a specific title, or specific titles, to be used for designation are found in some other place in the text. See the CitationTitle element for declarations of formal names of the regulation found in other places in the document.
source <xsd:element name="CitationDesignation" type="TextType">
  <xsd:annotation>
    <xsd:documentation>The full designation at the top of the document identifying the regulation. This designation if often used to cite the regulation. In other cases a specific title, or specific titles, to be used for designation are found in some other place in the text. See the CitationTitle element for declarations of formal names of the regulation found in other places in the document.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element CitationTitle
diagram
namespace http://www.metalex.nl/latest
type TextType
properties
content complex
mixed true
children TextVersion Annotation MetaData
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
A phrase designated as a formal name or acronym for citing the regulation. In some cases a specific title, or specific titles, to be used for designation, is (are) declared in the declarative/directive part of the regulation. This element is used in running text. Do not confuse this element with the CitationDesignation element.
source <xsd:element name="CitationTitle" type="TextType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A phrase designated as a formal name or acronym for citing the regulation. In some cases a specific title, or specific titles, to be used for designation, is (are) declared in the declarative/directive part of the regulation. This element is used in running text. Do not confuse this element with the CitationDesignation element.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element Cite
diagram
namespace http://www.metalex.nl/latest
type ReferringTextType
properties
content complex
mixed true
children TextVersion Annotation MetaData
used by
complexType CiteGroupType
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
xlink:type  required  
xlink:href  optional  
resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If a document contains xlink:href attributes pointing to URI that cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved.
Example: xlink:href="urn:nir:stato:decreto.legislativo:1992-07-24;358#art5 " and resolver="http://resolver.nl?" would result in a XHTML version of the MetaLex XML document in a hyperlink href="http://resolver.nl?urn:nir:stato:decreto.legislativo:1992-07-24;358#art5"
href  xsd:anyURIoptional  
If no reasonable URI candidate for the xlink:href attribute exists, use the href attribute to refer to the URL of some representation of the document on the Internet. For instance, if you only have a URL of a PDF version of a regulation, and you want a citation of article 31 of that regulation to point to that PDF document, then use this attribute instead of the xlink:href.
ref-date  xsd:dateoptional  
annotation
Cite denotes a citation of a regulation, article, part or subpart. Examples: "The Rome Statute, Article 1", "Article 12.1 of this regulation". It is used in running text. This element can be used in any other XML standard, and in running text in metalex documents.
Not to be confused with a quote or an allusion.
source <xsd:element name="Cite" type="ReferringTextType">
  <xsd:annotation>
    <xsd:documentation>Cite denotes a citation of a regulation, article, part or subpart. Examples: "The Rome Statute, Article 1", "Article 12.1 of this regulation". It is used in running text. This element can be used in any other XML standard, and in running text in metalex documents.
Not to be confused with a quote or an allusion.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element CiteFrom
diagram
namespace http://www.metalex.nl/latest
type AReferringTextType
properties
content complex
mixed true
children TextVersion Annotation MetaData
used by
complexType CiteRangeType
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
xlink:type  required  
xlink:href  optional  
resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If a document contains xlink:href attributes pointing to URI that cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved.
Example: xlink:href="urn:nir:stato:decreto.legislativo:1992-07-24;358#art5 " and resolver="http://resolver.nl?" would result in a XHTML version of the MetaLex XML document in a hyperlink href="http://resolver.nl?urn:nir:stato:decreto.legislativo:1992-07-24;358#art5"
href  xsd:anyURIoptional  
If no reasonable URI candidate for the xlink:href attribute exists, use the href attribute to refer to the URL of some representation of the document on the Internet. For instance, if you only have a URL of a PDF version of a regulation, and you want a citation of article 31 of that regulation to point to that PDF document, then use this attribute instead of the xlink:href.
annotation
Cite from this article/part/subpart.
source <xsd:element name="CiteFrom" type="AReferringTextType">
  <xsd:annotation>
    <xsd:documentation>Cite from this article/part/subpart.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element CiteGroup
diagram
namespace http://www.metalex.nl/latest
type CiteGroupType
properties
content complex
mixed true
children Cite CiteRange CiteGroup
used by
complexType CiteGroupType
attributes
Name  Type  Use  Annotation
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
Cite multiple regulations, parts, articles.
source <xsd:element name="CiteGroup" type="CiteGroupType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Cite multiple regulations, parts, articles.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element CiteRange
diagram
namespace http://www.metalex.nl/latest
type CiteRangeType
properties
content complex
mixed true
children CiteFrom CiteTo
used by
complexType CiteGroupType
attributes
Name  Type  Use  Annotation
ref-date  xsd:dateoptional  
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
Cite a range of articles/parts /subparts of a regulation.
source <xsd:element name="CiteRange" type="CiteRangeType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Cite a range of articles/parts /subparts of a regulation.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element CiteTo
diagram
namespace http://www.metalex.nl/latest
type AReferringTextType
properties
content complex
mixed true
children TextVersion Annotation MetaData
used by
complexType CiteRangeType
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
xlink:type  required  
xlink:href  optional  
resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If a document contains xlink:href attributes pointing to URI that cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved.
Example: xlink:href="urn:nir:stato:decreto.legislativo:1992-07-24;358#art5 " and resolver="http://resolver.nl?" would result in a XHTML version of the MetaLex XML document in a hyperlink href="http://resolver.nl?urn:nir:stato:decreto.legislativo:1992-07-24;358#art5"
href  xsd:anyURIoptional  
If no reasonable URI candidate for the xlink:href attribute exists, use the href attribute to refer to the URL of some representation of the document on the Internet. For instance, if you only have a URL of a PDF version of a regulation, and you want a citation of article 31 of that regulation to point to that PDF document, then use this attribute instead of the xlink:href.
annotation
Cite to (and including) this article/part/subpart.
source <xsd:element name="CiteTo" type="AReferringTextType">
  <xsd:annotation>
    <xsd:documentation>Cite to (and including) this article/part/subpart.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element Conclusion
diagram
namespace http://www.metalex.nl/latest
type TextType
properties
content complex
mixed true
children TextVersion Annotation MetaData
used by
complexType RegulationType
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
A text at the end of the primary document that contains formal language closing the document. Usually it contains information about who signed the regulation etc.
source <xsd:element name="Conclusion" type="TextType">
  <xsd:annotation>
    <xsd:documentation>A text at the end of the primary document that contains formal language closing the document. Usually it contains information about who signed the regulation etc.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element Index
diagram
namespace http://www.metalex.nl/latest
type TextType
properties
content complex
mixed true
children TextVersion Annotation MetaData
used by
complexType IndexDesignationType
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
Number of article, part or subpart. Can be 1,2,3 or a,b,c etc. The order of this numbering should be fixed.
source <xsd:element name="Index" type="TextType">
  <xsd:annotation>
    <xsd:documentation>Number of article, part or subpart. Can be 1,2,3 or a,b,c etc. The order of this numbering should be fixed.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element IndexDesignation
diagram
namespace http://www.metalex.nl/latest
type IndexDesignationType
properties
content complex
mixed true
children Category Index
used by
complexTypes ArticleType PartType SentenceFragmentSubPartType SubPartType
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
annotation
A fixed identifier (name, rank; normative) for a part. Consists of a designation of the category (optional) and an index. Examples of category: member, chapter etc. Numbering of index can be 1,2,3 or a,b,c. The order of this numbering should be fixed.
source <xsd:element name="IndexDesignation" type="IndexDesignationType">
  <xsd:annotation>
    <xsd:documentation>A fixed identifier (name, rank; normative) for a part. Consists of a designation of the category (optional) and an index. Examples of category: member, chapter etc. Numbering of index can be 1,2,3 or a,b,c. The order of this numbering should be fixed.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element Introduction
diagram
namespace http://www.metalex.nl/latest
type TextType
properties
content complex
mixed true
children TextVersion Annotation MetaData
used by
complexType RegulationType
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
A text between the title of the document and the declarative/directive part of the document that functions as an introduction. It may contain procedural information, and usually a statement of the purpose of the regulation.
source <xsd:element name="Introduction" type="TextType">
  <xsd:annotation>
    <xsd:documentation>A text between the title of the document and the declarative/directive part of the document that functions as an introduction. It may contain procedural information, and usually a statement of the purpose of the regulation.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element List
diagram
namespace http://www.metalex.nl/latest
type ListType
properties
content complex
children SentenceFragment SentenceFragmentSubPart
used by
complexTypes ArticleType ArticleType SentenceFragmentSubPartType SubPartType SubPartType
attributes
Name  Type  Use  Annotation
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
A sentence that consists of a list.
source <xsd:element name="List" type="ListType">
  <xsd:annotation>
    <xsd:documentation>A sentence that consists of a list.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element MetaData
diagram
namespace http://www.metalex.nl/latest
type MixedType
properties
content complex
mixed true
used by
complexTypes ArticleType PartType RegulationType SubPartType TextType
attributes
Name  Type  Use  Annotation
annotation
Any XML content not part of a regulation, and not human-readable text, but about the regulatory text in which it is embedded.
source <xsd:element name="MetaData" type="MixedType">
  <xsd:annotation>
    <xsd:documentation>Any XML content not part of a regulation, and not human-readable text, but about the regulatory text in which it is embedded.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element Part
diagram
namespace http://www.metalex.nl/latest
type PartType
properties
content complex
children IndexDesignation Title Part Article Annotation MetaData
used by
complexTypes PartType RegulationType
attributes
Name  Type  Use  Annotation
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
A part of a document that contains a number of articles. Example: chapters, paragraph etc.
source <xsd:element name="Part" type="PartType">
  <xsd:annotation>
    <xsd:documentation>A part of a document that contains a number of articles. Example: chapters, paragraph etc.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element Quote
diagram
namespace http://www.metalex.nl/latest
type TextType
properties
content complex
mixed true
children TextVersion Annotation MetaData
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
A phrase that repeats a passage from another text. Do not confuse with the cite element. The quote occurs in modifying laws
(where the text of the modified law is often quoted), and in external sources that explain legislation.
source <xsd:element name="Quote" type="TextType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A phrase that repeats a passage from another text. Do not confuse with the cite element. The quote occurs in modifying laws
(where the text of the modified law is often quoted), and in external sources that explain legislation.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element Reference
diagram
namespace http://www.metalex.nl/latest
type ReferringTextType
properties
content complex
mixed true
children TextVersion Annotation MetaData
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
xlink:type  required  
xlink:href  optional  
resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If a document contains xlink:href attributes pointing to URI that cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved.
Example: xlink:href="urn:nir:stato:decreto.legislativo:1992-07-24;358#art5 " and resolver="http://resolver.nl?" would result in a XHTML version of the MetaLex XML document in a hyperlink href="http://resolver.nl?urn:nir:stato:decreto.legislativo:1992-07-24;358#art5"
href  xsd:anyURIoptional  
If no reasonable URI candidate for the xlink:href attribute exists, use the href attribute to refer to the URL of some representation of the document on the Internet. For instance, if you only have a URL of a PDF version of a regulation, and you want a citation of article 31 of that regulation to point to that PDF document, then use this attribute instead of the xlink:href.
ref-date  xsd:dateoptional  
annotation
Reference (allusion) by name to a known person (the Minister, the King), body (the Tax and Customs Administration, the Government, the Crown), region (the territory of the Kingdom of the Netherlands in Europe) or concept defined in a regulation. Allusion is the implicit referencing of a related object or circumstance, which occurs or exists in an external context.
An allusion is understandable only to those with prior knowledge of the target of the reference in question (as the author assumes the reader has).
source <xsd:element name="Reference" type="ReferringTextType">
  <xsd:annotation>
    <xsd:documentation>Reference (allusion) by name to a known person (the Minister, the King), body (the Tax and Customs Administration, the Government, the Crown), region (the territory of the Kingdom of the Netherlands in Europe) or concept defined in a regulation. Allusion is the implicit referencing of a related object or circumstance, which occurs or exists in an external context.
An allusion is understandable only to those with prior knowledge of the target of the reference in question (as the author assumes the reader has).</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element Regulation
diagram
namespace http://www.metalex.nl/latest
type RegulationType
properties
content complex
children CitationDesignation Introduction Article Part Conclusion Appendix Annotation MetaData
attributes
Name  Type  Use  Annotation
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
A written decision from a public body containing general prescriptions in the form of articles.
source <xsd:element name="Regulation" type="RegulationType">
  <xsd:annotation>
    <xsd:documentation xml:lang="nl">A written decision from a public body containing general prescriptions in the form of articles.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element Sentence
diagram
namespace http://www.metalex.nl/latest
type TextType
properties
content complex
mixed true
children TextVersion Annotation MetaData
used by
complexTypes ArticleType ArticleType ArticleType SubPartType SubPartType SubPartType
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
A sentence.
source <xsd:element name="Sentence" type="TextType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A sentence.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element SentenceFragment
diagram
namespace http://www.metalex.nl/latest
type TextType
properties
content complex
mixed true
children TextVersion Annotation MetaData
used by
complexTypes ListType ListType SentenceFragmentSubPartType
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
A part of a sentence.
source <xsd:element name="SentenceFragment" type="TextType">
  <xsd:annotation>
    <xsd:documentation>A part of a sentence.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element SentenceFragmentSubPart
diagram
namespace http://www.metalex.nl/latest
type SentenceFragmentSubPartType
properties
content complex
children IndexDesignation SentenceFragment List
used by
complexType ListType
attributes
Name  Type  Use  Annotation
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
An indexed subpart (part of a list) that contains a part (SentenceFragment) of a sentence.
source <xsd:element name="SentenceFragmentSubPart" type="SentenceFragmentSubPartType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">An indexed subpart (part of a list) that contains a part (SentenceFragment) of a sentence. </xsd:documentation>
  </xsd:annotation>
</xsd:element>

element SubPart
diagram
namespace http://www.metalex.nl/latest
type SubPartType
properties
content complex
children IndexDesignation Title SubPart List Sentence Annotation MetaData
used by
complexTypes ArticleType ArticleType SubPartType SubPartType
attributes
Name  Type  Use  Annotation
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
Part of an article. Member, Sub etc. Use this element when an article is divided into multiple parts.
source <xsd:element name="SubPart" type="SubPartType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Part of an article. Member, Sub etc. Use this element when an article is divided into multiple parts.</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element TextVersion
diagram
namespace http://www.metalex.nl/latest
type TextVersionType
properties
content complex
mixed true
used by
complexType TextType
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
Contains mixed XML from any namespace. Is used to separate different versions of a piece of text. (both for languageversions as for the specification of newer and older versions)
source <xsd:element name="TextVersion" type="TextVersionType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Contains mixed XML from any namespace. Is used to separate different versions of a piece of text. (both for languageversions as for the specification of newer and older versions)</xsd:documentation>
  </xsd:annotation>
</xsd:element>

element Title
diagram
namespace http://www.metalex.nl/latest
type TextType
properties
content complex
mixed true
children TextVersion Annotation MetaData
used by
complexTypes ArticleType PartType SubPartType
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
The title (caption) of a part
source <xsd:element name="Title" type="TextType">
  <xsd:annotation>
    <xsd:documentation>The title (caption) of a part</xsd:documentation>
  </xsd:annotation>
</xsd:element>

complexType AReferringTextType
diagram
namespace http://www.metalex.nl/latest
type extension of TextType
properties
base TextType
mixed true
children TextVersion Annotation MetaData
used by
elements CiteFrom CiteTo
complexType ReferringTextType
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
xlink:type  required  
xlink:href  optional  
resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If a document contains xlink:href attributes pointing to URI that cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved.
Example: xlink:href="urn:nir:stato:decreto.legislativo:1992-07-24;358#art5 " and resolver="http://resolver.nl?" would result in a XHTML version of the MetaLex XML document in a hyperlink href="http://resolver.nl?urn:nir:stato:decreto.legislativo:1992-07-24;358#art5"
href  xsd:anyURIoptional  
If no reasonable URI candidate for the xlink:href attribute exists, use the href attribute to refer to the URL of some representation of the document on the Internet. For instance, if you only have a URL of a PDF version of a regulation, and you want a citation of article 31 of that regulation to point to that PDF document, then use this attribute instead of the xlink:href.
annotation
It is required to use the xlink:type attribute to instruct XML Linking implementations that this element is a link.
If the target of the link is unclear, use xlink:type="simple". If a target URI is known, use xlink:type="locator" and xlink:href to point to the URI. The URI should be a static URI that identifies the target legislation.
source <xsd:complexType name="AReferringTextType" mixed="true">
  <xsd:annotation>
    <xsd:documentation>It is required to use the xlink:type attribute to instruct XML Linking implementations that this element is a link.
If the target of the link is unclear, use xlink:type="simple". If a target URI is known, use xlink:type="locator" and xlink:href to point to the URI. The URI should be a static URI that identifies the target legislation.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexContent mixed="true">
    <xsd:extension base="TextType">
      <xsd:attribute ref="xlink:type" use="required"/>
      <xsd:attribute ref="xlink:href" use="optional"/>
      <xsd:attribute name="resolver" type="xsd:anyURI" use="optional">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If a document contains xlink:href attributes pointing to URI that cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved.
Example: xlink:href="urn:nir:stato:decreto.legislativo:1992-07-24;358#art5 " and resolver="http://resolver.nl?" would result in a XHTML version of the MetaLex XML document in a hyperlink href="http://resolver.nl?urn:nir:stato:decreto.legislativo:1992-07-24;358#art5"</xsd:documentation>
        </xsd:annotation>
      </xsd:attribute>
      <xsd:attribute name="href" type="xsd:anyURI" use="optional">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">If no reasonable URI candidate for the xlink:href attribute exists, use the href attribute to refer to the URL of some representation of the document on the Internet. For instance, if you only have a URL of a PDF version of a regulation, and you want a citation of article 31 of that regulation to point to that PDF document, then use this attribute instead of the xlink:href.</xsd:documentation>
        </xsd:annotation>
      </xsd:attribute>
    </xsd:extension>
  </xsd:complexContent>
</xsd:complexType>

complexType ArticleType
diagram
namespace http://www.metalex.nl/latest
children IndexDesignation Title SubPart List Sentence Annotation MetaData
used by
element Article
attributes
Name  Type  Use  Annotation
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
A regulation consists of articles (optionally organizeded in parts, and subdivided in subparts).
source <xsd:complexType name="ArticleType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A regulation consists of articles (optionally organizeded in parts, and subdivided in subparts).</xsd:documentation>
  </xsd:annotation>
  <xsd:sequence>
    <xsd:element ref="IndexDesignation">
      <xsd:annotation>
        <xsd:documentation>Articles are continuously numbered. Citation title of a regulation and article nummer thus uniquely identify part of a regulation (regardless of any division in parts).</xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element ref="Title" minOccurs="0"/>
    <xsd:choice>
      <xsd:element ref="SubPart" maxOccurs="unbounded"/>
      <xsd:sequence>
        <xsd:element ref="List"/>
        <xsd:element ref="Sentence" minOccurs="0" maxOccurs="unbounded"/>
      </xsd:sequence>
      <xsd:sequence>
        <xsd:element ref="Sentence" maxOccurs="unbounded"/>
        <xsd:choice minOccurs="0">
          <xsd:element ref="SubPart" maxOccurs="unbounded"/>
          <xsd:sequence>
            <xsd:element ref="List"/>
            <xsd:element ref="Sentence" minOccurs="0" maxOccurs="unbounded"/>
          </xsd:sequence>
        </xsd:choice>
      </xsd:sequence>
    </xsd:choice>
    <xsd:element ref="Annotation" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element ref="MetaData" minOccurs="0" maxOccurs="unbounded"/>
  </xsd:sequence>
  <xsd:attributeGroup ref="identityAttrs"/>
  <xsd:attributeGroup ref="temporalAttrs"/>
  <xsd:attributeGroup ref="extTemporalAttrs"/>
  <xsd:attributeGroup ref="descriptorAttrs"/>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>

complexType CiteGroupType
diagram
namespace http://www.metalex.nl/latest
properties
mixed true
children Cite CiteRange CiteGroup
used by
element CiteGroup
attributes
Name  Type  Use  Annotation
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
Cite multiple regulations, parts, articles. In some cases  you will find compound references of the pattern: "regulation X, art. |1|, |2-4|". The problem is that it consists of parts specifying the individual references (1, 2-4) and a description of a context that the individual references share. If you use the Cite element to hyperlink to a target document, then you need to mark up the individual references, but if you want to parse the references to identify the target, you have to parse the complete CiteGroup.
source <xsd:complexType name="CiteGroupType" mixed="true">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Cite multiple regulations, parts, articles. In some cases  you will find compound references of the pattern: "regulation X, art. |1|, |2-4|". The problem is that it consists of parts specifying the individual references (1, 2-4) and a description of a context that the individual references share. If you use the Cite element to hyperlink to a target document, then you need to mark up the individual references, but if you want to parse the references to identify the target, you have to parse the complete CiteGroup.</xsd:documentation>
  </xsd:annotation>
  <xsd:sequence>
    <xsd:choice maxOccurs="unbounded">
      <xsd:element ref="Cite"/>
      <xsd:element ref="CiteRange"/>
      <xsd:element ref="CiteGroup"/>
    </xsd:choice>
  </xsd:sequence>
  <xsd:attributeGroup ref="identityAttrs"/>
  <xsd:attributeGroup ref="temporalAttrs"/>
  <xsd:attributeGroup ref="extTemporalAttrs"/>
  <xsd:attributeGroup ref="descriptorAttrs"/>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>

complexType CiteRangeType
diagram
namespace http://www.metalex.nl/latest
properties
mixed true
children CiteFrom CiteTo
used by
element CiteRange
attributes
Name  Type  Use  Annotation
ref-date  xsd:dateoptional  
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
Cite a range of articles/parts /subparts of a regulation.
source <xsd:complexType name="CiteRangeType" mixed="true">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Cite a range of articles/parts /subparts of a regulation.</xsd:documentation>
  </xsd:annotation>
  <xsd:sequence>
    <xsd:element ref="CiteFrom"/>
    <xsd:element ref="CiteTo"/>
  </xsd:sequence>
  <xsd:attribute name="ref-date" type="xsd:date" use="optional"/>
  <xsd:attributeGroup ref="identityAttrs"/>
  <xsd:attributeGroup ref="temporalAttrs"/>
  <xsd:attributeGroup ref="extTemporalAttrs"/>
  <xsd:attributeGroup ref="descriptorAttrs"/>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>

complexType IndexDesignationType
diagram
namespace http://www.metalex.nl/latest
type restriction of xsd:anyType
properties
base xsd:anyType
mixed true
children Category Index
used by
element IndexDesignation
attributes
Name  Type  Use  Annotation
annotation
A fixed identifier (name, rank; normative) for a part. Consists of a designation of the category (optional) and an index. Examples of category: member, chapter etc. Numbering of index can be 1,2,3 or a,b,c. The order of this numbering should be fixed. The Index designation is added by the author to identify a textual element. It is therefore part of the original text. CitationDesignation of a regulation (global identity) and IndexDesignation (local identity; e.g. article number) usually uniquely identify a part of a regulation. There is however a difference between indexicals into an array of textual elements and the index designation added by the author. The second article of a regulation may be called "article 3" (indicating a gap) or "article 1bis" (indicating later insertion).
source <xsd:complexType name="IndexDesignationType" mixed="true">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A fixed identifier (name, rank; normative) for a part. Consists of a designation of the category (optional) and an index. Examples of category: member, chapter etc. Numbering of index can be 1,2,3 or a,b,c. The order of this numbering should be fixed. The Index designation is added by the author to identify a textual element. It is therefore part of the original text. CitationDesignation of a regulation (global identity) and IndexDesignation (local identity; e.g. article number) usually uniquely identify a part of a regulation. There is however a difference between indexicals into an array of textual elements and the index designation added by the author. The second article of a regulation may be called "article 3" (indicating a gap) or "article 1bis" (indicating later insertion).</xsd:documentation>
  </xsd:annotation>
  <xsd:complexContent mixed="true">
    <xsd:restriction base="xsd:anyType">
      <xsd:sequence>
        <xsd:element ref="Category" minOccurs="0"/>
        <xsd:element ref="Index"/>
      </xsd:sequence>
      <xsd:attribute ref="xml:lang"/>
      <xsd:attributeGroup ref="identityAttrs"/>
      <xsd:attributeGroup ref="temporalAttrs"/>
      <xsd:anyAttribute namespace="##other" processContents="lax"/>
    </xsd:restriction>
  </xsd:complexContent>
</xsd:complexType>

complexType ListType
diagram
namespace http://www.metalex.nl/latest
children SentenceFragment SentenceFragmentSubPart
used by
element List
attributes
Name  Type  Use  Annotation
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
A vertical, numbered list in a sentence whose sentence fragments are treated as subparts for purposes of reference.
source <xsd:complexType name="ListType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A vertical, numbered list in a sentence whose sentence fragments are treated as subparts for purposes of reference.</xsd:documentation>
  </xsd:annotation>
  <xsd:sequence>
    <xsd:element ref="SentenceFragment"/>
    <xsd:element ref="SentenceFragmentSubPart" maxOccurs="unbounded"/>
    <xsd:element ref="SentenceFragment" minOccurs="0"/>
  </xsd:sequence>
  <xsd:attributeGroup ref="identityAttrs"/>
  <xsd:attributeGroup ref="temporalAttrs"/>
  <xsd:attributeGroup ref="extTemporalAttrs"/>
  <xsd:attributeGroup ref="descriptorAttrs"/>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>

complexType MixedType
diagram
namespace http://www.metalex.nl/latest
type restriction of xsd:anyType
properties
base xsd:anyType
mixed true
used by
elements Annotation MetaData
attributes
Name  Type  Use  Annotation
annotation
Contains mixed XML from any namespace.
source <xsd:complexType name="MixedType" mixed="true">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Contains mixed XML from any namespace.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexContent mixed="true">
    <xsd:restriction base="xsd:anyType">
      <xsd:sequence>
        <xsd:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
      </xsd:sequence>
      <xsd:anyAttribute namespace="##other" processContents="lax"/>
    </xsd:restriction>
  </xsd:complexContent>
</xsd:complexType>

complexType PartType
diagram
namespace http://www.metalex.nl/latest
children IndexDesignation Title Part Article Annotation MetaData
used by
element Part
attributes
Name  Type  Use  Annotation
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
A part of a document that contains a number of articles. Example: chapters, paragraph etc.
source <xsd:complexType name="PartType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A part of a document that contains a number of articles. Example: chapters, paragraph etc.</xsd:documentation>
  </xsd:annotation>
  <xsd:sequence>
    <xsd:element ref="IndexDesignation"/>
    <xsd:element ref="Title" minOccurs="0"/>
    <xsd:choice>
      <xsd:element ref="Part" maxOccurs="unbounded"/>
      <xsd:element ref="Article" maxOccurs="unbounded"/>
    </xsd:choice>
    <xsd:element ref="Annotation" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element ref="MetaData" minOccurs="0" maxOccurs="unbounded"/>
  </xsd:sequence>
  <xsd:attributeGroup ref="identityAttrs"/>
  <xsd:attributeGroup ref="temporalAttrs"/>
  <xsd:attributeGroup ref="extTemporalAttrs"/>
  <xsd:attributeGroup ref="descriptorAttrs"/>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>

complexType ReferringTextType
diagram
namespace http://www.metalex.nl/latest
type extension of AReferringTextType
properties
base AReferringTextType
mixed true
children TextVersion Annotation MetaData
used by
elements Cite Reference
attributes
Name  Type  Use  Annotation
xml:lang    
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
xlink:type  required  
xlink:href  optional  
resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If a document contains xlink:href attributes pointing to URI that cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved.
Example: xlink:href="urn:nir:stato:decreto.legislativo:1992-07-24;358#art5 " and resolver="http://resolver.nl?" would result in a XHTML version of the MetaLex XML document in a hyperlink href="http://resolver.nl?urn:nir:stato:decreto.legislativo:1992-07-24;358#art5"
href  xsd:anyURIoptional  
If no reasonable URI candidate for the xlink:href attribute exists, use the href attribute to refer to the URL of some representation of the document on the Internet. For instance, if you only have a URL of a PDF version of a regulation, and you want a citation of article 31 of that regulation to point to that PDF document, then use this attribute instead of the xlink:href.
ref-date  xsd:dateoptional  
source <xsd:complexType name="ReferringTextType" mixed="true">
  <xsd:complexContent mixed="true">
    <xsd:extension base="AReferringTextType">
      <xsd:attribute name="ref-date" type="xsd:date" use="optional"/>
    </xsd:extension>
  </xsd:complexContent>
</xsd:complexType>

complexType RegulationType
diagram
namespace http://www.metalex.nl/latest
children CitationDesignation Introduction Article Part Conclusion Appendix Annotation MetaData
used by
element Regulation
attributes
Name  Type  Use  Annotation
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
The main element tag of a regulatiory document.
source <xsd:complexType name="RegulationType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The main element tag of a regulatiory document.</xsd:documentation>
  </xsd:annotation>
  <xsd:sequence>
    <xsd:element ref="CitationDesignation" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>Normative AR, but not always available.</xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element ref="Introduction" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>Normative AR and grondwet, but not always available (e.g. BW).</xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:choice>
      <xsd:element ref="Article" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>(AR) A single article is designated 'enig artikel'.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element ref="Part" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">Chapter, paragraph, Title, Part, etc. (normative AR)</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:choice>
    <xsd:element ref="Conclusion" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">Normative in constitution for law and royal decree (KB).</xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element ref="Appendix" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element ref="Annotation" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element ref="MetaData" minOccurs="0" maxOccurs="unbounded"/>
  </xsd:sequence>
  <xsd:attributeGroup ref="identityAttrs"/>
  <xsd:attributeGroup ref="temporalAttrs"/>
  <xsd:attributeGroup ref="extTemporalAttrs"/>
  <xsd:attributeGroup ref="descriptorAttrs"/>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>

complexType SentenceFragmentSubPartType
diagram
namespace http://www.metalex.nl/latest
children IndexDesignation SentenceFragment List
used by
element SentenceFragmentSubPart
attributes
Name  Type  Use  Annotation
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
An indexed subpart (part of a list) that contains a part (SentenceFragment) of a sentence.
source <xsd:complexType name="SentenceFragmentSubPartType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">An indexed subpart (part of a list) that contains a part (SentenceFragment) of a sentence. </xsd:documentation>
  </xsd:annotation>
  <xsd:sequence>
    <xsd:element ref="IndexDesignation"/>
    <xsd:choice>
      <xsd:element ref="SentenceFragment"/>
      <xsd:element ref="List"/>
    </xsd:choice>
  </xsd:sequence>
  <xsd:attributeGroup ref="identityAttrs"/>
  <xsd:attributeGroup ref="temporalAttrs"/>
  <xsd:attributeGroup ref="extTemporalAttrs"/>
  <xsd:attributeGroup ref="descriptorAttrs"/>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>

complexType SubPartType
diagram
namespace http://www.metalex.nl/latest
children IndexDesignation Title SubPart List Sentence Annotation MetaData
used by
element SubPart
attributes
Name  Type  Use  Annotation
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
Part of an article. Member, Sub etc. Use this element when an article is divided into multiple parts.
source <xsd:complexType name="SubPartType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Part of an article. Member, Sub etc. Use this element when an article is divided into multiple parts.</xsd:documentation>
  </xsd:annotation>
  <xsd:sequence>
    <xsd:element ref="IndexDesignation">
      <xsd:annotation>
        <xsd:documentation>The Index designation added by the author to identify a textual element. Parts,articles and subparts are continuously numbered, optionally with some hierarchical levels. Citation title of a regulation (global identity) and index designation (local identity; e.g. article number) usually uniquely identify a part of a regulation. There is however a difference between indexicals into an array of textual elements and the index designation added by the author. The second article of a regulation may be called "article 3" (indicating a gap) or "article 1bis" (indicating later insertion).</xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element ref="Title" minOccurs="0"/>
    <xsd:choice>
      <xsd:element ref="SubPart" maxOccurs="unbounded"/>
      <xsd:sequence>
        <xsd:element ref="List"/>
        <xsd:element ref="Sentence" minOccurs="0" maxOccurs="unbounded"/>
      </xsd:sequence>
      <xsd:sequence>
        <xsd:element ref="Sentence" maxOccurs="unbounded"/>
        <xsd:choice minOccurs="0">
          <xsd:element ref="SubPart" maxOccurs="unbounded"/>
          <xsd:sequence>
            <xsd:element ref="List"/>
            <xsd:element ref="Sentence" minOccurs="0" maxOccurs="unbounded"/>
          </xsd:sequence>
        </xsd:choice>
      </xsd:sequence>
    </xsd:choice>
    <xsd:element ref="Annotation" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element ref="MetaData" minOccurs="0" maxOccurs="unbounded"/>
  </xsd:sequence>
  <xsd:attributeGroup ref="identityAttrs"/>
  <xsd:attributeGroup ref="temporalAttrs"/>
  <xsd:attributeGroup ref="extTemporalAttrs"/>
  <xsd:attributeGroup ref="descriptorAttrs"/>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>

complexType TextType
diagram
namespace http://www.metalex.nl/latest
type restriction of xsd:anyType
properties
base xsd:anyType
mixed true
children TextVersion Annotation MetaData
used by
elements Appendix Category CitationDesignation CitationTitle Conclusion Index Introduction Quote Sentence SentenceFragment Title
complexType AReferringTextType
attributes
Name  Type  Use  Annotation
annotation
Contains either TextVersion elements and annotations or mixed XML from any namespace, with identity and version management attributes.
source <xsd:complexType name="TextType" mixed="true">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Contains either TextVersion elements and annotations or mixed XML from any namespace, with identity and version management attributes.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexContent mixed="true">
    <xsd:restriction base="xsd:anyType">
      <xsd:choice>
        <xsd:sequence>
          <xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
        </xsd:sequence>
        <xsd:sequence>
          <xsd:element ref="TextVersion" maxOccurs="unbounded"/>
          <xsd:element ref="Annotation" minOccurs="0" maxOccurs="unbounded"/>
          <xsd:element ref="MetaData" minOccurs="0" maxOccurs="unbounded"/>
        </xsd:sequence>
      </xsd:choice>
      <xsd:attribute ref="xml:lang"/>
      <xsd:attributeGroup ref="identityAttrs"/>
      <xsd:attributeGroup ref="temporalAttrs"/>
      <xsd:attributeGroup ref="extTemporalAttrs"/>
      <xsd:attributeGroup ref="descriptorAttrs"/>
      <xsd:anyAttribute namespace="##other" processContents="lax"/>
    </xsd:restriction>
  </xsd:complexContent>
</xsd:complexType>

complexType TextVersionType
diagram
namespace http://www.metalex.nl/latest
type restriction of xsd:anyType
properties
base xsd:anyType
mixed true
used by
element TextVersion
attributes
Name  Type  Use  Annotation
annotation
Contains mixed XML from any namespace, but does have identity and version management attributes. The region attributes obviously don't refer to the region associated with a language version.
source <xsd:complexType name="TextVersionType" mixed="true">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Contains mixed XML from any namespace, but does have identity and version management attributes. The region attributes obviously don't refer to the region associated with a language version.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexContent mixed="true">
    <xsd:restriction base="xsd:anyType">
      <xsd:sequence>
        <xsd:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
      </xsd:sequence>
      <xsd:attribute ref="xml:lang"/>
      <xsd:attributeGroup ref="identityAttrs"/>
      <xsd:attributeGroup ref="temporalAttrs"/>
      <xsd:attributeGroup ref="extTemporalAttrs"/>
      <xsd:attributeGroup ref="descriptorAttrs"/>
      <xsd:anyAttribute namespace="##other" processContents="lax"/>
    </xsd:restriction>
  </xsd:complexContent>
</xsd:complexType>

attributeGroup descriptorAttrs
namespace http://www.metalex.nl/latest
used by
complexTypes ArticleType CiteGroupType CiteRangeType ListType PartType RegulationType SentenceFragmentSubPartType SubPartType TextType TextVersionType
attributes
Name  Type  Use  Annotation
author  xsd:anyURIoptional  
The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.
region  xsd:anyURIoptional  
This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).
region-resolver  xsd:anyURIoptional  
A resolver for CRS coordinate URI used in the region attribute.
editor  xsd:anyURIoptional  
The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.
editor-resolver  xsd:anyURIoptional  
The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.
authority  xsd:anyURIoptional  
The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.
procedure  xsd:anyURIoptional  
The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.
annotation
These attributes form a coherent whole. These attributes apply to all kinds of regulatory texts, and to most elements of regulatory text up to the sentence level, or even lower. Usually they are only attached to the Regulation element. All attributes take a URI value that refers to an entity that can be described in a metadata standard like RDF, Topic Maps, or GML (Geography Markup Language).
The attribute value applies to the element to which it is attached and to all its subelements, unless these carry the same attribute.
source <xsd:attributeGroup name="descriptorAttrs">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">These attributes form a coherent whole. These attributes apply to all kinds of regulatory texts, and to most elements of regulatory text up to the sentence level, or even lower. Usually they are only attached to the Regulation element. All attributes take a URI value that refers to an entity that can be described in a metadata standard like RDF, Topic Maps, or GML (Geography Markup Language).
The attribute value applies to the element to which it is attached and to all its subelements, unless these carry the same attribute.
</xsd:documentation>
  </xsd:annotation>
  <xsd:attribute name="author" type="xsd:anyURI" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">The legislator that is responsible for creating the legislation, for instance 'the government', 'government and parliament', 'the Crown', 'the Minister of X', etc. This body or person is usually created by law, so there are usually references from (constitutional) law to this entity that describes the extent of its legislative competence.  The legislator is identified by a URI, and this URI functions as identifier for a description in RDF.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="region" type="xsd:anyURI" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">This is the spatial entity in which the rules in the regulation can be applied. It can be used in combination with RDF and GML to describe spatial extent of the regulation's applicability. In GML and similar geospatial standards a URI is used to refer to coordinates in a coordinate reference system (CRS).</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="region-resolver" type="xsd:anyURI" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">A resolver for CRS coordinate URI used in the region attribute.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="editor" type="xsd:anyURI" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">The editor that is responsible for creating and managing this metalex encoding of the legislation. The editor is identified by a URI, and this URI functions as identifier for a description in RDF.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="editor-resolver" type="xsd:anyURI" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">The URI of the element identifies the element, but it is not a requirement that the URI can be resolved through generic HTTP. If it cannot be resolved through http, then it is an option to set the resolver attribute is a URI resolution service exists. The URI value of the resolver attribute + the URI value in xlink:href should result in a URI that can resolved. Since URI can be assigned to legislation by editors of metalex data, URI resolvers for metalex elements should be logically linked to the editor.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="authority" type="xsd:anyURI" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">The legislator may be able to use different forms of legislative authority or legislative competence created and delegated by law. In some jurisdictions legislative competence is called legislative power. Formal law may for instance state that a Minister is able to make certain changes in formal law for specific purposes, where otherwise the Minister would not have this competence. In addition to the competence of drafting ministerial regulations the minister has a restricted competence to directly amend formal law for some purpose. A competence is usually created by other law, and there are textual references in that law to the competence.  The competence is identified by a URI, and this URI functions as identifier for a description in RDF. A decision maker uses
an authority or power created by law to make adiministrative decisions.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="procedure" type="xsd:anyURI" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">The type of procedure that resulted in the legislation. In some cases the formal legislator can produce different types of legislation depending on the type of procedure followed (for instance decrees vs. formal legislation). This may have consequences for determining Lex Superior relations between collections of regulations. The procedure is identified by a URI, and this URI functions as identifier for a description in RDF.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
</xsd:attributeGroup>

attributeGroup extTemporalAttrs
namespace http://www.metalex.nl/latest
used by
complexTypes ArticleType CiteGroupType CiteRangeType ListType PartType RegulationType SentenceFragmentSubPartType SubPartType TextType TextVersionType
attributes
Name  Type  Use  Annotation
date-start-efficacy  xsd:dateoptional  
date-end-efficacy  xsd:dateoptional  
date-start-effect  xsd:dateoptional  
date-end-effect  xsd:dateoptional  
duration-to-enactment  xsd:dateoptional  
The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
duration-active  xsd:dateoptional  
See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.
duration-efficacy  xsd:dateoptional  
The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.
annotation
These attributes are strictly optional. They are not needed for version management. They have been added to present a coherent theory on phenomena like retroactive application and delayed application etc.
The temporal attributes are based on a theory that a provision in a regulatory text can be read as a rule RULE(t1,t2): IF CONDITIONS(t3,t4) THEN EFFECTS(t5,t6). Between date enactment t1 and date-repeal t2 the rule is active, and therefore can be applied. The events to which is it applied must have happened between date-start-efficacy t3 and date-end-efficacy t4, the time interval in which the rule is capable of producing an effect. The effect itself exists somewhere in the time interval between t5 and t6.
Example: In 2001 there is a tax provision which states that the premium payments to be made in 2001-2005 for certain capital insurance policies closed in and meeting certain conditions in the period 1993-1998 are tax deductible.
The attribute value applies to the element to which it is attached and to all its subelements, unless these carry the same attribute. The duration attributes represent a time interval between two date attributes and should be consistent with the values of the date attributes.
source <xsd:attributeGroup name="extTemporalAttrs">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">These attributes are strictly optional. They are not needed for version management. They have been added to present a coherent theory on phenomena like retroactive application and delayed application etc.
The temporal attributes are based on a theory that a provision in a regulatory text can be read as a rule RULE(t1,t2): IF CONDITIONS(t3,t4) THEN EFFECTS(t5,t6). Between date enactment t1 and date-repeal t2 the rule is active, and therefore can be applied. The events to which is it applied must have happened between date-start-efficacy t3 and date-end-efficacy t4, the time interval in which the rule is capable of producing an effect. The effect itself exists somewhere in the time interval between t5 and t6.
Example: In 2001 there is a tax provision which states that the premium payments to be made in 2001-2005 for certain capital insurance policies closed in and meeting certain conditions in the period 1993-1998 are tax deductible.
The attribute value applies to the element to which it is attached and to all its subelements, unless these carry the same attribute. The duration attributes represent a time interval between two date attributes and should be consistent with the values of the date attributes.
</xsd:documentation>
  </xsd:annotation>
  <xsd:attribute name="date-start-efficacy" type="xsd:date" use="optional">
    <xsd:annotation>
      <xsd:documentation/>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="date-end-efficacy" type="xsd:date" use="optional">
    <xsd:annotation>
      <xsd:documentation/>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="date-start-effect" type="xsd:date" use="optional">
    <xsd:annotation>
      <xsd:documentation/>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="date-end-effect" type="xsd:date" use="optional">
    <xsd:annotation>
      <xsd:documentation/>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="duration-to-enactment" type="xsd:date" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">The length of the time interval between date-publication and date-enacted. Use this time interval to indicate a constraint on the duration to enactment when the precise dates are not known. The regulatory text may for instance state that it will be enacted 3 months after publication.
</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="duration-active" type="xsd:date" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">See date-enacted and date-repealed. The active time interval is the interval between date-enacted and date-repealed. In this time interval the regulatory text could be applied to a case, yielding a conclusion.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="duration-efficacy" type="xsd:date" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">The time interval between date-start-efficacy and date-end-efficacy. The facts to which a rule can be applied have happened in this time interval. Set this time interval to model retroactive applicability of regulatory text. Note that retroactive applicability does not usually refer to the possibility of making decisions using a regulation that does not exist yet, but instead to the possibility of applying the regulation to events that happened before the enactment of the regulatory text.
If multiple interpretations are possible, or if the length of the time interval depends on the exact case, choose the largest time interval possible.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
</xsd:attributeGroup>

attributeGroup identityAttrs
namespace http://www.metalex.nl/latest
used by
element Annotation
complexTypes ArticleType CiteGroupType CiteRangeType IndexDesignationType ListType PartType RegulationType SentenceFragmentSubPartType SubPartType TextType TextVersionType
attributes
Name  Type  Use  Annotation
id  xsd:IDoptional  
If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
uri  xsd:anyURIoptional  
The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.
annotation
These attributes form a coherent whole. These attributes apply to all kinds of regulatory texts, and to most elements of regulatory text up to the sentence level, or even lower. Every MetaLex element with identity is treated like a self-contained regulatory unit identified by a URI. There are two ways of stating the URI of an element: using the URI attribute to state the complete URI, or using the ID attribute and setting the xml:base attribute to state that the URI is base() + ID (for instance http://purl-org/foo#bar where xml:base="http://purl-org/foo" and id="bar").
source <xsd:attributeGroup name="identityAttrs">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">These attributes form a coherent whole. These attributes apply to all kinds of regulatory texts, and to most elements of regulatory text up to the sentence level, or even lower. Every MetaLex element with identity is treated like a self-contained regulatory unit identified by a URI. There are two ways of stating the URI of an element: using the URI attribute to state the complete URI, or using the ID attribute and setting the xml:base attribute to state that the URI is base() + ID (for instance http://purl-org/foo#bar where xml:base="http://purl-org/foo" and id="bar").
</xsd:documentation>
  </xsd:annotation>
  <xsd:attribute name="id" type="xsd:ID" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">If the id attribute is used on an element, then it must be possible to establish the xml base of
the XML element for RDF and XML Linking support to work.
Note that XML documents on the World Wide Web do have a base() that can generally be automatically established, but this base() is lost if the document is downloaded and saved to a local disk. It is good practice to set the at least the xml:base attribute of the Regulation element in a Metalex XML document on the World Wide Web, so that the context is not lost if the document is saved in a local file. Note that it is possible to set the xml:base in multiple places, for instance because the XML file contains legislation taken from multiple locations on the World Wide Web. See the XML Base and XML Linking specifications on http://www.w3.org for more information on the semantics of xml:base.
Instead of the metalex:id attribute, the xml:id attribute may be used. NEVER specify both a metalex:id and xml:id attribute on a single element. It is an XML requirement that only one id attribute be specified on a single element: an application allowing two id attributes on an element is not XML conformant.
</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="uri" type="xsd:anyURI" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">The URI of the element identifies the element. Note that it may be a URN (universal resource name). If the name cannot be resolved through generic HTTP, then set the resolver attribute.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
</xsd:attributeGroup>

attributeGroup temporalAttrs
namespace http://www.metalex.nl/latest
used by
complexTypes ArticleType CiteGroupType CiteRangeType IndexDesignationType ListType PartType RegulationType SentenceFragmentSubPartType SubPartType TextType TextVersionType
attributes
Name  Type  Use  Annotation
date-version  xsd:dateoptional  
date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.
date-enacted  xsd:dateoptional  
The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.
date-repealed  xsd:dateoptional  
The date at which the activity time interval is closed (see date-enacted, duration-active).
date-publication  xsd:dateoptional  
date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
annotation
These attributes form a coherent whole. These attributes apply to all kinds of regulatory texts. Strict application of the metalex standard requires a (possibly inferred) setting for these attributes on each text element. Because the rules for determining the applicable values are complex, they cannot be checked with XML schema.
The attribute value applies to the element to which it is attached and to all its subelements, unless these carry the same attribute.
source <xsd:attributeGroup name="temporalAttrs">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">These attributes form a coherent whole. These attributes apply to all kinds of regulatory texts. Strict application of the metalex standard requires a (possibly inferred) setting for these attributes on each text element. Because the rules for determining the applicable values are complex, they cannot be checked with XML schema.
The attribute value applies to the element to which it is attached and to all its subelements, unless these carry the same attribute.
</xsd:documentation>
  </xsd:annotation>
  <xsd:attribute name="date-version" type="xsd:date" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">date-version is the date of serialization of the XML element on which it occurs. This is important to determine whether the element represents a future modification to the regulation at the time of serialization. If it is, it may not be the text that eventually became active at that future date.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="date-enacted" type="xsd:date" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">The date at which the regulatory text represented by the element was enacted. The time interval between enactment and repeal (see date-repealed, duration-active) is when the text was active in the sense that it could be used in that interval to take decisions. If there are multiple versions of a regulatory text, then the activity intervals of the versions should form a continuous time interval in which the text element(s) existed in the legal system. If a regulatory text is repealed and then re-enacted, it should be treated as a new regulatory text even if it is the exact same text.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="date-repealed" type="xsd:date" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">The date at which the activity time interval is closed (see date-enacted, duration-active).</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="date-publication" type="xsd:date" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">date-publication is the date at which the regulation was formally made public. In the period before that the text does not exist in public awareness. Depending on jurisdiction this may be a date of signing (dies signum) by monarch or president, the date it passed in parliament, or the date it was published in a designated official publication channel. In most jurisdictions there are a number of relevant in the lifecycle of a regulatory text before it becomes 'real'. Choose a relevant date at which it 1) has become public, 2) a static identity is officially assigned, 3) any auxiliary provisions(s) in the text on the date of enactment become active, and the text cannot be changed anymore, except by legislative procedure.
</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
</xsd:attributeGroup>


XML Schema documentation generated by XMLSpy Schema Editor http://www.altova.com/xmlspy