Internet link in source citations #578
-
As an explict tag is missing for internet links in source citations we have the technical FAQ: We see the possibility if using OBJE, OBJE.FILE, OBJE.FILE.FORM which is fully backed by the standard to have 1 SOUR @S1@
2 OBJE @O1@
0 OBJE @O1@
1 FILE www.internet.link.example.com
2 FORM text/html This looks like a very conformant solution, whereas putting the link as (part of) SOUR.PAGE as recommended by the FAQ is a solution which is not that close to standard. Hope in 7.1. we will have the 1 SOUR @S1@
2 WWW www.internet.link.example.com solution like in other structures of the standard! By this the internet example link would be linked to the source citation. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 1 reply
-
I disagree, you are now asking for two different locations for the “where in source” to be added! In the software I use we already have implemented using the I’m writing this from my phone, don’t have access to my computer at this time! Sourcing needs a complete rewrite to accommodate many of the needs for writing a citation! |
Beta Was this translation helpful? Give feedback.
-
Discussed in steering committee 10 DEC 2024: A small note about the example: FILE requires a File Path, including one of the schemes ftp://, http://, or https://, so the original examples that start www are not correct. We know that there are many ways that current systems store URLs, and hence there is no ability to ban any of those because they exist in the wild. In the Technical FAQ, we have noted three ways, that differ in where they store the data and the granularity of the URL (i.e. does it apply to a single citation or to an entire source):
In principle an application could do more than one of these, though that would likely cause the URL to appear more than once in the formatted citation and could cause the links to get out of sync with one another. This discussion proposes a fourth
The first three of these have the property that they show up in common formatted citations, which OBJE.FILE does not. Depending on the intent of the user, that lack of showing up in most formatted citations could be seen as either a feature or a bug. |
Beta Was this translation helpful? Give feedback.
-
A quick reply to concerning the difference between the 4 places identified above, I currently use two application, my primary one is web based and the other is desktop based.
|
Beta Was this translation helpful? Give feedback.
-
Regarding pertinence of a URL to a “source artifact” vs citation of that source artifact. Obviously these are two different things. The “source artifact” (aka the Source_Record) uses the REPO.CALN to tell us where at the repository the source artifact can be found (i.e. the book, census, church registry, list of information). The citation is found in the Source_Citation (SOUR.PAGE) and always should point at where in the source artifact we can find the reference to the fact we are asserting, for example the page in the book, census, or church registry! |
Beta Was this translation helpful? Give feedback.
Discussed in steering committee 10 DEC 2024:
A small note about the example: FILE requires a File Path, including one of the schemes ftp://, http://, or https://, so the original examples that start www are not correct.
We know that there are many ways that current systems store URLs, and hence there is no ability to ban any of those because they exist in the wild. In the Technical FAQ, we have noted three ways, that differ in where they store the data and the granularity of the URL (i.e. does it apply to a single citation or to an entire source):
In principle an application could do more than one of these, though tha…