Source of Statements about Data schema for tool types (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:Distribution_of_data_schema_for_tool_types sadocontology1:arguments "To store the collected raw data in databases per system brings an extra boost in performance and parallel working abilities. But more it brings extra advantages in the administration and security side. It extends the possibility to move the schemas on different servers, if the load is more than expected, or even if one server moves to another. Further it brings separation of concern in the database schemas, so the backups could be planned per tool type and its database. A downside is it asks more administration needs then the one schema solution." ; sadocontology1:decision_is_about sadocontology1:relational_database ; sadocontology1:decision_issue "? For the data collector there 2 existing ways to store the extracted data from the different data sources (tool types)" ; sadocontology1:depends_on sadocontology1:Extensibility_of_data_sources, sadocontology1:Extractor, sadocontology1:Flexibility, sadocontology1:Performance, sadocontology1:Security ; sadocontology1:design_decision """Decentralized data schema. The decision is to use a database schema for every tool type. This decision is based on the conclusion above. The database schema per tool type brings the needed extensibility also on the administration side. It also brings flexibility in moving the schemas or even to delete them when no data Gatherer for this type exists.""" ; sadocontology1:knowledge_is_located_in
,
; sadocontology1:name "Data schema for tool types" ; sadocontology1:posit_design sadocontology1:Centralized_data_scheme, sadocontology1:Decentralized_data_scheme ; sadocontology1:status "Decided" ; a sadocontology1:Design_issue, owl:NamedIndividual ; rdfs:label "Data schema for tool types" .
# 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:Distribution_of_data_schema_for_tool_types sadocontology1:arguments "To store the collected raw data in databases per system brings an extra boost in performance and parallel working abilities. But more it brings extra advantages in the administration and security side. It extends the possibility to move the schemas on different servers, if the load is more than expected, or even if one server moves to another. Further it brings separation of concern in the database schemas, so the backups could be planned per tool type and its database. A downside is it asks more administration needs then the one schema solution." ; sadocontology1:decision_is_about sadocontology1:relational_database ; sadocontology1:decision_issue "? For the data collector there 2 existing ways to store the extracted data from the different data sources (tool types)" ; sadocontology1:depends_on sadocontology1:Extensibility_of_data_sources, sadocontology1:Extractor, sadocontology1:Flexibility, sadocontology1:Performance, sadocontology1:Security ; sadocontology1:design_decision """Decentralized data schema. The decision is to use a database schema for every tool type. This decision is based on the conclusion above. The database schema per tool type brings the needed extensibility also on the administration side. It also brings flexibility in moving the schemas or even to delete them when no data Gatherer for this type exists.""" ; sadocontology1:knowledge_is_located_in
,
; sadocontology1:name "Data schema for tool types" ; sadocontology1:posit_design sadocontology1:Centralized_data_scheme, sadocontology1:Decentralized_data_scheme ; sadocontology1:status "Decided" ; a sadocontology1:Design_issue, owl:NamedIndividual ; rdfs:label "Data schema for tool types" .
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