[OASIS Issue Tracker] (LEGALRULEML-12) XSLT for Phase 1+2 conversion from LegalRuleML to RDF

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Tara Athan commented on LEGALRULEML-12:
---------------------------------------

Fixed with commit https://tools.oasis-open.org/version-control/browse/wsvn/legalruleml/?rev=136&sc=1

> XSLT for Phase 1+2 conversion from LegalRuleML to RDF
> -----------------------------------------------------
>
>                 Key: LEGALRULEML-12
>                 URL: https://issues.oasis-open.org/browse/LEGALRULEML-12
>             Project: OASIS LegalRuleML TC
>          Issue Type: Improvement
>          Components: XSLT for conversion to RDF
>            Reporter: Tara Athan
>            Assignee: Tara Athan
>
>      This stylesheet generates valid RDF/XML if the input meets the preconditions.
>      There is no loss or ambiguity of information except:
>      1. Attributes other than @index on edge elements with child or text content will be ignored. This is the desired behavior- ideally, the normalization transformation will not generate such attributes.
>      2. The case of a Node element having a keyref attribute as well as other attributes or content is worked-around by transforming this to a "derivedFrom" child. In the case when properties are not functional, this is acceptable, but in case where properties are functional, this can lead to inconsistency. For example, a ruleml:content property for ruleml:Time is functional. If we keyreference another ruleml:Time and also have a ruleml:content child, then this should be interpreted as asserting the explicit ruleml:content property *instead of* the ruleml:content property of the original ruleml:Time. Therefore the consequences of a ruleml:derivedFrom property may be non-monotonic, and these consequences must be either determined in a third phase of the XSLT and incorporated into the final RDF output, or the assertion must be treated as an XML Literal.
> Input Preconditions
>   1. All CURIES have been processed into absolute IRIs
>      (e.g. using xslt as in https://apache.googlesource.com/stanbol/+/9b61625545e2ba6b903ea0752dcd20656bada822/enhancer/engines/xmpextractor/src/main/resources/xslt/rdfa.xslt)
>   2. The document is in the normalized form (e.g. after applying an XSLT normalizer.) including:
>       a. Collections may not be empty unless they have a keyref attribute.  



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