Source of Statements about Push 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:Push_data sadocontology1:arguments """However the solution has some problems: Not all applications can be integrated into the system. it appears that pushing the data only as a single major advantage: the fact that the critical systems can decide when they have sufficient resources available for pushing their code to the application. The biggest disadvantage however, the fact that not all systems are compatible with this solution is reason enough to discard the idea. advantages: control when to push at tool - performance Disadvantages: no control when data is pushed + not compatible with all tools""" ; sadocontology1:description "Pushing data from one layer to another when ready up to the data storage at the end. This performed very puristicly, the data extractors wouldn’t so much be extractors but API’s that are able to receive data from the appropriate sources." ; sadocontology1:knowledge_is_located_in
,
; sadocontology1:name "Push data" ; sadocontology1:status "Rejected" ; a sadocontology1:Design_Alternatives, owl:NamedIndividual ; rdfs:label "Push 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:Push_data sadocontology1:arguments """However the solution has some problems: Not all applications can be integrated into the system. it appears that pushing the data only as a single major advantage: the fact that the critical systems can decide when they have sufficient resources available for pushing their code to the application. The biggest disadvantage however, the fact that not all systems are compatible with this solution is reason enough to discard the idea. advantages: control when to push at tool - performance Disadvantages: no control when data is pushed + not compatible with all tools""" ; sadocontology1:description "Pushing data from one layer to another when ready up to the data storage at the end. This performed very puristicly, the data extractors wouldn’t so much be extractors but API’s that are able to receive data from the appropriate sources." ; sadocontology1:knowledge_is_located_in
,
; sadocontology1:name "Push data" ; sadocontology1:status "Rejected" ; a sadocontology1:Design_Alternatives, owl:NamedIndividual ; rdfs:label "Push 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