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.

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

Closed
SJagodzinski opened this issue Jan 30, 2020 · 9 comments
Closed

@instanceUrl #130

SJagodzinski opened this issue Jan 30, 2020 · 9 comments

Comments

@SJagodzinski
Copy link
Contributor

SJagodzinski commented Jan 30, 2020

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

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

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

@SJagodzinski SJagodzinski self-assigned this Jan 30, 2020
@SJagodzinski SJagodzinski changed the title @instanceurl @instanceUrl Aug 6, 2020
@SJagodzinski SJagodzinski assigned fordmadox and ailie-s and unassigned SJagodzinski Aug 6, 2020
@SJagodzinski SJagodzinski added this to the Schema milestone Aug 6, 2020
@fordmadox
Copy link
Member

fordmadox commented Aug 8, 2020

Adding to the draft schema, but I think that we might want to discuss this attribute again.

Given that @instanceurl is only used in one location in EAD3; and that the examples that I've seen in the real world don't line up with the TL definition; and given that I don't know of other XML schemas that attempt to provide a canonical URL for the XML file within the XML file itself: I wonder if this attribute is needed in either schema? If kept, then I think that additional documentation should be provided.

Also, not sure how/if other XML schemas handle this, but in HTML you can use a link tag like so:

<link rel="canonical" href="https://eac.staatsbibliothek-berlin.de/schema/taglibrary/cpfTagLibrary2019_EN" />

So, in EAD3's case, I like that this attribute is available in control, but I'm not sure if recordid is the best place to use it (nor if it's really needed). The recordid element stores the primary identifier for the record, so having an attribute on it that provides a link to the entire record itself doesn't seem entirely right to me (as the url is not qualifying the ID). Something like html/head/link, however, is more clear, to me at least, since you are providing a link (possibly back, possibly self-referencing ) to the canonical version of the file itself.

@kerstarno
Copy link
Contributor

Not sure, but would people use @instanceURL e.g. to enable downloads of their online finding aids or authority records in XML format? Or to maybe provide a link to the original XML when the EAS instances are shared with aggregators and enriched in that context? I know that we are using the attribute @url in that way in Archives Portal Europe, although we are rather pointing to the original HTML representation than to the original XML (seeing that we are using EAD 2002, which doesn't have such distinction).

Should we consider taking an alternative approach via a linking element, may be we could (re)consider incorporating @instanceURL in <representation> (#140), which already comes with the set of linking attributes, i.e. using a simple @href instead of @instanceURL? And if we'd consider that, might it be useful to consider introducing the terminology of "Instantiation" (instead of <representation>) picking up on RiC?

@fordmadox
Copy link
Member

fordmadox commented Aug 16, 2020

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.

@SJagodzinski
Copy link
Contributor Author

SJagodzinski commented Sep 22, 2020

Outcome EAC-CPF September 2020 meeting:

Agree to remove @instanceURL and not follow EAD; agree to move toward using <representation> with href link.
Explain this approach in the documentation/best practices guidelines.

@ailie-s
Copy link

ailie-s commented Nov 5, 2020

Tag Library Text:

Summary: The URL for the EAC-CPF instance itself (as opposed to HTML or other derivatives). Available on <recordId>.
Data type: anyURI

@SJagodzinski
Copy link
Contributor Author

@ailie-s : Sorry, my fault. @instanceURL will be omitted resp. not intruduces, cf #130 (comment).

@kerstarno
Copy link
Contributor

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.

@kerstarno kerstarno self-assigned this Nov 17, 2020
@fordmadox
Copy link
Member

I still have instanceURL on recordId, but I'll update that in just a bit.

@kerstarno
Copy link
Contributor

Just to confirm for schema testing, that @instanceURL has been removed (again) from RNG and XSD schemas.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants