Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }
- hasAuthors comment "The author or authors of a document. For multiple authors, use either an instance of <link>foaf:Group</link>, or multiple values.".
- hasPresenter comment "The presenter of a presentation.".
- hasTitle comment "The title of the publication (book, article, ...) or publication container (series, journal).".
- hasTutor comment "The tutors of a tutorial.".
- hasVolumes comment "The <link>Volume</link>s of this journal.".
- hasWorkpackages comment "The work packages of a project.".
- ofJournal comment "The <link>Journal</link> this volume belongs to.".
- organizedby comment "The organizers of an event. At least one agent has to organize an event. The inverse property is <link>organizes</link>.".
- organizes comment "This property relates an agent to the events it organizes. The inverse property is <link>organizedBy</link>.".
- Article comment "A peer reviewed , refereed article from a journal.".
- Book comment "A complete book, not formed from separate papers.".
- DevelopmentProject comment "disjoint with researchProject? maybe not. Olivier 2006-06-07".
- Document comment "Dublin Core elements added. \nSee: http://dublincore.org/documents/dces/\n\nfor document types see:\nhttp://www.bsz-bw.de/diglib/medserv/konvent/metadat/dcresour.html".
- Graduate comment "disjoint with undergrad? Olivier 2006-06-07\nPhilipp: I wouldn't make it disjoint, since someone can be a bachelor-graduate, but if he is doing his master he is a master-undergraduate at the same time.".
- GraduateClass comment "see: http://www.neurolabor.de/socrate/ects_ganz.htm".
- InProceedings comment "A single paper from a published workshop or conference proceedings.".
- MasterThesis comment "A university Masters thesis.".
- PhDThesis comment "A university Doctoral thesis.".
- Proceedings comment "A whole published workshop or conference proceedings.".
- Topic comment "If changing this concept (or its subconcepts) consider that the swrc topic ontology depends on the foresaid one.\nThe swrc topic ontology can be found at:\nhttp://ontoware.org/frs/download.php/187/swrc-swtopics.owl".
- UndergraduateAdvancedClass comment "see: http://www.neurolabor.de/socrate/ects_ganz.htm".
- UndergraduateIntermediateClass comment "see: http://www.neurolabor.de/socrate/ects_ganz.htm\n\nhttp://dict.leo.org/cgi-bin/dict/urlexp/20030705201638".
- Unpublished comment "A document with an author and title, but not formally published.".
- cite comment "check domain. Olivier 2006-06-07\nPhilipp: checked.".
- givenBy comment "check domain. Olivier 2006-06-07\nPhilipp: checked.".
- hasPartEvent comment "Example: FIFA World Cup 2006 hasPartEvent Final".
- headOfGroup comment "added domain and range. Olivier 2006-06-07".
- headOfGroup comment "made a subproperty of headOf. Olivier 2006-06-07".
- isAbout comment "check domain. Olivier 2006-06-07\nPhilipp: checked.".
- member comment "can an organization be a member of another organization? olivier 2006-06-07\nPhilipp: Hmm could be possible. Therefore I added Organization to the range that one can state: Organization (has)member Organization.".
- organization comment "meaning not clear. Olivier 2006-06-07\nPhilipp: This property appears in the class definition of swrc:Document. I think it is obsolete, since you may link a document via the dc:creator, dc:contributor or dc:publisher property to an organization.".
- publication comment "check domain. Olivier 2006-06-07\nPhilipp: checked.".
- publication comment "hasPublication (?). Olivier 2006-06-07\nPhilipp: Yes, I think it is meant as \"hasPublication\". Anytime you have just the verb, it is meant as has + verb in a property.".
- publisherOf comment "check domain. Olivier 2006-06-07\nPhilipp: checked.".
- publisherOf comment "check range. Olivier 2006-06-07\nPhilipp: checked.".
- school comment "meaning is not clear. Olivier 2006-06-07\nPhilipp: This property appears in the class description of Thesis and I think should relate a Thesis to the associated university.".
- technicalReport comment "check domain. Olivier 2006-06-07\nPhilipp: checked.".
- ontology-07 comment "Updated version of the swrc ontology (v0.7.1) based on the original swrc ontology. Responsible ontology engineer: Philipp Zaltenbach. Date: 22.06.2007. Contributions made by: Olivier Dameron.".
- ArchRepository comment "Dépôt GNU Arch du code source.".
- ArchRepository comment "GNU Arch Quellcode-Versionierungssystem.".
- ArchRepository comment "GNU Arch source code repository.".
- ArchRepository comment "Repositorio GNU Arch del código fuente.".
- ArchRepository comment "Úložiště zdrojových kódů GNU Arch.".
- ArchRepository comment "ソースコードのGNU Archのリポジトリ".
- BKRepository comment "BitKeeper Quellcode-Versionierungssystem.".
- BKRepository comment "BitKeeper source code repository.".
- BKRepository comment "Dépôt BitKeeper du code source.".
- BKRepository comment "Repositorio BitKeeper del código fuente.".
- BKRepository comment "Úložiště zdrojových kódů BitKeeper.".
- BKRepository comment "ソースコードのBitKeeperのリポジトリ".
- CVSRepository comment "CVS Quellcode-Versionierungssystem.".
- CVSRepository comment "CVS source code repository.".
- CVSRepository comment "Dépôt CVS du code source.".
- CVSRepository comment "Repositorio CVS del código fuente.".
- CVSRepository comment "Úložiště zdrojových kódů CVS.".
- CVSRepository comment "ソースコードのCVSのリポジトリ".
- Project comment "A project.".
- Project comment "Ein Projekt.".
- Project comment "Projekt.".
- Project comment "Un projet.".
- Project comment "Un proyecto.".
- Project comment "プログラミングのプロジェクト".
- Repository comment "Dépôt du code source.".
- Repository comment "Quellcode-Versionierungssystem.".
- Repository comment "Repositorio del código fuente.".
- Repository comment "Source code repository.".
- Repository comment "Úložiště zdrojových kódů.".
- Repository comment "ソースコードのリポジトリ".
- Specification comment "A specification of a system's aspects, technical or otherwise.".
- Specification comment "あるシステムの詳しく書いた明細書。多分技術的なもの。".
- Version comment "Détails sur une version d'une realease d'un projet.".
- Version comment "Informace o uvolněné verzi projektu.".
- Version comment "Información sobre la versión de un release del proyecto.".
- Version comment "Version information of a project release.".
- Version comment "Versionsinformation eines Projekt Releases.".
- Version comment "リリースのバーション情報".
- repository comment "Dépôt du code source.".
- repository comment "Quellcode-Versionierungssystem.".
- repository comment "Repositorio del código fuente.".
- repository comment "Source code repository.".
- repository comment "Úložiště zdrojových kódů.".
- repository comment "このプロジェクトのソースコードのリポジトリ".
- Authorship comment "".
- disposition comment "used to connect to the text describing disposition of something, for example, a disposition of an issue".
- DataAsset comment "The term “data asset” is synonymous with “data source”".
- DataSchema comment "A representation of metadata, often in the form of data artifacts such as logical data models or conceptual data models. The Data Schema concept group is comprised of those concepts pertaining to the representation of structured data. A Data Schema provides a means to provision data sharing services that is independent of the values of the data in the data resource that it describes.".
- DataSteward comment "A person responsible for managing a Data Asset.".
- DigitalDataResource comment "A digital container of information, typically known as a file. A Digital Data Resource may be one of three specific types of data resources, each corresponding to one of the three types of data described earlier, and each described below (see “Structured Data Resource”, “Semi-Structured Data Resource”, and “Unstructured Data Resource”). It will be a container for the metadata about the data resource.".
- Document comment "While a Document can contain structured data, it normally has explanatory material included, which would cause it to therefore be considered semi-structured. It is for this reason that there is no “contains” relationship from Document to Structured Data Resource. It is very important to separate Documents from Structured Data Resources because they are processed very differently. The difference between a Document and a Digital Data Resource, therefore, is that a Digital Data Resource can contained structured data.".
- Entity comment "An abstraction for a person, place, object, event, or concept described (or characterized) by common Attributes. For example, “Person” and “Agency” are Entities. An instance of an Entity represents one particular occurrence of the Entity, such as a specific person or a specific agency.".
- StructuredDataResource comment "A Digital Data Resource containing structured data. This data can be accessed in a uniform manner, independent of data values, once the Data Schema is known.".
- Agency comment "An agency of the US government".
- Customer comment "The diverse nature of federal programs means that there are many customers spanning the citizen, business, other government, and internal categories. Some customers\nreceive direct government services, such as veterans receiving health care from the Veterans Health Administration. Other “customers” are those subject to regulatory activities, such as large businesses conforming to safety regulations administered by the Occupational Safety and Health Administration. Importantly, the citizen is generally considered to be the ultimate “customer” of government activities regardless of the nature of the customer relationship.\nPRM volume 1, p.14".
- FEA_Model comment "1, the FEA is being constructed through a collection of interrelated\n“reference models” designed to facilitate cross-agency analysis and the identification of duplicative investments, gaps, and opportunities for collaboration within and across Federal Agencies.".
- GovernmentBody comment "Any US government organization".
- IT_Initiative comment "A program of work that implements information technology based capabilities.".
- IndustryBody comment "Any non government organization".
- Mission comment "Missions are carried out by the organizational entities".
- Partition comment "Each reference model has an extensional property based on partitioning. This reveals implicit semantics in each reference model.\n".
- ValuePoint comment "The point at which value is measured.".