OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (OSLCCORE-33) Extend ReSpec to generate Terms sections for specification documents from a common vocabulary file


    [ https://issues.oasis-open.org/browse/OSLCCORE-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60921#comment-60921 ] 

James Amsden commented on OSLCCORE-33:
--------------------------------------

Thanks Martin. I suspect that we won't make any ReSpec changes to be able to pull specific content out of the core-vocab.ttl document for a Terms setion in each multi-part specification. Rather I think we should encourage thinking about the Core vocabulary as a single unit, described in a single document, and only rely on the Constraints (i.e, resource shapes) to be covered in each individual specification - since different contexts could have different constraints.


> Extend ReSpec to generate Terms sections for specification documents from a common vocabulary file
> --------------------------------------------------------------------------------------------------
>
>                 Key: OSLCCORE-33
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-33
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>            Reporter: James Amsden
>            Assignee: James Amsden
>              Labels: ReSpec
>
> Currently each specification of the OSLC Core multi-part specifications has a Terms section that is generated by ReSpec from Turtle files that documents the vocabulary ontology for that section.
> However, OSLC core has a single namespace, and therefore requires a single ontology resource for the whole vocabulary, and the ability to render that ontology as an HTML page. 
> The OSLC Core TC decided to use one vocabulary document and extend ReSpec to generate the Terms sections for each multi-part specification from a list of classes and properties that should be included in that section.
> Specifically, for section with class="appendix", div section attribute data-include will refer to the complete OSLC Core vocabulary (vocab/core-vocab.ttl) and new property data-include-content will provide a list of classes and properties that should be included in the Terms section (based on the data-oninclude="vocabToSpec" value). ReSpec should then use these classes and properties to generate the vocabulary HTML content from the single core-vocab.ttl file.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]