-
Notifications
You must be signed in to change notification settings - Fork 410
Publishing HTS codes as Linked Data #923
Comments
Hi @nissimsan, thanks for your inquiry. The catalog.data.gov site federates the data provided by each individual agency; as such we're not the owners of these codes and we're not the best place to host stable identifiers, so we can't help you directly. The upstream office that supplies these codes also expose a PDF detailing a REST API they provide. It has a search API, but I know you'd rather have a static URL for an identifier. The contact listed for the dataset is [email protected]. Perhaps she can help you with having the API amended to provide stable URLs for each code? That would put the ownership and exposure of the URLs closest to where they're managed and revised. |
@mogul, many thanks for this! I will reach out to Catherine Defilippo about this. |
Sure, no problem. |
@mogul -- I'm confused by your closure of this issue, which has not been resolved satisfactorily ([email protected] has not been responsive; see w3c-ccg/traceability-vocab#178 (comment)), given that you were OK keeping this issue open as a tracker. I understand that your team is not the maintainer of the HTS dataset, but as a part of the greater data.gov bureaucracy, I think you are in a far better position than @nissimsan or me to find and/or get a response from the team that is. Please help? |
Sorry about that! The issue was closed in a bulk operation. I'll reopen it. |
Hi @nissimsan you can try the Chief Data Officer at the agency--he can be reached at [email protected] |
Hi,
https://catalog.data.gov/dataset/harmonized-tariff-schedule-of-the-united-states-2019 is a great list. Concise and intuitive. Thank you.
I'd like to request if you can expose this code list also as Linked Data, please. What this means is that each code has a URI. For example, code 6204.11.00.00 would be identified by a URI something like
https://catalog.data.gov/dataset/harmonized-tariff-schedule/6204.11.00.00
.Referencing such a URI makes allows explicit semantic expression and interpretations.
I don't know if you expose Linked Data elsewhere. If not, schema.org is a good source of inspiration of a well functioning linked data vocabulary. The common technology used for linked data is JSON-LD.
Thanks in general for doing an awesome job in this important field!
The text was updated successfully, but these errors were encountered: