You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Henry Story (JIRA)" <ji...@apache.org> on 2011/05/11 19:03:47 UTC
[jira] [Commented] (CLEREZZA-500) SchemaGen add instances to
classes
[ https://issues.apache.org/jira/browse/CLEREZZA-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031850#comment-13031850 ]
Henry Story commented on CLEREZZA-500:
--------------------------------------
This was solved in commit-1084739 and commit-1099381 which I forgot to tag properly in the comments.
http://svn.apache.org/viewvc?view=revision&revision=1084739
http://svn.apache.org/viewvc?view=revision&revision=1099381
> SchemaGen add instances to classes
> ----------------------------------
>
> Key: CLEREZZA-500
> URL: https://issues.apache.org/jira/browse/CLEREZZA-500
> Project: Clerezza
> Issue Type: New Feature
> Reporter: Henry Story
>
> Sometimes ontologies contain instances, and these also need to be used. An example are documents describing test suites using the EARL vocabulary. One such could be like this:
> @prefix earl: <http://www.w3.org/ns/earl#> .
> @prefix dct: <http://purl.org/dc/terms/> .
> @prefix : <>
> :profileGet a earl:TestRequirement;
> dct:title "WebId Profile is accessible and downloadable".
> :profileWF a earl:TestRequirement;
> dct:title "WebId Profile is well formed";
> dct:description "The WebId Profile is parseable Content and transformable to RDF" .
> here profileGet is not a class but an object. But it will be used by many services around the web, and will control program behaviors.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira