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

Why are we not using xref #1019

Closed
egekorkan opened this issue Apr 5, 2022 · 3 comments
Closed

Why are we not using xref #1019

egekorkan opened this issue Apr 5, 2022 · 3 comments

Comments

@egekorkan
Copy link
Contributor

After @aphillips comments at w3c/wot-thing-description#1437, more specifically the one about adding i18n-glossary to our xref, I thought "What is xref?". Then I have discovered a bunch of nice stuff from respec. Basically, xref allows documents written by respec (all WoT specs) to use each other's definitions. For this, we need to first export our definitions and then use in other specifications. Actually, we are not exporting even the TD since searching for it at https://respec.org/xref/ returns nothing, which is sad.

Is there a specific reason why we were not using it so far?

Some further documentation:

@k-toumura
Copy link
Contributor

Looking at data export manual page in Respec wiki, it appears that only "browser specs" can use this feature.

@egekorkan
Copy link
Contributor Author

That is sad but I think we can at least use the exported definitions. Our specs do not even have xref field in the respecConfig

@egekorkan
Copy link
Contributor Author

Closing. #1078 can continue the discussion

@egekorkan egekorkan closed this as not planned Won't fix, can't repro, duplicate, stale May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants