xsltforms-support Mailing List for XSLTForms (Page 2)
Brought to you by:
alain-couthures
Menu
▾
▴
xsltforms-support — XSLTForms support list
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(6) |
Jun
(9) |
Jul
(16) |
Aug
(5) |
Sep
(43) |
Oct
(36) |
Nov
(58) |
Dec
(43) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(79) |
Feb
(81) |
Mar
(107) |
Apr
(93) |
May
(85) |
Jun
(54) |
Jul
(64) |
Aug
(54) |
Sep
(45) |
Oct
(53) |
Nov
(34) |
Dec
(77) |
| 2011 |
Jan
(56) |
Feb
(53) |
Mar
(52) |
Apr
(66) |
May
(44) |
Jun
(16) |
Jul
(28) |
Aug
(5) |
Sep
(15) |
Oct
(21) |
Nov
(51) |
Dec
(46) |
| 2012 |
Jan
(16) |
Feb
(38) |
Mar
(47) |
Apr
(45) |
May
(41) |
Jun
(41) |
Jul
(72) |
Aug
(17) |
Sep
(10) |
Oct
(16) |
Nov
(29) |
Dec
(30) |
| 2013 |
Jan
(25) |
Feb
(13) |
Mar
(20) |
Apr
(25) |
May
(34) |
Jun
(8) |
Jul
(12) |
Aug
(9) |
Sep
(21) |
Oct
(19) |
Nov
(6) |
Dec
(2) |
| 2014 |
Jan
(14) |
Feb
(8) |
Mar
(7) |
Apr
(13) |
May
(33) |
Jun
(13) |
Jul
(6) |
Aug
(5) |
Sep
(5) |
Oct
(34) |
Nov
(7) |
Dec
|
| 2015 |
Jan
(1) |
Feb
(6) |
Mar
(17) |
Apr
(12) |
May
(10) |
Jun
(18) |
Jul
(31) |
Aug
(9) |
Sep
(3) |
Oct
(6) |
Nov
(19) |
Dec
(1) |
| 2016 |
Jan
(18) |
Feb
(4) |
Mar
(13) |
Apr
(19) |
May
|
Jun
(17) |
Jul
(7) |
Aug
|
Sep
(3) |
Oct
(6) |
Nov
(3) |
Dec
|
| 2017 |
Jan
(5) |
Feb
(17) |
Mar
(4) |
Apr
(8) |
May
(3) |
Jun
|
Jul
(8) |
Aug
(2) |
Sep
|
Oct
(5) |
Nov
(6) |
Dec
(4) |
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
|
Dec
(1) |
| 2019 |
Jan
|
Feb
|
Mar
(4) |
Apr
(2) |
May
(4) |
Jun
|
Jul
|
Aug
(2) |
Sep
(7) |
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
(13) |
Feb
(17) |
Mar
(8) |
Apr
(11) |
May
(15) |
Jun
(11) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
| 2021 |
Jan
(9) |
Feb
(26) |
Mar
(17) |
Apr
|
May
(7) |
Jun
(18) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(10) |
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(2) |
Sep
(3) |
Oct
(2) |
Nov
(10) |
Dec
(1) |
| 2023 |
Jan
(10) |
Feb
|
Mar
(7) |
Apr
(8) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(8) |
Oct
(11) |
Nov
(8) |
Dec
(5) |
| 2024 |
Jan
(7) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
(4) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Richard L. <ric...@gm...> - 2023-11-22 18:59:38
|
Hi, I have an XForms scenario where I am interacting with an API, so every item of data is fetched via a URL. I want to start with the selection of a file. That's straightforward, because I can quote the complete URL to get a list of possible values: The problem occurs when I then want to include the selected file name in the URL for the next stage of the query, which is to select the index to search. This is the sort of thing I would do in XSLT, using an AVT: What is the equivalent XForms/XsltForms syntax for including an entered value within a string? Thanks, Richard -- ------------------------------------------------------------------------ *Richard Light* ric...@gm... /@richardofsussex/ |
|
From: Richard L. <ric...@gm...> - 2023-11-21 17:51:28
|
Hi,
I have a grid control record which looks like this:
I want to use XForms to generate an editable grid of values, where each
row has values for a record which the user has selected. I can use
xf:repeat to output the headings:
and I then want to iterate over the selected records, and for each
record iterate over the <column> elements in the grid control record,
applying each column's @select attribute to the current record:
This requires two things I don't know how to do (one or both of which
may be impossible):
* pass a reference to the current Object node from the outer xf:repeat
into the inner xf:repeat
* /apply /the @select XPath to this Object node, rather than just
outputting its value
There are some other little challenges to overcome - my table row [of
headings] is coming out as a vertical list, and my record selection area
is blank - but it's only worth addressing these if the general strategy
has some hope of success.
Thanks in advance for any help you can offer,
Richard
--
------------------------------------------------------------------------
*Richard Light*
ric...@gm...
/@richardofsussex/ |
|
From: Mark S. <m_s...@ma...> - 2023-11-21 10:31:13
|
Hi again, I just noticed that if I just run instance() for the node whose value is set by the select1 from the debug command line, the dropdown select1 refreshes and works normally. Mark > On 21 Nov 2023, at 09:23, Mark Seaborne <m_s...@ma...> wrote: > > Hi, > > I have recently noticed that select1 as a dropdown list doesn't quite work in iPad browsers with XSLTForms 1.7 (using iPadOS 17.1.1). > > Where the node bound to the selected value starts empty, an initial selection works. However, the empty value row of the dropdown list isn't removed after the initial selection, which messes up the mapping between the index of the selected node in the itemset and the selected row of the dropdown list. > > The attached form can be used to demonstrate the problem on an iPad. Interestingly the form works fine on my old iPhone (iOS 15.8). > > My understanding is that all iPad Web browsers are built on WebKit and certainly those that I have tried (Vivaldi and Firefox) show the same behaviour. > > Best wishes > > Mark > > <select1.xml> > > > |
|
From: Mark S. <m_s...@ma...> - 2023-11-21 09:23:11
|
Hi, I have recently noticed that select1 as a dropdown list doesn't quite work in iPad browsers with XSLTForms 1.7 (using iPadOS 17.1.1). Where the node bound to the selected value starts empty, an initial selection works. However, the empty value row of the dropdown list isn't removed after the initial selection, which messes up the mapping between the index of the selected node in the itemset and the selected row of the dropdown list. The attached form can be used to demonstrate the problem on an iPad. Interestingly the form works fine on my old iPhone (iOS 15.8). My understanding is that all iPad Web browsers are built on WebKit and certainly those that I have tried (Vivaldi and Firefox) show the same behaviour. Best wishes Mark |
|
From: Alain C. <ala...@ag...> - 2023-10-17 18:41:36
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Hello Tony,
</div>
<div class="default-style">
</div>
<div class="default-style">
It might be possible to add support of Schematron in XSLTForms, transposing rules into constraints with Javascript and DOM.
</div>
<div class="default-style">
</div>
<div class="default-style">
XPath 3.1 support in XSLTForms will not be available before 2.0. Is XPath 1.0 a problem?
</div>
<div class="default-style">
</div>
<div class="default-style">
Do you have some examples for me to evaluate this more precisely?
</div>
<div class="default-style">
</div>
<div class="default-style">
Thank you in advance
</div>
<div class="default-style">
</div>
<div class="default-style">
--Alain
</div>
<blockquote type="cite">
<div>
Le 16/10/2023 22:33 CEST, ajb...@aj... a écrit :
</div>
<div>
</div>
<div>
</div>
<div class="WordSection1">
<p class="MsoNormal">Hello Alain,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">How does XSLTForms handle schematron within schemata, whether it is inline or referenced as an external file?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">As far as I can tell, I would have to parse all schematron separately and then try to fit the reflected business rules within @constraint attributes.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">If schematron is not handled out-of-the-box by XSLTForms, can you point me to any already-established alternatives that will work with your framework?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks Again,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">-Tony Bufort</p>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"> </p>
<table class="MsoNormalTable" border="0" cellpadding="0">
<tbody>
<tr>
<td style="border: solid red 1.0pt; border-left: none; padding: .75pt 5.25pt .75pt .75pt;"> <p class="MsoNormal"><span style="font-family: 'Arial',sans-serif;"><img id="Picture_x0020_26" style="width: 1.6354in; height: .875in;" src="cid:image001.png@01DA0035.5D95DC60" alt="ttp://www.ajbconsulting.us/images/outlook/AJB_Consulting_new_logo_OUTLOOK_SIGNATURE.png" width="157" height="84"></span></p> <p class="MsoNormal"><span style="font-family: Courier;"><a href="http://www.ajbconsulting.us/">www.ajbconsulting.us</a></span></p> </td>
<td style="border: solid red 1.0pt; border-right: none; padding: .75pt .75pt .75pt 3.75pt;"> <p class="MsoNormal"><span style="font-size: 12.0pt; font-family: 'Arial',sans-serif;"> <strong>Anthony J. (Tony) Bufort</strong><br> </span><em><span style="font-family: 'Arial',sans-serif;">Owner / Sr. Developer</span></em></p>
<table class="MsoNormalTable" border="0" cellpadding="0">
<tbody>
<tr>
<td style="padding: .75pt .75pt .75pt .75pt;"> <p class="MsoNormal"><span style="font-size: 9.0pt;"><img id="Picture_x0020_27" style="width: .1666in; height: .1666in;" src="cid:image002.png@01DA0035.5D95DC60" alt="ttp://www.ajbconsulting.us/images/outlook/icons/email.png" width="16" height="16" border="0"></span></p> </td>
<td style="padding: .75pt .75pt .75pt .75pt;"> <p class="MsoNormal"><strong><span style="font-size: 9.0pt;">EMAIL:</span></strong><span style="font-size: 9.0pt;"> <a>ajb...@aj...</a></span></p> </td>
</tr>
<tr>
<td style="padding: .75pt .75pt .75pt .75pt;"> <p class="MsoNormal"><span style="font-size: 9.0pt;"><img id="Picture_x0020_28" style="width: .1666in; height: .1666in;" src="cid:image003.png@01DA0035.5D95DC60" alt="ttp://www.ajbconsulting.us/images/outlook/icons/phone.png" width="16" height="16" border="0"></span></p> </td>
<td style="padding: .75pt .75pt .75pt .75pt;"> <p class="MsoNormal"><strong><span style="font-size: 9.0pt;">PHONE:</span></strong><span style="font-size: 9.0pt;"> (425) 221-4447</span></p> </td>
</tr>
<tr>
<td style="padding: .75pt .75pt .75pt .75pt;"> <p class="MsoNormal"><span style="font-size: 9.0pt;"><img id="Picture_x0020_29" style="width: .1666in; height: .1666in;" src="cid:image004.png@01DA0035.5D95DC60" alt="ttp://www.ajbconsulting.us/images/outlook/icons/skype.png" width="16" height="16" border="0"></span></p> </td>
<td style="padding: .75pt .75pt .75pt .75pt;"> <p class="MsoNormal"><strong><span style="font-size: 9.0pt;">SKYPE:</span></strong><span style="font-size: 9.0pt;"> ajbufort</span></p> </td>
</tr>
<tr>
<td style="padding: .75pt .75pt .75pt .75pt;"> <p class="MsoNormal"><span style="font-size: 9.0pt;"><img id="Picture_x0020_30" style="width: .1666in; height: .1666in;" src="cid:image005.png@01DA0035.5D95DC60" alt="ttp://www.ajbconsulting.us/images/outlook/icons/linkedin.png" width="16" height="16" border="0"></span></p> </td>
<td style="padding: .75pt .75pt .75pt .75pt;"> <p class="MsoNormal"><strong><span style="font-size: 9.0pt;">LINKEDIN:</span></strong><span style="font-size: 9.0pt;"> <a href="http://www.linkedin.com/in/anthonybufort">www.linkedin.com/in/anthonybufort</a></span></p> </td>
</tr>
</tbody>
</table> </td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="display: none;"> </span></p>
<table class="MsoNormalTable" style="border: none; border-bottom: solid red 1.0pt;" border="1" cellpadding="0">
<tbody>
<tr>
<td style="border: none; padding: 3.0pt .75pt .75pt .75pt;"> <p class="MsoNormal"><span style="font-size: 9.0pt; font-family: 'Arial',sans-serif;"> <img id="Picture_x0020_31" style="width: .3958in; height: .2604in;" src="cid:image006.jpg@01DA0035.5D95DC60" alt="ttp://www.ajbconsulting.us/images/outlook/wa_state_seal_sm.jpg" width="38" height="25" border="0"></span></p> </td>
<td style="border: none; padding: 3.0pt .75pt .75pt .75pt;"> <p class="MsoNormal"><span style="font-size: 9.0pt; font-family: 'Arial',sans-serif;"> A <strong><em>fully licensed, fully insured</em></strong> Washington state entity. </span></p> </td>
</tr>
</tbody>
</table>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
</div>
</blockquote>
</body>
</html> |
|
From: <ajb...@aj...> - 2023-10-16 20:34:01
|
Hello Alain, How does XSLTForms handle schematron within schemata, whether it is inline or referenced as an external file? As far as I can tell, I would have to parse all schematron separately and then try to fit the reflected business rules within @constraint attributes. If schematron is not handled out-of-the-box by XSLTForms, can you point me to any already-established alternatives that will work with your framework? Thanks Again, -Tony Bufort www.ajbconsulting.us <http://www.ajbconsulting.us/> Anthony J. (Tony) Bufort Owner / Sr. Developer EMAIL: ajb...@aj... <email:ajb...@aj...> PHONE: (425) 221-4447 SKYPE: ajbufort LINKEDIN: www.linkedin.com/in/anthonybufort <http://www.linkedin.com/in/anthonybufort> A fully licensed, fully insured Washington state entity. |
|
From: <ajb...@aj...> - 2023-10-16 20:27:43
|
Hi Alain, Your new code is now tested and confirmed working on my end. Thank you for this speedy attention and resolution! OSCAL and XForms have a bright future together. 😊 Attending Declarative Amsterdam, hope to see you there. -Tony Bufort www.ajbconsulting.us <http://www.ajbconsulting.us/> Anthony J. (Tony) Bufort Owner / Sr. Developer EMAIL: ajb...@aj... <email:ajb...@aj...> PHONE: (425) 221-4447 SKYPE: ajbufort LINKEDIN: www.linkedin.com/in/anthonybufort <http://www.linkedin.com/in/anthonybufort> A fully licensed, fully insured Washington state entity. From: ajb...@aj... <ajb...@aj...> Sent: Monday, October 16, 2023 11:41 AM To: 'Alain Couthures' <ala...@ag...>; 'Steven Pemberton' <ste...@cw...>; 'xsl...@li...' <xsl...@li...> Subject: RE: [Xsltforms-support] Question Re Implementing Custom Types Alain – FANTASTIC, thank you! I will test and get back to you ASAP. 😊 -Tony Bufort www.ajbconsulting.us <http://www.ajbconsulting.us/> Anthony J. (Tony) Bufort Owner / Sr. Developer EMAIL: ajb...@aj... <email:ajb...@aj...> PHONE: (425) 221-4447 SKYPE: ajbufort LINKEDIN: www.linkedin.com/in/anthonybufort <http://www.linkedin.com/in/anthonybufort> A fully licensed, fully insured Washington state entity. From: Alain Couthures <ala...@ag... <mailto:ala...@ag...> > Sent: Sunday, October 15, 2023 1:10 AM To: ajb...@aj... <mailto:ajb...@aj...> ; Steven Pemberton <ste...@cw... <mailto:ste...@cw...> >; xsl...@li... <mailto:xsl...@li...> Subject: Re: [Xsltforms-support] Question Re Implementing Custom Types Hello Tony, I have fixed some issues for supporting OSCAL schema. Please give a try to the xsltforms.js file attached. Thank you for your feedback! --Alain Steve, Alain, et al, Thanks for the quick replies. 😊 Alright, so I am using the OSCAL complete schema, v 1.1.0, along with an SSP instance (see attached). Though the instance is an SSP, I have started testing using the complete schema, as I am testing other aspects of my code in the process. In the resultant HTML, I get output like this: …so things are getting found and displayed, but I am not getting any validation or date-picker goodness. In my previous bind I sent you, I slimmed it down for purposes of brevity. Here is the actual bind… <xf:bind id="/system-security-plan/metadata/published" ref="/o:system-security-plan/o:metadata/o:published" type="oscal-metadata-published-FIELD"/> My expectation is that XSLTForms would find the type and its restriction base, follow that to the underlying type (DateTimeWithTimezoneDatatype), then follow its underlying type (DateTimeDatatype) to <xs:restriction base="xs:dateTime">, acknowledging the native type and allowing for both a rendering of a date-picker in the browser (Opera latest version in my case) and validation benefits within the resultant XForm. Thank you for considering my problem. -Tony <http://www.ajbconsulting.us/> www.ajbconsulting.us Anthony J. (Tony) Bufort Owner / Sr. Developer EMAIL: ajb...@aj... <mailto:ajb...@aj...> PHONE: (425) 221-4447 SKYPE: ajbufort LINKEDIN: <http://www.linkedin.com/in/anthonybufort> www.linkedin.com/in/anthonybufort A fully licensed, fully insured Washington state entity. From: Steven Pemberton <ste...@cw... <mailto:ste...@cw...> > Sent: Friday, October 6, 2023 1:11 AM To: ajb...@aj... <mailto:ajb...@aj...> ; xsl...@li... <mailto:xsl...@li...> Subject: Re: [Xsltforms-support] Question Re Implementing Custom Types Could you show us the instance you are referencing? Steven On Friday 06 October 2023 06:45:05 (+02:00), ajb...@aj... <mailto:ajb...@aj...> wrote: Hello Alain and Company, I am a new user of XSLTForms, exploring the framework, and am quite impressed, especially considering it’s a free product. However, I would like confirmation that what I am seeing is indeed the case, or if I am missing something, regarding handling custom types. In my model definition I reference a schema file, expecting to link up the types defined therein to my bind statements. The types I am trying to use are simpleTypes. Here is an example: <xs:simpleType name="DateTimeWithTimezoneDatatype"> <xs:annotation> <xs:documentation>A string representing a point in time with a required timezone.</xs:documentation> </xs:annotation> <xs:restriction base="DateTimeDatatype"> <xs:pattern value="(((2000|2400|2800|(19|2[0-9](0[48]|[2468][048]|[13579][26])))-02-29)|(((19|2[0-9])[0-9]{2})-02-(0[1-9]|1[0-9]|2[0-8]))|(((19|2[0-9])[0-9]{2})-(0[13578]|10|12)-(0[1-9]|[12][0-9]|3[01]))|(((19|2[0-9])[0-9]{2})-(0[469]|11)-(0[1-9]|[12][0-9]|30)))T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])(\.[0-9]+)?(Z|(-((0[0-9]|1[0-2]):00|0[39]:30)|\+((0[0-9]|1[0-4]):00|(0[34569]|10):30|(0[58]|12):45)))"/> </xs:restriction> </xs:simpleType> And the bind trying to use it (the ‘o:’ namespace used in @ref is indeed confirmed correct): <xf:bind id="/published" ref="/o:published" type=" DateTimeWithTimezoneDatatype"/> And finally, the input field: <xf:input bind="/published" incremental="true" type-ref=" DateTimeWithTimezoneDatatype"> <xf:label> <b>Published:</b> </xf:label> </xf:input> I get no ostensible complaints from the xf processor, but no validation behavior either (i.e. entering invalid values provokes no response). (Note that the slashes in the @id and @bind attributes seem to be permissible if non-standard.) Can the XSLTForms processor handle the schema type as defined above? It seems to acknowledge the type, but not operate using it. Or are users expected to create type-handling additions in xsltforms.js? I am unclear as to the situation in XSLTForms 1.7, which is the version I am using. Please advise, and thank you in advance! -Tony Bufort, AJB Consulting <http://www.ajbconsulting.us/> www.ajbconsulting.us Anthony J. (Tony) Bufort Owner / Sr. Developer EMAIL: ajb...@aj... <mailto:ajb...@aj...> PHONE: (425) 221-4447 SKYPE: ajbufort LINKEDIN: <http://www.linkedin.com/in/anthonybufort> www.linkedin.com/in/anthonybufort A fully licensed, fully insured Washington state entity. _______________________________________________ Xsltforms-support mailing list Xsl...@li... <mailto:Xsl...@li...> https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: <ajb...@aj...> - 2023-10-16 18:50:07
|
Alain – FANTASTIC, thank you! I will test and get back to you ASAP. 😊 -Tony Bufort www.ajbconsulting.us <http://www.ajbconsulting.us/> Anthony J. (Tony) Bufort Owner / Sr. Developer EMAIL: ajb...@aj... <email:ajb...@aj...> PHONE: (425) 221-4447 SKYPE: ajbufort LINKEDIN: www.linkedin.com/in/anthonybufort <http://www.linkedin.com/in/anthonybufort> A fully licensed, fully insured Washington state entity. From: Alain Couthures <ala...@ag...> Sent: Sunday, October 15, 2023 1:10 AM To: ajb...@aj...; Steven Pemberton <ste...@cw...>; xsl...@li... Subject: Re: [Xsltforms-support] Question Re Implementing Custom Types Hello Tony, I have fixed some issues for supporting OSCAL schema. Please give a try to the xsltforms.js file attached. Thank you for your feedback! --Alain Steve, Alain, et al, Thanks for the quick replies. 😊 Alright, so I am using the OSCAL complete schema, v 1.1.0, along with an SSP instance (see attached). Though the instance is an SSP, I have started testing using the complete schema, as I am testing other aspects of my code in the process. In the resultant HTML, I get output like this: …so things are getting found and displayed, but I am not getting any validation or date-picker goodness. In my previous bind I sent you, I slimmed it down for purposes of brevity. Here is the actual bind… <xf:bind id="/system-security-plan/metadata/published" ref="/o:system-security-plan/o:metadata/o:published" type="oscal-metadata-published-FIELD"/> My expectation is that XSLTForms would find the type and its restriction base, follow that to the underlying type (DateTimeWithTimezoneDatatype), then follow its underlying type (DateTimeDatatype) to <xs:restriction base="xs:dateTime">, acknowledging the native type and allowing for both a rendering of a date-picker in the browser (Opera latest version in my case) and validation benefits within the resultant XForm. Thank you for considering my problem. -Tony <http://www.ajbconsulting.us/> www.ajbconsulting.us Anthony J. (Tony) Bufort Owner / Sr. Developer EMAIL: ajb...@aj... <mailto:ajb...@aj...> PHONE: (425) 221-4447 SKYPE: ajbufort LINKEDIN: <http://www.linkedin.com/in/anthonybufort> www.linkedin.com/in/anthonybufort A fully licensed, fully insured Washington state entity. From: Steven Pemberton <ste...@cw... <mailto:ste...@cw...> > Sent: Friday, October 6, 2023 1:11 AM To: ajb...@aj... <mailto:ajb...@aj...> ; xsl...@li... <mailto:xsl...@li...> Subject: Re: [Xsltforms-support] Question Re Implementing Custom Types Could you show us the instance you are referencing? Steven On Friday 06 October 2023 06:45:05 (+02:00), ajb...@aj... <mailto:ajb...@aj...> wrote: Hello Alain and Company, I am a new user of XSLTForms, exploring the framework, and am quite impressed, especially considering it’s a free product. However, I would like confirmation that what I am seeing is indeed the case, or if I am missing something, regarding handling custom types. In my model definition I reference a schema file, expecting to link up the types defined therein to my bind statements. The types I am trying to use are simpleTypes. Here is an example: <xs:simpleType name="DateTimeWithTimezoneDatatype"> <xs:annotation> <xs:documentation>A string representing a point in time with a required timezone.</xs:documentation> </xs:annotation> <xs:restriction base="DateTimeDatatype"> <xs:pattern value="(((2000|2400|2800|(19|2[0-9](0[48]|[2468][048]|[13579][26])))-02-29)|(((19|2[0-9])[0-9]{2})-02-(0[1-9]|1[0-9]|2[0-8]))|(((19|2[0-9])[0-9]{2})-(0[13578]|10|12)-(0[1-9]|[12][0-9]|3[01]))|(((19|2[0-9])[0-9]{2})-(0[469]|11)-(0[1-9]|[12][0-9]|30)))T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])(\.[0-9]+)?(Z|(-((0[0-9]|1[0-2]):00|0[39]:30)|\+((0[0-9]|1[0-4]):00|(0[34569]|10):30|(0[58]|12):45)))"/> </xs:restriction> </xs:simpleType> And the bind trying to use it (the ‘o:’ namespace used in @ref is indeed confirmed correct): <xf:bind id="/published" ref="/o:published" type=" DateTimeWithTimezoneDatatype"/> And finally, the input field: <xf:input bind="/published" incremental="true" type-ref=" DateTimeWithTimezoneDatatype"> <xf:label> <b>Published:</b> </xf:label> </xf:input> I get no ostensible complaints from the xf processor, but no validation behavior either (i.e. entering invalid values provokes no response). (Note that the slashes in the @id and @bind attributes seem to be permissible if non-standard.) Can the XSLTForms processor handle the schema type as defined above? It seems to acknowledge the type, but not operate using it. Or are users expected to create type-handling additions in xsltforms.js? I am unclear as to the situation in XSLTForms 1.7, which is the version I am using. Please advise, and thank you in advance! -Tony Bufort, AJB Consulting <http://www.ajbconsulting.us/> www.ajbconsulting.us Anthony J. (Tony) Bufort Owner / Sr. Developer EMAIL: ajb...@aj... <mailto:ajb...@aj...> PHONE: (425) 221-4447 SKYPE: ajbufort LINKEDIN: <http://www.linkedin.com/in/anthonybufort> www.linkedin.com/in/anthonybufort A fully licensed, fully insured Washington state entity. _______________________________________________ Xsltforms-support mailing list Xsl...@li... <mailto:Xsl...@li...> https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Steven P. <ste...@cw...> - 2023-10-16 14:49:22
|
I hope you'll excuse a bit of spam. Nov 2/3 is the Declarative Amsterdam conference, where there will be at least three presentations that include XForms - Advanced XForms Tutorial - XForms current developments (describing the changes coming in the next version) - A Declarative Code Browser with ixml and XForms The conference is hybrid: both live, and streamed online. https://declarative.amsterdam/ Best wishes, Steven Pemberton |
|
From: <ajb...@aj...> - 2023-10-06 17:48:34
|
Steve, Alain, et al,
Thanks for the quick replies. 😊
Alright, so I am using the OSCAL complete schema, v 1.1.0, along with an SSP instance (see attached).
Though the instance is an SSP, I have started testing using the complete schema, as I am testing other aspects of my code in the process.
In the resultant HTML, I get output like this:
…so things are getting found and displayed, but I am not getting any validation or date-picker goodness.
In my previous bind I sent you, I slimmed it down for purposes of brevity. Here is the actual bind…
<xf:bind id="/system-security-plan/metadata/published"
ref="/o:system-security-plan/o:metadata/o:published"
type="oscal-metadata-published-FIELD"/>
My expectation is that XSLTForms would find the type and its restriction base, follow that to the underlying type (DateTimeWithTimezoneDatatype), then follow its underlying type (DateTimeDatatype) to <xs:restriction base="xs:dateTime">, acknowledging the native type and allowing for both a rendering of a date-picker in the browser (Opera latest version in my case) and validation benefits within the resultant XForm.
Thank you for considering my problem.
-Tony
<http://www.ajbconsulting.us/> www.ajbconsulting.us
Anthony J. (Tony) Bufort
Owner / Sr. Developer
EMAIL: <email:ajb...@aj...> ajb...@aj...
PHONE: (425) 221-4447
SKYPE: ajbufort
LINKEDIN: <http://www.linkedin.com/in/anthonybufort> www.linkedin.com/in/anthonybufort
A fully licensed, fully insured Washington state entity.
From: Steven Pemberton <ste...@cw...>
Sent: Friday, October 6, 2023 1:11 AM
To: ajb...@aj...; xsl...@li...
Subject: Re: [Xsltforms-support] Question Re Implementing Custom Types
Could you show us the instance you are referencing?
Steven
On Friday 06 October 2023 06:45:05 (+02:00), ajb...@aj... <mailto:ajb...@aj...> wrote:
Hello Alain and Company,
I am a new user of XSLTForms, exploring the framework, and am quite impressed, especially considering it’s a free product.
However, I would like confirmation that what I am seeing is indeed the case, or if I am missing something, regarding handling custom types.
In my model definition I reference a schema file, expecting to link up the types defined therein to my bind statements. The types I am trying to use are simpleTypes. Here is an example:
<xs:simpleType name="DateTimeWithTimezoneDatatype">
<xs:annotation>
<xs:documentation>A string representing a point in time with a required timezone.</xs:documentation>
</xs:annotation>
<xs:restriction base="DateTimeDatatype">
<xs:pattern value="(((2000|2400|2800|(19|2[0-9](0[48]|[2468][048]|[13579][26])))-02-29)|(((19|2[0-9])[0-9]{2})-02-(0[1-9]|1[0-9]|2[0-8]))|(((19|2[0-9])[0-9]{2})-(0[13578]|10|12)-(0[1-9]|[12][0-9]|3[01]))|(((19|2[0-9])[0-9]{2})-(0[469]|11)-(0[1-9]|[12][0-9]|30)))T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])(\.[0-9]+)?(Z|(-((0[0-9]|1[0-2]):00|0[39]:30)|\+((0[0-9]|1[0-4]):00|(0[34569]|10):30|(0[58]|12):45)))"/>
</xs:restriction>
</xs:simpleType>
And the bind trying to use it (the ‘o:’ namespace used in @ref is indeed confirmed correct):
<xf:bind id="/published" ref="/o:published" type=" DateTimeWithTimezoneDatatype"/>
And finally, the input field:
<xf:input bind="/published" incremental="true" type-ref=" DateTimeWithTimezoneDatatype">
<xf:label>
<b>Published:</b>
</xf:label>
</xf:input>
I get no ostensible complaints from the xf processor, but no validation behavior either (i.e. entering invalid values provokes no response).
(Note that the slashes in the @id and @bind attributes seem to be permissible if non-standard.)
Can the XSLTForms processor handle the schema type as defined above? It seems to acknowledge the type, but not operate using it.
Or are users expected to create type-handling additions in xsltforms.js?
I am unclear as to the situation in XSLTForms 1.7, which is the version I am using.
Please advise, and thank you in advance!
-Tony Bufort,
AJB Consulting
<http://www.ajbconsulting.us/> www.ajbconsulting.us
Anthony J. (Tony) Bufort
Owner / Sr. Developer
EMAIL: <email:ajb...@aj...> ajb...@aj...
PHONE: (425) 221-4447
SKYPE: ajbufort
LINKEDIN: <http://www.linkedin.com/in/anthonybufort> www.linkedin.com/in/anthonybufort
A fully licensed, fully insured Washington state entity.
|
|
From: Steven P. <ste...@cw...> - 2023-10-06 08:11:10
|
Could you show us the instance you are referencing?
Steven
On Friday 06 October 2023 06:45:05 (+02:00), ajb...@aj... wrote:
Hello Alain and Company,
I am a new user of XSLTForms, exploring the framework, and am quite impressed, especially considering it’s a free product.
However, I would like confirmation that what I am seeing is indeed the case, or if I am missing something, regarding handling custom types.
In my model definition I reference a schema file, expecting to link up the types defined therein to my bind statements. The types I am trying to use are simpleTypes. Here is an example:
<xs:simpleType name="DateTimeWithTimezoneDatatype">
<xs:annotation>
<xs:documentation>A string representing a point in time with a required timezone.</xs:documentation>
</xs:annotation>
<xs:restriction base="DateTimeDatatype">
<xs:pattern value="(((2000|2400|2800|(19|2[0-9](0[48]|[2468][048]|[13579][26])))-02-29)|(((19|2[0-9])[0-9]{2})-02-(0[1-9]|1[0-9]|2[0-8]))|(((19|2[0-9])[0-9]{2})-(0[13578]|10|12)-(0[1-9]|[12][0-9]|3[01]))|(((19|2[0-9])[0-9]{2})-(0[469]|11)-(0[1-9]|[12][0-9]|30)))T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])(\.[0-9]+)?(Z|(-((0[0-9]|1[0-2]):00|0[39]:30)|\+((0[0-9]|1[0-4]):00|(0[34569]|10):30|(0[58]|12):45)))"/>
</xs:restriction>
</xs:simpleType>
And the bind trying to use it (the ‘o:’ namespace used in @ref is indeed confirmed correct):
<xf:bind id="/published" ref="/o:published" type=" DateTimeWithTimezoneDatatype"/>
And finally, the input field:
<xf:input bind="/published" incremental="true" type-ref=" DateTimeWithTimezoneDatatype">
<xf:label>
<b>Published:</b>
</xf:label>
</xf:input>
I get no ostensible complaints from the xf processor, but no validation behavior either (i.e. entering invalid values provokes no response).
(Note that the slashes in the @id and @bind attributes seem to be permissible if non-standard.)
Can the XSLTForms processor handle the schema type as defined above? It seems to acknowledge the type, but not operate using it.
Or are users expected to create type-handling additions in xsltforms.js?
I am unclear as to the situation in XSLTForms 1.7, which is the version I am using.
Please advise, and thank you in advance!
-Tony Bufort,
AJB Consulting
[ttp://www.ajbconsulting.us/images/outlook/AJB_Consulting_new_logo_OUTLOOK_SIGNATURE.png]
www.ajbconsulting.us <http://www.ajbconsulting.us/>
Anthony J. (Tony) Bufort
Owner / Sr. Developer
[ttp://www.ajbconsulting.us/images/outlook/icons/email.png]
EMAIL: ajb...@aj... <email:ajb...@aj...>
[ttp://www.ajbconsulting.us/images/outlook/icons/phone.png]
PHONE: (425) 221-4447
[ttp://www.ajbconsulting.us/images/outlook/icons/skype.png]
SKYPE: ajbufort
[ttp://www.ajbconsulting.us/images/outlook/icons/linkedin.png]
LINKEDIN: www.linkedin.com/in/anthonybufort <http://www.linkedin.com/in/anthonybufort>
[ttp://www.ajbconsulting.us/images/outlook/wa_state_seal_sm.jpg]
A fully licensed, fully insured Washington state entity. |
|
From: Alain C. <ala...@ag...> - 2023-10-06 06:26:25
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Hello Tony,
</div>
<div class="default-style">
</div>
<div class="default-style">
I would suspect a missing namespace declaration because there is no prefix for "DateTimeWithTimezoneDatatype". A minimal test form should be necessary to investigate.
</div>
<div class="default-style">
</div>
<div class="default-style">
There is currently not full support for XML Schema but restrictions on simple types should work.
</div>
<div class="default-style">
</div>
<div class="default-style">
XSLTForms 1.7 is the latest version. It is based on HTML custom elements. Styling is to be done accordingly so transition with previous releases, before 1.5, can be non intuitive.
</div>
<div class="default-style">
</div>
<div class="default-style">
Thank you for your feedback!
</div>
<div class="default-style">
</div>
<div class="default-style">
--Alain
</div>
<blockquote type="cite">
<div>
Le 06/10/2023 06:45 CEST, ajb...@aj... a écrit :
</div>
<div>
</div>
<div>
</div>
<div class="WordSection1">
<p class="MsoNormal">Hello Alain and Company,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I am a new user of XSLTForms, exploring the framework, and am quite impressed, especially considering it’s a free product.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">However, I would like confirmation that what I am seeing is indeed the case, or if I am missing something, regarding handling custom types.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">In my model definition I reference a schema file, expecting to link up the types defined therein to my bind statements. The types I am trying to use are <em>simpleTypes</em>. Here is an example:</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="font-size: 9.0pt; font-family: 'Courier New'; color: #203864; mso-style-textfill-fill-color: #203864; mso-style-textfill-fill-alpha: 100.0%;"><xs:simpleType name="DateTimeWithTimezoneDatatype"><br> <xs:annotation><br> <xs:documentation>A string representing a point in time with a required timezone.</xs:documentation><br> </xs:annotation><br> <xs:restriction base="DateTimeDatatype"><br> <xs:pattern value="(((2000|2400|2800|(19|2[0-9](0[48]|[2468][048]|[13579][26])))-02-29)|(((19|2[0-9])[0-9]{2})-02-(0[1-9]|1[0-9]|2[0-8]))|(((19|2[0-9])[0-9]{2})-(0[13578]|10|12)-(0[1-9]|[12][0-9]|3[01]))|(((19|2[0-9])[0-9]{2})-(0[469]|11)-(0[1-9]|[12][0-9]|30)))T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])(\.[0-9]+)?(Z|(-((0[0-9]|1[0-2]):00|0[39]:30)|\+((0[0-9]|1[0-4]):00|(0[34569]|10):30|(0[58]|12):45)))"/><br> </xs:restriction></span></p>
<p class="MsoNormal"><span style="font-size: 9.0pt; font-family: 'Courier New'; color: #203864; mso-style-textfill-fill-color: #203864; mso-style-textfill-fill-alpha: 100.0%;"></xs:simpleType></span></p>
<p class="MsoNormal"><span style="color: #203864; mso-style-textfill-fill-color: #203864; mso-style-textfill-fill-alpha: 100.0%;"> </span></p>
<p class="MsoNormal">And the bind trying to use it (the ‘o:’ namespace used in @ref is indeed confirmed correct):</p>
<p class="MsoNormal"><span style="color: #203864; mso-style-textfill-fill-color: #203864; mso-style-textfill-fill-alpha: 100.0%;"> </span></p>
<p class="MsoNormal"><span style="font-size: 9.0pt; font-family: 'Courier New'; color: #203864; mso-style-textfill-fill-color: #203864; mso-style-textfill-fill-alpha: 100.0%;"><xf:bind id="/published" ref="/o:published" type=" DateTimeWithTimezoneDatatype"/></span></p>
<p class="MsoNormal"><span style="color: #203864; mso-style-textfill-fill-color: #203864; mso-style-textfill-fill-alpha: 100.0%;"> </span></p>
<p class="MsoNormal"><span style="color: #203864; mso-style-textfill-fill-color: #203864; mso-style-textfill-fill-alpha: 100.0%;">And finally, the input field:<br><br></span><span style="font-size: 9.0pt; font-family: 'Courier New'; color: #203864; mso-style-textfill-fill-color: #203864; mso-style-textfill-fill-alpha: 100.0%;"><xf:input bind="/published" incremental="true" type-ref="</span> <span style="font-size: 9.0pt; font-family: 'Courier New'; color: #203864; mso-style-textfill-fill-color: #203864; mso-style-textfill-fill-alpha: 100.0%;">DateTimeWithTimezoneDatatype"></span></p>
<p class="MsoNormal"><span style="font-size: 9.0pt; font-family: 'Courier New'; color: #203864; mso-style-textfill-fill-color: #203864; mso-style-textfill-fill-alpha: 100.0%;"> <xf:label></span></p>
<p class="MsoNormal"><span style="font-size: 9.0pt; font-family: 'Courier New'; color: #203864; mso-style-textfill-fill-color: #203864; mso-style-textfill-fill-alpha: 100.0%;"> <b>Published:</b></span></p>
<p class="MsoNormal"><span style="font-size: 9.0pt; font-family: 'Courier New'; color: #203864; mso-style-textfill-fill-color: #203864; mso-style-textfill-fill-alpha: 100.0%;"> </xf:label></span></p>
<p class="MsoNormal"><span style="font-size: 9.0pt; font-family: 'Courier New'; color: #203864; mso-style-textfill-fill-color: #203864; mso-style-textfill-fill-alpha: 100.0%;"></xf:input></span></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="mso-ligatures: none;">I get no ostensible complaints from the xf processor, but no validation behavior either (i.e. entering invalid values provokes no response). </span></p>
<p class="MsoNormal"><span style="mso-ligatures: none;"> </span></p>
<p class="MsoNormal"><span style="mso-ligatures: none;">(Note that the slashes in the @id and @bind attributes seem to be permissible if non-standard.)</span></p>
<p class="MsoNormal"><span style="mso-ligatures: none;"> </span></p>
<p class="MsoNormal"><span style="mso-ligatures: none;">Can the XSLTForms processor handle the schema type as defined above? It seems to acknowledge the type, but not operate using it.</span></p>
<p class="MsoNormal"><span style="mso-ligatures: none;"> </span></p>
<p class="MsoNormal"><span style="mso-ligatures: none;">Or are users expected to create type-handling additions in xsltforms.js?</span></p>
<p class="MsoNormal"><span style="mso-ligatures: none;"> </span></p>
<p class="MsoNormal"><span style="mso-ligatures: none;">I am unclear as to the situation in XSLTForms 1.7, which is the version I am using.</span></p>
<p class="MsoNormal"><span style="mso-ligatures: none;"> </span></p>
<p class="MsoNormal"><span style="mso-ligatures: none;">Please advise, and thank you in advance!</span></p>
<p class="MsoNormal"><span style="mso-ligatures: none;"> </span></p>
<p class="MsoNormal"><span style="mso-ligatures: none;">-Tony Bufort, </span></p>
<p class="MsoNormal"><span style="mso-ligatures: none;">AJB Consulting</span></p>
<p class="MsoNormal"><span style="mso-ligatures: none;"> </span></p>
<table class="MsoNormalTable" border="0" cellpadding="0">
<tbody>
<tr>
<td style="border: solid red 1.0pt; border-left: none; padding: .75pt 5.25pt .75pt .75pt;"> <p class="MsoNormal"><span style="font-family: 'Arial',sans-serif;"><img id="Picture_x0020_1" style="width: 1.6354in; height: .875in;" src="cid:image001.png@01D9F797.15A6DE00" alt="ttp://www.ajbconsulting.us/images/outlook/AJB_Consulting_new_logo_OUTLOOK_SIGNATURE.png" width="157" height="84"></span></p> <p class="MsoNormal"><span style="font-family: Courier; mso-ligatures: none;"><a href="http://www.ajbconsulting.us/"><span style="color: blue;">www.ajbconsulting.us</span></a></span></p> </td>
<td style="border: solid red 1.0pt; border-right: none; padding: .75pt .75pt .75pt 3.75pt;"> <p class="MsoNormal"><span style="font-size: 12.0pt; font-family: 'Arial',sans-serif; mso-ligatures: none;"> <strong>Anthony J. (Tony) Bufort</strong><br> </span><em><span style="font-family: 'Arial',sans-serif; mso-ligatures: none;">Owner / Sr. Developer</span></em></p>
<table class="MsoNormalTable" border="0" cellpadding="0">
<tbody>
<tr>
<td style="padding: .75pt .75pt .75pt .75pt;"> <p class="MsoNormal"><span style="font-size: 9.0pt;"><img id="Picture_x0020_2" style="width: .1666in; height: .1666in;" src="cid:image002.png@01D9F797.15A6DE00" alt="ttp://www.ajbconsulting.us/images/outlook/icons/email.png" width="16" height="16" border="0"></span></p> </td>
<td style="padding: .75pt .75pt .75pt .75pt;"> <p class="MsoNormal"><strong><span style="font-size: 9.0pt; mso-ligatures: none;">EMAIL:</span></strong><span style="font-size: 9.0pt; mso-ligatures: none;"> <a><span style="color: blue;">ajb...@aj...</span></a></span></p> </td>
</tr>
<tr>
<td style="padding: .75pt .75pt .75pt .75pt;"> <p class="MsoNormal"><span style="font-size: 9.0pt;"><img id="Picture_x0020_3" style="width: .1666in; height: .1666in;" src="cid:image003.png@01D9F797.15A6DE00" alt="ttp://www.ajbconsulting.us/images/outlook/icons/phone.png" width="16" height="16" border="0"></span></p> </td>
<td style="padding: .75pt .75pt .75pt .75pt;"> <p class="MsoNormal"><strong><span style="font-size: 9.0pt; mso-ligatures: none;">PHONE:</span></strong><span style="font-size: 9.0pt; mso-ligatures: none;"> (425) 221-4447</span></p> </td>
</tr>
<tr>
<td style="padding: .75pt .75pt .75pt .75pt;"> <p class="MsoNormal"><span style="font-size: 9.0pt;"><img id="Picture_x0020_4" style="width: .1666in; height: .1666in;" src="cid:image004.png@01D9F797.15A6DE00" alt="ttp://www.ajbconsulting.us/images/outlook/icons/skype.png" width="16" height="16" border="0"></span></p> </td>
<td style="padding: .75pt .75pt .75pt .75pt;"> <p class="MsoNormal"><strong><span style="font-size: 9.0pt; mso-ligatures: none;">SKYPE:</span></strong><span style="font-size: 9.0pt; mso-ligatures: none;"> ajbufort</span></p> </td>
</tr>
<tr>
<td style="padding: .75pt .75pt .75pt .75pt;"> <p class="MsoNormal"><span style="font-size: 9.0pt;"><img id="Picture_x0020_5" style="width: .1666in; height: .1666in;" src="cid:image005.png@01D9F797.15A6DE00" alt="ttp://www.ajbconsulting.us/images/outlook/icons/linkedin.png" width="16" height="16" border="0"></span></p> </td>
<td style="padding: .75pt .75pt .75pt .75pt;"> <p class="MsoNormal"><strong><span style="font-size: 9.0pt; mso-ligatures: none;">LINKEDIN:</span></strong><span style="font-size: 9.0pt; mso-ligatures: none;"> <a href="http://www.linkedin.com/in/anthonybufort"><span style="color: blue;">www.linkedin.com/in/anthonybufort</span></a></span></p> </td>
</tr>
</tbody>
</table> </td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="display: none; mso-ligatures: none;"> </span></p>
<table class="MsoNormalTable" style="border: none; border-bottom: solid red 1.0pt;" border="1" cellpadding="0">
<tbody>
<tr>
<td style="border: none; padding: 3.0pt .75pt .75pt .75pt;"> <p class="MsoNormal"><span style="font-size: 9.0pt; font-family: 'Arial',sans-serif; mso-ligatures: none;"> <img id="Picture_x0020_6" style="width: .3958in; height: .2604in;" src="cid:image006.jpg@01D9F797.15A6DE00" alt="ttp://www.ajbconsulting.us/images/outlook/wa_state_seal_sm.jpg" width="38" height="25" border="0"></span></p> </td>
<td style="border: none; padding: 3.0pt .75pt .75pt .75pt;"> <p class="MsoNormal"><span style="font-size: 9.0pt; font-family: 'Arial',sans-serif; mso-ligatures: none;"> A <strong><em>fully licensed, fully insured</em></strong> Washington state entity. </span></p> </td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="mso-ligatures: none;"> </span></p>
<p class="MsoNormal"> </p>
</div> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support
</blockquote>
</body>
</html> |
|
From: <ajb...@aj...> - 2023-10-06 06:01:11
|
Hello Alain and Company,
I am a new user of XSLTForms, exploring the framework, and am quite
impressed, especially considering it's a free product.
However, I would like confirmation that what I am seeing is indeed the case,
or if I am missing something, regarding handling custom types.
In my model definition I reference a schema file, expecting to link up the
types defined therein to my bind statements. The types I am trying to use
are simpleTypes. Here is an example:
<xs:simpleType name="DateTimeWithTimezoneDatatype">
<xs:annotation>
<xs:documentation>A string representing a point in time with a
required timezone.</xs:documentation>
</xs:annotation>
<xs:restriction base="DateTimeDatatype">
<xs:pattern
value="(((2000|2400|2800|(19|2[0-9](0[48]|[2468][048]|[13579][26])))-02-29)|
(((19|2[0-9])[0-9]{2})-02-(0[1-9]|1[0-9]|2[0-8]))|(((19|2[0-9])[0-9]{2})-(0[
13578]|10|12)-(0[1-9]|[12][0-9]|3[01]))|(((19|2[0-9])[0-9]{2})-(0[469]|11)-(
0[1-9]|[12][0-9]|30)))T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])(\.[0-9]+
)?(Z|(-((0[0-9]|1[0-2]):00|0[39]:30)|\+((0[0-9]|1[0-4]):00|(0[34569]|10):30|
(0[58]|12):45)))"/>
</xs:restriction>
</xs:simpleType>
And the bind trying to use it (the 'o:' namespace used in @ref is indeed
confirmed correct):
<xf:bind id="/published" ref="/o:published" type="
DateTimeWithTimezoneDatatype"/>
And finally, the input field:
<xf:input bind="/published" incremental="true" type-ref="
DateTimeWithTimezoneDatatype">
<xf:label>
<b>Published:</b>
</xf:label>
</xf:input>
I get no ostensible complaints from the xf processor, but no validation
behavior either (i.e. entering invalid values provokes no response).
(Note that the slashes in the @id and @bind attributes seem to be
permissible if non-standard.)
Can the XSLTForms processor handle the schema type as defined above? It
seems to acknowledge the type, but not operate using it.
Or are users expected to create type-handling additions in xsltforms.js?
I am unclear as to the situation in XSLTForms 1.7, which is the version I am
using.
Please advise, and thank you in advance!
-Tony Bufort,
AJB Consulting
<http://www.ajbconsulting.us/> www.ajbconsulting.us
Anthony J. (Tony) Bufort
Owner / Sr. Developer
EMAIL: <email:ajb...@aj...> ajb...@aj...
PHONE: (425) 221-4447
SKYPE: ajbufort
LINKEDIN: <http://www.linkedin.com/in/anthonybufort>
www.linkedin.com/in/anthonybufort
A fully licensed, fully insured Washington state entity.
|
|
From: Javier D. Estebaranz(UST,ES) <Jav...@us...> - 2023-10-04 15:23:34
|
Hello,
you can set headers in a submission with xsltforms, with something similar to:
<xf:submission id="send_authorized_req" method="get" replace="instance" instance="---instance name ---" resource="---url---" mode="synchronous">
<xf:header>
<xf:name>Authorization</xf:name>
<xf:value>Basic: ----credential---</xf:value>
</xf:header>
</xf:submission>
where ----credential--- is the user+password in base64 encoding (https://en.wikipedia.org/wiki/Basic_access_authentication).
I don't know if you can set headers in <xf:instance src="---url---"/> request (I haven't seen anything about it), but you can force a submission when page is finishing to load, so I think it could work for you something like this:
<xf:action ev:event="xforms-ready">
<xf:send submission="send_authorized_req"/>
</xf:action>
Best Regards,
Javier
El 4/10/23 a las 15:11, Richard Light escribió:
EXTERNAL EMAIL - Do not click any links or open any attachments unless you trust the sender and know the content is safe.
Our XForms application is pulling in various resources which are protected by Basic authentication. Given that XForms simply offers the src="XXX" syntax for accessing these external resources, what do people do/advise?
I can make it work by using the syntax:
http(s)://[username]:[password]@[requested URL]
(although my colleague gets a "401 (Unauthorised)" error for exactly the same URL), but this is surely a massive security hole, since the username and password are sitting there in full view in the XForms document.
Any thoughts or advice welcome!
Richard
--
________________________________
Richard Light
ric...@gm...<mailto:ric...@gm...>
@richardofsussex
_______________________________________________
Xsltforms-support mailing list
Xsl...@li...<mailto:Xsl...@li...>
https://lists.sourceforge.net/lists/listinfo/xsltforms-support
|
|
From: Richard L. <ric...@gm...> - 2023-10-04 13:11:29
|
Our XForms application is pulling in various resources which are protected by Basic authentication. Given that XForms simply offers the src="XXX" syntax for accessing these external resources, what do people do/advise? I can make it work by using the syntax: http(s)://[username]:[password]@[requested URL] (although my colleague gets a "401 (Unauthorised)" error for exactly the same URL), but this is surely a massive security hole, since the username and password are sitting there in full view in the XForms document. Any thoughts or advice welcome! Richard -- ------------------------------------------------------------------------ *Richard Light* ric...@gm... /@richardofsussex/ |
|
From: Steven P. <ste...@cw...> - 2023-09-29 16:39:47
|
On Friday 29 September 2023 16:27:01 (+02:00), Richard Light wrote:
Hi,
When I have a date value in a control, the calendar picker pops up and lets
me select a date. However, this is in the format 'MM/dd/YYYY', i.e.
American format.
xsltforms decides on the format to output dates using your environment. I
get the format dd/mm/yyyy from the calendar popup, and generally any user
of my XForms gets dates displayed in the form that they expect, not in the
form that I expect.
However, it is important to realise that how values are displayed is not
necessarily how they are stored (and vice versa). Dates for instance (at
least values that are declared as being of one of the date types) are
always stored using the ISO format 2023-09-29, so your substring-before( .,
'/') is never going to work, because they are stored using hyphens, not
slashes.
In general <output ref="..."/> takes types into account, and <output
value="..."/> doesn't and gives you the stored value.
Steven
I've tried putting xml:lang="en" into various places, but this doesn't
affect the outcome. Is there a special place to put xml:lang I have missed,
or is this not how you control the format of selected dates?
As well as switching day and month, I would really like to output the dates
that the user selects in the format we recommend to our users:
'dd.mm.YYYY'. I've tried writing a <setvalue> command, but to no avail:
<action ev:event="xforms-ready">
<setvalue
ref="ProcedureTemplate/Object/Movement/DateRequested"
value="concat(substring-before(substring-after(., '/'), '/'), '.',
substring-before(., '/'), '.', substring-after(substring-after(., '/'),
'/'))"/>
</action>
Is this approach doomed to failure, or have I just made a minor coding
error?
Thanks,
Richard
--
Richard Light
ric...@gm... <mailto:ric...@gm...>
@richardofsussex |
|
From: Richard L. <ric...@gm...> - 2023-09-29 14:45:04
|
Hi, To answer part of my own question: > As well as switching day and month, I would really like to output the > dates that the user selects in the format we recommend to our users: > 'dd.mm.YYYY'. I've tried writing a <setvalue> command, but to no avail: > > > <action ev:event="xforms-ready"> > > <setvalue > > ref="ProcedureTemplate/Object/Movement/DateRequested" > > value="concat(substring-before(substring-after(., '/'), '/'), '.', > > substring-before(., '/'), '.', substring-after(substring-after(., > > '/'), '/'))"/> > > </action> > Is this approach doomed to failure, or have I just made a minor coding > error? I had indeed made a coding error. In my XForms document I have chosen to declare the xf: prefix, so the above code was never acted upon. On adding the prefix, it works perfectly, in a sense. When I click on the three dots to the right of the input I get: without the date picker ever being displayed. Two dots is exactly what my value XPath should produce, when acting on an empty string. Presumably I need to call my action in response to a different event? Or is this whole approach doomed to failure? Thanks, Richard -- ------------------------------------------------------------------------ *Richard Light* ric...@gm... /@richardofsussex/ |
|
From: Richard L. <ric...@gm...> - 2023-09-29 14:27:13
|
Hi, When I have a date value in a control, the calendar picker pops up and lets me select a date. However, this is in the format 'MM/dd/YYYY', i.e. American format. I've tried putting xml:lang="en" into various places, but this doesn't affect the outcome. Is there a special place to put xml:lang I have missed, or is this not how you control the format of selected dates? As well as switching day and month, I would really like to output the dates that the user selects in the format we recommend to our users: 'dd.mm.YYYY'. I've tried writing a <setvalue> command, but to no avail: > <action ev:event="xforms-ready"> > <setvalue > ref="ProcedureTemplate/Object/Movement/DateRequested" > value="concat(substring-before(substring-after(., '/'), '/'), '.', > substring-before(., '/'), '.', substring-after(substring-after(., > '/'), '/'))"/> > </action> Is this approach doomed to failure, or have I just made a minor coding error? Thanks, Richard -- ------------------------------------------------------------------------ *Richard Light* ric...@gm... /@richardofsussex/ |
|
From: Richard L. <ric...@gm...> - 2023-09-28 13:15:46
|
Steven, Got that: thanks. Works a treat: Richard On 28/09/2023 13:36, Steven Pemberton wrote: > On Thursday 28 September 2023 14:24:14 (+02:00), Richard Light wrote: > > On 28/09/2023 12:50, Steven Pemberton wrote: >> Using <xf:copy ref="."> instead of <xf:value ref="@id">? > > Ah, clever! (I have a lot to learn ...) > > Thank you: I can now get the text content of all the selected XML > records dumped out as a long unformatted string, using <xf:output > ref="Object/ItemList">. > > I see I can use the value attribute on <xf:output> to evaluate a > single XPath expression, but is there a way of iterating over the > nodeset of selected Object elements and just outputting selected > elements, ideally with some formatting? > > That's what <repeat ref="..."> is for. > > I have written an XForms hands-on tutorial, available at > https://cwi.nl/~steven/xforms/xforms-hands-on/ which introduces many > of these techniques, and I will be giving a follow-on advanced XForms > hands-on at the Declarative Amsterdam conference on November 1st > (online and live). > > https://declarative.amsterdam/ > > Steven > > Thanks, > > Richard > >> >> Steven >> >> On Thursday 28 September 2023 12:40:17 (+02:00), Richard Light wrote: >> >> Hi, >> >> When I make a selection from a number of options: >> >>> <xf:select bind="object-list" appearance="full"> >>> <xf:label>Objects to move:</xf:label> >>> <xf:itemset model="objects-chosen" >>> nodeset="instance('objects')/record"> >>> <xf:label ref="Object/ObjectIdentity/Number"/> >>> <xf:value ref="@id"/> >>> </xf:itemset> >>> </xf:select> >> The <object-list> in my model is dynamically populated with a >> space-separated list of id's. >> >> What I would like to be able to do is to display (elsewhere >> on the XForm) selected information for each of the objects >> which is currently selected. I can (and currently do) >> display /all /the objects, e.g.: >> >>> <h4>Object details:</h4> >>> <div> >>> <p><b><xf:output >>> ref="instance('objects')/record[1]/Object/ObjectIdentity/Number"/></b> >>> <br/><b>Identification: </b> <xf:output >>> ref="instance('objects')/record[1]/Object/Identification/ObjectName/Keyword"/>; >>> >>> <xf:output >>> ref="instance('objects')/record[1]/Object/Identification/BriefDescription"/></p> >>> </div> >> Is there a way of iterating over the selected objects and >> outputting only their details? >> >> Thanks, >> >> Richard >> >> -- >> ------------------------------------------------------------------------ >> *Richard Light* >> ric...@gm... >> /@richardofsussex/ >> > -- > ------------------------------------------------------------------------ > *Richard Light* > ric...@gm... > /@richardofsussex/ > -- ------------------------------------------------------------------------ *Richard Light* ric...@gm... /@richardofsussex/ |
|
From: Steven P. <ste...@cw...> - 2023-09-28 12:36:52
|
On Thursday 28 September 2023 14:24:14 (+02:00), Richard Light wrote: On 28/09/2023 12:50, Steven Pemberton wrote: Using <xf:copy ref="."> instead of <xf:value ref="@id">? Ah, clever! (I have a lot to learn ...) Thank you: I can now get the text content of all the selected XML records dumped out as a long unformatted string, using <xf:output ref="Object/ItemList">. I see I can use the value attribute on <xf:output> to evaluate a single XPath expression, but is there a way of iterating over the nodeset of selected Object elements and just outputting selected elements, ideally with some formatting? That's what <repeat ref="..."> is for. I have written an XForms hands-on tutorial, available at https://cwi.nl/~steven/xforms/xforms-hands-on/ which introduces many of these techniques, and I will be giving a follow-on advanced XForms hands-on at the Declarative Amsterdam conference on November 1st (online and live). https://declarative.amsterdam/ Steven Thanks, Richard Steven On Thursday 28 September 2023 12:40:17 (+02:00), Richard Light wrote: Hi, When I make a selection from a number of options: <xf:select bind="object-list" appearance="full"> <xf:label>Objects to move:</xf:label> <xf:itemset model="objects-chosen" nodeset="instance('objects')/record"> <xf:label ref="Object/ObjectIdentity/Number"/> <xf:value ref="@id"/> </xf:itemset> </xf:select> The <object-list> in my model is dynamically populated with a space-separated list of id's. What I would like to be able to do is to display (elsewhere on the XForm) selected information for each of the objects which is currently selected. I can (and currently do) display all the objects, e.g.: <h4>Object details:</h4> <div> <p><b><xf:output ref="instance('objects')/record[1]/Object/ObjectIdentity/Number"/></b> <br/><b>Identification: </b> <xf:output ref="instance('objects')/record[1]/Object/Identification/ObjectName/Keyword"/>; <xf:output ref="instance('objects')/record[1]/Object/Identification/BriefDescription"/></p> </div> Is there a way of iterating over the selected objects and outputting only their details? Thanks, Richard -- Richard Light ric...@gm... <mailto:ric...@gm...> @richardofsussex -- Richard Light ric...@gm... <mailto:ric...@gm...> @richardofsussex |
|
From: Richard L. <ric...@gm...> - 2023-09-28 12:24:30
|
On 28/09/2023 12:50, Steven Pemberton wrote:
> Using <xf:copy ref="."> instead of <xf:value ref="@id">?
Ah, clever! (I have a lot to learn ...)
Thank you: I can now get the text content of all the selected XML
records dumped out as a long unformatted string, using <xf:output
ref="Object/ItemList">.
I see I can use the value attribute on <xf:output> to evaluate a single
XPath expression, but is there a way of iterating over the nodeset of
selected Object elements and just outputting selected elements, ideally
with some formatting?
Thanks,
Richard
>
> Steven
>
> On Thursday 28 September 2023 12:40:17 (+02:00), Richard Light wrote:
>
> Hi,
>
> When I make a selection from a number of options:
>
>> <xf:select bind="object-list" appearance="full">
>> <xf:label>Objects to move:</xf:label>
>> <xf:itemset model="objects-chosen"
>> nodeset="instance('objects')/record">
>> <xf:label ref="Object/ObjectIdentity/Number"/>
>> <xf:value ref="@id"/>
>> </xf:itemset>
>> </xf:select>
> The <object-list> in my model is dynamically populated with a
> space-separated list of id's.
>
> What I would like to be able to do is to display (elsewhere on the
> XForm) selected information for each of the objects which is
> currently selected. I can (and currently do) display /all /the
> objects, e.g.:
>
>> <h4>Object details:</h4>
>> <div>
>> <p><b><xf:output
>> ref="instance('objects')/record[1]/Object/ObjectIdentity/Number"/></b>
>> <br/><b>Identification: </b> <xf:output
>> ref="instance('objects')/record[1]/Object/Identification/ObjectName/Keyword"/>;
>>
>> <xf:output
>> ref="instance('objects')/record[1]/Object/Identification/BriefDescription"/></p>
>> </div>
> Is there a way of iterating over the selected objects and
> outputting only their details?
>
> Thanks,
>
> Richard
>
> --
> ------------------------------------------------------------------------
> *Richard Light*
> ric...@gm...
> /@richardofsussex/
>
--
------------------------------------------------------------------------
*Richard Light*
ric...@gm...
/@richardofsussex/ |
|
From: Steven P. <ste...@cw...> - 2023-09-28 12:09:49
|
Using <xf:copy ref="."> instead of <xf:value ref="@id">?
Steven
On Thursday 28 September 2023 12:40:17 (+02:00), Richard Light wrote:
Hi,
When I make a selection from a number of options:
<xf:select bind="object-list" appearance="full">
<xf:label>Objects to move:</xf:label>
<xf:itemset model="objects-chosen"
nodeset="instance('objects')/record">
<xf:label ref="Object/ObjectIdentity/Number"/>
<xf:value ref="@id"/>
</xf:itemset>
</xf:select>
The <object-list> in my model is dynamically populated with a
space-separated list of id's.
What I would like to be able to do is to display (elsewhere on the XForm)
selected information for each of the objects which is currently selected.
I can (and currently do) display all the objects, e.g.:
<h4>Object details:</h4>
<div>
<p><b><xf:output
ref="instance('objects')/record[1]/Object/ObjectIdentity/Number"/></b>
<br/><b>Identification: </b> <xf:output
ref="instance('objects')/record[1]/Object/Identification/ObjectName/Keyword"/>;
<xf:output
ref="instance('objects')/record[1]/Object/Identification/BriefDescription"/></p>
</div>
Is there a way of iterating over the selected objects and outputting only
their details?
Thanks,
Richard
--
Richard Light
ric...@gm... <mailto:ric...@gm...>
@richardofsussex |
|
From: Richard L. <ric...@gm...> - 2023-09-28 10:40:32
|
Hi,
When I make a selection from a number of options:
> <xf:select bind="object-list" appearance="full">
> <xf:label>Objects to move:</xf:label>
> <xf:itemset model="objects-chosen"
> nodeset="instance('objects')/record">
> <xf:label ref="Object/ObjectIdentity/Number"/>
> <xf:value ref="@id"/>
> </xf:itemset>
> </xf:select>
The <object-list> in my model is dynamically populated with a
space-separated list of id's.
What I would like to be able to do is to display (elsewhere on the
XForm) selected information for each of the objects which is currently
selected. I can (and currently do) display /all /the objects, e.g.:
> <h4>Object details:</h4>
> <div>
> <p><b><xf:output
> ref="instance('objects')/record[1]/Object/ObjectIdentity/Number"/></b>
> <br/><b>Identification: </b> <xf:output
> ref="instance('objects')/record[1]/Object/Identification/ObjectName/Keyword"/>;
>
> <xf:output
> ref="instance('objects')/record[1]/Object/Identification/BriefDescription"/></p>
> </div>
Is there a way of iterating over the selected objects and outputting
only their details?
Thanks,
Richard
--
------------------------------------------------------------------------
*Richard Light*
ric...@gm...
/@richardofsussex/ |
|
From: Alain C. <ala...@ag...> - 2023-05-15 17:29:54
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Hi Winona,
</div>
<div class="default-style">
</div>
<div class="default-style">
Yes, a simple example would be much helpful (line #14678 of xsltforms.js for 1.7 does not contain a removeChild call).
</div>
<div class="default-style">
</div>
<div class="default-style">
Thanks!
</div>
<div class="default-style">
</div>
<div class="default-style">
--Alain
</div>
<div class="default-style">
</div>
<blockquote type="cite">
<div>
Le 10/05/2023 14:09 CEST, Winona Salesky <wsa...@gm...> a écrit :
</div>
<div>
</div>
<div>
</div>
<div dir="ltr">
Hi Alain,
<br>
<div>
I have been testing out version 1.7 of XSLTForms for the past few weeks as I really want to take advantage of the support for xf:var. I have run into a few things that I believe are bugs with the new version, or at least things that worked in 1.3 but no longer work in 1.7.
</div>
<div>
</div>
<div>
In particular, I have a lookup function (in a subform) that loads search results into a select1 menu which the user can then add to the main instance. This worked in 1.3, but now returns the following error, when I select a result:
</div>
<div>
</div>
<div>
Error: Failed to execute 'removeChild' on 'Node' : the node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler? at xsltforms.js:14678:9
<br>at Array.forEach(<anonymous>)
</div>
<div>
</div>
<div>
Thoughts? Would you like me to mock up a simple example?
</div>
<div>
A complete example of the forms I am running can be found here:
</div>
<div>
<a href="https://github.com/majlis-erc/manuForma/tree/main/forms/msSimple">https://github.com/majlis-erc/manuForma/tree/main/forms/msSimple</a>
</div>
<div>
</div>
<div>
I run them in eXistdb v6.1.0
</div>
<div>
Thank you,
</div>
<div>
-Winona
</div>
<div>
</div>
</div> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support
</blockquote>
</body>
</html>
|
|
From: Winona S. <wsa...@gm...> - 2023-05-10 12:10:01
|
Hi Alain, I have been testing out version 1.7 of XSLTForms for the past few weeks as I really want to take advantage of the support for xf:var. I have run into a few things that I believe are bugs with the new version, or at least things that worked in 1.3 but no longer work in 1.7. In particular, I have a lookup function (in a subform) that loads search results into a select1 menu which the user can then add to the main instance. This worked in 1.3, but now returns the following error, when I select a result: Error: Failed to execute 'removeChild' on 'Node' : the node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler? at xsltforms.js:14678:9 at Array.forEach(<anonymous>) Thoughts? Would you like me to mock up a simple example? A complete example of the forms I am running can be found here: https://github.com/majlis-erc/manuForma/tree/main/forms/msSimple I run them in eXistdb v6.1.0 Thank you, -Winona |
97 messages has been excluded from this view by a project administrator.
![www.ajbconsulting.us/images/outlook/AJB_Consulting_new_logo_OUTLOOK_SIGNATURE.png"](http://www.ajbconsulting.us/images/outlook/AJB_Consulting_new_logo_OUTLOOK_SIGNATURE.png"){kind=link}
![www.ajbconsulting.us/images/outlook/icons/email.png"](http://www.ajbconsulting.us/images/outlook/icons/email.png"){kind=link}
![www.ajbconsulting.us/images/outlook/icons/phone.png"](http://www.ajbconsulting.us/images/outlook/icons/phone.png"){kind=link}
![www.ajbconsulting.us/images/outlook/icons/skype.png"](http://www.ajbconsulting.us/images/outlook/icons/skype.png"){kind=link}
![www.ajbconsulting.us/images/outlook/icons/linkedin.png"](http://www.ajbconsulting.us/images/outlook/icons/linkedin.png"){kind=link}
![www.ajbconsulting.us/images/outlook/wa_state_seal_sm.jpg"](http://www.ajbconsulting.us/images/outlook/wa_state_seal_sm.jpg"){kind=link}
