Skip to content

URL for the spec #138

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

Closed
bergos opened this issue Jan 16, 2019 · 13 comments
Closed

URL for the spec #138

bergos opened this issue Jan 16, 2019 · 13 comments
Assignees

Comments

@bergos
Copy link
Member

bergos commented Jan 16, 2019

The spec is currently hosted at http://rdf.js.org/. We are also working already on the Dataset spec. To have more future prove URLs, I propose to create a different repository, which will be used to host the start page. On the start page we can list all specs, libraries, additional documentation, etc.

@bergos
Copy link
Member Author

bergos commented Jan 16, 2019

That would also mean that the URL would change to the repository name, which would be http://rdf.js.org/representation-task-force/ at the moment. We should give the repo a better name, matching to the scope of the spec. It contains the Data Model + Stream interfaces. Let's just skip the Stream part from the repo name and just call it data-model-spec.

@RubenVerborgh
Copy link
Member

+1

@bergos
Copy link
Member Author

bergos commented Jan 21, 2019

Please +1 in the next 3 days if you agree or leave a comment if you disagree. I will rename the repo then and create a new repo for the start page.

@elf-pavlik
Copy link
Member

if you use index.html in those repos, will we get just

?

@vhf
Copy link
Member

vhf commented Jan 22, 2019

@elf-pavlik Yes that's how it works as long as we have:

https://github.com/rdfjs/rdfjs.github.io/blob/master/CNAME
                         ^^^^^^^^^^^^^^^             ^^^^^

and github pages enabled in the repos

@elf-pavlik
Copy link
Member

@bergos https://github.com/rdfjs/rdfjs.github.io could become the index (home) page

@elf-pavlik
Copy link
Member

I don't want to get into bikeshedding but maybe we should just call the first spec data-factory-spec, keep the second dataset-spec and come up with name for stream interfaces possibly even splitting source-sink-spec from store-spec which may include RegExp and/or filtering.

https://github.com/rdfjs/data-model/ actually exports Data Factory so naming spec and module data-factory makes more sense to me.

@RubenVerborgh
Copy link
Member

Let's not make it too complex people, or no one's gonna use it. factory by itself is already extremely heavy for JavaScript standards, let's not emphasize.

@bergos
Copy link
Member Author

bergos commented Jan 22, 2019

I think data-model is more understandable than data-factory. Also it's more important what your factory builds and Data Model objects sounds good to me for Term and Quad objects. The Dataset spec also defines a factory and that's also what the package exports. That could be also the case for a Prefix spec. So we may end up with a lot of -factory repos if we add factory to all of them.

@elf-pavlik
Copy link
Member

ok data-model sorry for distraction

@blake-regalia
Copy link
Contributor

I actually find data-factory easier to understand but maybe I am in the minority :)

@elf-pavlik
Copy link
Member

Should we rename this repo to data-model-spec and rename interface-spec.html to index.html so that we have it available on https://rdf.js.org/data-model-spec ?

@bergos
Copy link
Member Author

bergos commented Feb 7, 2019

I made a PR to rename the file to index.html #155 . I think it's not a problem to rename the repo already now. The new start page for rdf.js.org is in progress. I should be able to make a PR till tomorrow.

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

5 participants