Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }
- partialOverlapFrom comment "partialOverlapFrom is an abstract property to express the first object that takes part in a PartialOverlap.\n ".
- partialOverlapRatio comment "partialOverlapRatio is an abstract property to express the ratio of dividing the partialOverlapArea by the area of the object pointed by partialOverlapFrom. \n ".
- partialOverlapTo comment "partialOverlapTo is an abstract property to express the second object that takes part in a PartialOverlap.\n ".
- partialOverlapUnit comment "partialOverlapUnit is an abstract property to express the units of partialOverlapArea of two things in a PartialOverlap. \n ".
- partiallyOverlapping comment "partiallyOverlapping is an abstract property to express that an object is partially overlapping with another.".
- rightOf comment "rightOf is an abstract property to express that an object is to the right from another.".
- sharesPathWith comment "sharesPathWith is an abstract property to express that an object shares a path with another.".
- sizeOfLandArea comment "sizeOfLandArea is an abstract property to express the size of the land area of a region.".
- southEastOf comment "southEastOf is an abstract property to express that an object is Southeast of another.".
- southOf comment "southOf is an abstract property to express that an object is South of another.".
- southWestOf comment "southWestOf is an abstract property to express that an object is Southwest of another.".
- tangentialProperPart comment "tangentialProperPart is an abstract property to express that an object is tangential proper part of another.".
- touches comment "touches is an abstract property to express that a region touches another region.".
- unionOf comment "unionOf is an abstract property to express which union a spatiotemporal region forms.".
- westOf comment "westOf is an abstract property to express that an object is West of another.".
- determiner_str comment "The lexical space: \"\", \"the\", \"a\", \"an\", and \"auto\".".
- integer_str comment "A string representation of a 32-bit signed integer. Example lexical values include \"1234\" and \"-123\".".
- mime_type_str comment "Valid mime type strings (e.g., \"application/mp3\").".
- string comment "A string of Unicode characters.".
- url comment "A string of Unicode characters forming a valid URL having the http or https scheme.".
- Action comment "An action currently performed by the Agent (e.g., listening to music, reading a book).".
- Active comment "The Agent is active on the system.".
- Activity comment "OnlineStatusComponent used to represent the state of\n\t\t\tActivity of the Agent (e.g., Active, Inactive,\n\t\t\tProlongedInactive).".
- AllNotificationsPass comment "Agent can receive notifications from applications".
- Available comment "The agent is not busy and therefore available for contatc by\n\t\t\tother Agents.".
- ConstrainedContactability comment "The Agent cannot be contated by anyone on the Web, but the\n\t\t\tcontactability is controled by some rules/policies.".
- ConstrainedFindability comment "The Agent's contact details cannot be found by anyone on\n\t\t\tthe Web, but the findability is controled by some\n\t\t\trules/policies.".
- Contactability comment "OnlineStatusComponent used to represent the state of\n\t\t\tcontactability of an Agent. Contatctability relates to the\n\t\t\tpossiblity of other Agents to conatct the Agent freely or\n\t\t\tonly with regard to some conditions.".
- Disturbability comment "OnlineStatusComponent used to represent the wish of an Agent\n\t\t\tto be or not to be disturbed.".
- Findability comment "The OnlinePresenceComponent used to represent the\n\t\t\tpossibility to find contact details of an Agent in a public\n\t\t\tlisting".
- FreelyContactable comment "The Agent can be contacted by anyone on the Web".
- Inactive comment "The Agent is inactive for at least 5 min.".
- Invisible comment "The Agent's OnlineStatus is not visible to other Agents".
- Notifiability comment "The OnlinePresenceComponent used to represent the attitude\n\t\t\tof an Agent towards interaction with applications i.e., the\n\t\t\tpossibility of applications to show notifications.".
- NotificationsConstrained comment "The acceptance of notifications from applications is somehow\n\t\t\tconstrained (by using some rules or policies).".
- NotificationsProhibited comment "Agent cannot receive any notification form applications".
- OnlinePresence comment "OnlinePresence, described in termes of various\n\t\t\tOnlinePresenceComponents to represent the attitude of an\n\t\t\tAgent towards interaction with other Agents and\n\t\t\tApplications.".
- OnlinePresenceComponent comment "A component of OnlinePresence used to represent one of its\n\t\t\tdimensions.".
- OnlineStatus comment "The OnlinePresenceComponent used to represent the attitude\n\t\t\tof an Agent towards the possibility of communication with\n\t\t\tother Agents. The OnlineStatus is defined by its components.".
- OnlineStatusComponent comment "The component of the OnlineStatus representing one of its\n\t\t\tdimensions.".
- ProlongedInactive comment "The Agent is inactive for at least 20 min.".
- PubliclyFindable comment "The Agent's contact details canbe found by anyone on the\n\t\t\tWeb".
- SharingSpace comment "A group of people belonging to a space for sharing online psresence data - the intended audience of data.".
- SourceOfPublishing comment "The source that can publish Online Presence data.".
- Visibility comment "OnlineStatusComponent used to represent the possiblity of\n\t\t\tothers to see the OnlineStatus of the Agent".
- Visible comment "The Agent's OnlineStatus is visible to other Agents".
- declaredBy comment "The Agent that declared the OnlinePresence".
- declaresOnlinePresence comment "The OnlinePresence declared by the Agent".
- hasPresenceComponent comment "OnlinePresenceComponent included in this OnlinePresence".
- hasStatusComponent comment "OnlineStatusComponent included in this OnlineStatus".
- isPresenceComponentOf comment "The OnlinePresence that has this OnlinePresenceComponent".
- isStatusComponentOf comment "The OnlineStatus that includes this OnlineStatusComponent.".
- ActionItem comment "Subclasses pdo:Artifact and models the structure of an action item/task".
- Artefact comment "An abstract class for any kind of information artifact which can be structured according to its sematics.".
- Comment comment "Models a comment made by a person".
- Document comment "The base class for all kinds of electronic documents in a project-specific setting.".
- LeaveReport comment "Subclasses pdo:Artefact and models the structure of a leave report".
- PersonRole comment "The abstract class modelling various roles taken by individuals during a particular context ( for example, the attendees, scribe etc in a meeting or the reporter in a status report.)".
- Report comment "Subclasses pdo:Artefact and models the structure of a travel report".
- v1 comment "IT Service Management Ontology (ITSMO) provides the vocabulary for \n annotating resources related to IT Service Management. ITSMO try to be \n consistent with 2011 ITIL glossary. ITIL® is a Registered Trade Mark, and \n a Registered Community Trade Mark of the Office of Government Commerce, \n and is Registered in the U.S. Patent and Trademark Office. Please make \n sure you are only using element identifiers in this namespace, \n e.g.http://ontology.it/itsmo/v1#ITService. There may be copies of the \n ontology file on the Web which can be retrieved from other locations, BUT \n THOSE LOCATIONS MUST NOT BE USED AS REFERENCES.".
- Agreement comment "A document that describes a formal understanding between two or more parties.\nAn agreement is not legally binding, unless it forms part of a contract.".
- Baseline comment "A configuration baseline is a snapshot that is used as a reference point.".
- Building comment "Any human-made structure used or intended for supporting or sheltering any use or continuous occupancy".
- Catalogue comment "A complete list of items, typically one in alphabetical or other systematic order".
- Configuration comment "A term that indicate a set of related phisical object with their metadata that are considered as a whole.".
- ConfigurationItem comment "any component or other service asset that needs to be managed in order to deliver an IT service. Information about each configuration item is recorded [at least] in a configuration record within the configuration management system and is maintained throughout its lifecycle by service asset and configuration management.\nConfiguration items are under the control of change management. They typically include IT services, hardware, software, buildings, people and formal documentation such as process documentation and service level agreements.\nNote that tis definition is a bit extensive than ITIL one, because it allow a CI to be described in more than one configuration records.This make this definition compatible with semantic web architecture that allow metadata do be defined everywhere in the web. See ITSMO user manual for more info about this class.".
- ControlledConfiguration comment "A term used to describe configuration subjected to change management and stored in a configuration management database (CMDB).\nIf you use a Version Control System as CMDB, this is could be the the name of a source tree. If you use a plain filesystem as CMDB, this is the pathname of a directory that contains a file structure. Could be thinked as a \"versioned directory\". This term is similar to ITILs: \"configuration record\".".
- Criticality comment "A process Critcality".
- CustomerAgreementPortfolio comment "A database or\nstructured document used to manage service\ncontracts or agreements between an IT\nservice provider and its customers. Each IT\nservice delivered to a customer should have\na contract or other agreement that is listed in\nthe customer agreement portfolio.".
- CustomerPortfolio comment "A database or\nstructured document used to record all\ncustomers of the IT service provider. The\ncustomer portfolio is the business\nrelationship manager’s view of the customers\nwho receive services from the IT service\nprovider.>".
- Dependency comment "The direct or indirect reliance of one Configuraiton Item on another.\n [ Note that the ITIL 2011 restrict the domain of this terms to Processes or activity, this definition is more general ]. This is a superclass for all types of dependency relastionship for a CI.".
- DependencyStrength comment "A Strength level for a dependency".
- Document comment "Information in readable form. A document may be paper or electronic – for example, a policy statement, service level agreement, incident record or diagram of a computer room layout.\n\nDublin Core vocabulary appy to objetc of thes class.".
- Hardware comment "the physical part of a computer".
- ITService comment "A service is a means of delivering value to customers by facilitating \n outcomes customers want to achieve without the ownership of specific \n costs and risks. An IT is a service provided by an IT service provider. \n An IT service is made up of a combination of information technology, \n people and processes. A customer-facing IT service directly supports the \n business processes of one or more customers and its service level \n targets should be defined in a service level agreement. Other IT \n services, called supporting services, are not directly used by the \n business but are required by the service provider to deliver \n customer-facing services.".
- Identity comment "A unique name that is used to identify a user, person or role. The identity is used to grant rights to that user, person or role. Example identities might be the username SmithJ or the role ‘change manager’.".
- LifeCycleStage comment "A stage in the life of a configuration item. The lifecycle defines the \n categories for status and the status transitions that are permitted. For \n example:\n\n <ul>\n <li>\n The lifecycle of an application includes requirements, design, build, \n deploy, operate, optimize.\n </li>\n <li>\n The expanded incident lifecycle includes detection, diagnosis, repair, \n recovery and restoration\n </li>\n <li>\n The lifecycle of a server may include: ordered, received, in test, \n live, disposed etc\n </li>\n </ul>".
- ManagementProcess comment "Is a process of planning and controlling one or more of activities. Here \n are some examples:\n\n <ul>\n <li>\n <b>Configuration Management</b>: the process responsible for ensuring \n that the assets required to deliver services are properly controlled, \n and that accurate and reliable information about those assets is \n available when and where it is needed. This information includes \n details of how the assets have been configured and the relationships \n betweens [ITIL glossary].\n </li>\n <li>\n <b>Project Management</b>: the discipline of planning, organizing, \n securing, and managing resources to achieve specific goals. A project \n is a temporary endeavor with a defined beginning and end (usually \n time-constrained, and often constrained by funding or deliverables), \n undertaken to meet unique goals and objectives, typically to bring \n about beneficial change or added value[Wikipedia].\n </li>\n <li>\n Change Management: the process responsible for controlling the \n lifecycle of all changes, enabling beneficial changes to be made with \n minimum disruption to IT services.[ITIL glossary]\n </li>\n </ul>\n <p>".
- OLA comment "An Agreement between an IT Service Provider and another part of the same Organisation. An OLA supports the IT Service Provider's delivery of IT Services to Customers. The OLA defines the goods or Services to be provided and the responsibilities of both parties. For example there could be an OLA between the IT Service Provider and a procurement department to obtain hardware in agreed times, between the Service Desk and a Support Group to provide Incident Resolution in agreed times.\nSee Service Level Agreement.".
- Plan comment "A detailed proposal that describes the activities and resources needed to achieve\nan objective – for example, a plan to implement a new IT service or process.\nISO/IEC 20000 requires a plan for the management of each IT service management\nprocess.".
- Policy comment "Formally documented management expectations and intentions. Policies are used to direct decisions, and to ensure consistent and appropriate development and implementation of processes, standards, roles, activities, IT infrastructure etc.".
- Priority comment "A process priority".
- Process comment "A structured set of activities designed to accomplish a specific objective. \nA process takes one or more defined inputs and turns them into defined outputs. It may include any of the roles, responsibilities, tools and management controls required to reliably deliver the outputs. A process may define policies, standards, guidelines, activities and work instructions if they are needed.".
- Project comment "A temporary organization, with people and other assets, that is required to achieve an\nobjective or other outcome. Each project has a lifecycle that typically includes initiation,\nplanning, execution, and closure. Projects are usually managed using a formal\nmethodology such as PRojects IN Controlled Environments (PRINCE2) or the Project\nManagement Body of Knowledge (PMBOK).".
- QualitativeValue comment "This property share the same definition of gr:QualitativeValue.\n A qualitative value is a predefined value for a service characteristic. \n\t\nExamples: The Service is critical.\n\t\nNote: Value sets are supported by creating subclasses of this class. Ordinal relations between values (gr:greater, gr:lesser, ...) can be provided directly by GoodRelations after subclassing itsmo:QualitativeValue to gr:QualitativeValue".
- RunTimeDependency comment "A time dependent dinamic dependency. \nFor example there is a runtime dependency betwen proces A and ITservice B when A calls a REST service exposed by B.".
- RunnableResource comment "Configuration items that require an execution environment to go live.".
- SLA comment "An Agreement between an IT Service Provider and a Customer. The SLA describes the IT Service, documents Service Level Targets, and specifies the responsibilities of the IT Service Provider and the Customer. A single SLA may cover multiple IT Services or multiple Customers.\nSee Operational Level Agreement.".
- ServiceOption comment "A choice of utility and warranty offered to customers by a core service or service package.".
- ServicePortfolio comment "The complete set of\nservices that is managed by a service\nprovider. The service portfolio is used to\nmanage the entire lifecycle of all services,\nand includes three categories: service\npipeline (proposed or in development),\nservice catalogue (live or available for\ndeployment), and retired services.".
- ServiceScope comment "The service Scope (busines or infrastructure)".
- Snapshot comment "A shapshot at a defined time frame for a configuration Item. Use dcterms:created to annotate the date of the snapshot.".
- SoftwarePackage comment "A logical entity that identify a software release or a software feature set.\nFor example: \"VirtueMart 1.1.x\", \"Linux LTS 10.04\" , \"Windows 7 service pack 2\", \"Apache 2\" . Sometime referenced only with \"software\".".
- StructuralDependency comment "describes a part/whole relationship between components.\nA strucural dependency is an included file, a paragrapg in a text, a library used by applcation an application etc. etc.".
- System comment "A number of related things that work together to achieve an overall Objective. For example:computer System including hardware, software and Applications, a management System, including multiple Processes that are planned and managed together. For example a Quality Management System, a Database Management System or Operating System that includes many software modules that are designed to perform a set of related Functions.".
- Template comment "A skeleton document or a document to be used as reference for editing another document.".
- Utility comment "The functionality offered by a product or service to meet a particular need. Utility can be summarized as ‘what the service does’, and can be used to determine whether a service is able to meet its required outcomes, or is ‘fit for purpose’. The business value of an IT service is created by the combination of utility and warranty.".
- Warranty comment "Assurance that a product or service will meet agreed requirements. This may be a formal agreement such as a service level agreement or contract, or it may be a marketing message or brand image. Warranty refers to the ability of a service to be available when needed, to provide the required capacity, and to provide the required reliability in terms of continuity and security. Warranty can be summarized as ‘how the service is delivered’, and can be used to determine whether a service is ‘fit for use’. The business value of an IT service is created by the combination of utility and warranty.".
- hasAccountable comment "The one ultimately accountable for the correct and thorough completion of the process, and the one to whom Responsible is accountable. In other words, an Accountable must sign off (Approve) on work that Responsible provides. There must be only one Accountable specified for each process.".
- hasBaseline comment "A reference to a baseline of a configuration.".