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

pull in catalog-v001.xml file with namespace mapping to local files #148

Merged
merged 2 commits into from Jul 19, 2019

Conversation

smrgeoinfo
Copy link
Collaborator

the first commit here is from updating my fork from the esipFed github, it should have no effect. Second commit is the new catalog file that lets you open sweetAll.ttl from a repo clone using protege.

Stephen Richard and others added 2 commits July 18, 2019 13:51
sync with esipfed/sweet
To open sweetAll.ttl in protege, put this in the github repo /src directory with all the .ttl files
@lewismc lewismc added this to the 3.4.0 milestone Jul 19, 2019
@lewismc lewismc self-requested a review July 19, 2019 06:53
Copy link
Member

@lewismc lewismc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@lewismc
Copy link
Member

lewismc commented Nov 13, 2019

Dammit @smrgeoinfo this was never merged into master branch... can you please rebase against master?

@smrgeoinfo
Copy link
Collaborator Author

OK I rebased usgin master against the ESIPfed SWEET master. The catalog xml file should still be valid if none of the SWEET file names have changed. I'd completely forgotten I'd already generated a catalog to load things locally. I'd still suggest that it shouldn't be in the src directory, and the readme for the repo should have a note that if you want to load the local ontology files from your checkout, move the catalog-v001.xml file into the src directory.

@lewismc
Copy link
Member

lewismc commented Nov 13, 2019

ack, if you could send a pull request it would be great. Thank you

@smrgeoinfo
Copy link
Collaborator Author

OK, creating a new pull request #172

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants