Skip to content
This repository has been archived by the owner on Mar 15, 2022. It is now read-only.

Publishing HTS codes as Linked Data #923

Open
nissimsan opened this issue Aug 3, 2021 · 7 comments
Open

Publishing HTS codes as Linked Data #923

nissimsan opened this issue Aug 3, 2021 · 7 comments
Assignees

Comments

@nissimsan
Copy link

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!

@mogul
Copy link
Contributor

mogul commented Aug 5, 2021

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 Catherine.defilippo@usitc.gov. 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.

@nissimsan
Copy link
Author

@mogul, many thanks for this! I will reach out to Catherine Defilippo about this.
If you don't mind, I'll keep this ticket open for sharing info on further progress.
Thanks again!

@mogul
Copy link
Contributor

mogul commented Aug 11, 2021

Sure, no problem.

@mogul mogul self-assigned this Aug 19, 2021
@mogul mogul added this to the Sprint 20210819 milestone Aug 19, 2021
@mogul mogul closed this as completed Sep 3, 2021
@TallTed
Copy link

TallTed commented Oct 27, 2021

@mogul -- I'm confused by your closure of this issue, which has not been resolved satisfactorily (Catherine.defilippo@usitc.gov 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?

@mogul
Copy link
Contributor

mogul commented Oct 27, 2021

Sorry about that! The issue was closed in a bulk operation. I'll reopen it.

@mogul mogul reopened this Oct 27, 2021
@nissimsan
Copy link
Author

Thanks for following up, @TallTed and @mogul,

@mogul, might you have another name I can try reaching out to at USITC? I've sent Catherine three emails now and haven't heard anything back.

@hkdctol
Copy link
Contributor

hkdctol commented Oct 28, 2021

Hi @nissimsan you can try the Chief Data Officer at the agency--he can be reached at jeremy.wise@usitc.gov

@mogul mogul removed this from the Sprint 20210819 milestone Oct 28, 2021
@GSA GSA deleted a comment from Thegoon23 Oct 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants