On 4/9/2011 4:15 PM, wenlei zhou wrote:
> Can I say that Music Ontology Just defined the vocabulary\schema of
> music entities?
Yeah, that is what a Semantic Web ontology typical does today. You can
treat such ontologies* like vocabularies/schemata. One advantage of
such publishes ontologies is that everyone can be able to use them if
they are available in public. In contrast, a database schema usually
is proprietary and often only used by one system that deploys that
schema. For that reason, e.g., every music metadata related service,
such as MusicBrainz, Discogs or AllMusic can make use of the Music
Ontology to deliver a kind of "shared understanding".
> On 9 April 2011 22:09, wenlei zhou <wenlei.zho...@gmail.com
> <mailto:wenlei.zho...@gmail.com>> wrote:
> Hi, Bob
> I know that the goal of Music ontology is to construct the knowledge
> of music entities. But Where is the knowledge data stored? Is the
> data stored as RDF type? If so, how can I get it?
Semantic Web data is typically store in a triple store , which
usually a specific graph database system. However, one can also store
these knowledge representations a mature relational database system by
using a specific database schema, e.g., that one from Jena .
Albeit, this mailing list is not really intended to clarify general
Semantic Web foundations. Therefore, you should maybe use of
appropriated literature (see, e.g., ) or q&a boards, such as
*) a more natural definition of ontology includes everything, i.e.,
vocabulary specifications and instance data (however, please don't be
confused from this point of view, and prefer the vocabulary-aligned
definition of 'ontology' for the beginning)