Skip to content

Vocabulary for new semantic extensions #25

@dbooth-boston

Description

@dbooth-boston

"having a vocabulary and semantics for
forwards compatible introduction of new semantic extensions could be
nice too (imagine in worst case of compatibility a tool alert "The
loaded document uses OWL-23-XYZ features which are not supported. Do you
still wish to proceed?")."
https://lists.w3.org/Archives/Public/semantic-web/2018Nov/0172.html

"At present there is a minor gap in the RDF standards, in that there is no standard way for an RDF processor to recognize that a particular URI is intended to signal an opaque semantic extension: the knowledge of which URIs are intended to signal opaque semantic extensions must be externally supplied to the RDF processor. The RDF processor must magically know about them in advance. It cannot alert the user to the need for a new opaque semantic extension that was previously unknown. This gap could be addressed by defining a standard predicate, such as rdf2:requires, to explicitly indicate when a particular semantic extension is required."
http://dbooth.org/2010/ambiguity/paper.html#part3_2

"It would also fall out naturally from the RDF-with-Contexts
extension described in
https://www.w3.org/2011/rdf-wg/wiki/RDFwithContexts "
https://lists.w3.org/Archives/Public/semantic-web/2018Nov/0220.html

Metadata

Metadata

Assignees

No one assigned

    Labels

    Category: language featuresFor language features of RDF itself -- model and syntaxstandardsStandardization should address this

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions