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

What about RDF ? #76

Closed
akuckartz opened this issue Nov 16, 2017 · 8 comments
Closed

What about RDF ? #76

akuckartz opened this issue Nov 16, 2017 · 8 comments

Comments

@akuckartz
Copy link

The Recommendation seems to apply only to HTML. What about RDF serialisations ?

@devd
Copy link
Contributor

devd commented Nov 17, 2017

The spec is mostly focused on HTML intentionally. Maybe some day we will look at RDF but it is unlikely in the next version.

(unless browser vendors are really interested in this)

@BigBlueHat
Copy link
Member

FWIW, we are exploring integrity expression in JSON-LD in relationship to @context values and meaning. See w3c/json-ld-syntax#9 for more on the topic.

@dveditz
Copy link
Member

dveditz commented Nov 5, 2018

I could certainly see adding fetch parameters to indicate integrity, and then you'd be covered whatever the contents happen to be. Is that what you were getting at?

@awwright
Copy link
Contributor

awwright commented Nov 21, 2018

I'm working on standardizing some other hypermedia formats, what we really need is a Web linking attribute registry that we can register SRI with.

It would have to describe the link attribute name, the range of the target (is it a URI or a text string), and the metadata that it generates, and any other ways it affects the state of the link or relationship between the two resources.

As far as I understand, there's still no way to add an SRI attribute to the HTTP Link header, correct? That would otherwise have to be added in an update to RFC 8288, due to how link attributes are defined.

@mozfreddyb
Copy link
Collaborator

I could certainly see adding fetch parameters to indicate integrity, and then you'd be covered whatever the contents happen to be. Is that what you were getting at?

I'm not sure what you're saying but fetch() does support an integrity option.

@mozfreddyb
Copy link
Collaborator

Closed due to inactivity.

@akuckartz
Copy link
Author

Others issues created three years ago without any comment are still open but this younger ones with several comments is closed because there was no comment in seven months? Strange.

@mozfreddyb
Copy link
Collaborator

I'm going through issues one-by-one, not having triaged all of them yet that's what it looks like.
If you insist, I'm happy to re-open and label it with "far future" if you insist - but it seems there is other work required that is outside of this spec (e.g.,the RFC 8288 thing above) and I'm not going to drive that.
Happy to revisit once this is unblocked. Sounds fair?

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

6 participants