Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

@conventionDeclarationReference #174

Open
SJagodzinski opened this issue Nov 1, 2020 · 8 comments
Open

@conventionDeclarationReference #174

SJagodzinski opened this issue Nov 1, 2020 · 8 comments
Assignees
@SJagodzinski
Labels
Attribute Best Practice Guide Tested by Schema Team Passed both the RNG and XSD schemas.
Milestone
Best Practise Guide

Comments

@SJagodzinski
Copy link
Contributor

SJagodzinski commented Nov 1, 2020 •
edited
Loading

Convention declaration reference

Add new optional attribute @conventionDeclarationReference with data type IDREFS in all non-empty elements alongside the language attributes @lanuageOfElement and @scriptOfElement .

With @conventionDeclarationReference a direct link to a conventation declaration element within cpf/control/conventionDeclaration can be provided. The attribute can be used to link to a convention or rule that prescribe a method for converting one script into another script (transliteration). It also can be used to link to a national, international or other rule that govern the construction of EAC-CPF name (formerly used in dropped elements <alternativeForm>, <authorizedForm>, and preferredForm).

Creator of issue

  1. Silke Jagodzinski
  2. TS-EAS: EAC-CPF subgroup
  3. silkejagodzinski@gmail.com

Related issues / documents

Topic: Assertion Description in EAS
Assertion Description (or Assertion Control) #43
Topic_names_20200130.pdf
Names control #26

EAD3 Reconciliation

new EAS attribute

Context

new EAS attribute

Solution documentation: agreed solution for TL and guidelines

Rephrasing Summary, Description and Usage and Attribute usage needed

Data type: IDREF

May occur within: <abstract>, <address>, <addressLine>, <agencyCode>, <agencyName>, <agent>, <alternativeSet>, <biogHist>, <chronItem>, <chronItemSet>, <chronList>, <citedRange>, <componentEntry>, <contact>, <contactLine>, <conventionDeclaration>, <date>, <dateRange>, <dateSet>, <description>, <descriptiveNote>, <event>, <eventDateTime>, <eventDescription>, <existDates>, <fromDate>, <function>, <functions>, <generalContext>, <geographicCoordinates>, <head>, <identityId>, <item>, <language>, <languageDeclaration>, <languageUsed>, <languagesUsed>, <legalStatus>, <legalStatuses>, <list>, <localControl>, <localDescription>, <localDescriptions>, <localTypeDeclaration>, <maintenanceAgency>, <maintenanceEvent>, <maintenanceHistory>, <mandate>, <mandates>, <nameEntry>, <nameEntrySet>, <occupation>, <occupations>, <otherAgencyCode>, <otherEntityType>, <otherEntityTypes>, <otherRecordId>, <p>, <part>, <place>, <placeName>, <placeRole>, <places>, <recordId>, <reference>, <relation>, <relationType>, <representation>, <rightsDeclaration>, <setComponent>, <shortCode>, <source>, <sources>, <span>, <structureOrGenealogy>, <targetEntity>, <targetRole>, <term>, <toDate>, <useDates>, <writingSystem>

  • Example needed
  • Topic for Best Practise Guide

Example encoding
@SJagodzinski SJagodzinski added this to the Schema milestone Nov 1, 2020
@ailie-s
Copy link

ailie-s commented Nov 2, 2020 •
edited
Loading

Tag Library Text:

Summary: Use @conventionDeclarationReference to provide a direct link to a <conventionDeclaration> element within control/conventionDeclaration from any non-empty elements in the EAC-CPF instance. The attribute can be used to link to a convention or rule that prescribes a method for converting one script into another script (transliteration). It also can be used to link to a national, international or other rule that governs the construction of an EAC-CPF name.
Data type: IDREFS

@deletedname

This comment has been minimized.

Sign in to view
@SJagodzinski SJagodzinski changed the title @conventationDeclarationReference @conventionDeclarationReference Nov 17, 2020
@SJagodzinski

This comment has been minimized.

Sign in to view
@SJagodzinski SJagodzinski mentioned this issue Dec 23, 2020
Closed
This was referenced Jan 3, 2021
Closed
Closed
Closed
@fordmadox
Copy link
Member

fordmadox commented Jan 19, 2021 •
edited
Loading

Regarding the datatype: @ailie-s @SJagodzinski @kerstarno, I won't tag each issue unless there is agreement on this approach, but based on the discussion around how to convert the nameEntry / nameEntryParallel elements from EAC 1.x to 2.0 (e.g. #117 (comment)), I changed the datatypes for all of the *Reference attributes and @target from IDREF to IDREFS. Does that sound like a good approach for the call for comments / migration process?

@kerstarno kerstarno self-assigned this Jan 22, 2021
@kerstarno
Copy link
Contributor

There currently are some inconsistencies with regard to where @conventionDeclarationReference and its two sibling attributes, @maintenanceEventReference (#173) and @sourceReference (#172), can be used:

  • The solution documentation above lists 81 elements, which are the same as for @languageOfElement(@xml:lang #151) and @scriptOfElement(@scriptOfElement #152). Similarly, the TL draft above says, @conventionDeclarationReference can be used "from any non-empty elements in the EAC-CPF instance".
  • In the draft schema (RNG and XSD), however, there are currently only 63 elements that allow for the usage of @conventionDeclarationReference and its two sibling attributes.
    • This adds <cpfDescription>, <identity>, and <relations>, which are not listed here, but do have the @...Reference attributes as well as the language attributes at the moment.
    • And it excludes the elements that only appear in <control> (i.e. <agencyCode>, <agencyName>, <agent>, <citedRange>, <conventionDeclaration>, <eventDateTime>, <eventDescription>, <languageDeclaration>, <localControl>, <localTypeDeclaration>, <maintenanceAgency>, <maintenanceEvent>, <maintenanceHistory>, <otherAgencyCode>, <otherRecordId>, <recordId>, <representation> , <rightsDeclaration>, <shortCode>, <source>, <sources>), which is in line with the general decision on this taken during the Chicago meeting.
    • @SJagodzinski Could you please confirm where @conventionDeclarationReference and its two sibling attributes should be used?

Apart from that:

  • @conventionDeclarationReference has the data type IDREFS
  • It is always available alongside @maintenanceEventReference
  • It is always available alongside @sourceReference

The above applies to both schemas, RNG and XSD.

@ailie-s the data type has recently changed to IDREFS in order to allow for several IDs to be pointed to within one attribute.

@kerstarno kerstarno added Pending final decision Tested by Schema Team Passed both the RNG and XSD schemas. labels Jan 22, 2021
This was referenced Jan 22, 2021
Closed
Closed
@SJagodzinski
Copy link
Contributor Author

Regarding the datatype: @ailie-s @SJagodzinski @kerstarno, I won't tag each issue unless there is agreement on this approach, but based on the discussion around how to convert the nameEntry / nameEntryParallel elements from EAC 1.x to 2.0 (e.g. #117 (comment)), I changed the datatypes for all of the *Reference attributes and @target from IDREF to IDREFS. Does that sound like a good approach for the call for comments / migration process?

@fordmadox : I agree and true, no need to comment each issues with this solution.

@SJagodzinski
Copy link
Contributor Author

Schema version 85f90b0 uses reference attributes correctly, no need to change.

Documentation will be updated.

@SJagodzinski SJagodzinski modified the milestones: Schema, Tag Library Feb 2, 2021
@kerstarno
Copy link
Contributor

@SJagodzinski thanks for the confirmation.

With this, the attribute is ready.

@SJagodzinski SJagodzinski assigned SJagodzinski and unassigned ailie-s Mar 27, 2021
@SJagodzinski SJagodzinski removed this from the Tag Library milestone Jan 8, 2022
@SJagodzinski SJagodzinski added this to the Best Practise Guide milestone Feb 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SJagodzinski SJagodzinski

Labels
Attribute Best Practice Guide Tested by Schema Team Passed both the RNG and XSD schemas.
Projects
None yet
Milestone
Best Practise Guide
Development

No branches or pull requests
5 participants
@fordmadox @deletedname @SJagodzinski @kerstarno @ailie-s