-
Notifications
You must be signed in to change notification settings - Fork 13
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
idot:AccessPattern #100
Comments
sent email to identifiers.org group on Jan 26. no response as of yet. |
Hi, Sorry about the delay in response, and thank you for the reminder! Firstly, going back to the example of Gene Ontology that you gave: Gene Ontology defines their identifier as being equivalent to the 'GlobalID', which constitutes a 'GO' prefix, and a numerical 'LocalID', separated by a colon [1]. This identifier is used by official Gene Ontology Resources [2], by both BioPortal and OLS, and is by far the most prevalent form found in publications and cross-references. The OBO Foundry have a policy for the creation of URIs [3], which dictates the transformation of the colon into an underscore. While this policy is not enforced, it is recommended (when using URIs). Hence there are a mixture of ontologies who do or do not implement this. Anyway, for the Identifiers.org registry, our aim is to store the regular expression reflecting the identifiers assigned by the data provider. If no documentation is available describing identifier strategies, we make an informed decision based on existing identifiers and common practice within the user community. We originally captured this pattern for our own use, for example to provide users information on potentially malformed URIs. Of course, if we can extend this feature to be more useful to the community at large, then we would encourage them to give us feedback. If there is a clear and demonstrable need from our users to store identifier patterns at the level of individual resources and identification schemes, then we can add it to our roadmap for future development. However, as far as I understand, all this should not impact the dataset description document, as far as the definition of the idot terms you wish to use is clear and cover the needs. Cheers, [1] http://wiki.geneontology.org/index.php/Identifiers |
I don't think that we should be focusing on the GO example here. What we are really looking for is a property which allows for the specification of the complete URI pattern where the regex is used to capture the identifier part. As I understand it, identifiers.org make use of two properties – I think that what we are looking for is a single property that would allow for the specification of the whole pattern as a regex; something like
VoID's
|
+1 |
@perkeo would you be able to add an entry to the identifiers.org ontology document? |
@micheldumontier Do we need to have the following in the example?
|
for completeness, yes, we should include. Michel Dumontier On Mon, Mar 9, 2015 at 2:15 PM, Alasdair Gray notifications@github.com
|
On the call today we discussed concerns about the suitability of the formulation of the idot:AccessPattern. In particular, we are concerned that appending the idot:identifierPattern to the idot:accessPattern is underspecified and could lead to errors.
Let's take the Gene Ontology (http://identifiers.org/go/) as an example. The idot:identifierPattern is ^GO:\d{7}$
This identifier pattern does not work for the original ontology URI, which is of the form
http://purl.obolibrary.org/obo/GO_\d+$
This identifier pattern is not correct for Bio2RDF, as 'GO' should be lowercase 'go' - really the correct access pattern should be a regex of the form http://bio2rdf.org/go:\d{7}+$
I propose that somewhere in the instance of an access pattern is a predicate that specifies the regex pattern.
The text was updated successfully, but these errors were encountered: