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

Rename repository #16

Closed
ashepherd opened this issue Mar 27, 2019 · 13 comments
Closed

Rename repository #16

ashepherd opened this issue Mar 27, 2019 · 13 comments
Labels
question Further information is requested wontfix This will not be worked on
Milestone

Comments

@ashepherd
Copy link
Member

Ok, we picked the name science-in-schema.org quickly and without using our brains. I feel it's a little pretentious and not respecting other science disciplines and efforts in the schema.org space (e.g. bioschemas.org).

Any thoughts?

@ashepherd ashepherd added the question Further information is requested label Mar 27, 2019
@ashepherd ashepherd added this to the v1.0 milestone Mar 27, 2019
@lewismc
Copy link
Member

lewismc commented Mar 27, 2019

@ashepherd what about geosci.schema.org?

@ashepherd
Copy link
Member Author

ah, I like it. but, if we wanted to mint our own properties, we would have to go through schema.org first. maybe we can pick another domain too? @fils did you have a domain already?

Or we can punt and just change the name of this repo

@lewismc
Copy link
Member

lewismc commented Mar 28, 2019

@ashepherd aye that's an excellent point. I don't know to be honest.

@mbjones
Copy link
Collaborator

mbjones commented Apr 16, 2019

https://geoschemas.org ? Is that you already there, @ashepherd ? The format looks familiar.

@ashepherd
Copy link
Member Author

Yeah, we needed a stable URL to host any potential schema.org extensions. I threw that up quickly with a copy of schema.geolink.org, but the plan is to move that to Jekyll here in a new Github repo under ESIP. But, maybe we repurpose this repository and kill two birds with one stone? I didn't mean to step on toes by claiming all science. Thoughts?

@mbjones
Copy link
Collaborator

mbjones commented Apr 16, 2019

Honestly, I wasn't that worried about 'claiming all science'. But it would be nice to not have discipline bounds on what kind of extensions are in scope. Many of the extensions we are proposing (like how to link to associated metadata records in #4) are not specific to geo. An alternative might be esipschemas.org? Or scienceschemas.org?

@ashepherd
Copy link
Member Author

That's a very good point. Maybe we wait until RDA 14 when Mingfang's schema.org WG gets off the ground to determine the right place for general science recommendations and geo-specific recommendations.

@lewismc
Copy link
Member

lewismc commented Apr 16, 2019

Also, ideally we would want the domain to be minted for a decent length of time (10 years) as is done with sweetontology.net & .org. ESIP owns these. We convinced ESIP to purchase and own these domains.

@ashepherd
Copy link
Member Author

ashepherd commented Apr 16, 2019 via email

@lewismc
Copy link
Member

lewismc commented Apr 17, 2019

OK great. That sounds good @ashepherd

@lewismc
Copy link
Member

lewismc commented Apr 17, 2019

@ashepherd I'm registering this AGU session right now. Will I just use the name geoschemas.org ?

@ashepherd
Copy link
Member Author

ashepherd commented Apr 17, 2019 via email

@charlesvardeman
Copy link
Collaborator

I had a thought last week that maybe having two repositories could be useful for different purposes. I don't believe the existing science-on-schema.org has any new vocabulary as of yet but exists mainly of examples for integrating schema.org datasets at the repository level. I think having an effort that is giving examples and provides a place to go when getting into the schema.org weeds for the sciences is VERY important, and could be broader than just the earth sciences. Then having a second geoshemas.org that is similar to bioschemas.org that provides the geo-specific extensions to schema.org would make sense. The only purpose of geoschemas.org would be then to vet and discuss new vocabulary and publish that new vocabulary as community driven extensions to schema.org.

@ashepherd ashepherd added the wontfix This will not be worked on label Dec 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

4 participants