-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
@status #254
Comments
@ailie-s : Is |
@SJagodzinski : I don't think |
Might be constructed, but in theory the following encoding would be valid, if we wanted to say that something has a timespan and that we know it's still active, but we are not sure about the actual start date:
Question might be - do we instead want to "enforce" an encoding such as:
by restricting the values for |
We didn't discuss during today's meeting, did we? Anyhow, just let me know if I need to make any changes in the schemas. |
Let's keep it simple: Values:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Tag Library Text: Summary: Attribute that provides controlled terminology detailing the status of elements. Available in |
Tested as part of Schema Team's schema testing:
The above applies to both schemas, RNG and XSD. |
There is currently a pending question if at least |
Well, the question in #179 was pending. Anyway, note taken for feedback on the call for comments. :-) |
With the decision to not have |
Following their meeting on 18 June, the EAD team would like to suggest that |
EAC-CPF meeting 3 September 2021: Decision: add the optional |
Re-tested with the XSD and RNG schemas available in the development branch (status of 8 January 2022). I can confirm that |
Status
@status
to<agencyCode>
,<date>
,<fromDate>
,<nameEntry>
,<otherAgencyCode>
,<toDate>
to indicate if an element contains the authorized or alternative form of a code or a name or to indicate unknown and ongoing datesCreator of issue
Related issues / documents
New attribute
@status
#70Topic_names_20200130.pdf
Topic_dates_20200911.pdf
EAD3 Reconciliation
new EAC attribute
Context
new EAC attribute
Solution documentation:
Summary, Description and Usage and Attribute usage needed
May occur within:
<agencyCode>
,<fromDate>
,<nameEntry>
,<otherAgencyCode>
,<toDate>
Values:
<agencyCode>
,<nameEntry>
,<otherAgencyCode>
: authorized, alternative<fromDate>
: unknown<toDate>
: unknown, ongoing<date>
: unknownsee also: Kerstins comment in #70:
Example encoding
The text was updated successfully, but these errors were encountered: