openmobilealliance-archive / void-openmobilealliance.github.io Goto Github PK

Inside of most of the registries there is a link called 'here' that needs to be connected with the corresponding registry. At the moment the link 'here' opens a form to submit registration information.

The task of creating marketing menus are split in two issues:

• This one, Create Marketing Menus
  The menus are:
  • About
  • Join
  • News
  • Events
  • Contact Us
  • Developers
• and "Add New Marketing Menus"
  These new menus are described on the other above issue
  • The reason for splitting these menus is because this second list contains new menus and content and it may need further changes and discussions with Marketing people.

In the following web pages:
OMAN/wsp/wsp_content_type_codes.html
OMAN/wsp/wsp-extended-methods.html
OMAN/wsp/wsp-header-code-page-names.html
OMAN/wsp/wsp-header-parameters.html
we pasted the content from the current registries: http://technical.openmobilealliance.org/Technical/technical-information/omna
We need to apply the corresponding styling to render the content correctly. If it is possible then, we will copy and paste the content from the rest of the registries and apply the corresponding styling.

Add footer as indicated in #61

@seanmcilroy29, @jmudge please be aware that I have updated ALL the IPSO objects inside in the following FTP folders:

• devwww.openmobilealliance.org/tech/profiles/lwm2m, and
• www.openmobilealliance.org/tech/profiles/IPSO

The reason for this update is because IPSO has reviewed some Objects files but we don't know which ones, so I have updated all of them.

When submitting a Technical Comments, the form currently provides the following Terms and Conditions:

"I am the sole owner of the information which I provide to OMA ('Submission') and have the authority without any restrictions to submit such information. The Submission is not confidential and contains no intellectual property rights ('IPR'). In the event that there were any IPR related to the Submission, I hereby grant to OMA and its members (present and future) a payment-free, royalty-free, perpetual, irrevocable, non-exclusive, worldwide license to use such IPR in any manner for any reason."

Comments is being access via at least two different type of links: from "Specifications" page and directly in from the technical menu.
We need to introduce a page or system that the user needs to accept before sending the email.
@jmudge Could you please prepare a plan on what and how to do it?

The link below contains an example of column and row merge.
You need to create a template containing a table that has this type of merges.

http://technical.openmobilealliance.org/Technical/technical-information/omna/omna-bcast-parental-rating-system-registry

There are RDs and ADs in the following folders that need to be moved into the release area:

• http://devwww.openmobilealliance.org/old-Technical/Release_Program/docs/RD
• http://devwww.openmobilealliance.org/old-Technical/Release_Program/docs/Arch

Previously it was possible to see at least two lines and click on "more" to see the rest of the description.
Since we split the content of the original page: in "LwM2MRegistry" and "LwM2MObjects" this functionality of view just two lines of the description stopped working.

Now that we have a baseline, can I make the DevMaster branch the master branch?

Thanks,
Nathan

@nathan-omaorg

On DevMaster OMA Specifications page in the right hand column I understand there is only expected to be one line of release notes now. This could be aligned vertically with the Version number.

See the mockups at SyncIT > Projects > Publication > Mockups-v2.xlsx

We need to create a subfolder "lwm2m" inside of "oma" folder.
Inside "lwm2m" we need to create a new template "lwm2m.htm"
This template will contain the Technical Menu plus the tables listed in the spreadhseet "View Registry"

Also, in this template "lwm2m.html" we need to need to add:

• code block as seen in the above spreadsheet
• replace the icon (information) for the first line of the description

Links within the WAP forum current pages that are not listed inside of the FTP.
http://www1.wapforum.org
http://www.wapforum.org

These two are included in the above webpages:
(especially http://www.wapforum.org/DTD &
http://www.wapforum.org/xslt)

The current mockup page http://openmobilealliance.org/about-oma/affiliates-2/ is missing the above links.

When clicking in a link it should open the page in a new tab.

@seanmcilroy29 , @jmudge , @nathan-omaorg

After discussing the Marketing menus with Elizabeth Rose, Marketing Manager, there is no need for us to create a set of Marketing Menus.
The Marketing Menus will be hosted in the Marketing WordPress page and will open a new page containing the index.file.

The final list of Marketing Menus can be seen in the mockup spreadsheet:

• About
• Join
• News
• Events
• Technical (updated)
• Specs (new)
• Developers
• Contact us

Change name of the file from index.html to specifications.html

Remove the link in the paragraph at the bottom of the (x-label). Keep the phase as seen below but remove the link. The reason for that is because there is still a pending discussion in DM if OMA really needs to register: individuals or vendors Objects. In the GitHub repository for LwM2M Register we haven't created any register for this option.

"The registration of individual and proprietary LwM2M Objects is currently under review."

On some of the registry pages the table headers, rows and dashed lines are not aligned on the far right hand side e.g. https://openmobilealliance.github.io/OMNA/wsp/wsp_content_type_codes.html .

This is also the case (but to a lesser extent) with the current production pages e.g. http://technical.openmobilealliance.org/Technical/technical-information/omna/omna-wsp-content-type

#14 @nathan-omaorg, @jmudge, @seanmcilroy29

Final list of menus in the Technical Menus:

• "Specifications", (file is called index.html)
• "Pubic Documents"
• "Supporting Data"
• "Registries"
• "Comments"
• "Watch/Unwatch"
• "Developer's"

The OMA icon is connected to the OMA Marketing homepage.
This final list was produced after discussions with the Marketing Manager

See mockups in spread sheet

1. Column titles should be in the center of the column
2. The declaration of "Historic" in the 3rd or 4th column should be part of the link e.g. "V1.0 - Historic"
   Where "Historic" is in red font.

@nathan-omaorg

On DevMaster OMA Specifications page in the left hand column the second line of a cell’s contents needs to use a smaller sized font and not be in bold.

See the mockups at SyncIT > Projects > Publication > Mockups-v2.xlsx

See the new tab "Footer" in the Mockups spreadsheet

Currently a number of OMNA registries have links to Register an item that doesn't exists.
These should be removed as it may cause a degree of confusion to the user

The first row of the tables that has blue background colour needs to be taller. The high of the this first row is a bit more than the high of the titles. We need at least another blank space.

See title

@seanmcilroy29
It is a good practice to don't name file names with blank spaces or event capital letters.
e.g. currently "BCAST Service Class Registry.html"
it should be called something like: "bcast-service-class-registry.html"
@jmudge may be able to provide you with even better rules
The reason for these rules is to improve how the links are encoded by the browser, sometimes they need feel the blank space with some characters.

• In addition to the column that calls the LwM2M Editor, we need add another column to open the object using Vorto
• Add a Search button to the page (see spreadsheet containing mockup)

Currently, to download documents from the affiliates it is necessary to accept a copyright.
Do we need to maintain this copyright in the new publication system?

The following table titles are not centered:

• public_documents
• registries
  However, index.html page uses the same table class ```class="table-bordered" but the table titles are centered.

Description

From web page http://devwww.openmobilealliance.org/tech/dtd/ when an attempt is made to download file with the extension mod the following error is displayed:

"Server Error
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable."

Note these files can be downloaded from the production web server.
E.g.
http://www.openmobilealliance.org/tech/DTD/wml-framework-1.mod - works
http://devwww.openmobilealliance.org/tech/dtd/wml-framework-1.mod - does not work

Table titles in the lwm2m registry page needs an enhancement: see a possible way to do it below
oma-label, ext-label, and x-label tables.
"Object ID" change it to "Object ID / xml"
"Object Name" change it to "Object Name / Specifications"
"Resource ID" change it to "Resource ID / xml"

Reusable Resources Table
"Resource Name / DDF" change it to "Resource Name / xml"
"Owner / TS" remove the "TS"

The registry will required the creation of new folders in the github repository.

• the registries.html page will be stored in the root folder
• "omna" folder needs to be created and stored in the root folder.
  • the "omna" folder will contain several folders inside. One folder for each register. And each of these folders will contain one or more html pages.

See details on the wiki pages under "Changes to Marketing Pages"
https://wiki.openmobilealliance.org/display/PROJ/Mapping+Public+Menus
The new menus in the marketing pages are: (each of these menus has sub-menus) see wiki

• Technical (previously called) "technology"
• Specifications
• TestFests
• Product Listing
  The rest of menus are under marketing pages don't change

Many of the registries use rowspan e.g. http://technical.openmobilealliance.org/Technical/technical-information/omna/omna-schema-based-namespace-registry . Displaying rows with alternating colours does not work well for these registries. If @nathan-omaorg added an option to alternate the colour of columns instead then this would help resolve this issue.

In the http://devwww.openmobilealliance.org/release/ directories there are many occurrences of the folder "_vti_cnf" e.g. http://devwww.openmobilealliance.org/release/DiagMon/V1_2-20131008-A/_vti_cnf/

Apparently these folders are created automatically by the FrontPage, Dreamweaver and Expression web. Are we currently using any of these programs (I'm not)? I noticed Carol using Dreamweaver a few years ago.

Opinion seems to be divided on whether "_vti_cnf" folders should be deleted. I would suggest that we delete them all before we go live with the new web pages.

This Issue is just to collect the information on how create a encoded link that opens the object or resource in the LwM2M Editor directly:

The new links has two components:
The link that opens the LwM2M Editor

• The link that opens the Editor in View mode is: http://devtoolkit.openmobilealliance.org/OEditor/LWMOView

The link that call the Object (encoded)

• The link that call the xml resource is: ?url=http%3A%2F%2Fdevwww.openmobilealliance.org%2Ftech%2Fprofiles%2FLWM2M_Security-v1_0.xml

This second link is unique for each object/resource and it needs to be encoded to ensure that it will work with all type of browsers.
A tool to encode links could be: http://meyerweb.com/eric/tools/dencoder/

1. Upload to this tool the link that points to the resource.
2. Copy and past in the HTML page the encoded link prefix by ?url=

The full link for the above example is: (it needs to be created in two steps: Open the LwM2M Editor part + the Link to the Object (encoded))
http://devtoolkit.openmobilealliance.org/OEditor/LWMOView?url=http%3A%2F%2Fdevwww.openmobilealliance.org%2Ftech%2Fprofiles%2FLWM2M_Security-v1_0.xml

Where will the links to the following pages be?

• LwM2M registry
• Supporting data
• Affiliates

I don't see them in the menu or elsewhere.

Thanks

There are some files with .ac as an extension that may need to have .txt instead.

Such as: http://devwww.openmobilealliance.org/tech/omna/Presence-v1_0.ac

This was originally brought up in issue #63

On page https://openmobilealliance.github.io/OMNA/wsp/wsp_content_type_codes.html in the Registered Values table some of the test content in the last column is not displayed e.g. for Assigned Number 0x0300. Please note that this is also true (but to a lesser extent) with the current production page at http://technical.openmobilealliance.org/Technical/technical-information/omna/omna-wsp-content-type .

We need to reuse the tables that display Objects and Resources in the LwM2M Editor Tool.
Suggestion:
Create a new file (LwM2MTables) which stores the tables that contain objects and embed that content in the LwM2MRegistry.

In this way we can reuse the LwM2MTables page in the LwM2M Editor tool without having to replicate this content over and over.
See Mockups-V5.xlsx spreadsheet in the syncfolder/projects/publication

In the OMA LightweightM2M (LwM2M) Object and Resource Registry web page (see https://openmobilealliance.github.io/OMNA/LwM2M/LwM2MRegistry.html)

The following top level menu links do not work:

• Specifications
• Public Documents
• Supporting Data
• Registries
• Comments

The "registries.html" page needs to be updated with the links to the registries that you are adding.
Also the "Register" of column needs to be updated to point the corresponding registration form.

@jmudge, @seanmcilroy29
As the "Affiliate" page has been moved under the Marketing pages.

@jmudge I am checking the links to the new http://devwww.openmobilealliance.org/tech/dtd and when upload it to a browser, it opens the ftp server rather than redirect but in your page "Supporting Data" it is redirected as we see on Tuesday.

It is something strange, could you check it again?

For pull request: #102

• bcast-client-manufacturer-code-registry.html looks wrong
  
• bcast-indentification-authority-registry.html looks wrong
  
• For any files that is a copy and paste from the existing registries (i.e. using DIVs instead of TABLE for layout), please remove: <script src="/Scripts/LwM2MRegistry.js"></script> from the HEAD
• Make sure you use the following template for the copied information from existing registries: /OMNA/wsp/RegistryTemplate.html

The top technical menu appears to be on the left of the screen rather than in the center as the rest of the content.

@jmudge This link "Comment" needs to point to the GitHub Issues for LwM2M Developers directly.

When an attempt is made to download the following file from the dev web site the error message "Server Error 404 - File or directory not found." is generated:
http://devwww.openmobilealliance.org/tech/omna/OMA-OIDs.asn

Perhaps the filetype asn is configured to be not allowed to be downloaded by the web server.