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

Add option for catalog file #313

Merged
merged 7 commits into from
Jul 23, 2018
Merged

Conversation

beckyjackson
Copy link
Contributor

See #274

* @param pattern wildcard pattern to match
* @return array of files
*/
private static File[] getFileByPattern(String pattern) {
Copy link
Member

Choose a reason for hiding this comment

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

Should be plural: getFilesByPattern

docs/global.md Outdated

## Prefixes

Terms in OBO and OWL are identified using <a href="https://en.wikipedia.org/wiki/Internationalized_resource_identifier" target="_blank">IRIs</a> (Internationalized Resource Identifiers), which generalize the familiar addresses for web pages. IRIs have many advantages, but one of their disadvantages is that they can be pretty long. So we have standard ways to abbreviate IRIs in a particular context by specifying **prefixes**. For example, Turtle files start with `@prefix` statements, SPARQL queries start with `PREFIX` statements, and JSON-LD data includes a `@context` with prefixes.
Copy link
Member

Choose a reason for hiding this comment

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

Please use normal Markdown links throughout, not HTML links. We'll assume that people know how to use their browsers by now, and can open links in new windows/tabs if they want to.

docs/global.md Outdated

## XML Catalogs

OWLAPI, Protègè, and ROBOT use XML catalogs to specify where import files are located when loading an ontology. By default, this catalog is called `catalog-v001.xml`. ROBOT assumes that a `catalog-v001.xml` file exists in the working directory and attempts to resolve imports based on that. Because Protègè also predicts that catalog, we recommend sticking to this standard. For more details, see <a href="https://protegewiki.stanford.edu/wiki/Importing_Ontologies_in_P41" target="_blank">Importing Ontologies in Protègè and OWL 2</a>.
Copy link
Member

Choose a reason for hiding this comment

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

Wrong accents, should be Protégé.

docs/global.md Outdated
--input edit.owl --output merged.owl
```

If a catalog file is provided and cannot be located, the ontology will be loaded without a catalog file. Similarly, if you do not provide a `--catalog` and the `catalog-v001.xml` file does not exist in your working directory, the ontology will be loaded without a catalog file. Finally, if the catalog specifies an import file that does not exist, the command will fail.
Copy link
Member

Choose a reason for hiding this comment

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

Should be "If a catalog file is specified and cannot be located"

docs/global.md Outdated

## Error Messages

### JDON-LD Error
Copy link
Member

Choose a reason for hiding this comment

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

Should be JSON-LD Error. Will this error IRI work after renaming to global.md?

@jamesaoverton
Copy link
Member

Hmm. d4cbc6c passes mvn verify on my laptop, but Travis is unhappy with it.

@jamesaoverton jamesaoverton merged commit aaf531f into ontodev:master Jul 23, 2018
@beckyjackson beckyjackson deleted the catalog-file branch July 31, 2018 15:32
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.

2 participants