Source of Statements about Rule handling for processing data (without imported statements)
Properties
History
Community
Source
You have no permissions to edit this model.
Saving has been disabled.
# Exported with the Erfurt API - http://aksw.org/Projects/Erfurt @base
. @prefix dct:
. @prefix ns0:
. @prefix ns1:
. @prefix ns2:
. @prefix ns3:
. @prefix ontology1288790966584:
. @prefix ontowiki_wikipage:
. @prefix owl2xml:
. @prefix owl:
. @prefix rdf:
. @prefix rdfs:
. @prefix sadocontology1:
. @prefix sioc:
. @prefix sioct:
. @prefix sysconf:
. @prefix uva-sa-ontology:
. @prefix view:
. @prefix xsd:
. sadocontology1:Rule_handling_for_processing_data sadocontology1:decision_is_about sadocontology1:Business_Logic_Layer ; sadocontology1:decision_issue "After the data has been abstracted and gathered, it still needs to be processed. It is useful to have already assigned some properties to users (such as: “is expert on”) and to have made connections between users." ; sadocontology1:depends_on sadocontology1:Complexity, sadocontology1:Rule_handling ; sadocontology1:design_decision "The use of a business rules engine is more fit for the problem in our opinion, because of the straight-forwardness of rule adaption as well as the fact that it’s an industry-standard practice. The fact that it introduces a bit of complexity is not reason enough to discard the idea, especially since the alternative solution does the same in a different space." ; sadocontology1:name "Rule handling for processing data" ; sadocontology1:posit_design sadocontology1:Use_of_business_rules_engine, sadocontology1:Use_of_hard-coded_rules ; sadocontology1:results_in sadocontology1:Business_rules_engine ; sadocontology1:status "Decided" ; a sadocontology1:Design_issue, owl:NamedIndividual ; rdfs:label "Rule handling for processing data" .
# Exported with the Erfurt API - http://aksw.org/Projects/Erfurt @base
. @prefix dct:
. @prefix ns0:
. @prefix ns1:
. @prefix ns2:
. @prefix ns3:
. @prefix ontology1288790966584:
. @prefix ontowiki_wikipage:
. @prefix owl2xml:
. @prefix owl:
. @prefix rdf:
. @prefix rdfs:
. @prefix sadocontology1:
. @prefix sioc:
. @prefix sioct:
. @prefix sysconf:
. @prefix uva-sa-ontology:
. @prefix view:
. @prefix xsd:
. sadocontology1:Rule_handling_for_processing_data sadocontology1:decision_is_about sadocontology1:Business_Logic_Layer ; sadocontology1:decision_issue "After the data has been abstracted and gathered, it still needs to be processed. It is useful to have already assigned some properties to users (such as: “is expert on”) and to have made connections between users." ; sadocontology1:depends_on sadocontology1:Complexity, sadocontology1:Rule_handling ; sadocontology1:design_decision "The use of a business rules engine is more fit for the problem in our opinion, because of the straight-forwardness of rule adaption as well as the fact that it’s an industry-standard practice. The fact that it introduces a bit of complexity is not reason enough to discard the idea, especially since the alternative solution does the same in a different space." ; sadocontology1:name "Rule handling for processing data" ; sadocontology1:posit_design sadocontology1:Use_of_business_rules_engine, sadocontology1:Use_of_hard-coded_rules ; sadocontology1:results_in sadocontology1:Business_rules_engine ; sadocontology1:status "Decided" ; a sadocontology1:Design_issue, owl:NamedIndividual ; rdfs:label "Rule handling for processing data" .
OntoWiki
Search for Resources
User
Register New User
Extras
SPARQL Query Editor
News
Help
Documentation
Bug Report
Version Info
About
Knowledge Bases
Architecture Knowledge Domain Ontology
View
Show Hidden Knowledge Bases
Navigation
Search in Navigation
View
Number of Elements
10
20
30
Toggle Elements
Hidden Elements
Empty Elements
Implicit Elements
Reset Navigation
Type
Classes
Properties
SKOS
Groups
Login
Local
OpenID
FOAF+SSL
Username
Password
Remember me
Login
Register
OpenID
Login
Register
Login
Register