Generated from UML->XMI->intermediate->XSD. This class represents the main resources defined by the Simulation Data Model in the same way as the Registry/Resource class represents resources in registries. It is the base class of specialisations SimDM/Protocol, SimDM/Experiment, SimDM/Project and SimDM/Service. These resources are the root entities that would get registered in a Simulation Database for example. They are also represented by root element declarations in XML schema serialisations of the model. This class is a thin copy of the Registry/Resource and borrows some of its elements. It *is-not-a* Registry Resource in the sense of inheritance. In particular a SimDM/Resource has a more refined and targeted content model. Also, SimDM/Resource-s are in general (much) more fine grained than Registry/Resource-s and would not qualify to be registered in an IVOA Registry. It will howevere be possible to transform certain SimDM/Resource-s into Registry/Resource-s. _12_1_1_8e0028f_1178789094562_459260_296 For Protocol : The name by which this simulator is commonly known. Ex: Gadget, Flash For Project : the name of the project For Experiment : the name of this experiment _14_0_8e0028f_1202994215578_466351_2236 A description of this resource. _14_0_8e0028f_1202994225718_41210_2238 a URL to a web page describing the resource. _14_0_8e0028f_1202820901406_132212_2887 The UTC date and time this resource was created in the real world. _12_1_bd102fc_1207069813179_860162_204 The UTC date and time this resource was updated in the real world. _12_1_213004e4_1315644458656_107294_466 a tag indicating whether this resource is believed to be still actively maintained. _12_1_bd102fc_1207069870715_18336_214 Information that describes a Party, that is a person/individual or possibly an organisation. _12_1_bd102fc_1206601369187_165113_153 the name or title of the contact person. This can be a person's name, e.g. "John P. Jones" or a group, "Archive Support Team". _12_1_bd102fc_1206601454839_501438_173 the contact email address _12_1_bd102fc_1206601562607_6509_183 the contact mailing address All components of the mailing address are given in one string, e.g. "3700 San Martin Drive, Baltimore, MD 21218 USA". _12_1_bd102fc_1206601501647_3817_178 the contact telephone number Complete international dialing codes should be given, e.g. "+1-410-338-1234". _12_1_bd102fc_1206601595223_756513_188 A SimDM/Project is an aggregation of SimDM/Resource-s that belong together, for example because they have been produced together in the course of a scientific project. Examples are parameter studies where a large number of simulations is run with slightly varying parameter settings. But also a single large simulation with a number of post-processing results can be gathers in this way. It is assumed that SimDM/Project are generally "big enough" to qualify to be represented as a full-fledged Registry/Resource in an IVOA Registry. This possibility was on of the reasons to add this concept to the model. _12_1_2_8e0028f_1191338785390_934381_291 Associative class between a SimDM/Project and its constitutent SimDM/Resource-s. _14_0_8e0028f_1202820710484_502833_2761 Reference to another SimDM/Resource that is included in the containing SimDM/Project. _12_1_8e0028f_1224855169437_868401_705 This class connects a Party to a resource. It indicates the role the party plays on the resource, for example creator, owner or publisher. _12_1_213004e4_1274444062671_377653_391 The role this contact plays in the Resource _12_1_8e0028f_1224853332062_719679_435 Reference to the Party that the Contact associates to the Resource. _12_1_213004e4_1274444081593_12789_464 Represents the scientific goal associated to a SimDM/Resource. This can be the goal of an experiment or project, or the type of object that a particular protocol will always produce. Is made concrete by suclasses representing objects or processes. We model a Target as "being an" ObjectType, which allows one to give a more detailed representation of its properties. The target is important as it represents one of the main questions scientists will ask about an experiment: what kind of astrophysical object or system or process was being simulated or modelled. _12_1_213004e4_1274345546500_619096_413 This class represents the actual system that is being simulated. Instances of this object should correspond to physical objects and/or systems. They should be the answer to queries such as, “what does this simulation simulate?” _12_1_8e0028f_1175527967546_211274_169 Indication on how many objects of this type are being modelled. _12_1_8e0028f_1175773895625_51712_255 If the target object type referes to a real object, this attribute allows one to indicate which object. This is performed by a URI that should identify the object in the Ontology of SimbadIdentifiedNames In some cases a real identified object in the universe is being modelled. If that is the case, this attribute allows that object to be identified. We assume a list of such objects may be provided through some means, embodied by the IdentifiedObject data type. Ex: Galaxy, Antennae, M31. _12_1_8e0028f_1175790322468_364162_369 Represents a concept in a SKOS vocabulary of astronomical and astrophysical object types. _12_1_8e0028f_1175874156890_481760_321 This class represents the fact that some simulations are run with the goal (Target) to investigate physical processes, rather than simulation specific objects or systems. Instances of this class can be used to describe this. For example one may study "turbulence", or "gravitational cluster" or "galaxy formation". _12_1_2_213004e4_1193927417218_156887_401 A term from the AstroJournalSubjectKeywords ontology. _12_1_2_213004e4_1193927509421_457098_479 The ContactRole enumeration contains the different roles a SimDM/Party can play in the creation or publishing of a SimDM/Resource. _12_1_8e0028f_1210681081343_459631_731 Role indicating that a certain SimDM/Party owns the SimDM/Resource. Role indicating that a certain SimDM/Party created the SimDM/Resource. Role indicating that a certain SimDM/Party published the SimDM/Resource in a SimDB repository for example. Role indicating that a certain SimDM/Party made some otherwise unspecified contribution to the creation of the SimDM/Resource.