-
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
@instanceUrl #130
Comments
Adding to the draft schema, but I think that we might want to discuss this attribute again. Given that Also, not sure how/if other XML schemas handle this, but in HTML you can use a link tag like so:
So, in EAD3's case, I like that this attribute is available in control, but I'm not sure if |
Not sure, but would people use Should we consider taking an alternative approach via a linking element, may be we could (re)consider incorporating |
I think that would make a lot more sense than having an attribute named instanceURL on an element named recordid. I've got the "EAD3 way of doing things" set up in a draft version of the schema, but I think it would be a good idea to try out this suggestion in a different branch. |
Outcome EAC-CPF September 2020 meeting: Agree to remove @instanceURL and not follow EAD; agree to move toward using |
Tag Library Text: Summary: The URL for the EAC-CPF instance itself (as opposed to HTML or other derivatives). Available on |
@ailie-s : Sorry, my fault. |
I think, this still needs to go through schema testing, too, even if only to confirm that the attribute is not in the schema anymore. Will do that check later on today or early tomorrow. |
I still have instanceURL on recordId, but I'll update that in just a bit. |
Just to confirm for schema testing, that |
Instance URL
The idea to add the optional attribute
@instanceUrl
with data type any URI to<recordId>
and to follow EAD for alignment was rejected. Use<representation>
with@href
link and explain this approach in the documentation/best practices. guidelines.Creator of issue
Related issues / documents
20200128_SharedSchemaOverview
EAD3 Reconciliation
Decision from EAC-EAD-Schema joint meeting, 28 Jan 2020, due to alignment of in both standards.
Summary:
The URL for the EAD instance itself (as opposed to HTML or other derivatives, which may be captured in
<representation>
elements). Available on<recordid>.
Data Type: anyURI
Context
EAD3 specific attribute.
Solution documentation
no added
The text was updated successfully, but these errors were encountered: