Provide a general summary of the issue in the Title above.Delete the part of the issue template that does not apply depending on whether you describe a change to an existing element / attribute or the addition of a new one.
Creator of issue
State your name, organisation and ways to reach you.
Name: Kerstin Arnold
Organisation: Archives Portal Europe Foundation, Working Group on Standards
Email: standards@archivesportaleurope.net
GitHub username (if applicable): @kerstarno
New element / attribute
Give the name of the new element / attribute. Include the tag name and the full name.
Name: <functions>, <function>, <legalStatuses>, <legalStatus>
Context and availability
List all parent elements to which the element / attribute should be added.For elements, give an indication of their availability within each parent element ("1..1" for required but not repeatable, "1 (or another number)..n" for required and repeatable, "0..1" for optional but not repeatable", "0..n" for optional and repeatable). For attributes, indicate their availability with "1" for required or "0" for optional within each parent element.
Parent element(s):
Add <functions> (0..1) and <legalStatuses> (0..n) to <description> (see #85 for predefined sequence of <description>'s sub-elements)
Add <function> (1..n) to <functions> and <legalStatus> (1..n) to <legalStatuses>
Content model (elements)
List all sub-elements and attributes of the new element.For sub-elements, give an indication of their availability ("1..1" for required but not repeatable, "1 (or another number)..n" for required and repeatable, "0..1" for optional but not repeatable", "0..n" for optional and repeatable). For attributes, indicate their availability with "1" for required or "0" for optional.
<functions> requires at least one <function> (1..n) and allows for <descriptiveNote> (0..1). It also allows for the attributes @audience with the values "external" and "internal" (0), @id (0), @languageOfElement (0), @scriptOfElement (0), @target(0), @conventionDeclarationReference (0), @maintenanceEventReference (0), @sourceReference (0), @localType (0), @localTypeDeclarationReference (0), and an option to include attributes from any other namespace.
<legalStatuses> requires at least one <legalStatus> (1..n) and allows for <descriptiveNote> (0..1). It also allows for the attributes @audience with the values "external" and "internal" (0), @id (0), @languageOfElement (0), @scriptOfElement (0), @target(0), @conventionDeclarationReference (0), @maintenanceEventReference (0), @sourceReference (0), @localType (0), @localTypeDeclarationReference (0), and an option to include attributes from any other namespace.
<function> and <legalStatus> both require at least one <term> (1..n) and allows one of <date> or <dateRange> or <dateSet>, <placeName> (0..n), and <descriptiveNote> (0..1). It also allows for the attributes @audience with the values "external" and "internal" (0), @id (0), @languageOfElement (0), @scriptOfElement (0), @target(0), @conventionDeclarationReference (0), @maintenanceEventReference (0), @sourceReference (0), @localType (0), @localTypeDeclarationReference (0), @valueURI (0), @vocabularySource (0), @vocabularySourceURI, and an option to include attributes from any other namespace.
Example of XML code
Provide a sample encoding in XML of the new / changed element (with potential attributes).Write your text after the "Example:" below.
As these are adopted from EAC-CPF see the EAC-CPF tag library for encoding examples:
Provide a general summary of the issue in the Title above. Delete the part of the issue template that does not apply depending on whether you describe a change to an existing element / attribute or the addition of a new one.
Creator of issue
State your name, organisation and ways to reach you. Name: Kerstin Arnold Organisation: Archives Portal Europe Foundation, Working Group on Standards Email: standards@archivesportaleurope.net GitHub username (if applicable): @kerstarno
New element / attribute
Give the name of the new element / attribute. Include the tag name and the full name. Name:
<functions>,<function>,<legalStatuses>,<legalStatus>Context and availability
List all parent elements to which the element / attribute should be added. For elements, give an indication of their availability within each parent element ("1..1" for required but not repeatable, "1 (or another number)..n" for required and repeatable, "0..1" for optional but not repeatable", "0..n" for optional and repeatable). For attributes, indicate their availability with "1" for required or "0" for optional within each parent element. Parent element(s):
<functions>(0..1) and<legalStatuses>(0..n) to<description>(see #85 for predefined sequence of<description>'s sub-elements)<function>(1..n) to<functions>and<legalStatus>(1..n) to<legalStatuses>Content model (elements)
List all sub-elements and attributes of the new element. For sub-elements, give an indication of their availability ("1..1" for required but not repeatable, "1 (or another number)..n" for required and repeatable, "0..1" for optional but not repeatable", "0..n" for optional and repeatable). For attributes, indicate their availability with "1" for required or "0" for optional.
<functions>requires at least one<function>(1..n) and allows for<descriptiveNote>(0..1). It also allows for the attributes@audiencewith the values "external" and "internal" (0),@id(0),@languageOfElement(0),@scriptOfElement(0),@target(0),@conventionDeclarationReference(0),@maintenanceEventReference(0),@sourceReference(0),@localType(0),@localTypeDeclarationReference(0), and an option to include attributes from any other namespace.<legalStatuses>requires at least one<legalStatus>(1..n) and allows for<descriptiveNote>(0..1). It also allows for the attributes@audiencewith the values "external" and "internal" (0),@id(0),@languageOfElement(0),@scriptOfElement(0),@target(0),@conventionDeclarationReference(0),@maintenanceEventReference(0),@sourceReference(0),@localType(0),@localTypeDeclarationReference(0), and an option to include attributes from any other namespace.<function>and<legalStatus>both require at least one<term>(1..n) and allows one of<date>or<dateRange>or<dateSet>,<placeName>(0..n), and<descriptiveNote>(0..1). It also allows for the attributes@audiencewith the values "external" and "internal" (0),@id(0),@languageOfElement(0),@scriptOfElement(0),@target(0),@conventionDeclarationReference(0),@maintenanceEventReference(0),@sourceReference(0),@localType(0),@localTypeDeclarationReference(0),@valueURI(0),@vocabularySource(0),@vocabularySourceURI, and an option to include attributes from any other namespace.Example of XML code
Provide a sample encoding in XML of the new / changed element (with potential attributes). Write your text after the "Example:" below. As these are adopted from EAC-CPF see the EAC-CPF tag library for encoding examples: