Closed acheambe closed 8 years ago
After analyzing the requirements for the URL factory we propose to follow the approach below:
We'll create an initial version of the class so that can be used now and then we'll be adding the intelligence to verify the semantics.
I would suggest to have it as much as possible compliant with WHATWG URL API standard, which was the basis of the reTHINK address model design and I've found this implementation:
@pchainho sure! We will review that implementation and study if we can reuse it for the reThink purposes. Moreover, some additional logic will be necessary to add some intelligence to decide if a given set of values for each field are consistent between them and coherent with the project description.
BTW, could you, please, give me access to https://github.com/reTHINK-project/architecture/blob/master/docs/datamodel/address/readme.md?? @antonroman shared a copy with me, but I don't have permission to read it in github.
Thanks,
I've just added you, @aecostas, to WP2 team : can you check pls?
Thanks @pchainho, it works
@aecostas : Great. Could you please use this document to specify the class attributes, constructor(s) and functionalities. Thx
At the end of the day we'll have completed 20% of the task, @acheambe please add @aecostas to frameworker-developer team so that we can start pushing code. Thanks!
Done. @aecostas should now have access to repository. In case you run into any problems on repo please let me know.
specification completed. Follow-up to this task in dev-service-framework repository
The Address Resource Factory creates the different types of URLs required as specified here.
specification document template