<objectXMLWrap>

[SJagodzinski]

Object XML Wrap

• add attributes:
  @audience
• keep name and scope

Creator of issue

1. Silke Jagodzinski
2. TS-EAS: EAC-CPF subgroup
3. [email protected]

Related issues / documents

EAD3 Reconciliation

Additional EAD 3 attributes
@altrender - Optional
@audience - Optional (values limited to: external, internal)
@lang - Optional
@script - Optional

Context

A place for incorporating XML elements from any XML namespace.

May contain: any element from any namespace
May occur within: <cpfRelation> <functionRelation> <resourceRelation> <setComponent> <source>
Attributes: @xml:id - optional
Availability: Optional, Non-repeatable

Solution documentation

Rephrasing Summary, Description and Usage and Attribute usage needed?

May contain: any element from any namespace
May occur within: <relation>, <setComponent>, <source>
Attributes:
@audience - optional (values limited to: external, internal)
@id - optional
Availability: Optional, Not repeatable

• New or other example needed
• Topic for Best Practise Guide

Encoding example

<objectXMLWrap audience="external" id="objectxmlwrap1">
 <anyelementofanynamespace/>
</objectXMLWrap>

[ailie-s]

Tag Library text:

Summary: An optional child element of <relation>, <setComponent> and <source> that allows for the inclusion of an XML element from any XML namespace other than EAC-CPF.
May contain: [any element from any namespace]
May occur within: <relation>, <setComponent>, <source>
Description and usage:
A wrapper element that provides a place to express data in any XML encoding language other than EAC-CPF.
While the element is not restricted with respect to namespace, to facilitate interoperability the XML should conform to an open, standard XML schema and a namespace attribute should be present on the root element referencing the namespace of the standard.
<objectXMLWrap> may be used to store related XML data locally rather than linking to external resources in order to facilitate processing or in cases where the related data may not be reliably accessible.
Attributes:
@audience - optional (values limited to: external, internal)
@id - optional
@languageOfElement - optional
@scriptOfElement - optional
Availability: Optional, not repeatable

[karinbredenberg]

Test of element objectXMLWrap:
May occur within: relation 0..1, Ok in both schemas
setComponent 0..1, Ok in both schemas
source 0..1 Ok in both schemas if placed after sourceEntry
Contains other xml Ok in both schemas, must have a namespace
@Audience - optional (values limited to: external, internal) Ok in both schemas
@id - optional Ok in both schemas
@languageOfElement - optional Ok in both schemas
@scriptOfElement - optional Ok in both schemas

Result: In source must be placed after sourceEntry, the XML within must have a namespace, attributes conventionDeclarationReference, maintenanceEventReference, sourceReference are present in both schemas and not in the TL definition. @ailie-s so you see the extra attributes that might be waiting for a decision? and we have the sourceEnty -> reference pending.

[fordmadox]

Updated with 9eef90a.

Also removed the language and script attributes as per meeting decision on 6 November.

Still the open question about enforcing the order, but keeping that as-is from EAC 1.0 for now.

[karinbredenberg]

Retest:
Only attributes present:
@Audience - optional (values limited to: external, internal) Ok in both schemas
@id - optional Ok in both schemas

Result: Pending if the XML must have a namespace or not.

[karinbredenberg]

Reconfirmation:

There can be non-namespace but it needs to be set to no-namespace:

<objectXMLWrap>
<non-eas-xml xmlns="">
<etcetera/>
</non-eas-xml>
</objectXMLWrap>

Result: Element passed test. @ailie-s and example with no namespace as shown here is needed and perhaps also in the explanation?

[karinbredenberg]

2 Examples (with and withour namespace) will be made by the EAC-CPF team.

[SJagodzinski]

No comment on <objectXMLWrap> from the Call for Comments.