Closed rockivist closed 9 years ago
I am inclined to think it superfluous in that there are no xlink processors as such, that I know of. The main reason for retaining the xlink attributes is that is reasonably well thought out as to what ought to be in a good actionable link for processing, and of course, while not quite right, it helps with creating semantic links.
D
On Mar 24, 2014, at 1:35 PM, Michael Rush notifications@github.com wrote:
Now that we have removed all non-simple links from EAD, do we need to keep @linktype in the schema? I see no functional reason to do so. The only argument I can see is for careful compatibility with xlink. I note that EAC-CPF only includes simple links, but still carries @xlink:type. See http://www3.iath.virginia.edu/eac/cpf/tagLibrary/cpfTagLibrary.html#xlinktype.
@tcatapano - what do you think? This came up from the tag library editorial team.
— Reply to this email directly or view it on GitHub.
I agree with @dpitti that it is superfluous. The Tag Library can state that the linking attributes align with xlink and that all links in EAD documents are simple links in the xlink sense. As Daniel rightly points out, xlink is more useful as a conceptual model than it is for processing.
Thank you gentlemen. I'll pass this to TS-EAD.
Based on email feedback from TS-EAD, go ahead and remove @linktype
from the schema.
Keep open after implementation and assign to Kelcy for documentation review.
Implemented.
Reopening for documentation review
I've removed linktype from the TL. @rockivist or @tcatapano - any thoughts on where in the documentation to address "that the linking attributes align with xlink and that all links in EAD documents are simple links in the xlink sense"?
@kshepher I'll include something about the linking model in the introduction.
Thanks, @rockivist. I'll leave this open, then.
Addressed in TL preface. Closing.
Now that we have removed all non-simple links from EAD, do we need to keep
@linktype
in the schema? I see no functional reason to do so. The only argument I can see is for careful compatibility with xlink. I note that EAC-CPF only includes simple links, but still carries@xlink:type
. See http://www3.iath.virginia.edu/eac/cpf/tagLibrary/cpfTagLibrary.html#xlinktype.@tcatapano - what do you think? This came up from the tag library editorial team.