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

feat(data-cite): add support for data-cite attribute #1008

Merged
merged 3 commits into from Jan 5, 2017

Conversation

marcoscaceres
Copy link
Member

@marcoscaceres marcoscaceres commented Dec 30, 2016

This adds a new foundation feature to ReSpec, allowing authors to directly cite another SpecRef spec in inline text. This is currently very simple, on purpose... so we can build:

<!-- normative -->
It's in the <a data-cite="!DOM">DOM spec</a>.

<!-- informative -->
It's in the <a data-cite="HTML">HTML spec</a>.

That automatically adds href attribute pointing to the DOM spec. It also adds the reference to the References section in the right place.

@marcoscaceres
Copy link
Member Author

So, once this goes in, we can start targeting particular "types" - like methods, etc. that will allow seamless cross linking between specs.

@marcoscaceres marcoscaceres force-pushed the data-cite-biblio branch 5 times, most recently from 1710683 to fcedaf6 Compare December 30, 2016 06:38
@marcoscaceres
Copy link
Member Author

Thinking about next steps... I think I want:

<a data-cite=spec data-lt="xref in other spec" data-cite-type="">thing</a>

We then need a xref service tho.... it's not clear how BikeShed specs are currently producing their xref.json files, but we need to generate the same thing.

Then we need a central database for those with a RESTful API on the front.

@marcoscaceres marcoscaceres merged commit db87e6e into develop Jan 5, 2017
@marcoscaceres marcoscaceres deleted the data-cite-biblio branch January 5, 2017 02:06
@marcoscaceres
Copy link
Member Author

Merging as it's blocking my other stuff... will fix the async() issue on develop branch, as it's unrelated to this. Would still appreciate any feedback.

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

Successfully merging this pull request may close these issues.

None yet

1 participant