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


Help: OASIS Mailing Lists Help | MarkMail Help

legalruleml message

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

Subject: [OASIS Issue Tracker] (LEGALRULEML-20) Add two new elements <LegalReference> and <Source>

     [ https://issues.oasis-open.org/browse/LEGALRULEML-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tara Athan updated LEGALRULEML-20:

    Component/s: Examples-draft
                 RDFS metamodel
                 Relax NG-driver

> Add two new elements <LegalReference> and <Source>
> --------------------------------------------------
>                 Key: LEGALRULEML-20
>                 URL: https://issues.oasis-open.org/browse/LEGALRULEML-20
>             Project: OASIS LegalRuleML TC
>          Issue Type: Improvement
>          Components: Examples-approved, Examples-draft, RDFS metamodel, Relax NG-driver, Relax NG-modules, XSD schema, XSLT compactifier, XSLT for post-processing of schemas, XSLT for postprocessing generated instances, XSLT normalizer
>            Reporter: Tara Athan
>              Labels: Usability
> The existing Nodes LegalSource and Reference are, according to the Vocabulary, to be used only for referring to external *approved legal documents* or fragments thereof, and so cannot be used to define local identifiers for other sorts of external sources, e.g. a Rule in another LegalRuleML document.
> Rather than use internal xml:base attributes to change the base IRI for a relative IRI reference, and especially to avoid using non-IRI identifiers as if they were relative IRI references, it is better to create new elements, similar to the existing ones, for the purpose of defining such local identifiers.

This message was sent by Atlassian JIRA

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