--
You received this message because you are subscribed to the Google Groups "akomantoso-xml" group.
To unsubscribe from this group and stop receiving emails from it, send an email to akomantoso-xm...@googlegroups.com.
To post to this group, send email to akomant...@googlegroups.com.
Visit this group at https://groups.google.com/group/akomantoso-xml.
To view this discussion on the web visit https://groups.google.com/d/msgid/akomantoso-xml/ea72cde8-776d-437a-99ab-c1545734b225%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/akomantoso-xml/CAEFAe-E1uRwuA9D82%2BiN6OLiFJXJNUdr2jL773LnC5W0k8aZew%40mail.gmail.com.
Hi,
thanks a lot!
We did know the subschema generator and also know the AKN4UN-Specification, but find that they are not really applicable to our case - do you know any other examples, possibly using schematron, too?
Kind regards
Olof
To view this discussion on the web visit https://groups.google.com/d/msgid/akomantoso-xml/0db7e1eed5df4095b1d6178ba6d1fba6%40init.de.
In attachment you can see the list of the use-cases and example bulks.
If you have more information about use-cases please add them in the file and resent it.
All the best,
Monica
-- =================================== Full 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.p...@unibo.it ====================================
Dear All,
dear Matt,
Thanks for the helpful insights into your project. Your use case sounds very similar to ours and we would appreciate the possibility to take a look at your work as soon as you’re ready to share.
In our context we want to implement both structural constraints (such as “a clause can contain either content or subclauses”) and content constraints (ie. logic based on attribute values). We’re currently considering two approaches to the formulation of these constraints:
Option A: All constraints asserted
Structural rules: XPath-based constraints (Schematron or XSD1.1 assertions)
Content rules: XPath-based constraints (Schematron or XSD1.1 assertions)
Validation: AKN-Schema and XPath-based ruleset for structure and content
Option B: Specified structures and asserted content
Structural rules: Custom XSD1.0 or XSD1.1 schema (overwriting AKN types)
Content rules: XPath-based Schematron rules in additions to custom XSD1.0 or constraints as XSD1.1 assertions within the same XSD1.1
Validation: AKN-schema and [custom XSD1.0 schema + Schematron rules] or AKN-schema and custom XSD1.1 schema
@Matt: From what I understand you’re pursuing option A, correct? We haven’t ruled out that option yet, but are a bit wary of the complexity involved in formulating (and maintaining) all our structural rules in a rule set free of contradictions. As we also intend to source a WYSIWYG-editor the issue of completion suggestions based on Schematron keeps cropping up.
@Fabio: Do you know of any XML-editors sufficiently Schematron-aware to offer completion suggestions based on Schematron/XPath-assertions?
Regards,
Olof