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
Changes to existing element / attribute
Give the current name of the element / attribute. Include the tag name and the full name.
Name: @resourceRelationType and @eagRelationType
Change in context
List all parent elements to which the element / attribute should be added. Furthermore, list all parent elements from which the element / attribute should be removed.
Remove from
Parent element(s): <resourceRelation> and <eagRelation> (which are to be removed themselves)
New element / attribute
Give the name of the new element / attribute. Include the tag name and the full name.
Name: <relationType>
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): <relation> (0..n)
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.
Sub-element(s): [TEXT]
Attributes (with default values, if applicable): @audience with values "external" or "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 (0), option to add an attribute from any other namespace
Example for usage of the new / changed element (including potential attributes)
Describe how the new / changed element should be used.Write your text after the "Text:" below.
Text: For the conversion route between the current attributes and the new element see #107 and #103
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.
Example: See #103
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
Changes to existing element / attribute
Give the current name of the element / attribute. Include the tag name and the full name. Name:
@resourceRelationTypeand@eagRelationTypeChange in context
List all parent elements to which the element / attribute should be added. Furthermore, list all parent elements from which the element / attribute should be removed.
Remove from
Parent element(s):
<resourceRelation>and<eagRelation>(which are to be removed themselves)New element / attribute
Give the name of the new element / attribute. Include the tag name and the full name. Name:
<relationType>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):
<relation>(0..n)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. Sub-element(s): [TEXT] Attributes (with default values, if applicable):
@audiencewith values "external" or "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(0), option to add an attribute from any other namespaceExample for usage of the new / changed element (including potential attributes)
Describe how the new / changed element should be used. Write your text after the "Text:" below. Text: For the conversion route between the current attributes and the new element see #107 and #103
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. Example: See #103