Comments (6)
The status attribute will be handled in a similar way as with the visibility one. There will be a fixed set of possible values, at least initially.
- In ontology page, include button showing current status and drop-down list with options to change it
- For create vocab/mapping options, no need to include this attribute, at least initially, given the new option above that allows to changed it on any registered ontology
- However, do include it in the Upload sequence (which already has the visibility one)
Note: For now we will handle status similarly as with visibility: as a direct attribute to the ontology version model and not with direct association to any metadata property. In this sense we can explain to the user that if any metadata attribute (in particular for uploaded ontologies) should reflect the intended status, then it's up to them to maintain the correspondence. That is, upon a change in status that should be reflected:
- the user would first create a new version with the relevant metadata property updated; then use the change-status option to reflect the corresponding value for the attribute.
from orr-portal.
From https://www.w3.org/2003/06/sw-vocab-status/note.html, the following status values will be made available (with "resource" substituted for "term" in the descriptions, plus an additional draft entry):
- draft
The resource is in preliminary stages of development. - unstable
The meaning, deployment practices, documentation (or important associated software/services)
associated with this resource are liable to change arbitrarily at some point in the future.
They may not, but stability is not guaranteed. Use with caution. - testing
The meaning, deployment practices, documentation and general understanding of this resource are
approaching some stability, but changes are still possible due to implementation experience
or other unanticipated factors. - stable
The resource is relatively stable, and its documentation and meaning are not expected to
change substantially. - archaic
This resource is marked as old-fashioned; although used, it is not considered typical
of current best practice and alternative expressions may be preferable.
from orr-portal.
Much better. Please add also "deprecated: This resource is marked as no longer suitable for use, although past uses may still exist."
from orr-portal.
I actually had "deprecated" in my initial addition to the list, but then thought that it was so similar to "archaic" . In fact I was thinking about simply changing that key from "archaic" to "deprecated". Please give me your opinion to select one, or some combination of the following:
- if you think there's enough differentiation between them, keep both "archaic" and "deprecated"
- else, keep "archaic" (as already defined, or with your new definition)
- ... or, rename "archaic" to "deprecated"
- ... or?
from orr-portal.
I'm working on this right now -- will add your "deprecated" option to list in the mean time.
from orr-portal.
Thanks Carlos, adding deprecated is the right thing, so, no further action needed. The two are quite distinct, and I think archaic is something that wouldn’t be used much, but is worth having for compatibility.
from orr-portal.
Related Issues (20)
- Upgrade gulp 3.9.1 --> 4.0.1 HOT 4
- Admin: show indication of public or owner visibility in main list HOT 1
- gulp tasks broken HOT 2
- `gulp install` not fully completing HOT 3
- Nested IRI not being handled correctly HOT 3
- Double slash in create vocab or mapping
- Update YASGUI to Triply.cc version HOT 2
- No URL-encoding when dispatching external viewer for fully-hosted ontology
- Broken links for CF ontology HOT 2
- Embed ORCID ID handling in portal HOT 1
- Retry without trailing slash
- Icons failing to build
- Move mmisw.org/ont away from TAMU-CC HOT 1
- encode external IRI in links from browse page
- change mappings to use SSSOM-compatible format
- fix variable types on metadata entry
- tab descriptions in metadata
- improve implementation of vocabulary creation (SKOS etc)
- better searching experience
- better ontology browse page UI
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from orr-portal.