-
Notifications
You must be signed in to change notification settings - Fork 3
Issues: nimble-platform/common
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Extending party data model for terms considering seller/buyer roles
#19
opened Jul 20, 2018 by
dogukan10
Rework index/core Concepts to have all necessary information for concepts
blocker
data schema
Related to the NIMBLE ontology and generated cores/index
very high priority
Redundant properties for each uploaded product (if assigned to a category)
data schema
Related to the NIMBLE ontology and generated cores/index
medium priority
Mapping of fields (core: catalogue2, properties) and ontology properties (Marmotta) doesn't exist
data schema
Related to the NIMBLE ontology and generated cores/index
very high priority
Common label for concepts of the ontology (domain specific and eclass)
data schema
Related to the NIMBLE ontology and generated cores/index
very high priority
Integration of all properties of a product in core properties
data schema
Related to the NIMBLE ontology and generated cores/index
high priority
Monitor (Business-Process) according-to (Platform data channels)
affects user interface
new feature
#5
opened Feb 7, 2018 by
jinnerbichler
Execute (Business-Process) according-to (Contract)
affects user interface
new feature
#4
opened Feb 7, 2018 by
jinnerbichler
Delivery / Shipment Terms [06Nov2017-1225]
affects user interface
new feature
#1
opened Feb 7, 2018 by
jinnerbichler
ProTip!
Mix and match filters to narrow down what you’re looking for.