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: Re: [legalruleml] [Repository for the examples]


Hi Tara,
On 12/07/2012, at 7:58 PM, Tara Athan wrote:

> I would like to propose a repository structure as follows:
>
> (following http://svn.apache.org/repos/asf/subversion/trunk/doc/user/svn-best-practices.html)
>
> 1. it is conventional to have a top level of
> lrm
>  |_branches
>  |_tags
>  |_trunk
>  where
> "trunk, meaning the directory under which the main project development occurs; branches, which is a directory in which to create various named branches of the main development line; tags, which is a directory of branches that are created, and perhaps destroyed, but never changed."

tags is often used for releases, so it might be appropriate for approved versions.

> 2. under "trunk" (and consequently under each branch or tag) I propose
> lrm
>  |_examples
>    |_draft
>    |_approved
>    |_sources
>  |_schemas
>    |_relaxng
>      |_modules
>    |_xsd
>      |_modules
>    |_schematron
>      |_modules
> |_xslt
>
> I suggest having separate directories for draft and approved examples so that we can develop, and keep a record of, alternate syntax proposals. However, the schemas will only be required to validate the examples in the "approved" directory.
>
> I also suggest that source examples (in xml, pdf, jpg, doc, etc) be kept in a parallel directory "sources", and that each of the directories draft, approved, sources, have a flat structure (no subdirectories).
>
> One reason is that it makes it easier for me to validate during schema development if I can point to the directory "approved" and know that it contains only the .lrml examples at the top level. Also, the same source could be used by several examples.

Do you also want to set us some coding conventions for XML files.

All the best

Guido

> Tara
>
> On 7/10/2012 4:42 PM, monica.palmirani wrote:
>> Dear all,
>>
>> as suggested by Harold it is a very good idea to have a versioning
>> system for a library of LegalRuleML XML examples.
>>
>> Please take a look to the following pages where you can find the SVN
>> tool provided by OASIS in order to discuss the issue tomorrow:
>> https://tools.oasis-open.org/
>> https://tools.oasis-open.org/version-control/browse/
>>
>> Yours,
>> Monica
>>
>> --
>> ===================================
>> Associate professor of Legal Informatics
>> School of Law
>> Alma Mater Studiorum Università di Bologna
>> C.I.R.S.F.I.D. http://www.cirsfid.unibo.it/
>> Palazzo Dal Monte Gaudenzi - Via Galliera, 3
>> I - 40121 BOLOGNA (ITALY)
>> Tel +39 051 277217
>> Fax +39 051 260782
>> E-mail  monica.palmirani@unibo.it
>> ====================================
>>
>>
>> LA RICERCA C’È E SI VEDE:
>> 5 per mille all'Università di Bologna - C.F.: 80007010376
>> http://www.unibo.it/5permille
>>
>> Questa informativa è inserita in automatico dal sistema al fine esclusivo della realizzazione dei fini istituzionali dell’ente.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: legalruleml-unsubscribe@lists.oasis-open.org
>> For additional commands, e-mail: legalruleml-help@lists.oasis-open.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legalruleml-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: legalruleml-help@lists.oasis-open.org
>

All the best

Guido
--
Prof Guido Governatori
Associate Education Director and Principal Researcher
Queensland Research Laboratory

NICTA | PO Box 6020 | St Lucia QLD 4067
T +61 7 33008523 | M +61 (0)400 934 738 | F +61 7 3300 8420
www.nicta.com.au | guido.governatori@nicta.com.au


The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.


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