Re: [ubl-dev] makeaneinvoice.com

["Roberto Cisternino" <roberto@javest.com>]

> Will the UBL Security SC be looking to produce a conformance profile
> committee specification or standard to cover their final decisions on
> this?

Yes the intention is to keep clear and simple the use of the enveloped
signature.
However we are not constraining at all the use of XAdES or other
Standards, but just how signature should be applied to an UBL document.

This step seems to be important to have a reference guide to be mentioned
by national regulations provided by Public Administrations.

Probably we will evaluate also other kind of signatures but the enveloped
is one of the favorites and required in the real world.

> I guess that might be important to get real, interoperable
> implementations
> wouldn't it?
>
> Best regards
>
> Stephen D Green
>
>
>>>> "Roberto Cisternino" <roberto@javest.com> 16/11/09 11:48 >>>
> Thank you it is a nice sample !
>
> About the way the signature is referenced in the cac:Signature, this
> is
> still a draft proposal that is currently discussed within the UBL
> Security
> subcommitee.
>
> Pratically we are not sure the #Signature URI specified into the
> cac:Signature is the right way to reference the enveloped signature
> inside
> the UBLExtension.
>
> We are associating the ds:Signature/@id with an URI and this seems to
> be
> not xml friendly.
>
> There is currently the proposal to use an xpointer syntax containing
> the
> full xpath to reach the UBLExtension where the signature is enveloped:
>
> xpointer(//ext:UBLExtensions/ext:UBLExtension[1]/ext:ExtensionContent)
>
> Pratically this is still a valid URI and uses just the xpointer() part
> of
> the XPointer specification (so no troubles...) and has the benefit that
> we
> can specify the full XPath to reference the precise UBLExtension where
> the
> Signature is enveloped.
>
> This methodology seems to me more explicit and robust.
>
> I will appreciate your comments.
>
> Best regards
>
> Roberto Cisternino
>
>> Excellent. Many thanks. I hope your work goes very well.
>>
>> Best regards
>> ---
>> Stephen D Green
>>
>>
>>
>>
>> 2009/11/16 Enxendra Technologies <info@enxendra.com>:
>>> Hello, Stephen:
>>>
>>> Thank you for your congratulations.
>>> It is our intention to make things easy and useful.
>>>
>>> To see a signed invoice, it is attached one.
>>>
>>> Regards,
>>>
>>> Angel Aparicio
>>>
>>>
>>> Stephen Green wrote:
>>>
>>> Nice to see the changes now in place for making the e-invoice
>>> online. I've not tried the signing (no certificate) but the basic
>>> invoice creation works nicely and I found the form easy to use.
>>> Many thanks indeed.
>>>
>>> Congratulations
>>>
>>> Best regards
>>>
>>> Stephen D Green
>>>
>>>
>>>
>>> Stephen Green <stephengreenubl@gmail.com> 05/11/09 08:06 >>>
>>>
>>>
>>> That's terriffic. Many thanks and so glad to see this service.
>>> I'll be eager to see how it progresses. Very well done.
>>>
>>> Best regards
>>> ---
>>> Stephen D Green
>>>
>>>
>>>
>>>
>>> 2009/11/5 Enxendra Technologies <info@enxendra.com>:
>>>
>>>
>>> Many thanks for your comments Stephen. Make us happy your interest
> in
>>>
>>>
>>> the
>>>
>>>
>>> site!
>>> I answer on your mail:
>>>
>>> Stephen Green wrote:
>>>
>>> Wonderful site/provision. Congratulations!
>>>
>>> A few comments:
>>>
>>> I think there should be a question/answer in the FAQ about
>>> why the expiration data is needed (for the signature, not for
>>> the UBL invoice).
>>>
>>>
>>> I add here your next mail to answer it together
>>>
>>> "I've tried creating an invoice (without a certificate) - great
>>> - and now I realise that the expiration section relates to the
>>> payment due date. I think this is not so obvious (I first thought,
>>> wrongly it seems, it related to the certificate/signature expiry).
>>> I don't think an invoice 'expires' when payment is due. It carries
>>> on being valid as an invoice because if payment is not made
>>> it has to still be valid and maybe enforceable. So I think this
>>> section needs to be renamed, perhaps to 'payment due details'."
>>>
>>> You're right. Expiration date is really Payment date. We will
> change
>>>
>>>
>>> this
>>>
>>>
>>> name to make it clear.
>>> About why this data is needed it's a restriction on the site. We
> know
>>>
>>>
>>> that
>>>
>>>
>>> in UBL is not required but still we thought that we should
> establish
>>>
>>>
>>> a few
>>>
>>>
>>> additional data as required.
>>> So we follow your advice to include a new question / answer in the
>>>
>>>
>>> FAQ
>>>
>>>
>>> explaining this.
>>>
>>> It isn't clear what is the "Total" in "Total Summary" section
>>>
>>>
>>> You're right. We must especify that this "Total" is "Total to pay".
>>>
>>> I think there should be a question/answer in the FAQ about
>>> why the party Fiscal id is needed (for the signature, not for
>>> the UBL invoice? the UBL invoice doesn't make it mandatory).
>>>
>>>
>>> This case is the same as previous payments.
>>> We will add the question / answer in the FAQ.
>>>
>>> In any case it is not our intention that the website is fully
> closed.
>>>
>>>
>>> We are
>>>
>>>
>>> willing to make any changes deemed necessary to improve overall
>>>
>>>
>>> service to
>>>
>>>
>>> people. So if you advise us to change these points to make them not
>>> mandatory, we will do it.
>>>
>>> It isn't immediately clear that you have to click "add an invoice
>>> line" before the invoice line gets added (it is ambiguous - add
>>> invoice line could mean 'add another invoice line' - so if there
>>> is just one line it isn't obvious you have to click this). It does
>>> quickly become apparent though that you have to click this
>>> when you look at the total which doesn't include the line
>>> amount until you click it.
>>>
>>>
>>> You're right. We know this and we will change it for do it more
>>>
>>>
>>> easy.
>>>
>>>
>>> Maybe you should ask people to create a userid and login
>>> but you also need an assurance of whether the data people
>>> enter is stored against their userid if you do that (see also next
>>> comment).
>>>
>>> I think you need to include a privacy policy statement to
>>> ensure people are aware what happens to data they enter -
>>> whether it is stored on the server, who might have access to it
>>> and how long it is stored. Maybe something about this in the
>>> FAQ too. Maybe you should have a checkbox for the user to
>>> tick to state that they have read and agree to the privacy policy
>>> before they can continue to create the invoice. It also needs to
>>> include assurance of what will be done with their certificate -
>>> whether it is stored on the site server at all and who can access
>>> it, etc.
>>>
>>>
>>> The failure here is that we have forgotten to include a question /
>>>
>>>
>>> answer in
>>>
>>>
>>> the FAQ explaining what we do with the data.
>>> We don't store any data. In fact the service does not use a
> database.
>>>
>>>
>>> So we
>>>
>>>
>>> think is not needed to include any privacy policy.
>>> About the certificate is the same. The signing is done locally on
> the
>>>
>>>
>>> user
>>>
>>>
>>> computer, which the server has no access to certificates.
>>> Privacy in this service is indispensable for us.
>>>
>>> Some people might want some assurance of how long this site
>>> will likely be available and whether it will always be free to use.
>>>
>>>
>>> The site will be available indefinitely and always will be free.
> Our
>>> intention is to improve it, but not charge for its use.
>>> We are currently working on a premium service called eninvoice
>>> (http://www.enxendra.com/en/eninvoice), allowing many more
>>>
>>>
>>> possibilities,
>>>
>>>
>>> but makeaneinvoice.com will remain active and free.
>>>
>>> Maybe also make it clearer that the invoice produced is a UBL
>>> 2.0 one since only people whose systems can process UBL 2.0
>>> can receive the invoice this way - but I realise that accompanying
>>> it with a PDF might alleviate this a bit.
>>>
>>>
>>> You're right. We always specify that the final invoice is in UBL
> 2.0
>>>
>>>
>>> format.
>>>
>>>
>>> All in all it is so excellent to have such a web facility
> available.
>>>
>>>
>>> Thanks so much, Stephen!
>>>
>>> Many thanks.
>>>
>>> Best regards
>>> ---
>>> Stephen D Green
>>>
>>>
>>>
>>>
>>> 2009/11/4 Enxendra Technologies <info@enxendra.com>:
>>>
>>>
>>> Hello,
>>>
>>> Enxendra has done a free web site to make signed UBL 2.0 invoices:
>>>
>>> www.makeaneinvoice.com
>>>
>>> You can make the invoices with or without signature. To generate
> the
>>> signature you only need a digital certificate.
>>>
>>> We thank Ken Holman and Oriol Bausà their help.
>>>
>>> Any comments about the web are welcomed.
>>>
>>> Thanks.
>>>
>>> Enxendra Technologies
>>> www.enxendra.com
>>>
>>>
>>>
>>>
>>>
>>>
>>>
> ---------------------------------------------------------------------
>>>
>>>
>>> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
>>> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org
>>>
>>>
>>>
>>>
>>>
>>>
>>>
> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
>>> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org
>>>
>>>
> ______________________________________________________________________
>>> 'Do it online' with our growing range of online services -
>>> http://www.bristol.gov.uk/services
>>>
>>> Sign-up for our email bulletin giving news, have-your-say and event
>>> information at: http://www.bristol.gov.uk/newsdirect
>>>
>>> View webcasts of Council meetings at
> http://www.bristol.gov.uk/webcast
>>>
>>>
> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
>>> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org
>>>
>>>
>>>
>>>
>>>
> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
>>> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org
>>>
>>
>>
> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
>> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org
>>
>>
>
>
> --
> * JAVEST by Roberto Cisternino
> *
> * Document Engineering Services Ltd. - Alliance Member
> * UBL Italian Localization SubCommittee (ITLSC), co-Chair
> * UBL Online Community editorial board member (ubl.xml.org)
> * Italian UBL Advisor
>
>   Roberto Cisternino
>
>   mobile: +39 328 2148123
>   skype:  roberto.cisternino.ubl-itlsc
>
> [UBL Technical Committee]
>     http://www.oasis-open.org/committees/ubl
>
> [UBL Online Community]
>     http://ubl.xml.org
>
> [UBL International Conferences]
>     http://www.ublconference.org
>
> [UBL Italian Localization Subcommittee]
>     http://www.oasis-open.org/committees/ubl-itlsc
>
> [Iniziativa divulgativa UBL Italia]
>     http://www.ubl-italia.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org
>
> ______________________________________________________________________
> 'Do it online' with our growing range of online services -
> http://www.bristol.gov.uk/services
>
> Sign-up for our email bulletin giving news, have-your-say and event
> information at: http://www.bristol.gov.uk/newsdirect
>
> View webcasts of Council meetings at http://www.bristol.gov.uk/webcast
>
> Find out about the council's Cycling City project by visiting
> http://www.betterbybike.info/cycling-city-project-0
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org
>
>


-- 
* JAVEST by Roberto Cisternino
*
* Document Engineering Services Ltd. - Alliance Member
* UBL Italian Localization SubCommittee (ITLSC), co-Chair
* UBL Online Community editorial board member (ubl.xml.org)
* Italian UBL Advisor

  Roberto Cisternino

  mobile: +39 328 2148123
  skype:  roberto.cisternino.ubl-itlsc

[UBL Technical Committee]
    http://www.oasis-open.org/committees/ubl

[UBL Online Community]
    http://ubl.xml.org

[UBL International Conferences]
    http://www.ublconference.org

[UBL Italian Localization Subcommittee]
    http://www.oasis-open.org/committees/ubl-itlsc

[Iniziativa divulgativa UBL Italia]
    http://www.ubl-italia.org