Data Portal @ linkeddatafragments.org

Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }

• sound comment "This object property has been mapped".
• street-address comment "The street address associated with the address of the object".
• tel comment "This object property has been mapped".
• title comment "To specify the position or job of the object".
• url comment "This object property has been mapped".
• Label comment "Super class of ISO ThesaurusTerm and of ISO NodeLabel.\n\nA ThesaurusTerm has mandatory attributes lexicalValue and identifier. lexicalValue can be mapped to skos xl:literalForm. The value of identifier can be used as the URI of the skos xl:Label or as the object of a dc:identifier statement on that skos-xl:Label.\nA NodeLabel has mandatory attributes lexicalValue.\n\nThe optional ISO25964 lang attribute of ThesaurusTerm and of NodeLabel must be mapped to RDF language tag for RDF plain literals.\n\nAttributes or associations not detailed below typically are mapped to dc: (or dct:) properties:\n- dct:created\n- dct:modified\n- dc:source".
• altLabel comment "Complex super property of ISO hasNonPreferredLabel\n\nApplies if the value of \"hasNonPreferredLabel\" is of class SimpleNonPreferredTerm with the Boolean attribute \"hidden\" either absent or with value false.".
• altLabel comment "If C skosxl:altLabel L and L skosxl:literalForm V, then X skos:altLabel V.".
• hiddenLabel comment "Complex super property of ISO hasNonPreferredLabel\n\nApplies if the value of \"hasNonPreferredLabel\" is of class SimpleNonPreferredTerm with the Boolean attribute \"hidden\" having value true.".
• hiddenLabel comment "If C skosxl:hiddenLabel L and L skosxl:literalForm V, then C skos:hiddenLabel V.".
• literalForm comment "If two instances of the class skosxl:Label have the same literal form, they are not necessarily the same resource.".
• literalForm comment "The range of skosxl:literalForm is the class of RDF plain literals.".
• prefLabel comment "Complex super property of ISO hasPreferredLabel\n\nWhen a label is represented as skos xl:Label, a skos:prefLabel statement is derived from the skos-xl:prefLabel one. (Likewise for altLabel and hiddenLabel.)".
• prefLabel comment "If C skosxl:prefLabel L and L skosxl:literalForm V, then X skos:prefLabel V.".
• content comment "Representing Content in RDF as defined by http://www.w3.org/TR/Content-in-RDF/".
• Content comment "The content.".
• ContentAsBase64 comment "The base64 encoded content (can be used for binary content).".
• ContentAsText comment "The text content (can be used for text content).".
• ContentAsXML comment "The XML content (can only be used for XML-wellformed content).".
• DoctypeDecl comment "The document type declaration.".
• http comment "A namespace for describing HTTP messages (http://www.w3.org/Protocols/rfc2616/rfc2616.html)".
• Connection comment "A connection used for HTTP transfer.".
• HeaderElement comment "A part of a deconstructed header value.".
• HeaderName comment "A header name.".
• Message comment "An HTTP message.".
• MessageHeader comment "A header in an HTTP message.".
• Method comment "The HTTP method used for the request.".
• Parameter comment "A parameter for a part of a header value.".
• Request comment "An HTTP request.".
• Response comment "An HTTP response.".
• StatusCode comment "The status code of an HTTP response.".
• requestURI comment "The request URI of an HTTP request.".
• food comment "Derived from the DAML Wine ontology at \n http://ontolingua.stanford.edu/doc/chimaera/ontologies/wines.daml\n Substantially modified.".
• wine comment "An example OWL ontology".
• wine comment "Derived from the DAML Wine ontology at \n http://ontolingua.stanford.edu/doc/chimaera/ontologies/wines.daml\n Substantially changed, in particular the Region based relations.".
• WineDescriptor comment "Made WineDescriptor unionType of tastes and color".
• adms comment "This file specifies the set of RDF classes and properties used in ADMS".
• Asset comment "An Asset is an abstract entity that reflects the intellectual content of the asset and represents those characteristics of the asset that are independent of its physical embodiment. This abstract entity combines the FRBR entities work (a distinct intellectual or artistic creation) and expression (the intellectual or artistic realization of a work). Assets can be versioned. Every time the intellectual content of an asset changes, the result is considered to be a new asset that can be linked to previous and next versions of the Asset. The physical embodiment of an Asset is called an Asset Distribution. A particular Asset may have zero or more Asset Distributions..".
• AssetDistribution comment "An Asset Distribution represents a particular physical embodiment of an Asset, which is an example of the FRBR entity manifestation (the physical embodiment of an expression of a work). An Asset Distribution is typically a downloadable computer file (but in principle it could also be a paper document) that implements the intellectual content of an Asset. A particular Asset Distribution is associated with one and only one Asset, while all Distributions of an Asset share the same intellectual content in different physical formats. Asset Distributions themselves are not versioned.".
• Identifier comment "The ADMS class of Identifier fully represents the Business Core Vocabulary term of the same name".
• Identifier comment "This class is based on the UN/CEFACT Identifier complex type defined in See Section 5.8 of Core Components Data Type Catalogue Version 3.1 (http://www.unece.org/fileadmin/DAM/cefact/codesfortrade/CCTS/CCTS-DTCatalogueVersion3p1.pdf) In RDF this is expressed using the following properties: - the content string should be provided using skos:notation, datatyped with the identifier scheme (inclduing the version number if appropriate); - use dcterms:creator to link to a class describing the agency that manages the identifier scheme or adms:schemaAgency to provide the name as a literal. Although not part of the ADMS conceptual model, it may be useful to provide further properties to the Identifier class such as dcterms:created to provide the date on which the identifier was issued.".
• identifier comment "adms:identifier is used to link any resource to an instance of adms:Identifier which is its range. N.B. it is not appropriate to use dcterms:identifer to link to the Identifier class as its range is rdfs:Literal. ADMS uses this to provide any identifier for the Asset.".
• Access comment "Any kind of access to a resource. Don't use this, use R W and RW".
• Append comment "Append accesses are specific write access which only add information, and do not remove information.\n For text files, for example, append access allows bytes to be added onto the end of the file.\n For RDF graphs, Append access allows adds triples to the graph but does not remove any.\n Append access is useful for dropbox functionality.\n Dropbox can be used for link notification, which the information added is a notification\n that a some link has been made elsewhere relevant to the given resource.".
• Authorization comment "An element of access control,\n allowing agent to agents access of some kind to resources or classes of resources".
• Read comment "The class of read operations".
• mode comment "A mode of access such as read or write.".
• cert comment "\n Ontology for Certificates and crypto stuff.\n This is in development. \n Some other ontologies to look at:\n * http://www.w3.org/2000/10/swap/crypto\n + has cwm builtins: http://www.w3.org/2000/10/swap/doc/Trust\n - a bit old perhaps. It imports daml+oil\n - would help to be more completely specified\n - uses literals as subjects a little liberally, which makes this a \n bit difficult to work with frameworks that don't permit this\n * http://xmlns.com/wot/0.1/\n - limited very much to PGP (though on can map PGP to X509)\n - a little coarse grained, mixes up the PGP certificate with the PGP\n public key\n *\n Todo: \n - add some classes and relations for DSA\n - should this all be in one file? Or should this be cut up a little? Say one file for the general CERT ontology, and then files for RSA, DSA, PGP, etc... Or perhaps it does not really matter?\n - expand more on the certification side of things\n - verify this by security experts\n - owl2 has some constructs for combined inverse functional properties. \n This may be useful to use in defining an RSA key which is identified\n by two numbers.\n - also create html version of the spec by using this as a template.\n - should comments such as this be in html?\n ".
• Certificate comment "A certificate is a Document that is signed.\n As explained here http://www.pgpi.org/doc/pgpintro/#p16\n 'A digital certificate consists of three things:\n * A public key.\n * Certificate information. ('Identity' information about the \n user, such as name, user ID, and so on.)\n * One or more digital signatures.'\n ".
• Key comment "the class of keys".
• PublicKey comment "Public Key".
• RSAKey comment "\n The union of the public and private components of an RSAKey.\n Usually those pieces are not kept together\n ".
• RSAPublicKey comment "\n The RSA public key. Padded message m are encrypted by applying the function\n modulus(power(m,exponent),modulus)\n ".
• identity comment "\n the identity of the public key. This is the entity that knows the private key and \n so can decrypt messages encrypted with the public key, or encrypt messages that can \n be decrypted with the public key. \n ".
• key comment "relates an agent to a key - most often the public key.".
• dcat comment "DCAT es un vocabulario RDF diseñado para facilitar la interoperabilidad entre catálogo de datos publicados en la Web.\n Gracias a utilizar DCAT para describir conjuntos de datos en los catálogo de datos, los editores aumentan el descubrimiento y permiten\n que las aplicaciones consuman fácilmente los metadatos de varios catálogos.".
• dcat comment "DCAT est un vocabulaire développé pour faciliter l'interopérabilité entre les jeux de données publiées sur le Web.\n\t\t\t\tEn utilisant DCAT pour décrire les jeux de données dans les catalogues de données, les fournisseurs de données augmentent leur découverte et permettent\n\t\t\t\tque les applications facilement les métadonnées de plusieurs catalogues. Il permet en plus la publication décentralisée des catalogues et facilitent\n\t\t\t\tla recherche fédérée des données entre plusieurs sites. Les métadonnées DCAT aggrégées peuvent servir comme un manifeste pour faciliter la préservation digitale des ressources.\n\t\t\t\tDCAT est définie à l'adresse http://www.w3.org/TR/vocab-dcat/. Une quelconque version de ce document normatif et ce vocabulaire est une erreur dans ce vocabulaire".
• dcat comment "DCAT is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web.\n By using DCAT to describe datasets in data catalogs, publishers increase discoverability and enable \n applications easily to consume metadata from multiple catalogs. It further enables decentralized \n publishing of catalogs and facilitates federated dataset search across sites. Aggregated DCAT metadata can \n serve as a manifest file to facilitate digital preservation.\n DCAT is defined at http://www.w3.org/TR/vocab-dcat/. Any variance between that normative\n document and this schema is an error in this schema.".
• dcat comment "DCATは、ウェブ上で公開されたデータ・カタログ間の相互運用性の促進を目的とするRDFの語彙です。このドキュメントでは、その利用のために、スキーマを定義し、例を提供します。\nデータ・カタログ内のデータセットを記述するためにDCATを用いると、公開者が、発見可能性を増加させ、アプリケーションが複数のカタログのメタデータを容易に利用できるようになります。さらに、カタログの分散公開を可能にし、複数のサイトにまたがるデータセットの統合検索を促進します。集約されたDCATメタデータは、ディジタル保存を促進するためのマニフェスト・ファイルとして使用できます。".
• dcat comment "Το DCAT είναι ένα RDF λεξιλόγιο που σχεδιάσθηκε για να κάνει εφικτή τη διαλειτουργικότητα μεταξύ καταλόγων δεδομένων στον Παγκόσμιο Ιστό.\n Χρησιμοποιώντας το DCAT για την περιγραφή συνόλων δεδομένων, οι εκδότες αυτών αυξάνουν την ανακαλυψιμότητα και επιτρέπουν στις εφαρμογές την εύκολη κατανάλωση μεταδεδομένων από πολλαπλούς καταλόγους.\n Επιπλέον, δίνει τη δυνατότητα για αποκεντρωμένη έκδοση και διάθεση καταλόγων και επιτρέπει δυνατότητες ενοποιημένης αναζήτησης μεταξύ διαφορετικών πηγών.\n Συγκεντρωτικά μεταδεδομένα που έχουν περιγραφεί με το DCAT μπορούν να χρησιμοποιηθούν σαν ένα δηλωτικό αρχείο (manifest file) ώστε να διευκολύνουν την ψηφιακή συντήρηση.".
• dcat comment "هي أنطولوجية تسهل تبادل البيانات بين مختلف الفهارس على الوب. استخدام هذه الأنطولوجية يساعد على اكتشاف قوائم البيانات المنشورة على الوب و يمكن التطبيقات المختلفة من الاستفادة أتوماتيكيا من البيانات المتاحة من مختلف الفهارس.".
• Catalog comment "A curated collection of metadata about datasets".
• Catalog comment "Una colección conservada de metadatos de conjuntos de datos".
• Catalog comment "Une collection élaborée de métadonnées sur les jeux de données".
• Catalog comment "Μια επιμελημένη συλλογή μεταδεδομένων περί συνόλων δεδομένων".
• Catalog comment "مجموعة من توصيفات قوائم البيانات".
• Catalog comment "データ・カタログは、データセットに関するキュレートされたメタデータの集合です。".
• CatalogRecord comment "1つのデータセットを記述したデータ・カタログ内のレコード。".
• CatalogRecord comment "A record in a data catalog, describing a single dataset.".
• CatalogRecord comment "Un registre du catalogue ou une entrée du catalogue, décrivant un seul jeu de données".
• CatalogRecord comment "Un registro en un catálogo de datos que describe un solo conjunto de datos.".
• CatalogRecord comment "Μία καταγραφή ενός καταλόγου, η οποία περιγράφει ένα συγκεκριμένο σύνολο δεδομένων.".
• Dataset comment "1つのエージェントによって公開またはキュレートされ、1つ以上の形式でアクセスまたはダウンロードできるデータの集合。".
• Dataset comment "A collection of data, published or curated by a single source, and available for access or download in one or more formats".
• Dataset comment "Una colección de datos, publicados o conservados por una única fuente, y disponibles para acceder o descagar en uno o más formatos".
• Dataset comment "Une collection de données, publiée ou élaborée par une seule source, et disponible pour accès ou téléchargement dans un ou plusieurs formats".
• Dataset comment "Μία συλλογή από δεδομένα, δημοσιευμένη ή επιμελημένη από μία και μόνο πηγή, διαθέσιμη δε προς πρόσβαση ή μεταφόρτωση σε μία ή περισσότερες μορφές".
• Dataset comment "قائمة بيانات منشورة أو مجموعة من قبل مصدر ما و متاح الوصول إليها أو تحميلها".
• Distribution comment "Representa una forma disponible y específica a un conjunto de datos. Cada conjunto de datos puede estar disponible en\n formas diferentes, estas formas pueden representar formatos diferentes del conjunto de datos o puntos de acceso diferentes.".
• Distribution comment "Represents a specific available form of a dataset. Each dataset might be available in \n different forms, these forms might represent different formats of the dataset or different \n endpoints. Examples of distributions include a downloadable CSV file, an API or an RSS feed".
• Distribution comment "Représente une forme spécifique d'un jeu de données. Caque jeu de données peut être disponible\n\t\t\t\t\tsous différentes formes, celles-ci pouvant représenter différents formats du jeu de données ou différents endpoint. Des exemples de distribution\n\t\t\t\t\tsont des fichirs CSV, des API ou des flux RSS.".
• Distribution comment "Αναπαριστά μία συγκεκριμένη διαθέσιμη μορφή ενός συνόλου δεδομένων. Κάθε σύνολο δεδομενων μπορεί να είναι διαθέσιμο σε \n\t\t\t\t\tδιαφορετικές μορφές, οι μορφές αυτές μπορεί να αναπαριστούν διαφορετικές μορφές αρχείων ή διαφορετικά σημεία διάθεσης.\n\t\t\t\t\tΠαραδείγματα διανομών συμπεριλαμβάνουν ένα μεταφορτώσιμο αρχείο μορφής CSV, ένα API ή ένα RSS feed.".
• Distribution comment "شكل محدد لقائمة البيانات يمكن الوصول إليه. قائمة بيانات ما يمكن أن تكون متاحه باشكال و أنواع متعددة. ملف يمكن تحميله أو واجهة برمجية يمكن من خلالها الوصول إلى البيانات هي أمثلة على ذلك.".
• Distribution comment "データセットの特定の利用可能な形式を表わします。各データセットは、異なる形式で利用できることがあり、これらの形式は、データセットの異なる形式や、異なるエンドポイントを表わす可能性があります。配信の例には、ダウンロード可能なCSVファイル、API、RSSフィードが含まれます。".
• core comment "A lightweight vocabulary for hypermedia-driven Web APIs".
• ApiDocumentation comment "The Hydra API documentation class".
• Class comment "The class of Hydra classes. Hydra classes and their instances are dereferenceable resources.".
• Collection comment "A collection holding references to a number of related resources.".
• IriTemplate comment "The class of IRI templates.".
• IriTemplateMapping comment "A mapping from an IRI template variable to a property.".
• Link comment "The class of properties representing links.".
• Operation comment "An operation.".
• PagedCollection comment "A PagedCollection is a subclass of Collection with the only difference that its members are sorted and only a subset of all members are returned in a single PagedCollection. To get the other members, the nextPage/previousPage properties have to be used.".
• Resource comment "The class of dereferenceable resources.".
• StatusCodeDescription comment "Additional information about a status code that might be returned.".
• SupportedProperty comment "A property known to be supported by a Hydra class.".
• TemplatedLink comment "A templated link.".
• ldp comment "This ontology provides an informal representation of the concepts and terms as defined in the LDP specification. Consult the LDP specification for normative reference.".
• Container comment "A Linked Data Platform RDF Source (LDP-RS) that also conforms to additional patterns and conventions for managing membership. Readers should refer to the specification defining this ontology for the list of behaviors associated with it.".
• RDFSource comment "A Linked Data Platform Resource (LDPR) whose state is represented as RDF.".

• first
• previous
• next